From: Anthony Kozar <anthony.kozar@utoledo.edu>
Subject: Re: Newbie - desigining apps
Date: Fri, 08 Oct 2004 14:43:27 -0400 [thread overview]
Message-ID: <BD8C580F.C3B7%anthony.kozar@utoledo.edu> (raw)
In-Reply-To: <4165E98D.3090304@triad.rr.com>
IHDTM (I haven't done this myself), but based on knowledge of how scriptable
applications are often implemented on other platforms, I would suggest using
the Model-View-Controller pattern/paradigm. Basically, you strive for a
clean separation between your data objects, the objects that display the
data, and the mechanisms/interface objects that allow those objects to be
manipulated. (Just do a seach online for MVC to learn more).
This approach definitely requires designing your app from the beginning with
this separation in mind. But the benefits of this design will I think be
useful in the future if you decide to add other controllers, views, etc.
In your case, I would guess that you will start off with two sets of
controllers for the same data -- one for your GUI and one for Guile.
Anthony Kozar
anthony.kozar@utoledo.edu
http://akozar.spymac.net/
On 10/7/04 9:12 PM, Max Polk<ux9i003@triad.rr.com> etched in stone:
> Have others found that supporting Guile in an application means
> rethinking how it runs at it's very core? For example, instead of
> writing use cases and designing from that, now I have a use case like
> "let the user call any higher-level function".
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-10-08 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 1:12 Newbie - desigining apps Max Polk
2004-10-08 2:49 ` Julian Graham
2004-10-08 18:43 ` Anthony Kozar [this message]
2004-10-09 21:47 ` Neil Jerram
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=BD8C580F.C3B7%anthony.kozar@utoledo.edu \
--to=anthony.kozar@utoledo.edu \
/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).