Hi Jasintha,
On Thu, Apr 10, 2014 at 2:14 PM, Jasintha Dasanayake <[email protected]>wrote: > > > > On Wed, Apr 9, 2014 at 12:40 PM, Gayan Yalpathwala <[email protected]>wrote: > >> Hi, >> >> Visual data mapper currently operates by taking two avro schemas for >> input and output. Considering the fact that end users are not supposed to >> write avro schema by themselves, we have decided to provide a UI to >> manually build the schema of input and output. This will basically extend >> the current input and output boxes implementation in data-mapper editor. >> >> Users can build the schema from scratch and add a new element by choosing >> the option provided in right click menu. >> >> [image: Inline image 2] >> >> This will pop up the following dialog asking user input for element name >> and respective attributes. >> >> [image: Inline image 4] >> >> Here, Element type combo box will list all primitive types supported by >> avro. Eg:- STRING, INT, DOUBLE etc. >> >> The element added will appear as the root node of a tree structure and >> user can add more elements by choosing either "Add new child" or "Add new >> sibling" options from right click menu. These two options will be available >> for every element added further. >> >> [image: Inline image 3] >> > > I think it's better to have a option in this menu, to import existing > types(Avro types), and provide a edit option to change the data type of the > existing element. Also I personally preferred to have another sub context > menu which provide following 3 items > 1) create record element > 2) create record list element > 3) create a field element > +1 for this approach. What if the first menu item be "Add new" and three options (record element, records list element, field) in its sub context menu? This way, we can get rid of "Add new sibling" menu item and introduce a second menu item to import existing types instead. > > I think this option might be simple and easy for users rather having a > complex dialog and ask to define those information , WDYT ? > > /Jasintha > > > >> A user can use this method to build a complete schema without having any >> idea about the underlying avro schema specification. >> >> Please raise and forward if you have any thoughts and concerns on design >> aspects and the flow that I have mentioned. >> >> Thanks, >> >> >> -- >> *Gayan Kaushalya Yalpathwala* >> Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 71 8682704 <http://asia14.wso2con.com/> >> >> <http://asia14.wso2con.com/> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > *Jasintha Dasanayake * > > > *Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/> lean . > enterprise . middleware* > > > *mobile :- 0711368118* > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > Thanks, -- *Gayan Kaushalya Yalpathwala* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 8682704 <http://asia14.wso2con.com/> <http://asia14.wso2con.com/>
<<inline: Right-click menu2.png>>
<<inline: New element dialog.png>>
<<inline: Right-click menu1.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
