+1 for keep zip format, We can use unique extension and pretend it as a single file (if required) , (AFAIK Microsft ".docx" also zip format we can do something smiler ).
/Jasintha On Wed, Apr 2, 2014 at 1:35 PM, Srinath Perera <[email protected]> wrote: > Since visual editor is the only way we let people edit the mapping file, I > am +1 have a zip file containing all the files. > > --Srinath > > > On Wed, Apr 2, 2014 at 1:21 PM, Melan Nimesh <[email protected]> wrote: > >> >> Hi, >> >> On Wed, Apr 2, 2014 at 12:34 PM, Gayan Yalpathwala <[email protected]>wrote: >> >>> Hi, >>> >>> Data-mapper configuration file that is generated from the tool is >>> currently saved in .js (javascript) extension which is planned to be >>> changed to an abstract file type (Let's say .mapconfig). This is mainly >>> because, user does not need to be aware that the configuration is in >>> javascript since we are not going to support reverse-engineering for manual >>> changes done in the file. >>> >> >> +1 to this approach. >> >> >>> >>> Additionally, in order to populate data-mapper editor in developer >>> studio, two other files (.datamapper and .datamapper_diagram) are generated >>> automatically. These files are not known to the user yet they are >>> compulsory to be present in the system to generate the design view. >>> >> >> is there any specific reason to maintain two files (.datamapper and >> .datamapper_diagram) ?, There's an option in GMF to use same file for >> diagram and model in order to keep it simple >> >> >> >>> >>> This becomes a concern when analyzing use case of 'importing an existing >>> configuration from the file system'. Here, user browsing a xxx.mapconfig >>> file from file system will not be sufficient as other two files are >>> missing. What if we can come up with a compound file type which is >>> obviously a zip type including .mapconfig, .datamapper and >>> .datamapper_diagram in it? I hope this will solve the above problem as user >>> can point the compound file directly. >>> >> >> .mapconfig generates from .datamapper (model) file, right? so it's >> redundancy. I guess it's better to generate .mapconfig when needed (such >> as artifact exporting, deploying,etc ) >> >> >> >>> >>> 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 >>> >>> >> >> >> -- >> *Melan Nimesh* >> Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: melan AT wso2.com; >> Mobile: +94 77 631 6759 >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > ============================ > Srinath Perera, Ph.D. > http://people.apache.org/~hemapani/ > http://srinathsview.blogspot.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
