On Tue, 31 Jul 2012 18:52:56 +0900 Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> On Tue, 31 Jul 2012 18:34:43 +1000 David Seikel <onef...@gmail.com> > said: > > > On Tue, 31 Jul 2012 17:27:27 +0900 Carsten Haitzler (The Rasterman) > > <ras...@rasterman.com> wrote: > > > > > On Tue, 31 Jul 2012 17:16:38 +1000 David Seikel > > > <onef...@gmail.com> said: > > > > > > he's complaining about lack of features in e17 vs e16... and the > > > comp dialog hasnt split advanced vs basic - its all advanced. all > > > options there. > > > > The composite settings dialog is just one of the things he brought > > up in this thread, but I don't think there was one in e16, so E16 is > > irrelevant to this part of the conversation. > > > > It's not advanced, it's so far past advanced it's silly. That's my > > point. Even advanced users can't use it. > > then don't touch what u don't understand. those settings exist > because that's how comp works. several of them exist due to faults in > drivers and for fine tuning optimizations. if you don't know - then > don't touch. Which is the exact opposite of the advice you gave to "just try it and see". You can't have both. I'm pointing out that those parts you are saying to "just try it and see" are just as hard to figure out as the parts you are now saying "don't touch what you don't understand". No one understands any parts of it, this is the problem. That dialog really needs a major overhaul, and it seems that the only people that understand enough of it to do that overhaul are the people that wrote it. This makes it almost entirely useless for every one else. Face it raster, it's a raster only settings dialog, and you can't tell people "just try it and see" and also tell them "don't touch what you don't understand". Coz they don't understand any of it, and are telling you they don't understand any of it. You just can't have it both ways raster. I can see that there are parts that MIGHT be easy to understand if only they where done a little differently, but I can only see that after some experimentation and what you have described here. If a very experienced E17 developer does not understand it, then the 99.9999% of people that are less experienced non-E17 developers have no hope in hell, and it might as well not be there. It needs work, plain and simple. I suggest a basic dialog, which would likely be just "Shadows". Then an advanced dialog which might be "choose stuff from the current theme", though perhaps if that was actually easy to understand (it isn't now) then it could go into "Basic". Then a "fix faulty drivers" dialog, though perhaps that could be disabled if those faulty drivers are not being used? A "fine tuning" dialog. Finally, a "debug" dialog, which you got already. Oddly enough, "debug" implies "for developers only", yet it's the only part that's almost entirely understandable for most people. lol -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
