I think that there is a key aspect in the story: Risk management.
In addition I see the following problems: addition without removal.
- if we integrate bloc in the future it means that we will have Athens for
Morphic and the tools that we will use while
developing the rest AND Sparta for the external window.
Now I think that we should throw away Athens if it does not support the
future scenario but have
a Sparta-MorphicFriendly variation to replace Athens so that we can
continue to work.
I mean we CANNOT continue to stack libraries on the side of each others.
Because it makes us super slow to move.
This is also a part of risk management. Each time that we improve the
**current** infrastructure
we build a MILESTONE. If you want to go the everest you build intermediary
camps in case of tempest you can rest there and restart.
In Bloc and Brick I see no camp.
Let us look at SDL and OS-Window. So now it is bad and terrible.
If we do not do anything we will have MorphHand the ugly + SDL20 is not
useful + OSWindow the stupid + GTK the great
Come on this is not possible!
If you do not prepare integration and milestone I can tell you that the
integration will not happen.
And your risk gets higher and higher.
So far I did not see any roadmap and a roadmap should place such concerns
on the table.
For me having Bloc and Brick with horrible borders around the windows
would be just perfect.
And not having SVG support for hyper fancy morphs too.
Let us think incrementally.
Why we cannot have a scenario
- Default and Simple
- Advanced and risky where you load your mozz2d lib
Stef
PS: I agree with norbert.
