[vwnc] SUnit Status Bar is not shown
Locked
[vwnc] SUnit Status Bar is not shown
 
|
Hi all,
I am very novice developer, when it comes to SmallTalk and Visual Works. This time I have a very strange issue. I want to write test cases for a class. Thus, I loaded parcel "RBSUnitExtensions" from Essential , using Parcel Manager. I also make sure, that, "SUnit" and "SUnitUI" parcels are already loaded by Visual Works. Now, when I create a Class extending "XProgramming.SUnit.TestCase", I should be able to see SUnit Status bar, containing buttons like Run Defect, List Defects, Profile, Debug, Run etc. (in disabled mode, since, I haven't written any method yet) in the Browse Window, when I select that Class. This is not happening. Even if I wrote a method(test case), still no such SUnit status bar is shown. Question is -> Why can't I see, SUnit Status Bar for test cases? ( I am using Visual Works 7.6, non-commercial product). Can anybody Please, help me out in this matter?? Thanks Kulkarni Simit S. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [vwnc] SUnit Status Bar is not shown
|
|
If the browser’s tabs above the protocols and methods are set to
show Class methods, it won’t show up. Select Instance instead. Selecting “Instance
Variable” or, oddly, ”Shared Variable” also works. Steve From: [hidden email]
[mailto:[hidden email]] On Behalf Of Simit Kulkarni Hi all, _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [vwnc] SUnit Status Bar is not shown
|
|
In reply to this post by Simit Kulkarni
Dear Simit,
suggestion (apologies if I'm pointing out the obvious): the RBSUnitExtensions updates new browsers; you will not see a change to an existing browser you had open before you loaded RBSUnitExtensions. (BTW I think you do not need SUnitUI to run RBSUnitExtensions. SUnitUI provides the alternative TestRunner UI. This is a basic 'looks the same on all dialects' UI for running tests.) HTH. Yours faithfully Niall Ross > Hi all, > > I am very novice developer, when it comes to SmallTalk and > Visual Works. This time I have a very strange issue. > > I want to write test cases for a class. Thus, I loaded parcel > "RBSUnitExtensions" from Essential , using Parcel Manager. I also make > sure, that, "SUnit" and "SUnitUI" parcels are already loaded by Visual > Works. Now, when I create a Class extending > "XProgramming.SUnit.TestCase", I should be able to see SUnit Status > bar, containing buttons like Run Defect, List Defects, Profile, Debug, > Run etc. (in disabled mode, since, I haven't written any method yet) > in the Browse Window, when I select that Class. *This is not > happening*. *Even if I wrote a method(test case), still no such SUnit > status bar is shown.* > > Question is -> Why can't I see, SUnit Status Bar for test cases? ( I > am using Visual Works 7.6, non-commercial product). > > Can anybody Please, help me out in this matter?? > > > Thanks > Kulkarni Simit S. > >------------------------------------------------------------------------ > >_______________________________________________ >vwnc mailing list >[hidden email] >http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
[vwnc] SUnit Status Bar is not shown
|
|
In reply to this post by Simit Kulkarni
Hi Niall,
Sorry for such a late response. But, Thank you so much for your response. That solved the puzzle. I felt really silly for raising such a problem. But this is strange , isn't it? Because, when we load package RBCodeHighlighting, change is immediately applied to the browser, but this is not happening, in case of RBSUnitExtensions load. Anyways thanks again! Thanks & Regards Kulkarni Simit S. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [vwnc] SUnit Status Bar is not shown
|
|
On Dec 2, 2008, at 11:38 PM, Simit Kulkarni wrote:
> Hi Niall, > Sorry for such a late response. But, Thank you so much for your > response. That solved the puzzle. I felt really silly for raising > such a > problem. > But this is strange , isn't it? Because, when we load package > RBCodeHighlighting, change is immediately applied to the browser, but > this is not happening, in case of RBSUnitExtensions load. > Anyways thanks again! I know that some of the later versions of RBSUnitExtensions and/or SUnitToo(ls) put a message in the transcript telling you to open new browsers. There are some who would like to believe that any IDE modifying package load can immediately take affect. To the extent that all it changes is behavior, I see no problem with this. But as soon as it starts changing state, the equation gets trickier. RBSUnitExtensions changes code, which is used at browser construction time, to assemble the state of the browser. So it can be tricky to figure out, after the tool is loaded, how to replay the parts of that state assembly that leave the existing state intact, but add your new state to it as well. RBCodeHighlighter is really no different. But it deceives you into thinking it takes affect right away. Because after we load a package, we do a navigate in the open browsers, which causes it think a method has been selected, which causes the method source tool to be rebuilt. Thus picking up on the new algorithm or creating state. To see otherwise, open the inspector on Object, flip to the "methods" view, and look at some methods without the RBCodeHighlighter loaded. Now load the highlighter, your inspector doesn't suddenly start highlighting. You have to get it to rebuild that view (open a new one, force a dramatic navigate, etc). I'm not saying fixing up instances on the fly is impossible at all. Just that it's not always worth the ROI. -- Travis Griggs Objologist Time and Countertops. They both get used up way too fast. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [vwnc] SUnit Status Bar is not shown
|
|
Actually, for VW7.6 the code highlighter does take effect immediately, but it does so by cheating. It doesn’t really affect the browser state because it swaps the existing text editor controller in place without requiring components to be rebuilt. The new controller implements the highlighting. What might not be true is that it doesn’t refresh the display, causing any displayed text to be highlighted. My branch (63.4.*) should cause the refresh because it handles controller management a little differently. The VW7.7 branch does all of the highlight management different, so the jury is out on that.
Of course, that has nothing to do with the SUnitToo(ls) status bar changes.
Cheers!
Tom Hawker -------------------------- Senior Framework Developer -------------------------- Home +1 (408) 274-4128 Office +1 (408) 576-6591 Mobile +1 (408) 835-3643
-----Original Message-----
On Dec 2, 2008, at 11:38 PM, Simit Kulkarni wrote:
> Hi Niall, > Sorry for such a late response. But, Thank you so much for your > response. That solved the puzzle. I felt really silly for raising > such a > problem. > But this is strange , isn't it? Because, when we load package > RBCodeHighlighting, change is immediately applied to the browser, but > this is not happening, in case of RBSUnitExtensions load. > Anyways thanks again!
I know that some of the later versions of RBSUnitExtensions and/or SUnitToo(ls) put a message in the transcript telling you to open new browsers.
There are some who would like to believe that any IDE modifying package load can immediately take affect. To the extent that all it changes is behavior, I see no problem with this. But as soon as it starts changing state, the equation gets trickier. RBSUnitExtensions changes code, which is used at browser construction time, to assemble the state of the browser. So it can be tricky to figure out, after the tool is loaded, how to replay the parts of that state assembly that leave the existing state intact, but add your new state to it as well.
RBCodeHighlighter is really no different. But it deceives you into thinking it takes affect right away. Because after we load a package, we do a navigate in the open browsers, which causes it think a method has been selected, which causes the method source tool to be rebuilt. Thus picking up on the new algorithm or creating state. To see otherwise, open the inspector on Object, flip to the "methods" view, and look at some methods without the RBCodeHighlighter loaded. Now load the highlighter, your inspector doesn't suddenly start highlighting. You have to get it to rebuild that view (open a new one, force a dramatic navigate, etc).
I'm not saying fixing up instances on the fly is impossible at all. Just that it's not always worth the ROI.
-- Travis Griggs Objologist Time and Countertops. They both get used up way too fast.
_______________________________________________ vwnc mailing list http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
| Free forum by Nabble | Edit this page |