XF 2.4 general discussion, feedback, complaints, random off topic posts, etc.
- Thread starter Paul B
- Start date
Arantor
Well-known member
I have done my share of writing addons for CKEditor and TinyMCE, TipTap is a world more convenient for additions and changes than those two. Can't speak for Froala, but I can't imagine it's wildly easier to build with than the two titans.
But yeah, it is a ton of work. Just a smaller ton of work than fixing Froala!
Was looking at writing an add-on that incorporates VideoJS today and noticed XF already comes with that bundled, so figured I'd go ahead and reference it. Turns out the version bundled with XF is 6.2.8, which is 7+ years old. Out of curiosity, I looked through a couple of others and most of them are jQuery dependent (which I thought XF no longer uses) and some are completely unmaintained projects going back 8+ years old.
I get replacing a library is easier said than done, but I'm surprised some of this isn't naturally updated as part of ongoing builds... Any of this getting love in 2.4?
As a developer, I honestly (not sarcastic), am OK with dependencies like this getting upgraded and breaking my add-ons, as it forces me to not let mine stale out either.
I get replacing a library is easier said than done, but I'm surprised some of this isn't naturally updated as part of ongoing builds... Any of this getting love in 2.4?
As a developer, I honestly (not sarcastic), am OK with dependencies like this getting upgraded and breaking my add-ons, as it forces me to not let mine stale out either.
Mouth
Well-known member
Actions speak louder than words, and once again, sadly, XF is not walking the talk.
With 2.3 we were told that release cycles would be no less than every 6 months. That means 2.4 should be released by no later than Jan 09th. Since that's 3 weeks away, and there's not even an alpha yet, it's certainly logical to believe that's its going to be ~9 months between 2.3 and 2.4.
So a Mar '25 release for 2.4, at best and optimistically a Sept '25 release for a possible 2.5 or 3.0.
But hey, we should be happy that our annual subscriptions gives a single dot point (minor) release at all. It was 3.75 years of subscriptions for the previous single dot point release.
Yes so a marked improvement all being well
duderuud
Well-known member
I sadly have to agree. XF 3.0 would be released quickly after 2.3 because it was a minor update. Looks like the 2.3 release once again...months and months later.
Maybe it's better to not make any statements/eta's because so far those statements were never met (by a long shot).
Ozzy47
Well-known member
But when they don’t give ETA’s they get criticized.
I wouldn’t put no stock in any ETA’s they provide, it’s okay for them to be delinquent in updating to said versions, but addon developers better not delay updating their addons to work on the latest version.
Dammed if ya do, dammed if ya don’t.
XF 3.0 delayed, but that’s the entire reason 2.4 exists and why 2.5 may exist. Who knows? Maybe there’ll be a 2.6 and 2.7. Maybe a 2.8 and a 2.9. We’ve still not run out of numbers, there could be a 2.10!
I think the important thing is we continue delivering what we can until it’s ready. And it being ready is absolutely critical because we’re not going to release something before it’s ready just to appease an arbitrary release date. This is a good thing.
I think the important thing is we continue delivering what we can until it’s ready. And it being ready is absolutely critical because we’re not going to release something before it’s ready just to appease an arbitrary release date. This is a good thing.
frm
Well-known member
That's it, time to start a 2.5 thread.
Suzanne O
Well-known member
Maybe Chris and his crew are keeping it for next Wednsday being Christmas Day.
Remember, they do like to surprise us.
2.4 is not postponed, it is on target for “between Q4 2024 and Q1 2025” as we originally stated.
There is not going to be a release on Christmas Day. We have families so we’ll be spending it with them, along with the majority of the festive period.
Suzanne O
Well-known member
Fair enough.
I was just using it as an example.
