Well, I'm not that sure about portlet support gaining wider usage for
Stripes. I would love to get an answer "yeah, here's a Stripes-Liferay
integration bridge we've created" when I asked about possibility of
using Stripes with portals. But it's only because I've been forced into
Liferay and already know and love Stripes. Seeing what an unholy mess
Liferay is, I don't really believe that many of its fans would get to
love Stripes. It's simply to little convoluted and "enterprise'y" and it
gets you results too fast.
And about the frontend -- I've asked about reusing some of the Stripes
code recently on this list. We've exchanged some e-mails with Remi and I
got interested in his Woko project -- take a look
(http://www.pojosontheweb.com/)
I myself have a bit different approach and am still going to write my
own "framework", but I got some new ideas and I'm basing it on Stripes
now instead of writing it from ground up. I am concentrating my efforts
on providing a "base project" which you would fork to bootstrap your new
project and that will contain a good CMS out of the box. I also develop
mechanisms that make developers write much less code for standard grids,
forms and other every day stuff that we tend to write manually and is
repeatable. I'm encapsulating things like "text edit", "combobox",
"listbox", "treeview", etc. in the way that makes the amount of glue
code between JPA model and the frontend minimal while providing
"scaffolded" frontend that not only looks and feels "good enough" for
90% of cases but is also very easy to customize without anything more
than what we already know - JSP, CSS and jQuery.
I feel that I'm filling an important gap between Stripes and "full stack
frameworks". There are websites that are too complex (or get too much
traffic) for Wordpress or other PHP CMSes but are still not
"enterprise'y" enough to take advantage of heavy frameworks that make
all decisions for you. I love many of PHP SilverStripe framework/CMS
ideas, but it's not very polished and it's PHP. I'm trying to create
something even better for JavaEE and Stripes.
It will probably take me until the end of the year to have something
working and documented enough to be published. I'll most likely go with
Apache 2 license, so You'll be free to take a look and use it. Right now
I am implementing things I have already designed (I've put a lot of
thought into it) and until I'm finished with a prototype, I'll probably
won't be able to share work with other developers. But if you check out
the prototype once it's finished and you like it, you'll be welcome to
join the effort :-) If you're good with frontend side, there's probably
be a lot of web UI controls polishing to be done :-)
Best regards,
Grzegorz
W dniu 05.10.2012 23:20, azizi yazit pisze:
Hi Tim,
I just think by providing the portlet support would be oppurtunity for
stripes to be used by more ppl. But i get your points. I do agree with
that. I guess a lot of developers here want stripes-portlet because of
the portlet development will be much easier and simple by using
stripes. I'm more interested to provide a front-end stuffs to stripes.
Every web business now concentrate and spend a lots of money to have a
good web user experiences. And stripes tag have small capability for
that. I would like to start develop a restful library for stripes and
like to integrate front-end framework like ember or backbone with
stripes. It's less pain than providing portlet in stripes. Currently
we have a low activities in providing new stuffs. And we also not care
much regarding the stripes front-end. If you guys have a free time and
like to proceed with stripes front-end, just let me know. I can
provide with front-end expertises but i need back-end folks to
cooperate with me regarding the layer between back to front. Are guys
interested ;) ?
On Oct 5, 2012 11:12 PM, "Grzegorz Krugły" <g...@karko.net
<mailto:g...@karko.net>> wrote:
W dniu 05.10.2012 15:08, Stone, Timothy pisze:
> Bottomline, I can do “portals” without a single portlet.
However, I do
Exactly what I'm trying to accomplish with my own framework (I'm
basing
it on Stripes even though I thought I won't).
> sympathize with those that are forced into a Portlet platform,
any one.
> I’ve been there. Worse architecture experience of my career.
Yeah, it's a nightmare and - after such a wonderful experience with
Stripes - the pain is almost physical :-(
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New
Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
<mailto:Stripes-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/stripes-users
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
