yeah, cool stuff
I advise. Install wtp eclipse, install the Graphical modeling framework from
eclipse. start playing with EMF and GMF.
I am committing a plugin based on JET in the next week to the slide tools.
but just to get started with JET
create a new plugin project.
new->other->convert project to jet project
set your jet properties so the source folder is your src folder in the
project
drop a jet file in and see how it creates the java code for you
if using a custom model make sure the custom model is in the same class
path.
to invoke your JET template
use the first batch of code below
sit back, gape for 15 minutes and then check out EMF, then GMF. become an
insomniac.
On Mon, Aug 11, 2008 at 10:13 AM, Niels Wolf
<[EMAIL PROTECTED]>wrote:
> This looks actually really nice.. Does anybody has more resources on this
> flax/flash + JET?
>
>
>
> On 8/7/08 12:21 PM, "Johannes Nel" <[EMAIL PROTECTED]> wrote:
>
> also, does anyone else use emf for modeling and has anyone tied this up to
> custom jet templates?
>
> On Thu, Aug 7, 2008 at 12:09 PM, Johannes Nel <[EMAIL PROTECTED]>
> wrote:
>
> Hi All
>
> Don't know who uses JET but I would like to outline how I have been using
> it and asking people how they use it after that.
>
> At the moment what i do
> 1. Convert my project to a JET project
> 2. Set my JET source path = my plugin.src
> thus when i create my jet template, i get the template.java in my source
> path, which I then invoke via
> SlideViewPresentationModel emitter = new
> SlideViewPresentationModel();
> String result = emitter.generate(sv);
> where sv is a custom model of the type SlideView.
>
> My reason behind this was that I had so many problems using dynamic
> templates which i would invoke
> ClassLoader loader = getClass().getClassLoader();
> JETEmitter emitter = new JETEmitter(uri,loader);
> emitter.addVariable("Slide", pluginId);
> String result = emitter.generate(monitor,new Object[]{sv});
> not only due to the dynamic models which I use (solved via the custom
> classLoader) but also templates which would then output the template.java to
> my eclipse workspace .JETEmitter project and cannot be compiled from there
> (event though I had all the necesary variables). Its not that it did not
> work, but it only worked once (when the template is compiled and you create
> the new emitter it cannot override existing files!) and at other times
> pretty infrequently when i played around with settings.
>
> So the bad part of this is that I cannot update templates on the fly
> without updating the plugin, i can also not thus have a user output a
> template from the plugin - one level of abstraction too many anyway IMO.
>
> So how do other people use Jet in their plugins?
>
> Also swt sucks, big time, so slow to develop. I am considering using a
> socket to just speak to a flex app. I have concerns around the plugin
> activator livecycle and a socket, but need to do more research on this, any
> thoughts?
>
> Also has anyone polled the flex builder api for information and if so, can
> they give me a heads up around performance, my first touches on inspecting
> the availible object model went badly (you always get the whole object tree,
> no way to filter that I could figure out first off).
>
> As you can see I am a noob with plugin development and on top of that do
> not consider myself very good at java.
>
> I would like to get people who have been down some of these roads before to
> tell me what has worked and what not ideally.
>
> johan
>
>
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
--
j:pn
\\no comment
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
