Hi Peter,I've reread the email you linked to. You write there about your own inventions on the subject of visual building of application. This is very interesting to me. Very ambitious also. If you need some help from the InstantCRUD side (common data structure, API whatever) - then email me.
Nice
The subclassing of templates sounds really interesting, but actually I don't have many strong convitions on this front - I think we need some more experimentation. Or perhaps I have one idea about the templates. I found it really simpler to code some more complicated parts as perl functions, put
Some more technical details.The main idea of how the scaffolding should work is that we generate only a skeleton of directories, nearly empty controllers and some config stuff. The generated controllers only contain their package declaration and a 'use base
There's that, and there's also the ease of prototyping an application
really, really fast when scaffolding is available. Without such
scaffolding, you may end up taking a month to build a prototype. It
certainly depends on the complexity of the project, however, speed may
be more important in
Hi Max,
There's that, and there's also the ease of prototyping an application
really, really fast when scaffolding is available. Without such
scaffolding, you may end up taking a month to build a prototype. It
certainly depends on the complexity of the project, however, speed may
be more
Totally agree, and I guess this is why they call it 'scaffolding'. The
word brings with itself the notion of the stuff being temporary.
The need for scaffolding only goes away in an ideal world where
management gets excited about ideas. However, these days, it's hard to
pitch an idea unless
Max Afonov wrote:
There's that, and there's also the ease of prototyping an application
really, really fast when scaffolding is available. Without such
scaffolding, you may end up taking a month to build a prototype. It
certainly depends on the complexity of the project, however, speed may