On 1/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Well as any good programmer you learn new ways of doing things and
> more efficient ways of completing a task every day (or week :P). Since
> my original work in making pfSense themeable I have found a couple of
> ways to "improve" upon this.
>
> My first and only idea that I am going to share at this point with you
> is basically the concept Firefox uses with extension development. See
> Figure 1 for an example of the heirachical (sp?) structure.
>
> Basically I am thinking of making the themeing system use an xml file
> to contain the "elements" of the theme and just have the webgui read
> the xml file to find out what CSS files need to be included,
> javascript, etc ... overall or per page.
>
> ++++++++++++++++++
> + Figure 1.1     +
> +----------------+
> + /themes        +
> +  /metallic     +
> +   /css         +
> +   /images      +
> +   /javascript  +
> +   metallic.xml +
> ++++++++++++++++++
>
> Comments? :) (I know GeekGod will have plenty, as this is the first
> time he is seeing this idea :P)

For 1.1 the XML approach is a great idea.

However for 1.0 we may want to somehow fix the misc small issues so
that others can create themes.  Can we get a list of outstanding items
that need fixing in the themes section as a ticket in cvstrack?

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to