Re: [Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Erik van Oosten
Rick, Ted, At this stage of the project we are just researching which options current popular CMS systems There are many many many (did I say many?) different features possible. I think you should first pick a target audience and then model your CMS towards that group of users with their

Re: [Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Che Schneider
Hey, At this stage of the project we are just researching which options current popular CMS systems I think you should first pick a target audience and then model your CMS towards that group of users with their application. Agree to disagree :) The few stars in the flood of available CMS

Re: [Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Pierre-Yves Saumont
Hello, What is the intended audience? Do you intend to create a product suitable for CMS administrators needs? In that case, we (the list) might not really be the ones to ask. Most people here would probably be more interested in a Wicket-CMS extension, something that would help us to create

Re: [Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Ted Roeloffzen
What we would like to do is create these components and to incorporate those in a comlete application.The components could become a Wicket-extension and the CMS could be used by others. Ted Rick On 9/13/06, Pierre-Yves Saumont [EMAIL PROTECTED] wrote: Hello,What is the intended audience? Do you

Re: [Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Pierre-Yves Saumont
That sounds good. The main component that I think is needed is one that allow the user to create rich documents. There are already many solutions for this, but they are generally not well integrated. (By rich documents, I mean rich text + images + minimal layout). Images are an important

Re: [Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Erik van Oosten
I can imagine 2 very basic components (assuming jsr-170 is used): - An editor component Features: - supporting different client side editors (e.g. FCKeditor and such) or clear text (e.g. for Textile fans) - supporting different models, but at least an implementation of a jsr-170

Re: [Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Justin Lee
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 If you're wanting your CMS to be anything more than a school projects, I don't really consider JSR-170 to be an optional piece. Both Liferay and JBoss Portal are either adding or have already added support for it. AFAIK, all the major players

[Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Ted Roeloffzen
Hello Wicket community, We, two IT-students, are currently working on our graduation assignment. Our assignment states that we develop a Wicket CMS, or at least components for the CMS. This assignment will take place from 4-9-2006 until late January of 2007. At this stage of the

Re: [Wicket-user] Developing a Wicket CMS

2006-09-13 Thread Jean-Baptiste Quenot
* Ted Roeloffzen: Our assignment states that we develop a Wicket CMS, or at least components for the CMS [...] We are also in doubt about using the JSR-170. Are you familiar with this JSR JSR-170 and especially its reference implementation Jackrabbit rock! I would love to see a