- Pharo-users - lists.pharo.org

Re: [Pharo-users] GitFileTree Warning on Pharo 5

by Peter UhnÃ¡k

Camping with internet access is a sign of not enough wilderness. :) On Mon, Jul 27, 2015 at 10:35 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Please camp and have fun by all means. I am in no hurry. I used > loadDevelopment and there are no issues. > Happy camping :) > > On Mon, Jul 27, 2015 at 11:33 PM Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> >> Le 27 juil. 2015 10:03 PM, "Dimitris Chloupis" <kilon.alios(a)gmail.com> a >> Ã©crit : >> > >> > maybe add it to stable and update config in the pharo 5 meta repo so we >> can all get it through conf browser ? >> >> I'll do that. >> >> I'm camping at the moment, so I'm not supposed to do Pharo coding ;) >> >> Thierry >> >> > >> > On Mon, Jul 27, 2015 at 10:58 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> >> >> This has been fixed some time ago, but is still in dev branch, so >> #loadDevelopment should do the trick. >> >> >> >> Peter >> >> >> >> On Mon, Jul 27, 2015 at 9:50 PM, Dimitris Chloupis < >> kilon.alios(a)gmail.com> wrote: >> >>> >> >>> I try to install GitFileTree on Pharo and I get this warning >> >>> >> >>> This package depends on the following classes: StringHolder You must >> resolve these dependencies before you will be able to load these >> definitions: CrLfFileEditor CrLfFileEditor>>#defaultLineEndConvention >> CrLfFileEditor>>#editFileNamed: CrLfFileEditor>>#fileNamed: >> CrLfFileEditor>>#fileNamed:inDirectoryPath: >> CrLfFileEditor>>#fileNamed:withLabel: CrLfFileEditor>>#initialize >> CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName: >> CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName:lineEndConvention: >> CrLfFileEditor>>#openForFileNamed: >> CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName: >> CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName:lineEndConvention: >> CrLfFileEditor>>#windowColorSpecification CrLfFileEditor>>#bogusTruncate: >> CrLfFileEditor>>#browseChanges CrLfFileEditor>>#contents >> CrLfFileEditor>>#contents: CrLfFileEditor>>#controllerForAccept >> CrLfFileEditor>>#currentFilePathName CrLfFileEditor>>#defaultFont >> CrLfFileEditor>>#directory: CrLfFileEditor>>#exit >> CrLfFileEditor>>#fileContentsMenu:shifted: CrLfFileEditor>>#fileName: >> CrLfFileEditor>>#forceDirtyBuffer CrLfFileEditor>>#getAnotherFileName: >> CrLfFileEditor>>#getFileName: CrLfFileEditor>>#getHex >> CrLfFileEditor>>#getSelection CrLfFileEditor>>#getText >> CrLfFileEditor>>#hexFormat: CrLfFileEditor>>#labelString >> CrLfFileEditor>>#lineEndConvention: CrLfFileEditor>>#mvcWithLabel: >> CrLfFileEditor>>#openAsMorphLabel: CrLfFileEditor>>#openLabel: >> CrLfFileEditor>>#put: CrLfFileEditor>>#save CrLfFileEditor>>#saveAs >> CrLfFileEditor>>#selectedClassOrMetaClass >> CrLfFileEditor>>#selectedMessageCategoryName >> CrLfFileEditor>>#updateFilePathWith: CrLfFileEditor>>#viewStyle: >> CrLfFileEditor>>#withLabel: Select Proceed to continue, or close this >> window to cancel the operation. >> >>> >> >>> Should I be worried ? Will this mess up my git repo ? >> >> >> >> >> >

July 27, 2015

Announcments vs Events schism

by Peter UhnÃ¡k

Hi, is there a good reason why not just rename Announcement to Event since everyone is calling it that anyways? Everybody (almost irrespective of language) understands what an event, whilst Announcement is a new vocabulary. Most people when subclassing will anyways do Announcement subclass: MyEvent and so forth. Is there a benefit in naming it Announcement? Doesn't it just add more confusion? For example Bloc has Announcement subclass: #BlAbstractEvent and Announcement subclass: #BlMorphAnnouncement whilst Event is clearly favored. BlMorphAnnouncement allSubclasses size. "5" BlAbstractEvent allSubclasses size. "60" (Why does Bloc has this separation anyways?) Peter

July 27, 2015

Re: [Pharo-users] SmaCC Warning on Pharo 5

by Thierry Goubier

Hi Kilon, I haven't done the work to port the SmaCC Gui to Pharo 5. As long as you don't use the GUI, you should be fine. Thierry Le 27 juil. 2015 9:48 PM, "Dimitris Chloupis" <kilon.alios(a)gmail.com> a Ã©crit : > I am installing my project Ephestos on Pharo 5 that depends on SmaCC and > SmaCC gives me the following warning > > This package depends on the following classes: StringHolder You must > resolve these dependencies before you will be able to load these > definitions: SmaCCCodeHolder SmaCCCodeHolder>>#owner: > SmaCCCodeHolder>>#owner:ownerAcceptSelector: > SmaCCCodeHolder>>#contents:notifying: > SmaCCCodeHolder>>#contentsMenu:shifted: SmaCCCodeHolder>>#contentsMorph > SmaCCCodeHolder>>#hasUnacceptedEdits SmaCCCodeHolder>>#okToChange > SmaCCCodeHolder>>#owner SmaCCCodeHolder>>#owner: > SmaCCCodeHolder>>#owner:ownerAcceptSelector: > SmaCCCodeHolder>>#ownerAcceptSelector > SmaCCCodeHolder>>#ownerAcceptSelector: SmaCCCodeHolder>>#perform:orSendTo: > SmaCCCodeHolder>>#readContentsFromFile SmaCCCodeHolder>>#saveContentsInFile > Select Proceed to continue, or close this window to cancel the operation. > > Is this normal ? Should I be worried ? Is SmaCC ok on Pharo 5 ? > > Clicking proceed does not appear to create any side effect. >

July 27, 2015

Re: [Pharo-users] GitFileTree Warning on Pharo 5

by Dimitris Chloupis

Please camp and have fun by all means. I am in no hurry. I used loadDevelopment and there are no issues. Happy camping :) On Mon, Jul 27, 2015 at 11:33 PM Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 27 juil. 2015 10:03 PM, "Dimitris Chloupis" <kilon.alios(a)gmail.com> a > Ã©crit : > > > > maybe add it to stable and update config in the pharo 5 meta repo so we > can all get it through conf browser ? > > I'll do that. > > I'm camping at the moment, so I'm not supposed to do Pharo coding ;) > > Thierry > > > > > On Mon, Jul 27, 2015 at 10:58 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> > >> This has been fixed some time ago, but is still in dev branch, so > #loadDevelopment should do the trick. > >> > >> Peter > >> > >> On Mon, Jul 27, 2015 at 9:50 PM, Dimitris Chloupis < > kilon.alios(a)gmail.com> wrote: > >>> > >>> I try to install GitFileTree on Pharo and I get this warning > >>> > >>> This package depends on the following classes: StringHolder You must > resolve these dependencies before you will be able to load these > definitions: CrLfFileEditor CrLfFileEditor>>#defaultLineEndConvention > CrLfFileEditor>>#editFileNamed: CrLfFileEditor>>#fileNamed: > CrLfFileEditor>>#fileNamed:inDirectoryPath: > CrLfFileEditor>>#fileNamed:withLabel: CrLfFileEditor>>#initialize > CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName: > CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName:lineEndConvention: > CrLfFileEditor>>#openForFileNamed: > CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName: > CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName:lineEndConvention: > CrLfFileEditor>>#windowColorSpecification CrLfFileEditor>>#bogusTruncate: > CrLfFileEditor>>#browseChanges CrLfFileEditor>>#contents > CrLfFileEditor>>#contents: CrLfFileEditor>>#controllerForAccept > CrLfFileEditor>>#currentFilePathName CrLfFileEditor>>#defaultFont > CrLfFileEditor>>#directory: CrLfFileEditor>>#exit > CrLfFileEditor>>#fileContentsMenu:shifted: CrLfFileEditor>>#fileName: > CrLfFileEditor>>#forceDirtyBuffer CrLfFileEditor>>#getAnotherFileName: > CrLfFileEditor>>#getFileName: CrLfFileEditor>>#getHex > CrLfFileEditor>>#getSelection CrLfFileEditor>>#getText > CrLfFileEditor>>#hexFormat: CrLfFileEditor>>#labelString > CrLfFileEditor>>#lineEndConvention: CrLfFileEditor>>#mvcWithLabel: > CrLfFileEditor>>#openAsMorphLabel: CrLfFileEditor>>#openLabel: > CrLfFileEditor>>#put: CrLfFileEditor>>#save CrLfFileEditor>>#saveAs > CrLfFileEditor>>#selectedClassOrMetaClass > CrLfFileEditor>>#selectedMessageCategoryName > CrLfFileEditor>>#updateFilePathWith: CrLfFileEditor>>#viewStyle: > CrLfFileEditor>>#withLabel: Select Proceed to continue, or close this > window to cancel the operation. > >>> > >>> Should I be worried ? Will this mess up my git repo ? > >> > >> >

July 27, 2015

Re: [Pharo-users] GitFileTree Warning on Pharo 5

by Thierry Goubier

Le 27 juil. 2015 10:03 PM, "Dimitris Chloupis" <kilon.alios(a)gmail.com> a Ã©crit : > > maybe add it to stable and update config in the pharo 5 meta repo so we can all get it through conf browser ? I'll do that. I'm camping at the moment, so I'm not supposed to do Pharo coding ;) Thierry > > On Mon, Jul 27, 2015 at 10:58 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> This has been fixed some time ago, but is still in dev branch, so #loadDevelopment should do the trick. >> >> Peter >> >> On Mon, Jul 27, 2015 at 9:50 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >>> >>> I try to install GitFileTree on Pharo and I get this warning >>> >>> This package depends on the following classes: StringHolder You must resolve these dependencies before you will be able to load these definitions: CrLfFileEditor CrLfFileEditor>>#defaultLineEndConvention CrLfFileEditor>>#editFileNamed: CrLfFileEditor>>#fileNamed: CrLfFileEditor>>#fileNamed:inDirectoryPath: CrLfFileEditor>>#fileNamed:withLabel: CrLfFileEditor>>#initialize CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName: CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName:lineEndConvention: CrLfFileEditor>>#openForFileNamed: CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName: CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName:lineEndConvention: CrLfFileEditor>>#windowColorSpecification CrLfFileEditor>>#bogusTruncate: CrLfFileEditor>>#browseChanges CrLfFileEditor>>#contents CrLfFileEditor>>#contents: CrLfFileEditor>>#controllerForAccept CrLfFileEditor>>#currentFilePathName CrLfFileEditor>>#defaultFont CrLfFileEditor>>#directory: CrLfFileEditor>>#exit CrLfFileEditor>>#fileContentsMenu:shifted: CrLfFileEditor>>#fileName: CrLfFileEditor>>#forceDirtyBuffer CrLfFileEditor>>#getAnotherFileName: CrLfFileEditor>>#getFileName: CrLfFileEditor>>#getHex CrLfFileEditor>>#getSelection CrLfFileEditor>>#getText CrLfFileEditor>>#hexFormat: CrLfFileEditor>>#labelString CrLfFileEditor>>#lineEndConvention: CrLfFileEditor>>#mvcWithLabel: CrLfFileEditor>>#openAsMorphLabel: CrLfFileEditor>>#openLabel: CrLfFileEditor>>#put: CrLfFileEditor>>#save CrLfFileEditor>>#saveAs CrLfFileEditor>>#selectedClassOrMetaClass CrLfFileEditor>>#selectedMessageCategoryName CrLfFileEditor>>#updateFilePathWith: CrLfFileEditor>>#viewStyle: CrLfFileEditor>>#withLabel: Select Proceed to continue, or close this window to cancel the operation. >>> >>> Should I be worried ? Will this mess up my git repo ? >> >>

July 27, 2015

Re: [Pharo-users] Markdown -> Pillar

by HernÃ¡n Morales Durand

Thanks Damien, HernÃ¡n 2015-07-27 5:52 GMT-03:00 Damien Cassou <damien.cassou(a)inria.fr>: > > HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> writes: > > > Has anyone implemented a feature to convert a document from Markdown > format > > to Pillar? > > not yet. But Jan implemented a full-featured Markdown parser in > PetitParser so I guess the hard part has been written already. I know > others are interested in that too, e.g., Norbert. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

July 27, 2015

Re: [Pharo-users] GitFileTree Warning on Pharo 5

by Dimitris Chloupis

maybe add it to stable and update config in the pharo 5 meta repo so we can all get it through conf browser ? On Mon, Jul 27, 2015 at 10:58 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > This has been fixed some time ago, but is still in dev branch, so > #loadDevelopment should do the trick. > > Peter > > On Mon, Jul 27, 2015 at 9:50 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > >> I try to install GitFileTree on Pharo and I get this warning >> >> This package depends on the following classes: StringHolder You must >> resolve these dependencies before you will be able to load these >> definitions: CrLfFileEditor CrLfFileEditor>>#defaultLineEndConvention >> CrLfFileEditor>>#editFileNamed: CrLfFileEditor>>#fileNamed: >> CrLfFileEditor>>#fileNamed:inDirectoryPath: >> CrLfFileEditor>>#fileNamed:withLabel: CrLfFileEditor>>#initialize >> CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName: >> CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName:lineEndConvention: >> CrLfFileEditor>>#openForFileNamed: >> CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName: >> CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName:lineEndConvention: >> CrLfFileEditor>>#windowColorSpecification CrLfFileEditor>>#bogusTruncate: >> CrLfFileEditor>>#browseChanges CrLfFileEditor>>#contents >> CrLfFileEditor>>#contents: CrLfFileEditor>>#controllerForAccept >> CrLfFileEditor>>#currentFilePathName CrLfFileEditor>>#defaultFont >> CrLfFileEditor>>#directory: CrLfFileEditor>>#exit >> CrLfFileEditor>>#fileContentsMenu:shifted: CrLfFileEditor>>#fileName: >> CrLfFileEditor>>#forceDirtyBuffer CrLfFileEditor>>#getAnotherFileName: >> CrLfFileEditor>>#getFileName: CrLfFileEditor>>#getHex >> CrLfFileEditor>>#getSelection CrLfFileEditor>>#getText >> CrLfFileEditor>>#hexFormat: CrLfFileEditor>>#labelString >> CrLfFileEditor>>#lineEndConvention: CrLfFileEditor>>#mvcWithLabel: >> CrLfFileEditor>>#openAsMorphLabel: CrLfFileEditor>>#openLabel: >> CrLfFileEditor>>#put: CrLfFileEditor>>#save CrLfFileEditor>>#saveAs >> CrLfFileEditor>>#selectedClassOrMetaClass >> CrLfFileEditor>>#selectedMessageCategoryName >> CrLfFileEditor>>#updateFilePathWith: CrLfFileEditor>>#viewStyle: >> CrLfFileEditor>>#withLabel: Select Proceed to continue, or close this >> window to cancel the operation. >> >> Should I be worried ? Will this mess up my git repo ? >> > >

July 27, 2015

Re: [Pharo-users] GitFileTree Warning on Pharo 5

by Peter UhnÃ¡k

This has been fixed some time ago, but is still in dev branch, so #loadDevelopment should do the trick. Peter On Mon, Jul 27, 2015 at 9:50 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > I try to install GitFileTree on Pharo and I get this warning > > This package depends on the following classes: StringHolder You must > resolve these dependencies before you will be able to load these > definitions: CrLfFileEditor CrLfFileEditor>>#defaultLineEndConvention > CrLfFileEditor>>#editFileNamed: CrLfFileEditor>>#fileNamed: > CrLfFileEditor>>#fileNamed:inDirectoryPath: > CrLfFileEditor>>#fileNamed:withLabel: CrLfFileEditor>>#initialize > CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName: > CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName:lineEndConvention: > CrLfFileEditor>>#openForFileNamed: > CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName: > CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName:lineEndConvention: > CrLfFileEditor>>#windowColorSpecification CrLfFileEditor>>#bogusTruncate: > CrLfFileEditor>>#browseChanges CrLfFileEditor>>#contents > CrLfFileEditor>>#contents: CrLfFileEditor>>#controllerForAccept > CrLfFileEditor>>#currentFilePathName CrLfFileEditor>>#defaultFont > CrLfFileEditor>>#directory: CrLfFileEditor>>#exit > CrLfFileEditor>>#fileContentsMenu:shifted: CrLfFileEditor>>#fileName: > CrLfFileEditor>>#forceDirtyBuffer CrLfFileEditor>>#getAnotherFileName: > CrLfFileEditor>>#getFileName: CrLfFileEditor>>#getHex > CrLfFileEditor>>#getSelection CrLfFileEditor>>#getText > CrLfFileEditor>>#hexFormat: CrLfFileEditor>>#labelString > CrLfFileEditor>>#lineEndConvention: CrLfFileEditor>>#mvcWithLabel: > CrLfFileEditor>>#openAsMorphLabel: CrLfFileEditor>>#openLabel: > CrLfFileEditor>>#put: CrLfFileEditor>>#save CrLfFileEditor>>#saveAs > CrLfFileEditor>>#selectedClassOrMetaClass > CrLfFileEditor>>#selectedMessageCategoryName > CrLfFileEditor>>#updateFilePathWith: CrLfFileEditor>>#viewStyle: > CrLfFileEditor>>#withLabel: Select Proceed to continue, or close this > window to cancel the operation. > > Should I be worried ? Will this mess up my git repo ? >

July 27, 2015

GitFileTree Warning on Pharo 5

by Dimitris Chloupis

I try to install GitFileTree on Pharo and I get this warning This package depends on the following classes: StringHolder You must resolve these dependencies before you will be able to load these definitions: CrLfFileEditor CrLfFileEditor>>#defaultLineEndConvention CrLfFileEditor>>#editFileNamed: CrLfFileEditor>>#fileNamed: CrLfFileEditor>>#fileNamed:inDirectoryPath: CrLfFileEditor>>#fileNamed:withLabel: CrLfFileEditor>>#initialize CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName: CrLfFileEditor>>#on:withLabel:inDirectory:defaultFileName:lineEndConvention: CrLfFileEditor>>#openForFileNamed: CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName: CrLfFileEditor>>#openOn:withLabel:inDirectory:defaultFileName:lineEndConvention: CrLfFileEditor>>#windowColorSpecification CrLfFileEditor>>#bogusTruncate: CrLfFileEditor>>#browseChanges CrLfFileEditor>>#contents CrLfFileEditor>>#contents: CrLfFileEditor>>#controllerForAccept CrLfFileEditor>>#currentFilePathName CrLfFileEditor>>#defaultFont CrLfFileEditor>>#directory: CrLfFileEditor>>#exit CrLfFileEditor>>#fileContentsMenu:shifted: CrLfFileEditor>>#fileName: CrLfFileEditor>>#forceDirtyBuffer CrLfFileEditor>>#getAnotherFileName: CrLfFileEditor>>#getFileName: CrLfFileEditor>>#getHex CrLfFileEditor>>#getSelection CrLfFileEditor>>#getText CrLfFileEditor>>#hexFormat: CrLfFileEditor>>#labelString CrLfFileEditor>>#lineEndConvention: CrLfFileEditor>>#mvcWithLabel: CrLfFileEditor>>#openAsMorphLabel: CrLfFileEditor>>#openLabel: CrLfFileEditor>>#put: CrLfFileEditor>>#save CrLfFileEditor>>#saveAs CrLfFileEditor>>#selectedClassOrMetaClass CrLfFileEditor>>#selectedMessageCategoryName CrLfFileEditor>>#updateFilePathWith: CrLfFileEditor>>#viewStyle: CrLfFileEditor>>#withLabel: Select Proceed to continue, or close this window to cancel the operation. Should I be worried ? Will this mess up my git repo ?

July 27, 2015

SmaCC Warning on Pharo 5

by Dimitris Chloupis

I am installing my project Ephestos on Pharo 5 that depends on SmaCC and SmaCC gives me the following warning This package depends on the following classes: StringHolder You must resolve these dependencies before you will be able to load these definitions: SmaCCCodeHolder SmaCCCodeHolder>>#owner: SmaCCCodeHolder>>#owner:ownerAcceptSelector: SmaCCCodeHolder>>#contents:notifying: SmaCCCodeHolder>>#contentsMenu:shifted: SmaCCCodeHolder>>#contentsMorph SmaCCCodeHolder>>#hasUnacceptedEdits SmaCCCodeHolder>>#okToChange SmaCCCodeHolder>>#owner SmaCCCodeHolder>>#owner: SmaCCCodeHolder>>#owner:ownerAcceptSelector: SmaCCCodeHolder>>#ownerAcceptSelector SmaCCCodeHolder>>#ownerAcceptSelector: SmaCCCodeHolder>>#perform:orSendTo: SmaCCCodeHolder>>#readContentsFromFile SmaCCCodeHolder>>#saveContentsInFile Select Proceed to continue, or close this window to cancel the operation. Is this normal ? Should I be worried ? Is SmaCC ok on Pharo 5 ? Clicking proceed does not appear to create any side effect.

July 27, 2015