Changes

31 bytes added ,  12:36, 3 April 2009
no edit summary
Line 69: Line 69:  
==== Technical Approach ====  
 
==== Technical Approach ====  
 
Below is the rough draft, it talks about the implementation in abstract way just to share the idea of implementation.
 
Below is the rough draft, it talks about the implementation in abstract way just to share the idea of implementation.
:[[Image:marbles-flowchart.png|left| Marlbes-development environment.]]<br>
+
:[[Image:marbles-flowchart.png|left| Marlbes-development environment.]]
      −
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
+
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
 
Here visual UI representations gives an option to select widgets, authoring tool will assist the users to place the widgets on frame and also do some prechecks on UI widget compatibility.Program generator then generates the optimized code based on UI types, positions and associates event handlers to the widgets. Views should be handled independently and it includes final checks on widgets too. History generation is being done side by side to facilitate recoveries if error occurs and finally, output generation ( both UI and code output ) . Code output from the software will be stored in specific directories or in database.
 
Here visual UI representations gives an option to select widgets, authoring tool will assist the users to place the widgets on frame and also do some prechecks on UI widget compatibility.Program generator then generates the optimized code based on UI types, positions and associates event handlers to the widgets. Views should be handled independently and it includes final checks on widgets too. History generation is being done side by side to facilitate recoveries if error occurs and finally, output generation ( both UI and code output ) . Code output from the software will be stored in specific directories or in database.
   Line 80: Line 80:  
#*Fields: Widget id,name,label,icon, height, width, position,parent_container id ,visible,focus-type, param1,param2
 
#*Fields: Widget id,name,label,icon, height, width, position,parent_container id ,visible,focus-type, param1,param2
 
#*Widget table will contain widget id , it's name,label,positional parameters, id to its paraent container, and other parameters specific to <br/>
 
#*Widget table will contain widget id , it's name,label,positional parameters, id to its paraent container, and other parameters specific to <br/>
widget functionality like for checkbox we could have parameters like "default check". This table includes all type of widgets like containers, <br/>
+
widget functionality like for checkbox we could have parameters like "default check". This table includes all type of widgets like containers,<br/>
 
menu, buttons, checkbox etc<br/>
 
menu, buttons, checkbox etc<br/>
 
#Events
 
#Events
122

edits