What is the status of any art work projects?
I'm curious because many of the images in the wallpaper collection need branding attention.
Darrell
On 5 April 2012 12:03, Darrell Anderson humanreadable@yahoo.com wrote:
What is the status of any art work projects?
I'm curious because many of the images in the wallpaper collection need branding attention.
Anybody?
Darrell
What files need branding attention?
I can do basic - medium rebranding stuff :-)
Calvin
What is the status of any art work projects?
I'm curious because many of the images in the wallpaper collection need branding attention.
Anybody?
What files need branding attention?
I can do basic - medium rebranding stuff :-)
Many. Look through the wallpaper collection: tdebase/pics/wallpapers.
Darrell
On 5 April 2012 12:16, Darrell Anderson humanreadable@yahoo.com wrote:
What is the status of any art work projects?
I'm curious because many of the images in the wallpaper collection need branding attention.
Anybody?
What files need branding attention?
I can do basic - medium rebranding stuff :-)
Many. Look through the wallpaper collection: tdebase/pics/wallpapers.
Darrell
Ok!
Calvin
On 04/05/2012 11:03 AM, Darrell Anderson wrote:
What is the status of any art work projects?
I'm curious because many of the images in the wallpaper collection need branding attention.
Anybody?
Darrell
Darrell,
By my look the only 2 in tdeartwork/wallpapers that reference kde are
mystical_rightturn.jpg and kubical.png
Both would be utter pains to convert. kubical would be damn near impossible. I don't really think either are necessary. Why can't we just nuke them and add some really good wallpapers? I have bazillions to choose from....
What is the status of any art work projects?
I'm curious because many of the images in the wallpaper collection need branding attention.
Anybody?
By my look the only 2 in tdeartwork/wallpapers that reference kde are
mystical_rightturn.jpg and kubical.png
Both would be utter pains to convert. kubical would be damn near impossible. I don't really think either are necessary. Why can't we just nuke them and add some really good wallpapers? I have bazillions to choose from....
Here is a list of the wallpaper images I have installed from Trinity that have branding issues:
andes-venezolanos.svgz aurora.svgz celtic.svgz default_gears.jpg globe.svgz konqui.svgz kraftwurm.jpg moon.svgz mystical_rightturn.jpg
I vote that all svgz wallpaers get purged. Period. They require too much CPU and graphics horsepower to display. Nice for art shows but useless as wallpaper. celtic.svgz is the grand monster of all, requiring several seconds to load even on a dual core. In fact, while viewing celtic.svgz in my virtual machine, I could not toggle to my primary desktop without losing the desktop screen painting.
Darrell
On Fri, 6 Apr 2012 21:36:19 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
What is the status of any art work projects?
I'm curious because many of the images in the wallpaper collection need branding attention.
Anybody?
By my look the only 2 in tdeartwork/wallpapers that reference kde are
mystical_rightturn.jpg and kubical.png
Both would be utter pains to convert. kubical would be damn near impossible. I don't really think either are necessary. Why can't we just nuke them and add some really good wallpapers? I have bazillions to choose from....
Here is a list of the wallpaper images I have installed from Trinity that have branding issues:
andes-venezolanos.svgz aurora.svgz celtic.svgz default_gears.jpg globe.svgz konqui.svgz kraftwurm.jpg moon.svgz mystical_rightturn.jpg
I vote that all svgz wallpaers get purged. Period. They require too much CPU and graphics horsepower to display. Nice for art shows but useless as wallpaper. celtic.svgz is the grand monster of all, requiring several seconds to load even on a dual core. In fact, while viewing celtic.svgz in my virtual machine, I could not toggle to my primary desktop without losing the desktop screen painting.
The main advantage of the svgz wallpapers is that because they're in a vector format, they expand to fit large screens without loss of quality (when they work at all—bug 744). That's of limited value if they take too much CPU/GPU horsepower, though.
My suggestion would be to strip the branding (easier with these than with the jpg files—it took me longer to open Inkscape than to test-delete the KDE logo from aurora) and include a static PNG rendering of each svgz in the core wallpaper set. The svgz files themselves can go to Planet-Trinity, if such a thing ever comes into existence.
As for the other four images, default_gears, kraftwurm, and mystical_rightturn are probably fixable with a bit of effort. kubical might be as well (or at least I have a tentative idea of how it might be done), but I don't think it's worth it—more efficient to purge it.
Do you want me to take this on? If so, where do you want the finished files sent?
There is one other thing about the wallpapers, though: everything in the default set is sized for an old-style 4:3 monitor. Most people these days use 16:9 widescreens. We need some wallpapers that are designed for that aspect ratio. A few of the existing ones can probably be cropped to conform, but adding something new might be better.
My suggestion would be to strip the branding (easier with these than with the jpg files—it took me longer to open Inkscape than to test-delete the KDE logo from aurora) and include a static PNG rendering of each svgz in the core wallpaper set. The svgz files themselves can go to Planet-Trinity, if such a thing ever comes into existence.
As for the other four images, default_gears, kraftwurm, and mystical_rightturn are probably fixable with a bit of effort. kubical might be as well (or at least I have a tentative idea of how it might be done), but I don't think it's worth it—more efficient to purge it.
Do you want me to take this on? If so, where do you want the finished files sent?
There is one other thing about the wallpapers, though: everything in the default set is sized for an old-style 4:3 monitor. Most people these days use 16:9 widescreens. We need some wallpapers that are designed for that aspect ratio. A few of the existing ones can probably be cropped to conform, but adding something new might be better.
Yes, please move forward with this if you feel up to the task.
Send the completed images here to this list as attachments or save then somewhere in internet land where all of us have access.
An easy fix for branding issues is not to convert "KDE" to "TDE." Just delete the text, leaving only the image.
Regarding the 4:3 vs. 16:9 challenge, we could create two versions, one for each aspect ratio. I understand SVG lends well to solving that problem, but test them on a PIII. I'm not going to salvage anything that does not render immediately on older hardware, let alone my dual core. :) Wallpapers cannot bog down a system. I have no idea who would find celtic.svgz usable on any system as wallpaper.
Darrell
On Sat, 7 Apr 2012 12:29:44 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
My suggestion would be to strip the branding (easier with these than with the jpg files—it took me longer to open Inkscape than to test-delete the KDE logo from aurora) and include a static PNG rendering of each svgz in the core wallpaper set. The svgz files themselves can go to Planet-Trinity, if such a thing ever comes into existence.
As for the other four images, default_gears, kraftwurm, and mystical_rightturn are probably fixable with a bit of effort. kubical might be as well (or at least I have a tentative idea of how it might be done), but I don't think it's worth it—more efficient to purge it.
Do you want me to take this on? If so, where do you want the finished files sent?
There is one other thing about the wallpapers, though: everything in the default set is sized for an old-style 4:3 monitor. Most people these days use 16:9 widescreens. We need some wallpapers that are designed for that aspect ratio. A few of the existing ones can probably be cropped to conform, but adding something new might be better.
Yes, please move forward with this if you feel up to the task.
Okay, I'll take a shot at the first few tonight.
Send the completed images here to this list as attachments or save then somewhere in internet land where all of us have access.
An easy fix for branding issues is not to convert "KDE" to "TDE." Just delete the text, leaving only the image.
Logos I intend to delete, and any text in the svgzs that was saved as outlines. In the case of the jpegs, turning the K into a T is actually easier than scrubbing the text out, because the area that needs to be redrawn is smaller.
Regarding the 4:3 vs. 16:9 challenge, we could create two versions, one for each aspect ratio. I understand SVG lends well to solving that problem, but test them on a PIII. I'm not going to salvage anything that does not render immediately on older hardware, let alone my dual core. :) Wallpapers cannot bog down a system. I have no idea who would find celtic.svgz usable on any system as wallpaper.
I suspect my main system would be able to handle it (I upgraded it last year to a quad-core Phenom II), but I wouldn't try it on a PIII. Anyway, my hope is that I'll be able to render static PNGs from aurora and one or two others at 1600x900, which will be a start on providing widescreen wallpaper.
I suspect my main system would be able to handle it (I upgraded it last year to a quad-core Phenom II), but I wouldn't try it on a PIII. Anyway, my hope is that I'll be able to render static PNGs from aurora and one or two others at 1600x900, which will be a start on providing widescreen wallpaper.
I mentioned the PIII because I think that should be our lowest standard. That is, if a wallpaper image won't display quickly and snappily on a PIII then we don't include the image as wallpaper. We don't need poor PR reports from people who can't load any wallpapers we provide. People running dual and quad cores might or might not notice any lagging, but people running a PIII sure will. Because one of the reasons people provide for wanting to run classic desktop environments as opposed to newer desktops is to keep using older hardware, then we should keep that reason in mind.
As I mentioned, the celtic.svgz kills my dual core system. Granted, I'm using the on-board Nvidia graphics and not a stand alone video card, but wallpaper should not bring a system to its proverbial knees. :)
Darrell
On Sat, 7 Apr 2012 15:58:15 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
As I mentioned, the celtic.svgz kills my dual core system. Granted, I'm using the on-board Nvidia graphics and not a stand alone video card, but wallpaper should not bring a system to its proverbial knees. :)
I may have figured out what was causing the problem with celtic (or not, but those nigh-invisible dotted borders on the roundel looked awfully suspicious, so I replaced them with plain ones while I was messing with the lettering).
Anyway, the attachment contains re- or de-brands of all the original problem svgz files except moon, which is going to be a little more work because that K on the moon itself is done as negative space. In all cases, I've included both the original svgz (which should be stored somewhere even if it's not distributed from now on, in case we want to render a variant), and a 1600x1200 PNG image version which may require less horsepower to display than the vector version. I would suggest running a comparison test before deciding what to distribute.
All of these files appear to belong to tdebase (kdebase-data on my system) rather than to the artwork package.
I'll tackle moon and the three jpegs tomorrow, if I can.
I may have figured out what was causing the problem with celtic (or not, but those nigh-invisible dotted borders on the roundel looked awfully suspicious, so I replaced them with plain ones while I was messing with the lettering).
The revised version displays much faster. Good job!
Anyway, the attachment contains re- or de-brands of all the original problem svgz files except moon, which is going to be a little more work because that K on the moon itself is done as negative space. In all cases, I've included both the original svgz (which should be stored somewhere even if it's not distributed from now on, in case we want to render a variant), and a 1600x1200 PNG image version which may require less horsepower to display than the vector version. I would suggest running a comparison test before deciding what to distribute.
Not sure what happened or what I am doing wrong. When I view two of the revised svgz images, I see only blocks where the text used to be. I am using gwenview to view the images. The originals don't do this:
http://humanreadable.nfshost.com/trinity/build_logs/gwenview3.png
http://humanreadable.nfshost.com/trinity/build_logs/gwenview4.png
All of these files appear to belong to tdebase (kdebase-data on my system) rather than to the artwork package.
The other images I listed must be from other packages.
Darrell
On Sat, 7 Apr 2012 19:16:04 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
I may have figured out what was causing the problem with celtic (or not, but those nigh-invisible dotted borders on the roundel looked awfully suspicious, so I replaced them with plain ones while I was messing with the lettering).
The revised version displays much faster. Good job!
I don't even know why the original artist put those dotted borders in, since I couldn't tell them from solid ones until I went to 1000% magnification to do some fine work.
Anyway, the attachment contains re- or de-brands of all the original problem svgz files except moon, which is going to be a little more work because that K on the moon itself is done as negative space. In all cases, I've included both the original svgz (which should be stored somewhere even if it's not distributed from now on, in case we want to render a variant), and a 1600x1200 PNG image version which may require less horsepower to display than the vector version. I would suggest running a comparison test before deciding what to distribute.
Not sure what happened or what I am doing wrong. When I view two of the revised svgz images, I see only blocks where the text used to be. I am using gwenview to view the images. The originals don't do this:
I probably forgot to do a text-to-path conversion (in other words, it's my, or more accurately Inkscape's, fault). I'll include fixed versions of the svgzs in the next file pack. Apologies for the error.
Batch #2. Contains moon.svgz, revised versions of globe and andes-venezolanos that will hopefully not have text display problems (I assume those were the two that were bad before—I didn't actually bother to check), and the three jpgs (default_gears, kraftwurm, mystical_right_turn). The unfortunate gap in kraftworm's text is due to the surgical removal of a "3", which would take forever to fix properly without the original layered document (unless I were to plonk some other random symbol into the space).
kraftwurm and mystical_right_turn appear to belong to the artwork package; the others are from base.
<snip>
The unfortunate gap in kraftworm's text is due to the surgical removal of a "3", which would take forever to fix properly without the original layered document (unless I were to plonk some other random symbol into the space).
How about a couple/few faint lines, tastefully inserted so that they look like a purposeful graphical separator element?
Tim
Batch #2. Contains moon.svgz, revised versions of globe and andes-venezolanos that will hopefully not have text display problems (I assume those were the two that were bad before—I didn't actually bother to check), and the three jpgs (default_gears, kraftwurm, mystical_right_turn). The unfortunate gap in kraftworm's text is due to the surgical removal of a "3", which would take forever to fix properly without the original layered document (unless I were to plonk some other random symbol into the space).
kraftwurm and mystical_right_turn appear to belong to the artwork package; the others are from base.
Those all look great. Thanks!
I will push them to GIT.
Should we delete tdebase/pics/wallpapers/here-gear.svgz?
Darrell
On Mon, 9 Apr 2012 20:11:12 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
Batch #2. Contains moon.svgz, revised versions of globe and andes-venezolanos that will hopefully not have text display problems (I assume those were the two that were bad before—I didn't actually bother to check), and the three jpgs (default_gears, kraftwurm, mystical_right_turn). The unfortunate gap in kraftworm's text is due to the surgical removal of a "3", which would take forever to fix properly without the original layered document (unless I were to plonk some other random symbol into the space).
kraftwurm and mystical_right_turn appear to belong to the artwork package; the others are from base.
Those all look great. Thanks!
I will push them to GIT.
Should we delete tdebase/pics/wallpapers/here-gear.svgz?
I think I can fix that one too—it just wasn't on your original list, so I missed it. (I'll also try plonking lines or an asterisk or something from my collection of fractal brushes into that gap in kraftwurm to see if it improves it.)
Any others?
Should we delete tdebase/pics/wallpapers/here-gear.svgz?
I think I can fix that one too—it just wasn't on your original list, so I missed it. (I'll also try plonking lines or an asterisk or something from my collection of fractal brushes into that gap in kraftwurm to see if it improves it.)
Any others?
None that I am aware. I'm just glad somebody like you has the talent and willingness to help. :)
After receiving the change I'll push all of the updates in one effort.
Thank you!
Darrell
On Tue, 10 Apr 2012 10:31:55 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
Should we delete tdebase/pics/wallpapers/here-gear.svgz?
I think I can fix that one too—it just wasn't on your original list, so I missed it. (I'll also try plonking lines or an asterisk or something from my collection of fractal brushes into that gap in kraftwurm to see if it improves it.)
Any others?
None that I am aware. I'm just glad somebody like you has the talent and willingness to help. :)
This didn't require talent so much as a knowledge of how to use the tools, a lot of patience, and a strong perfectionist streak. ;P
After receiving the change I'll push all of the updates in one effort.
This should be the last set, I hope: here-gear + kraftwurm take 2.
On Tue, 10 Apr 2012 10:31:55 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
Should we delete tdebase/pics/wallpapers/here-gear.svgz?
I think I can fix that one tooâit just wasn't on your original list, so I missed it. (I'll also try plonking lines or an asterisk or something from my collection of fractal brushes into that
gap in
kraftwurm to see if it improves it.)
Any others?
None that I am aware. I'm just glad somebody like you has the talent and willingness to help. :)
This didn't require talent so much as a knowledge of how to use the tools, a lot of patience, and a strong perfectionist streak. ;P
After receiving the change I'll push all of the updates in one effort.
This should be the last set, I hope: here-gear + kraftwurm take 2.
Kraftwurm looks a bit better now; definitely usable.
Tim
On 7 April 2012 18:58, Darrell Anderson humanreadable@yahoo.com wrote:
I suspect my main system would be able to handle it (I upgraded it last year to a quad-core Phenom II), but I wouldn't try it on a PIII. Anyway, my hope is that I'll be able to render static PNGs from aurora and one or two others at 1600x900, which will be a start on providing widescreen wallpaper.
I mentioned the PIII because I think that should be our lowest standard. That is, if a wallpaper image won't display quickly and snappily on a PIII then we don't include the image as wallpaper. We don't need poor PR reports from people who can't load any wallpapers we provide. People running dual and quad cores might or might not notice any lagging, but people running a PIII sure will. Because one of the reasons people provide for wanting to run classic desktop environments as opposed to newer desktops is to keep using older hardware, then we should keep that reason in mind.
As I mentioned, the celtic.svgz kills my dual core system. Granted, I'm using the on-board Nvidia graphics and not a stand alone video card, but wallpaper should not bring a system to its proverbial knees. :)
Darrell
No I disagree on this point.
If we build our software to be bottlenecked by the most inferior system, we won't get a good product. Instead we need software that works for all systems.
That means we should have SVGs and JPGs.
A good solution would be to disable SVGs on low end systems (like we do for other extra's) instead of removing them altogether.
Calvin
On 04/06/2012 11:36 PM, Darrell Anderson wrote:
I vote that all svgz wallpaers get purged. Period. They require too much CPU and graphics horsepower to display. Nice for art shows but useless as wallpaper. celtic.svgz is the grand monster of all, requiring several seconds to load even on a dual core. In fact, while viewing celtic.svgz in my virtual machine, I could not toggle to my primary desktop without losing the desktop screen painting.
Darrell
+1
Also,
Browse the files in;
http://www.3111skyline.com/dl/dt/tde/img/wp/
for some to replace those we nuke with. Let me know if you like this style, etc..
Browse the files in;
http://www.3111skyline.com/dl/dt/tde/img/wp/
for some to replace those we nuke with. Let me know if you like this style, etc..
You two figure out what we want.
Please let me know which package a wallpaper is from. I don't want to spend time grepping the sources to learn where to replace an updated file. :)
If we add files, then remember we need to revise the respective make files too so the file actually gets installed into the package. :)
Darrell
-
Calvin Morrison -
Darrell Anderson -
David C. Rankin -
E. Liddell -
Timothy Pearson