Comments inline --- Francisco Herrador <[EMAIL PROTECTED]> wrote: > Just a point on size, why do you use the entire b7 BeanShell package for > scripting, just using the core version will strip arround 100kb ... (hint) Good thinking. > > My .2 cents on axualize & SiwxML & Thinlet > > Thinlet is *really* a great XML'ish widget library, MIDP & J2ME compatible > as far as i know, paired with Theodore lets you build just interfaces & > dessign applications with absolute MVC isolation (just on a mere 53kb wow!. > Robert wrote the largest sneaky java class i've seen but, heck! it works > like a charm! & fast even on old "standard" JVM 1.1.4), but the lack of many > common features right now avoids thinking on it for a "serious" application. I aggree it is very cool, but extemely limited. > > SwixML is a Swing-only (well not really true but...) , probably the slowest > widget toolkit arround, heavy, sometimes buggy and not widely supported > (remember, you need the *infamous/big* Sun's Java plug-in). > > On Axualize... Well, you do support SWT(good move, really as fast as can be) > and other GUI libraries, even support scripting with BeanShell (we use it > too, Pat Niemeyer did a very good work), well that's ok, but > interface-layout and interface-logic must be *really* sepparated when All of this is very plausible with Axualize. You do not have to include event handling in the GUI building document if you do not wish to. You can implement all of that in stand alone classes. In classes which extend Container, or maybe just put the listeners in their own documents neatly tucked away where only those folks who need to see it do. > working on large projects with distributed developpers & designers. Remember > that even VB sepparates form layout from event driven logic, otehrwise is > just a reedition of xsl transforms or jsp with code and usebean: just > different on syntax. > > Abstraction on several issues is desirable in areas like automatic field > validation and common tasks as filtered value lists/combos, there are > several ways to do it, but binding that code to the layout doesn't seem a > good idea, i know that Russell will tell us how easy is to abstract this > layer, only if we knew how to use axualize and JSR-57.... but that's the > point, we don't (have to/want to) learn new tricks to write code to support > events & actions & such on Thinlets and shortly on SwixML. Minimizing > learning curves is a critical factor to increase development production > ratio, and that's the key point nowadays, Rapid Application Developpement, a > missunderstood concept that is easily forgotten and missused. If what you are after is simplicy, and seperation of responsibility (think MVC) Axualize is a natural fit. If what you want is SWIXML type markup it would be cake to add that to Axualize as a subset. It is possible provide all of the functionality of Thinlets, SWIXML, XUL, XFORMS.. as plugabble subsets to Axualize. But at some point many developers will outgrow the capabilities of all of those tools. That is where Axualize has found it niche. It is still small (soon to be about 100K smaller) and very performant with a very powertful toolbox of features. > > Split clearly interface from events, add automatic common form validation / > translation / server communications, cover with easy to use and interactive > tools and, voila! > > Keep it simple on the outside no matter how complex is inside, and they will > come..... You are right, I will keep it simple, and yes they are coming. > > Best wishes on your project Russell. Thank you, you are very kind. > > PD: Congratulations to Wolf, just can't wait to see Franklyn running .... > but Don't forget Theodore!!!!!! please! Yes Kudos to Wolf. Congrats.
__________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com
