does anyone have the latest on the status of the debugger window in Scipad ?
The link below suggests it has been 'unplugged' because of code
reorganisation but there is no date on the release
Scilab 5.1.1 Release Notes
http://www.scilab.org/download/index_download.php?page=5.1.1
Also, can someone say what development environment they are using that
allows code completion of Scilab objects and is there an object map around ?
thanks and regards
David
You'll never have it again in Scilab 5.
Check out this interesting thread and references therein (this is 6
months old but I have nothing to change in what I said at this time).
The latest news is that the opteam has now developed this new editor
("xpad") in Java, and kicked out Scipad from Scilab (but you might get
it with ATOMS). In its current development state my opinion is that
xpad is just not a usable tool due to very basic bugs and flaws.
Also, xpad does not feature a debugger. Again, what I stated 6 months
ago in the above thread is still my opinion:
"Scicoslab is the only maintained environment featuring the debugger.
Scicoslab-4.3 provides a reasonably recent version of Scipad (7.4.BP3
- 20/09/08) that includes all the latest major improvements of the
debugger (e.g. conditional breakpoints). If you want the debugger I
don't see any other possible choice."
Good luck.
Francois
This one, sorry:
Francois
regards
David
"Francois Vogel" <fsvogeln...@free.fr> wrote in message
news:4ad9ac2f$0$9977$426a...@news.free.fr...
Is there a "Scilab has no debugger" bug? Does the Scilab bugbase have a
"vote for this bug" feature (OpenOffice has this).
I don't particularly care if the debugger is in Scipad or in its own
window or what (in fact, I'd just as soon they figure out how to
integrate Scilab with Eclipse for debugging). But debugging would be
awfully nice.
Hmm, not exactly. It has a "Scipad debugger is broken" bug (#2789):
http://bugzilla.scilab.org/show_bug.cgi?id=2789
This bug has just been tagged this week with "Fix_me_for_Scilab_5.2"
tag. I'm wondering how it will be fixed in Scilab 5.2 (that is
supposed to be released in October this year).
Feel free to comment in bug 2789, or to open a new bug if you think
it's appropriate.
> Does the Scilab bugbase have a
> "vote for this bug" feature (OpenOffice has this).
My understanding is that the Bugzilla software is featuring votes but
that this feature is not enabled in the Bugzilla configuration that is
specific to Scilab.
I have asked that question about voting for bugs a long time ago in
the developers mailing list, see the discussion here:
http://lists.scilab.org/cgi-bin/ezmlm-browse?list=dev&cmd=showmsg&msgnum=370
Francois
I understand your choice, here is the link:
> And is there a (UML) object map for Scilab ?
I'm not aware of this, sorry, but I'm interested by the answer as well.
Francois
"Francois Vogel" <fsvogeln...@free.fr> wrote in message
news:4adacc83$0$19298$426a...@news.free.fr...
Were there not plans afoot to replace Scipad with an entirely different
IDE? What's the status of that effort? Is there a bug associated with
_that_?
(I'm in a 'rock the boat' mood today: I want to get on that bug's page
and point out that Eclipse is a really nifty IDE that lots of people are
already familiar with and like, and that rather than reinventing the
wheel perhaps it would make more sense to give Scilab an Eclipse-
compatible debugging interface.)
I think the status of the development of the opteam's replacement for xpad
is reflected in the bugzilla. Check it against the "Text Editor" (aka Xpad)
item:
All bugs:
http://bugzilla.scilab.org/buglist.cgi?&component=Text+Editor
All open bugs:
http://bugzilla.scilab.org/buglist.cgi?&component=Text+Editor&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
Browsing through this list will quickly convince you that this piece of code
is just not usable, at least for the time being. Fortunately they did not
release it to the wild.
> (I'm in a 'rock the boat' mood today:
How funny, I've just seen this movie "The boat that rocked"!
> I want to get on that bug's page
> and point out that Eclipse is a really nifty IDE that lots of people are
> already familiar with and like, and that rather than reinventing the
> wheel perhaps it would make more sense to give Scilab an Eclipse-
> compatible debugging interface.)
I know no word from the opteam about any plans for having again a debugger,
be it in Eclipse or not. Where is the roadmap again?? ;-)
Francois