search

dhumphreys / cfrel

ColdFusion Relational Algebra Framework
16 stars 5 forks source link

Finalize structure of cfrel and plugins #16

Closed dhumphreys closed 13 years ago

dhumphreys commented 13 years ago

I would like to open this up to discussion from all of the followers. My initial goal with cfrel was to create a query-generation engine that could optionally be integrated with any ColdFusion ORM. Through months of production use of cfrel at my work, we have found that it works very well and has simplified a lot of our advanced queries. However, as the features have been piling up, two things have happened:

As I have not yet found an alternative ORM for use with cfrel, I am considering dropping the pending support of other ORMs in favor of a simplified repository structure. I would get rid of the cfwheels-cfrel plugin and use this repository for all plugin work. Either that, or I need to organize this repository better so that releases and issues can be more easily kept track of.

Should I make cfrel strictly a cfwheels plugin? Does anyone know of any other ORM I should support? Is there a need to have cfrel available to non-wheels users that just want to fancy-up their ColdFusion queries? I'd like to put a stable cfrel release up on the wheels website within the next two weeks, but I need to decide how to structure and release the plugin before that point.

@rip747, @liferealized, @clearcrystalmedia, @mhenke, @russjohnson, @murpg any suggestions?

dhumphreys commented 13 years ago

All of this seems to work during initial testing. I haven't confirmed that the full test suite works. The structure should allow plugins and the core code to exist in the same repository. Using some symlink tricks, I think that live development could also be done on the plugin from within a cfwheels environment. After a couple more tests I will merge into truck.

rip747 commented 13 years ago

I'm sorry i didn't participate in this conversation sooner. Personally I don't want to see CFREL being exclusive to cfwheels. If it goes down that route then there is little chance for adoption in other frameworks like FW/1, ColdBox, ColdMVC, you name it. again, this is just my feeling as I see a very big and bright future for this project and all the hard work that you have been doing.

dhumphreys commented 13 years ago

Thanks for the response. If you look at the commits I ended up with a /src folder for the coldroute core, and /plugins/cfwheels for the plugin. If you wanted to develop on the plugin cfwheels plugin in a wheels app, you could symlink /plugins/cfwheels/lib to /src and then symlink from /plugins/cfrel in your wheels app to /plugins/cfwheels in cfrel.

The build script outputs a cfrel-core-{VERSION}.zip for the core and cfrel-{VERSION}.zip for the wheels plugin. This should allow the two projects to co-exist without so much maintenance between repositories. Also keeps issues with the plugin in the same place as issues with the core. Sound like a good solution?

dhumphreys commented 13 years ago

These commits are now in master and put the cfwheels plugin in the same repo as the core code. I will be removing the cfwheels-cfrel plugin repository after I can verify this all works.