Maybe it is a deployment model is it?
On Tue, Jun 25, 2013 at 11:46 AM, Danushka Menikkumbura < [email protected]> wrote: > +1. > > How would you use shared JS libraries in this boilerplate BTW?. > > Cheers, > Danushka > > > On Tue, Jun 25, 2013 at 11:36 AM, Subho Banerjee <[email protected]>wrote: > >> I would like to suggest a slightly different layout. Particularly because >> the logic for the UI for Workflow composition and Workflow composition >> itself in HTML are not seperate. Also, I am following the HTML5 >> Boilerplate >> to structure my front end code[1], so this means that code which I write >> for the workflow composition UI is structured as follows - >> >> /:. >> ├───index.html >> ├───css >> └───vendor >> ├───doc >> ├───img >> └───js >> ├───vendor >> ├───model >> └───controlers >> >> Now, the js folder contains all the front end logic for the UI as well as >> workflow composition. I would suggest that we follow this structure and >> not >> further subdivide the web UI module. In which case, we can reuse objects >> in >> between the various web-ui sub-projects. >> >> Cheers, >> Subho. >> >> >> [1] http://html5boilerplate.com/ >> >> >> On Mon, Jun 24, 2013 at 11:47 PM, Danushka Menikkumbura < >> [email protected]> wrote: >> >> > Hi Suresh, >> > >> > I think we need to have the following structure. >> > >> > 1. web-gui (xbaya-web-ui?) - The Web UI would be a top-level module, >> under >> > which we may have the following sub modules. >> > >> > - ui (Widgets, graph, canvases, etc) >> > - workflow (Workflow composition, execution) >> > - monitor (Workflow monitoring) >> > - protocol (XML/JSON protocol conversion module) >> > >> > 2. ws-messenger.client.protocol.amqp - AMQP client API bits >> > >> > 3. xbaya-gui.ui - AMQP configuration + monitoring. >> > >> > Sanchit, Shameera, Subho, Vijayendra and Viknes, what do you think?. >> > >> > Thanks, >> > Danushka >> > >> > >> > >> > On Sun, Jun 23, 2013 at 6:16 PM, Suresh Marru <[email protected]> >> wrote: >> > >> > > Hi All, >> > > >> > > Please discuss how should we structure the SVN repo for gsoc projects? >> > > certainly not by student since every one is contributing to master >> > project. >> > > So may be the functional components? >> > > >> > > I created a sandbox area, please discuss how individual modules >> should be >> > > organized and please create JIRA's and submit patches to this repo. >> > > >> > > https://svn.apache.org/repos/asf/airavata/sandbox/gsoc2013 >> > > >> > > Suresh >> > > >> > > >> > >> > >
