Hi, I think using BXML like layout language separated from programming language would make sense. But the current BXML is almost full programming language like JSP. Many sample code in Pivot looks suggesting such approach. These are misleading thing for the need of some layout language.
Even we have a simple GUI description In Scala/Java, these are compiled langauge. So it is not possible to change them without recompilation. >From my experience using Pivot one month, I feel it would be better to have more concise layout language than BXML, which is dedicated to only for layout information. For instance boxpane/tab/split pane etc are layuout object. on the other hand, radio button/TextInoput etc are information receptor which should be part of Programming language (Java/Scala). And from programming point of view, the GUI aspect should be hidden from API level. That means they should just look like some String to some type converter. It should be associated with these type information, and provide some getter/setter to access user input data. Also this may allow to have higher layer API to remove specific GUI library dependency.(maybe it might be possible to support both GWT/Pivot/SWT etc, with common layout script plus receptor adaptor API) Anyway this might have been a bit digression. But I would like to know other poeple's option for this type of approach.. On Thu, Jan 27, 2011 at 10:36 PM, Philippe Lhoste <[email protected]> wrote: > On 27/01/2011 23:15, Sandro Martini wrote: > >> Just a quick info, me and Greg (and maybe other Pivot developers) are >> very interested in Scala ... but as you the problem is to find enough >> time :-) ... >> > > Sure! I have the secret (well, not so much now) hope to help a little bit > here. > > > This week I committed some simple eclipse projects on Scala 2.8.x and >> Pivot-2, in our Pivot-Scala project ( >> http://code.google.com/p/pivot-scala/ ), there aren't released >> distribution files, but from its Subversion trunk you can download >> everything even as a guest (you can find all the info under its Source >> link. >> But attention, it's a work-in-progress, and it's only at the beginning. >> > > Like my own work... > I also noticed the recent thread on Scala, I also share the feeling that a > Scala DSL to replace BXML would be nice. > But my initial work is to stick to closely to the current tutorial way (I > would have put the list of states in a text file...) while using some Scala > mechanisms. I like the line: > states filter(_.toUpperCase.startsWith(text)) foreach(suggestions.add) > replacing 5 lines of Java while remaining reasonably readable. > > Note: it is unfortunate that Pivot uses its own set of collections, it > cannot interact nicely with Scala, unless re-doing some wrappers/implicits. > > > Much more content could go there, for some I have already some working >> test, and probably even Greg ... but I know Scala only a little so >> anything is really much more time consuming. >> > > Same here (Scala newbie, little time...). > Trying to advance a bit by myself, for self-educational purpose, before > looking at the work of others... > > > -- > Philippe Lhoste > -- (near) Paris -- France > -- http://Phi.Lho.free.fr > -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- Cheers, calathus
