for one thing, dev-c++ is able to read thru all the included files
& make lists of the objects & their members, functions, &
maybe even to some extent global vars. then autocomplete
works from those lists, and does it nicely.
sphere's autocomplete is actually ok, but it's main problem is
that it doesn't know what a var may be at its particular time
(an apparent strength of c++), so it doesn't let you
autocomplete something like:
<pre>
var img = LoadImage("someimg.png");
// now img is an img
img.blit... // it should offer autocomplete for any image
methods
</pre>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
JavaScript's loose type binding makes this nigh-on
impossible. The prototyping model pushes it over that mark.
The best that could be done is to show a list of possible
method signatures based on everything preceding the function
call opening parenthesis, and where would this information
fit in the interface?
If this is still a pressing issue after over a year, make
yourself heard at the Spherical forums. There's a feature
request thread there.
Logged In: YES
user_id=387078
How is dev-c++'s autocomplete more useful?
(Apart from sphere's autocomplete sucks and is turned off by
default)
Logged In: YES
user_id=988268
for one thing, dev-c++ is able to read thru all the included files
& make lists of the objects & their members, functions, &
maybe even to some extent global vars. then autocomplete
works from those lists, and does it nicely.
sphere's autocomplete is actually ok, but it's main problem is
that it doesn't know what a var may be at its particular time
(an apparent strength of c++), so it doesn't let you
autocomplete something like:
<pre>
var img = LoadImage("someimg.png");
// now img is an img
img.blit... // it should offer autocomplete for any image
methods
</pre>
Logged In: YES
user_id=1206940
JavaScript's loose type binding makes this nigh-on
impossible. The prototyping model pushes it over that mark.
The best that could be done is to show a list of possible
method signatures based on everything preceding the function
call opening parenthesis, and where would this information
fit in the interface?
If this is still a pressing issue after over a year, make
yourself heard at the Spherical forums. There's a feature
request thread there.
http://www.spheredev.org/forums/