W dniu 22.09.2012 13:27, Remi VANKEISBELCK pisze: > Comments inlined... Doing the same...
>> 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. > By "users" you mean users of the app, or some kind of "developer" or > "content manager" role ? I mean users of the app. What I like about SilverStripe is that you install it and you instantly have user and content management. You can then create a new Page type that has custom fields, with custom GUI and that gets placed in the CMS tree and renders using standard mechanisms. I try to mimic this. > 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. Sounds interesting, will take a look. >> 3. 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. I don't really know rails. But probably yes ;-) > Woko doesn't generate anything. It's fully dynamic. What do you mean by that? I was rather thinking of one-time initialization on deployment, but yes - automatic, based on existing code and annotations. > Woko is written in pure Java. You can use Java or anything in order to > write facets, and all your code. Cool. >> 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. > > Well, this is a bit subjective : what do you want it to do ? But I think > I get the idea... More or less what SilverStripe does but better executed and NOT in PHP ;-) > 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). I don't mind using some annotations, Stripes is nice in this regards. But when I look at some of Spring or Hibernate classes, there's more @ than normal lines of code -- I strongly dislike this, because it just looks like they've moved XMLs to annotations without ever thinking about improving it. >> 9. 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... Nice. I also want to integrate Bootstrap. I think You have similar ideas to me, I want my framework to still be based on "good old reload", but also automate data moving from Entities to Forms to HTML and back. > 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 !! I'll take a look at Woko. But... > The docs are sparse and probably outdated some times, but the framework > ain't : we actively use it to ship various apps. ...that's one main point, I forgot to write in my last e-mail. I am committed to spending at least 30-40% of my time writing my framework on writing documentation. I want to have nice javadocs (Stripes is brilliant in this regard) and I want to have nice documentation along with how-tos. What's stopping me from finding my ideal framework is very probably lack of documentation for most of them. It'll take less of my time and resources to implement my own framework than it would to deeply test all of existing ones. This sucks, but that's how the world works. > So just drop us an email there if you have any question : > pojosonthe...@googlegroups.com <mailto:pojosonthe...@googlegroups.com> Thanks. I'll most likely go on with developing my own (I've already designed most of it and started some proof of concept implementations), but I'm open on cooperation and if I can take something good from Woko or give something good back -- I'm all for it. ------------------------------------------------------------------------------ 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
