G'day all. First time posting, so don't abuse me too much. :-)
This may have been too much trouble, and even if it's not it might be too late now to change, but wouldn't it have been better if all the UI objects only had Dabo Attributes etc? Then there would never be any confusion as to what's Dabo and what's the UI (wx at the moment, but one day, anything). So the object would only have all of the Dabo entries plus one new one, WrappedObject. WrappedObject would then be a reference to the underlying object that can then be used on the odd occasions that you want to access it directly. This would perhaps also help developers keep in mind that one day there might/will be other UI libraries and that they are doing something that will bite them if they ever want to change. Just a thought. Ian Simcock. On 24/03/2010 4:33 AM, Paul McNett wrote: > On 3/23/10 10:58 AM, Ed Leafe wrote: >> On Mar 23, 2010, at 1:53 PM, Ricardo Aráoz wrote: >> >>> But my point is that you can not know (without looking deep into the >>> framework) if it's a property or an attribute, and therefore the upper >>> or lower case won't help you to determine if the prop/att belongs or not >>> to wx. (not really in your case, as it is a method :-) ) >> >> Methods are indeed easier: if it starts with an upper-case character, >> it's not Dabo. >> >> For atts/props, yes, it is not obvious. However, the 80/20 rule applies >> here: 80% (or possibly more) of the time you'll be working with a very small >> subset of all the available properties, and you'll become familar with them >> very quickly (e.g., Form, Caption, Visible, ControllingSizer, Children, >> DataSource, DataField, Height, Width, RegID). The other 20% or less of the >> time you'll have to look it up, and when you do you should be looking at the >> docs or the source to find the available properties for the class. > > And properties are always capitalized; attributes are always lower. And as Ed > said > before, we never (hardly ever) expose attributes to users of the framework. > > One thing happened in wxPython to confuse things in 2.7: wxPython added > properties to > their framework (so now you have not only SetValue() and GetValue(), but also > the > Value property which wraps those getters and setters). The unfortunate thing > is that > the wxPython properties use the same capitalization conventions that Dabo > uses, so > they overlap. Dabo's properties trump wxPython's, but it is still confusing. > > Paul > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users > Searchable Archives: http://leafe.com/archives/search/dabo-users > This message: http://leafe.com/archives/byMID/[email protected] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
