unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: David Pirotte <david@altosw.be>
Cc: Dmitry Polyakov <liltechdude@gmail.com>, guile-user@gnu.org
Subject: Re: Looking for graph library
Date: Mon, 10 Oct 2022 01:00:28 +0200	[thread overview]
Message-ID: <878rlok396.fsf@elephly.net> (raw)
In-Reply-To: <20221009154724.507c016f@aicha>


David Pirotte <david@altosw.be> writes:

>> > 	https://reposcope.com/man/en/3guile/gv  
>
>> Yes, graphviz comes with Guile bindings.  Since they don’t provide a
>> Guile module you need to define a module like this:
>
>> --8<---------------cut here---------------start------------->8---
>> (define-module (libgv)
>>   #:export (digraph node edge layout render setv))
>> 
>> (load-extension "libgv_guile" "SWIG_init")
>> --8<---------------cut here---------------end--------------->8---
>
> Right, but the module I was looking at - but did not try - exports quite
> a lot more functionality ...
>
> 	https://github.com/roelj/graphviz-guile/blob/master/graphviz.scm

Yes, this is essentially the same.  My example above just shows the
pattern that needs to be used.  Roel’s module there exports *all* the
procedures.

The point, however, is — as Dmitry wrote earlier — that gv does not
provide any predicates or search algorithms.  gv only provides
constructors and accessors to the graphviz data structure, and the means
to render them.

-- 
Ricardo



  reply	other threads:[~2022-10-09 23:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 10:29 Looking for graph library Dmitry Polyakov
2022-10-08 13:42 ` Maxime Devos
2022-10-08 14:07 ` Ricardo Wurmus
2022-10-10 17:18   ` zimoun
2022-10-09  0:20 ` David Pirotte
2022-10-09 10:51   ` Ricardo Wurmus
2022-10-09 18:47     ` David Pirotte
2022-10-09 23:00       ` Ricardo Wurmus [this message]
2022-10-12  9:13         ` Dmitry Polyakov
2022-10-12 16:33           ` Ricardo Wurmus
2022-10-12 19:35             ` Dmitry Polyakov
2022-10-14 17:17             ` zimoun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rlok396.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=david@altosw.be \
    --cc=guile-user@gnu.org \
    --cc=liltechdude@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).