I'm turning this in to a broader sail discussion so I took it off
otrunk-dev list.
I commented on the questions below. However after doing that, and
thinking about our sail-tels-loops discussions over the past 2 weeks.
It would be good to consider starting to use the OTrunk view system. It
is this view system that typically takes care of these questions asked
below for UDL. So if TELS/Pas eventually moves to the OTrunk view
system then any effort put into doing it without the view system would
be wasted.
I think any move to the OTrunk view system should be made in a backward
compatible way. This will result in more complicated code than a
complete reimplementation. However the backward compatible approach
will be less disruptive and in the end require less energy from leaders,
developers, and users.
In that context I have to make a choice.
Do I investigate the changes needed to move to the otrunk view system? or
Do I move forward with rim and sock support when running the steps under
OTrunk?
Currently I think I will stick with my original goal of the rim and sock
support.
Scott
Anthony Perritano wrote:
> Hi,
>
> I have two otrunk questions.
>
> 1. I would like for the user to click on a button to preview the
> curnit that they are working. Is there a facility in OTrunk where i
> can do this easily with my bean structure? the way that i see off hand
> to preview is with EMF Launcher2
>
> File dummyFile = new File("dummy.txt");
>
>
> URL contextUrl = dummyFile.toURL();
> URL configUrl = new URL(contextUrl, path);
>
>
> ArrayList<Bundle> standardBundles = new ArrayList<Bundle>();
>
>
> EMFBundleAnnotationService annotationServiceBundle =
> new EMFBundleAnnotationService();
> standardBundles.add(annotationServiceBundle);
>
>
> BundleLauncher.launch(configUrl, (ICurnitProvider)null, standardBundles);
>
> would this the path i need to go down?
This doesn't have a clear solution. You can try to use the
BundleLauncher to launch the preview. You will need to use a config
file that is similar to the one you are using to test the
OTrunkCurnits. I think you will run into problems though, but it is
worthwhile to figure out what those problems are.
>
> 2. We had something in Pas Authoring called live preview, as you
> changed the bean properties it updated an open vle on the fly. would
> this also be possible with otrunk? if so what steps would i need to
> take to develop this?
This also doesn't have a clear solution. You need to share data
between the authoring and the preview. This can be done by having each
of them access the same java objects. And then there needs to
notifications of changes, so the preview updates when the author changes
things.
I can think of 2 ways to handle the data model for this:
1. The common java objects can be the OTObjects. Then you will have 2
sets of "bean" or "realObjects" for one set of OTObjects. The
OTObjects have an event system, so your controllers can listen for
changes in the OTObjects and then update the realObjects when those
changes happen. This might also require the realObjects (Pas steps...)
to be able to update the JComponents that they are displaying.
2. The common java objects can be the beans themselves. Then you would
just have one set of "bean" or "realObjects" objects. I'm not familiar
enough with the Pas runtime and authoring system, to know if it can
handle having the same bean be used for authoring and running. One
problem I can imagine are the bean context. A bean can only be part of
one bean context at a time. And from the previous problems it seems at
runtime the bean has to be a member of the of the same bean context as
the used by the PasProject.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---
