I can understand the desirability of a plug-in (to hold parts or all of the deprecated stuff), but that would then be one more thing (for AW) to maintain. I suppose someone in the community could maintain it...

But my idea - for the fork and transitory builds - gives you (AW) an exit point at least. You can release the "lite" fork and carry on - with the understanding that the "fat" build will be around for X months as a production fallback - while people test their dev environments with "lite" to expose any cfinputs, cfselects or cfgrids that might still be in there.

Then "lite" becomes your regular build, and "fat" becomes the deprecated/archived build after X months, a year, whatever. It wouldn't be maintained, but I suppose people could still run and/or patch it on their own? And if someone wanted to make a cfform plug in on their own?

Al

On 2/10/2015 6:11 AM, Alan Williamson wrote:
That is not a bad idea, one we could explore. There is a lot of stuff that has been integrated into the core engine so unpicking it may not be easy without effecting stuff as a plugin may be hard. But yes, i think if we create a new build and go from there, should be interesting to see.


On 09-Feb-15 12:42, 'Alan Holden' via Open BlueDragon wrote:
Perhaps you could just fork an "OpenBD-Lite" package to start off.
I'd love to dump some of my apps in there and see what - if anything - breaks.

After a few months, you can just archive today's "full" package, and the lite version could take its place. Just swap some names.

It would allow for some transition, so we folks could see in advance what we coded (and forgot) all those years ago, and give us some time - rather than just pulling out the rug from under us one day.

Al Holden


--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en

--- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to