APIs appear colored in code

I was thinking maybe if when one is coding, the computer could detect APIs and make them a certain color, just like it does with loops, variables, and stuff in quotes. I know that this doesn't really happen with lua or whatever but it would be nice to add in.

I don't think Dan200 or any of the other devs feel like looking through all the api's and documenting their "keywords". The keywords are defined and set as a color within the edit file using a table. So, good luck with that :P/>

EDIT: If you wish, you can add to the pre-existing table and make the words whatever color you want!

I'm thinking about making an IDE. I'll link you if I ever get it done.

Dlcruz129, on 08 March 2013 - 04:38 PM said:

I'm thinking about making an IDE. I'll link you if I ever get it done.

It's a great idea, dont' get me wrong, the only problem being that there is an insane amount of APIs that would need to be documented thoroughly and updated frequently.

That reminds me, IDE needs to go on my list of programs to make.

SuicidalSTDz, on 08 March 2013 - 04:41 PM said:

Dlcruz129, on 08 March 2013 - 04:38 PM said:

I'm thinking about making an IDE. I'll link you if I ever get it done.

It's a great idea, dont' get me wrong, the only problem being that there is an insane amount of APIs that would need to be documented thoroughly and updated frequently.

That's why you reference them before importing them.
In visual studio (known for being a damned awesome IDE) you have to reference a library before you can use it, after which all of it's features get registered into the syntax analyser, available for highlighting (assuming you remember to put the using line at the top of the page).
In theory you could cheat by running the API, then pulling apart it's components, noting their name and type (using pairs() ofc) then caching that data for use in the lexical analyser. If the file updates, force the IDE to recache it. Cheating but simpler than you think.

Pharap, on 08 March 2013 - 04:57 PM said:

That reminds me, IDE needs to go on my list of programs to make.

SuicidalSTDz, on 08 March 2013 - 04:41 PM said:

Dlcruz129, on 08 March 2013 - 04:38 PM said:

I'm thinking about making an IDE. I'll link you if I ever get it done.

It's a great idea, dont' get me wrong, the only problem being that there is an insane amount of APIs that would need to be documented thoroughly and updated frequently.

That's why you reference them before importing them.
In visual studio (known for being a damned awesome IDE) you have to reference a library before you can use it, after which all of it's features get registered into the syntax analyser, available for highlighting (assuming you remember to put the using line at the top of the page).
In theory you could cheat by running the API, then pulling apart it's components, noting their name and type (using pairs() ofc) then caching that data for use in the lexical analyser. If the file updates, force the IDE to recache it. Cheating but simpler than you think.

My point still stands :P/> I don't think Dan or any devs have time to be doing this, nor do they really have a need to.

My IDE will constantly scan code for user-created functions, and will scan files loaded with os.loadAPI(). If the user types an un-recognized function, it will display a warning which may be dismissed. I'm trying to make it extremely noob-friendly, if a noob types print(hi world), it will notify the user and have a quick-fix button to add "s. It's very large and ambitious, but I think I can handle it with enough time.

SuicidalSTDz, on 08 March 2013 - 05:02 PM said:

Pharap, on 08 March 2013 - 04:57 PM said:

That's why you reference them before importing them.
In visual studio (known for being a damned awesome IDE) you have to reference a library before you can use it, after which all of it's features get registered into the syntax analyser, available for highlighting (assuming you remember to put the using line at the top of the page).
In theory you could cheat by running the API, then pulling apart it's components, noting their name and type (using pairs() ofc) then caching that data for use in the lexical analyser. If the file updates, force the IDE to recache it. Cheating but simpler than you think.

My point still stands :P/> I don't think Dan or any devs have time to be doing this, nor do they really have a need to.

I wasn't intending them to. I was intending someone to hear the idea and try to incorporate it into their own IDE because they think it sounds cool lol
IDEs are fiddly but worth the effort if done right.

Dlcruz129, on 08 March 2013 - 05:37 PM said:

My IDE will constantly scan code for user-created functions, and will scan files loaded with os.loadAPI(). If the user types an un-recognized function, it will display a warning which may be dismissed. I'm trying to make it extremely noob-friendly, if a noob types print(hi world), it will notify the user and have a quick-fix button to add "s. It's very large and ambitious, but I think I can handle it with enough time.

Never say will when planning to make a program, 'will' usually jinxes things with the curse of procrastination or great difficulty lol
Not doubting you can't do it, just try avoiding saying 'will', use 'I intend to' or 'I hope to' it makes it easier to back down if need be lol