Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » [AGR] Widget relative position based recording and playback
[AGR] Widget relative position based recording and playback [message #121194] Tue, 22 January 2008 20:20 Go to next message
Jimmy Jin is currently offline Jimmy Jin
Messages: 32
Registered: July 2009
Member
I just encountered a case that I need to simulate a click on a CLabel
control in my AGR script. Current position based recording in AGR only
store the coordinates to the Display. If I just use this way, then if
the CLabel's position has some change, then the script will not work. So
I'm thinking that why the position based recording and playback cannot
be relative to the widget?

I did some try by modifying the AGR code, to:
1. When doing position based recording, resolve the widget coming
together with the event in the same way as normal recording, and store
the information.
2. Change the coordinates to relative to the widget.
3. Save the widget ContextId and WidgetId in the position based command,
such as mouse-click, together with the coordinates relative to the widget.
4. When playback, find the widget according to the ContextId and
WidgetId, and then calculate the coordinates to the display. Then post
the event to the display.

In this way, no matter what widget, you can always record actions like
mouse click and playback it.

I think this may be a good enhancement to the AGR tool. Any comments
from anyone?

Regards,
Jimmy Jin
Re: [AGR] Widget relative position based recording and playback [message #121246 is a reply to message #121194] Wed, 23 January 2008 11:37 Go to previous messageGo to next message
Paul Slauenwhite is currently offline Paul Slauenwhite
Messages: 970
Registered: July 2009
Senior Member
Hi Jimmy,
This strategy would help decrease the brittleness of positional-based
recordings, assuming the widget (actually its parent) can be resolved during
playback. For example, mouse click within a GEF canvas. Unfortunately, in
TPTP 4.5, the AGR was moved from a Technology Preview component to an As-Is
component. As-Is components are primarily provided for prior users but
imply no enhancements or support (for example, defects, news group, and
mailing lists). Would you or your company be interested in contributing
this feature?

Paul
"Jimmy Jin" <jimmyjin.jxm@gmail.com> wrote in message
news:fn5j5b$lmh$1@build.eclipse.org...
>I just encountered a case that I need to simulate a click on a CLabel
>control in my AGR script. Current position based recording in AGR only
>store the coordinates to the Display. If I just use this way, then if the
>CLabel's position has some change, then the script will not work. So I'm
>thinking that why the position based recording and playback cannot be
>relative to the widget?
>
> I did some try by modifying the AGR code, to:
> 1. When doing position based recording, resolve the widget coming together
> with the event in the same way as normal recording, and store the
> information.
> 2. Change the coordinates to relative to the widget.
> 3. Save the widget ContextId and WidgetId in the position based command,
> such as mouse-click, together with the coordinates relative to the widget.
> 4. When playback, find the widget according to the ContextId and WidgetId,
> and then calculate the coordinates to the display. Then post the event to
> the display.
>
> In this way, no matter what widget, you can always record actions like
> mouse click and playback it.
>
> I think this may be a good enhancement to the AGR tool. Any comments from
> anyone?
>
> Regards,
> Jimmy Jin
Re: [AGR] Widget relative position based recording and playback [message #121360 is a reply to message #121246] Thu, 24 January 2008 20:31 Go to previous messageGo to next message
Jimmy Jin is currently offline Jimmy Jin
Messages: 32
Registered: July 2009
Member
Hi, Paul,

I will consider to contribute some of our fixes. Many fixes I did is
mostly focusing on accommodating the scenarios in our application,
rather than a very common scenario, so I'm not sure if they are good
ones to contribute to the public release of AGR. If I provide the patch,
who will review the code? Who will be in charge of deciding whether to
take or not take the fix into new releases?

BTW, I looked at the current Bugzilla entries of AGR and found lots of
them are "wont fix". If I found some defect, and entered into Bugzilla,
will that also be just simply changed to "wont fix"? What if someone
else can provide the fix for the defect?

So, a more general question in my mind: what practically will be needed
to keep AGR tool to still continue to be maintained and developed as a
project? What is/will be still available now/in future for it as an
"As-is" project?

Thanks,
Jimmy Jin

Paul Slauenwhite wrote:
> Hi Jimmy,
> This strategy would help decrease the brittleness of positional-based
> recordings, assuming the widget (actually its parent) can be resolved during
> playback. For example, mouse click within a GEF canvas. Unfortunately, in
> TPTP 4.5, the AGR was moved from a Technology Preview component to an As-Is
> component. As-Is components are primarily provided for prior users but
> imply no enhancements or support (for example, defects, news group, and
> mailing lists). Would you or your company be interested in contributing
> this feature?
>
> Paul
> "Jimmy Jin" <jimmyjin.jxm@gmail.com> wrote in message
> news:fn5j5b$lmh$1@build.eclipse.org...
>> I just encountered a case that I need to simulate a click on a CLabel
>> control in my AGR script. Current position based recording in AGR only
>> store the coordinates to the Display. If I just use this way, then if the
>> CLabel's position has some change, then the script will not work. So I'm
>> thinking that why the position based recording and playback cannot be
>> relative to the widget?
>>
>> I did some try by modifying the AGR code, to:
>> 1. When doing position based recording, resolve the widget coming together
>> with the event in the same way as normal recording, and store the
>> information.
>> 2. Change the coordinates to relative to the widget.
>> 3. Save the widget ContextId and WidgetId in the position based command,
>> such as mouse-click, together with the coordinates relative to the widget.
>> 4. When playback, find the widget according to the ContextId and WidgetId,
>> and then calculate the coordinates to the display. Then post the event to
>> the display.
>>
>> In this way, no matter what widget, you can always record actions like
>> mouse click and playback it.
>>
>> I think this may be a good enhancement to the AGR tool. Any comments from
>> anyone?
>>
>> Regards,
>> Jimmy Jin
>
>
Re: [AGR] Widget relative position based recording and playback [message #121417 is a reply to message #121360] Fri, 25 January 2008 17:55 Go to previous message
Paul Slauenwhite is currently offline Paul Slauenwhite
Messages: 970
Registered: July 2009
Senior Member
Hi Jimmy,
If you are interested in contributing patch(es), please read the Eclipse
Legal Process (http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf)
and attach the patch(es) to the Bugzilla(s). The component owner will
review and determine if they are suitable for integration. If suitable,
they will handle the integration.

We have returned all current AGR Bugillas as WONTFIX. If the community
wants to contribute patch(es), they can reopen the Bugzila(s) and attach the
patch(es).

We have sized the maintenance costs at roughly 0.5 Person Year (PY).
Currently, there are no plans for move the AGR out of its As-Is status.

Paul
"Jimmy Jin" <jimmyjin.jxm@gmail.com> wrote in message
news:fnasjl$r2s$1@build.eclipse.org...
> Hi, Paul,
>
> I will consider to contribute some of our fixes. Many fixes I did is
> mostly focusing on accommodating the scenarios in our application, rather
> than a very common scenario, so I'm not sure if they are good ones to
> contribute to the public release of AGR. If I provide the patch, who will
> review the code? Who will be in charge of deciding whether to take or not
> take the fix into new releases?
>
> BTW, I looked at the current Bugzilla entries of AGR and found lots of
> them are "wont fix". If I found some defect, and entered into Bugzilla,
> will that also be just simply changed to "wont fix"? What if someone else
> can provide the fix for the defect?
>
> So, a more general question in my mind: what practically will be needed to
> keep AGR tool to still continue to be maintained and developed as a
> project? What is/will be still available now/in future for it as an
> "As-is" project?
>
> Thanks,
> Jimmy Jin
>
> Paul Slauenwhite wrote:
>> Hi Jimmy,
>> This strategy would help decrease the brittleness of positional-based
>> recordings, assuming the widget (actually its parent) can be resolved
>> during playback. For example, mouse click within a GEF canvas.
>> Unfortunately, in TPTP 4.5, the AGR was moved from a Technology Preview
>> component to an As-Is component. As-Is components are primarily provided
>> for prior users but imply no enhancements or support (for example,
>> defects, news group, and mailing lists). Would you or your company be
>> interested in contributing this feature?
>>
>> Paul
>> "Jimmy Jin" <jimmyjin.jxm@gmail.com> wrote in message
>> news:fn5j5b$lmh$1@build.eclipse.org...
>>> I just encountered a case that I need to simulate a click on a CLabel
>>> control in my AGR script. Current position based recording in AGR only
>>> store the coordinates to the Display. If I just use this way, then if
>>> the CLabel's position has some change, then the script will not work. So
>>> I'm thinking that why the position based recording and playback cannot
>>> be relative to the widget?
>>>
>>> I did some try by modifying the AGR code, to:
>>> 1. When doing position based recording, resolve the widget coming
>>> together with the event in the same way as normal recording, and store
>>> the information.
>>> 2. Change the coordinates to relative to the widget.
>>> 3. Save the widget ContextId and WidgetId in the position based command,
>>> such as mouse-click, together with the coordinates relative to the
>>> widget.
>>> 4. When playback, find the widget according to the ContextId and
>>> WidgetId, and then calculate the coordinates to the display. Then post
>>> the event to the display.
>>>
>>> In this way, no matter what widget, you can always record actions like
>>> mouse click and playback it.
>>>
>>> I think this may be a good enhancement to the AGR tool. Any comments
>>> from anyone?
>>>
>>> Regards,
>>> Jimmy Jin
>>
Previous Topic:Cant bring BIRT reports to work with TPTP profiler.
Next Topic:TPTP & jre 1.6
Goto Forum:
  


Current Time: Thu Oct 30 14:30:17 GMT 2014

Powered by FUDForum. Page generated in 0.02205 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software