[Aiml-programr-developers] Thoughts on programR AIML ver 1.0

[mauro at cicio.org]

Hi,

I am trying to catchup with the mails I missed in the last days...
This answers Ben's one.

> Nick, when you get a chance can you please send me a copy of the diagrammee
> as I would like to read through it and start to get a handle on the programR
> work-flow process. Just confirm that you are using the Gnome package Dia for
> these UML images.


Right. I myself always used Dia, so I am happy with it. I believe that
in the meantime something else is out there for Ruby... is it true? I
remeber a few years ago I patched a ruby/dia module written by a
Russian guy (direct engeenirig). Is there anything for reverse
engeeniring? Not urgent at all, just curious. For programR, we can
live happly with DIaUml.

> Once I get a solid understanding of this, I could author a complete, precise
> and complex document detailing exactly how this process occurs.

Cool!

> The I will
> make a simpler version to be included as part of the Userspace Tools &
> Documents.

Even cooler!

> Tests:
>
> I agree with this, on the concepts of good projects is good user
> documentation and tests. There are many test models that we can use from the
> Ruby codespace and in particular Ruby on Rails. I was wondering if we could
> make programR into a Rails application also or just leave it as a standalone
> package depedndent on the Ruby Librabries or even both..

At the moment I am completely in the RoR world, so I defenitevily
would like to have programR as RoR plugin.
Considering that I am not interested in the Tk interface, I think we
can already have some assignments done :-)
Anyhow: we should look at the specification to:
- build a gem
- create a plugin
and based on those use a compatible dir structure.
Very likely the current one is already OK (almost).
I can take care of this aspects if you are not in a hurry to do it yourselves...
I created a couple of tasks and put myself as assignee, but I can
change this of course.
As soon as we have a clear idea on the list of tests, we can probably
put them in the task list as well, as single tasks. It can be a way to
help programR as soon as we have 30minutes: program a small test and
close a task.

> Rake:
>
> I like the concept of automation, certainly for testing/deployment but
> recognise the value of developing a dual user fork, one for developers and
> the other for users. As far as an interface, if we just code a GUI based on
> another common well-supported Open Source library (Tcl/TK) that should allow
> maximum cross system interoperability. I know that none of us like WIN
> software but we will need to code for it in some capacity I think. Or
> alternately, ProgramR is only going to be an application served by a
> webserver. I think this is one of those key geography questions that you are
> asking Nick. Maybe both then, a simple standalone version with all enclosed
> libraries, documentation, tests etc that can run standalone and a full
> developers version that runs via Apache or a Rails application.

I see programR as a library, but it should be more (it is not libraryR
after all :-))
I like the idea of the RoR plugin. Is anybody signing in for a Tk (or
similar) interface? I would just then different downloads: library
only, library+GUI, RoRplugin.

> Organisation:
>
> I'd be happy to start write user Documentation, deployment instructions onto
> *nix based systems, with perhaps a focus on Debian-based distributions. I
> already have a monster HOWTO on installing/configuring RadiantCMS/Rails onto
> a Debian Etch Server. Could also migrate that rather easily into an Ubuntu
> specific HOWTO also.
> I'd also be happy to run/report all tests as they get built and configure
> some sort of benchmarking programme to report of direct shell enquiries to
> the interpreter and via an interface (webserver/standalone).

Fine, it seems a lot of valuable work to be done.

Ciao,
Mauro