Join GitHub today
Editor: Theme #50
The editor could get a little lift
There is just too many information, and too many colors, contrast is weird
Should go with a real dark / light theme, not something in the middle
Unity is about to get a new theme, the current one is already readable, but the new one is even better, it put the focus on the scene view, nothing busy, nothing fancy
That's a good idea. We never took the time to properly cleanup the theme.
Most of the colors/styles/templates are defined in https://github.com/xenko3d/xenko/blob/master/sources/presentation/Xenko.Core.Presentation/Themes/ExpressionDark/Theme.xaml. There might be some other location where the colors are hardcoded, so that would be a good time to cleanup that and make sure everything is in the same theme.
Once that is done, the next step would be to provide a white/gray theme. Some people don't like dark themes (for example Michael from GameFromScratch). A high-contrast theme could also be a good idea.
It's not cross-platform. It's hard to maintain and extend. You need to host your game in another environment which make things more complicated. WPF (and all xaml based products in general) is complicated and over-engineered beast.
What we need is an editor as unified platform for content authoring tools and runtime components as assets/packages developed by community. Xenko developers should really focus on providing such platform first, not on implementing specific tools on top of old WPF editor.
@qril I don't think you realize how big a task it is to implement such UI. We are talking about months (years?) of development with no guarantee to reach the same level of functionalities that are currently available in the editor.
Until our community grows is a much higher number, I don't think it is worth to spend time on that.
So what? The market/target audience for games is mostly on Windows and mobiles. Xenko already supports building for Linux, Xamarin and MacOS could be supported. Even then, you would not make a game only for Linux or MacOS anyway but you would also target Windows. Therefore having the editing/build tools on Windows only is not such a big deal.
Not necessarily. WPF has some limitations but it is not that hard to maintain, especially with its templating/style capabilities. But if you are talking on extending the editor itself, then WPF is not a limiting factor. We can make it work to allow plugins. In fact, although incomplete, its architecture is already plugin-based in some areas. And we could also look at pattern/libraries such as Prism.
I'm not saying that if someone or a group of people wants to start to work on a new editor, they shouldn't. By all means, if you are motivated, go for it. But I don't think that it should be the main focus of the community.
All that said, you have the right to disagree with me.