Mailing-List: contact user-help@pivot.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@pivot.apache.org
Received-SPF: pass (nike.apache.org: domain of gk_brown@verizon.net designates
 206.46.173.5 as permitted sender)
Sun-Java-System-SMTP-Warning: Lines longer than SMTP allows found and wrapped.
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (Apple Message framework v1082)
Subject: Re: [pivot] are there any tools to convert bxml to Java?
From: Greg Brown <gk_brown@verizon.net>
In-reply-to: <AANLkTi=8TzT5YMX1-raTo_wttSKrqvV7Zsy_22vf55Ln@mail.gmail.com>
Date: Mon, 03 Jan 2011 15:34:56 -0500
Content-transfer-encoding: quoted-printable
Message-id: <939528E8-2DA8-4541-B7D4-FDCA16E436B2@verizon.net>
References: <AANLkTimGToL8tdsjqFUHJUugmZAknb2mTjyycsJkLk=b@mail.gmail.com>
 <108F6E9D-38CE-4AB2-BFCE-502735631D5F@verizon.net>
 <AANLkTinV2kKxfmzWbjRFXrmM+JpAML-_eZuNku3nPoLA@mail.gmail.com>
 <AANLkTi=NXb2PevGTn0SBMv5asiOSAkbvhR0T29NQvhaM@mail.gmail.com>
 <87421A05-96A8-436C-9F1F-3AF13F0DDE7E@verizon.net>
 <1293466832098-2152270.post@n3.nabble.com>
 <AANLkTi=xnoeA76sReqRLPKCiReJTiDchmro+VQ6crFAh@mail.gmail.com>
 <1293701556655-2166783.post@n3.nabble.com>
 <AANLkTiktFrR8Scg3AZDni_FHDJxQPDFk3uosminNKitj@mail.gmail.com>
 <53C785D4-E53A-4C8D-8AF2-89596C621345@verizon.net>
 <AANLkTi=6h-TGqWn2sQecJvam4Fr8oQSNptqUSgp=OBnG@mail.gmail.com>
 <242A80D2-ADFE-4249-9F6C-8F71600745E7@verizon.net>
 <AANLkTinMtheKXK7FCjbERjuVt9T_=tQFe=pyQrBzmzvq@mail.gmail.com>
 <B4E2F387-601B-47C2-AD16-3C3A89844754@verizon.net>
 <AANLkTikpitjkSrSgM968eC2BWbBF5MCvvozG8_03+ZXz@mail.gmail.com>
 <DD3F80A8-64CF-47C4-9D59-625C681AC861@verizon.net>
 <AANLkTin+fod7uALGr+NuWgQOpG_k=WCc3Zb=xX=Gyrth@mail.gmail.com>
 <E70800F6-1EDC-4829-B397-1846E89B28BD@verizon.net>
 <AANLkTi=Q1f2pxa27MCGyzWKL3R98O5nsuRT-40jsd31M@mail.gmail.com>
 <F96829C5-1A3C-48A4-9DD3-826C69125F9F@verizon.net>
 <AANLkTi=8TgCJwpru2m-+qC8QkeRoKpadcTVrccV5PCsc@mail.gmail.com>
 <07EC81E3-7257-4452-AB5E-F6973B918B08@verizon.net>
 <AANLkTi=8TzT5YMX1-raTo_wttSKrqvV7Zsy_22vf55Ln@mail.gmail.com>
To: user@pivot.apache.org

> OK, I'm not actually thinking BXML should be abandoned.  There are =
many type of user and usage scenario which would fit BXML approach.
> But these approach is static, it is not good fit for creating more =
dynamic library for GUI(for instance the number of table columns are =
changed based on passed parameter class).
> Since you put low priority for supporting readable Java code =
generation, I thought you may not be interested in this type of =
approach.

I don't see the value in trying to generate "readable" Java code from =
BXML. If you are a developer who prefers to declare your UI in Java =
(perhaps using your builder approach), then you probably won't be using =
BXML anyways and won't care what the generated code looks like. If you =
are a developer who prefers BXML, you most likely will never look at the =
generated code, since presumably you want to continue developing in BXML =
and only use the compiler for the performance or compile-time type =
safety benefits.

Besides, all we're really talking about here is where generated =
attribute setters go. The generated code would still be quite readable - =
it just may not be organized exactly the way you would do it had you =
written it by hand. To me, that's just not a major issue.