On the web site it says the project requires Fusebox but I think you are
building with modelGlue.
What is the latest on the framework?
I was thinking about offering to build a Fusebox version with same database
and user interface.
Kevin
Nick,
I am not sure how to get involved. What do you need?
I could start by running the Fusebox scaffolding code generator to generate some CFCs which we could add to manually.
Kevin
Nick,
I have seen and used Brian’s code generator and it is good. You are right about the ability to make your own rules being a good thing.
The ability to modify the templates is important as it allows a further level of abstraction that improves what can be done in terms of customisation. Last time I looked Brian’s code generator had two ways of creating code either with XSLT or with Peter Bell’s cftemplate.
If there is a choice I would go with the cftemplate method as it is much easier to write the templates. You don’t need to know XSLT or any XML cleverness to do it. The Fusebox scaffolding generator is also based on the same cftemplate. Unfortunately they were based on slightly different versions of the code and they also use different metadata so they are not compatible with each other.
In that respect either would be good.
The main difference, I think, is that the Fusebox Scaffolder generates a whole bunch of other things too so you can generate a complete Fusebox application in one go. When I tried Brian’s generator you had to choose each thing one at a time.
Its really a matter of taste but you will find that Brian’s code does different things so it may be a better choice, since you want to generate model glue code specifically.
Brian’s code generator has support for more databases right now.
The Fusebox Scaffolder generates more front end user interface code.
I am considering making some changes to the Fusebox Scaffolder to allow more compatibility between the templates so would be interested in using Brian’s generator in some way to learn what it does better.
Although the Scaffolder generates a complete application it is based on the tables in the database and is only useful as it come in a few cases most applications need further modification.
I have found that it can be quite tricky to make use of the generated CFCs without changing them in some way. I am getting more used to it as time goes by, but the ability to tweak the template means that over time I can improve the templates bit by bit so the code generated doesn’t need to be modified. Sometimes I do need to think carefully about how I use it to make sure it doesn’t break when regenerated. That’s just a learning experience we will have to go through.
Solves lots of your code gen' extension issues out of the box, and if
you keep your DB interaction to purely being through Transfer (or
really simple stuff), you have 4 db support right out of the box.
Just a thought... not that I'm biased at all ;o)
Mark
They're just to show support for the project mainly but to also show
you're involvment as well.
I would like to use Transfer. The only issue I have with it is my own lack
of understanding of how to make it do what I want to do.
One of my clients has a bad experience with a project built with Reactor and
I have not had a client willing to try Transfer since. I want a project to
learn transfer on.
I would also like to add Transfer support to the Fusebox Scaffolder so using
something (this project) as a learning experience would be a good idea.
Seems like a good choice as you are on the team.
Kevin
Hi, here is my suggestion.
We should build a model that will support both Fusebox and MG front ends.
This will be extra work but I am interested in the Fusebox version and would be willing to do that.
I suggest we use Brian’s code generator and Transfer for the model CFCs.
Kevin Roche