emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Gary <orgmode@garydjones.name>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: From state table to state diagram
Date: Wed, 25 Aug 2010 00:28:13 +0100	[thread overview]
Message-ID: <87tymjy4j6.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <i50ck8$h4o$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

On Tue, 24 Aug 2010 14:06:32 +0200, Gary <orgmode@garydjones.name> wrote:
> 
> Eric S Fraga wrote:
> 
> > Sorry, that should have been graphviz... typing on a phone.  :-( 
> 
> :))
> 
> Okay, thanks. I know about graphviz, but it is not really what I am
> looking for. Ideally I would create a state transition table and then
> just "magically" get a diagram as a by-product. I can definitely see
> that the DOT language might be a good target though - generating that
> from a table should be easier than generating a diagram directly.

Yes, that is what I was thinking (but did not want to type on the
little on-screen keyboard of my phone...) when I suggested graphviz:
dot could be a good intermediate language.

> Well, maybe it's a bit specific and nobody has done anything so I should
> look into it on my own :)

It is indeed specific but I think there would be some interest in what
you manage to concoct so please post it here!  

If I were to have time to do this right now, I would probably use awk
to convert a state transition table to a dot graph representation but
only because I'm very comfortable with awk and much less so with emacs
lisp...

And the ease will depend on the type of transition table you have as
the starting point, of course...

As an aside, when it comes to actually generating a diagram, I would
in practive typically use tikz due to the quality of the graphs that
can be achieved.  However, it may be harder to do a table \to tikz
translation automatically.

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-08-24 23:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 10:38 Gary
2010-08-24 11:03 ` Eric S Fraga
2010-08-24 11:24   ` Gary
2010-08-24 11:25   ` Eric S Fraga
2010-08-24 12:06     ` Gary
2010-08-24 23:28       ` Eric S Fraga [this message]
2010-08-25  0:33       ` Eric Schulte
2010-09-23 15:02         ` Gary
2010-09-24 10:00           ` Dan Davison
2010-09-25  7:40           ` Rainer M Krug
2010-09-27  6:27             ` Gary
2010-09-27 15:21               ` Mark Elston
2010-09-28 14:04               ` Rainer M Krug
2010-11-24  1:25                 ` Vladimir Alexiev

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87tymjy4j6.wl%ucecesf@ucl.ac.uk \
    --to=ucecesf@ucl.ac.uk \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@garydjones.name \
    --subject='Re: Re: From state table to state diagram' \
    /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

Code repositories for project(s) associated with this inbox:

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).