On 02/20/2012 01:25 PM, Darrell Anderson wrote:
> How will these packages be handled? Just another package in applications? A special web page at the Trinity web site?
> 
> I ask because there a few places in the handbook help files specifically referencing the kde-look.org web site. I want to know how to revise those snippets.
> 
> Darrell
> 

  Themes/color schemes/etc.. are generally small and don't require too much
bandwidth. I prefer collecting the various themes into a separate package or two
rather than trying to maintain a download site referenced by the handbook.
Perhaps another module named 'tdelook' could be added to the git repository.
That way the handbook could reference the base tde packages to install rather
than a site to visit (even simple pages become difficult to remember to maintain
over time by any project) I would vote for something in git like:

main/tdelook
main/tdelook/color-schemes
main/tdelook/theme-nameOfTheme1
main/tdelook/theme-nameOfTheme2
main/tdelook/theme-nameOfTheme3

  I would combine all contributed color themes because the size in negligible (a
few hundred bytes to a few K each) -- even for 100 color schemes. The 'themes'
should be packaged individually due to each containing a possible background and
various icons that can be .2-5 Meg each.

  A web page or web app similar to kde-look would work, but it then becomes a
separate maintenance issue for lucky person.

  Those are just my thoughts on it. As mentioned - either way will work, I just
see advantages to packaging them like we do with window styles and window
decorations.

-- 
David C. Rankin, J.D.,P.E.