Tim,
There is no embeddedHandler part. Rather, a topic describes use of a
variable (named embeddedHandler in the example). That variable is based
on another Rich UI handler.
Here is the most recent content, from
http://www.ibm.com/software/rational/cafe/docs/DOC-2689 .
Regards, Saul Ben Margolis
***********************
You can use multiple Rich UI handler parts to compose a single
application. However, we do not mean to say that you embed one handler
part in another. Instead, the handler part declares variables that are
each based on another handler part. A variable based on an Rich UI handler
part is called an embedded handler, as in the following example:
embeddedHandler AnotherHandlerPart{}; // declared Rich UI handler
(based on part
AnotherHandlerPart)
The embedding Rich UI handler can access the global widgets and public
functions declared in an embedded Rich UI handler. In particular, the
embedding handler can add widgets to its own initialUI and children
arrays. Also, you can embed a handler that invokes services or otherwise
handles business processing. A reasonable practice is to use one handler
to present the UI and to use other handlers to oversee the backend,
business processing.
You access widgets and functions with a dot syntax. In the following
outline, the Handler part AnotherHandlerPart is assumed to have declared a
button named itsButton, which is attached to the DOM tree only when that
button is included in the initialUI array of the embedding handler:
handler SimpleHandler type RUIHandler { initialUI = [
embeddedHandler.itsButton ] }
embeddedHandler AnotherHandlerPart{};
end
Similarly, you can add an embedded widget to a children array.
You can access a function or property in an embedded widget by extending
the a dot syntax. For example, the following statement retrieves the
displayed text of the embedded Button itsButton:
myString STRING = embeddedHandler.itsButton.text;
The initialUI array of the embedded handler has no effect at run time.
That array is used only when the embedded handler is the basis of a Rich
UI application and is not embedded at all.
egl-i-request@xxxxxxxxxxxx
Sent by: egl-i-bounces@xxxxxxxxxxxx
01/22/2009 01:00 PM
Please respond to
egl-i@xxxxxxxxxxxx
To
egl-i@xxxxxxxxxxxx
cc
Subject
EGL-i Digest, Vol 2, Issue 6
Send EGL-i mailing list submissions to
egl-i@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/egl-i
or, via email, send a message with subject or body 'help' to
egl-i-request@xxxxxxxxxxxx
You can reach the person managing the list at
egl-i-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of EGL-i digest..."
Today's Topics:
1. embeddedHandler question (tim)
----------------------------------------------------------------------
message: 1
date: Thu, 22 Jan 2009 11:17:40 -0500
from: "tim" <tim2006@xxxxxxxxxxx>
subject: [EGL-i] embeddedHandler question
Has anyone used this part yet. Im looking for a why and how on this. I am
creating rui projects with multi RUIHandler's. Should I be using the
embeddedhandler instead?
------------------------------
_______________________________________________
EGL-i mailing list
EGL-i@xxxxxxxxxxxx
http://lists.midrange.com/mailman/listinfo/egl-i
End of EGL-i Digest, Vol 2, Issue 6
***********************************
midrange.com
