Hmm! Yes, I would not want the common classes to be generated into my project because they've already been generated in the common project. From looking at the Sculptor code, it appears that when someone uses an "import" statement, the elements from that design file get merged into my project's scope. Is there a way to tell the objects apart? Like maybe in DslTransformation template where there's a method for "importModel", can we tag the imported objects with a flag? Because then we can change the templates to skip generating those imported objects. It still may not be easy, but at least we'd be able to tell them apart.
I'll check on the oAW forums for more information about their "import" facility. It's hard to follow what they're saying though. oAW just has a really steep learning curve. So if you have any insight or inspiration, please let me know. :) Thanks, Polly Patrik Nordwall wrote: > > Most of these problems are probably related to limitations in the oAW > import mechanism. Search oAW forum and you will probably find similar > questions and answers. > > However, one major thing is that Sculptor is currently not designed for > this kind of cross project imports. When you import the common stuff in > the app project the classes from common will be generated in the app > project (in each app project that are using the common stuff). That kind > of duplication is probably not what you would like? I understand why you > would like to separate the common stuff in a separate project, but it is > currently not supported. I don't know how to solve this right now. Any > suggestions, anyone? > > /Patrik > -- View this message in context: http://www.nabble.com/-Sculptor--problems-importing-design-files-tp20236014s17564p20248661.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
