- Pharo-dev - lists.pharo.org

Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixes applicable to Pharo

by StÃ©phane Ducasse

On Sep 26, 2008, at 10:07 PM, Simon Kirk wrote: > hi Stef. > > Hmm, strange. How are you viewing the diffs? If I browse the MCZ in > a Monticello browser I see extensions to these classes: > > BrowserCommentTextMorph > BrowserRequestor > CanvasCharacterScanner > Character > ConnectionQueue > GrafPort > MultiCanvasCharacterScanner > NaturalLanguageTranslator > Random > RemoteString > TranscriptStream > > Is this the diffs you're talking about? If so, I think they're > correct. It's possible my rough list below may have missed some > changes. I see the same but I cannot see the diff between the changes and what is in the image (for example in the merge tools I do not (changed) and the like. Stef > > > Cheers, > Simon > > On 26 Sep 2008, at 20:20, StÃ©phane Ducasse wrote: > >> Simon >> >> with which machine did you create you mcz? >> Because apparently I can see the diffs for other packages. >> >> Can somebody else check the pinesoft package I put in the pharoInbox? >> >> Stef >> >> >> >>> Hi all. >>> >>> Gary and I decided we ought to give out an MCZ of our fixes that >>> we've put together over the last two years. >>> >>> Obviously some of those we found have been pulled into Pharo >>> already, but the attached MCZ represents those that we think are >>> still relevant :) >>> >>> This is a rough list of the fixes: >>> >>> 1. Fixed flaky borwser comment text area sometime not showing. >>> >>> 2. Added getArgumentPermutation to support RefactoringEngine. >>> >>> 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner >>> to correctly align the first line of text when centered/justifed >>> etc. >>> >>> 4. Added more constant names to Character class. >>> >>> 5. Modified ConnectionQueue to not accept connections when queue >>> is full. >>> >>> 6. Changed GrafPort to answer a MultiDisplayScanner when >>> appropriate (allows subclasses of MultiNewParagraph). >>> >>> 7. NaturalLanguageTranslator startup postion move to after >>> PasteUpMorph since it will show a progress bar. >>> >>> 8. Fix to Random>>nextInt: to allow large numbers which would be >>> out of range if using Floats (as mentioned recently on dev, use of >>> Floats is dodgy anyway...) >>> >>> 9. Changed TranscriptStream>>clear to use a new buffer (was just >>> reset which could leave a massive collection). >>> >>> 10. Changed RemoteString to handle concurrent processes safely. >>> This one's particularly interesting: we were load-testing our >>> Seaside app here and getting lots of syntax errors when hitting >>> the image with around the 20 concurrent processes due to source >>> file access. After this change we were hitting it with >>> approximately 500 concurrent processes, and the failure was in the >>> Java load tester (it timed out). >>> >>> Hope just submitting a .mcz is OK! :) >>> >>> Cheers, >>> Simon and Gary >>> >>> >>> >>> ****************************************************************************************************************************************** >>> This email is from Pinesoft Limited. Its contents are confidential >>> to the intended recipient(s) at the email address(es) to which it >>> has been addressed. It may not be disclosed to or used by anyone >>> other than the addressee(s), nor may it be copied in anyway. If >>> received in error, please contact the sender, then delete it from >>> your system. Although this email and attachments are believed to >>> be free of virus, or any other defect which might affect any >>> computer or IT system into which they are received and opened, it >>> is the responsibility of the recipient to ensure that they are >>> virus free and no responsibility is accepted by Pinesoft for any >>> loss or damage arising in any way from receipt or use thereof. >>> ******************************************************************************************************************************************* >>> >>> >>> Pinesoft Limited are registered in England, Registered number: >>> 2914825. Registered office: 266-268 High Street, Waltham Cross, >>> Herts, EN8 7EA >>> <Pinesoft-Fixes-Misc-gvc.24.mcz> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > ****************************************************************************************************************************************** > This email is from Pinesoft Limited. Its contents are confidential > to the intended recipient(s) at the email address(es) to which it > has been addressed. It may not be disclosed to or used by anyone > other than the addressee(s), nor may it be copied in anyway. If > received in error, please contact the sender, then delete it from > your system. Although this email and attachments are believed to be > free of virus, or any other defect which might affect any computer > or IT system into which they are received and opened, it is the > responsibility of the recipient to ensure that they are virus free > and no responsibility is accepted by Pinesoft for any loss or damage > arising in any way from receipt or use thereof. > ******************************************************************************************************************************************* > > > Pinesoft Limited are registered in England, Registered number: > 2914825. Registered office: 266-268 High Street, Waltham Cross, > Herts, EN8 7EA > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 27, 2008

Re: [Pharo-project] About Flap

by Gary Chambers

I quite like the tools flap, when configured for auto-popout and with "solid" style... Just my 2c Gary. ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, September 24, 2008 8:46 PM Subject: Re: [Pharo-project] About Flap > 2008/9/24 Marcus Denker <denker(a)iam.unibe.ch>: >> >> On 24.09.2008, at 20:14, Bill Schwab wrote: >> >>> Lukas, >>> >>> That's fine if my hands are on the keyboard, but if I have one on the >>> mouse (common when browsing), then (in Dolphin at least), I end up >>> either right clicking on a class in an open browser, or hitting a >>> toolbar button. For the more obscure tools, the shell menus (Tools) do >>> the trick. Shortcuts are great, but we should also provide mouse-based >>> options. >>> >> >> remember: there will be a menu, with a "tools" entry. And there will >> always be the world-menu (click on the backround). >> >> the flap is not faster in the number of clicks than a pulldown menu... >> > > well, with flaps is more convenient because you can drag a tool window > and place it where you want to. > While from menu - first, it placing a window automatically, and then > often you need to arrange it again. > How about putting a window in hand, when you opening it from menu? > I find it very convenient and useful feature - it gives you chance to > arrange window with no extra clicks. > > >> Marcus >> >> -- >> Marcus Denker -- denker(a)iam.unibe.ch >> http://www.iam.unibe.ch/~denker >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 26, 2008

Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixes applicable to Pharo

by Simon Kirk

hi Stef. Hmm, strange. How are you viewing the diffs? If I browse the MCZ in a Monticello browser I see extensions to these classes: BrowserCommentTextMorph BrowserRequestor CanvasCharacterScanner Character ConnectionQueue GrafPort MultiCanvasCharacterScanner NaturalLanguageTranslator Random RemoteString TranscriptStream Is this the diffs you're talking about? If so, I think they're correct. It's possible my rough list below may have missed some changes. Cheers, Simon On 26 Sep 2008, at 20:20, StÃ©phane Ducasse wrote: > Simon > > with which machine did you create you mcz? > Because apparently I can see the diffs for other packages. > > Can somebody else check the pinesoft package I put in the pharoInbox? > > Stef > > > >> Hi all. >> >> Gary and I decided we ought to give out an MCZ of our fixes that >> we've put together over the last two years. >> >> Obviously some of those we found have been pulled into Pharo >> already, but the attached MCZ represents those that we think are >> still relevant :) >> >> This is a rough list of the fixes: >> >> 1. Fixed flaky borwser comment text area sometime not showing. >> >> 2. Added getArgumentPermutation to support RefactoringEngine. >> >> 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner >> to correctly align the first line of text when centered/justifed etc. >> >> 4. Added more constant names to Character class. >> >> 5. Modified ConnectionQueue to not accept connections when queue is >> full. >> >> 6. Changed GrafPort to answer a MultiDisplayScanner when >> appropriate (allows subclasses of MultiNewParagraph). >> >> 7. NaturalLanguageTranslator startup postion move to after >> PasteUpMorph since it will show a progress bar. >> >> 8. Fix to Random>>nextInt: to allow large numbers which would be >> out of range if using Floats (as mentioned recently on dev, use of >> Floats is dodgy anyway...) >> >> 9. Changed TranscriptStream>>clear to use a new buffer (was just >> reset which could leave a massive collection). >> >> 10. Changed RemoteString to handle concurrent processes safely. >> This one's particularly interesting: we were load-testing our >> Seaside app here and getting lots of syntax errors when hitting the >> image with around the 20 concurrent processes due to source file >> access. After this change we were hitting it with approximately 500 >> concurrent processes, and the failure was in the Java load tester >> (it timed out). >> >> Hope just submitting a .mcz is OK! :) >> >> Cheers, >> Simon and Gary >> >> >> >> ****************************************************************************************************************************************** >> This email is from Pinesoft Limited. Its contents are confidential >> to the intended recipient(s) at the email address(es) to which it >> has been addressed. It may not be disclosed to or used by anyone >> other than the addressee(s), nor may it be copied in anyway. If >> received in error, please contact the sender, then delete it from >> your system. Although this email and attachments are believed to be >> free of virus, or any other defect which might affect any computer >> or IT system into which they are received and opened, it is the >> responsibility of the recipient to ensure that they are virus free >> and no responsibility is accepted by Pinesoft for any loss or >> damage arising in any way from receipt or use thereof. >> ******************************************************************************************************************************************* >> >> >> Pinesoft Limited are registered in England, Registered number: >> 2914825. Registered office: 266-268 High Street, Waltham Cross, >> Herts, EN8 7EA >> <Pinesoft-Fixes-Misc-gvc.24.mcz> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. ******************************************************************************************************************************************* Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

Sept. 26, 2008

Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixes applicable to Pharo

by StÃ©phane Ducasse

I'm trying to understand the problem I have the hypothesis that this is linked with the class extension or the fact that the package does not exist in the image. Can you also check that you can see diff when the changes is in an class extension? Because this is strange with some packages I can see the diff and with the pinesoft-fixes-misc I cannot. Stef On Sep 26, 2008, at 9:20 PM, StÃ©phane Ducasse wrote: > Simon > > with which machine did you create you mcz? > Because apparently I can see the diffs for other packages. > > Can somebody else check the pinesoft package I put in the pharoInbox? > > Stef > > > >> Hi all. >> >> Gary and I decided we ought to give out an MCZ of our fixes that >> we've put together over the last two years. >> >> Obviously some of those we found have been pulled into Pharo >> already, but the attached MCZ represents those that we think are >> still relevant :) >> >> This is a rough list of the fixes: >> >> 1. Fixed flaky borwser comment text area sometime not showing. >> >> 2. Added getArgumentPermutation to support RefactoringEngine. >> >> 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner >> to correctly align the first line of text when centered/justifed etc. >> >> 4. Added more constant names to Character class. >> >> 5. Modified ConnectionQueue to not accept connections when queue is >> full. >> >> 6. Changed GrafPort to answer a MultiDisplayScanner when >> appropriate (allows subclasses of MultiNewParagraph). >> >> 7. NaturalLanguageTranslator startup postion move to after >> PasteUpMorph since it will show a progress bar. >> >> 8. Fix to Random>>nextInt: to allow large numbers which would be >> out of range if using Floats (as mentioned recently on dev, use of >> Floats is dodgy anyway...) >> >> 9. Changed TranscriptStream>>clear to use a new buffer (was just >> reset which could leave a massive collection). >> >> 10. Changed RemoteString to handle concurrent processes safely. >> This one's particularly interesting: we were load-testing our >> Seaside app here and getting lots of syntax errors when hitting the >> image with around the 20 concurrent processes due to source file >> access. After this change we were hitting it with approximately 500 >> concurrent processes, and the failure was in the Java load tester >> (it timed out). >> >> Hope just submitting a .mcz is OK! :) >> >> Cheers, >> Simon and Gary >> >> >> >> ****************************************************************************************************************************************** >> This email is from Pinesoft Limited. Its contents are confidential >> to the intended recipient(s) at the email address(es) to which it >> has been addressed. It may not be disclosed to or used by anyone >> other than the addressee(s), nor may it be copied in anyway. If >> received in error, please contact the sender, then delete it from >> your system. Although this email and attachments are believed to be >> free of virus, or any other defect which might affect any computer >> or IT system into which they are received and opened, it is the >> responsibility of the recipient to ensure that they are virus free >> and no responsibility is accepted by Pinesoft for any loss or >> damage arising in any way from receipt or use thereof. >> ******************************************************************************************************************************************* >> >> >> Pinesoft Limited are registered in England, Registered number: >> 2914825. Registered office: 266-268 High Street, Waltham Cross, >> Herts, EN8 7EA >> <Pinesoft-Fixes-Misc-gvc.24.mcz> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 26, 2008

Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixes applicable to Pharo

by StÃ©phane Ducasse

Simon with which machine did you create you mcz? Because apparently I can see the diffs for other packages. Can somebody else check the pinesoft package I put in the pharoInbox? Stef > Hi all. > > Gary and I decided we ought to give out an MCZ of our fixes that > we've put together over the last two years. > > Obviously some of those we found have been pulled into Pharo > already, but the attached MCZ represents those that we think are > still relevant :) > > This is a rough list of the fixes: > > 1. Fixed flaky borwser comment text area sometime not showing. > > 2. Added getArgumentPermutation to support RefactoringEngine. > > 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner > to correctly align the first line of text when centered/justifed etc. > > 4. Added more constant names to Character class. > > 5. Modified ConnectionQueue to not accept connections when queue is > full. > > 6. Changed GrafPort to answer a MultiDisplayScanner when appropriate > (allows subclasses of MultiNewParagraph). > > 7. NaturalLanguageTranslator startup postion move to after > PasteUpMorph since it will show a progress bar. > > 8. Fix to Random>>nextInt: to allow large numbers which would be out > of range if using Floats (as mentioned recently on dev, use of > Floats is dodgy anyway...) > > 9. Changed TranscriptStream>>clear to use a new buffer (was just > reset which could leave a massive collection). > > 10. Changed RemoteString to handle concurrent processes safely. This > one's particularly interesting: we were load-testing our Seaside app > here and getting lots of syntax errors when hitting the image with > around the 20 concurrent processes due to source file access. After > this change we were hitting it with approximately 500 concurrent > processes, and the failure was in the Java load tester (it timed out). > > Hope just submitting a .mcz is OK! :) > > Cheers, > Simon and Gary > > > > ****************************************************************************************************************************************** > This email is from Pinesoft Limited. Its contents are confidential > to the intended recipient(s) at the email address(es) to which it > has been addressed. It may not be disclosed to or used by anyone > other than the addressee(s), nor may it be copied in anyway. If > received in error, please contact the sender, then delete it from > your system. Although this email and attachments are believed to be > free of virus, or any other defect which might affect any computer > or IT system into which they are received and opened, it is the > responsibility of the recipient to ensure that they are virus free > and no responsibility is accepted by Pinesoft for any loss or damage > arising in any way from receipt or use thereof. > ******************************************************************************************************************************************* > > > Pinesoft Limited are registered in England, Registered number: > 2914825. Registered office: 266-268 High Street, Waltham Cross, > Herts, EN8 7EA > <Pinesoft-Fixes-Misc-gvc.24.mcz> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 26, 2008

[Pharo-project] who is YM

by StÃ©phane Ducasse

because there is a package Network YM 44 Please please avoid to use initials. Stef

Sept. 26, 2008

[Pharo-project] Bug? I cannot see the diff anymore doing merge or browse

by StÃ©phane Ducasse

Hi I'm tracking a problem I have and which is quite annoying I cannot see the diff when I do a merge or browse with MC. I'm with 10074 and I woudl like to know if you have the same behavior. Stef

Sept. 26, 2008

Re: [Pharo-project] Fwd: [Seaside-dev] preliminary Seaside 2.9 alphauniverse

by StÃ©phane Ducasse

>>> > My objection, the big ball of mud called Kernel-Extensions and the > liberal > use of overrides, which I think are evil. I like using packages > that do > their best to only use extensions and don't just go around the > system willy > nilly monkey patching everything. I don't trust packages with > overrides not > to break my system and I absolutely don't like packages that once > installed > can't be uninstalled, try removing Kernel-Extensions sometime. Thanks! Seriously. This is the kind of feedback I like. Now we know what should be done. Cleaning, reviewing, integrating... > Now, the code may work perfectly fine, and Keith's done a lot of > work, but > it's just not community friendly code. A package should have a clear > responsibility, few dependencies, not too many extensions, no > overrides if > at all possible, and must install and uninstall cleanly without > hosing my > system. 100% agree. This is why I'm saying that we want to integrate extensions or reject them. > If it doesn't meet those criteria, I don't consider it safe to even > experiment with.

Sept. 26, 2008

Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixes applicable to Pharo

by StÃ©phane Ducasse

This is GREAT! you checked with Pharo, so I will check to see and publish that. Stef On Sep 26, 2008, at 6:36 PM, Simon Kirk wrote: > Hi all. > > Gary and I decided we ought to give out an MCZ of our fixes that > we've put together over the last two years. > > Obviously some of those we found have been pulled into Pharo > already, but the attached MCZ represents those that we think are > still relevant :) > > This is a rough list of the fixes: > > 1. Fixed flaky borwser comment text area sometime not showing. > > 2. Added getArgumentPermutation to support RefactoringEngine. > > 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner > to correctly align the first line of text when centered/justifed etc. > > 4. Added more constant names to Character class. > > 5. Modified ConnectionQueue to not accept connections when queue is > full. > > 6. Changed GrafPort to answer a MultiDisplayScanner when appropriate > (allows subclasses of MultiNewParagraph). > > 7. NaturalLanguageTranslator startup postion move to after > PasteUpMorph since it will show a progress bar. > > 8. Fix to Random>>nextInt: to allow large numbers which would be out > of range if using Floats (as mentioned recently on dev, use of > Floats is dodgy anyway...) > > 9. Changed TranscriptStream>>clear to use a new buffer (was just > reset which could leave a massive collection). > > 10. Changed RemoteString to handle concurrent processes safely. This > one's particularly interesting: we were load-testing our Seaside app > here and getting lots of syntax errors when hitting the image with > around the 20 concurrent processes due to source file access. After > this change we were hitting it with approximately 500 concurrent > processes, and the failure was in the Java load tester (it timed out). > > Hope just submitting a .mcz is OK! :) > > Cheers, > Simon and Gary > > > > ****************************************************************************************************************************************** > This email is from Pinesoft Limited. Its contents are confidential > to the intended recipient(s) at the email address(es) to which it > has been addressed. It may not be disclosed to or used by anyone > other than the addressee(s), nor may it be copied in anyway. If > received in error, please contact the sender, then delete it from > your system. Although this email and attachments are believed to be > free of virus, or any other defect which might affect any computer > or IT system into which they are received and opened, it is the > responsibility of the recipient to ensure that they are virus free > and no responsibility is accepted by Pinesoft for any loss or damage > arising in any way from receipt or use thereof. > ******************************************************************************************************************************************* > > > Pinesoft Limited are registered in England, Registered number: > 2914825. Registered office: 266-268 High Street, Waltham Cross, > Herts, EN8 7EA > <Pinesoft-Fixes-Misc-gvc.24.mcz> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 26, 2008

RE: [Pharo-project] Fwd: [Seaside-dev] preliminary Seaside 2.9 alphauniverse

by Ramon Leon

> On Fri, Sep 26, 2008 at 8:38 AM, Lukas Renggli > <renggli(a)gmail.com> wrote: > > One problem I see with Sake/Packages is that these tools depend on a > > lot of other packages, that I don't necessarily want to > have loaded in > > my images: Logging, Rio, Installer, Sake, Packages ... > > > > I guess one could argue the same with XML and Universe. > > > This is the only argument against Sake/Packages I guess. Keith, could > you please give us more information on that? > - what mcz do we need to load exactly to have universes features using > Sake/Packages? > - is LPF necessary? My objection, the big ball of mud called Kernel-Extensions and the liberal use of overrides, which I think are evil. I like using packages that do their best to only use extensions and don't just go around the system willy nilly monkey patching everything. I don't trust packages with overrides not to break my system and I absolutely don't like packages that once installed can't be uninstalled, try removing Kernel-Extensions sometime. Now, the code may work perfectly fine, and Keith's done a lot of work, but it's just not community friendly code. A package should have a clear responsibility, few dependencies, not too many extensions, no overrides if at all possible, and must install and uninstall cleanly without hosing my system. If it doesn't meet those criteria, I don't consider it safe to even experiment with. Ramon Leon http://onsmalltalk.com

Sept. 26, 2008