|
|
| Re: TPTP User Interface [message #72417 is a reply to message #70199] |
Wed, 31 May 2006 12:38   |
 Bertrand Quenin
Messages: 70
Registered: July 2009 |
Member |
|
|
Hi Ali,
Thanks for your answer ! But it seems that i'm still in an dead-end
concerning TPTP ui extensions. On one hand, I can use the deprecated API
that will be replaced in the future (understand that my potential
evolutions are useless) and on the other hand I have the "hidden"
*.internal.*.*Forms API, that seems to be the one which is going to
replace the former, but which is moving all the time (numerous differences
between 4.1 and 4.2 for example).
So i'm still wondering how I could achieve my evolutions without being
forced to rewrite (refactor) them in the future ...
I think i'm going to use the later and stay on the 4.1 build (it seems
that 4.2 won't be available before the end of summer).
Another thing that's annoying: AutoGUI sources are not available for
download in a standalone package (only on CVS) which is really disturbing
for me as i only have an HTTP access. It's a really good sample for what i
want to achieve and it's really harrasing to browse the CVS HTTP interface
anf get files one after another.
Regards.
BQ.
Ali Mehregani wrote:
> Hi Bertrand,
> You're right. I wasn't involved in TPTP when many of its APIs were
> deprecated but no alternatives were offered for contributors to use. During
> the time when I was creating the automated GUI test type, I figured out a
> new way to use Eclipse forms in TPTP editors. So I ended up spending weeks
> re-writing some code to beef up my editor's look and feel. The new APIs
> that I introduced are all internal and I suspect that they would stay
> internal until its requested for them to be moved to a provisional package.
> You can find the code for the auto GUI runner under the following plug-in:
> org.eclipse.tptp.test.auto.gui. The editor code is under the following
> package: org.eclipse.tptp.test.auto.gui.internal.editor
> Chances are that you'll still be pretty safe using the deprecated APIs.
> It's very unlikely for these APIs to be pulled out anytime soon. I have
> opened the following defect in the hopes of the code to be refactored
> sometime in the future:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=101922
> "Bertrand Quenin" <bquenin@axway.com> wrote in message
> news:dc6f7e9b3b1181013100e3caf930461f$1@www.eclipse.org...
>> Hi All,
>>
>> I'm here again with some questions about TPTP UI. As i'm a rigorous
>> person, i read the TPTP tutorial from EclipseCon 2005 (#6 Build a custom
>> test environment) and eveerything works fine. But i'm a bit confused about
>> UI programming; Indeed, all TPTP "widgets" use deprecated APIs and there's
>> no information about what to use instead of these deperecated APIs. I'm
>> using TPTP 4.1 and it seems to be the same in TPTP 4.2.
>> Extending the TPTP UI seems to be useless considering that the UI
>> framework will be rebranded soon to Eclipse Forms 3.X (as soon as the
>> graphic editor is ready). So here are my questions:
>> - Should i extend the current TPTP UI framework by using all these
>> deprecated methods ?
>> - Can i mix current TPTP UI widgets with Eclipse Forms one (that i
>> must create, of course) ?
>> - If mixing widgets is impossible, does it mean that i have to redraw
>> all existing widgets to eclipse forms if i want to use them ?
>>
>> I'm curretly thinking to extend the current TPTP UI framework anyway,
>> but i'm wondering if it's a good idea or not. The ideal solution would to
>> be able to mix existing widgets and new ones written in eclipse forms.
>> This would avoid rewriting all the new widgets on future realease of TPTP
>> (the one with Eclipse forms inside).
>> Or perhaps there's already something replacing the deprecated API that
>> i haven't found already.
>>
>> Any solutions would be greatly appreciated =)
>>
>> Thanks
>> BQ.
>>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03122 seconds
] 
Search
Help
Register
Login
Home
