[
https://issues.apache.org/jira/browse/HADOOP-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087319#comment-13087319
]
Robert Joseph Evans commented on HADOOP-7532:
---------------------------------------------
bq. I guess the confusion is mostly from the composition of the existing
webapps rather than the framework?
My biggest confusion was with Guice and how it integrates with Hamlet/Jetty. I
like inversion of control(IOC) for the flexibility that it can offer,
especially with testing. I have used Spring extensively in the past but IOC
always comes with a steep learning curve. Even more so when attributes are
used to tie the dependencies to where they are injected. This is because there
are no clean direct links between implementation and usage in the code. Yes an
XML description of the dependencies is often worse, but at least it is mostly
in a single place and no real magic is happening behind the scenes where
objects just appear. Granted this was not as steep of a curve because there
was not as much of the typical Interface/Implementation split that you see in
typical IOC programming. I did not have to look at the class hierarchy to try
and figure out what is going where as much. But the lack of it confused me a
bit because I was expecting it.
The other big thing to confuse me was the composable blocks as you called them.
It took me a while to trace down to the deep layers of JQueryUI, View, etc. to
see where each of the parameters were being set and used to know what I had to
do to change them. Some javadocs with simple examples would be a big help in
understanding how to use them properly.
bq. Since you don't have to learn any new syntax (like wtf is <%& etc. in a
template system)
$() and _() threw me for a bit of a loop too. Not as bad as <%& because it is
not a new language. Typically in java they would be something like
getContextValue() and endBlock() respectively. I understand the desire to make
the code smaller and more compact but that too is confusing.
I do think that it is a fairly simple framework to use, once you have overcome
the learning curve. Documentation and simple examples could go a very long way
in making the system more accessible to new developers. Without it I can see
lots of other people wanting to go back to JSPs etc. Simply because it is
something they know and can work on without having to learn something new.
bq. I didn't say that.
Sorry, I misunderstood you. I like the builder snippet that you put in, I
would like it if we could look at moving most of the common HTML generation
widgets to something like that.
bq. If anyone can solve the problem cleanly.
I trust you to have done your due diligence on this. Like I said previously I
am not an expert on HTML and I am not a web developer. I know enough to be
dangerous which is why I was asking.
> Hadoop web UI 2.0
> -----------------
>
> Key: HADOOP-7532
> URL: https://issues.apache.org/jira/browse/HADOOP-7532
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 0.23.0
> Reporter: Luke Lu
> Assignee: Luke Lu
> Fix For: 0.23.0
>
>
> People have expressed interests of bringing Hadoop web UI up to date with the
> lightweight embedded web mvc framework used in MAPREDUCE-279 (cf.
> MAPREDUCE-2399). This is the umbrella jira for UI improvement for 0.23+.
> Individual items like web framework refactor/move and the unique challenge
> for MR2 webapp security will be filed separately.
> Thoughts/ideas on various improvement of Hadoop web UI are welcome here. Some
> of the ideas will naturally become sub-issues.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
