IDE TF Minutes 2007-06-28
Attendees this week
- Jon Ferraiolo <jferrai(at)us.ibm.com>
- Ingo Muschenetz <ingo(at)aptana.com>
- Kevin Hakman <khakman(at)tibco.com>
- Phil Berkland <berkland(at)us.ibm.com> representing Eclipse ATF project
CONTROLS AND APIS There was much discussion per Jon's comments in teh general section of the requirements that the requirements were perhap light on metadata for APIs. This led to some additional nomenclature clarification generally summarized as:
Libraries contain controls and APIs. Controls have APIs. In some cases APIs may not be associated with a Control or Library: e.g. when there's an extension to a standard language object, or in the case of a stand-alone function that's not part of a contining package.
Kevin argued that everything wa a control including "when there's an extension to a standard language object, or in the case of a stand-alone function that's not part of a contining package", but on Jon and Ingo's arguments that perhaps the distinction would be more intuitive to users. On that Kevin agreed.
Jon committed to edit the content to add the notion of "API" where there were existing instances of "Control" and where it made sense to do so.
Jon, Kevin, Ingo also discussed that IDEs often provide a means to instance a control visually. For exmaple TIBCO General Interface Builder has a notion of "prototypes" which you can populate a visual pallete with then WYSIWYG drop into place in a canvas. jMaki has the idea of snippets -- code that gets you statred with creating an instance with defult values set that you can overrride and change. Eclipse ATF has wizards to register component libraries and create instance data and editable snippets. Most IDEs have editable property sheets.
In addition there's the use case of coding a GUI from scratch or starting with some sort of snippet of code. Usually the IDE, as in the case of Aptana and others, provides some sort of type-ahead and option selection capabilities to assist in the code completion and provide assitance with the signatures and parameters for API methods and properties whther to controls or mere functions.
The metadata SHOULD cover both of these cases.
Kevin said he'd not be able to attend next week. Jon said that next week was bad for many. So the next meeting is July 12th. Same time. Same dial-in numbers.