Hi, all

I'd like to introduce some of the work where I spent lately.

First of all, as introduction, I say that I use to make applications that mostly
runs in enterprise intranets and are rather data-driven.

This is the target that I focus.

Decisions: Some of my decissions are

..Quixote: I won't discuss that point here now.

..Durus: It's the only OODB that I know and it has demostrated that is fast and
reliable. The first application based on with my field schema used and O-R
mapping and I soon realized that my model was handicapped for this, although It
is still running.

As a principle, most of the work and intelligence must be put in the model and
it shouldn't be afected for idiosyncracies of the persistent mechanism. Then UI
should be straightforward.

..Spec module. Is the perfect complement for an OODB. It provides much of the
functionality that I need: typification, querying, validation.



At this point I guess targeted audience should have decreased somehow.

For those who can't stand its curiosity, I've attached a pair of files that are
snippets of my supplier's orders modules corresponding to model (mcab.py) and ui
(mcab.ptl).

------------------------------------------

We are even fewer now. But I continue if there is someone still there.

I have no documentation but here are some hints.

.. Mcab corresponds to the supplier's order and mlin to the items of the order.

..All Fields classes derive from a Field Class whose base class is Specification
in the spec module.

I've defined not only a set of Field classes corresponding to python data types
but a rather rich set that include very specialized behaviors.

..This style of rather declarative programming fills 80% of the applications ui
code.

But I still like to create quixote forms directly and calling lower level
functions when I need

a different behavior than the default or not provided by directory base classes.

Another principle is that I've tried to do things simple. I use no interfaces.

The reason of this message is that I'd be interested to collaborate with
quixotists that share the same or similar target, decisions and principles that
I took.

I'm unmodestly happy with my work, but I know that one thing is that it runs for
me and another very different that it could run for anyone else.

My modules are still rather pretty dirty an fully undocumented. Another
challenge is nomenclature. Is a task for a real creator (God give name to all
the animals in the beginning:)

Those interested in more explanations or in a demo can address to me by email
and I'll facilitate access to my limited resources. I will value your opinions.

My gratitude goes to the team that has inspired all these.

That's all.

--Oscar Rambla Serra