We've decided to start the ball rolling with a beta release for Dolphin 6.1.
Unlike our previous beta programmes this one will be public rather than closed, although you will have to have a valid Dolphin Professional license to take part (i.e. Dolphin Community Edition keys will not yet unlock the installer).
As you'll see, this release offers quite a few bug fixes to 6.02 and a number of enhancements. The latter are things like: better cosmetic appearence under Vista, the ability to save out Idea Space templates and an SUnit Plugin for the Class and System browsers.
Actually, although we've called this a beta, in some ways it's more like an alpha. There are a number of features we'd still like to add to the IDE, particularly in the area of the STS integration and these should appear in the next beta release.
Please use the Dolphin Newsgroup (comp.lang.smalltalk.dolphin) for any discussion about the beta.
I just installed it on Windows XP home. When I opened the Class Diagram (I like it very much :-) ) I got a warning in the System Transcript about a missing file: msmask32.ocx . I downloaded it from the Internet and no more warning.
All installed without any problem and, with one minor exception, all my "working image" packages installed without any flagged errors at all. I'll try redeploying my apps next - that's usually a good test.
The only problem I can see is that, due to the recent change in US regulations, the icon for the Idea Space should really depict an energy saving bulb :-)
Fantastic news! Thank you very much for all your efforts.
I have installed the Beta 1 on Windows XP (32Bit) and Windows Vista (64Bit) with the following first findings:
1. Under XP I have a problem in the Class Browser and the System Browser: The text ("Instance") of the first radio button in the Methods window is broken into two lines because the next radio button ("Class") is too close to it. I have chosen a bigger font size in Window's System Settings.
2. When I select a method in a Class Browser's or a System Browser's Methods window, the leading icons of the highlighted row are hidden. This happens only under Windows XP, not under Vista. As far as I remember this problem already existed with Dolphin 6.02.
3. The Method Spies package from Solutions Software does not load anymore. SSWDebugger class>>initialize does not compile because "SkipMethods" is unknown.
Later this day I will start some tests with ReStore from Solutions Software.
> The only problem I can see is that, due to the recent change in US > regulations, the icon for the Idea Space should really depict an > energy saving bulb :-)
That would give new meaning to the panic button - it would have something to do with cleanup after dropping the bulb ;)
Have a good one,
Bill
-- Wilhelm K. Schwab, Ph.D. bi...@anest4.anest.ufl.edu
> 3. The Method Spies package from Solutions Software does not load > anymore. SSWDebugger class>>initialize does not compile because > "SkipMethods" is unknown.
gives an Error ("This methhod did not compile") when loading the Package. The debugger says: Error: undeclared 'SkipMethods'. SkipMethods used to be a LookupTable in D6 and now it seems to be gone.
>> 3. The Method Spies package from Solutions Software does not load >> anymore. SSWDebugger class>>initialize does not compile because >> "SkipMethods" is unknown.
> I still don't know what happens here:
> SSWDebugger class>>initialize > super initialize.
> gives an Error ("This methhod did not compile") when loading the > Package. The debugger says: Error: undeclared 'SkipMethods'. > SkipMethods used to be a LookupTable in D6 and now it seems to be gone.
> Any comments?
Some time ago, John Aspinall of Solutions Software gave us permission to include the Method Spies/Breakpoints package as part of Dolphin 6.1. So one of the tasks in the weeks to come is to get this into the next beta. I'd have to take a look at why the package is refusing to load, which I haven't the time to do right now.
BTW, both the Methods Spies and the Source Tracking System will be available in the free DCE version of Dolphin 6.1. The presence of STS in all versions should go some way towards promoting the STS export format as a global exchange mechanism for all Dolphin users. Indeed, we're hoping that David Gorisek (author of STS) will find time to finish a WAN version of STS which can then be used as a central respository for all shared code.
On 10 August 2007, Andy wrote, "We will try to issue the 6.1 maintenance release that we have been using internally (wrapping all outstanding bug fixes) before the end of this year." (http://www.object-arts.com/content/blog/2007Aug10.html). Other than being a few days late (on a prediction made months ago!), this does not seem to indicate any change in the situation.
I'm very appreciative of the continued contributions of Andy and Blair to the Smalltalk community.
James Foster
"Fernando Rodriguez" <fernandoREMOVE_T...@easyjob.net> wrote in message
>>> 3. The Method Spies package from Solutions Software does not load >>> anymore. SSWDebugger class>>initialize does not compile because >>> "SkipMethods" is unknown.
>> I still don't know what happens here:
>> SSWDebugger class>>initialize >> super initialize.
>> gives an Error ("This methhod did not compile") when loading the >> Package. The debugger says: Error: undeclared 'SkipMethods'. >> SkipMethods used to be a LookupTable in D6 and now it seems to be gone.
>> Any comments?
> Some time ago, John Aspinall of Solutions Software gave us permission to > include the Method Spies/Breakpoints package as part of Dolphin 6.1. So > one of the tasks in the weeks to come is to get this into the next beta. > I'd have to take a look at why the package is refusing to load, which I > haven't the time to do right now.
These are good news. Method Spies are a valuable IDE enhancement.
> i get an "Image version mismatch" and a crash on opening a Class > Browser.
I don't understand this. "Image version mismatch" is an error that can be generated when starting Dolphin using the wrong VM for the image file being used. Yet you say the error occurs when opening a class browser (so the image must already be started).
Can you let us know the exact sequence of events you go through to see this error so we can try and reproduce it.
> Please use the Dolphin Newsgroup (comp.lang.smalltalk.dolphin) for any > discussion about the beta.
Thanks for the bug reports/encouragement so far. Just to let you know that, in order to keep newsgroup traffic down, we won't acknowledge bug reports here unless we need more information to track the problems down but rest assured that we will be recording all the issues as they crop up.
> > i get an "Image version mismatch" and a crash on opening a Class > > Browser.
> I don't understand this. "Image version mismatch" is an error that can > be generated when starting Dolphin using the wrong VM for the image file > being used. Yet you say the error occurs when opening a class browser > (so the image must already be started).
> Can you let us know the exact sequence of events you go through to see > this error so we can try and reproduce it.
> Best regards
> Andy Bower
Andy,
i installed 6.1 on my machine, which has 6.0 installed. I started my old image and got the "Image version mismatch".
In that image i get the crash when opening a new Class Browser.
I packaged my project, uninstalled 6.0, started a new image in 6.1, installed my package and it worked fine for some hours. Now i can´t open my image again "An unhandled win32 exception occurred in Dolphin.exe [5544]" :-(
I'm having a similar problem as Marco's. I had 6.0 installed in a machine with Win XP sp2. I installed 6.1, then tried to open a 6.0 image and got "Image version mismatch". Then I uninstalled 6.1 and reinstall 6.0, but still can't open an image by double clicking on it. I've tried deleting the img associaton in every form I can imagine, but still can't get it. After the "Image version mismatch" message box there is another one suggesting that I regsvr32 DolphinVM???.dll, but the registration fails (the actual file is DolphinVM006.dll). Dropping the 6.0 image file on the 6.0 Dolphin.exe works just fine.
I uninstalled the 6.1 because the Class Browser flickered a lot with any selection change. It was running on a really really slow machine, but 6.0 is ok in the same machine.
On Jan 7, 3:21 am, Andy Bower <bo...@SnipThisObject-arts.com> wrote:
> Folks,
> > Please use the Dolphin Newsgroup (comp.lang.smalltalk.dolphin) for any > > discussion about the beta.
> Thanks for the bug reports/encouragement so far. Just to let you know > that, in order to keep newsgroup traffic down, we won't acknowledge bug > reports here unless we need more information to track the problems down > but rest assured that we will be recording all the issues as they crop up.
Andy,
First, thanks! Second, I have to ask, I wasn't expecting any more Dolphin updates from you or Blair. While I doubt this marks a return to OA, does this mean that we can expect future updates to Dolphin (as rare as they may come)? Or is it just that Dolphin 7.0 will never come out?
Sorry, I don't mean to beat a dead horse, but I figured Dolphin was pretty much "dead" in that it may never work with future versions of Windows, etc. Seeing a post like this on the forums almost brought a tear of joy to my eye. :)
Jeff M. wrote: > On Jan 7, 3:21 am, Andy Bower <bo...@SnipThisObject-arts.com> wrote: >> Folks,
>>> Please use the Dolphin Newsgroup (comp.lang.smalltalk.dolphin) for any >>> discussion about the beta. >> Thanks for the bug reports/encouragement so far. Just to let you know >> that, in order to keep newsgroup traffic down, we won't acknowledge bug >> reports here unless we need more information to track the problems down >> but rest assured that we will be recording all the issues as they crop up.
> Andy,
> First, thanks! Second, I have to ask, I wasn't expecting any more > Dolphin updates from you or Blair. While I doubt this marks a return > to OA, does this mean that we can expect future updates to Dolphin (as > rare as they may come)? Or is it just that Dolphin 7.0 will never come > out?
> Sorry, I don't mean to beat a dead horse, but I figured Dolphin was > pretty much "dead" in that it may never work with future versions of > Windows, etc. Seeing a post like this on the forums almost brought a > tear of joy to my eye. :)
> Jeff M.
yes, Indeed - there was much excitement about this in our organization. May we hope?
I'm Korean who use multi byte character set(MBCS), so this X6.1 version solve the problem about Hangeul breaking in source editor. Maybe new version of Scintilla does that.
I hope to release more stable and more powerful tools for Windows OS.
|
