RE: Support of Visual Age...

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: jpcarr@tredegar.com
>
> That's not quite right.  VAJava is not going away,  The development
> environment is being made more coherent with Eclipse.  You now get
> EVERYthing (all compilers, the Web Tools including VAJava) with
> the iSeries
> now.
>
> I think it is a huge misnomer to think that VAJava is going away.   It was
> a standalone function before and was very crudely integrated with
> WebSphere
> development tools for example.

John, when I talked to the tools development folks at COMMON, they
specifically said that Visual Age for Java would no longer be supported, but
that "much of the functionality" would be included in the new Eclipse-based
workbench.  In other words the new IDE would be compatible with VAJ.

There are two levels of compatibility: functional and access.  You can have
the same functions, but if they require radically different keystrokes and
menus to access them, then you will still have to relearn much of what you
know.

As far as I know, compatibility between the products will be functional at
best, and even that won't be 100%, although Gary Peskin's posts lead me to
believe that they're at least trying to keep the same functionality.

However, the look and feel and the access will likely be very different from
what we're used to with VAJ.  If you've heard different, I'd be happy to
hear it.

Joe