[aplusdev] Fw: [aplusdev] Win port revisited (Cross Platform GUI)

[stevan apter]

----- Original Message -----
From: "stevan apter" <sapter at earthlink.net>
To: <arcane at znet.com>
Sent: Thursday, August 02, 2001 3:12 PM
Subject: Re: [aplusdev] Win port revisited (Cross Platform GUI)


> here are the documents mike and i distributed at the APL conference.
> i think our design is neutral with respect to the APL selected.  that
> is, your language needs to support:
>
>     variables
>     assignment triggers (although you really only need one for the ws)
>     the APL process has to receive synchronous messages from java
>     the APL process has to send asynchronous messages to java
>
> everything else can be tailored to fit.
>
> what you'll wind up with is an APL workspace or script (the APL side
> of the gui) and a java jar file (the java side).
>
> fyi, mike rosenberg, who is a sharp programmer, didn't know java when
> we started this project.
>
> have fun.
>
> ----- Original Message -----
> From: "Bob Cain" <arcane at znet.com>
> To: "stevan apter" <sapter at earthlink.net>
> Sent: Thursday, August 02, 2001 3:10 PM
> Subject: Re: [aplusdev] Win port revisited (Cross Platform GUI)
>
>
> >
> >
> > stevan apter wrote:
> > >
> > > it seems to me that A+ can be retooled along similar lines,
> independently of
> > > the mstk gui.  indeed, mike and i have published enough information
> about
> > > the k trigger architecture so that, together with arthur's java
> > > communications class (also public), the motivated programmer can
> duplicate
> > > our work without much difficulty.
> >
> > You guys are generating some great discussion on the options and
> > tradeoffs.  The real problem seems to be that motivated programmer.
> > Anybody got a clue how to scare a few up?
> >
> > What might make that more likely would be if those of you who are facile
> > in GUI technology were to agree upon and formally specify an
> > architecture and high level design for a cross platform GUI with the
> > likely implementation resource constraints in mind.  The latter
> > considerations would inlude the size of the pool of programmers that
> > could and might be motivated to rise to the challenge.  While a good
> > deal of work in and of itself that first design step is a necessasary
> > one in any event and could go a long way toward stimulating a full
> > effort.
> >
> >
> > Bob
> > --
> >
> > "Things should be described as simply as possible, but no simpler."
> >
> >                                              A. Einstein
> >
> >
> >
>
////////////////////////////////////////\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> \\\
> >
> >  To contribute your unused processor cycles to the fight against cancer:
> >
> >      http://www.intel.com/cure
> >
> >  To feed a hungry kid today at the cost of a click follow this link:
> >
> >      http://www.thehungersite.com/cgi-bin/WebObjects/HungerSite
> >
> >
>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\////////////////////////////////////
> ///
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: k-javagui.doc
Type: application/msword
Size: 46592 bytes
Desc: not available
Url : http://berdom.net/pipermail/apluslist/attachments/20010802/087ecfe1/k-javagui.doc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: How the K-Java GUI Works.doc
Type: application/msword
Size: 28672 bytes
Desc: not available
Url : http://berdom.net/pipermail/apluslist/attachments/20010802/087ecfe1/HowtheK-JavaGUIWorks.doc