Hello all,
> - Copy configure.xml to the localsearches directory under
> your install dir
> - Open the copy in your favorite text editor
> - Search for "loadcssfile(\"classic\")" with or without
> quotes included
> - After this line, you'll want to add a new one, with the
following
> contents:
> mb.AppendMenuItem("Theme name",
"loadcssfile(\"mytheme.css\")",
> "Description", confthememenu);
> // Exchange mytheme.css for the actual css filename, of
course
This would be a PITA to share a new theme with the world. Users
(I'll never understand why) are very visual people.
I think we ought to have a separate folder for themes (./themes/)
and use xml files that function similar to the search files in their
function: sections for theme name, description, author, images
required, stylesheet reference (or inline!) and any other shtuff one
would need for their theme.
This is 'next-release' Shawn talking, so don't think I'm pushing too
hard for this right now.
How hard could it be to modify the search parsing code to function
similarly for themes? Theoretically, using CDATA blocks, we could
even distribute themes as a single XML file. :)
Regards,
Shawn K. Hall
http://12PointDesign.com/
http://ReliableAnswers.com/
'// ========================================================
"The life so short, the craft so long to learn."
-- Hippocrates
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
