V4REV update -- design

[Robert Brenstein]

>  >> People. If this is normal for Revolution, then believe me,
>  >> Revolution will NEVER become tool for collective work/development and
>  >> therefore for enterprise use.

Collective work/development are possible in Rev but not in the same 
way. The forte and the application of xTalks is different. But that 
does not mean there is no place for Rev in enterprise environments.

>  > These are examples.  Not a major development project.  The way you
>>  design an example that teaches basic functions of how to use db calls
>>  is not how you would design large application.
>
>Trevor, we have a lots of examples!!!
>So it become itself big project.

Yes and no. It is bigger effort to start with because you are 
catching up with things you did in RB and MD over many years.

>Just to open each example, and test it, takes 8-10 hours of work.

8-10 to develop an example? Gee, some of them should not take more 
than half an hour and most no more than 4-5 hours IMHO.

>I do not say how many it will take to CHANGE each example and again make
>sure it works....

But then why we still see problems?

>And more probably the number of examples will grow.
>This is why we here try simplify our job and make it consistent.

If you do it right, it will be trivial to add more examples later.

>But we have TEAM.
>And we often want team work on examples and projects.

As Trevor said, Rev lends itself for high automation very nicely. I 
outlined some options for automating developing with individual 
stacks while assembling all into a single stackfile for distribution. 
No idea whether you are using any of them.

But keep in mind that your effort will be largely wasted if v4rev 
users find your examples awkward to use. You need to strike a balance 
or rather compromise between minimizing effort of your team and 
maximizing the benefit of your users.

Robert