Yeah I just didn't take the time out to edit the package names, so
feel free to hack away in there.
If you were looking to add a TabNavigator you could create a
TabNavigatorSkin for use with a Navigator. Put a TabBar in it and
bind the dataProvider of the TabBar to the NavigatorGroup also in
the skin. Assign that skin to a Navigator and your should be up and
running.
You could go one further and create a TabNavigator class that
extends Navigator and give it your new skin as a default. I'v always
wondered whether having these empty classes just so I can define a
default skin to it and give it a new name made any sense, although I
did do it for the 2 Accordions as the layout for those is a little
tricker to set up.
Tink
Ok, I am going to do this.
But what are the package names going to be? Should I just change them
to org.apache.spark.components... etc for now? or spark.components ?
Mike
