   
Why is aiSee a single executable and
not an object-oriented library for C++, for example?
A C library version of aiSee is available
on request to selected customers.
Using GDL (Graph Description Language),
a purely textual exchange, offers a number of advantages:
- GDL specifications can be produced from
all programming languages
(including Perl, Java, Ruby, PHP, ASP/.NET,
Visual Basic, C, and C++).
- Debugging is less complicated
(many people find this invaluable).
- DLL problems are avoided.
If you prefer the OO style, we recommend writing a small
library that produces GDL from your internal graph class. This is usually
quite straightforward, and the additional overhead is small as compared to
the complexity of the layout task.

Can aiSee communicate back to my application
if I integrate aiSee into it?
aiSee features the concept of
User Actions enabling commands to be
associated with nodes. For example, this means that nodes can be selected
and their titles communicated to an application for processing.

How do I get information on the DDE interface?
There is a small C-program
on this website that demonstrates the use of aiSee's DDE interface. The
sources are contained in a self-extracting zip file.
Note: if you don't want aiSee to talk back
to your application, you won't need the DDE interface in the first place. All
of aiSee's functionality can be easily accessed via the command line and/or
the GDL file itself. The DDE interface is only useful for communicating certain
user actions back to your application.

How do I tell aiSee to reload its current graph from Visual Basic?
Courtesy of Conrad Hughes, University of Edinburgh.

More FAQs
» Graph layout
» Legal issues
» SVG related
» aiCall related
» FAQs index
|