Flourish PHP Unframework
This is an archived copy of the forum for reference purposes

Dead project?

posted by audvare 7 years ago

With Will gone from iMarc now it seems Flourish may lose any real support from its primary developer. I don't know if this is so but there are quite a few signs here:

1) Moved to GitHub, no responses yet on my pull request

2) Flourish never came out of beta so far

3) Some bugs still remain

4) Some features still missing

I am maintaining a fork of Flourish here https://github.com/Tatsh/flourish-classes and an ebuild for Gentoo here https://github.com/Tatsh/tatsh-overlay if anyone is interested. I will be directly putting bug fixes on my fork from now on and will no longer be providing patches in my Sutra project https://github.com/Tatsh/sutra

I will continue porting Flourish to JavaScript: https://github.com/Tatsh/flourish-js

Please send me a message on GitHub if you would like more information (will likely not be checking this forum post). I have worked with the Flourish library for over 1.5 years and at this point cannot imagine PHP without it, but I think since inkWell goes too far astray I am going to be splitting the last version of Flourish away (will likely change name too to avoid issues) unless the project turns around really quickly.

Audvare, my initial impression is that Will is probably very busy with his new work as he's learning the ropes. iMarc afforded Will time to work on Flourish because iMarc uses the library internally and is predominately a PHP shop.

I cannot say that I'm not concerned at all. Will has been at this a long time, and I assume as with most developers, new things capture interest quite a bit more. That said. I'm also not concerned because working for iMarc, I can assure you there is a vested interest in the other developers there maintaining and pushing it into the future.

Flourish represents years worth of development, testing, and polishing. Throwing it away would be a bad decision for all interested parties. My understanding of the "difficult" part for iMarc is replicating Will's extensive test environments. For this reason they've been focusing on small bugfixes rather than larger ones which could have more extensive consequences and/or new features: https://github.com/imarc/flourish-classes

My general suggestion would be to push bug-fixes towards iMarc's fork which can undergo more thorough review and stable inclusion... unless of course you have gone through the trouble of replicating Will's test environment. Similarly, I also maintain and for that matter extend the .inK fork, so I'd be happy to take any bugfixes or new features there. One area in which I differ from iMarc is that I'm not overly concerned with backwards compatibility since Flourish is primarily used as a core for my framework which is not proposed to be API stable yet.

Overall I think someone just needs to take the time to talk to Will about his long-term intentions with Flourish to determine if the project should be forked in a more absolute sense.

posted by mattsah 7 years ago

I should also add, inKWell is separate from the .inK Flourish fork. That is to say, there is nothing included in that fork that requires inKWell. inKWell requires .inK Flourish (to operate as documented), but not the other way around. Also, although I'm not concerning myself with backwards compatibility, the API remains to this day 100% compatible.

posted by mattsah 7 years ago