The New & Improved Flarum Roadmap

kaktux

have you given long-time compability of extensions some thought?
I mean the case: a well used extension no longer is maintained - what happens then? Will it just be not-compatible at some point - or what will happen?

I have in mind e.g. dokwiki software - which i use. There are several extension which a lot of people (non programmmers) use - but then got abondoned by the developer. The most used got "pooled" in a low maintainance form and kept compatible/secure - but dont get updates/new features.

As a compact core might come with this problems have you had anything in mind for these situations?

Franz

kaktux We hope that the new extension API will keep breaking changes to a minimum, so that extensions will remain compatible for a fairly long time.

As for keeping old, no-longer-maintained extensions in a separate group, that will have to be a community project. But it sounds good! ?

Kyrne

kaktux From what I've seen of the new code. Every extension will break with the new changes. Any extension that isn't updated will flat out not work.

Toby

amdad Hey @Toby, question about search improvements. Do you plan add full power index to flarum?
Something like TNTSearch?

Probably not by default, but we will eventually support custom search drivers so you can write an extension to use whatever kind of index you want.

kaktux Kyrne There will be breaking changes for extensions with each release (0.1, 0.2, 0.3, etc.) – as Franz said, we are aiming to keep them to a minimum by introducing the new Extension API early, but some breaking changes will still be unavoidable. Patch releases (0.1.x) will not contain any breaking changes.

kaktux

guys - thats exactly what i meant with my post in the roadmap thread: long term compability.
kaktux

promolaSA's question is based on the same thought.

knowing an answer to that will eliminate those "doubts" ?

The replies were
Franz
Toby

Franz

Wait... are we talking about compatibility during the beta, or once we have a stable release?

Kyrne

Franz I'm referring to the next-back and front branches, and whatever version they will be merged into.

kaktux

Franz i meant "compability for years to come" not during a rather small timeline - so stable.

jaguartrials

Toby You've got more problems than you think.

meetdilip

Unless you maintain an official add-on base for popular features, it's going to be a headache. Even Google has come up with project Treble to solve such issues.

amdad

Thanks for answer Toby. Engine doesn't matter, performance does. So anything that can make search fast will be good. Extensions would have sense only if default one will not be quick enough.

bachmx

Oh, can not wait for 0.4.

Eldenroot

bachmx cant wait for 1.0 ?

Sabo

Are we there yet mom? ?

FebriTriHarmoko

wow... good news :thumbup:

[deleted]

Toby

YAAAAAAASSSSSSS FINALLY!!!!!!!

Pollux

[deleted] I just created a new tech forum

... and already have the first spam ... ?

datitisev

[deleted] Most likely, as Flarum is the successor of Esotalk, and created by Toby. Don't quote me on that, though.

Prosperous

[deleted] I do believe Toby has mentioned a couple of times before in various topics that there will be cross-compatibility with esoTalk. You should be all good using it in the interim and migrate later once stable is here if that's what you're waiting on.

Ralkage

Prosperous it's also listed on the Flarum features page too ?

http://flarum.org/features/

"Once Flarum is stable, we plan to build importers so you can easily migrate your data from older forum software such as esoTalk, FluxBB, and more."

Not like anyone reads that page anymore or anything even being a tad outdated ? (I read 3deep into Flarum before I became part of this community and was sold on the idea".

Blueh

Ralkage

"coming son features" will be make by "core team"?

Sapioit

I'm sad that nowhere is it mentioned removing the composer dependency for deploying things. Instead, a php script which to fetch an archive from a CND and unpack it, for the latest version of everything. That could also be paired with changing the update system to include that.

clarkwinkelmann

Sapioit a php script which to fetch an archive from a CND and unpack it, for the latest version of everything

You know who developed exactly that ? The Composer team ? It's not used without reason, it does a fantastic job to this very task: host, manage, download and handle versions between all packages !

I don't think Flarum should drop it, it's a big plus to help code quality. However making user-friendly interfaces around it is definitely a necessity. That's what we've been working on at Flagrow with Bazaar.

I guess you mean CDN by the way ?

« Previous Page Next Page »