[OpenAjaxIDE] IDE requirements matrix wiki page

Bertrand Le Roy Bertrand.Le.Roy at microsoft.com
Fri Aug 24 18:54:01 PDT 2007


Understood. I agree, but I would add that our own code comment format is also widely used even if it’s not necessarily very visible from your point of view, so I’d greatly appreciate if the symmetric requirement to the one about JSDoc could be included too.
I’ll be on next call.

Thanks,
Bertrand

From: Jon Ferraiolo [mailto:jferrai at us.ibm.com]
Sent: Friday, August 24, 2007 6:49 PM
To: Bertrand Le Roy
Cc: ide at openajax.org
Subject: RE: [OpenAjaxIDE] IDE requirements matrix wiki page


Hi Bertrand,
My thinking is that the comparison table is informational and educational but not deterministic about which technical direction we would go. The table will help us understand the metadata formats that people are using and it will help us see if we left out any key requirements.

In terms of how we might proceed, we could:

(a) Use one of the existing industry metadata formats as a starting point, from which we (undoubtedly) make changes
(b) Invent something new from scratch

Option (a) seems more attractive to me because we probably can move more quickly with (a) both in terms of completing a specification and in achieving at least one implementation.

I recommend that we have discussions soon about the criteria we use in evaluating existing metadata formats for suitability. You list four criteria below. I would add three others:

* Good workflow with Ajax libraries that use JSDoc - There are a good number of Ajax libraries, particularly some of the most popular ones, that use JSDoc to document their APIs. The whole point of our initiative is to allow IDEs to do good things with these Ajax libraries, so compatibility with what is used today is important.

* Open source reference implementation(s) - At OpenAjax Alliance, if at all possible, at the same time we deliver a specification, we also make sure that there is open source available so that (most of) the world can work with things immediately. For example, with the OpenAjax Hub, we have both a specification and our own open source.

* Can be supported reasonably by the IDEs that have been represented in this WG

Will you be available for the phone call this week or are you still on leave?

Jon

Jon Ferraiolo <jferrai at us.ibm.com>
Web Architect, Emerging Technologies
IBM, Menlo Park, CA
Mobile: +1-650-926-5865

[cid:image001.gif at 01C7E680.222F5C40]Bertrand Le Roy <Bertrand.Le.Roy at microsoft.com>

Bertrand Le Roy <Bertrand.Le.Roy at microsoft.com>

08/24/2007 12:28 PM


To


Jon Ferraiolo/Menlo Park/IBM at IBMUS, "ide at openajax.org" <ide at openajax.org>


cc




Subject


RE: [OpenAjaxIDE] IDE requirements matrix wiki page








I did what I could but I’m not sure what we’re trying to achieve here.
We have a list of requirements which encapsulate where we want to go, and we have a number of existing formats, none of which is the one we want exactly. We know it’s going to take work to get where we want to go. The different requirements are not weighed except for the MUST/SHOULD/MAY, but some MUSTs are much more important than others. There is a number of other things the list doesn’t capture:
• Is the format already being used and tested against real-world, large-scale applications and how well does it do?
• Is the scope just Ajax applications or is it broader (other languages and environments)?
• How many of the requirements could be satisfied through a simple extensibility feature? Should the most Ajax-specific features be simple extensions?
• How flexible is the format? I mean by that flexible as a format but also is each owner completely open to modifications?
What we need to find is which format will be the easiest to steer into our goals, which is not necessarily the same as asking which format satisfies the most requirements today.

Thanks,
Bertrand

From: ide-bounces at openajax.org [mailto:ide-bounces at openajax.org] On Behalf Of Jon Ferraiolo
Sent: Friday, August 24, 2007 10:26 AM
To: ide at openajax.org
Subject: Re: [OpenAjaxIDE] IDE requirements matrix wiki page

Oops. I forgot to include the URL:

http://www.openajax.org/member/wiki/IDE/requirements_matrix

Jon

----- Forwarded by Jon Ferraiolo/Menlo Park/IBM on 08/24/2007 10:25 AM -----
Jon Ferraiolo/Menlo Park/IBM

08/24/2007 10:25 AM

To


ide at openajax.org

cc



Subject


IDE requirements matrix wiki page









Hi everyone,
I have created a wiki page that has a table that lists all of our IDE requirements in as row headers and has column headers for "Adobe", "Aptana", "jMaki" and "Microsoft". The idea is that we can see at a glance how some existing metadata formats align versus the requirements we have identified.

Definitely feel free to relabel columns, delete columns, or add columns as people see fit. (Just don't break the page!) Also, if you notice that I have included an extra section at the bottom of the table to allow people to add new rows if they notice that we neglected to identify key requirements.

Most importantly, please populate the table cells so we can have a good at-a-glance idea of which existing metadata formats support which of our requirements.

Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openajax.org/pipermail/ide/attachments/20070824/f431ae5f/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 105 bytes
Desc: image001.gif
Url : http://openajax.org/pipermail/ide/attachments/20070824/f431ae5f/attachment-0001.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 168 bytes
Desc: image002.png
Url : http://openajax.org/pipermail/ide/attachments/20070824/f431ae5f/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 166 bytes
Desc: image003.png
Url : http://openajax.org/pipermail/ide/attachments/20070824/f431ae5f/attachment-0003.png 


More information about the IDE mailing list