> This anti coding/scripting mentality on the forums is disheartening. Providing users with as many options as possible should be the goal, not limiting it to a click only interface. Certain individuals do not like coding or simply are unable to do it, and thats why the event system is so great for them. Others love it and enjoy it and are desperately trying to work with the event system in a way that flows like the way they code and script.
> I spent good money on the software and so have many others that like coding/scripting. Our opinions are just as relevant as those that do not like coding.
You spent your good money on a codeless developer tool. Whoops.
Nearly limitless options already exist through programming. C2 seeks to port as much of that functionality over to a codeless environment as they can. That's my understanding of it, anyways. If you want a coding environment with WYSIWYG, you have plenty of options elsewhere. And with C2, you have the SDK which is developed hand-in-hand with the primary software. And nobody I've seen is against its use. So if you want to code, use it.
And why do you feel that providing as many options as possible is not a goal here? It's just trying to make those options available without coding. That's the whole point, as it has been since day one so far as I can tell.
If you bought this software to code in a way that isn't accessible in C2, then you made a mistake.
Why whoops? I made a whoops because I see validity in the opinions others have for scripting and coding with game development? Whoops because you assume I made a purchase without knowing exactly what I was buying? I knew exactly what I was spending my money on when I bought construct. I have followed it for quite some time. I was agreeing with others who make points about scripting and understand their point of view.
Instead of having a constructive conversation you simply point to the door to seek alternative solutions.
Also I remember "day one" including python scripting.
Yeah, I apologize. Conditions of last night left me in a poor mood, which I needlessly revealed in my statements to you.
While I disagree with the tone I used to say it, particularly the portions directed at you personally, I still maintain that C2 should focus on its event-based scripting, and that the SDK, along with any other plug-ins (apparently C2 is modulated in such a way that plug-ins can come into effect through tremendously variable means) should be the sole conventional coding apparatus for the foreseeable future.
And while I don't disagree that having something like a "split-screen" (code/design) view in the event editor would be a nice addition, my understanding is that it is not practical in C2, and would have to be forged with that intent from the start, like in Microsoft Visual Web Developer 2010, or GWT Designer (which I cannot install!!! <img src="smileys/smiley7.gif" border="0" align="middle" /> ).
So yeah, I apologize for my initial tone. I certainly didn't mean to appear to be pointing at any doors, and indeed should not have been pointing at all.