at them, including jquery.autocomplete.css so that we don't have stuff
from lib that points into a theme directory. They were common images
anyway. Incidentally, rename sm/lg to small/large.
theme. Because the theme comes first, this means that themes can
override any module resources, at the cost that we no longer have
namespacing for JS and CSS files.
The only file getting used outside of this model is
themes/default/screen.css which is used in the admin theme. I fixed
that by copying screen.css into admin_default and renaming its
screen.css to admin_screen.css. I also copied over all the images
that it was referencing.
Fixes tickets #48 and #539.
Theme API changes:
- theme_script(), theme_url() and theme_css() are no longer needed
- script(), url() and css() now refer to the first matching asset in
the module load path, where gallery3/lib is at the end of the path
stored in the persistant cache for 30 days. On the admin_maintenance page
there is a new link for completed tasks "browse log". Clicking this will
open a dialog box that has the the contents of the log displayed.
The user can then view the log and close the dialog, or press the save button
to download the log to their local machine.
1) Simplify the admin settings page to what most of our users
want. Eliminate basic_ and default_ ids. We just have company_id
and default_id. Advanced users can use advanced settings for now.
2) Fix security in print_photos (didn't get it right in my last commit)
3) Use the regular thumb and full urls if the images are publicly
available to reduce load on the proxy.
4) Simplify proxy expiration code.
5) Eliminate all specialized styles from the admin theme.
2) Removed the tabs on the digibug admin page word count is now at 35.
3) Added a default link which resets the event and company id's to gallery's ids
2) Remove most of the marketing cruft on the admin pages
3) Change the name of the admin settings to just Digibug
4) Remove the "switch on mouseover" approach
enter a module name, a description and pick the call backs and or
events they want to support and generate the basic module skeleton
with one click.
@todo: clone a module, clone a theme, generate skeleton controller,
view,
Surround the the attempt to use gd_info with a try catch block.
Created a new class gInstalledToolkit which has the highlighting and
the over pointer definition. Now if you mouse across an inactive
toolkit it remains inert.
