July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 2635 - methods recategorization

by Pavel Krivanek

On Wed, Jul 7, 2010 at 10:44 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > On Tue, Jul 6, 2010 at 11:13 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: >> On Tue, Jul 6, 2010 at 11:05 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: >>>>> 2) e.g you move somethings to *Tools and some things to *Tools-Explorer >>>>> is that not going to create the same problem that happened to System, >>>>> with both parent and child packages defined in the same image? >>>> >>>> There's only one MC package named Tools and this package is not >>>> splitted. But we may make future split of this package easier if we >>>> will use a category name Tools-Base (or more fitting one) instead of >>>> Tools. >>>> >>> >>> ok fair enough. but if i look in #12038 there appear a few cases: >>> Graphics-Stef.256 >>> Graphics-* >>> >>> Multilingual-Markus.2 >>> Multilingual-* >> >> At least the Multilingual package is automatically registered because >> of one method in the Character class and the fix is already mentioned >> in this thread. However I have no idea why MC registers automatically >> the Graphics package > > maybe the empty *Graphics category in the String. > > -- Pavel > I suggest to remove all empty method categories in the whole system. -- Pavel > >> >> Cheers, >> -- Pavel >> >>> >>> this needs fixing before applying more recategorisation? >>> >>> >>> thanks, >>> Mike >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >

July 7, 2010

Re: [Pharo-project] Issue 2635 - methods recategorization

by Pavel Krivanek

code: Behavior organization classify: #inspectAllInstances under: '*Tools-Inspector'. Behavior organization classify: #inspectSubInstances under: '*Tools-Inspector'. String organization classify: #displayProgressAt:from:to:during: under: '*UIManager-Support'. String organization classify: #base64Encoded under: '*MimeConverter'. String organization classify: #asDisplayText under: '*Graphics-Support'. DataStream class organization classify: #exampleWithPictures under: '*Graphics-Display Objects'. Text organization classify: #embeddedMorphs under: '*Morphic'. Text organization classify: #embeddedMorphsFrom:to: under: '*Morphic'. Text organization classify: #asDisplayText under: '*Graphics-Support'. Text organization classify: #asParagraph under: '*ST80'. Text organization classify: #asUrl under: '*Network-Url'. Rectangle class organization classify: #fromUser under: '*Graphics-Display Objects'. Rectangle class organization classify: #fromUser: under: '*Graphics-Display Objects'. Rectangle class organization classify: #originFromUser: under: '*Graphics-Display Objects'. Rectangle class organization classify: #originFromUser:grid: under: '*Graphics-Display Objects'. ArrayedCollection organization classify: #writeOnGZIPByteStream: under: '*Compression'. description: Behavior organization classify: #inspectAllInstances under: '*Tools-Inspector'. Behavior organization classify: #inspectSubInstances under: '*Tools-Inspector'. - inspector support String organization classify: #displayProgressAt:from:to:during: under: '*UIManager-Support'. - it will not remove it from the PharoKernel String organization classify: #base64Encoded under: '*MimeConverter'. - Base64MimeConverter moved to MimeConverter package (part of the PharoKernel) String organization classify: #asDisplayText under: '*Graphics-Support'. - DisplayText support DataStream class organization classify: #exampleWithPictures under: '*Graphics-Display Objects'. - an example with a Form from display Text organization classify: #embeddedMorphs under: '*Morphic'. Text organization classify: #embeddedMorphsFrom:to: under: '*Morphic'. - TextMorph support Text organization classify: #asDisplayText under: '*Graphics-Support'. - DisplayText support Text organization classify: #asParagraph under: '*ST80'. - Paragraph support Text organization classify: #asUrl under: '*Network-Url'. - Network Url support Rectangle class organization classify: #fromUser under: '*Graphics-Display Objects'. Rectangle class organization classify: #fromUser: under: '*Graphics-Display Objects'. Rectangle class organization classify: #originFromUser: under: '*Graphics-Display Objects'. Rectangle class organization classify: #originFromUser:grid: under: '*Graphics-Display Objects'. - still part of the PharoKernel, works with Display ArrayedCollection organization classify: #writeOnGZIPByteStream: under: '*Compression'. - compression support

July 7, 2010

Re: [Pharo-project] Updating VM links for Pharo 1.1

by StÃ©phane Ducasse

We should move to Mac 5.0 for 1.2 Stef On Jul 7, 2010, at 10:39 AM, Mariano Martinez Peck wrote: > Hi. Henry made me remember that we need to update the VMs links for Pharo 1.1. We are in RC4 and very very near of the stable release. Thus, I suggest to fix this problem. > > You can see in http://code.google.com/p/pharo/issues/detail?id=2646 > > Mac: > 4.2.5 > Windows: > 4.0.2 > Linux: > 4.0.3.2202 > > What I am not sure if we should put these links in a particular section of Pharo 1.1 or just update the current VMs links. The problem of doing the last one is that these VMs will be downloaded for both images: 1.0 and 1.1. Are there problems with it ? The only thing I can image is if the vm has FreeType compiled. > > Cheers > > Mariano _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 7, 2010

Re: [Pharo-project] I updated the how to contribute web page

by StÃ©phane Ducasse

laurent I did a pass on the wiki and I suggest that we removed it from the wiki and put it on the book and ideally in the help :) Stef On Jul 6, 2010, at 9:48 AM, laurent laffont wrote: > Hi, > > I've seen http://book.pharo-project.org/book/Contribute > > Should we Cut / Paste from google project's wiki ? (So we have only one source of documentation, that can be later integrated to HelpSystem). > > Cheers, > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > > On Tue, Jul 6, 2010 at 12:21 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > thanks hernan. > I will not have the time to edit the changes but this is important that we keep this information upto date and that > people can understand it. > > Stef > > On Jul 5, 2010, at 4:34 PM, HernÃ¡n Morales Durand wrote: > > > Ok, > > > > ================ > > Here: "First and foremost, you must be aware that the Pharo project > > only accepts code published under the MIT license. By publishing your > > code in the SqueakSource Pharo or PharoInbox repositories, you are > > agreeing to this condition. With that out of the way, here are the > > steps to submit your contributions. " > > > > Please provide a link which explain the implications of code published > > under the MIT license. Or better, a little comparison table between > > different licensing schemes. > > > > ================ > > Here: "If your change is directly related to a Mantis report, add the > > label "Type-Mantis" and add the Mantis ticket number in front of the > > subject. Else choose another appropriate label " > > > > Please clarify or link to. Manits is the bugs.squeak.org right? It > > should be named by what it is, and not by the tool which is used for > > bug tracking (if they change their tool 10 times, you must update the > > page 10 times) > > > > ================ > > Here: "Announce your contribution by sending a mail to the mailing > > list and herewith ask to have somebody review your change. This person > > should change the state of the issue to "Verified". " > > > > Provide a link to the mailing list. Note "herewith" is most used and > > understood as a legal term. > > > > ================ > > Here: "For complex changes use a slice since there is a much better > > merging support. " > > > > What is a complex change? (please include this information in the page too) > > > > ================ > > "Prepare a changeset with your changes. File it out. Important: Put > > your Full name instead of your initials, it will help up to contact > > you as it is often necessary. Do not use space and only alphabetical > > characters. " > > > > 1) This is killing more than 50% of the habitants of the world :) What > > happens with contributors without latin alphabet? how they setup their > > system? (that should be included) > > > > 2) What is the problem with using space? If it is a limitation imposed > > by a tool then the tool should be responsible of trimming all blanks, > > not the users. > > > > 3) How do you distinguish between two John Smith? And how do you > > contact contributors? (I've never wrote my e-mail or gmail user name > > in a Pharo image). > > > > 4) Some brief explanation on how to create a changeset would be nice. > > > > ================ > > Finally, this information should be in all images. Better, provide a > > wizard to guide this process, it sounds like a nice excercise to do a > > standard window flow with Morphic. > > > > Cheers, > > > > HernÃ¡n > > > > 2010/7/5 stephane ducasse <stephane.ducasse(a)free.fr>: > >> please comment :) > >> http://code.google.com/p/pharo/wiki/HowToContribute > >> > >> Stef > >> > >> _______________________________________________ > >> 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 > > > _______________________________________________ > 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

July 7, 2010

Re: [Pharo-project] Markup Builder in Smalltalk

by StÃ©phane Ducasse

looks more readable :) On Jul 7, 2010, at 7:49 AM, Sudhakar Krishnamachari wrote: > Accepted and committed as alpha: 1.13 in http://squeaksource.com/PharoGoodies/ > > modified api is: > newBldr := XMLBuilder new. > newBldr xmlPreprocessor; attributes: #(âa=â6â³â âb=â7â³â); > > test: âwelcome to buildersâ > > with: [ newBldr attributes: #('a="1"' 'b="2"'); trial: ''; > attributes: #('a="3"' 'b="4"'); trial: 'testing..' ; > > trial ]. > > to get: > > '<?xml version="1.0" ?><test a="6" b="7" >welcome to builders<trial a="1" b="2" ></trial><trial a="3" b="4" >testing..</trial><trial></trial></test>' > > > hope this aligns.. lots more stil to be cleaned for plugins, will do so by the next commit.. > > -Skrish > ***** > There is an interest! Please submit/publish it... > > Now What is the exact API I found cNode: a bit a bad name. What does it mesn childrenNode: > > > > newBldr := XMLBuilder new xmlPreprocessor. > newBldr mbAttr: #(âa=â6â³â âb=â7â³â); test: âwelcome to buildersâ > > why new and xmlPreprocessor > > > mbAttr: sucks also! > > Could you shine a bit the API to be reader friendly? > > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 7, 2010

Re: [Pharo-project] Mysql Port of Josh Mcdonald Driver

by StÃ©phane Ducasse

this is not in squeaksource? Stef On Jul 7, 2010, at 6:49 AM, Sudhakar Krishnamachari wrote: > Hi, > > Can anyone forward the latest version of Alan Reider's fixes of the Mysql driver. I cant access the squeak map I get link of.. > > -Skrish > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 7, 2010

Re: [Pharo-project] Issue 2635 - methods recategorization

by Pavel Krivanek

On Tue, Jul 6, 2010 at 11:13 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > On Tue, Jul 6, 2010 at 11:05 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: >>>> 2) e.g you move somethings to *Tools and some things to *Tools-Explorer >>>> is that not going to create the same problem that happened to System, >>>> with both parent and child packages defined in the same image? >>> >>> There's only one MC package named Tools and this package is not >>> splitted. But we may make future split of this package easier if we >>> will use a category name Tools-Base (or more fitting one) instead of >>> Tools. >>> >> >> ok fair enough. but if i look in #12038 there appear a few cases: >> Graphics-Stef.256 >> Graphics-* >> >> Multilingual-Markus.2 >> Multilingual-* > > At least the Multilingual package is automatically registered because > of one method in the Character class and the fix is already mentioned > in this thread. However I have no idea why MC registers automatically > the Graphics package maybe the empty *Graphics category in the String. -- Pavel > > Cheers, > -- Pavel > >> >> this needs fixing before applying more recategorisation? >> >> >> thanks, >> Mike >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

July 7, 2010

[Pharo-project] Updating VM links for Pharo 1.1

by Mariano Martinez Peck

Hi. Henry made me remember that we need to update the VMs links for Pharo 1.1. We are in RC4 and very very near of the stable release. Thus, I suggest to fix this problem. You can see in http://code.google.com/p/pharo/issues/detail?id=2646 Mac: 4.2.5 Windows: 4.0.2 Linux: 4.0.3.2202 What I am not sure if we should put these links in a particular section of Pharo 1.1 or just update the current VMs links. The problem of doing the last one is that these VMs will be downloaded for both images: 1.0 and 1.1. Are there problems with it ? The only thing I can image is if the vm has FreeType compiled. Cheers Mariano

July 7, 2010

Re: [Pharo-project] Issue 2635 - methods recategorization

by Pavel Krivanek

code: SystemDictionary organization moveCategory: 'ui' to: '*Tools-Inspector'. Quadrangle organization moveCategory: 'displaying-display' to: '*Graphics-Display Objects'. Quadrangle organization moveCategory: 'displaying-generic' to: '*Graphics-Display Objects'. DefaultExternalDropHandler organization moveCategory: 'event handling' to: '*Morphic'. Rectangle organization moveCategory: '*morphic-truncation and roundoff' to: 'truncation and roundoff'. description: SystemDictionary organization moveCategory: 'ui' to: '*Tools-Inspector'. - single method inspectGlobals, not used Quadrangle organization moveCategory: 'displaying-display' to: '*Graphics-Display Objects'. Quadrangle organization moveCategory: 'displaying-generic' to: '*Graphics-Display Objects'. - graphics dependent, not used DefaultExternalDropHandler organization moveCategory: 'event handling' to: '*Morphic'. - single morphic support method Rectangle organization moveCategory: '*morphic-truncation and roundoff' to: 'truncation and roundoff'. - morphic independent useful methods

July 7, 2010

Re: [Pharo-project] Issue 2635 - methods recategorization

by Pavel Krivanek

code: StandardFileStream organization classify: #directoryUrl under: '*Network-RemoteDirectory'. Object organization classify: #customizeExplorerContents under: '*Tools-Explorer'. Object organization classify: #asDraggableMorph under: '*Morphic'. Object organization classify: #printDirectlyToDisplay under: '*Graphics-Display Objects'. Object organization classify: #doExpiredInspectCount under: '*Tools-Inspector'. Object organization classify: #inspectOnCount: under: '*Tools-Inspector'. Object organization classify: #inspectOnce under: '*Tools-Inspector'. Object organization classify: #inspectUntilCount: under: '*Tools-Inspector'.. Object organization classify: #fullDrawPostscriptOn: under: '*Morphic'. Object organization classify: #currentEvent under: '*Morphic'. Object organization classify: #currentHand under: '*Morphic'. Object organization classify: #currentWorld under: '*Morphic'. Object organization classify: #saveOnFile under: '*Morphic'. Object organization classify: #showDiffs under: '*Tools-Base'. Object organization classify: #commandHistory under: '*Morphic'. Object organization classify: #purgeAllCommands under: '*Morphic'. Object organization classify: #rememberCommand: under: '*Morphic'. Object organization classify: #updateListsAndCodeIn: under: '*Tools-Base'. Object organization classify: #asExplorerString under: '*Tools-Explorer'. Object organization classify: #defaultBackgroundColor under: '*Tools-Base'. Object organization classify: #defaultLabelForInspector under: '*Tools-Inspector'. Object organization classify: #explore under: '*Tools-Explorer'. Object organization classify: #hasContentsInExplorer under: '*Tools-Explorer'. Object organization classify: #inspectWithLabel: under: '*Tools-Inspector'. Object class organization classify: #services under: '*Tools'. description: StandardFileStream organization classify: #directoryUrl under: '*Network-RemoteDirectory'. - a method dependent on network package. Called only from RemoteDirectory class Object organization classify: #customizeExplorerContents under: '*Tools-Explorer'. - support for the explorer Object organization classify: #asDraggableMorph under: '*Morphic'. - morphic specific method called only from morphic Object organization classify: #printDirectlyToDisplay under: '*Graphics-Display Objects'. - show text representation of an object on the display, not used. Object organization classify: #doExpiredInspectCount under: '*Tools-Inspector'. Object organization classify: #inspectOnCount: under: '*Tools-Inspector'. Object organization classify: #inspectOnce under: '*Tools-Inspector'. Object organization classify: #inspectUntilCount: under: '*Tools-Inspector'. - inspector support Object organization classify: #fullDrawPostscriptOn: under: '*Morphic'. - PostScript support, not used Object organization classify: #currentEvent under: '*Morphic'. Object organization classify: #currentHand under: '*Morphic'. Object organization classify: #currentWorld under: '*Morphic'. - morphic support Object organization classify: #saveOnFile under: '*Morphic'. - morphic support Object organization classify: #showDiffs under: '*Tools-Base'. - CodeHolder support Object organization classify: #commandHistory under: '*Morphic'. Object organization classify: #purgeAllCommands under: '*Morphic'. Object organization classify: #rememberCommand: under: '*Morphic'. - CommandHistory support Object organization classify: #updateListsAndCodeIn: under: '*Tools-Base'. - CodeHolder support Object organization classify: #asExplorerString under: '*Tools-Explorer'. - explorer support Object organization classify: #defaultBackgroundColor under: '*Tools-Base'. - tools support Object organization classify: #defaultLabelForInspector under: '*Tools-Inspector'. - inspector support Object organization classify: #explore under: '*Tools-Explorer'. Object organization classify: #hasContentsInExplorer under: '*Tools-Explorer'. - explorer support Object organization classify: #inspectWithLabel: under: '*Tools-Inspector'. - inspector support Object class organization classify: #services under: '*Tools-FileList''. - file list associations StandardFileStream class >> #privateCheckForBrowserPrimitives should be in the same package as the rest of browser plugin supporting methods (see previous comment) We should open an issue for Object >> #notifyWithLabel: senders. It should be more UI independent

July 7, 2010