Summary: | Custom Widgets Directory | ||
---|---|---|---|
Product: | Chameleon | Reporter: | Ken-ichi <kueda@wso.williams.edu> |
Component: | Core | Assignee: | chameleon-dev <chameleon-dev@lists.maptools.org> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
It would also be nice if I didn't instinctively preface these feature requests with "It would be nice." Jeez.
I'd like to second that request! Sounds like a fine idea. If a configuration line could be added in the Chameleon Config for this option (when designed) that would be great too, so that it doesn't need to reside in the chameleon tree. The reasoning for this, is that it would make upgrading easier keeping all the chameleon standard components together, and then the custom stuff separate. Skins could also go here. :-)
this exists on a 'per-application' basis already by passing an array of extra directories to the execute function, i.e: $oApp->CWCExecute( array( '/path/to/my/widgets/' ) ); where the path can be either absolute or relative to the directory of the 'index.phtml' file. Skins can be in any directory too, using: $oApp->registerSkin( 'path/to/skin' ); Again, skins are either absolute or relative to the local directory. If you have both widgets and skins in an application myApp/htdocs/widgets myApp/htdocs/skins/myskin $oApp->registerSkin( 'skins/myskin' ); $oApp->CWCExecute( array( 'widgets' ) );