Great that you guys are bootstrapping this. Assuming I understand correctly these 2 JIRAs: OOZIE-884 is for graphic representation of a WF and OOZIE-883 is for WYSIWYG authoring a workflow.....
* OOZIE-884 would belong to the web UI where the user would see graphically where the processing is for the WF * The web UI needs a revamp to be able to see detailed info of coord/bundle jobs * The web UI needs to be rewritten using a UI framework other than ExtJS for licensing issues * A problem we always had the Oozie developers is the lack of Javascript skills to improve the web UI * What I really like about Oozie-883 mock up is the 'load WF' button, this is a critical feature, being able to suck and edit an existing WF * Using GWT seems like a good choice as it would allow IDE development and Java skills * As GWT converts things to JS we could still deploy the console as we do today (part of the WAR) (this is a big plus over things like PHP, Phyton backend solutions) * IMO we should open an new JIRA to port the existing web UI to GWT as well. An maybe we should model a couple of screen of the existing web UI in GWT to see that it will work. Thx. On Wed, Jun 27, 2012 at 9:50 PM, Mohammad Islam <[email protected]> wrote: > Hi, > At last, the Oozie team at Yahoo has taken concrete steps to implement the > most expected feature of Oozie: Workflow modeling tool to generate XML. > Ryota is evaluating different UI tools and opened a JIRA ( > https://issues.apache.org/jira/browse/OOZIE-884). > Ashish is designing a mock UI and also created another JIRA to track. ( > https://issues.apache.org/jira/browse/OOZIE-883) > > Please give your suggestions/comments into those JIRAs. > > Regards, > Mohammad > -- Alejandro
