|
I’ll like to put a NO vote out there for the idea of turning SwixML into a JSR57. The syntax of JSR57 really is much more complex then SwixML from a non programmers point of view. I think JSR57 is great and should be the basis for all the IDE’s GUI tools out there but that’s not what I thought SwixML was about. Axualize sounds like a great product and I hope it gets the attention it deserves but if I wanted to use Axualize I’ld use it. Axualize and JSR57 are directed at a different crowd (the programmer) than SwixML (the dialog designer or user). I want the simplest xml that covers 90% of the cases (actually 100% of mine). I’m hoping users of my application (as well as non programming designers) will be able to make custom changes to dialogs by simply opening the xml and making the changes. When designers (who know HTML) look at JSR57 output they’re really put off. When I show them SwixML they instantly understand (no training necessary). The application user and dialog designer is the crowd I’m looking to address.
Also, as a programmer, I love the simplicity of the SwixML model. Most users of SwixML code will not be nearly as skilled programmers as the others on this list. A simply model that everyone can understand is always a plus. I was able to start making my own dialogs and adding custom tags almost instantly with very little effort. I don’t care about size of lib but it is a pretty good indicator of a design patterns complexity. SwixML is simpler then the others. I plan on using products based on JSR57 but just not in the same capacity.
Just a users vote and opinion on why I like the current model of SwixML. Let’s not mess it up by trying to make it all things to all people. KISS. |
- Re: [Forum] Don't do JSR57 John Piersol
- Re: [Forum] Don't do JSR57 Dan Kirkpatrick
- Re: [Forum] Don't do JSR57 Russell White
