On 27 Jan 2012, at 08:05, Jose Badeau wrote: > Hey Scott I'm not exactly sure how I should involve myself. I have a design > in mind for a way to make the front-end pluggable like the java side. > Should I submit a design spec or talk to someone?
You can discuss the idea here on the list, or if you want you can put together a proposal doc and add that to an issue in Jira depending on what works best for you. I think most people here are quite open to ideas when it comes to how the UI is managed longer term (v2.0?), so kicking off that discussion would be good. Though I think for now the emphasis is on having a reasonably feature-complete application. > I really think jsps are > not the way but rather json to HTML conversion using something like pure > js. The idea is to provide a data model apply HTML templates, generate HTML > and them apply styles. OK, so is basically the idea to work primarily on the API, and then the front end UI is just another client? I like the toolkit idea for making theming easier - I guess something similar to Twitter Bootstrap? > The styles should be designed like a toolkit (dojo, > extjs) widgets .menu .ui-button rather than #nav .nav-item. This way > clients can easily theme the portal, change the markup, and upgrade easily. > I am away on vacation for 1.5 weeks then ready to contribute. I will write > up the design and submit it then. I dont won't to be counter productive > with other peoples work do if there is someone I should contact just let me > know. Great! As for how it affects other work, thats for the community to feed back on - as I said above I can't see Rave accepting a major change to how the UI is managed immediately, but we do need the UI to be easily themed and customised, and longer term I think the options are still open for how we can best do that. My personal interest is in the API for export and import of pages between different instances of Rave or between Rave and other platforms such as iGoogle (e.g. GadgetTabML) and LifeRay. The project I work on (OMELETTE) has starting working on a spec for this use case, we're just discussing now how we might take that forward in a more open way. But I think thats a different semi-related discussion. > > Cheers from switzerland > Jose > > On Monday, January 23, 2012, Scott Wilson (Commented) (JIRA) < > [email protected]> wrote: >> >> [ https://issues.apache.org/jira/browse/RAVE-256?n to hrml > page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191220#comment-13191220 > ] >> >> Scott Wilson commented on RAVE-256: >> ----------------------------------- >> >> Yes you're correct - currently the page export model uses JAXB > annotations on some parts of the model rather than the whole model. I saw > the model on RAVE-26 comments and we should definitely work together on > this one. >> >>> As a user I want to export a page model so that I can use it elsewhere >>> ---------------------------------------------------------------------- >>> >>> Key: RAVE-256 >>> URL: https://issues.apache.org/jira/browse/RAVE-256 >>> Project: Rave >>> Issue Type: Story >>> Reporter: Scott Wilson >>> Assignee: Scott Wilson >>> Fix For: 0.4-INCUBATING >>> >>> >>> This is the capability to export a page model using a representation > such as XML or JSON, for example for importing into another Rave server, or > to submit it to a "workspace registry" (see RAVE-26). The exported page > would include the region, layout and widgets, but not any user data or > preferences, so it would function more as a template than an archive. >> >> -- >> 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 >> >> >>
