RE: [cdt-dev] Visual Editor and CDT GUIs

["Lott, Jeremiah" <jeremiah.lott@xxxxxxxxxxx>]

Title: Message

I wouldn't really like it if it became a requirement to use the Visual Editor to contribute to CDT UI development (although I could live with it if the majority want that).  Are there other requirements as to the coding style that has to be used to be compatable with the VEP?  I'd like to see that the requirements on the coding-style are well-defined so that people who aren't using the VEP can also contribute.

 

  Jeremiah

-----Original Message-----
From: Recoskie, Chris [mailto:crecoskie@xxxxxx]
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

Software Designer

IDE Frameworks Group

Texas Instruments, Toronto