It looks like we have a troll
http://i.imgur.com/BAsp1pv.png
Would it sound jaded if I were to be surprised that it took this long... <img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing"> <img src="{SMILIES_PATH}/icon_rolleyes.gif" alt=":roll:" title="Rolling Eyes">
jayderyu:
You can roll back, right?
> If there are customizable windows, and associated actions. Then the architecture can already support the request down the road. Either by Scirra or some one else.
>
Extensions are great and all, but I want the main software to function well from the get go. I'm already going trough nightmare of custom extensions in other software I'm using, and I don't C2 to be this way.
This +1000.
I know the whole point of this thread is to articulate how C3 should be more open to tinkering and third-party-extensions, but megatronx makes a really good point: we need basic functionality that works. I just don't want to see C3 typified by this response from Ashley (and/or other devs, if there ever are other C2 devs):
"Yeah, that's a good idea, and it's on the todo list, but you know, you can just add it yourself with the sdk."
Also, while I can think of all sorts of awesomeness that could come from custom IDE elements, such a feature must be designed so that extensions can be rolled into a capx on export (hopefully such a feature can be extended to plugs/behaviors/effects too).
Otherwise, we are going to be looking at an expansion of the dependency-hell that already affects many C2 projects due to third party plugins/behaviors/effects.
Anyway, don't mind me, just being the devil's advocate. Now, where's another parade I can piss on... <img src="{SMILIES_PATH}/icon_twisted.gif" alt=":twisted:" title="Twisted Evil">