[
https://issues.apache.org/jira/browse/HBASE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399660#comment-13399660
]
Elliott Clark commented on HBASE-6259:
--------------------------------------
I don't really know enough to have a very in-depth discussion about those so I
would hold off on throwing my support to one until I have some time to poke at
the options.
As for do I think it's worth the effort, that kind of depends on what people
want from hbase. If a minimal ui is all that we invision ever having then just
keeping jamon and moving the last pages off of jsp seems the best. However if
we want to have things like monitoring and trending (stack you and I had
mentioned this), a shell (someone at hadoop summit mentioned this), and
configuration (we started talking about dynamic configs lately) all on the ui
then I think it *could* be worth it to go to a more modern and adopted
framework (GWT would seem to be a good way to get rich views without a UI
expert but that's just a first thought).
ps. Why is rails even in there? I like rails and all but I don't really relish
pulling in all of the ruby wold to make some html strings.
> Unify all of the templates into one templating language
> -------------------------------------------------------
>
> Key: HBASE-6259
> URL: https://issues.apache.org/jira/browse/HBASE-6259
> Project: HBase
> Issue Type: Improvement
> Components: master, regionserver
> Affects Versions: 0.96.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Labels: noob
>
> Right now .jsp and jammon templates can't share common parts as they are
> un-related. We should move to one templating language. Maybe also move away
> from jamon.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
