Path: utzoo!mnetor!uunet!husc6!cmcl2!phri!dasys1!raylau
From: raylau@dasys1.UUCP (Raymond Lau)
Newsgroups: comp.sys.mac
Subject: Re: V.I.P. prototyping tool
Message-ID: <2755@dasys1.UUCP>
Date: 28 Jan 88 16:23:14 GMT
References: <1113@hao.ucar.edu>
Organization: The Big Electric Cat
Lines: 30
Keywords: LSC, modifying VIP --> LSC output
Summary: Stuck with VIP

In article <1113@hao.ucar.edu>, bill@hao.ucar.edu (Bill Roberts) writes:
> Can anyone in this group make any comments about the value of V.I.P. as a 
> prototyping tool for writing complex applications on the Mac?  I thought it 
> would be nice to use V.I.P. to gen up a nice "custom shell" application, use the
> VIP->LSC translator to get the "shell" into the C language, and then do things
> like adding PopUpMenus, custom windows, etc.  Can V.I.P. and its companion
> product, the VIP->LSC translator handle this type of thing?  Or would I be stuck
> with what VIP gives me?  That is, the only thing the translator could do would
> be to compile the code and improve the runtime of the "simple" application?
> 
> Thanks in advance for any info on this...
> 
> --Bill

You're more or less stuck with the code.  I've looked at the output the
VIP=> LSC translator creates.  It's about 95% calls to VIP's library!
argh...that means ea. little thing you add in VIP is just a call to the
library.  Want to change the behavior of something?  Guess what parameters
and variables are accessed by the library routine....and rewrite that
routine!  (argh!)  Now, if it translated to toolbox calls, it would be great..
If the library source were provided, it'd be almost bearable...

But!  That just isn't so....you're more or less STUCK.

--
Raymond Lau                       GEnie: RayLau
100-04 70 Ave.                    CIS: 76174,2617
Forest Hills, NY 11375-5133       Delphi: RaymondLau
United States of America          MacNET: RayLau
uucp: raylau@dasys1.UUCP (..{phri,cucard,bc-cis,mstan}!dasys1!raylau})