🚀 go-pugleaf

In <1996Apr5.190323.1@fermi.nsrl.rochester.edu> skulski@fermi.nsrl.rochester.edu writes:

>In article <4k3u61$js3@yikes.winc.com>, 
>delozier@aristar.com (Gregory S. DeLozier) writes:
>> In article <4jt6s0$pem@neptune.ethz.ch>, oswald@inf.ethz.ch writes:
>> 
>>> [...resources] 
>>> are just too limited to port System 3 to a lot of platforms and
>>> _support_ it there, i.e. keep it up to date for every release. The only
>>> official version in the future will be the PC native version, probably
>>> along with versions for MS Windows and Mac. 
>> 
...
>> 
>> I don't have any particular problem with your decision to support 
>> primarily one platform; I'm just trying to figure out where to put my 
>> resources and how to best utilize all this S3 code I've got up and
>> running...
>> 
>> Thanks for your comments.
>> 
>> -greg

>  That is the point. I also was thinking about my own plans and which way 
>to go with my development. Everybody seems to advocate Gadgets, but you 
>know -- portability is the prime concern. It would be terrific if 
>Prof. Gutknecht group could strike some helthy balance between novelty 
>and the ability to actually use that novelty in practice. It would be 
>a pity if the only way to know your new developments would be to read 
>Postscript files from your server. I would love to use Gadgets, but 
>perspectives for future are very important.

>BTW, if we need to convince your boss, we can perhaps write some e-mails
>to him? A few dozens of e-mails might convince him that a good way 
>to disseminate new ideas could be to put them on the desktops of researchers 
>worldwide. He does not seem to read Usenet, does he? (Is it not interesting, 
>that the originator of the net-aware System does not seem to frequent the net 
>himself :-)

>Wojtek

   Portability is the main issue.  Under two very different working 
situations I have found that a mix of Windows and Unix (on SUN machines)
always seems to be needed.
  The lack of a UNIX port for Oberon/F has definitely detered me from
going in that direction.  The haphazard System3 development has detered
me from advocation it to others.
  I committed (my self) last year to using V4 + XE + Dialogs because
I could port to so many different environments quickly and easily.
The one button behavior of Dialogs solves the "user" issue for 
applications.  XE unifies the develpment process (compile, etc), and both
come in source form so that recompilation on new platforms is no
problem.
  If I could say the same about System3 I would be much more likely to
advocate it.

-Doug

-- 
-----------------------------------------------------------------------------
  Douglas G. Danforth, Ph.D.                       danforth@csli.stanford.edu
  Visiting Scholar                                 (415)723-2487 x332 vox  
  Applied Speech Technology Lab                    (415)725-2166 fax
  Center for the Study of Language and Information
  Ventura Hall                    
  Stanford University, Stanford CA.  94305-4115             
-----------------------------------------------------------------------------