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
> 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
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."
Thanks Francois, as a new user I think I will fall back to the verson that has conditional break points and watch variables etc. And is there a (UML) object map for Scilab ?
regards
David
"Francois Vogel" <fsvogelnew5NOS...@free.fr> wrote in message
> Francois Vogel said on 17/10/2009 13:34: >> 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).
On Sat, 17 Oct 2009 13:34:57 +0200, Francois Vogel wrote: > David K said on 17/10/2009 07:02: >> 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
> 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
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.
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:
> David K said on 17/10/2009 20:57: >> Thanks Francois, >> as a new user I think I will fall back to the verson that has conditional >> break points and watch variables etc.
> 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:
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.)
"Tim Wescott" <t...@seemywebsite.com> a écrit dans le message de news: oaidnRrceq1FvXLXnZ2dnUVZ_s1i4...@web-ster.com...
> 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 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:
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?? ;-)
|
