joseph@valnet.UUCP (Joseph P. Hillenburg) (10/21/90)
Hello. I got AmigaVision and I have been working on a graphic interface to Lattice. It's fairly simple, except it will require ARexx to funish, which I don't have. (and don't plan on buying until I get OS 2.0) but I was wondering if anyone else out there has any nice AV stacks they'd like to share with the Amiga community. Also, how hard would it be to write a program that compiles AV stacks to from executables that we could just run? This would be a helpful thing for the next major AV release. -Joseph Hillenburg UUCP: ...iuvax!valnet!joseph ARPA: valnet!joseph@iuvax.cs.indiana.edu INET: joseph@valnet.UUCP
manes@vger.nsu.edu (10/22/90)
In article <RqRcR1w163w@valnet>, joseph@valnet.UUCP (Joseph P. Hillenburg) writes: > Hello. > > I got AmigaVision and I have been working on a graphic interface to > Lattice. It's fairly simple, except it will require ARexx to funish, I am not sure you will find all the AREXX support that you need to do this, however I am interested in your efforts here. > which I don't have. (and don't plan on buying until I get OS 2.0) but I > was wondering if anyone else out there has any nice AV stacks they'd like > to share with the Amiga community. Also, how hard would it be to write a > program that compiles AV stacks to from executables that we could just > run? This would be a helpful thing for the next major AV release. Currently AmigaVision is required to execute all AmigaVision flows. FYI: You should refer to AmigaVision 'programs' as flows rather than 'stacks' as 'stacks' implies 'hypercard' type of program, which AmigaVision is not (thanfully?). > > -Joseph Hillenburg > > UUCP: ...iuvax!valnet!joseph > ARPA: valnet!joseph@iuvax.cs.indiana.edu > INET: joseph@valnet.UUCP -mark= +--------+ ================================================== | \/ | Mark D. Manes "Mr. AmigaVision" | /\ \/ | manes@vger.nsu.edu | / | (804) 683-2532 "Make up your own mind! - AMIGA" +--------+ ==================================================
amhartma@silver.ucs.indiana.edu (Andy Hartman - AmigaMan) (10/23/90)
In article <81.2722b9c3@vger.nsu.edu> manes@vger.nsu.edu writes: [...stuff deleted...] >Currently AmigaVision is required to execute all AmigaVision flows. _FROM THE AMIGAVISION BOOK_ (with permision?!? Right...) "Once you have completed a presentation or a course, the material can be prepared for use by others with the RUNTIME feature. This feature helps you to create the complete disks that you will distribute to end users." Maybe I'm interpreting this wrong, but it sounds to me like you can create a disk that will automatically run your "program", "stack", "flow" (whatever) upon boot. > -mark= AMH * Andy Hartman | I'd deny half of this crap anyway!| "Somedays, you just * Indiana University | amhartma@silver.ucs.indiana.edu | can't get rid of a * // Amiga Man | AMHARTMA@rose.ucs.indiana.edu | bomb!" * \X/ At Large! | or just "Hey putz!" | - Batman (original)
manes@vger.nsu.edu (10/23/90)
In article <66639@iuvax.cs.indiana.edu>, amhartma@silver.ucs.indiana.edu (Andy Hartman - AmigaMan) writes: > In article <81.2722b9c3@vger.nsu.edu> manes@vger.nsu.edu writes: > > [...stuff deleted...] > >>Currently AmigaVision is required to execute all AmigaVision flows. > > _FROM THE AMIGAVISION BOOK_ (with permision?!? Right...) > > "Once you have completed a presentation or a course, the material can be > prepared for use by others with the RUNTIME feature. This feature helps you > to create the complete disks that you will distribute to end users." Well, it does make runtime disks. Let me explain. Most people create there individual flows on their harddisk. Having files from this directory and that directory. AmigaVision will (using the runtime option) create a set of floppies with all that you need to execute a flow from a floppy(s). (It will not move fonts, nor the AmigaVision Executable however) AmigaVision *is* REQUIRED to run the flow. > > Maybe I'm interpreting this wrong, but it sounds to me like you can create > a disk that will automatically run your "program", "stack", "flow" (whatever) > upon boot. I had the same misinterpetation, until I played with it a bit more. > >> -mark= > > AMH > * Andy Hartman | I'd deny half of this crap anyway!| "Somedays, you just > * Indiana University | amhartma@silver.ucs.indiana.edu | can't get rid of a > * // Amiga Man | AMHARTMA@rose.ucs.indiana.edu | bomb!" > * \X/ At Large! | or just "Hey putz!" | - Batman (original) -mark= +--------+ ================================================== | \/ | Mark D. Manes "Mr. AmigaVision" | /\ \/ | manes@vger.nsu.edu | / | (804) 683-2532 "Make up your own mind! - AMIGA" +--------+ ==================================================
bobl@pro-graphics.cts.com (System Administrator) (10/25/90)
In-Reply-To: message from joseph@valnet.UUCP
Hmm..maybe we can stay away from the Hypercard metaphor "stacks" and call them
the more logical name of "modules". AmigaVision isn't like HyperCard and it
probably shouldn't be associated with it even remotely.
Just a thought.
-- Bob
______ Pro-Graphics BBS `It's better than a sharp stick in the eye!' ________
UUCP: crash!pro-graphics!bobl | Pro-Graphics: 908/469-0049
ARPA/DDN: pro-graphics!bobl@nosc.mil | America Online: Graphics3d
Internet: bobl@pro-graphics.cts.com | CompuServe: RIP
_________ ___________
Raven Enterprises 25 Raven Avenue Piscataway, NJ 08854 karl@cbmvax.commodore.com (Karl Herrman - CATS) (10/27/90)
In article <66639@iuvax.cs.indiana.edu> amhartma@silver.ucs.indiana.edu (Andy Hartman - AmigaMan) writes: >In article <81.2722b9c3@vger.nsu.edu> manes@vger.nsu.edu writes: > >[...stuff deleted...] > >>Currently AmigaVision is required to execute all AmigaVision flows. > > _FROM THE AMIGAVISION BOOK_ (with permision?!? Right...) Not Really. >"Once you have completed a presentation or a course, the material can be >prepared for use by others with the RUNTIME feature. This feature helps you >to create the complete disks that you will distribute to end users." > >Maybe I'm interpreting this wrong, but it sounds to me like you can create >a disk that will automatically run your "program", "stack", "flow" (whatever) >upon boot. > AmigaVision _flows_ require the AmigaVision program to be present to run. You can load the flow by double-clicking on its icon and it will load the flow and AmigaVision and then present the flow. Not all of AmigaVision is loaded to present a flow so memory isn't as tight. >> -mark= > >AMH >* Andy Hartman | I'd deny half of this crap anyway!| "Somedays, you just >* Indiana University | amhartma@silver.ucs.indiana.edu | can't get rid of a >* // Amiga Man | AMHARTMA@rose.ucs.indiana.edu | bomb!" >* \X/ At Large! | or just "Hey putz!" | - Batman (original) Karl Herrmann Software Specialist CATS