Bug 919 - Custom Widgets Directory
: Custom Widgets Directory
Status: RESOLVED INVALID
: Chameleon
Core
: 2.0
: All All
: P2 normal
: ---
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-01-07 14:11 by
Modified: 2005-01-10 12:26 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-01-07 14:11:59
It would be nice to have the option of setting a custom widgets directory that
exists outside of Chameleon, so users developing custom widgets don't have to
muck around in the standard widgets dir.  This would also make upgrading to new
versions of Chameleon easier
------- Comment #1 From 2005-01-07 14:13:47 -------
It would also be nice if I didn't instinctively preface these feature requests
with "It would be nice."  Jeez.
------- Comment #2 From 2005-01-10 11:05:00 -------
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.  :-)

------- Comment #3 From 2005-01-10 12:26:19 -------
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' ) );