Comments inlined... Le 22 sept. 2012 à 11:15, Grzegorz Krugły a écrit :
> Well, main points would be: > 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. By "users" you mean users of the app, or some kind of "developer" or "content manager" role ? > > 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. Well you should definitely have a look at Woko ! It actually does exactly that. We call it "ObjectRenderer" : feed it with any Object and it uses reflection (and facets) in order to render it with FORM elements (text fields, checkboxes, selects etc.). And it's fully configurable on a Class / user role basis. > Built in support for CSS extensions such as SASS and combining, minimizing > and versioning static files. Kindof rail's "assets" ? Excellent, I'm thinking of something similar for Woko. > No command line tools - I prefer coding in Java using IDE, not some scripts > using bash. We have command-line tooling, but it's more a didactical thing : you can do everything inside your IDE. > > 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. Woko doesn't generate anything. It's fully dynamic. > > 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. Woko is written in pure Java. You can use Java or anything in order to write facets, and all your code. > 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. Same again. Pure Java, a very lightweight codebase... > > 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. Well, this is a bit subjective : what do you want it to do ? But I think I get the idea... > > No special templating engines - JSP is enough and if used wisely without > inserting Java code, but just EL and JSTL, it is elegant enough. In my arms :) > No XML and no more than 1 simple config file. Also, no annotation craze -- > most common case should require next to none metadata. Woko is convention-over config, uses classpath scanning etc. it doesn't require anything to startup excepted a small Java class that "boots up" everything. It does use annotations though : it has 1 annotation that you use on the components you write, and Stripes' and JPA (if you use Annotation Mapping) and Bean Validation (if you use annotation mapping again). Of course, it's far from stuff like WebBeans etc. : Woko doesn't require you to write annotations, just use some. > > 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. Yep. > No javascript and CSS componentization, and if they're gonna force me to use > a javascript library, I can only accept jQuery ;-) Woko's default pages don't need JS. The "work flow" is fully "good old page reload" by default. You can change this of course, but there ain't nothing fancy by default. Oh, yeah, we have a "bootstrap" skin that uses twitter bootstrap... and JQuery. Woko's RPC JavaScript API works with JQuery or Dojo... I definitely think you should have a look at Woko. It actually does almost everything you need, and maybe more... And I'd be definitely interested by your feedback : you raise very good points IMHO !! The docs are sparse and probably outdated some times, but the framework ain't : we actively use it to ship various apps. So just drop us an email there if you have any question : pojosonthe...@googlegroups.com It'd be my pleasure to answer you ! Cheers Remi http://www.pojosontheweb.com
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ 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
