February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] how does zip filesystem work?

by Max Leske

On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I am trying to get the ZipFileSystem to work, but I cannot quite manage it. > > I am doing this: > (FileSystem zip: > (FileSystem disk workingDirectory / 'sample.zip')) > open > > and I get an error. > > The error comes from the fact that the code uses readStreamDo: which does not work anymore with binary streams. I tried to use binaryReadStreamDo:, but that crashes in another place. > > I think this is a bug. Or am I doing something wrong? You shouldnât beâ¦ Iâll take a look later since that would be me who introduced the bug (probably). > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Feb. 6, 2014

Re: [Pharo-dev] OpalCompiler and Semantic analyzer

by Nicolai Hess

No problem, don't hurry, take your time :) 2014-02-06 13:51 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 05 Feb 2014, at 17:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > > 2014-02-03 Nicolai Hess <nicolaihess(a)web.de>: > >> Can someone with some background knowledget on the opal compiler, >> look at my fix for issue 12442. >> >> It seems to work, but I don't like it. >> >> There were 2 problems with OCUnusedVariableWarning, removing unused temps: >> 1. Removes the RBTemporaryNode and updates the source text but does >> not correct the sourcetext offset of the remaining nodes. >> 2. Removed temporaries are left in the methodnode/blocknode scope >> >> One additional issue, if you have removed all temporaries, the two bars >> from the empty variable declaration still there >> >> >> nicolai >> > > > Now we have 3 Opal Compiler related bugs waiting for a review: > > 12442 Nautilus brakes code when removing more than one unused local > variables > 12512 SemanticAnalyzer ignores answer from UnknownSelectorWarning > 12514 OCSemanticWarnings ignore "cancel" from a confirmation dialog > > please report back if you find any issues in the bug fixes. > > > > Yes, sorry for being a bit slow... sadly there is right now so much other > stuff to do that > I did not find yet the time to look at it. (and this is not good). > Marcus >

Feb. 6, 2014

how does zip filesystem work?

by Tudor Girba

I am trying to get the ZipFileSystem to work, but I cannot quite manage it. I am doing this: (FileSystem zip: (FileSystem disk workingDirectory / 'sample.zip')) open and I get an error. The error comes from the fact that the code uses readStreamDo: which does not work anymore with binary streams. I tried to use binaryReadStreamDo:, but that crashes in another place. I think this is a bug. Or am I doing something wrong? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Feb. 6, 2014

Re: [Pharo-dev] OpalCompiler and Semantic analyzer

by Marcus Denker

On 05 Feb 2014, at 17:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-02-03 Nicolai Hess <nicolaihess(a)web.de>: > Can someone with some background knowledget on the opal compiler, > look at my fix for issue 12442. > > It seems to work, but I don't like it. > > There were 2 problems with OCUnusedVariableWarning, removing unused temps: > 1. Removes the RBTemporaryNode and updates the source text but does > not correct the sourcetext offset of the remaining nodes. > 2. Removed temporaries are left in the methodnode/blocknode scope > > One additional issue, if you have removed all temporaries, the two bars > from the empty variable declaration still there > > > nicolai > > > Now we have 3 Opal Compiler related bugs waiting for a review: > > 12442 Nautilus brakes code when removing more than one unused local variables > 12512 SemanticAnalyzer ignores answer from UnknownSelectorWarning > 12514 OCSemanticWarnings ignore "cancel" from a confirmation dialog > > please report back if you find any issues in the bug fixes. > Yes, sorry for being a bit slowâ¦ sadly there is right now so much other stuff to do that I did not find yet the time to look at it. (and this is not good). Marcus

Feb. 6, 2014

Re: [Pharo-dev] Fwd: working on pharo 3.0?

by Guillermo Polito

The ci jobs :). I didn't want to announce them (and actually i didn't do it properly) until having them finished at some good degree. The ci jobs for dbxtalk will give the people doing dbxtalk so muuuuch air (no more manual testing on 3 platforms x 5+ different database engines per change). + binaries available and built every day On Thu, Feb 6, 2014 at 1:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > What was a bit secret? > > Doru > > > On Thu, Feb 6, 2014 at 12:25 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Well, it was a bit secret, but I was starting on my free time to setup >> some ci jobs to build automagically all the opendbx libraries + test them. >> >> https://ci.inria.fr/dbxtalk/ >> >> Now my problem is that my free time for hacking on non phd stuff -> 0 >> lately... :/ >> >> >> On Thu, Feb 6, 2014 at 12:13 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >> >>> And Sven insist on still cutting/copying/evaluating one-liners >>> in the age of a configuration browser where loading is just mouse >>> clicking ;) >>> >>> But putting jokes aside - it would IMHO be really important to >>> have DBXTalk running for Pharo 3.0. Without good database >>> support one would loose any argument for Pharo in the >>> business world... >>> >>> It would also be a real bonus if the necessary support DLL's/shared libs >>> could be easily provided or installed. >>> >>> For instance the PUnQLite (Pharo wrapper for UnQlite NoSQL) provides >>> the current binaries on Github https://github.com/mumez/PunQLite >>> >>> Or the NaCl (a binding for Crypto-Nacl library) directly downloads >>> and installs them when you install the config (see ConfigurationOfNacl in >>> config browser of Pharo 3.0). >>> >>> Easy access without much hazzle is always a plus... install, connect to >>> the DB and go! >>> >>> Thx >>> T. >>> >>> > Gesendet: Donnerstag, 06. Februar 2014 um 11:54 Uhr >>> > Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> >>> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>> > Cc: dbxtalk(a)googlegroups.com >>> > Betreff: Re: [Pharo-dev] Fwd: working on pharo 3.0? >>> > >>> > Ah, it is just because you insist on using old school two line code ;-) >>> > >>> > On 06 Feb 2014, at 11:38, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> > >>> > > Gofer new >>> > > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; >>> > > package: 'ConfigurationOfOpenDBXDriver'; >>> > > load >>> > > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge >>> > > >>> > >>> > Gofer new >>> > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; >>> > configurationOf: 'OpenDBXDriver'; >>> > loadVersion: #bleedingEdge. >>> > >>> > Just joking, >>> > >>> > Sven >>> > >>> > >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Feb. 6, 2014

Re: [Pharo-dev] Fwd: working on pharo 3.0?

by Tudor Girba

What was a bit secret? Doru On Thu, Feb 6, 2014 at 12:25 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Well, it was a bit secret, but I was starting on my free time to setup > some ci jobs to build automagically all the opendbx libraries + test them. > > https://ci.inria.fr/dbxtalk/ > > Now my problem is that my free time for hacking on non phd stuff -> 0 > lately... :/ > > > On Thu, Feb 6, 2014 at 12:13 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >> And Sven insist on still cutting/copying/evaluating one-liners >> in the age of a configuration browser where loading is just mouse >> clicking ;) >> >> But putting jokes aside - it would IMHO be really important to >> have DBXTalk running for Pharo 3.0. Without good database >> support one would loose any argument for Pharo in the >> business world... >> >> It would also be a real bonus if the necessary support DLL's/shared libs >> could be easily provided or installed. >> >> For instance the PUnQLite (Pharo wrapper for UnQlite NoSQL) provides >> the current binaries on Github https://github.com/mumez/PunQLite >> >> Or the NaCl (a binding for Crypto-Nacl library) directly downloads >> and installs them when you install the config (see ConfigurationOfNacl in >> config browser of Pharo 3.0). >> >> Easy access without much hazzle is always a plus... install, connect to >> the DB and go! >> >> Thx >> T. >> >> > Gesendet: Donnerstag, 06. Februar 2014 um 11:54 Uhr >> > Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> >> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> > Cc: dbxtalk(a)googlegroups.com >> > Betreff: Re: [Pharo-dev] Fwd: working on pharo 3.0? >> > >> > Ah, it is just because you insist on using old school two line code ;-) >> > >> > On 06 Feb 2014, at 11:38, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> > >> > > Gofer new >> > > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; >> > > package: 'ConfigurationOfOpenDBXDriver'; >> > > load >> > > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge >> > > >> > >> > Gofer new >> > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; >> > configurationOf: 'OpenDBXDriver'; >> > loadVersion: #bleedingEdge. >> > >> > Just joking, >> > >> > Sven >> > >> > >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 6, 2014

Re: [Pharo-dev] [ANN] GitFileTree with no git command line at all

by Goubier Thierry

Le 06/02/2014 12:05, Stephan Eggermont a Ã©crit : > Hmm, I think it needs a bit more detailed explanation. > - it doesnât find installed git. It assumes you installed git by loading apple command line developer tools > (instead of brew, or fink) Hum, good question: it doesn't assumes anything apart from a git command available in the default path when opening a shell. I would have expected the open source tools to be up to date on that... The last version of Mac I used was 10.3 > - after installing them,trying to install SmaCC > 'Git error: ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory > Host key verification failed. > fatal: Could not read from remote repository. You need to register to github.com and record your ssh key. I will look if a read only access exists; there is some code inside Metacello (github: urls) but I have no idea about how to use it (and I asked). Thanks for trying all this :) Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 6, 2014

Re: [Pharo-dev] Fwd: working on pharo 3.0?

by Guillermo Polito

Well, it was a bit secret, but I was starting on my free time to setup some ci jobs to build automagically all the opendbx libraries + test them. https://ci.inria.fr/dbxtalk/ Now my problem is that my free time for hacking on non phd stuff -> 0 lately... :/ On Thu, Feb 6, 2014 at 12:13 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > And Sven insist on still cutting/copying/evaluating one-liners > in the age of a configuration browser where loading is just mouse > clicking ;) > > But putting jokes aside - it would IMHO be really important to > have DBXTalk running for Pharo 3.0. Without good database > support one would loose any argument for Pharo in the > business world... > > It would also be a real bonus if the necessary support DLL's/shared libs > could be easily provided or installed. > > For instance the PUnQLite (Pharo wrapper for UnQlite NoSQL) provides > the current binaries on Github https://github.com/mumez/PunQLite > > Or the NaCl (a binding for Crypto-Nacl library) directly downloads > and installs them when you install the config (see ConfigurationOfNacl in > config browser of Pharo 3.0). > > Easy access without much hazzle is always a plus... install, connect to > the DB and go! > > Thx > T. > > > Gesendet: Donnerstag, 06. Februar 2014 um 11:54 Uhr > > Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> > > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Cc: dbxtalk(a)googlegroups.com > > Betreff: Re: [Pharo-dev] Fwd: working on pharo 3.0? > > > > Ah, it is just because you insist on using old school two line code ;-) > > > > On 06 Feb 2014, at 11:38, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > > Gofer new > > > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; > > > package: 'ConfigurationOfOpenDBXDriver'; > > > load > > > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge > > > > > > > Gofer new > > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; > > configurationOf: 'OpenDBXDriver'; > > loadVersion: #bleedingEdge. > > > > Just joking, > > > > Sven > > > > > >

Feb. 6, 2014

Re: [Pharo-dev] Fwd: working on pharo 3.0?

by Torsten Bergmann

And Sven insist on still cutting/copying/evaluating one-liners in the age of a configuration browser where loading is just mouse clicking ;) But putting jokes aside - it would IMHO be really important to have DBXTalk running for Pharo 3.0. Without good database support one would loose any argument for Pharo in the business world... It would also be a real bonus if the necessary support DLL's/shared libs could be easily provided or installed. For instance the PUnQLite (Pharo wrapper for UnQlite NoSQL) provides the current binaries on Github https://github.com/mumez/PunQLite Or the NaCl (a binding for Crypto-Nacl library) directly downloads and installs them when you install the config (see ConfigurationOfNacl in config browser of Pharo 3.0). Easy access without much hazzle is always a plus... install, connect to the DB and go! Thx T. > Gesendet: Donnerstag, 06. Februar 2014 um 11:54 Uhr > Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: dbxtalk(a)googlegroups.com > Betreff: Re: [Pharo-dev] Fwd: working on pharo 3.0? > > Ah, it is just because you insist on using old school two line code ;-) > > On 06 Feb 2014, at 11:38, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > Gofer new > > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; > > package: 'ConfigurationOfOpenDBXDriver'; > > load > > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge > > > > Gofer new > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; > configurationOf: 'OpenDBXDriver'; > loadVersion: #bleedingEdge. > > Just joking, > > Sven > >

Feb. 6, 2014

Re: [Pharo-dev] comments :)

by Nicolai Hess

How about using category "cleanup" instead of "bug"? And thank you for your work! nicolai 2014-02-06 11:16 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > Hi Ben > > if we would just like to increase the number of cases/issues > using a "case per class" would have been better. > Adding final quality improvements (like docu) is usual before releases > not only in the ST world. > > For the reasons: > A single person can only do it step by step and therefore I > used the granularity of projects/packages. This also helps reintegration > /mergin back into external managed parts. > There was no reaction onto my call for action from others. > > So instead of grumbling afterwards better use your keyboard to comment on > classes ;) > > Thx > T. > > > Gesendet: Donnerstag, 06. Februar 2014 um 10:43 Uhr > > Von: btc(a)openinworld.com > > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Betreff: Re: [Pharo-dev] comments :) > > > > Good work. Minor thing though - could they maybe grouped under one Case. > > I'd hate for someone to look at the massive amount work done for Pharo 3 > > indicated by the cases close and think "Its just lots of comment updates" > > Sure it would end up being a long running case - with a lot of slices > > (each based off the most recent image). You'd have to see how that > > panned out, and itf it got too long, just link to a new case for the > > next group. > > Or maybe there is some difficulty that I can't forsee. > > cheers -ben > > > > Torsten Bergmann wrote: > > > Still 1017 to go. Feel free to help: > > > > > > Smalltalk allClasses select: [:each | each comment > includesSubstring: 'xxxx' ] > > > > > > External Package owners should also reintegrate too so these do not > > > get lost when a new version of external packages get integrated. > > > (for instance https://pharo.fogbugz.com/f/cases/12812 for Spec) > > > > > > step by step it goes ... > > > > > > Bye > > > T. > > > > > > > > > Gesendet: Mittwoch, 05. Februar 2014 um 08:36 Uhr > > > Von: Pharo4Stef <pharo4Stef(a)free.fr> > > > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > > Betreff: [Pharo-dev] comments :) > > > > > > Thanks for all these comments! > > > > > > > > > On 05 Feb 2014, at 00:27, GitHub <noreply(a)github.com> wrote: 30742 > > > 12794 Class comments missing in UpdateStreamer package > > > > https://pharo.fogbugz.com/f/cases/12794[https://pharo.fogbugz.com/f/cases/1… > > > > > > 12802 Class comments missing for Kernel package > > > > https://pharo.fogbugz.com/f/cases/12802[https://pharo.fogbugz.com/f/cases/1… > > > > > > 12804 Class comment missing in AST packages > > > > https://pharo.fogbugz.com/f/cases/12804[https://pharo.fogbugz.com/f/cases/1… > > > > > > 12797 Class comments missing for tools package > > > > https://pharo.fogbugz.com/f/cases/12797[https://pharo.fogbugz.com/f/cases/1… > > > > > > 12796 Class comments missing for Traits package > > > > https://pharo.fogbugz.com/f/cases/12796[https://pharo.fogbugz.com/f/cases/1… > > > > > > 12798 Class comments missing in GroupManager package > > > > https://pharo.fogbugz.com/f/cases/12798[https://pharo.fogbugz.com/f/cases/1… > > > > > > 12806 Class comment missing in package FreeType + categorizing for > FreeTypeCacheTest > > > > https://pharo.fogbugz.com/f/cases/12806[https://pharo.fogbugz.com/f/cases/1… > > > > > > 12800 EyeContextInspector should be renamed to > EyeMethodContextInspector > > > > https://pharo.fogbugz.com/f/cases/12800[https://pharo.fogbugz.com/f/cases/1… > > > > > > > > > > > > > > > > >

Feb. 6, 2014