You are right. The manual steps you describe are unfortunately needed right now. We had problems getting dynamic ecore model to work for the gui dsl and therefore we use the static (generated) ecore. It is an ugly workaround and I hope we can get it right when migrating to TMF Xtext.
Please update documentation. /Patrik PaloT wrote: > > Hello, > I found that after changing sculptordsl.xtxt in dsl project and > running generate.oaw I have to manually copy sculptordsl.ecore from > dsl project to gui.dsl project, open sculptorguidsl.genmodel and > regenerate Java classes (with right click and 'Generate model code'). > Am I missing something what is doing this automatically? If not, > should I rewrite chapter about adding new concept in dev > documentation? > > Regards > > Pavel > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Fornax-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fornax-developer > > -- View this message in context: http://www.nabble.com/Changing-sculptordsl.xtxt-tp24920634s17564p24957143.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
