Fig 1 : execution flow of a page that has one unit (X) in a web app that has three Units (X, Y , Z)
On Sun, Jul 13, 2014 at 9:05 PM, Manuranga Perera <[email protected]> wrote: > Summary of what has been discussed so far on $subject > > *Features* > > *Self Contained Units* - Each with backend logic / HTML / routes > > *Unit Composition* - Create new units out of existing ones > > *Declarative manifestation* - Units can specify where it should appear > (as opposed to composition) > > *Separated layouts* - Bootstrap compatible HTML layout with placeholders > for Zones that units can appear > > *Unit intercommunication* - A Unit can manipulate input data of any other > unit in the system. > > > *Implementation * > > Each unit is a combination of following > > *Controller* - a javascript file. get executed when the http URL is > requested, if the given Unit appears in the page. creates the viewmodel (a > json data object). > > *View* - a jag file. renders HTML when the execution reach the > placeholder in the layout. use the data in the viewmodel to get dynamic > data. > > *Association Logic *- a javascript file. gets executed for every request. > responsible for pushing data to other units. > *Definition* - a json file. specifies the routers and zones the current > Unit will appear > > > > > Fig 1 : execution flow of a page that has one unit (X) in a web app that > has three Units (X, Y , Z) > > > > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
