|Subject||:||Adobe Apollo - coming sooner than you think...|
|Date||:||01 Jan, 2007 on 00:16|
|Adobe Apollo is intended to become another "free web standard" like PDF & Flash to informally secure Adobe's market position.
What are your initial thoughts about the open-source Adobe Apollo and its' porting potential with OS/2-eCS?
Here's the Adobe Apollo F.A.Q.:
Two interesting F.A.Q. quotes...
 "We spent a considerable amount of time researching a number of HTML rendering engines for use in Apollo. We had four main criteria, all of which WebKit met:
* Open project that we could contribute to
While the final decision was difficult, we felt that WebKit is the best match for Apollo at this time."
Here's a link to the Webkit Project:
|Subject||:||Re:Adobe Apollo - coming sooner than you think...|
|Date||:||01 Jan, 2007 on 17:37|
The choices for an OS/2er are becoming more and more reduced. If you were to have something that works on OS/2 --even if partially...nay, even if not with all the bells and whistles of the Adobe offering-- I would point to the Google Web Toolkit (GWT) of BigWarpGuy's inquiry.
Although potential OS/2 Web developers would not be able to use the SWT aspect of the GWT, the code for generating AJAX is Java --open source.
In the documentation it is recommended version 1.4.2 and up but, at least for the near term, the sample code compiles under Golden Code Development (GCD) 1.4.1_7.
Hence, although currently OS/2ers can not use SWT to try this default Hello sample (shown here on Linux): (( gwtHello )).
OS/2ers ARE ABLE to modify the example in a text editor and compile it with GCD to turn it into: (( gwtHello modified a la OS/2 Go ahead, "hit" the AJAX button.))
OS/2, again, is short in developers. Consequently, Apollo may not be as close to embrace as GWT.
Having a more current version of Java is of utmost importance and urgency for OS/2 since web technologies' major enterprises (IBM, BEA, SUN, Google, etc.) are leveraging Java's cross platform property.
OS/2 could do even without SWT if a more current version of Java existed. Case in point, Linux has individualists who are not keeping their hands in their pockets and waiting for private entities to develop what they need (or awakens their creative curiosity). As an example, see the SWT to SWING project:
that could benefit us indirectly if we had a current Java port. The above version 1.0 of the hack is designed for Java 5. Although currently I am attempting to smooth some the hiccups experienced under OS/2's Java with the GNU's Classpath Java 5 equivalents, I am not making much progress.