Migrate to a trait-based implementation

[etrepat]

Starting from L4.2, support for PHP 5.3 has been dropped.

It's time for Baum to try to move to a trait-based implementation so that we can "mix-in" nested set functionality instead of inheritening, which will improve composability.

I'm thinking of leaving the 1.0.x branch as-is (with needed bug-fixes) with a tag like 1.0.x-stable. Then start a 1.1 branch with the new implementation.

[J5Dev]

This would be fantastic, and much welcomed.

I have been working on implementing Baum into my project, though have hit the stumbling block of wanting to use Polymorphic categories, as I have a number of categoriseable (word?) entities within my project. The only way I have been able to achieve this is to actually not use polymorphism, and instead go for NewsCategories, BlogCategories, QuestionCategories etc... which shoots down removing re-use of code.

Obviously, moving to a Trait based system would hopefully allow me to do something a little simpler.....

That is, unless I've missed something and could do this a simpler way as-is :)

[Garbee]

A 2.0 branch would be preferred since it is a backwards incompatible change and you don't know how others have configured their composer's to pull the 1.x branch.

I do highly encourage a trait move though, it would be fantastic to use this with other tools that also require extending a class.

[garygreen]

+1 a million times to this. Time to move onwards and upwards, keep up with the trends :-)

[deletosh]

+1 severally to this -- any update in the pipeline?

[jackdbrowne]

+1 really hoping this happens!

[Atorich]

+1 it would be great

[dimsav]

+1

[stevebauman]

Any update on this? Definitely interested in a trait based implementation

[andrewmy]

+1

Currently using Polyglot for multi-language models which also uses a base model to inherit from.

[tabacitu]

+1

Would have used in it in 4 projects if it were trait-based.