March 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Fail on condense when image name is drgeo.image

by Alistair Grant

Hi Hilaire, On Tue, 5 Mar 2019 at 21:16, Hilaire <hilaire(a)drgeo.eu> wrote: > > Alistair, > > I checked, the error shows under this specific situation I described in > my previous email. I figured out the environment that caused the primtiveFailure and can see how my modified code avoids the issue. > Yes, your code fixes this condition, the condense does not hit this > error anymore. Great. I've refactored this quite a bit to make it more efficient and related methods more consistent. I'll be opening an issue and submitting a PR for it. Cheers, Alistair

March 5, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Hilaire

Cool. Le 05/03/2019 Ã 18:04, peter yoo a Ã©critÂ : > ok. today me tested again. maybe my XIM env is bad before. is ok now. > thanks to all. > all fcitx package remove and re-install. and ok... > > ê°ì¬í©ëë¤. for pharo users. :D -- Dr. Geo http://drgeo.eu

March 5, 2019

Re: [Pharo-users] Fail on condense when image name is drgeo.image

by Hilaire

Alistair, I checked, the error shows under this specific situation I described in my previous email. Yes, your code fixes this condition, the condense does not hit this error anymore. Thanks Hilaire Le 05/03/2019 Ã 17:59, Alistair Grant a Ã©critÂ : > I've attached a change-set that fixes #nextVersion so it returns the > correct values for file names with dots in them, e.g. "file.name.ext". > Could you check if it behaves as expected? -- Dr. Geo http://drgeo.eu

March 5, 2019

Re: [Pharo-users] Google Protobuf and usage of Slots

by HenrikNergaard5

Hi Holger, > My plan of action is to start with a protobuf compiler/model and then look > into binding the gRPC C implementation to Pharo. I have an almost complete parser and compiler (class generation) implementation of protobuf in Pharo around somewhere... I cant quite remember the state of it, but I think everything is implemented parsing wise expect the gRPC part. Instead of using slots the compiler generates accessor methods for each variable, initialization, custom encoding and decoding based on its message definition. i can probably dig it up and make it publicly available if it is of interest. Best regards, Henrik -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 5, 2019

Re: [Pharo-users] [Pharo-fuel] Serializing classes with Fuel

by Max Leske

On 5 Mar 2019, at 19:22, Mariano Martinez Peck wrote: > On Tue, Mar 5, 2019 at 1:42 PM Konrad Hinsen > <konrad.hinsen(a)fastmail.net> > wrote: > >> Hi everyone, >> >> does anyone here have some experience with Fuel? >> >> Its Web site says "It can serialize/materialize not only plain >> objects >> but also classes, traits, methods, closures, contexts, packages, >> etc.". So I should be able to serialize a class somehow, right? >> >> But classes are by default treated as global objects, even if they >> aren't. The class I want to serialize is created by >> newAnonymousSubclass. And yet, Fuel only stores its name in the >> output >> file. >> >> The documentation describes considerGlobal: which does the opposite >> of >> what I want. So my question is: how can I tell Fuel *not* to consider >> a >> class as global? >> >> Konrad. >> >> > Yes, that's the "default" behavior. To fully serialize classes you > need > FuelMetalevel packages. This brings a new visitors and mappers to > allow you > to fully serialize methods, classes, contexts, etc. > I am sorry but I couldn't remember where the docs about that were. You > may > want to at least take a look to the packages and their tests. I'm afraid we don't really have documentation for meta level. The tests are the best place to look for guidance. But if you have concrete questions, best send them to the fule list. Max > > Best, > > > -- > Mariano > https://twitter.com/MartinezPeck > http://marianopeck.wordpress.com > _______________________________________________ > Pharo-fuel mailing list > Pharo-fuel(a)lists.gforge.inria.fr > https://lists.gforge.inria.fr/mailman/listinfo/pharo-fuel

March 5, 2019

Re: [Pharo-users] Serializing classes with Fuel

by Mariano Martinez Peck

On Tue, Mar 5, 2019 at 1:42 PM Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > Hi everyone, > > does anyone here have some experience with Fuel? > > Its Web site says "It can serialize/materialize not only plain objects > but also classes, traits, methods, closures, contexts, packages, > etc.". So I should be able to serialize a class somehow, right? > > But classes are by default treated as global objects, even if they > aren't. The class I want to serialize is created by > newAnonymousSubclass. And yet, Fuel only stores its name in the output > file. > > The documentation describes considerGlobal: which does the opposite of > what I want. So my question is: how can I tell Fuel *not* to consider a > class as global? > > Konrad. > > Yes, that's the "default" behavior. To fully serialize classes you need FuelMetalevel packages. This brings a new visitors and mappers to allow you to fully serialize methods, classes, contexts, etc. I am sorry but I couldn't remember where the docs about that were. You may want to at least take a look to the packages and their tests. Best, -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

March 5, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by peter yoo

ok. today me tested again. maybe my XIM env is bad before. is ok now. thanks to all. all fcitx package remove and re-install. and ok... ê°ì¬í©ëë¤. for pharo users. :D

March 5, 2019

Re: [Pharo-users] Fail on condense when image name is drgeo.image

by Alistair Grant

Hi Hilaire, On Tue, 5 Mar 2019 at 15:09, HilaireFernandes <hilaire(a)drgeo.eu> wrote: > > The problem seems to happen when there is the following conditions, in the > folder containing the image: > > - there is a drgeo file, in my situation it is a link to the DrGeo > repository > - the image name is drgeo.image, ... > - PharoCondense is executed, then FileRefrence>>nextVersion seems confused > by the drgeo file. > > I could recheck, but it will be evening late. I had a bit of trouble reading the stack traces, but it looked like the issue is with FileReference>>nextVersion. If that is the case: #nextVersion is self contained, so the easiest thing will be to trigger the problem, go in to the debugger and copy the pathString of the FileReference that causes the issue. I've attached a change-set that fixes #nextVersion so it returns the correct values for file names with dots in them, e.g. "file.name.ext". Could you check if it behaves as expected? Cheers, Alistair

March 5, 2019

Serializing classes with Fuel

by Konrad Hinsen

Hi everyone, does anyone here have some experience with Fuel? Its Web site says "It can serialize/materialize not only plain objects but also classes, traits, methods, closures, contexts, packages, etc.". So I should be able to serialize a class somehow, right? But classes are by default treated as global objects, even if they aren't. The class I want to serialize is created by newAnonymousSubclass. And yet, Fuel only stores its name in the output file. The documentation describes considerGlobal: which does the opposite of what I want. So my question is: how can I tell Fuel *not* to consider a class as global? Konrad.

March 5, 2019

Re: [Pharo-users] Fail on condense when image name is drgeo.image

by HilaireFernandes

The problem seems to happen when there is the following conditions, in the folder containing the image: - there is a drgeo file, in my situation it is a link to the DrGeo repository - the image name is drgeo.image, ... - PharoCondense is executed, then FileRefrence>>nextVersion seems confused by the drgeo file. I could recheck, but it will be evening late. ----- http://drgeo.eu -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 5, 2019