pivot-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Brannon <greg.d.bran...@gmail.com>
Subject Re: Determining Pivot component attributes and styles
Date Sun, 19 Aug 2012 21:54:12 GMT
Roger (representing many),

As I said, it's only been a few days, but in that short, often 
frustrating time, the good fortune to find the Component Explorer was 
not mine.  After your response, a simple Google search led me here:


I see its potential, though somewhat indirect, to answer many of my 
questions about attributes and styles, and I thank you for taking the 
time to respond to my plea for help and for the encouragement.  I'm 
often blind to the obvious, but the value and location of the Component 
Explorer should be more prominently displayed for explorers wandering 
off the beaten path like me.

I understand the connection to the bean methods, but I don't yet know 
how to exploit that and wonder why I'd want to, hoping I'll never have 
to.  I'm completely mystified by skins and how I'll use them to my 
advantage, but I think I understand their importance to tailoring the 
Pivot experience, and I hope I figure them out someday.

Back to the tutorials with a new and improved perspective . . .


On 08/19/2012 05:25 PM, Roger Whitcomb wrote:
> Hi Greg,
>    First of all, thanks for using Pivot!  And I sympathize with you -- 
> I am always on the Component Explorer looking at things.
>    Anyway, the short answer to your question is:  the component 
> properties correspond to the "bean" methods in the components 
> themselves. These would be the "getXXX" and "setXXX" methods of (for 
> instance) PushButton, while the style attributes are the "bean" 
> methods for the skin, which (in my example) would be 
> TerraPushButtonSkin (and all their superclasses).  Some of the 
> multi-value things are a bit tricky, but most have several ways to set 
> them. Playing around with the ComponentExplorer demo is one of the 
> best ways to start, as are all the various demo and tutorial 
> applications on the website (and of course the Javadoc).
>    And you can always ask here if you get stumped -- we're fairly 
> responsive because we've been where you are ;)
> HTH,
> ~Roger Whitcomb
> Sent from my iPhone
> On Aug 19, 2012, at 11:25 AM, GregBrannon <greg.d.brannon@gmail.com> 
> wrote:
>> Sorry to be the slow guy in the group, but I find the bxml document 
>> approach
>> to UI definition difficult.  I'm much more confident with it today 
>> than I
>> was a few days ago when I first picked up Pivot, but I'm still unsure 
>> how to
>> know what attributes and styles are available for specific 
>> components.  The
>> FAQ says:
>> ". . . So, you can simply refer to the Javadoc for the component to 
>> identify
>> the supported attributes. . . "
>> I then go to the API page for PushButton, and I see the buttonData 
>> default
>> property but no mention of 'x', 'y', 'width', 'height', and the other
>> who-knows-what attributes that can be used to define this component.
>> What am I doing wrong?  I want to like this GUI framework, and I do 
>> so far,
>> but I'm still struggling a bit with the actual implementation.
>> Thanks for your help and your great work!
>> -- 
>> View this message in context: 
>> http://apache-pivot-users.399431.n3.nabble.com/Determining-Pivot-component-attributes-and-styles-tp4022058.html
>> Sent from the Apache Pivot - Users mailing list archive at Nabble.com.

View raw message