Survey: New Script Editor Ideas Thread

[Darthatron]

We may be on the wrong foot from an earlier conversation, but my only bit of advice would be to keep the syntax as simple as possible. XSE does a fine job of making sure that things are easy to read at a glance. There really is no need for syntax from languages like java or c++.

I don't think we're on the wrong foot?

Anyway, some people find C++ easier than things like XSE. I'll post a poll some time soon to see what the community wants.

 

[chrunch]

Yes, but a lot of people at PC wouldn't know C++ syntax, and it'd be easier for everyone to have a familiar scripting language. Why don't you go with the option to use either C++ or XSE/Pokescript style, like I mentioned earlier, though?

 

[droomph]

Yes, but a lot of people at PC wouldn't know C++ syntax, and it'd be easier for everyone to have a familiar scripting language. Why don't you go with the option to use either C++ or XSE/Pokescript style, like I mentioned earlier, though?

BASIC, however, is C/C++ syntax but with more easy-to-understand terms.

Well, wouldn't you think

#org @main
[B]if[/B] variable condition number
     [B]then[/B] statement

is easier to read than

#org @main
[B]compare[/B] variable number
[B]if2[/B] condition @statement

blahbitty blahbitty blah

#org @statement
statement

?
I get lost so much when reading scripts from the actual game...
C syntax is just more logical sometimes.

 

[Darthatron]

Yes, but a lot of people at PC wouldn't know C++ syntax, and it'd be easier for everyone to have a familiar scripting language. Why don't you go with the option to use either C++ or XSE/Pokescript style, like I mentioned earlier, though?

I probably will end up having both.

Well, wouldn't you think

#org @main
[B]if[/B] variable condition number
     [B]then[/B] statement

is easier to read than

#org @main
[B]compare[/B] variable number
[B]if2[/B] condition @statement

blahbitty blahbitty blah

#org @statement
statement

?
I get lost so much when reading scripts from the actual game...
C syntax is just more logical sometimes.

Agreed.

EDIT:

Spoiler:

Main:
____lockf
____iif (flag.pokedex == true) goto EndNow
____msgbox "Here, have a\nPokéDex." msgNormal
____setflag flag.pokedex
EndNow:
____release
____end

 

[war rock exe]

Sorry for the stupid question but could you please elaborate what you mean by "Templates"?

 

[droomph]

EDIT:

Spoiler:

Main:
____lockf
____iif (flag.pokedex == true) goto EndNow
____msgbox "Here, have a\nPokéDex." msgNormal
____setflag flag.pokedex
EndNow:
____release
____end

It's not that big of a deal, but was the "iif" part intentional?

 

[Darthatron]

It's not that big of a deal, but was the "iif" part intentional?

Yeah, iif stands for inline if. I figured this would allow people to keep using the current if, if they wanted.

 

[droomph]

Yeah, iif stands for inline if. I figured this would allow people to keep using the current if, if they wanted.

Well iif just looks like a typo.

And plus, why would you use compare when you have an inline if?

Ah, I don't know. Do whatever you want.

 

[Darthatron]

Well iif just looks like a typo.

And plus, why would you use compare when you have an inline if?

Ah, I don't know. Do whatever you want.

Right now it's all just concepts. I'm here to get ideas from users. So thanks for your feedback. :) You made good points.

 

[Satoshi Ookami]

I agree with droomph, iif really does not look very nice...
We should think of better command :D

 

[droomph]

Also, instead of if condition goto statement you should have the destination code included right after, but indented (by default).

Like so:
if condition call {

statement
return
}​

​

or:
if condition goto {

statement
end​

​

That way we won't have to scroll and match up numbers, or deal with seperating out brackets.

 

[Darthatron]

Taking what you guys said... What do you think looks better? Or perhaps some other way you have in mind? Please make suggestions. :)

Spoiler:

____LockF___//Shorthand for lock; faceplayer
____If Flag.Pokedex != True
____{
________MsgBox "Here, have a\nPokéDex." MsgNormal
________SetFlag Flag.Pokedex
____}
____REnd____//Shorthand for release; end

Spoiler:

____lockf___//Shorthand for lock; faceplayer
____if flag.pokedex != true
____{
________msgbox "Here, have a\nPokéDex." msgNormal
________setflag flag.pokedex
____}
____rend____//Shorthand for release; end

Spoiler:

____lockf;___//Shorthand for lock; faceplayer
____if (flag.pokedex != true)
____{
________msgbox("Here, have a\nPokéDex.", msgNormal);
________setflag(flag.pokedex);
____}
____rend;____//Shorthand for release; end

At the moment my idea is to let all of these syntaxes work, rather than having a specific one. But this could make tutorials very confusing since they could all be using different syntax.

 

[BattleChan]

Actually, I'd prefer version 3. It looks clear and has the best structure.

 

[Speedster]

I also prefer version 3. Reminds me the most of C# and seems very organized and simple to learn.

 

[Chaos Rush]

Definitely 3. It's most similar to GML (a language used in Game Maker that I'm familiar with), which in turn is similar to C++. And it looks the most sensible anyway.

 

[droomph]

I think two. It's just neater without all those semicolons.

 

[link12552]

Personally I LOVE the semi-colon, it makes thing so much more readable (especially having dealt with VB which doesn't use it)
Style 3 is a lot more pleasing to me (it's C#!!!!!!! yes, hahahaha evil laughter)
and it resembles C++/C and a couple of other scripting languages I've encountered over the years, which is good.
The fewer prog-languages we have to remember the better. :)

 

[droomph]

Oh, and also, I think it should have a custom pointer thing just like the flag namer.

For example, instead of memorizing bl #0x82E7BE0 we could just type in bl mod or another name like so.

Just a thought...

 

[Darthatron]

Yes, of course. I am currently coding the assembler and it includes that.

 

[Full Metal]

May I suggest something? PYTHON STYLE. ;)

flag_name = 0x123 #<- flag number.
flag_name2 = 0x456 #<- a different flag
@entry:
   lock();faceplayer()
   if flag_name:
           do_things();
   elif flag_name2: jump @next_label
   release; end;