> Hi, > > I suggest each technology provides a demo similar to Kai's, in the > "spirit" of each technology. E.g. when using the toolkit model + > javascript support, it's natural to implement the contact list and > contact class using EMF. The demo should be part of a separate examples > project specific for each technology, that may be imported and tried out > by the others. E.g. tm has a org.eclipse.e4.tm.examples project with an > almost-finished library demo and just-started contacts demo.
My concern is to have one entry point for outside users. yves > > BTW, I don't think we should require that the demo is a complete RCP > application, because the packaging as an RCP application is fairly > independent of the UI technology. E.g. the demo could just be a special > editor with views, or a file that may be opened with a special editor > with supporting views. > > Hallvard > > [email protected] wrote: >> Hi All, >> >> I have integrated XWT in Kai's contact demo. The patch is published >> here: >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=279047 >> >> I wonder how to integrated it in CVS. I see two possibilities: >> 1. each one technology forks the project and creates a new version >> 2. All in one with a switch. >> >> My preference is 2. >> >> Regards >> Yves >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
