[comp.windows.interviews] InterViews documentation

mclemore@gnd1.wtp.contel.com (KENNY MCLEMORE) (05/03/91)

found serveral documents in "interviews.stanford.edu (pub/papers)"
however, when trying to print interviews tutorial (postscript format)
i had problems.  first page printed great but a "range error" occurred
right at the page break...@#~$^!!.   any suggestions ?  articles available
is ascii format (i can live without graphics) ?  

thx, ken

connolly@convex.convex.COM (Dan Connolly) (06/04/91)

In article <9106040032.AA23987@hadar.fai.com>, adobe!hadar!michael@LABREA.STANFORD.EDU (Michael Young) writes:
|> 
|> This is LONG, so read only if interested.
|> 
|> 
|> To the InterViews people at Stanford:
|> 
|> After struggling to understand InterViews 3.0, I have
|> come to the conclusion that this is what is needed:
|> 
|> ------------------------
|> InterViews Style Guides:
|> ------------------------
etc...

I too have just spent several days porting an poring over interviews 3.0.

First: Nifty! I like it.
Second: What I need is examples.

Good doc is hard to write. It's hard to keep accurate and up to date. I think
that for an experienced InterViews programmer, 
the time it takes to write a page of example code is much less than the time to
write a page of quality doc, and folks learn abstract concepts monkey-see-
monkey-do much easier than trying to understand prose descriptions.

For every class, or every closely related group of classes, I'd like to see
a one- or two-page example demonstrating its use. This would help clear up
my confusion over what classes implement the 2.6 (interactors) style and
which ones do the 3.0 (glyphs) style and which ones do both.
Plus, to see if example code is up to date, all I've got to do is compile
it and see if it works. I can trust it much easier than a man page.


I'd REALLY like to see more work on iclass:
* if I'm browsing something like:
class A{
  public:
	bcd(int x, int y);
}
	I'd like to be able to click on bcd() and see:
	* the code that implements it (the REAL doc :)
	* the man page that explains it.

linton@marktwain.rad.sgi.com (Mark Linton) (06/04/91)

In article <1991Jun04.041701.21620@convex.com>, connolly@convex.convex.COM (Dan Connolly) writes:
|> For every class, or every closely related group of classes, I'd like to see
|> a one- or two-page example demonstrating its use. This would help clear up
|> my confusion over what classes implement the 2.6 (interactors) style and
|> which ones do the 3.0 (glyphs) style and which ones do both.
|> Plus, to see if example code is up to date, all I've got to do is compile
|> it and see if it works. I can trust it much easier than a man page.
|> 
|> 
|> I'd REALLY like to see more work on iclass:
|> * if I'm browsing something like:
|> class A{
|>   public:
|> 	bcd(int x, int y);
|> }
|> 	I'd like to be able to click on bcd() and see:
|> 	* the code that implements it (the REAL doc :)
|> 	* the man page that explains it.

I agree completely.  Alas, there are many more things that would be good to have
than we have time to work on.  Current higher priorities include more glyph-based
UI components (especially text/document-oriented), converting ibuild to work
with glyph-based components, and completing the reference manual.

CJB@MTUS5.BITNET (Chris Barrera) (06/10/91)

i have been trying to print out the post-script instructions for
Ibuild and my post-script printer just won't print out past page33.
i suspect the printer is running out of memory ( it is a 5 meg file
after all ), and no matter how many pages i manually edit out of the
file i can't get them pages printed.

question: this document was created using FrameMaker software. since
i have access to FrameMaker at my site, i was wondering if anyone out
there could e-mail me the FrameMaker MIF files or the Maker files so
that i could load it in and print the pages from FrameMaker???


thanks to anyone who could help in advance...

chris barrera
cjb@mtus5.cts.mtu.edu
barrera@mtu.edu   cjb@mtu.edu

mussat@irisa.fr (Louis Mussat) (06/11/91)

From article <91161.094747CJB@MTUS5.BITNET>, by CJB@MTUS5.BITNET (Chris Barrera):
> i have been trying to print out the post-script instructions for
> Ibuild and my post-script printer just won't print out past page33.
> i suspect the printer is running out of memory ( it is a 5 meg file
> after all ), and no matter how many pages i manually edit out of the
> file i can't get them pages printed.
> 
[...]
> barrera@mtu.edu   cjb@mtu.edu

I've mailed to Chris a copy of a Perl script I wrote just for this purpose.
It split a FrameMaker-generated PS file in chunks of size less than 1 Meg.
I have successfully printed those pieces with lpr.
If anyone is interested, I can mail him a copy.

	
			  /  _       .  /
			 /  (_) (_/ /  |
			 `-------------/--
				      /
						Louis Mussat
						mussat@irisa.fr

G.Joly@cs.ucl.ac.uk (Gordon Joly) (06/12/91)

Louis Mussat writes:
 > From article <91161.094747CJB@MTUS5.BITNET>, by CJB@MTUS5.BITNET (Chris Barrera):
 > > i have been trying to print out the post-script instructions for
 > > Ibuild and my post-script printer just won't print out past page33.
 > > i suspect the printer is running out of memory ( it is a 5 meg file
 > > after all ), and no matter how many pages i manually edit out of the
 > > file i can't get them pages printed.
 > > 
 > [...]
 > > barrera@mtu.edu   cjb@mtu.edu
 > 
 > I've mailed to Chris a copy of a Perl script I wrote just for this purpose.
 > It split a FrameMaker-generated PS file in chunks of size less than 1 Meg.
 > I have successfully printed those pieces with lpr.
 > If anyone is interested, I can mail him a copy.


Or use "lpr -s" (symbolic link to file; no copying)?
Under SunOS 4.x anyway.

____

Gordon Joly                                       +44 71 387 7050 ext 3716
Internet: G.Joly@cs.ucl.ac.uk          UUCP: ...!{uunet,ukc}!ucl-cs!G.Joly
Computer Science, University College London, Gower Street, LONDON WC1E 6BT

                        Drop a utensil.

CJB@MTUS5.BITNET (Chris Barrera) (06/13/91)

i have tried lpr -s filename everytime. one thing though,
it says "file not linked, copying instead". maybe that is
the problem...