Idea for a future construct

With all the talk about C3 coming some time in the future, I have been thinking about how this "visual" coding could be taken further. Here are some ideas (the visuals are just to illustrate the idea):

We could have much the same properties as now, but change the way they can be set - not with behaviours, but with modular "controllers" - since most behaviours can be sorted by either what they effect or what values they produce. Click the little plug and a panel opens...

You could pick a controller and link it to any property that accepts a value - perhaps even link several controllers to do what would take plenty of actions and variables in one click.

Here's an example - if you want a sprite to rotate, for example, add a cycle controller to it with a range of 0-360 and time. Link the same to opacity and the sprite will fade out and then jump back to full opacity.

Or you could use the usual control options and, for example, link it to size with a ratio - so the sprite kinda stretches a little while moving. Enable and disable them as usual behaviours.

Well, just my 2 cents and 4 images - perhaps something Ashley could consider.

Who invented this? This visual coding visual theme looks very decent and professional kinda way. I would be glad to test this application or theme!

I just drew it to illustrate the idea, Naji. There's no usable stuff in there as is.

It would be nice to know which direction the new editor is going.

Linking with lines is a brilliant idea, surprised no one else has grabbed this idea and putt into a game engine to lessen the coding burden for game makers.

Very cool!

Cliffu There is something called PlayMaker for Unity that does the same, but I really like the block/"lines of code" style that Construct has, it feels much less messy than spaghetti lines.

but I really like the block/"lines of code" style that Construct has, it feels much less messy than spaghetti lines.

One reason I'm suggesting this for properties only - to keep the event sheet cleaner and leaner. Imagine having limiter controllers:

Just add one to values and that's it - no more different events checking where things are, if the values are within range, doing Value = clamp(Value+X,LowVal,HiVal) - just do a clean action and the system does the rest:

I really don't like line linking. It's always sort of unclear which data is going where, and in which direction - this gets confusing really quick - the 'spaghetti problem'.

I really like the event system because it makes a wonderful transition to learning real code. Events are basically real code, just with a few helpful constraints.

Here, that's quite abstracted away.

Just my thoughts, I'm by no means an expert in spaghetti

sqiddster

These diagram is another possible way to display the setting of object's properties. Like to add a behavior in C2 IDE.

I really don't like line linking. It's always sort of unclear which data is going where, and in which direction - this gets confusing really quick - the 'spaghetti problem'.

Never had a problem with that, especially with a setup like this where the main object is locked onto a side. But it's obviously a question of taste - the thing is this would act the same as behaviours, just more versatile - use it or use events. rexrainbow gets it.

Oh! I see now! Sorry for being dense.

Yeah, this is actually really cool, provided it had a solid connection with the event system.

Oh! I see now! Sorry for being dense.

Yeah, this is actually really cool, provided it had a solid connection with the event system.

Hehe, I see it as basically different behaviours - so all the same actions would be available - turn them on or off, etc. Just you see them at a glance and given how some could work with only values it gives a lot more freedom change or combine things.

I think a cool thing this "visual" way would allow would be modifiers, like this:

So you easily set, in this example, the time something is or isn't active - in this case the angle would change for one second, then wait half a second, then continue. Quite handy for platforms and such.

It is a behavior setting, too. IMO.

its really nesesery to change event system? for what?

Not talking about event system here, delgado.