mdipierro

There are two types of workflow engines: sequential and finite state machines. The latter is more general and includes the former. In a finite state machine external event let you move through the nodes of a graph. The present node is the state. In workflow.py the creation/update of a file is the external event. The state is also characterized by the files present in the file system. The change of state is associated to the execution of a program. I agree it is a little different than what people are used to and I am not arguing semantics. It was useful to me. Hope it is useful to others. That is all. I will be happy to take patches to improve functionality.

Eventually it should be rewritten to use pyinotify. For now it was good enough for my needs.

From my prospective if one likes the web2py libraries, one should use just web2py and not other frameworks. Some web2py users have also complained: what's the point? I think the point is that everybody could learn something from trying to use different tools. I have learned a lot about the other frameworks just trying to implement this. I think others could learn something too from just reading the example code.

Point me to one SQLAlchemy example that you think has no web2py DAL equivalent and I will try show you otherwise.

and of course this is a completely neutral and unbiased suggestion. LOL

If you use web2py, web2py does that for example here is complete code to create a page that lets user post messages and read previous messages.

    m=db.define_table('message',Field('body'))
    def index():
        return dict(form=crud.create(m),rows=db(m).select())

It runs on GAE as it is (requires the scaffolding app).

I think you want this: http://vimeo.com/13485916

This is based on a web2py which has a full web based IDE although the web2py web based IDE does not run on GAE because of GAE file system limitation. cube2py has a partial workaround by storing everything in the database. Still before you run it GAE you have to run the code locally to create the indexes.

Why? Don't you like Star Trek?

For the record. They tested web.py not web2py. It is not the same thing and they are completely unrelated.

Both Rails and web2py follow "convention over configuration" while Django follows "configuration over convention". Each has pros and cons but coming from a Rails background you'll probably find web2py closer.

not acknowledging actual competitors is a marketing strategy.

Agee except for the "own" term. About 100 people have contributed/are contributing to web2py.