Hi Iresha, This proposal looks good. Specially the UI proposed for RXT configuration is a huge usability improvement. Could you please add the sample JSON format you proposed in the mailing list to the proposal as well?
Thanks On Fri, Mar 14, 2014 at 2:51 PM, Iresha Udayangani <[email protected]>wrote: > Hi all, > > I have created a draft proposal for the project. Please find the document > in [1]. It would be greatly helpful for me if you could provide me with > some feedback so that I could improve it in next couple of days. > > [1] > https://docs.google.com/document/d/1WzRicvDTOjINU4zm9txzJRpftF-Tfr_e6YezSHGtvkc/edit?usp=sharing > > Thanks, > Iresha > > > On Tue, Mar 11, 2014 at 9:24 PM, Iresha Udayangani <[email protected]>wrote: > >> Hi all, >> >> Thank you for your replies. I was able to create a sample JSON file >> which can be used instead of the current XML file (attached). The >> current default rxt in the Artifact Source editor can be replaced by >> something similar to the above. >> >> I also went through org.wso2.carbon.governance.generic and >> org.wso2.carbon.governance.generic.ui components in governance and >> seems like it's the best starting point to look at the code. As far as I >> could understand, the java classes corresponding jsp files needs to be >> modified in order to facilitate using json instead of xml. >> >> The XML parsing done through axiom needs to be replaced by a new JSON >> parser. As mentioned in the [4] above, the new json based >> implementation could facilitate adding a new artifact type inside >> another artifact. I could understand how a new artifact can be added >> inside an existing json file of an artifact, but I'm not very much >> sure how to implement it in the code level. >> >> Please let me know what are the other aspects of the project which I >> could look at in order to get an overall idea of the project. I will >> upload a draft proposal in couple of days. >> >> Thanks, >> Iresha >> >> >> >> On Mon, Mar 10, 2014 at 7:39 AM, Eranda Sooriyabandara >> <[email protected]>wrote: >> >>> Hi Iresha, >>> The deliverables to this project would be, >>> >>> 1. A jason configuration for replacing current RXT configuration model >>> 2. Plug that model to the existing UI generator model (This should be >>> refactor or replace our old UI generator) >>> 3. Plug that model to the existing Governance API >>> 4. Implementing nested RXT support - Currently we only allow to have >>> basic data support in field. But we need to improve this to define another >>> datatype inside a datatype. I'll explain this in detail later. >>> >>> thanks >>> Eranda >>> >>> >>> On Fri, Mar 7, 2014 at 11:01 AM, Iresha Udayangani >>> <[email protected]>wrote: >>> >>>> Hi all, >>>> >>>> >>>> I'm Iresha Udayangani, a 3rd year undergraduate of department of >>>> Electronic and Telecommunication Engineering, University of Moratuwa, >>>> Sri Lanka. I went through the list of WSO2 project ideas for GSOC >>>> >>>> 2014. Proposal 1: Implement Registry Extension (RXT) 2.0 + Associated >>>> >>>> UI support seemed to be quite interesting and match my past >>>> experiences. >>>> >>>> I was able to download wso2greg-4.6.0, then run it. I went through >>>> some of the reference documents/webinars and uploaded a couple of rxt >>>> files(person.rxt, project.rxt) in Extensions->Artifact Types ->Add new >>>> Artifacts and got familiar with their functionality. >>>> >>>> As far as I can understand the project expects the following, >>>> >>>> [1] A new RXT format should be defined using JSON, instead of the >>>> current XML Structure, so that existing JSPs might need few >>>> alterations in order to render UIs based on the new JSON format. >>>> JSON seems to be more efficient and browser friendly compared to XML. >>>> >>>> [2] Instead of user manually configuring/creating the XML structure >>>> (RXT definition) the project expects to automatically generate the RXT >>>> definition from a UI template. >>>> >>>> [3] When adding a new Artifact type, user can be provided with a new >>>> UI where it contains basic fields to be filled (such as artifactType, >>>> singularLabel, pluralLabel, storagePath etc. ) and few custom elements >>>> (to add UI columns, content fields) instead of the current XML editor, >>>> where user needs a bit of programming background to configure things. >>>> After the user successfully configured the new artifact, the RXT >>>> format can be generated using the information provided in the previous >>>> step. An editor can be provided for the advanced users as well. >>>> >>>> I'm a bit struggling in understanding some of the project >>>> deliverables and trying to find the code samples, where it needs to be >>>> modified. It would be much helpful if anyone could help me out with >>>> more details. >>>> >>>> Thanks, >>>> Iresha. >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> *Eranda Sooriyabandara*Senior Software Engineer; >>> Integration Technologies Team; >>> WSO2 Inc.; http://wso2.com >>> Lean . Enterprise . Middleware >>> >>> E-mail: eranda AT wso2.com >>> Mobile: +94 716 472 816 >>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >>> Blog: http://emsooriyabandara.blogspot.com/ >>> >>> >>> >>> >>> >> >> >> -- >> Iresha Udayangani >> Undergraduate , >> Department of Electronic & Telecommunication, >> University Of Moratuwa. >> >> > > > -- > Iresha Udayangani > Undergraduate , > Department of Electronic & Telecommunication, > University Of Moratuwa. > > -- *Shelan Perera* Senior Software Engineer Integration Technology Group *WSO2, Inc. : wso2.com <http://wso2.com>* lean.enterprise.middleware. *Blog* : blog.shelan.org *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* : https://twitter.com/#!/shelan *Mobile* : +94 772 604 402
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
