If you've created a symbol for BeepingTransition, you must have successfully created the type, so I guess you've either cleared the name field or then are trying to create a new type with no name.

 

The Digital Watch WatchApplication language specifies the actions that should happen during a Transition by attaching an Action object to the Transition. The various actions can then be connected to that Action object, e.g. an Icon action is connected to the Action with an Icon relationship. If you follow that pattern, life is pretty easy:

 

You can just create a Beep object, Beep relationship and Beep role and a binding for them (with ActionBody role to the Action), then make a _Beep generator that produces the Java code needed to beep, e.g. just

 

Report '_Beep'

'beep();'

endreport

 

I wouldn't suggest making BeepingTransition as a subtype, because then if a user draws a Transition (with all its Buttons and Actions attached), and later decides it should beep, he'll have to delete the Transition and draw it again as a BeepingTransition.

 

An alternative might be to add a Boolean 'Beep?' property to Transition. That would allow the user to change later whether to beep or not on that transition. The downside would be an extra dialog whenever a Transition was created, because now there will be properties that could be filled in. You'd also have to work harder to make the code generator and update the framework, because the existing framework only supports Actions attached to Action objects, not directly on the Transition. You'd need to change the _TransitionData generator to add a new bool beep parameter, and update the framework to use it: add the beep bool to AbstractWatchApplication's addTransition(), add the beep bool to the Result class, and change AbstractWatchApplication's handleEvent() to beep as well as perform the Actions:

 

if (result.action != 0) perform(result.action);

if (result.beep) beep();

 

Have you done the http://www.metacase.com/support/45/manuals/evaltut/et-Preface_.html - 'Family Tree' Evaluation Tutorial ? If not, that's the best way to learn the concepts and tools of MetaEdit+.

 

ii) No, that's not what I meant. Or indeed what I said . Maybe you want to slow down a bit, and if things don't seem to show what you expected, make sure you've read the earlier answers correctly. I don't mind answering again, I just don't want you to have to waste your time waiting for us to answer.

 

The binding you have added is a new kind of transition from a State to a State, but that's not what you want. Instead, you want to be able to draw a line from an Action to a Beep, in a similar way to the current Icon binding. At least I suggest you do it this way first, as the watch language supports easy addition of new kinds of actions - once you can do that successfully, you can think about the alternatives, like parameterizing transitions with a property.

You don't need to create a new binding for it, because WatchApplication already includes a binding for Transition, and BeepingTransition is legal in that binding by inheritance.

 

In the generators you'll need to check any places that refer to Transition, and make them allow BeepingTransition too. E.g. if the generator has

 

foreach >Transition

 

You can replace that with

 

foreach >(Transition | BeepingTransition)

 

or indeed with a wildcard match

 

foreach >(*Transition)

 

That will make your BeepingTransitions work as Transitions, but you also need to extend the generators and framework so that they remember to beep for each BeepingTransition. You'd need to change the _TransitionData generator to add a new bool beep parameter, and update the framework to use it: add the beep bool to AbstractWatchApplication's addTransition(), add the beep bool to the Result class, and change AbstractWatchApplication's handleEvent() to beep as well as perform the Actions:

 

You can find the domain framework classes from the "Language Frameworks" properties of the 2012Models: WatchFamily model. There are two frameworks, C# and Java, and within each are all its domain framework classes -"Framework Components". Some of the classes are there multiple times, e.g. for different versions for WPF vs. WP7. Adding beeping transitions probably affects all the different versions.

 

In a Framework Component's Source Code text property, you can choose Editor from the pop-up menu to open the source in a larger window.