Page MenuHomePhabricator

Does the MaterialEditor Bundle belong to CoreUI
Closed, ResolvedPublic

Description

There have been some complains that the MaterialEditor bundle is always build. This is due to the fact that all CoreUI bundles are build by default (the reason was that the "core things" should be, by definition, not optional). So does the bundle actually belong there?

If the bundle really needs to stay there, we can fix the default build option problem.

Event Timeline

What is the status of the material editor bundle (Jochen asked about it too...)?

I really think this bundle should be moved out of the CoreUI directory. I will move the bundle till monday if no one objects.

I also think that Material Editor does not belong to CoreUI. Thanks for noting and moving it out.

Okay, this is NOT okay!

Markus, you are on CC of this bug since I entered it and never replied. You moved it with a commit message on T2292, which has a core modification flag but is not really related to the problem described here.

I am putting some effort into the bug description and am writing a (small) specification page, just to find that you moved the bundle eleven days ago without notice on this bug.

:-(

(In reply to comment #5)

Okay, this is NOT okay!

:-(

I totally agree. The discussion should be continued outside of this scope.