Well Daniel I guess you're correct on this one. the
StyleManager is not fully documented that's why it
might take some getting use to.
I'll go ahead and redesign it and add some basic
examples and documentation.
PS. Please remember that the StyleManager Components
are main for demo use. The fin
Cool. I think I'll try to implement something that's
very simple as well.
--
Raymond Irving
--- Michael Bystrom <[EMAIL PROTECTED]>
wrote:
> I have a theme system that I like allot in the IOS
> library, it uses a
>
> dynapi.theme = {}
>
> object as the main theme holder, then for each new
> t
I have a theme system that I like allot in the IOS library, it uses a
dynapi.theme = {}
object as the main theme holder, then for each new theme that is loaded it
get it's own namespace
dynapi.theme.button = {}
The first time the button is called it creates the theme and then for each
new call
The StyleManager component are more complex than
traditional widgets. It will take alonger time to
create a StyleManager component than it would an
ordinary widget.
The beauty about the StyleManager is that it give the
user the flexibility to change the behavoir of the
component without having to
Hi,
I agree with Daniel. I just don't understand it. A very nice
project but who is going to use the StyleManager implementation
without full documentation of how the internals work. I printed
off nearly 10 files from one top level example and then gave up.
These completed StyleManger component
Hi Raymond!
I still actually dont get the style manager completly...
I have found styles in the gui catalog, but forgive me if i am a bit
slow. But i dont really get it :(
Say i have the viewpane and by default it uses a style like
viewpane.style (or am i already out of the area)?
How do i chan
