When I’ve started flow, one of the features I wanted for it was scaffolding from the front-end and be able to do things like: Flow scaffold model: #User or: Flow scaffold crudFor: #Task and have created the Model and Controller classes and accessors in environment so you can continue developing the app pulling things from there.
I’m starting this blog here to make a coder-friendly open conversation with contributors and enthusiasts about flow’s design. This blog will be doing two things in one move: A source of fresh input, so feedback, so inspiration. An output about progress on this line of work, so relevance of the mission. But lets back up a bit, what is flow after all? I like to say that flow is a mission with a framework. Here is flow’s mission from the project’s readme:
When I was doing engineering, I had a very good algebra teacher.* Those were the days full of vectors and subspaces and subspaces of polynomials and matrices and subspaces of matrices of polynomials. All from 7 a.m to 12 p.m. In the middle of that math trench he said once something that my head really saved. The teacher was explaining yet another concept while the sky was still dark in the morning and there was this guy that asked him to clarify a detail. ...
When you trust your content is when you can forget it.