[Chameleon-dev] code reorg and skinning support

Christopher R. Thorne cthorne at dmsolutions.ca
Mon Apr 26 09:25:23 EDT 2004


I am not sure having the files placed just /htdocs/ is the best. If 
these files are specific to the chameleon core, than maybe they should 
go into a separate directory? eg. /htdocs/core, ccore/ or /htdocs/resource/

If these files found in /htdocs/ are specific files shared between 
widgets and not the core directly then, maybe a hierarchy would be best? 
Like what Zak suggested.

Chris

Zak James wrote:

> Paul,
>
> I was really considering it from the point of view of a developer 
> unfamiliar with chameleon who is trying to create new widgets. From 
> that perspective, I think that having those files loose in the widgets 
> directory, alongside directories for individual widgets, is confusing. 
> Maybe there is a need for a (gulp!) common directory within the 
> widgets directory. Either that, or perhaps more hierarchy for widgets 
> that extend other widgets.
>
> zak
>
> On Apr 23, 2004, at 7:38 AM, Paul Spencer wrote:
>
>> Zak,
>>
>> would you suggest that these files be located directly in htdocs 
>> rather than in the widgets directory?  I am tempted to agree since 
>> there are already files in the htdocs directory that support the 
>> chameleon core. I believe that it was a somewhat arbitrary decision 
>> initially to put these files in with the widgets (i.e. it made sense 
>> in a flat directory structure, not from an architectural point of view).
>>
>> The other side of the argument is that the files in the htdocs 
>> directory are purely there for the chameleon core engine and 
>> everything in the widgets directory is specific or common to 
>> widgets.  I still like this separation now that I think about it.
>>
>> Comments and suggestions welcome on this.  It will take me a couple 
>> of days to make the other changes so we some time to make a decision 
>> on this one.
>>
>> Paul
>>
>> Zak James wrote:
>>
>>> Paul,
>>> I think some of these files (and maybe some of the associated js 
>>> files) don't belong in /widgets because they contain code used by 
>>> most widgets. Maybe they should be in the parent htdocs directory or 
>>> some other separate location.
>>> zak
>>> -- 
>>> Zak James
>>> Applications and Software Development
>>> DM Solutions Group Inc.
>>> http://www.dmsolutions.ca
>>> On Apr 22, 2004, at 11:26 PM, Paul Spencer wrote:
>>>
>>>> * figuring out what to do with common code shared between several 
>>>> widgets.  I expect to leave these in the widgets directory.  This 
>>>> will include:
>>>>
>>>>  - Widget.php
>>>>  - Button.php
>>>>  - common.dbf
>>>>  - CWC2ButtonCache.php
>>>>  - geomath.php
>>>>  - Label.php
>>>>  - NavTool.php
>>>>  - Popup.php
>>>>  - session.inc.php
>>>>  - utils.php
>>>
>>
>> -- 
>>  -----------------------------------------------------------------
>> |Paul Spencer                           pspencer at dmsolutions.ca   |
>> |-----------------------------------------------------------------|
>> |Applications & Software Development                              |
>> |DM Solutions Group Inc                 http://www.dmsolutions.ca/|
>>  -----------------------------------------------------------------
>>
>> _______________________________________________
>> Chameleon-dev mailing list
>> Chameleon-dev at lists.maptools.org
>> http://lists.maptools.org/mailman/listinfo/chameleon-dev
>>
>
> _______________________________________________
> Chameleon-dev mailing list
> Chameleon-dev at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/chameleon-dev
>


-- 
---------------------
Christopher R. Thorne
GIS Product Specialist,
DM Solutions Group Inc.

http://www.dmsolutions.ca
Email: cthorne at dmsolutions.ca
Phone: (613) 565-5056 ext.22
Fax :  (613) 565-0925 




More information about the Chameleon-dev mailing list