Folder structure change?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Folder structure change?

Johan Solve-2
In the current suggested folder structure and how mt_nav behaves for includes and stuff, each type of file (config, action, library and content) are grouped into folders for each type of file.
Example:
index.lasso
_config:
        cfg_cust_edit.inc
        cfg_cust_list.inc
        cfg_order_edit.inc
        cfg_order_list.inc
_action:
        act_cust_edit.inc
        act_order_edit.inc
_library:
        lib_cust_edit.inc
        lib_cust_list.inc
        lib_order_edit.inc
        lib_order_list.inc
_content:
        cnt_cust_edit.inc
        cnt_cust_list.inc
        cnt_order_edit.inc
        cnt_order_list.inc


I realize now that it can be a bit unpractical to quickly find the related files as a project grows, and different people might need to work on different parts independently.

Maybe the files need to be organized more like this, separated into different folders based on the first level of navigation instead of the type of file:

index.lasso
cust:
        cfg_cust_edit.inc
        cfg_cust_list.inc
        act_cust_edit.inc
        lib_cust_edit.inc
        lib_cust_list.inc
        cnt_cust_edit.inc
        cnt_cust_list.inc
order:
        cfg_order_edit.inc
        cfg_order_list.inc
        act_order_edit.inc
        lib_order_edit.inc
        lib_order_list.inc
        cnt_order_edit.inc
        cnt_order_list.inc

This would also better support a more modularized thinking, where you could more easily reuse for example an entire customer management "module" in another project.

What do you think?


--
     Johan Sölve    [FSA Member, Lasso Partner]
     Web Application/Lasso/FileMaker Developer
     MONTANIA SOFTWARE & SOLUTIONS
http://www.montania.se   mailto:[hidden email]
 (spam-safe email address, replace '-' with 'a')

#############################################################
This message is sent to you because you are subscribed to
the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
List archive http://lists.montania.se/Lists/knop/
(log in with your email and ConfirmationID as password, send message to
<[hidden email]> to get that ID)
Project homepage http://montania.se/projects/knop/
AIM chatroom knop aim:gochat?roomname=knop

Reply | Threaded
Open this post in threaded view
|

Re: Folder structure change?

Jolle Carlestam-2
I'm all for a modular setup. As easy as possible for moving and  
isolating modules.

HDB
Jolle

8 mar 2007 kl. 12.33 skrev Johan Solve:

> In the current suggested folder structure and how mt_nav behaves  
> for includes and stuff, each type of file (config, action, library  
> and content) are grouped into folders for each type of file.
> Example:
> index.lasso
> _config:
> cfg_cust_edit.inc
> cfg_cust_list.inc
> cfg_order_edit.inc
> cfg_order_list.inc
> _action:
> act_cust_edit.inc
> act_order_edit.inc
> _library:
> lib_cust_edit.inc
> lib_cust_list.inc
> lib_order_edit.inc
> lib_order_list.inc
> _content:
> cnt_cust_edit.inc
> cnt_cust_list.inc
> cnt_order_edit.inc
> cnt_order_list.inc
>
>
> I realize now that it can be a bit unpractical to quickly find the  
> related files as a project grows, and different people might need  
> to work on different parts independently.
>
> Maybe the files need to be organized more like this, separated into  
> different folders based on the first level of navigation instead of  
> the type of file:
>
> index.lasso
> cust:
> cfg_cust_edit.inc
> cfg_cust_list.inc
> act_cust_edit.inc
> lib_cust_edit.inc
> lib_cust_list.inc
> cnt_cust_edit.inc
> cnt_cust_list.inc
> order:
> cfg_order_edit.inc
> cfg_order_list.inc
> act_order_edit.inc
> lib_order_edit.inc
> lib_order_list.inc
> cnt_order_edit.inc
> cnt_order_list.inc
>
> This would also better support a more modularized thinking, where  
> you could more easily reuse for example an entire customer  
> management "module" in another project.
>
> What do you think?
>
>
> --
>      Johan Sölve    [FSA Member, Lasso Partner]
>      Web Application/Lasso/FileMaker Developer
>      MONTANIA SOFTWARE & SOLUTIONS
> http://www.montania.se   mailto:[hidden email]
>  (spam-safe email address, replace '-' with 'a')
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list <[hidden email]>.
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
> List archive http://lists.montania.se/Lists/knop/
> (log in with your email and ConfirmationID as password, send  
> message to
> <[hidden email]> to get that ID)
> Project homepage http://montania.se/projects/knop/
> AIM chatroom knop aim:gochat?roomname=knop


#############################################################
This message is sent to you because you are subscribed to
the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
List archive http://lists.montania.se/Lists/knop/
(log in with your email and ConfirmationID as password, send message to
<[hidden email]> to get that ID)
Project homepage http://montania.se/projects/knop/
AIM chatroom knop aim:gochat?roomname=knop


Reply | Threaded
Open this post in threaded view
|

Re: Folder structure change?

Johan Solve-2
In reply to this post by Johan Solve-2
I think I will make nav look first in folders by type (_config etc), then by first nav level (module if you want). That way the change will be transparent.


At 16.12 +0100 2007-03-08, [hidden email] wrote:

>I'm all for a modular setup. As easy as possible for moving and isolating modules.
>
>HDB
>Jolle
>
>8 mar 2007 kl. 12.33 skrev Johan Solve:
>
>>In the current suggested folder structure and how mt_nav behaves for includes and stuff, each type of file (config, action, library and content) are grouped into folders for each type of file.
>>Example:
>>index.lasso
>>_config:
>> cfg_cust_edit.inc
>> cfg_cust_list.inc
>> cfg_order_edit.inc
>> cfg_order_list.inc
>>_action:
>> act_cust_edit.inc
>> act_order_edit.inc
>>_library:
>> lib_cust_edit.inc
>> lib_cust_list.inc
>> lib_order_edit.inc
>> lib_order_list.inc
>>_content:
>> cnt_cust_edit.inc
>> cnt_cust_list.inc
>> cnt_order_edit.inc
>> cnt_order_list.inc
>>
>>
>>I realize now that it can be a bit unpractical to quickly find the related files as a project grows, and different people might need to work on different parts independently.
>>
>>Maybe the files need to be organized more like this, separated into different folders based on the first level of navigation instead of the type of file:
>>
>>index.lasso
>>cust:
>> cfg_cust_edit.inc
>> cfg_cust_list.inc
>> act_cust_edit.inc
>> lib_cust_edit.inc
>> lib_cust_list.inc
>> cnt_cust_edit.inc
>> cnt_cust_list.inc
>>order:
>> cfg_order_edit.inc
>> cfg_order_list.inc
>> act_order_edit.inc
>> lib_order_edit.inc
>> lib_order_list.inc
>> cnt_order_edit.inc
>> cnt_order_list.inc
>>
>>This would also better support a more modularized thinking, where you could more easily reuse for example an entire customer management "module" in another project.
>>
>>What do you think?
>>
>>
>>--
>>     Johan Sölve    [FSA Member, Lasso Partner]
>>     Web Application/Lasso/FileMaker Developer
>>     MONTANIA SOFTWARE & SOLUTIONS
>>http://www.montania.se   mailto:[hidden email]
>> (spam-safe email address, replace '-' with 'a')
>>
>>#############################################################
>>This message is sent to you because you are subscribed to
>>the mailing list <[hidden email]>.
>>To unsubscribe, E-mail to: <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>>List archive http://lists.montania.se/Lists/knop/
>>(log in with your email and ConfirmationID as password, send message to
>><[hidden email]> to get that ID)
>>Project homepage http://montania.se/projects/knop/
>>AIM chatroom knop aim:gochat?roomname=knop
>
>
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list <[hidden email]>.
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>
>List archive http://lists.montania.se/Lists/knop/
>(log in with your email and ConfirmationID as password, send message to
><[hidden email]> to get that ID)
>Project homepage http://montania.se/projects/knop/
>AIM chatroom knop aim:gochat?roomname=knop


--
     Johan Sölve    [FSA Member, Lasso Partner]
     Web Application/Lasso/FileMaker Developer
     MONTANIA SOFTWARE & SOLUTIONS
http://www.montania.se   mailto:[hidden email]
 (spam-safe email address, replace '-' with 'a')

#############################################################
This message is sent to you because you are subscribed to
the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
List archive http://lists.montania.se/Lists/knop/
(log in with your email and ConfirmationID as password, send message to
<[hidden email]> to get that ID)
Project homepage http://montania.se/projects/knop/
AIM chatroom knop aim:gochat?roomname=knop

Reply | Threaded
Open this post in threaded view
|

Re: Folder structure change?

stevepiercy
In reply to this post by Johan Solve-2
Modularization good.  Easier to search a single folder too.

--steve


On Thursday, March 8, 2007, [hidden email] (Johan Solve) pronounced:

>In the current suggested folder structure and how mt_nav behaves for includes and stuff,
>each type of file (config, action, library and content) are grouped into folders for
>each type of file.
>Example:
>index.lasso
>_config:
>   cfg_cust_edit.inc
>   cfg_cust_list.inc
>   cfg_order_edit.inc
>   cfg_order_list.inc
>_action:
>   act_cust_edit.inc
>   act_order_edit.inc
>_library:
>   lib_cust_edit.inc
>   lib_cust_list.inc
>   lib_order_edit.inc
>   lib_order_list.inc
>_content:
>   cnt_cust_edit.inc
>   cnt_cust_list.inc
>   cnt_order_edit.inc
>   cnt_order_list.inc
>
>
>I realize now that it can be a bit unpractical to quickly find the related files as a
>project grows, and different people might need to work on different parts independently.
>
>Maybe the files need to be organized more like this, separated into different folders
>based on the first level of navigation instead of the type of file:
>
>index.lasso
>cust:
>   cfg_cust_edit.inc
>   cfg_cust_list.inc
>   act_cust_edit.inc
>   lib_cust_edit.inc
>   lib_cust_list.inc
>   cnt_cust_edit.inc
>   cnt_cust_list.inc
>order:
>   cfg_order_edit.inc
>   cfg_order_list.inc
>   act_order_edit.inc
>   lib_order_edit.inc
>   lib_order_list.inc
>   cnt_order_edit.inc
>   cnt_order_list.inc
>
>This would also better support a more modularized thinking, where you could more easily
>reuse for example an entire customer management "module" in another project.
>
>What do you think?
>
>
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Steve Piercy               Web Site Builder               Soquel, CA
<[hidden email]>                   <http://www.StevePiercy.com>

#############################################################
This message is sent to you because you are subscribed to
the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
List archive http://lists.montania.se/Lists/knop/
(log in with your email and ConfirmationID as password, send message to
<[hidden email]> to get that ID)
Project homepage http://montania.se/projects/knop/
AIM chatroom knop aim:gochat?roomname=knop

Reply | Threaded
Open this post in threaded view
|

Re: Folder structure change?

Jolle Carlestam-2
In reply to this post by Johan Solve-2
I have used a solution that kind of what jono showed at the Summit.  
But without the atbegin handling etc.

It's simply a folder at root level that contain all files for logic,  
processing, display etc. Translated to Knop I would call that folder  
_knop. This folder is actually a symbolic link pointing to the real  
folder located elsewhere. Thus I can keep the common code for all  
sites on one place. In _knop is a folder for every module I handle on  
that site. And in the module folders I keep all "_knop" files.

Then I have a local folders in each site that reflects what modules  
that site utilises. In them there's usually only one file pointing to  
the module folder within _knop. But if the site need some special  
localisation then the folder contains a mirror of the _knop folder  
structure with localised files. I have no magic like Jonos to first  
look local and if not present go global. Instead it's all handled by  
the module settings document.

I suggest the following structure:

/
index.lasso // only routes to respective module
_knop/ // Could be a symbolic link to a server wide folder
        _site // serverwide settings and configurations
        _config // root level handling
        _action // -"-
        _library // -"-
        _content // -"-

        _customer // Module for customer handling
                _config // module level handling
                _action // -"-
                _library // -"-
                _content // -"-

        _shop // Module for online store handling
                _config // module level handling
                _action // -"-
                _library // -"-
                _content // -"-

        _news // Module for news handling
                _config // module level handling
                _action // -"-
                _library // -"-
                _content // -"-

/.../
_local // Specific for this site. Only contains files if there's a  
need for site specific behavior
        _site // sitewide settings and configurations
        _config // root level handling
        _action // -"-
        _library // -"-
        _content // -"-

        _shop // Localised module for online store handling. Overrides the  
global module
                _config // local module level handling
                _action // -"-
                _library // -"-
                _content // -"-
/.../

Knop first look to see if there's a local module to handle the  
request. If not it looks in _knop if there's a module. If not it's a  
file not found error.

One ambition with this setup is to be able to create and handle  
modules that are self contained as much as possible and to be able to  
handle common code in a way similar to what Jono described.


How does that sound to you?

HDB
Jolle

8 mar 2007 kl. 16.19 skrev Johan Solve:

> I think I will make nav look first in folders by type (_config  
> etc), then by first nav level (module if you want). That way the  
> change will be transparent.
>
>
> At 16.12 +0100 2007-03-08, [hidden email] wrote:
>> I'm all for a modular setup. As easy as possible for moving and  
>> isolating modules.
>>
>> HDB
>> Jolle
>>
>> 8 mar 2007 kl. 12.33 skrev Johan Solve:
>>
>>> In the current suggested folder structure and how mt_nav behaves  
>>> for includes and stuff, each type of file (config, action,  
>>> library and content) are grouped into folders for each type of file.
>>> Example:
>>> index.lasso
>>> _config:
>>> cfg_cust_edit.inc
>>> cfg_cust_list.inc
>>> cfg_order_edit.inc
>>> cfg_order_list.inc
>>> _action:
>>> act_cust_edit.inc
>>> act_order_edit.inc
>>> _library:
>>> lib_cust_edit.inc
>>> lib_cust_list.inc
>>> lib_order_edit.inc
>>> lib_order_list.inc
>>> _content:
>>> cnt_cust_edit.inc
>>> cnt_cust_list.inc
>>> cnt_order_edit.inc
>>> cnt_order_list.inc
>>>
>>>
>>> I realize now that it can be a bit unpractical to quickly find  
>>> the related files as a project grows, and different people might  
>>> need to work on different parts independently.
>>>
>>> Maybe the files need to be organized more like this, separated  
>>> into different folders based on the first level of navigation  
>>> instead of the type of file:
>>>
>>> index.lasso
>>> cust:
>>> cfg_cust_edit.inc
>>> cfg_cust_list.inc
>>> act_cust_edit.inc
>>> lib_cust_edit.inc
>>> lib_cust_list.inc
>>> cnt_cust_edit.inc
>>> cnt_cust_list.inc
>>> order:
>>> cfg_order_edit.inc
>>> cfg_order_list.inc
>>> act_order_edit.inc
>>> lib_order_edit.inc
>>> lib_order_list.inc
>>> cnt_order_edit.inc
>>> cnt_order_list.inc
>>>
>>> This would also better support a more modularized thinking, where  
>>> you could more easily reuse for example an entire customer  
>>> management "module" in another project.
>>>
>>> What do you think?
>>>
>>>
>>> --
>>>     Johan Sölve    [FSA Member, Lasso Partner]
>>>     Web Application/Lasso/FileMaker Developer
>>>     MONTANIA SOFTWARE & SOLUTIONS
>>> http://www.montania.se   mailto:[hidden email]
>>> (spam-safe email address, replace '-' with 'a')
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list <[hidden email]>.
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>> List archive http://lists.montania.se/Lists/knop/
>>> (log in with your email and ConfirmationID as password, send  
>>> message to
>>> <[hidden email]> to get that ID)
>>> Project homepage http://montania.se/projects/knop/
>>> AIM chatroom knop aim:gochat?roomname=knop
>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list <[hidden email]>.
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>> List archive http://lists.montania.se/Lists/knop/
>> (log in with your email and ConfirmationID as password, send  
>> message to
>> <[hidden email]> to get that ID)
>> Project homepage http://montania.se/projects/knop/
>> AIM chatroom knop aim:gochat?roomname=knop
>
>
> --
>      Johan Sölve    [FSA Member, Lasso Partner]
>      Web Application/Lasso/FileMaker Developer
>      MONTANIA SOFTWARE & SOLUTIONS
> http://www.montania.se   mailto:[hidden email]
>  (spam-safe email address, replace '-' with 'a')
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list <[hidden email]>.
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
> List archive http://lists.montania.se/Lists/knop/
> (log in with your email and ConfirmationID as password, send  
> message to
> <[hidden email]> to get that ID)
> Project homepage http://montania.se/projects/knop/
> AIM chatroom knop aim:gochat?roomname=knop


#############################################################
This message is sent to you because you are subscribed to
the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
List archive http://lists.montania.se/Lists/knop/
(log in with your email and ConfirmationID as password, send message to
<[hidden email]> to get that ID)
Project homepage http://montania.se/projects/knop/
AIM chatroom knop aim:gochat?roomname=knop


Reply | Threaded
Open this post in threaded view
|

Re: Folder structure change?

Johan Solve-2
In reply to this post by Johan Solve-2
Something like what you describe seems reasonable.

Maybe the nav object could take a -module name, which would  correspond to a folder name where the files for that module is stored. If not specifying -module in nav, the current folder structure would be used instead.

The looking upwards in hierarchy is very similar to my [include_global] that we developed and intended to use a few years ago but never actually found a good use for in reality. Well, not yet anyway.
Hmm, I already mentioned that didn't I...?


At 18.27 +0100 2007-03-08, [hidden email] wrote:

>I have used a solution that kind of what jono showed at the Summit. But without the atbegin handling etc.
>
>It's simply a folder at root level that contain all files for logic, processing, display etc. Translated to Knop I would call that folder _knop. This folder is actually a symbolic link pointing to the real folder located elsewhere. Thus I can keep the common code for all sites on one place. In _knop is a folder for every module I handle on that site. And in the module folders I keep all "_knop" files.
>
>Then I have a local folders in each site that reflects what modules that site utilises. In them there's usually only one file pointing to the module folder within _knop. But if the site need some special localisation then the folder contains a mirror of the _knop folder structure with localised files. I have no magic like Jonos to first look local and if not present go global. Instead it's all handled by the module settings document.
>
>I suggest the following structure:
>
>/
>index.lasso // only routes to respective module
>_knop/ // Could be a symbolic link to a server wide folder
> _site // serverwide settings and configurations
> _config // root level handling
> _action // -"-
> _library // -"-
> _content // -"-
>
> _customer // Module for customer handling
> _config // module level handling
> _action // -"-
> _library // -"-
> _content // -"-
>
> _shop // Module for online store handling
> _config // module level handling
> _action // -"-
> _library // -"-
> _content // -"-
>
> _news // Module for news handling
> _config // module level handling
> _action // -"-
> _library // -"-
> _content // -"-
>
>/.../
>_local // Specific for this site. Only contains files if there's a need for site specific behavior
> _site // sitewide settings and configurations
> _config // root level handling
> _action // -"-
> _library // -"-
> _content // -"-
>
> _shop // Localised module for online store handling. Overrides the global module
> _config // local module level handling
> _action // -"-
> _library // -"-
> _content // -"-
>/.../
>
>Knop first look to see if there's a local module to handle the request. If not it looks in _knop if there's a module. If not it's a file not found error.
>
>One ambition with this setup is to be able to create and handle modules that are self contained as much as possible and to be able to handle common code in a way similar to what Jono described.
>
>
>How does that sound to you?
>
>HDB
>Jolle
>
>8 mar 2007 kl. 16.19 skrev Johan Solve:
>
>>I think I will make nav look first in folders by type (_config etc), then by first nav level (module if you want). That way the change will be transparent.
>>
>>
>>At 16.12 +0100 2007-03-08, [hidden email] wrote:
>>>I'm all for a modular setup. As easy as possible for moving and isolating modules.
>>>
>>>HDB
>>>Jolle
>>>
>>>8 mar 2007 kl. 12.33 skrev Johan Solve:
>>>
>>>>In the current suggested folder structure and how mt_nav behaves for includes and stuff, each type of file (config, action, library and content) are grouped into folders for each type of file.
>>>>Example:
>>>>index.lasso
>>>>_config:
>>>> cfg_cust_edit.inc
>>>> cfg_cust_list.inc
>>>> cfg_order_edit.inc
>>>> cfg_order_list.inc
>>>>_action:
>>>> act_cust_edit.inc
>>>> act_order_edit.inc
>>>>_library:
>>>> lib_cust_edit.inc
>>>> lib_cust_list.inc
>>>> lib_order_edit.inc
>>>> lib_order_list.inc
>>>>_content:
>>>> cnt_cust_edit.inc
>>>> cnt_cust_list.inc
>>>> cnt_order_edit.inc
>>>> cnt_order_list.inc
>>>>
>>>>
>>>>I realize now that it can be a bit unpractical to quickly find the related files as a project grows, and different people might need to work on different parts independently.
>>>>
>>>>Maybe the files need to be organized more like this, separated into different folders based on the first level of navigation instead of the type of file:
>>>>
>>>>index.lasso
>>>>cust:
>>>> cfg_cust_edit.inc
>>>> cfg_cust_list.inc
>>>> act_cust_edit.inc
>>>> lib_cust_edit.inc
>>>> lib_cust_list.inc
>>>> cnt_cust_edit.inc
>>>> cnt_cust_list.inc
>>>>order:
>>>> cfg_order_edit.inc
>>>> cfg_order_list.inc
>>>> act_order_edit.inc
>>>> lib_order_edit.inc
>>>> lib_order_list.inc
>>>> cnt_order_edit.inc
>>>> cnt_order_list.inc
>>>>
>>>>This would also better support a more modularized thinking, where you could more easily reuse for example an entire customer management "module" in another project.
>>>>
>>>>What do you think?
>>>>
>>>>
>>>>--
>>>>    Johan Sölve    [FSA Member, Lasso Partner]
>>>>    Web Application/Lasso/FileMaker Developer
>>>>    MONTANIA SOFTWARE & SOLUTIONS
>>>>http://www.montania.se   mailto:[hidden email]
>>>>(spam-safe email address, replace '-' with 'a')
>>>>
>>>>#############################################################
>>>>This message is sent to you because you are subscribed to
>>>>the mailing list <[hidden email]>.
>>>>To unsubscribe, E-mail to: <[hidden email]>
>>>>Send administrative queries to  <[hidden email]>
>>>>List archive http://lists.montania.se/Lists/knop/
>>>>(log in with your email and ConfirmationID as password, send message to
>>>><[hidden email]> to get that ID)
>>>>Project homepage http://montania.se/projects/knop/
>>>>AIM chatroom knop aim:gochat?roomname=knop
>>>
>>>
>>>#############################################################
>>>This message is sent to you because you are subscribed to
>>>the mailing list <[hidden email]>.
>>>To unsubscribe, E-mail to: <[hidden email]>
>>>Send administrative queries to  <[hidden email]>
>>>List archive http://lists.montania.se/Lists/knop/
>>>(log in with your email and ConfirmationID as password, send message to
>>><[hidden email]> to get that ID)
>>>Project homepage http://montania.se/projects/knop/
>>>AIM chatroom knop aim:gochat?roomname=knop
>>
>>
>>--
>>     Johan Sölve    [FSA Member, Lasso Partner]
>>     Web Application/Lasso/FileMaker Developer
>>     MONTANIA SOFTWARE & SOLUTIONS
>>http://www.montania.se   mailto:[hidden email]
>> (spam-safe email address, replace '-' with 'a')
>>
>>#############################################################
>>This message is sent to you because you are subscribed to
>>the mailing list <[hidden email]>.
>>To unsubscribe, E-mail to: <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>>List archive http://lists.montania.se/Lists/knop/
>>(log in with your email and ConfirmationID as password, send message to
>><[hidden email]> to get that ID)
>>Project homepage http://montania.se/projects/knop/
>>AIM chatroom knop aim:gochat?roomname=knop
>
>
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list <[hidden email]>.
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>
>List archive http://lists.montania.se/Lists/knop/
>(log in with your email and ConfirmationID as password, send message to
><[hidden email]> to get that ID)
>Project homepage http://montania.se/projects/knop/
>AIM chatroom knop aim:gochat?roomname=knop


--
     Johan Sölve    [FSA Member, Lasso Partner]
     Web Application/Lasso/FileMaker Developer
     MONTANIA SOFTWARE & SOLUTIONS
http://www.montania.se   mailto:[hidden email]
 (spam-safe email address, replace '-' with 'a')

#############################################################
This message is sent to you because you are subscribed to
the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
List archive http://lists.montania.se/Lists/knop/
(log in with your email and ConfirmationID as password, send message to
<[hidden email]> to get that ID)
Project homepage http://montania.se/projects/knop/
AIM chatroom knop aim:gochat?roomname=knop

Reply | Threaded
Open this post in threaded view
|

Re: Folder structure change?

Bil Corry-3
In reply to this post by Johan Solve-2
Johan Solve wrote on 3/8/2007 1:44 PM:
> The looking upwards in hierarchy is very similar to my [include_global] that we developed

I use [lp_file_findPath] to search up for a file:

  <http://www.tagswap.net/lp_file_findPath>

This allows you to include a config file that is stored in the web root, then override it by providing a different version farther down in the directory tree.

I also use it to determine where my applications root is by searching where the "_system" directory is located (always at root level in my framework), rather than it being a hardcoded value somewhere.

- Bil



#############################################################
This message is sent to you because you are subscribed to
the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
List archive http://lists.montania.se/Lists/knop/
(log in with your email and ConfirmationID as password, send message to
<[hidden email]> to get that ID)
Project homepage http://montania.se/projects/knop/
AIM chatroom knop aim:gochat?roomname=knop