-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx
[mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf
Of Recoskie, Chris
Sent: Friday, October 01, 2004
12:02 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Visual Editor
and CDT GUIs
So, the Visual Editor Project recently released version 1.0,
and I’ve been trying it out. Overall, I’ve been pretty
impressed, but it in essence it can’t be used to work with the existing
Eclipse and CDT GUIs because it’s unable to parse the original,
hand-written code.
I am wondering if we should consider the notion of making
any new GUIs VEP compatible wherever possible. This would make things
theoretically faster/easier for us to create, and also easier for new
developers to get up to speed modifying our GUIs.
Basically what this would mean is you would create your GUI
as a single SWT Composite object in SWT, then use that in whatever parent
object (e.g. dialog, property page, view, etc.) as necessary to keep the
Eclipse infrastructure happy. This adds an additional layer to the code,
but at the same time has its benefits by virtue of the VEP.
Thoughts?
___________________________________________
Chris Recoskie
Texas Instruments, Toronto