Home » Archived » Test and Performance Tools Platform (TPTP) » Select items by name in AGR macro
| Select items by name in AGR macro [message #66176] |
Wed, 12 April 2006 12:58  |
Eclipse User |
|
|
|
Originally posted by: vladimir.au.ru
Al items in my generated script selected by their number.
For instance:
<command type="item-select" contextId="wizard-page/moduleSelection"
widgetId="org.eclipse.swt.widgets.Tree#1">
<item
path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||0| "/>
<item
path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||1| "/>
<item
path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||2| "/>
<item
path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||3| "/>
</command>
You can see, that items selected by their position in the tree. But if the
tree has changed, the script become invalid. Is it possible to select
items by name?
Thanks,
Vladimir.
|
|
| | |
| Re: Select items by name in AGR macro [message #66701 is a reply to message #66530] |
Fri, 14 April 2006 13:06  |
 Barbara Rosi-Schwartz
Messages: 448
Registered: July 2009 |
Senior Member |
|
|
Ali Mehregani wrote:
> In fact I strongly recommend for users to use custom widget resolvers.
> There are a few defects and features open to make the widget resolving
> mechanism more robust but until they're implemented, users are encouraged to
> use their own custom widget resolvers.
>
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=112634 (feature)
> and https://bugs.eclipse.org/bugs/show_bug.cgi?id=128271 (defect)
>
> Thanks.
>
> "Vladimir" <vladimir@au.ru> wrote in message
> news:a8fb3016767df645cc88239e4b556d24$1@www.eclipse.org...
>> Al items in my generated script selected by their number.
>> For instance:
>> <command type="item-select" contextId="wizard-page/moduleSelection"
>> widgetId="org.eclipse.swt.widgets.Tree#1">
>> <item
>> path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||0| "/>
>> <item
>> path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||1| "/>
>> <item
>> path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||2| "/>
>> <item
>> path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||3| "/>
>> </command>
>>
>> You can see, that items selected by their position in the tree. But if the
>> tree has changed, the script become invalid. Is it possible to select
>> items by name?
>>
>> Thanks,
>> Vladimir.
>>
>
>
Ali,
I have re-read the manual on this subject and I must admit I now have
more questions than answers. Could you possibly enlighten me?
1) As I understand it, I have two ways of improving on recognition:
either by defining my own widget resolver and add it by an extension
point or by adding <class> elements to the widgetReg.xml file that you
provide. Is this accurate?
2) If item 1) is correct, which one of the two routes is the recommended
one?
3) I am not clear how and where to define my extension point. Is it in
the manifest of my test plugins? If so, when I try to add an extension
point using the standard manifest editor (Extensions editor tab), the
org.eclipse.tptp.test.auto.gui.widgetResolver extension point does not
appear in the list of possible extension points. Could you possibly
provide a snippet showing how the extension point is defined in the
plugin.xml file so that I can enter it by hand?
4) If I go the custom widget resolver class route, I don't understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example implementation?
A similar question applies to the addition of <class> elements to the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
5) How does the connection happen between the custom methods I define
and the macro element occur? How do we define the specific values of the
custom defined properties in the macros?
6) Finally, please note that the schema file contains the wrong
information as to the full classpath of the IWidgetResolver interface.
Apologies for the numerous questions, but I am really not getting it.
Thank you very much in advance,
B.
|
|
|
| Re: Select items by name in AGR macro [message #66778 is a reply to message #66701] |
Mon, 17 April 2006 14:38 |
No real name
Messages: 404
Registered: July 2009 |
Senior Member |
|
|
Hi Barbara,
> 1) As I understand it, I have two ways of improving on recognition:
> either by defining my own widget resolver and add it by an extension
> point or by adding <class> elements to the widgetReg.xml file that you
> provide. Is this accurate?
Yes, that's correct.
> 2) If item 1) is correct, which one of the two routes is the recommended
> one?
It depends what is being used to resolve the widget. If you're using direct
methods of the widget, then use widgetReg.xml but if you intend to use some
properties that can't be captured in the XML file, then register your own
widget resolver. Keep in mind that you have to always keep a copy of your
version of widgetReg.xml. You'll always need to overwrite the default one
when you download AGR.
> 3) I am not clear how and where to define my extension point. Is it in
> the manifest of my test plugins? If so, when I try to add an extension
> point using the standard manifest editor (Extensions editor tab), the
> org.eclipse.tptp.test.auto.gui.widgetResolver extension point does not
> appear in the list of possible extension points. Could you possibly
> provide a snippet showing how the extension point is defined in the
> plugin.xml file so that I can enter it by hand?
You have to first declare a dependency on org.eclipse.tptp.test.auto.gui.
Only then you can add the widgetResolver extension point.
> 4) If I go the custom widget resolver class route, I don't understand
> clearly how to implement my IWidgetResolver class: do I need one class
> per widget? Or per widget type? Can you provide an example implementation?
> A similar question applies to the addition of <class> elements to the
> widgetReg.xml file: do I need one per physical widget or one per widget
> type?
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
> 5) How does the connection happen between the custom methods I define
> and the macro element occur? How do we define the specific values of the
> custom defined properties in the macros?
The connection is the widget resolver that you register and the custom
properties are just the string representation of the returned value of
methods that you have registered.
> 6) Finally, please note that the schema file contains the wrong
> information as to the full classpath of the IWidgetResolver interface.
Thanks. I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=136988
"Barbara Rosi-Schwartz" <Barbara.Rosi-Schwartz@Etish.org> wrote in message
news:e1o6q1$o9h$1@utils.eclipse.org...
> Ali Mehregani wrote:
> > In fact I strongly recommend for users to use custom widget resolvers.
> > There are a few defects and features open to make the widget resolving
> > mechanism more robust but until they're implemented, users are
encouraged to
> > use their own custom widget resolvers.
> >
> > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=112634 (feature)
> > and https://bugs.eclipse.org/bugs/show_bug.cgi?id=128271 (defect)
> >
> > Thanks.
> >
> > "Vladimir" <vladimir@au.ru> wrote in message
> > news:a8fb3016767df645cc88239e4b556d24$1@www.eclipse.org...
> >> Al items in my generated script selected by their number.
> >> For instance:
> >> <command type="item-select" contextId="wizard-page/moduleSelection"
> >> widgetId="org.eclipse.swt.widgets.Tree#1">
> >> <item
> >>
path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||0| "/>
> >> <item
> >>
path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||1| "/>
> >> <item
> >>
path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||2| "/>
> >> <item
> >>
path=" org.eclipse.team.internal.ccvs.core.resources.RemoteFolder0| 7||3| "/>
> >> </command>
> >>
> >> You can see, that items selected by their position in the tree. But if
the
> >> tree has changed, the script become invalid. Is it possible to select
> >> items by name?
> >>
> >> Thanks,
> >> Vladimir.
> >>
> >
> >
>
> Ali,
>
> I have re-read the manual on this subject and I must admit I now have
> more questions than answers. Could you possibly enlighten me?
>
> 1) As I understand it, I have two ways of improving on recognition:
> either by defining my own widget resolver and add it by an extension
> point or by adding <class> elements to the widgetReg.xml file that you
> provide. Is this accurate?
>
> 2) If item 1) is correct, which one of the two routes is the recommended
> one?
>
> 3) I am not clear how and where to define my extension point. Is it in
> the manifest of my test plugins? If so, when I try to add an extension
> point using the standard manifest editor (Extensions editor tab), the
> org.eclipse.tptp.test.auto.gui.widgetResolver extension point does not
> appear in the list of possible extension points. Could you possibly
> provide a snippet showing how the extension point is defined in the
> plugin.xml file so that I can enter it by hand?
>
> 4) If I go the custom widget resolver class route, I don't understand
> clearly how to implement my IWidgetResolver class: do I need one class
> per widget? Or per widget type? Can you provide an example implementation?
> A similar question applies to the addition of <class> elements to the
> widgetReg.xml file: do I need one per physical widget or one per widget
> type?
>
> 5) How does the connection happen between the custom methods I define
> and the macro element occur? How do we define the specific values of the
> custom defined properties in the macros?
>
> 6) Finally, please note that the schema file contains the wrong
> information as to the full classpath of the IWidgetResolver interface.
>
> Apologies for the numerous questions, but I am really not getting it.
>
> Thank you very much in advance,
> B.
>
|
|
|
| Re: Select items by name in AGR macro [message #66876 is a reply to message #66778] |
Mon, 17 April 2006 19:44 |
Barbara Rosi-Schwartz
Messages: 448
Registered: July 2009 |
Senior Member |
|
|
Hi Ali.
Please see my comments inline. For brevity, I have removed the questions
and answers that I am now satisfied with.
Ali Mehregani wrote:
> Hi Barbara,
>
>
>
>> 4) If I go the custom widget resolver class route, I don't understand
>> clearly how to implement my IWidgetResolver class: do I need one class
>> per widget? Or per widget type? Can you provide an example implementation?
>> A similar question applies to the addition of <class> elements to the
>> widgetReg.xml file: do I need one per physical widget or one per widget
>> type?
>
> For widget resolver class, see
> org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
> org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
> For widgetReg.xml, read the internal document.
>
I have looked at and played around with widgetReg.xml during the
weekend. What do you mean exactly by the internal document? Do you mean
the bit of documentation at the top of the xml file itself (if so, I
have read that) or something else?
I have actually tried to add a <class> element to widgetReg.xml
corresponding to one of my own model elements, but without success.
Perhaps I can outline what I have done and ask you to spot the error for
me.
a) I have a view containing a tree which is the visualization of an XML
model whose basic model element is of type com.xxx.yyy.IModelElement. I
therefore added to widgetReg.xml the following element:
<class name = "com.xxx.yyy.IModelElement" matchThreshold = "1.0">
<method name = "getFullPath" weight = "1.0"/>
</class>
where getFullPath is a method declared by the IModelElement interface.
b) I brought down and then re instantiated Eclipse.
c) I recorded a test case against the view, in which I select a couple
of elements in the tree and do something with them.
d) I inspected the macro. I was hoping to see the selection events being
based upon the full path of the selected tree elements, something like:
<item
path=" org.eclipse.swt.widgets.TreeItem#{{/myServer/myProject}}-{{1 .0}} "/>
but all I got was the relative index position of the selected elements,
as if I had not registered anything at all in the widgetReg.xml file, as in
<item path="com.xxx.yyy.Project0"/>
where class com.xxx.yyy.Project, which implements IModelElement, is the
correct class for the selected node.
What did I do wrong?
>
>> 6) Finally, please note that the schema file contains the wrong
>> information as to the full classpath of the IWidgetResolver interface.
>
> Thanks. I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=136988
Thanks for opening the bug.
Thank you very much for taking the time to reply so exhaustively.
Cheerio,
B.
|
|
|
| Re: Select items by name in AGR macro [message #66884 is a reply to message #66778] |
Mon, 17 April 2006 20:09 |
|
This is a multi-part message in MIME format.
--------------090202030406060001090209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi Ali,
Ali Mehregani wrote:
> Hi Barbara
>> 4) If I go the custom widget resolver class route, I don't understand
>> clearly how to implement my IWidgetResolver class: do I need one class
>> per widget? Or per widget type? Can you provide an example implementation?
>> A similar question applies to the addition of <class> elements to the
>> widgetReg.xml file: do I need one per physical widget or one per widget
>> type?
>>
>
> For widget resolver class, see
> org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
> org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
> For widgetReg.xml, read the internal document.
>
Is there an easy way to get the source for AGR. I find that to pull down
all of AGR from cvs pretty much requires getting all of TPTP. (Please
correct me if this is not correct.) This can be pretty gruesome and slow
going. I have downloaded the TPTP sdk download for 4.2, but this does
not seem to contain AGR source features, which makes sense since AGR is
not yet "official" :-( Any suggestions?
Thanks,
Joel
--------------090202030406060001090209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi Ali,</font><br>
<br>
Ali Mehregani wrote:
<blockquote cite="mide20999$b49$1@utils.eclipse.org" type="cite">
<pre wrap="">Hi Barbara</pre>
<blockquote type="cite">
<pre wrap="">4) If I go the custom widget resolver class route, I don't understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example implementation?
A similar question applies to the addition of <class> elements to the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
</pre>
</blockquote>
<pre wrap=""><!---->
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
</pre>
</blockquote>
Is there an easy way to get the source for AGR. I find that to pull
down all of AGR from cvs pretty much requires getting all of TPTP.
(Please correct me if this is not correct.) This can be pretty gruesome
and slow going. I have downloaded the TPTP sdk download for 4.2, but
this does not seem to contain AGR source features, which makes sense
since AGR is not yet "official" :-( Any suggestions?<br>
<br>
Thanks,<br>
Joel<br>
</body>
</html>
--------------090202030406060001090209--
|
|
|
| Re: Select items by name in AGR macro [message #66951 is a reply to message #66876] |
Tue, 18 April 2006 15:38 |
No real name
Messages: 404
Registered: July 2009 |
Senior Member |
|
|
The steps that you've described below seem to be correct. You don't need to
kill the workbench and restart it everytime the widgetReg.xml file is
changed. If the file size is changed, then adaptive widget resolver will
reload it. I tried registering multiple widgets to ensure that everything
was working fine and I didn't notice any problems. As an experiment, can
you register something under the Eclipse environment to see if it works.
If you would like to debug this issue, place a breakpoint just after the
following comment in AdaptiveWidgetResolver and record a session involving
the selection of the tree item:
/* As a final resolution, try and call the driver class to resolve the
widget */
If widgetValue is null, then that means that there was something wrong with
the registeration. If it's not null, then place a breakpoing in the
invokeProperty method and see if it's able to find the right class and
methods to invoke.
"Barbara Rosi-Schwartz" <Barbara.Rosi-Schwartz@Etish.org> wrote in message
news:e20r6p$j11$1@utils.eclipse.org...
> Hi Ali.
>
> Please see my comments inline. For brevity, I have removed the questions
> and answers that I am now satisfied with.
>
> Ali Mehregani wrote:
> > Hi Barbara,
> >
> >
> >
> >> 4) If I go the custom widget resolver class route, I don't understand
> >> clearly how to implement my IWidgetResolver class: do I need one class
> >> per widget? Or per widget type? Can you provide an example
implementation?
> >> A similar question applies to the addition of <class> elements to the
> >> widgetReg.xml file: do I need one per physical widget or one per widget
> >> type?
> >
> > For widget resolver class, see
> >
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
> > org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
> > For widgetReg.xml, read the internal document.
> >
>
> I have looked at and played around with widgetReg.xml during the
> weekend. What do you mean exactly by the internal document? Do you mean
> the bit of documentation at the top of the xml file itself (if so, I
> have read that) or something else?
>
> I have actually tried to add a <class> element to widgetReg.xml
> corresponding to one of my own model elements, but without success.
> Perhaps I can outline what I have done and ask you to spot the error for
> me.
>
> a) I have a view containing a tree which is the visualization of an XML
> model whose basic model element is of type com.xxx.yyy.IModelElement. I
> therefore added to widgetReg.xml the following element:
>
> <class name = "com.xxx.yyy.IModelElement" matchThreshold = "1.0">
> <method name = "getFullPath" weight = "1.0"/>
> </class>
>
> where getFullPath is a method declared by the IModelElement interface.
>
> b) I brought down and then re instantiated Eclipse.
>
> c) I recorded a test case against the view, in which I select a couple
> of elements in the tree and do something with them.
>
> d) I inspected the macro. I was hoping to see the selection events being
> based upon the full path of the selected tree elements, something like:
> <item
> path=" org.eclipse.swt.widgets.TreeItem#{{/myServer/myProject}}-{{1 .0}} "/>
>
> but all I got was the relative index position of the selected elements,
> as if I had not registered anything at all in the widgetReg.xml file, as
in
>
> <item path="com.xxx.yyy.Project0"/>
>
> where class com.xxx.yyy.Project, which implements IModelElement, is the
> correct class for the selected node.
>
> What did I do wrong?
>
> >
> >> 6) Finally, please note that the schema file contains the wrong
> >> information as to the full classpath of the IWidgetResolver interface.
> >
> > Thanks. I've opened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=136988
>
> Thanks for opening the bug.
>
> Thank you very much for taking the time to reply so exhaustively.
>
> Cheerio,
> B.
|
|
|
| Re: Select items by name in AGR macro [message #66969 is a reply to message #66884] |
Tue, 18 April 2006 15:40 |
No real name
Messages: 404
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0054_01C662DC.EB90A450
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I would recommend using a TPTP SDK driver when importing the auto gui =
plug-in. That way you'll only need to extract the auto gui plug-in from =
CVS and Eclipse should automatically use the TPTP plug-ins under the =
plug-in folder to resolve its dependencies.
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message =
news:e20smf$pte$1@utils.eclipse.org...
Hi Ali,
Ali Mehregani wrote:=20
Hi Barbara4) If I go the custom widget resolver class route, I don't =
understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example =
implementation?
A similar question applies to the addition of <class> elements to the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
=20
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver=
OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
Is there an easy way to get the source for AGR. I find that to pull =
down all of AGR from cvs pretty much requires getting all of TPTP. =
(Please correct me if this is not correct.) This can be pretty gruesome =
and slow going. I have downloaded the TPTP sdk download for 4.2, but =
this does not seem to contain AGR source features, which makes sense =
since AGR is not yet "official" :-( Any suggestions?
Thanks,
Joel
------=_NextPart_000_0054_01C662DC.EB90A450
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I would recommend using a TPTP SDK =
driver when=20
importing the auto gui plug-in. That way you'll only need to =
extract the=20
auto gui plug-in from CVS and Eclipse should automatically use the TPTP =
plug-ins=20
under the plug-in folder to resolve its dependencies.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>"Joel Rosi-Schwartz" <<A=20
href=3D"mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org=
</A>>=20
wrote in message <A=20
href=3D"news:e20smf$pte$1@utils.eclipse.org">news:e20smf$pte$1@utils.ecli=
pse.org</A>...</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"><FONT=20
face=3D"Helvetica, Arial, sans-serif">Hi Ali,</FONT><BR><BR>Ali =
Mehregani wrote:=20
<BLOCKQUOTE cite=3Dmide20999$b49$1@utils.eclipse.org =
type=3D"cite"><PRE wrap=3D"">Hi Barbara</PRE>
<BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">4) If I go the custom =
widget resolver class route, I don't understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example =
implementation?
A similar question applies to the addition of <class> elements to =
the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
</PRE></BLOCKQUOTE><PRE wrap=3D""><!---->
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver=
OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
</PRE></BLOCKQUOTE>Is there an easy way to get the source for AGR. I =
find=20
that to pull down all of AGR from cvs pretty much requires getting all =
of=20
TPTP. (Please correct me if this is not correct.) This can be pretty =
gruesome=20
and slow going. I have downloaded the TPTP sdk download for 4.2, but =
this does=20
not seem to contain AGR source features, which makes sense since AGR =
is not=20
yet "official" :-( Any=20
suggestions?<BR><BR>Thanks,<BR>Joel<BR></BLOCKQUOTE></BODY ></HTML>
------=_NextPart_000_0054_01C662DC.EB90A450--
|
|
|
| Re: Select items by name in AGR macro [message #66996 is a reply to message #66969] |
Tue, 18 April 2006 16:47 |
|
This is a multi-part message in MIME format.
--------------060501030501060407090109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Thanks Ali. I have done as you suggest and imported
org.eclipse.tptp.test.auto.gui. I still have 36 "unresolved errors" in
the workspace. For the moment that is not a problem, because I really
only needed the source for the Resolvers that you mentioned so Barbara
can have a look at them. In the long run, though, I would like to be
able to have buildable source. Perhaps when you have time :-D you
could put clear source procurement instructions into the the Guide.
Much thanks,
Joel
Ali Mehregani wrote:
> I would recommend using a TPTP SDK driver when importing the auto gui
> plug-in. That way you'll only need to extract the auto gui plug-in
> from CVS and Eclipse should automatically use the TPTP plug-ins under
> the plug-in folder to resolve its dependencies.
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org
> <mailto:Joel.Rosi-Schwartz@Etish.org>> wrote in message
> news:e20smf$pte$1@utils.eclipse.org...
>
> Hi Ali,
>
> Ali Mehregani wrote:
>> Hi Barbara
>>> 4) If I go the custom widget resolver class route, I don't understand
>>> clearly how to implement my IWidgetResolver class: do I need one class
>>> per widget? Or per widget type? Can you provide an example implementation?
>>> A similar question applies to the addition of <class> elements to the
>>> widgetReg.xml file: do I need one per physical widget or one per widget
>>> type?
>>>
>>
>> For widget resolver class, see
>> org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
>> org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
>> For widgetReg.xml, read the internal document.
>>
> Is there an easy way to get the source for AGR. I find that to
> pull down all of AGR from cvs pretty much requires getting all of
> TPTP. (Please correct me if this is not correct.) This can be
> pretty gruesome and slow going. I have downloaded the TPTP sdk
> download for 4.2, but this does not seem to contain AGR source
> features, which makes sense since AGR is not yet "official" :-(
> Any suggestions?
>
> Thanks,
> Joel
>
--------------060501030501060407090109
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Thanks Ali. I have done as
you suggest and imported org.eclipse.tptp.test.auto.gui. I still have
36 "unresolved errors" in the workspace. For the moment that is not a
problem, because I really only needed the source for the Resolvers that
you mentioned so Barbara can have a look at them. In the long run,
though, I would like to be able to have buildable source. Perhaps when
you have time <span class="moz-smiley-s5"><span> :-D </span></span>
you could put clear source procurement instructions into the the Guide.<br>
<br>
Much thanks,<br>
Joel<br>
</font><br>
Ali Mehregani wrote:
<blockquote cite="mide231aj$amn$1@utils.eclipse.org" type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2800.1528" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">I would recommend using a TPTP SDK
driver when importing the auto gui plug-in. That way you'll only need
to extract the auto gui plug-in from CVS and Eclipse should
automatically use the TPTP plug-ins under the plug-in folder to resolve
its dependencies.</font></div>
<div> </div>
<div>"Joel Rosi-Schwartz" <<a
href="mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org</a>>
wrote in message <a href="news:e20smf$pte$1@utils.eclipse.org">news:e20smf$pte$1@utils.eclipse.org</a>...</div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"><font
face="Helvetica, Arial, sans-serif">Hi Ali,</font><br>
<br>
Ali Mehregani wrote:
<blockquote cite="mide20999$b49$1@utils.eclipse.org" type="cite">
<pre wrap="">Hi Barbara</pre>
<blockquote type="cite">
<pre wrap="">4) If I go the custom widget resolver class route, I don't understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example implementation?
A similar question applies to the addition of <class> elements to the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
</pre>
</blockquote>
<pre wrap=""><!---->
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
</pre>
</blockquote>
Is there an easy way to get the source for AGR. I find that to pull
down all of AGR from cvs pretty much requires getting all of TPTP.
(Please correct me if this is not correct.) This can be pretty gruesome
and slow going. I have downloaded the TPTP sdk download for 4.2, but
this does not seem to contain AGR source features, which makes sense
since AGR is not yet "official" :-( Any suggestions?<br>
<br>
Thanks,<br>
Joel<br>
</blockquote>
</blockquote>
</body>
</html>
--------------060501030501060407090109--
|
|
|
| Re: Select items by name in AGR macro [message #67252 is a reply to message #66951] |
Fri, 21 April 2006 09:58 |
Barbara Rosi-Schwartz
Messages: 448
Registered: July 2009 |
Senior Member |
|
|
Ali Mehregani wrote:
> The steps that you've described below seem to be correct. You don't need to
> kill the workbench and restart it everytime the widgetReg.xml file is
> changed. If the file size is changed, then adaptive widget resolver will
> reload it. I tried registering multiple widgets to ensure that everything
> was working fine and I didn't notice any problems. As an experiment, can
> you register something under the Eclipse environment to see if it works.
>
> If you would like to debug this issue, place a breakpoint just after the
> following comment in AdaptiveWidgetResolver and record a session involving
> the selection of the tree item:
> /* As a final resolution, try and call the driver class to resolve the
> widget */
>
> If widgetValue is null, then that means that there was something wrong with
> the registeration. If it's not null, then place a breakpoing in the
> invokeProperty method and see if it's able to find the right class and
> methods to invoke.
>
Ali,
My apologies if I sound really thick, but how do I go about debugging
the recording of a test case? :-(
Thanks,
B.
|
|
| |
| Re: Select items by name in AGR macro [message #67372 is a reply to message #66996] |
Fri, 21 April 2006 14:59 |
No real name
Messages: 404
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_002B_01C66532.B3C54D20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Can you tell me what the unresolved errors are (just the first 10 of =
them)?
Thanks.
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message =
news:e2356b$t9c$1@utils.eclipse.org...
Thanks Ali. I have done as you suggest and imported =
org.eclipse.tptp.test.auto.gui. I still have 36 "unresolved errors" in =
the workspace. For the moment that is not a problem, because I really =
only needed the source for the Resolvers that you mentioned so Barbara =
can have a look at them. In the long run, though, I would like to be =
able to have buildable source. Perhaps when you have time :-D you =
could put clear source procurement instructions into the the Guide.
Much thanks,
Joel
Ali Mehregani wrote:=20
I would recommend using a TPTP SDK driver when importing the auto =
gui plug-in. That way you'll only need to extract the auto gui plug-in =
from CVS and Eclipse should automatically use the TPTP plug-ins under =
the plug-in folder to resolve its dependencies.
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message =
news:e20smf$pte$1@utils.eclipse.org...
Hi Ali,
Ali Mehregani wrote:=20
Hi Barbara4) If I go the custom widget resolver class route, I don't =
understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example =
implementation?
A similar question applies to the addition of <class> elements to the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
=20
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver=
OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
Is there an easy way to get the source for AGR. I find that to pull =
down all of AGR from cvs pretty much requires getting all of TPTP. =
(Please correct me if this is not correct.) This can be pretty gruesome =
and slow going. I have downloaded the TPTP sdk download for 4.2, but =
this does not seem to contain AGR source features, which makes sense =
since AGR is not yet "official" :-( Any suggestions?
Thanks,
Joel
------=_NextPart_000_002B_01C66532.B3C54D20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV>
<DIV><FONT face=3DArial size=3D2>Can you tell me what the unresolved =
errors are=20
(just the first 10 of them)?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks.</FONT></DIV></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Joel Rosi-Schwartz" <<A=20
=
href=3D"mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org=
</A>>=20
wrote in message <A=20
=
href=3D"news:e2356b$t9c$1@utils.eclipse.org">news:e2356b$t9c$1@utils.ecli=
pse.org</A>...</DIV><FONT=20
face=3D"Helvetica, Arial, sans-serif">Thanks Ali. I have done as =
you=20
suggest and imported org.eclipse.tptp.test.auto.gui. I still have 36=20
"unresolved errors" in the workspace. For the moment that is not a =
problem,=20
because I really only needed the source for the Resolvers that you =
mentioned=20
so Barbara can have a look at them. In the long run, though, I would =
like to=20
be able to have buildable source. Perhaps when you have time <SPAN=20
class=3Dmoz-smiley-s5><SPAN>:-D </SPAN></SPAN> you could =
put clear=20
source procurement instructions into the the Guide.<BR><BR>Much=20
thanks,<BR>Joel<BR></FONT><BR>Ali Mehregani wrote:=20
<BLOCKQUOTE cite=3Dmide231aj$amn$1@utils.eclipse.org type=3D"cite">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR>
<STYLE></STYLE>
<DIV><FONT face=3DArial size=3D2>I would recommend using a TPTP SDK =
driver when=20
importing the auto gui plug-in. That way you'll only need to =
extract=20
the auto gui plug-in from CVS and Eclipse should automatically use =
the TPTP=20
plug-ins under the plug-in folder to resolve its =
dependencies.</FONT></DIV>
<DIV> </DIV>
<DIV>"Joel Rosi-Schwartz" <<A=20
=
href=3D"mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org=
</A>>=20
wrote in message <A=20
=
href=3D"news:e20smf$pte$1@utils.eclipse.org">news:e20smf$pte$1@utils.ecli=
pse.org</A>...</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px"><FONT=20
face=3D"Helvetica, Arial, sans-serif">Hi Ali,</FONT><BR><BR>Ali =
Mehregani=20
wrote:=20
<BLOCKQUOTE cite=3Dmide20999$b49$1@utils.eclipse.org =
type=3D"cite"><PRE wrap=3D"">Hi Barbara</PRE>
<BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">4) If I go the custom =
widget resolver class route, I don't understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example =
implementation?
A similar question applies to the addition of <class> elements to =
the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
</PRE></BLOCKQUOTE><PRE wrap=3D""><!---->
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver=
OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
</PRE></BLOCKQUOTE>Is there an easy way to get the source for AGR. I=20
find that to pull down all of AGR from cvs pretty much requires =
getting=20
all of TPTP. (Please correct me if this is not correct.) This can =
be=20
pretty gruesome and slow going. I have downloaded the TPTP sdk =
download=20
for 4.2, but this does not seem to contain AGR source features, =
which=20
makes sense since AGR is not yet "official" :-( Any=20
=
suggestions?<BR><BR>Thanks,<BR>Joel<BR></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQ=
UOTE></BODY></HTML>
------=_NextPart_000_002B_01C66532.B3C54D20--
|
|
|
| Re: Select items by name in AGR macro [message #67430 is a reply to message #67372] |
Fri, 21 April 2006 16:19 |
|
This is a multi-part message in MIME format.
--------------010306090704060707080108
Content-Type: multipart/alternative;
boundary="------------070803060607030608080308"
--------------070803060607030608080308
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I know you said just the first ten, but it was just easy to past all of
them into excel so I you get the lot at no extra cost ;-)
Let me know if there is anything else I can do to assist.
Cheers,
Joel
Ali Mehregani wrote:
> Can you tell me what the unresolved errors are (just the first 10 of
> them)?
> Thanks.
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org
> <mailto:Joel.Rosi-Schwartz@Etish.org>> wrote in message
> news:e2356b$t9c$1@utils.eclipse.org...
> Thanks Ali. I have done as you suggest and imported
> org.eclipse.tptp.test.auto.gui. I still have 36 "unresolved
> errors" in the workspace. For the moment that is not a problem,
> because I really only needed the source for the Resolvers that you
> mentioned so Barbara can have a look at them. In the long run,
> though, I would like to be able to have buildable source. Perhaps
> when you have time :-D you could put clear source procurement
> instructions into the the Guide.
>
> Much thanks,
> Joel
>
> Ali Mehregani wrote:
>> I would recommend using a TPTP SDK driver when importing the auto
>> gui plug-in. That way you'll only need to extract the auto gui
>> plug-in from CVS and Eclipse should automatically use the TPTP
>> plug-ins under the plug-in folder to resolve its dependencies.
>>
>> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org
>> <mailto:Joel.Rosi-Schwartz@Etish.org>> wrote in message
>> news:e20smf$pte$1@utils.eclipse.org...
>>
>> Hi Ali,
>>
>> Ali Mehregani wrote:
>>> Hi Barbara
>>>> 4) If I go the custom widget resolver class route, I don't understand
>>>> clearly how to implement my IWidgetResolver class: do I need one class
>>>> per widget? Or per widget type? Can you provide an example implementation?
>>>> A similar question applies to the addition of <class> elements to the
>>>> widgetReg.xml file: do I need one per physical widget or one per widget
>>>> type?
>>>>
>>>
>>> For widget resolver class, see
>>> org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
>>> org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
>>> For widgetReg.xml, read the internal document.
>>>
>> Is there an easy way to get the source for AGR. I find that
>> to pull down all of AGR from cvs pretty much requires getting
>> all of TPTP. (Please correct me if this is not correct.) This
>> can be pretty gruesome and slow going. I have downloaded the
>> TPTP sdk download for 4.2, but this does not seem to contain
>> AGR source features, which makes sense since AGR is not yet
>> "official" :-( Any suggestions?
>>
>> Thanks,
>> Joel
>>
--------------070803060607030608080308
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">I know you said just the
first ten, but it was just easy to past all of them into excel so I you
get the lot at no extra cost <span class="moz-smiley-s3"><span> ;-) </span></span><br>
<br>
Let me know if there is anything else I can do to assist.<br>
<br>
Cheers,<br>
Joel<br>
</font><br>
Ali Mehregani wrote:
<blockquote cite="mide2as1k$3b6$1@utils.eclipse.org" type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2800.1528" name="GENERATOR">
<div>
<div><font face="Arial" size="2">Can you tell me what the unresolved
errors are (just the first 10 of them)?</font></div>
<div><font face="Arial" size="2">Thanks.</font></div>
</div>
<blockquote dir="ltr"
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div>"Joel Rosi-Schwartz" <<a
href="mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org</a>>
wrote in message <a href="news:e2356b$t9c$1@utils.eclipse.org">news:e2356b$t9c$1@utils.eclipse.org</a>...</div>
<font face="Helvetica, Arial, sans-serif">Thanks Ali. I have done
as you suggest and imported org.eclipse.tptp.test.auto.gui. I still
have 36 "unresolved errors" in the workspace. For the moment that is
not a problem, because I really only needed the source for the
Resolvers that you mentioned so Barbara can have a look at them. In the
long run, though, I would like to be able to have buildable source.
Perhaps when you have time <span class="moz-smiley-s5"><span>:-D </span></span>
you could put clear source procurement instructions into the the Guide.<br>
<br>
Much thanks,<br>
Joel<br>
</font><br>
Ali Mehregani wrote:
<blockquote cite="mide231aj$amn$1@utils.eclipse.org" type="cite">
<meta content="MSHTML 6.00.2800.1528" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">I would recommend using a TPTP
SDK driver when importing the auto gui plug-in. That way you'll only
need to extract the auto gui plug-in from CVS and Eclipse should
automatically use the TPTP plug-ins under the plug-in folder to resolve
its dependencies.</font></div>
<div> </div>
<div>"Joel Rosi-Schwartz" <<a
href="mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org</a>>
wrote in message <a href="news:e20smf$pte$1@utils.eclipse.org">news:e20smf$pte$1@utils.eclipse.org</a>...</div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"><font
face="Helvetica, Arial, sans-serif">Hi Ali,</font><br>
<br>
Ali Mehregani wrote:
<blockquote cite="mide20999$b49$1@utils.eclipse.org" type="cite">
<pre wrap="">Hi Barbara</pre>
<blockquote type="cite">
<pre wrap="">4) If I go the custom widget resolver class route, I don't understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example implementation?
A similar question applies to the addition of <class> elements to the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
</pre>
</blockquote>
<pre wrap=""><!---->
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
</pre>
</blockquote>
Is there an easy way to get the source for AGR. I find that to pull
down all of AGR from cvs pretty much requires getting all of TPTP.
(Please correct me if this is not correct.) This can be pretty gruesome
and slow going. I have downloaded the TPTP sdk download for 4.2, but
this does not seem to contain AGR source features, which makes sense
since AGR is not yet "official" :-( Any suggestions?<br>
<br>
Thanks,<br>
Joel<br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--------------070803060607030608080308--
--------------010306090704060707080108
Content-Type: application/vnd.ms-excel;
name="autogui_build_problems.xls"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="autogui_build_problems.xls"
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAAB AAAAIwAAAAAA
AAAAEAAA/v///wAAAAD+////AAAAACIAAAD///////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////8JCBAAAAYFAEwfzQfBwAAABgMA AOEAAgCwBMEA
AgAAAOIAAABcAHAAEgAASm9lbCBSb3NpLVNjaHdhcnR6ICAgICAgICAgICAg ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAg
ICAgICAgICAgICAgICAgIEIAAgCwBGEBAgAAAMABAAA9AQYAAQACAAMAnAAC AA4AGQACAAAA
EgACAAAAEwACAAAArwECAAAAvAECAAAAPQASAOABeADMYGc+OAAAAAAAAQBY AkAAAgAAAI0A
AgAAACIAAgAAAA4AAgABALcBAgAAANoAAgAAADEAGgDIAAAA/3+QAQAAAAAA lgUBQQByAGkA
YQBsADEAGgDIAAAA/3+QAQAAAAAAlgUBQQByAGkAYQBsADEAGgDIAAAA/3+Q AQAAAAAAlgUB
QQByAGkAYQBsADEAGgDIAAAA/3+QAQAAAAAAlgUBQQByAGkAYQBsAB4EGAAF ABMAACKjIiMs
IyMwO1wtIqMiIywjIzAeBB0ABgAYAAAioyIjLCMjMDtbUmVkXVwtIqMiIywj IzAeBB4ABwAZ
AAAioyIjLCMjMC4wMDtcLSKjIiMsIyMwLjAwHgQjAAgAHgAAIqMiIywjIzAu MDA7W1JlZF1c
LSKjIiMsIyMwLjAwHgQ1ACoAMAAAXy0ioyIqICMsIyMwXy07XC0ioyIqICMs IyMwXy07Xy0i
oyIqICItIl8tO18tQF8tHgQsACkAJwAAXy0qICMsIyMwXy07XC0qICMsIyMw Xy07Xy0qICIt
Il8tO18tQF8tHgQ9ACwAOAAAXy0ioyIqICMsIyMwLjAwXy07XC0ioyIqICMs IyMwLjAwXy07
Xy0ioyIqICItIj8/Xy07Xy1AXy0eBDQAKwAvAABfLSogIywjIzAuMDBfLTtc LSogIywjIzAu
MDBfLTtfLSogIi0iPz9fLTtfLUBfLeAAFAAAAAAA9f8gAAAAAAAAAAAAAADA IOAAFAABAAAA
9f8gAAD0AAAAAAAAAADAIOAAFAABAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAC AAAA9f8gAAD0
AAAAAAAAAADAIOAAFAACAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8g AAD0AAAAAAAA
AADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAA AAAAAADAIOAA
FAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADA IOAAFAAAAAAA
9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAA AAAA9f8gAAD0
AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8g AAD0AAAAAAAA
AADAIOAAFAAAAAAAAQAgAAAAAAAAAAAAAADAIOAAFAABACsA9f8gAAD4AAAA AAAAAADAIOAA
FAABACkA9f8gAAD4AAAAAAAAAADAIOAAFAABACwA9f8gAAD4AAAAAAAAAADA IOAAFAABACoA
9f8gAAD4AAAAAAAAAADAIOAAFAABAAkA9f8gAAD4AAAAAAAAAADAIJMCBAAQ gAP/kwIEABGA
Bv+TAgQAEoAE/5MCBAATgAf/kwIEAACAAP+TAgQAFIAF/2ABAgAAAIUADgBV EQAAAAAGAFNo
ZWV0MYUADgAQIAAAAAAGAFNoZWV0MoUADgAXIQAAAAAGAFNoZWV0M4wABAAB ACwAwQEIAMEB
AAAivgEA/AB+C7kAAABGAAAACAAAU2V2ZXJpdHkEAABQYXRoCAAAUmVzb3Vy Y2ULAABEZXNj
cmlwdGlvbggAAExvY2F0aW9uBQAARXJyb3JSAABvcmcuZWNsaXBzZS50cHRw LnRlc3QuYXV0
by5ndWkvc3JjL29yZy9lY2xpcHNlL3RwdHAvdGVzdC9hdXRvL2d1aS9pbnRl cm5hbC9hY3Rp
b25zHQAAQXV0b0dVSU9yaWVudGF0aW9uQWN0aW9uLmphdmEvAABBdXRvQ29u dHJvbFJlc2l6
ZXIgY2Fubm90IGJlIHJlc29sdmVkIHRvIGEgdHlwZQcAAGxpbmUgMjchAABj b250cm9sUmVz
aXplciBjYW5ub3QgYmUgcmVzb2x2ZWQHAABsaW5lIDQ0BwAAbGluZSA0Nm8A AFRoZSBpbXBv
cnQgb3JnLmVjbGlwc2UuaHlhZGVzLnRlc3QudG9vbHMudWkuY29tbW9uLmlu dGVybmFsLnV0
aWwuRm9ybVV0aWwuQXV0b0NvbnRyb2xSZXNpemVyIGNhbm5vdCBiZSByZXNv bHZlZAcAAGxp
bmUgMTNRAABUaGUgbWV0aG9kIGdldExvZ2ljYWxBdXRvUmVzaXplcigpIGlz IHVuZGVmaW5l
ZCBmb3IgdGhlIHR5cGUgQXV0b0dVSVRlc3RDYXNlc0Zvcm1RAABvcmcuZWNs aXBzZS50cHRw
LnRlc3QuYXV0by5ndWkvc3JjL29yZy9lY2xpcHNlL3RwdHAvdGVzdC9hdXRv L2d1aS9pbnRl
cm5hbC9lZGl0b3IYAABBdXRvR1VJT3ZlcnZpZXdGb3JtLmphdmGWAABUaGUg bWV0aG9kIGNy
ZWF0ZUdlbmVyaWNJbmZvcm1hdGlvbihDb21wb3NpdGUsIFN0cmluZywgU3Ry aW5nKSBpbiB0
aGUgdHlwZSBPdmVydmlld0VjbGlwc2VGb3JtIGlzIG5vdCBhcHBsaWNhYmxl IGZvciB0aGUg
YXJndW1lbnRzIChDb21wb3NpdGUsIFN0cmluZykHAABsaW5lIDc5rwAAVGhl IG1ldGhvZCBz
ZXRTZWN0aW9uUHJvcGVydHkoRm9ybVRvb2xraXQsIFNlY3Rpb24sIENvbnRy b2wsIFN0cmlu
ZywgU3RyaW5nKSBpbiB0aGUgdHlwZSBGb3JtVXRpbCBpcyBub3QgYXBwbGlj YWJsZSBmb3Ig
dGhlIGFyZ3VtZW50cyAoRm9ybVRvb2xraXQsIFNlY3Rpb24sIENvbXBvc2l0 ZSwgU3RyaW5n
KQcAAGxpbmUgOTEZAABBdXRvR1VJVGVzdENhc2VzRm9ybS5qYXZhCAAAbGlu ZSAxNDcIAABs
aW5lIDI5NAgAAGxpbmUgMzUzCAAAbGluZSA1NTUIAABsaW5lIDg0OCUAAGxv Z2ljYWxBdXRv
UmVzaXplciBjYW5ub3QgYmUgcmVzb2x2ZWQIAABsaW5lIDI5NQgAAGxpbmUg ODUwBwAAbGlu
ZSAzOGoAAFRoZSBtZXRob2QgZ2V0Q29tbW9uU2VjdGlvbigpIGlzIHVuZGVm aW5lZCBmb3Ig
dGhlIHR5cGUgQXV0b0dVSVRlc3RDYXNlc0Zvcm0uTG9naWNhbFJlcHJlc2Vu dGF0aW9uTGlz
dGVuZXIIAABsaW5lIDc0N7IAAFRoZSBtZXRob2Qgc2V0U2VjdGlvblByb3Bl cnR5KEZvcm1U
b29sa2l0LCBTZWN0aW9uLCBDb250cm9sLCBTdHJpbmcsIFN0cmluZykgaW4g dGhlIHR5cGUg
Rm9ybVV0aWwgaXMgbm90IGFwcGxpY2FibGUgZm9yIHRoZSBhcmd1bWVudHMg KEF1dG9HVUlU
b29sa2l0LCBTZWN0aW9uLCBDb21wb3NpdGUsIFN0cmluZykIAABsaW5lIDI5 OAgAAGxpbmUg
MzcxNQAAVHlwZSBtaXNtYXRjaDogY2Fubm90IGNvbnZlcnQgZnJvbSBDb250 cm9sIHRvIFNl
Y3Rpb24IAABsaW5lIDM2NFEAAG9yZy5lY2xpcHNlLnRwdHAudGVzdC5hdXRv Lmd1aS9zcmMv
b3JnL2VjbGlwc2UvdHB0cC90ZXN0L2F1dG8vZ3VpL2ludGVybmFsL3dpemFy ZB4AAEF1dG9H
VUlUZXN0U3VpdGVOZXdXaXphcmQuamF2YTAAAFRlc3RTdWl0ZU5ld1dpemFy ZDIgY2Fubm90
IGJlIHJlc29sdmVkIHRvIGEgdHlwZQcAAGxpbmUgNDNTAABUaGUgaW1wb3J0 IG9yZy5lY2xp
cHNlLmh5YWRlcy50ZXN0LnVpLndpemFyZC5UZXN0U3VpdGVOZXdXaXphcmQy IGNhbm5vdCBi
ZSByZXNvbHZlZAcAAGxpbmUgMjVhAABUaGUgbWV0aG9kIGFkZFBhZ2UoQXV0 b0dVSUV4dGVu
ZGVkU291cmNlUGFnZSkgaXMgdW5kZWZpbmVkIGZvciB0aGUgdHlwZSBBdXRv R1VJVGVzdFN1
aXRlTmV3V2l6YXJkCAAAbGluZSAxNDY2AABUaGUgbWV0aG9kIGFkZFBhZ2Vz KCkgaXMgdW5k
ZWZpbmVkIGZvciB0aGUgdHlwZSBPYmplY3QIAABsaW5lIDE1NE8AAFRoZSBt ZXRob2QgYWRq
dXN0U2VsZXRpb24oKSBpcyB1bmRlZmluZWQgZm9yIHRoZSB0eXBlIEF1dG9H VUlUZXN0U3Vp
dGVOZXdXaXphcmQHAABsaW5lIDY2VwAAVGhlIG1ldGhvZCBnZXRBdHRyaWJ1 dGVXaXphcmRQ
YWdlKCkgaXMgdW5kZWZpbmVkIGZvciB0aGUgdHlwZSBBdXRvR1VJVGVzdFN1 aXRlTmV3V2l6
YXJkCAAAbGluZSAxNTEIAABsaW5lIDE1MlEAAFRoZSBtZXRob2QgZ2V0Rmls ZUV4dGVuc2lv
bigpIGlzIHVuZGVmaW5lZCBmb3IgdGhlIHR5cGUgQXV0b0dVSVRlc3RTdWl0 ZU5ld1dpemFy
ZAgAAGxpbmUgMTE4UAAAVGhlIG1ldGhvZCBnZXRMb2NhdGlvblBhZ2UoKSBp cyB1bmRlZmlu
ZWQgZm9yIHRoZSB0eXBlIEF1dG9HVUlUZXN0U3VpdGVOZXdXaXphcmQIAABs aW5lIDEyNggA
AGxpbmUgMTQ4CAAAbGluZSAxNDlqAABUaGUgbWV0aG9kIHNldEF0dHJpYnV0 ZVdpemFyZFBh
Z2UoQXR0cmlidXRlV2l6YXJkUGFnZSkgaXMgdW5kZWZpbmVkIGZvciB0aGUg dHlwZSBBdXRv
R1VJVGVzdFN1aXRlTmV3V2l6YXJkCAAAbGluZSAxMjVtAABUaGUgbWV0aG9k IHNldERlZmF1
bHRQYWdlSW1hZ2VEZXNjcmlwdG9yKEltYWdlRGVzY3JpcHRvcikgaXMgdW5k ZWZpbmVkIGZv
ciB0aGUgdHlwZSBBdXRvR1VJVGVzdFN1aXRlTmV3V2l6YXJkBwAAbGluZSA1 NGEAAFRoZSBt
ZXRob2Qgc2V0RGlhbG9nU2V0dGluZ3MoSURpYWxvZ1NldHRpbmdzKSBpcyB1 bmRlZmluZWQg
Zm9yIHRoZSB0eXBlIEF1dG9HVUlUZXN0U3VpdGVOZXdXaXphcmQHAABsaW5l IDYwXAAAVGhl
IG1ldGhvZCBzZXRMb2NhdGlvblBhZ2UoTG9jYXRpb25QYWdlKSBpcyB1bmRl ZmluZWQgZm9y
IHRoZSB0eXBlIEF1dG9HVUlUZXN0U3VpdGVOZXdXaXphcmQIAABsaW5lIDEx NlUAAFRoZSBt
ZXRob2Qgc2V0V2luZG93VGl0bGUoU3RyaW5nKSBpcyB1bmRlZmluZWQgZm9y IHRoZSB0eXBl
IEF1dG9HVUlUZXN0U3VpdGVOZXdXaXphcmQHAABsaW5lIDUz/wBKAAgAdAUA AAwAAAAnBgAA
vwAAAGsHAAADAgAAYAkAAPgDAADUCQAAbAQAAK4LAABGBgAAFA0AAKwHAABK DgAA4ggAALAP
AABICgAAYwgVAGMIAAAAAAAAAAAAABUAAAAAAAAAzgoAAAAJCBAAAAYQAEwf zQfBwAAABgMA
AAsCGAAAAAAAAAAAACUAAAAVEgAAvR0AAMcfAAANAAIAAQAMAAIAZAAPAAIA AQARAAIAAAAQ
AAgA/Knx0k1iUD9fAAIAAQAqAAIAAAArAAIAAACCAAIAAQCAAAgAAAAAAAAA AAAlAgQAAAD/
AIEAAgDBBBQAAAAVAAAAgwACAAAAhAACAAAAoQAiAAAA/wABAAEAAQAEAAAA AAAAAAAAAADg
PwAAAAAAAOA/AABVAAIACAB9AAwAAAAAACQKDwACAAQAfQAMAAEAAQC2Qw8A AgAEAH0ADAAC
AAIA2yIPAAIABAB9AAwAAwADAG1pDwACAAQAfQAMAAQABAC2Dw8AAgAEAAAC DgAAAAAAJQAA
AAAABQAAAAgCEAAAAAAABQD/AAAAAAAAAQ8ACAIQAAEAAAAFAP8AAAAAAAAB DwAIAhAAAgAA
AAUA/wAAAAAAAAEPAAgCEAADAAAABQD/AAAAAAAAAQ8ACAIQAAQAAAAFAP8A AAAAAAABDwAI
AhAABQAAAAUA/wAAAAAAAAEPAAgCEAAGAAAABQD/AAAAAAAAAQ8ACAIQAAcA AAAFAP8AAAAA
AAABDwAIAhAACAAAAAUA/wAAAAAAAAEPAAgCEAAJAAAABQD/AAAAAAAAAQ8A CAIQAAoAAAAF
AP8AAAAAAAABDwAIAhAACwAAAAUA/wAAAAAAAAEPAAgCEAAMAAAABQD/AAAA AAAAAQ8ACAIQ
AA0AAAAFAP8AAAAAAAABDwAIAhAADgAAAAUA/wAAAAAAAAEPAAgCEAAPAAAA BQD/AAAAAAAA
AQ8ACAIQABAAAAAFAP8AAAAAAAABDwAIAhAAEQAAAAUA/wAAAAAAAAEPAAgC EAASAAAABQD/
AAAAAAAAAQ8ACAIQABMAAAAFAP8AAAAAAAABDwAIAhAAFAAAAAUA/wAAAAAA AAEPAAgCEAAV
AAAABQD/AAAAAAAAAQ8ACAIQABYAAAAFAP8AAAAAAAABDwAIAhAAFwAAAAUA /wAAAAAAAAEP
AAgCEAAYAAAABQD/AAAAAAAAAQ8ACAIQABkAAAAFAP8AAAAAAAABDwAIAhAA GgAAAAUA/wAA
AAAAAAEPAAgCEAAbAAAABQD/AAAAAAAAAQ8ACAIQABwAAAAFAP8AAAAAAAAB DwAIAhAAHQAA
AAUA/wAAAAAAAAEPAAgCEAAeAAAABQD/AAAAAAAAAQ8ACAIQAB8AAAAFAP8A AAAAAAABDwD9
AAoAAAAAAA8AAAAAAP0ACgAAAAEADwABAAAA/QAKAAAAAgAPAAIAAAD9AAoA AAADAA8AAwAA
AP0ACgAAAAQADwAEAAAA/QAKAAEAAAAPAAUAAAD9AAoAAQABAA8ABgAAAP0A CgABAAIADwAH
AAAA/QAKAAEAAwAPAAgAAAD9AAoAAQAEAA8ACQAAAP0ACgACAAAADwAFAAAA /QAKAAIAAQAP
AAYAAAD9AAoAAgACAA8ABwAAAP0ACgACAAMADwAKAAAA/QAKAAIABAAPAAsA AAD9AAoAAwAA
AA8ABQAAAP0ACgADAAEADwAGAAAA/QAKAAMAAgAPAAcAAAD9AAoAAwADAA8A CgAAAP0ACgAD
AAQADwAMAAAA/QAKAAQAAAAPAAUAAAD9AAoABAABAA8ABgAAAP0ACgAEAAIA DwAHAAAA/QAK
AAQAAwAPAA0AAAD9AAoABAAEAA8ADgAAAP0ACgAFAAAADwAFAAAA/QAKAAUA AQAPAAYAAAD9
AAoABQACAA8ABwAAAP0ACgAFAAMADwAPAAAA/QAKAAUABAAPAAwAAAD9AAoA BgAAAA8ABQAA
AP0ACgAGAAEADwAQAAAA/QAKAAYAAgAPABEAAAD9AAoABgADAA8AEgAAAP0A CgAGAAQADwAT
AAAA/QAKAAcAAAAPAAUAAAD9AAoABwABAA8AEAAAAP0ACgAHAAIADwARAAAA /QAKAAcAAwAP
ABQAAAD9AAoABwAEAA8AFQAAAP0ACgAIAAAADwAFAAAA/QAKAAgAAQAPABAA AAD9AAoACAAC
AA8AFgAAAP0ACgAIAAMADwAIAAAA/QAKAAgABAAPABcAAAD9AAoACQAAAA8A BQAAAP0ACgAJ
AAEADwAQAAAA/QAKAAkAAgAPABYAAAD9AAoACQADAA8ACAAAAP0ACgAJAAQA DwAYAAAA/QAK
AAoAAAAPAAUAAAD9AAoACgABAA8AEAAAAP0ACgAKAAIADwAWAAAA/QAKAAoA AwAPAAgAAAD9
AAoACgAEAA8AGQAAAP0ACgALAAAADwAFAAAA/QAKAAsAAQAPABAAAAD9AAoA CwACAA8AFgAA
AP0ACgALAAMADwAIAAAA/QAKAAsABAAPABoAAAD9AAoADAAAAA8ABQAAAP0A CgAMAAEADwAQ
AAAA/QAKAAwAAgAPABYAAAD9AAoADAADAA8ACAAAAP0ACgAMAAQADwAbAAAA /QAKAA0AAAAP
AAUAAAD9AAoADQABAA8AEAAAAP0ACgANAAIADwAWAAAA/QAKAA0AAwAPABwA AAD9AAoADQAE
AA8AGAAAAP0ACgAOAAAADwAFAAAA/QAKAA4AAQAPABAAAAD9AAoADgACAA8A FgAAAP0ACgAO
AAMADwAcAAAA/QAKAA4ABAAPAB0AAAD9AAoADwAAAA8ABQAAAP0ACgAPAAEA DwAQAAAA/QAK
AA8AAgAPABYAAAD9AAoADwADAA8AHAAAAP0ACgAPAAQADwAeAAAA/QAKABAA AAAPAAUAAAD9
AAoAEAABAA8AEAAAAP0ACgAQAAIADwAWAAAA/QAKABAAAwAPAA0AAAD9AAoA EAAEAA8AHwAA
AP0ACgARAAAADwAFAAAA/QAKABEAAQAPABAAAAD9AAoAEQACAA8AFgAAAP0A CgARAAMADwAg
AAAA/QAKABEABAAPACEAAAD9AAoAEgAAAA8ABQAAAP0ACgASAAEADwAQAAAA /QAKABIAAgAP
ABYAAAD9AAoAEgADAA8AIgAAAP0ACgASAAQADwAjAAAA/QAKABMAAAAPAAUA AAD9AAoAEwAB
AA8AEAAAAP0ACgATAAIADwAWAAAA/QAKABMAAwAPACIAAAD9AAoAEwAEAA8A JAAAAP0ACgAU
AAAADwAFAAAA/QAKABQAAQAPABAAAAD9AAoAFAACAA8AFgAAAP0ACgAUAAMA DwAlAAAA/QAK
ABQABAAPACYAAAD9AAoAFQAAAA8ABQAAAP0ACgAVAAEADwAnAAAA/QAKABUA AgAPACgAAAD9
AAoAFQADAA8AKQAAAP0ACgAVAAQADwAqAAAA/QAKABYAAAAPAAUAAAD9AAoA FgABAA8AJwAA
AP0ACgAWAAIADwAoAAAA/QAKABYAAwAPACsAAAD9AAoAFgAEAA8ALAAAAP0A CgAXAAAADwAF
AAAA/QAKABcAAQAPACcAAAD9AAoAFwACAA8AKAAAAP0ACgAXAAMADwAtAAAA /QAKABcABAAP
AC4AAAD9AAoAGAAAAA8ABQAAAP0ACgAYAAEADwAnAAAA/QAKABgAAgAPACgA AAD9AAoAGAAD
AA8ALwAAAP0ACgAYAAQADwAwAAAA/QAKABkAAAAPAAUAAAD9AAoAGQABAA8A JwAAAP0ACgAZ
AAIADwAoAAAA/QAKABkAAwAPADEAAAD9AAoAGQAEAA8AMgAAAP0ACgAaAAAA DwAFAAAA/QAK
ABoAAQAPACcAAAD9AAoAGgACAA8AKAAAAP0ACgAaAAMADwAzAAAA/QAKABoA BAAPADQAAAD9
AAoAGwAAAA8ABQAAAP0ACgAbAAEADwAnAAAA/QAKABsAAgAPACgAAAD9AAoA GwADAA8AMwAA
AP0ACgAbAAQADwA1AAAA/QAKABwAAAAPAAUAAAD9AAoAHAABAA8AJwAAAP0A CgAcAAIADwAo
AAAA/QAKABwAAwAPADYAAAD9AAoAHAAEAA8ANwAAAP0ACgAdAAAADwAFAAAA /QAKAB0AAQAP
ACcAAAD9AAoAHQACAA8AKAAAAP0ACgAdAAMADwA4AAAA/QAKAB0ABAAPADkA AAD9AAoAHgAA
AA8ABQAAAP0ACgAeAAEADwAnAAAA/QAKAB4AAgAPACgAAAD9AAoAHgADAA8A OAAAAP0ACgAe
AAQADwA6AAAA/QAKAB8AAAAPAAUAAAD9AAoAHwABAA8AJwAAAP0ACgAfAAIA DwAoAAAA/QAK
AB8AAwAPADgAAAD9AAoAHwAEAA8AOwAAANcARABACwAAbAJGAEYARgBGAEYA RgBGAEYARgBG
AEYARgBGAEYARgBGAEYARgBGAEYARgBGAEYARgBGAEYARgBGAEYARgBGAAgC EAAgAAAABQD/
AAAAAAAAAQ8ACAIQACEAAAAFAP8AAAAAAAABDwAIAhAAIgAAAAUA/wAAAAAA AAEPAAgCEAAj
AAAABQD/AAAAAAAAAQ8ACAIQACQAAAAFAP8AAAAAAAABDwD9AAoAIAAAAA8A BQAAAP0ACgAg
AAEADwAnAAAA/QAKACAAAgAPACgAAAD9AAoAIAADAA8APAAAAP0ACgAgAAQA DwA9AAAA/QAK
ACEAAAAPAAUAAAD9AAoAIQABAA8AJwAAAP0ACgAhAAIADwAoAAAA/QAKACEA AwAPAD4AAAD9
AAoAIQAEAA8APwAAAP0ACgAiAAAADwAFAAAA/QAKACIAAQAPACcAAAD9AAoA IgACAA8AKAAA
AP0ACgAiAAMADwBAAAAA/QAKACIABAAPAEEAAAD9AAoAIwAAAA8ABQAAAP0A CgAjAAEADwAn
AAAA/QAKACMAAgAPACgAAAD9AAoAIwADAA8AQgAAAP0ACgAjAAQADwBDAAAA /QAKACQAAAAP
AAUAAAD9AAoAJAABAA8AJwAAAP0ACgAkAAIADwAoAAAA/QAKACQAAwAPAEQA AAD9AAoAJAAE
AA8ARQAAANcADgDCAQAAUABGAEYARgBGAD4CEgC2BgAAAABAAAAAAAAAAAAA AAAdAA8AAwAA
BAAAAAEAAAAAAAQE7wAGAAAANwAAAAoAAAAJCBAAAAYQAEwfzQfBwAAABgMA AAsCEAAAAAAA
AAAAAAAAAADIIAAADQACAAEADAACAGQADwACAAEAEQACAAAAEAAIAPyp8dJN YlA/XwACAAEA
KgACAAAAKwACAAAAggACAAEAgAAIAAAAAAAAAAAAJQIEAAAA/wCBAAIAwQQU AAAAFQAAAIMA
AgAAAIQAAgAAAKEAIgAAAP8AAQABAAEABAAABAQEAAAAAAAA4D8AAAAAAADg PwAAVQACAAgA
AAIOAAAAAAAAAAAAAAAAAAAAPgISALYAAAAAAEAAAAAAAAAAAAAAAB0ADwAD AAAAAAAAAQAA
AAAAAADvAAYAAAA3AAAACgAAAAkIEAAABhAATB/NB8HAAAAGAwAACwIQAAAA AAAAAAAAAAAA
AM8hAAANAAIAAQAMAAIAZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIA AQAqAAIAAAAr
AAIAAACCAAIAAQCAAAgAAAAAAAAAAAAlAgQAAAD/AIEAAgDBBBQAAAAVAAAA gwACAAAAhAAC
AAAAoQAiAAAA/wABAAEAAQAEAAAAAAAAAAAAAADgPwAAAAAAAOA/AABVAAIA CAAAAg4AAAAA
AAAAAAAAAAAAAAA+AhIAtgAAAAAAQAAAAAAAAAAAAAAAHQAPAAMAAAAAAAAB AAAAAAAAAO8A
BgAAADcAAAAKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAD+/wAABQACAAAAAAAAAAAAAAAAAAAAAAABAAAA4IWf8vlPaBCr kQgAKyez2TAA
AAC4AAAABwAAAAEAAABAAAAABAAAAEgAAAAIAAAAZAAAABIAAACAAAAADAAA AJgAAAANAAAA
pAAAABMAAACwAAAAAgAAAOQEAAAeAAAAFAAAAEpvZWwgUm9zaS1TY2h3YXJ0 egAAHgAAABQA
AABKb2VsIFJvc2ktU2Nod2FydHoAAB4AAAAQAAAATWljcm9zb2Z0IEV4Y2Vs AEAAAACAckp9
XmXGAUAAAACAGh/TXmXGAQMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
/v8AAAUAAgAAAAAAAAAAAAAAAAAAAAAAAQAAAALVzdWcLhsQk5cIACss+a4w AAAA5AAAAAkA
AAABAAAAUAAAAA8AAABYAAAAFwAAAHAAAAALAAAAeAAAABAAAACAAAAAEwAA AIgAAAAWAAAA
kAAAAA0AAACYAAAADAAAAMEAAAACAAAA5AQAAB4AAAAQAAAARXRpc2ggTGlt aXRlZAAAAAMA
AACoGQsACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAAeEAAAAwAA AAcAAABTaGVl
dDEABwAAAFNoZWV0MgAHAAAAU2hlZXQzAAwQAAACAAAAHgAAAAsAAABXb3Jr c2hlZXRzAAMA
AAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAEAAAACAAAA
AwAAAAQAAAAFAAAABgAAAAcAAAAIAAAACQAAAAoAAAALAAAADAAAAA0AAAAO AAAADwAAABAA
AAARAAAA/v///xMAAAAUAAAAFQAAABYAAAAXAAAAGAAAABkAAAD+////GwAA ABwAAAAdAAAA
HgAAAB8AAAAgAAAAIQAAAP7////9/////v////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
//////////////////////////////////////////////////////////// ////////////
////////////////////////UgBvAG8AdAAgAEUAbgB0AHIAeQAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYABQH//////////wIAAAAg CAIAAAAAAMAA
AAAAAABGAAAAAAAAAAAAAAAAAAAAAAAAAAD+////AAAAAAAAAABXAG8AcgBr AGIAbwBvAGsA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAEgACAf//
/////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAeIgAA
AAAAAAUAUwB1AG0AbQBhAHIAeQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4AAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAoAAIBAQAAAAMAAAD/////AAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA
AAAAAAAAAAAAAAAAEgAAAAAQAAAAAAAABQBEAG8AYwB1AG0AZQBuAHQAUwB1 AG0AbQBhAHIA
eQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4AAAAAAAAAAAAAADgAAgH///////// //////8AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaAAAAABAAAAAAAAA=
--------------010306090704060707080108--
|
|
|
| Re: Select items by name in AGR macro [message #67910 is a reply to message #67430] |
Mon, 24 April 2006 19:42 |
No real name
Messages: 404
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0012_01C667B5.B7F07B10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
It appears that your driver is outdated. You need to use a recent =
development SDK build before downloading the auto gui plug-in from CVS. =
From the first few messages, it seemed like =
"org.eclipse.hyades.test.tools.ui" was outdated.
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message =
news:e2b0ms$j62$1@utils.eclipse.org...
I know you said just the first ten, but it was just easy to past all =
of them into excel so I you get the lot at no extra cost ;-)=20
Let me know if there is anything else I can do to assist.
Cheers,
Joel
Ali Mehregani wrote:=20
Can you tell me what the unresolved errors are (just the first 10 of =
them)?
Thanks.
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in =
message news:e2356b$t9c$1@utils.eclipse.org...
Thanks Ali. I have done as you suggest and imported =
org.eclipse.tptp.test.auto.gui. I still have 36 "unresolved errors" in =
the workspace. For the moment that is not a problem, because I really =
only needed the source for the Resolvers that you mentioned so Barbara =
can have a look at them. In the long run, though, I would like to be =
able to have buildable source. Perhaps when you have time :-D you =
could put clear source procurement instructions into the the Guide.
Much thanks,
Joel
Ali Mehregani wrote:=20
I would recommend using a TPTP SDK driver when importing the =
auto gui plug-in. That way you'll only need to extract the auto gui =
plug-in from CVS and Eclipse should automatically use the TPTP plug-ins =
under the plug-in folder to resolve its dependencies.
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in =
message news:e20smf$pte$1@utils.eclipse.org...
Hi Ali,
Ali Mehregani wrote:=20
Hi Barbara4) If I go the custom widget resolver class route, I don't =
understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example =
implementation?
A similar question applies to the addition of <class> elements to the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
=20
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver=
OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
Is there an easy way to get the source for AGR. I find that to pull =
down all of AGR from cvs pretty much requires getting all of TPTP. =
(Please correct me if this is not correct.) This can be pretty gruesome =
and slow going. I have downloaded the TPTP sdk download for 4.2, but =
this does not seem to contain AGR source features, which makes sense =
since AGR is not yet "official" :-( Any suggestions?
Thanks,
Joel
------=_NextPart_000_0012_01C667B5.B7F07B10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.2800.1543" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>It appears that your driver is =
outdated. You=20
need to use a recent development SDK build before downloading the auto =
gui=20
plug-in from CVS. From the first few messages, it seemed like=20
"org.eclipse.hyades.test.tools.ui" was outdated.</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Joel Rosi-Schwartz" <<A=20
=
href=3D"mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org=
</A>>=20
wrote in message <A=20
=
href=3D"news:e2b0ms$j62$1@utils.eclipse.org">news:e2b0ms$j62$1@utils.ecli=
pse.org</A>...</DIV><FONT=20
face=3D"Helvetica, Arial, sans-serif">I know you said just the first =
ten, but it=20
was just easy to past all of them into excel so I you get the lot at =
no extra=20
cost <SPAN class=3Dmoz-smiley-s3><SPAN>;-) </SPAN></SPAN><BR><BR>Let =
me know if=20
there is anything else I can do to=20
assist.<BR><BR>Cheers,<BR>Joel<BR></FONT><BR>Ali Mehregani wrote:=20
<BLOCKQUOTE cite=3Dmide2as1k$3b6$1@utils.eclipse.org type=3D"cite">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR>
<DIV>
<DIV><FONT face=3DArial size=3D2>Can you tell me what the unresolved =
errors are=20
(just the first 10 of them)?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks.</FONT></DIV></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Joel Rosi-Schwartz" <<A=20
=
href=3D"mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org=
</A>>=20
wrote in message <A=20
=
href=3D"news:e2356b$t9c$1@utils.eclipse.org">news:e2356b$t9c$1@utils.ecli=
pse.org</A>...</DIV><FONT=20
face=3D"Helvetica, Arial, sans-serif">Thanks Ali. I have =
done as you=20
suggest and imported org.eclipse.tptp.test.auto.gui. I still have =
36=20
"unresolved errors" in the workspace. For the moment that is not a =
problem, because I really only needed the source for the Resolvers =
that=20
you mentioned so Barbara can have a look at them. In the long run, =
though,=20
I would like to be able to have buildable source. Perhaps when you =
have=20
time <SPAN class=3Dmoz-smiley-s5><SPAN>:-D =
</SPAN></SPAN> you=20
could put clear source procurement instructions into the the=20
Guide.<BR><BR>Much thanks,<BR>Joel<BR></FONT><BR>Ali Mehregani =
wrote:=20
<BLOCKQUOTE cite=3Dmide231aj$amn$1@utils.eclipse.org =
type=3D"cite">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR>
<STYLE></STYLE>
<DIV><FONT face=3DArial size=3D2>I would recommend using a TPTP =
SDK driver=20
when importing the auto gui plug-in. That way you'll only =
need to=20
extract the auto gui plug-in from CVS and Eclipse should =
automatically=20
use the TPTP plug-ins under the plug-in folder to resolve its=20
dependencies.</FONT></DIV>
<DIV> </DIV>
<DIV>"Joel Rosi-Schwartz" <<A=20
=
href=3D"mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org=
</A>>=20
wrote in message <A=20
=
href=3D"news:e20smf$pte$1@utils.eclipse.org">news:e20smf$pte$1@utils.ecli=
pse.org</A>...</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px"><FONT=20
face=3D"Helvetica, Arial, sans-serif">Hi =
Ali,</FONT><BR><BR>Ali=20
Mehregani wrote:=20
<BLOCKQUOTE cite=3Dmide20999$b49$1@utils.eclipse.org =
type=3D"cite"><PRE wrap=3D"">Hi Barbara</PRE>
<BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">4) If I go the =
custom widget resolver class route, I don't understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example =
implementation?
A similar question applies to the addition of <class> elements to =
the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
</PRE></BLOCKQUOTE><PRE wrap=3D""><!---->
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver=
OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
</PRE></BLOCKQUOTE>Is there an easy way to get the source for AGR. I=20
find that to pull down all of AGR from cvs pretty much =
requires=20
getting all of TPTP. (Please correct me if this is not =
correct.) This=20
can be pretty gruesome and slow going. I have downloaded the =
TPTP sdk=20
download for 4.2, but this does not seem to contain AGR source =
features, which makes sense since AGR is not yet "official" =
:-( =20
Any=20
=
suggestions?<BR><BR>Thanks,<BR>Joel<BR></BLOCKQUOTE></BLOCKQUOTE ></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0012_01C667B5.B7F07B10--
|
|
|
| Re: Select items by name in AGR macro [message #68054 is a reply to message #67910] |
Tue, 25 April 2006 20:57 |
|
This is a multi-part message in MIME format.
--------------000207010904070602060305
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Thanks Ali that makes perfect sense. I am planning on updating in the
next couple of days to the TPTP 4.2 I2 Stable Build. Will that do the trick?
Cheers,
Joel
Ali Mehregani wrote:
> It appears that your driver is outdated. You need to use a recent
> development SDK build before downloading the auto gui plug-in from
> CVS. From the first few messages, it seemed like
> "org.eclipse.hyades.test.tools.ui" was outdated.
>
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org
> <mailto:Joel.Rosi-Schwartz@Etish.org>> wrote in message
> news:e2b0ms$j62$1@utils.eclipse.org...
> I know you said just the first ten, but it was just easy to past
> all of them into excel so I you get the lot at no extra cost ;-)
>
> Let me know if there is anything else I can do to assist.
>
> Cheers,
> Joel
>
> Ali Mehregani wrote:
>> Can you tell me what the unresolved errors are (just the first 10
>> of them)?
>> Thanks.
>>
>> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org
>> <mailto:Joel.Rosi-Schwartz@Etish.org>> wrote in message
>> news:e2356b$t9c$1@utils.eclipse.org...
>> Thanks Ali. I have done as you suggest and imported
>> org.eclipse.tptp.test.auto.gui. I still have 36 "unresolved
>> errors" in the workspace. For the moment that is not a
>> problem, because I really only needed the source for the
>> Resolvers that you mentioned so Barbara can have a look at
>> them. In the long run, though, I would like to be able to
>> have buildable source. Perhaps when you have time :-D you
>> could put clear source procurement instructions into the the
>> Guide.
>>
>> Much thanks,
>> Joel
>>
>> Ali Mehregani wrote:
>>> I would recommend using a TPTP SDK driver when importing the
>>> auto gui plug-in. That way you'll only need to extract the
>>> auto gui plug-in from CVS and Eclipse should automatically
>>> use the TPTP plug-ins under the plug-in folder to resolve
>>> its dependencies.
>>>
>>> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org
>>> <mailto:Joel.Rosi-Schwartz@Etish.org>> wrote in message
>>> news:e20smf$pte$1@utils.eclipse.org...
>>>
>>> Hi Ali,
>>>
>>> Ali Mehregani wrote:
>>>> Hi Barbara
>>>>> 4) If I go the custom widget resolver class route, I don't understand
>>>>> clearly how to implement my IWidgetResolver class: do I need one class
>>>>> per widget? Or per widget type? Can you provide an example implementation?
>>>>> A similar question applies to the addition of <class> elements to the
>>>>> widgetReg.xml file: do I need one per physical widget or one per widget
>>>>> type?
>>>>>
>>>>
>>>> For widget resolver class, see
>>>> org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
>>>> org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
>>>> For widgetReg.xml, read the internal document.
>>>>
>>> Is there an easy way to get the source for AGR. I find
>>> that to pull down all of AGR from cvs pretty much
>>> requires getting all of TPTP. (Please correct me if this
>>> is not correct.) This can be pretty gruesome and slow
>>> going. I have downloaded the TPTP sdk download for 4.2,
>>> but this does not seem to contain AGR source features,
>>> which makes sense since AGR is not yet "official" :-(
>>> Any suggestions?
>>>
>>> Thanks,
>>> Joel
>>>
--------------000207010904070602060305
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Thanks Ali that makes perfect
sense. I am planning on updating in the next couple of days to the TPTP
4.2 I2 Stable Build. Will that do the trick?<br>
<br>
Cheers,<br>
Joel<br>
</font><br>
Ali Mehregani wrote:
<blockquote cite="mide2j9oa$j9f$1@utils.eclipse.org" type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2800.1543" name="GENERATOR">
<div><font face="Arial" size="2">It appears that your driver is
outdated. You need to use a recent development SDK build before
downloading the auto gui plug-in from CVS. From the first few
messages, it seemed like "org.eclipse.hyades.test.tools.ui" was
outdated.</font></div>
<div> </div>
<blockquote dir="ltr"
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div>"Joel Rosi-Schwartz" <<a
href="mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org</a>>
wrote in message <a href="news:e2b0ms$j62$1@utils.eclipse.org">news:e2b0ms$j62$1@utils.eclipse.org</a>...</div>
<font face="Helvetica, Arial, sans-serif">I know you said just the
first ten, but it was just easy to past all of them into excel so I you
get the lot at no extra cost <span class="moz-smiley-s3"><span>;-) </span></span><br>
<br>
Let me know if there is anything else I can do to assist.<br>
<br>
Cheers,<br>
Joel<br>
</font><br>
Ali Mehregani wrote:
<blockquote cite="mide2as1k$3b6$1@utils.eclipse.org" type="cite">
<meta content="MSHTML 6.00.2800.1528" name="GENERATOR">
<div>
<div><font face="Arial" size="2">Can you tell me what the
unresolved errors are (just the first 10 of them)?</font></div>
<div><font face="Arial" size="2">Thanks.</font></div>
</div>
<blockquote dir="ltr"
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div>"Joel Rosi-Schwartz" <<a
href="mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org</a>>
wrote in message <a href="news:e2356b$t9c$1@utils.eclipse.org">news:e2356b$t9c$1@utils.eclipse.org</a>...</div>
<font face="Helvetica, Arial, sans-serif">Thanks Ali. I have
done as you suggest and imported org.eclipse.tptp.test.auto.gui. I
still have 36 "unresolved errors" in the workspace. For the moment that
is not a problem, because I really only needed the source for the
Resolvers that you mentioned so Barbara can have a look at them. In the
long run, though, I would like to be able to have buildable source.
Perhaps when you have time <span class="moz-smiley-s5"><span>:-D </span></span>
you could put clear source procurement instructions into the the Guide.<br>
<br>
Much thanks,<br>
Joel<br>
</font><br>
Ali Mehregani wrote:
<blockquote cite="mide231aj$amn$1@utils.eclipse.org" type="cite">
<meta content="MSHTML 6.00.2800.1528" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">I would recommend using a
TPTP SDK driver when importing the auto gui plug-in. That way you'll
only need to extract the auto gui plug-in from CVS and Eclipse should
automatically use the TPTP plug-ins under the plug-in folder to resolve
its dependencies.</font></div>
<div> </div>
<div>"Joel Rosi-Schwartz" <<a
href="mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org</a>>
wrote in message <a href="news:e20smf$pte$1@utils.eclipse.org">news:e20smf$pte$1@utils.eclipse.org</a>...</div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"><font
face="Helvetica, Arial, sans-serif">Hi Ali,</font><br>
<br>
Ali Mehregani wrote:
<blockquote cite="mide20999$b49$1@utils.eclipse.org"
type="cite">
<pre wrap="">Hi Barbara</pre>
<blockquote type="cite">
<pre wrap="">4) If I go the custom widget resolver class route, I don't understand
clearly how to implement my IWidgetResolver class: do I need one class
per widget? Or per widget type? Can you provide an example implementation?
A similar question applies to the addition of <class> elements to the
widgetReg.xml file: do I need one per physical widget or one per widget
type?
</pre>
</blockquote>
<pre wrap=""><!---->
For widget resolver class, see
org.eclipse.tptp.test.auto.gui.internal.recorder.NonTrivialW idgetResolver OR
org.eclipse.tptp.test.auto.gui.internal.recorder.AdaptiveWid getResolver.
For widgetReg.xml, read the internal document.
</pre>
</blockquote>
Is there an easy way to get the source for AGR. I find that to pull
down all of AGR from cvs pretty much requires getting all of TPTP.
(Please correct me if this is not correct.) This can be pretty gruesome
and slow going. I have downloaded the TPTP sdk download for 4.2, but
this does not seem to contain AGR source features, which makes sense
since AGR is not yet "official" :-( Any suggestions?<br>
<br>
Thanks,<br>
Joel<br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--------------000207010904070602060305--
|
|
|
Goto Forum:
Current Time: Tue Apr 23 06:36:53 GMT 2024
Powered by FUDForum. Page generated in 0.04074 seconds |
] 
Search
Help
Register
Login
Home
