Sure these kinds of things exist. In Hippo CMS 7, we're nesting panels that each have their own instance-specific configuration. Different document types have a corresponding (admittedly quite simple) plugin configuration that can be edited within the cms. The cms itself is mostly a (more involved) configuration of such loosely-coupled generic panels.
This approach is actually opposite to Wickets philosophy (only Java + HTML). But the great thing about combining opposites is that there is a sliding scale for doing things. You can start out using the generic building blocks, giving you limited flexibility in terms of how these panels can interact, but at least they can be easily configured using a web interface. Then, as your needs transcend the possibilities of this simplistic solution, you can write your own plugins with the full power of Wicket at your disposal. Cheers, Frank > -----Original Message----- > From: Tobias Marx [mailto:superoverdr...@gmx.de] > Sent: 16 January 2009 14:10 > To: users@wicket.apache.org > Subject: Re: Things I miss in Wicket > > Brix only works the way it works because it does not need a > database......with a flexible achitecture and a database this > would not be possible without too many limitations either. > > The ultimate goal would be a web-application builder...or at > least a highly configurable website (whatever kind of) that > only needs to be written once and can be customized easily > without "changing" the code. > > So far this does not exist....the thing that comes closed is > Typo3, Drupal or something like that...or the Dolphin > community builder - but this is all at a very early stage and > so far starting from scratch is often the better option in > the long-term. > > -------- Original-Nachricht -------- > > Datum: Fri, 16 Jan 2009 07:59:11 -0500 > > Von: Richard Allen <richard.l.al...@gmail.com> > > An: users@wicket.apache.org > > Betreff: Re: Things I miss in Wicket > > > > > > > > > > What I don't like about Wicket is, that it is like writing normal > > > Java applications - although rich clients applications are being > > > replaced > > with > > > web-based solutions and there is a fundamental difference between > > > web-applications and normal java applications. If you have a java > > > application as a product, it is normal to employ software > developers > > that > > > work on bug fixes and new features all the time - they constantly > > develop > > > and it is expensive....everything has to be done by a software > > developer. > > > > > > Being more like a "normal" Java application (whatever that is :) is > > precisely why some of us like Wicket. > > > > > > > > > > > An ideal web-application is developed once and the Java code is > > > never touched again for 3-5 years until there are a lot of new > > > features necessary.... but in this time there could be > several small > > > changes or complete re-designs...and in that time this > should be a > > > pure matter of HTMLing without the need of touching the > Java code. > > > If a new input field > > is > > > added or some new strings.....or whatever....or maybe a new Flash > > component > > > etc....this should still work without changing the -war file that > > carries > > > the Java code...only changes in the templates or the > database should > > > be made. > > > > > > This sounds quite unrealistic to me for most applications. > But I think > > a CMS (such as Brix: http://code.google.com/p/brix-cms/) > comes close > > to what you are asking for if I understand what you are > trying to get > > at. > > > > > > > > > > > Wicket does does not really allow this. Or assume you have a > > > web-application you want to sell - and don't want the customer to > > > know Java....they would be really restricted in the > changes that are > > possible. > > > Another advantage of Wicket is that it creates a session > for every > > visitor > > > - no matter whether it is a crawler/search engine that > does not need > > > a session or a logged in user.... > > > > > > Again, a CMS. > > > > -Richard > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > f.vanlankv...@onehippo.com www.onehippo.com Amsterdam Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100 +1-877-41-HIPPO --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
