Well, main points would be:
1. Tight integration with Web Content Management - so the same tools
are used for simple static HTML page editing AND for "built in"
pages with forms, grids, etc. So users can for instance easily add a
picture and a message to log in form.
2. A don't-repeat-yourself mechanism to quickly build forms from JPA
entities and their relations. I don't want a scaffolding code
generator, I want a mechanism that takes POJOs with maybe some
annotations on fields and generates a form and two way form<-->POJO
mapping with defaults sane enough for 95% of usual cases.
3. Built in support for CSS extensions such as SASS and combining,
minimizing and versioning static files.
I don't know how many of you do PHP work and know SilverStripe CMS, but
I like their approach a lot. Of course PHP is hell and SilverStripe is
far from perfect, but the speed with which I can build complex websites
with custom forms that nicely integrate in the management panel is
impressive and I would love to marry their form and grid concepts with
Stripes approach.
Fulfilling first two points using existing framework makes model and
code too complex in my opinion (I HAVE a private framework fulfilling
point 1 based on Stripes, use it since 2008 and it's grown very complex
over the years) -- such a tight integration requires work at lower
abstraction level than frameworks expose.
More of my wishes, which are nicely done by Stripes (except maybe
special JSP tags for form fields, but not sure if it's possible to get
rid of them at all) and I'd love to "steal" them:
1. No command line tools - I prefer coding in Java using IDE, not some
scripts using bash.
2. No code generation - it looks good while doing Hello World tutorials
but when the project is 2 years old and changes are neccessary, it
usually gets in the way.
3. No fancy JVM languages -- it's hard enough to find good Java
developers, so I'm not going to look for Groovy, Scala or JRuby ones.
4. Simplicity, no magic or bending standard JavaEE rules - I need
ability to debug, understand what's going on inside the framework
and get meaningful stacktraces.
5. Focused scope, small size - I don't want the framework to do my
dishes and contain code for that strange task I'm never gonna need
to implement. I want it to do one thing and do it well.
6. No special templating engines - JSP is enough and if used wisely
without inserting Java code, but just EL and JSTL, it is elegant enough.
7. No XML and no more than 1 simple config file. Also, no annotation
craze -- most common case should require next to none metadata.
8. No convention over configuration at all cost. I want the framework
to have sane defaults, but I don't want someone's convention shoved
down my throat.
9. No javascript and CSS componentization, and if they're gonna force
me to use a javascript library, I can only accept jQuery ;-)
W dniu 22.09.2012 10:00, VANKEISBELCK Remi pisze:
Interesting...
What kind of stuff are you trying to achieve ?
I mean, what is your requirement that no other fwk supports ?
------------------------------------------------------------------------------
How fast is your code?
3 out of 4 devs don\\\'t know how their code performs in production.
Find out how slow your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219672;13503038;z?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
