Re: Questions on goo / samurui

[Jonathan Bachrach <jrb@xxxxxxxxxx>]

Benedikt Grundmann <Benedikt-Grundmann@web.de> writes:

> Hi again,
> 
> I've got a few questions 
> 
> on goo:
> =======
> 
> First of all is there a fundamental reason for goo not being able to do
> 
> goo somefile
> 
> (like ruby or python or nearly any other programming language which
> provides an interpreter).

no.

> It would be very practical (at least until goo is able to reuse a
> module).  

agreed.  i also want to fix module reuse.

> I started experimenting with samurui and currently my dev - circle
> looks like this:
> 
> 1. Edit foo.goo (inside xemacs) 
> 
> 2. start my goo image: ~/goo/c/g2c-magic/g2c-magic
> 
> 3. Use the file: (use mystuff/test/foo)
> 
> 4. Quit goo 
> 
> repeat everything until I'm either satisfied with the result or annoyed
> by 2 - 4 :-(

i would say that this is rather unusual and somewhat samurui specific.
the usual devo cycle is to load a module into goo (or build it into it
using g2c-goo) by saying 

  ,in foo

and then to interactively modify it using (re)definition from the
top-level listener or using the emacs goo mode support for
editor-based compilation.  this is how i work.  i do have reason to
exit goo from time to time but mostly i can stay in there and fight
the good fight interactively devo'ing my code.

now samurui needs more work until it can support full interactive
devo.  i'll let andrew comment more fully but i will say that once you
have the basic samurui layout, you can interactively adjust its update
and interactively redefine your model's behavior.  what's a bit broken
is samurui's ability to clean up after itself when layouts are
rebuilt.  he's working on this.

> on samurui:
> ===========
> 
> Why does 
> (samurui-init)
> (present "Hello World")
> (samurui-go)
> do not work?  I know one will almost always use more than just a label
> inside an window but I think it would fit into the design principles of
> samurui.  And it makes for an impressivly short "Hello World" app.
> 
> 
> How can I:
> 
> 1. Modify a label
> 
> 2. Create and show one of the standard dialogs (open, save, print,
> color, font)
> 
> 3. Modal / Modeless dialogs / More than one mainwindow 
> 
> 4. Gray out an control.  
> 
> I got more questions but I can't remember them right now :-(

i'll leave these for andrew to answer.

jonathan