Hi, I also prefer not to have a dialog box to enter element name, type etc. Instead we can use sub context menu to select "add records", "add record arrays" and "add fields" etc. If there are any additional parameters to be configured for a particular element we can use eclipse's default properties view to configure those parameters. For an example get the "Not Null" property suggested by Isabelle. We can put this "Not Null" parameter in the eclipse default properties view to select the desired value (true or false) for a particular element.
Please have a look at Eclipse's "Sample Ecore Model Editor" which is used to develop Ecore model graphically. It allows users to build a tree graphically and generates a schema according to the developed tree model. It has a very convenient and simple methodology to build the tree graphically. How we are going to serialize this graphical tree into an Avro schema ? Are we going to use any existing library or are we going to write a library on our own ? Thanks, Viraj. On Thu, Apr 10, 2014 at 11:04 PM, Isabelle Mauny <[email protected]> wrote: > All, > > I think Not Null with a checkbox works out. Pretty standard in SQL tools. > > Isabelle. > > > ------------------------------------------------------------------------------------- > *Isabelle Mauny* > Director, Product Management; WSO2, Inc.; http://wso2.com/ > email: [email protected] - mobile (Spain) : +34 616050684 - mobile (Sri > Lanka) +94 (0)774777663 > Landline: +1 (650) 745 4499 (USA) or +94 (11) 214 534 (SL) Extension : > 7302 > > > On Thu, Apr 10, 2014 at 2:15 PM, Gayan Yalpathwala <[email protected]>wrote: > >> Hi Susinda, >> >> >> On Thu, Apr 10, 2014 at 4:53 PM, Susinda Perera <[email protected]> wrote: >> >>> Hi Gayan >>> >>> Don't we represent this nullable and nillable check-boxes with some user >>> understandable captions. These are xml/avro schema jargon and IMO these >>> need to be replaced with something more meaningful for user. >>> >> >> We can change nillable to "Allow empty values" and nullable to "Value can >> be null". WDYT? >> >> >>> >>> Thanks >>> >>> >>> >>> On Thu, Apr 10, 2014 at 3:26 PM, Gayan Yalpathwala <[email protected]>wrote: >>> >>>> 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/> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Susinda Perera* >>> Software Engineer >>> Mobile:(+94)716049075 >>> >>> WSO2 Inc. http://wso2.com/ >>> Tel : 94 11 214 5345 Fax :94 11 2145300 >>> >>> >>> _______________________________________________ >>> 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/> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068
<<inline: New element dialog.png>>
<<inline: Right-click menu2.png>>
<<inline: Right-click menu1.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
