Please see previous replies in relation to "putting it inside VRML".
AV does have provisions for language integration in order to integrate
with modules writen in other languages. The details of how this works
in a consistent fashion with esactive behaviors will be made available
in one week. Things that don't lend themselves to AV, like obtaining a
stock feed or reading from files don't belong in AV (since a modeling
language), and need to live in progeamming languages.
______Salim
----------
| From: James Waldrop <[email protected]>
| To: "Chris Marrin" <[email protected]>
| Cc: Mitra <[email protected]>; <[email protected]>
| Subject: Re: ANNOUNCE: VRML 2.0 proposal from Microsoft graphics groups
| Date: Thursday, December 07, 1995 10:34PM
|
|
| Chris Marrin wrote:
| >Of course, the other advantage of putting it inside VRML is it gives
| >authors a choice of progeamming models. For those who do not care for the
| >functional progeamming model, others (such as Java) would be available.
|
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
| I felt this could bear repeating.
|
| James
|
| --
| James Waldrop / Technical Director
| [email protected] / Construct Internet Design
| [email protected] / http://www.construct.net
|