Answered Is Evo Still Being Worked On ? (05/2015)

I think this is a question that a lot of people would like to be answered.

It has been said that there will be support for future PHP versions 5.5+, but as of yet, I haven't seen any confirmation.

Quote from: Jako at Oct 09, 2013, 10:37 AM

It is in the pipeline. All db access have to be changed to mysqli before.

Post on GitHub

Is it possible to hear from the Evo dev team what is happening ?

Is it time to move to Revo, or can Evo users carry on using their beloved software in the near future ?

Thanks for the reply Jako.

Should I understand that the Dev team are still working on a solution to the problem or not ?

Under the impression that Evo development would be continuing, I recently paid out a lot of money to have some snippets developed - has this now been a waste of money ?

I fully appreciate that the work that goes into Evo is carried out on a "free will" base and as such am very gratefull for all the work the Evo dev team do.

Does further development require some form of financial initiative ?

I don't active develop in the Evo team at the moment.

The russian speaking communitiy is quite active under the lead of Dmytro. So better ask him directly.

Hi Jako, is it possible to contact you personally ?

I am in DE, English but speak German.

Clipper has solid Mysqli support, and has had for some time. I'm using it with PHP 5.5.15 on my local server without problems. I develop with the config set to throw errors on deprecated functions, but don't see them in general.

Though it might be an understatement to say things have been a little quiet lately, version 1.3 was released recently. The latest version of Evo I've used for real was 1.0.12. I don't think the key API calls and so on have diverged far enough to make snippet transplants unrealistic - I still pick up some Evo extras as and when required and use them without headaches. I haven't tried the Evo package manager, but suspect it's quite different from Clipper's. And I haven't tried MultiTV on Clipper. No doubt Jako can comment on that!

If you're committed to the Evo way as opposed to Revo, and are looking for a future-compatible option, maybe you should give Clipper a try.

;) KP

@KP, thanks for the feedback.

Clipper is not a solution that I wish to use - personal reasons dated back to the start of Clipper

I have spoken with Jako and am now awaiting more feedback, according to Jako a lot of the code transition has already taken place

I am not a back-end tech so I won't try to give back what Jako explained to me as I don't want to get things mixed up and possibly write down wrong infos.