Hi Todd,
> I'd start by reading the WTKX primer a few times - there's a lot of dense
> content in there as to how WTKX works.
> http://incubator.apache.org/pivot/1.3/tutorials/wtkx_primer.html
Ok, I have to study a lot here :-) ...
>> And a last question:
>> could be useful (for my applications using this component) to add the
>> visual part of this component to a custom extension of the TerraTheme
> I don't understand the question - can you clarify?
I've seen that in the constructor of TerraTheme, there is a
registration for all Pivot Standard GUI components, like:
componentSkinMap.put(Accordion.class, TerraAccordionSkin.class);
componentSkinMap.put(ActivityIndicator.class,
TerraActivityIndicatorSkin.class);
componentSkinMap.put(Alert.class, TerraAlertSkin.class);
...
So my question is to understand if I'd have to register in a similar
way also my custom components (if this could have some utility), for
example to have some benefits (some behavior or other) from TerraTheme
... what do you think ?
> What I'd do is create your component first, then write up the experience
> from the point of view of someone who'd never created a custom component
> before. Then that write-up could both be published as an article and
> checked into the platform developer's guide :). No JIRA ticket necessary
> for stuff like this - it falls into the existing bucket of "improve
> documentation".
Ok, and in the future this could go in our documentation, or maybe
(revised) in an article ... but until I'll have this many weeks are
required :-) (it's a low priority in my new application at the moment)
.
Thanks,
Sandro
