> I'm not sure I fully understand what you are proposing. > > Is this to remove the need for methods such as > BoxPane#setOrientation(String orientation)
Yes. Noel had suggested something along these lines last week - I'm basically following up on that discussion. > If so, then how about first attempting a valueOf using the raw attribute > value from the BXML? If that fails, then try with the uppercase ersion. > That would allow case sensitive, mixed case values to be supplied in BXML. I thought about that, but it didn't seem very elegant, especially since the first attempt will fail for pretty much every use of an enum in BXML. :-) > This could happen the other way around if preferred, and also could enforce > a toUpperCase() conversion if the enum lived in a Pivot package. (If that > is the Pivot convention) True. On the other hand, BeanAdapter also lives in a Pivot package, so we could potentially use that to justify the naming convention. And maybe there are other options. I'm not sure what would be best - just thinking out loud. G
