January 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] TxText configuration

by Igor Stasenko

On 29 January 2013 08:14, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hello > > > 2013/1/29 Camillo Bruni <camillobruni(a)gmail.com> >> >> Who's in charge of the development of TxText right now? >> It would like the maintainers on the ci-job description: >> >> https://ci.inria.fr/rmod/job/TxText/ >> >> >> thanks :) >> > Last changes is my and I continue development (slowly). But I know nothing > about ci-jobs. What I can do? > > Also Tristan Bourgois join development. And sombody (Igor) should add him to > contributors. > done -- Best regards, Igor Stasenko.

Jan. 29, 2013

Re: [Pharo-project] NativeBoostFFI out parameters passing pointers back and forth is confusing...

by Igor Stasenko

On 25 January 2013 02:13, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi: > > I don't really understand how NativeBoostFFI handles pointers. > > > I have two functions like this: > > > self call: #(int git_repository_open(git_repository * * handle, char * path)) > > and > > self call: #(int git_repository_head(git_reference * * refHandle, git_repository * repo)) > > > > They use a type mapping like this: > #('git_repository' 'NBVoid' > 'git_reference' 'NBVoid' ) > > So, nothing special going on here, just pointers to pointers, > and pointers to opaque data structures. > > Now, the call to the _open function is done with a `repoHandle := NBExternalHandle new`. > This works, and I get the result value of the c lib inside my repoHandle. > > However, if I want to use it in the _head call, I first have to convert it into a NBExternalAddress (`NBExternalAddress value: repoHandle value`). > > Took me a while to figure out that passing in the repoHandle to _head does actually do the wrong thing. > The _head function then gets the address of repoHandle instead of its value, which is wrong for my usecase. > > However, just passing in `repoHandle value` results in some strange _nil_ error. > > So, the main question is, why do I need to convert between Handle and Address? > > For the library I am trying to use, that becomes a somehow recurring pattern: > > > | repo repoPath cb branches headHandle | > repo := NBExternalHandle new. > repoPath := NBExternalAddress fromString: '/Users/smarr/tmp/filetree'. why not just pass the string? > > LG2RepositoryH uniqueInstance repository_open: repo path: repoPath. > repo := NBExternalAddress value: repo value. "<-- Why is this necessary?" > > headHandle := NBExternalHandle new. > LG2RepositoryH uniqueInstance repository_head: headHandle repo: repo. > > ^ (LG2RefsH uniqueInstance > reference_name: (NBExternalAddress value: headHandle value)) "<-- Why is this necessary?" > readString > yeah.. that double indirection is often source of confusion. but you can make a subclass of NBExternalObject , say 'GitReference' to be equal to 'git_reference *' and 'GitRepository' to 'git_repository *' like that, then in signature you need to rewrite to: self call: #(int git_repository_head(GitReference * refHandle, GitRepository repo)) this should work, because converter will push a pointer to the location where your handle value is stored (if with *) or push its value without. > > Thanks > Stefan > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > -- Best regards, Igor Stasenko.

Jan. 29, 2013

Re: [Pharo-project] nativeboost google groups

by Camillo Bruni

so then I want the issue tracker entries back on this mailing list. otherwise it is inconsistent... On 2013-01-29, at 10:51, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > well.. I more or less agree with Torsten (even if I already subscribed): component parts of Pharo should be kept together, otherwise... why not to create a group for mophic, for zinc, for filesystem, etc.? > jutst to have a nice header? do you know you have some rules that you can apply to auto-label mails? :) > > > > On Jan 29, 2013, at 9:15 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> subscribe and you're done, >> >> the thing you get for Free is a decent title in the message in your mail client. >> For me that saves a couple of second on each mail to check about what it is. >> >> >> On 2013-01-29, at 08:40, Torsten Bergmann <astares(a)gmx.de> wrote: >> >>> I dislike outsourcing it to a google group. NB is now part of the image >>> and the discussion should be here as well. >> >> valid point. but then again, we will anyway allways announce changes made by >> NativeBoost automatically via the update mails. >> >> Besides, the issue tracker is also no longer in the mailinglist, which is essentially >> the heart of development? How do you argue in favor of that? >> >>> Otherwise we end up with too many places nobody will be able >>> to follow or find... >> >> invalid point: >> well then the INRIA mailing lists are the worst place since they don't have >> a proper index either. the only thing that get's indexed is the mapped forum >> on http://forum.world.st/ >> >>> Please close the group since it adds more confusion. >> >> nah, my personal opinion outweighs, besides you're always free to not use it... > >

Jan. 29, 2013

Re: [Pharo-project] Monticello class V.S. classSide

by Esteban Lorenzano

I think classSide is there for something with traits... not sure thought :P On Jan 29, 2013, at 10:23 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > What is the difference between 'class' and 'classSide'? > > We believe this is one symptom of a major problem > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > <monticello-classSide.png>

Jan. 29, 2013

Re: [Pharo-project] nativeboost google groups

by Esteban Lorenzano

well.. I more or less agree with Torsten (even if I already subscribed): component parts of Pharo should be kept together, otherwise... why not to create a group for mophic, for zinc, for filesystem, etc.? jutst to have a nice header? do you know you have some rules that you can apply to auto-label mails? :) On Jan 29, 2013, at 9:15 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > subscribe and you're done, > > the thing you get for Free is a decent title in the message in your mail client. > For me that saves a couple of second on each mail to check about what it is. > > > On 2013-01-29, at 08:40, Torsten Bergmann <astares(a)gmx.de> wrote: > >> I dislike outsourcing it to a google group. NB is now part of the image >> and the discussion should be here as well. > > valid point. but then again, we will anyway allways announce changes made by > NativeBoost automatically via the update mails. > > Besides, the issue tracker is also no longer in the mailinglist, which is essentially > the heart of development? How do you argue in favor of that? > >> Otherwise we end up with too many places nobody will be able >> to follow or find... > > invalid point: > well then the INRIA mailing lists are the worst place since they don't have > a proper index either. the only thing that get's indexed is the mapped forum > on http://forum.world.st/ > >> Please close the group since it adds more confusion. > > nah, my personal opinion outweighs, besides you're always free to not use it...

Jan. 29, 2013

Re: [Pharo-project] [Issue Tracker] [Action Needed] Show Stoppers 2.0

by Marcus Denker

On Jan 29, 2013, at 10:25 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hello. > > Just want to notice issue http://code.google.com/p/pharo/issues/detail?id=6885 > It about hanging image when it can not load fonts. > > If it will not fixed in 2.0 release I think many non latin users will have many bad words about pharo when they can't move their images on different computers. Images with loaded specific fonts can't start on computers which not have it (or placed in different directories). > > I was wait somebody with fonts knowledge look at this issue. I'm sure it is not difficult problem. Now when nobody solve it I will try fix it by myself. There are two solutions: 1) decide which issues are needed to be fixed and fixable, fix them and release 2) Do not decide, claim that "only a perfect release is a good release", and *never* release. Marcus

Jan. 29, 2013

Re: [Pharo-project] [Issue Tracker] [Action Needed] Show Stoppers 2.0

by Denis Kudriashov

Hello. Just want to notice issue http://code.google.com/p/pharo/issues/detail?id=6885 It about hanging image when it can not load fonts. If it will not fixed in 2.0 release I think many non latin users will have many bad words about pharo when they can't move their images on different computers. Images with loaded specific fonts can't start on computers which not have it (or placed in different directories). I was wait somebody with fonts knowledge look at this issue. I'm sure it is not difficult problem. Now when nobody solve it I will try fix it by myself. 2013/1/29 Marcus Denker <marcus.denker(a)inria.fr> > Hi, > > We should stat to get serious to evaluate the remaining issues that are > tagged 2.0. > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D2.0 > > Which of the are true show stoppers? This means, is the issue of a > severity that, > just for this single issue, we can not release 2.0? > > By definition, all problems that are already in 1.4 do not qualify for > this, as we > did already release 1.4 and the world did not stop spinning. > > The same is for "nice to have" issues. "It would be nice if.." is not a > show stopper. > > Marcus >

Jan. 29, 2013

[Pharo-project] Monticello class V.S. classSide

by Damien Cassou

What is the difference between 'class' and 'classSide'? We believe this is one symptom of a major problem -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 29, 2013

Re: [Pharo-project] nativeboost google groups

by Camillo Bruni

well it crashes regularly every month or so... and they reboot it only with our intervention. to that is called running on the egde ;)... On 2013-01-29, at 00:52, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > but this is always good to know the limit of key infrastructure of pharo. > So now we will not know it, only if we register to the google group. > > Stef > >> it's mostly offtopic low-level stuff which has nothing to do with Pharo per se. >> >> hence separate mailing list, plus it's much easier to separate discussions ;). >> >> >> On 2013-01-28, at 23:55, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> why? >>> because this is cool to see that there is activity around NB >>> >>> Stef >>> >>>> I thought it might be a good idea to outsource the nativeboost discussions from the main mailinglist. >>>> So I started a new google groups: >>>> >>>> https://groups.google.com/forum/?fromgroups#!forum/nativeboost >>>> nativeboost(a)googlegroups.com >>>> >>>> cami >>> >>> >> >> > >

Jan. 29, 2013

Re: [Pharo-project] nativeboost google groups

by Camillo Bruni

subscribe and you're done, the thing you get for Free is a decent title in the message in your mail client. For me that saves a couple of second on each mail to check about what it is. On 2013-01-29, at 08:40, Torsten Bergmann <astares(a)gmx.de> wrote: > I dislike outsourcing it to a google group. NB is now part of the image > and the discussion should be here as well. valid point. but then again, we will anyway allways announce changes made by NativeBoost automatically via the update mails. Besides, the issue tracker is also no longer in the mailinglist, which is essentially the heart of development? How do you argue in favor of that? > Otherwise we end up with too many places nobody will be able > to follow or find... invalid point: well then the INRIA mailing lists are the worst place since they don't have a proper index either. the only thing that get's indexed is the mapped forum on http://forum.world.st/ > Please close the group since it adds more confusion. nah, my personal opinion outweighs, besides you're always free to not use it...

Jan. 29, 2013