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
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.
On 20 February 2012 14:51, David C. Rankin drankinatty@suddenlinkmail.com wrote:
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.
tdeartwork guys... that's where it belongs.
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.
tdeartwork guys... that's where it belongs.
Pushing any of them to tdeartwork makes sense to me :). However, my focus is knowing how to revise the various references. I can delete those sentences and that might be the easiest approach as long as the imported kde-look.org themes are available to users in an obvious manner. If they are all a part of tdeartwork then the new themes will appear in KControl.
This now raises another point --- probably a bug report needed to resolve. In KControl, Appearance, Theme Manager, top right corner is a link to...
kde-look.org :)
As these theme discussions started because many of the themes no longer are compatible with Trinity, we probably should remove that link in KControl. We could provide a page at our web site and change the KControl link to that URL, but I suspect we'll only migrate a handful of these themes, which I then suspect get absorbed somewhere in the GIT tree, which then appear directly in KControl.
Darrell
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
A new subdirectory of main, probably "themes" or "addons". A couple of existing themes would need to be moved from "applications" (where they don't belong) as well.
Tim
On 20 February 2012 15:00, Timothy Pearson kb9vqf@pearsoncomputing.net 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
A new subdirectory of main, probably "themes" or "addons". A couple of existing themes would need to be moved from "applications" (where they don't belong) as well.
Tim
Wait I am so confused. Why isn't tdeartwork the right place? from the README in main/tdeartwork:
This package contains additional
* themes, * screensaver, * sounds, * wallpapers, * widget styles and * window styles
Calvin
-
Calvin Morrison -
Darrell Anderson -
David C. Rankin -
Timothy Pearson