On Jan 3, 9:43 am, Oliver <[EMAIL PROTECTED]> wrote: > 1. Functionality before GUI: the GUI should come second to the > application's functionality.
I'm not sure this principle is really needed. Leo is gui agnostic: it can support multiple gui's. At present, a wxWidgets gui plugin is under active development. > 2. Modularized functionality: define the "services" that should be > available in IDE, THEN define an interface for each service, THEN > build components that satisfy those interfaces, THEN build the > glue that binds the services into an application. I am most interested in this approach, and I am eager to learn how pida encourages this way. > 3. Modularized GUI: the GUI should be broken down into independent > pieces that communicate via pubsub-type messaging. Hmm. Leo factors out the gui by defining what might be called an abstract text widget that then gets implemented by a gui-specific classes. Base classes handle common code, subclasses fill in details. This has worked surprisingly well in Leo, and I see no reason it could not work in other contexts. In particular, Leo can (or easily could) handle all the situations that you enumerate. OTOH, perhaps a message-oriented approach might simplify the code further. I want to keep an open mind about this. Edward
