For me, it's the "real world apps", *plus* the interest in porting GXP
to other platforms, like C++, and Ruby. Personally, I'd like to add C#
to that list. ASPX, like JSF, has its charms, but many .NET developers
(including me) would like alternatives.
I do find the zipscript YUI examples interest
Thank you for taking the time to evaluate zipscript.
This is not currently being used in any real world apps because it is
new. That is certainly a valid concern. It is kind of a catch 22
because how can you ever be used in a real world app if people only
want an engine that is being used in a r
Joe,
My advice would be to spend some time writing demo apps and deploying
them on some servers, that way people can see the library in action.
S2 has a wide user base and so (imho) we can't afford to take risks by
dedicating time to converting the core templates to work on an unproven
libra
As I'm never a big fan of relying solely on the fact that technologies
have been "used", I'd compare feature sets. Here's what I like from GXP:
- Pre-compile for performance
- Type safe
- Injectable
- White space reduction
- l10n and i18n support (although difficult to determine exactly how
t
Thank you for your feedback Al.
While you can't see the code in action with a deployed application,
you can view some of the unit test/scripts/output (there are more)
with the following links:
- if directive
- test case:
http://code.google.com/p/zipscript/source/browse/trunk/core/src/main/test
I have committed my changes to xwork trunk, I will be testing more on
Showcase and trying to write some integration tests as I go. If
anybody else could help testing this, have fun :). If nothing is
broken I will also commit the changes to the xwork branch.
musachy
On Sat, Jul 19, 2008 at 8:50 AM
