This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
What is the most efficient way to provide a user interface for a guile-based application in a non-monoloithic way, i.e. it should be possible to replace the user interface without recompilation? Is it possible to provide stubs for dynamically loadable module, so that the user can decide whether at startup time whether to use a ncurses-based ui or a gtk-based or a motif-based? The emacs seems to have trouble with such a design and needs to decide at compilation time which ui libraries to use. I heard that e.g. for integrating something into gnome, it doesn't just suffice to provide a thin gtk wrapper for the user interface. So are pipes or sockets to a seperated user frontend program a better solution? In the special case of 'Naos', a turn-based game, the communication of user and gamedriver is completely synchronous and blocking, if that matters. -- Klaus Schilling