Hi, I think there's a good idea in here, but I wouldn't be too sure about where to begin with it today. Partly because my head goes to other subjects here, like performance, timing and synchronicity, and partly because your work on this subject illustrates how complicated this gets. You list five areas affected.
But I think you're not wrong when you point to an architectural step into it with a single global constant like high, med and low. And let skins and effects and easings look at that as they will or won't. As for an autoheuristic setup, reminds me of another graphics capabilities selection process http://code.google.com/p/wtkx/source/browse/trunk/src/wtkx/in/Screen.java if (Java.IsVersion16OrNewer) return BackingStore.Type.GPU; else if (Os.IsDarwin && Java.IsVersion15OrNewer){ if (Os.Version.equalsOrNewer(10,5)){ if (container instanceof java.applet.Applet){ Object peer = container.getPeer(); if (null != peer && "apple.awt.MyCPanel".equals(peer.getClass().getName())) return BackingStore.Type.GPU; else return BackingStore.Type.CPU; } else return BackingStore.Type.CPU; } else return BackingStore.Type.GPU; } else return BackingStore.Type.CPU; cheers, john On Thu, Apr 2, 2009 at 5:07 AM, Sandro Martini <[email protected]>wrote: > Hi to all, > sorry, some other hints on this subject. > > As effects, we could have the following categories (and handle on/off > when desired): > - animations (like animated images or movies) > - transitions (like fading or sliding) > - gradients > - transparencies (like for menus, popups, etc) > - background (with gradient, with watermark, with vectorial drawings, etc) > - others ... > > Having a support in the base Pivot classes for standard levels (and by > default all on), but leaving any skin to override what is > enabled/disabled, or at least for the custom level. > Instead Minimum (none) and Maximum levels could be handled in base Pivot. > > For example, I've seen many articles on (poor) performance of > gradients etc on many OS / Window Managers and Graphics Cards / > Drivers, the the category for this. > > But the best could be to have a utility class to query the graphics > engine to tell is the desired effect is Hardware-enabled (but I don't > know if this is possible and how to do, sorry), maybe in a way > callable (if desired) by the user Applet/Application at Startup (and > maybe persisting results with Preferences or some other way). > Then any skin could think at what to do in its custom level, depending > also on these values, but i understand that all this could be > difficult. > > > What do you think ? > > Bye, > Sandro >
