Topic Editor as separate executable
This board is threaded (i.e. has a tree structure). Please use the Reply button of the specific post you are referring to, not just any random button. If you want to reply to the topic in general, use the Post button near the top and bottom of the page.
In Response to Luchs
I'd prefer to keep it as-is. Other downsides I can think of:
(1) Longer build. It's pretty slow already, having a third "openclonk" target would make it ~1.5 times slower.
(2) The build breaks often because noone builds openclonk-server during development. Introducing another #ifdef configuration may make this worse?
(3) Qt is also useful in fullscreen mode to open URLs.
Do we really want people to build openclonk without the editor anyways? The dev experience should be "oh I can just click that button and create my own stuff!", not "I think there's some way to create scenarios, but I have to install the editor first".
(1) Longer build. It's pretty slow already, having a third "openclonk" target would make it ~1.5 times slower.
(2) The build breaks often because noone builds openclonk-server during development. Introducing another #ifdef configuration may make this worse?
(3) Qt is also useful in fullscreen mode to open URLs.
Do we really want people to build openclonk without the editor anyways? The dev experience should be "oh I can just click that button and create my own stuff!", not "I think there's some way to create scenarios, but I have to install the editor first".
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill