[dev] potential optimizations: static css and javascript
Marko Djukic
mdjukic at horde.org
Mon Oct 18 02:02:49 PDT 2004
Quoting Jan Schneider <jan at horde.org>:
> Zitat von Chuck Hagenbuch <chuck at horde.org>:
>
> > Quoting Jan Schneider <jan at horde.org>:
> >
> >> Ah, understood. But this is not necessary, see above. There already is a
> >> parameter to addScriptFile that defines the path to be an absolute path to
> >> a static js file. No file extension magic.
> >
> > Ah, right. Before I go ahead with this, do you think there's any reason
> > for the
> > .js files to live in the theme/ dir? Say, so a theme can have a different
> > version of the date picker? Or should they go in a new /js dir? Another
> > advantage is that keeping them in theme/ would put all the static
> > files in one
> > place. We could have a flag similar to $theme_icons ($theme_js) to
> > say whether
> > or not to look in theme/themename or theme/horde for .js files.
>
> To be honest, I can't really see a reason to have themeable js files for
> something that can't be achieved by CSS. I'd like to keep them separate
> from the themes directory.
i agree. at least for now too, lets see how the graphics to themes/ migration
settles down. plus not sure how much there is js to theme to be worth the
effort?
--
Marko Djukic
Horde Project (http://horde.org)
More information about the dev
mailing list