Blockland Forums > General Discussion
Events Replacement - How would you prefer?
Tezuni 2.0:
I think this whole concept is great, but the reason things are simplified into event form is so that kids can use it.
So if this new idea is implemented, it should just be an alternative option for 'advanced' users.
Marcem:
Am I the only one who thinks that the current system is perfect for setting events? Maybe I'm just too used to Hammer.
LoserHero:
Current event system is fine. Reactor Worker has valid points in his argument that I agree with. I have never found myself stumped by the default event system , even when working on complex ideas that would be better done via script. Anyways, I don't think you'll find support from Badspot.
Rugged:
--- Quote from: Colten on November 20, 2011, 03:41:35 PM ---
--- Code: ---onActivate
pixel1
pixel2
pixel3
pixel4
setColor
red
--- End code ---
or maybe a more efficient way.
--- End quote ---
I would honestly love to see this sort of feature implemented. It would take away so much tediousness of constantly writing the same line over and over again, just having the same minor change in it every single time.
DontCare4Free:
This is like moving from the Ant DSL to a stripped-down version of Groovy/Python. Yes please.
Speaking of layout, some combination of RCX Code (image below) and NXT-G (picture even lower down) would both be pretty simple and fast to use, and pretty powerful. However, if that isn't possible (or isn't popular enough to be justified or making it look good would be too much work (as you said)), then my vote goes to text-based with somewhat Python-ish syntax (or M's on the bottom of page 1). With that comes, of course, a big need for documentation, since having it purely text-based can be a bit off-putting for newcomers.
RCX Code:
NXT-G:
The wires are basically the NXT-G equivalent of local variables, and the wire colour tells the data type (bool/int/string). The briefcase blocks stores/loads the data from named variables. There is also a similar block for file I/O (SaveVariable/LoadVariable).
Oh, and custom blocks (functions; these are present in both versions too):