That would be a very nice component to have in extensions. So if you make it really nice... I think an API like DatePicker works for a component like this. The 'problem' is that components like these are very configurable. You don't want to loose too much of this flexibility, but you have to choose between how much you support (strongly typed) out of the box and what part you don't (or e.g. support by having a template method for JS generation).
Of course, if you just want to use it in your own project, you don't have to support the flexibility, and don't have to think hard about what a good API would be. It's fun to try to really make it good though. One final thing. For previewability, it would be great if you could attach the rich text component just to a textarea tag. Eelco On 9/1/05, Nick Heudecker <[EMAIL PROTECTED]> wrote: > > > make it as easy to use as possible for users. > > > Where's the fun in that? :) > > > > did you look at this one: > > > > http://tinymce.moxiecode.com/ > > I did look at TinyMCE. I think they're pretty similiar and both licensed > under the LGPL. Which one I use doesn't really matter to me, so if people > on the mailing list have preferences, I'll go with what's preferred. > > > > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
