The web console has been designed to be very lightweight, and the first consequence is of course the fact that by not using a big framework, the code is a bit more complicated as you have seen.
If we plan to rewrite one, we need to make sure the benefits outweight the drawbacks of rewriting for the sake of it, as if we are to rewrite, we will have to actually maintain it, whereas, now, the felix community does the maintenance. Also, i don't think such a console is specific to Karaf, so it might very well make sense to look for other communities to work together (such as felix, sling, geronimo) ... On Mon, Feb 28, 2011 at 21:06, Charles Moulliard <[email protected]> wrote: > Hi, > > This week-end, I have spend some time on Apache Felix & Karaf > WebConsole code. What I have discovered make me very unhappy and > frustrated because the project(s) lack of structure, complicate the > development of screens and decrease development productivity (html > code is mixed in javascript, json variables are set everywhere in the > code and use in several of javascript functions, no template is used > to render html pages, locale is not used to translate text, ....). > > I have no idea about what is planned to do for the future (Karaf 3.0), > if we will continue to use Apache Felix WebConsole or create our own > web console, but a reflexion about which Web frameworks, Ajax > Javascript should take place to simplify development lifecycle. > > Regards, > > Charles Moulliard > Apache Committer > > Blog : http://cmoulliard.blogspot.com > Twitter : http://twitter.com/cmoulliard > Linkedin : http://www.linkedin.com/in/charlesmoulliard > Skype: cmoulliard > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
