[Pharo-dev] NativeBoost and memory management

Good Morning, I used NB to access openlog, closelog and syslog of libc and I am not sure if I got it right but didn’t really get further by browsing testcases/reading the examples. openlog(3) takes an “char *ident” as first parameter and the caller needs to make sure that the string passed remai

[Pharo-dev] [pharo-project/pharo-core] 3ba71f: 50037

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 3ba71f9830807f1a1e1167a05dcbcae3245b50c1 https://github.com/pharo-project/pharo-core/commit/3ba71f9830807f1a1e1167a05dcbcae3245b50c1 Author: Jenkins Build Server Date: 2015-05-07 (Thu, 07 May 2015

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50037 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] RewriteTool

* Sean P. DeNigris [06.05.2015. @12:23:09 -0700]: > There are two repos: > http://smalltalkhub.com/#!/~PharoExtras/RewriteTool , which seems to have > been forked some time ago > and > http://smalltalkhub.com/#!/~MarkRizun/RewriteTool/ , which is now about 70 > commits ahead of the first! > > Wh

Re: [Pharo-dev] Package comments

> On 6 maj, 2015, at 21:27 , Sergio Fedi [via Smalltalk] > wrote: > > Does this mean that we should focus on adding the comments on this > ManifestXXX class? > (instead of other implementations)​ Yes, that seems like the right approach to me. I believe we could add some methods to “TheManifes

Re: [Pharo-dev] Package comments

> On 6 maj, 2015, at 21:23 , stepharo [via Smalltalk] > wrote: > > our idea is that each package should have meta-data: > - default code formatting > - false positive for rules > - and of course package comment. > > So for now the simplest thing we did was to add a class cal

[Pharo-dev] [Review]: Issue 15503 Add RPackage>>#mcWorkingCopy for MCSliceInfo>>#makeSlice

It's really quick - 3 tiny methods changed and two tests added. The monkey passed it and it's holding up two more fixes I want to do... Thanks :) - Cheers, Sean -- View this message in context: http://forum.world.st/Review-Issue-15503-Add-RPackage-mcWorkingCopy-for-MCSliceInfo-makeSlice-tp4

Re: [Pharo-dev] Roadmaps

stepharo wrote > There are notes for me. But I've been adding a few :) They are handy places to stash common understanding about the system (e.g. from mailing list posts or exploring the image) which are not quite ready to be proper documentation. - Cheers, Sean -- View this message in con

Re: [Pharo-dev] Where to start contributing

​Thanks for the advice. Seems a really safe and newbie-friendly task to: 1 - Review other people's fixes and comment on them 2 - Try to reproduce bugs, post them and maybe make a test case for it

Re: [Pharo-dev] Roadmaps

Aha, ok. I understand them more now. Thanks for the explanation. ​

Re: [Pharo-dev] Roadmaps

I suppose we can incorporate this documentation of the process in the comments of a bug fix (Editing the case) On Wed, May 6, 2015 at 6:57 PM, Sergio Fedi wrote: > Aha, ok. I understand them more now. > > Thanks for the explanation. > ​ >

Re: [Pharo-dev] external package handling ... a concrete case

Le 6/5/15 22:37, Esteban Lorenzano a écrit : but that happens because GTools guys made a mistake: spotterActDefault ^ Smalltalk tools browser openOnPackage: self that’s the correct implementation of that method. Ok but I do not care. This is just an example of the problem. I will **

Re: [Pharo-dev] Roadmaps

Interesting. So, these roadmaps. I read some of them but I didn't get a clear picture of what are they, so here I am asking: What are roadmaps? There are notes for me. Usually I spent time reading code to get an understanding about a part so that at least I remember. And I keep so log abo

Re: [Pharo-dev] Where to start contributing

Hi sergio start small. Here is what I did when I started to want to participate to squeak. Read the description of bugs or enhancement and check if what the people are doing is making sense. LIke that you will start to get a feel of some parts of the system. Read the bugs report and try to rep

Re: [Pharo-dev] [Pharo-users] SDL plugin ?

I can add them to the vm compilation. Adding it to the TODO… Esteban ps: again, pharo-dev :) > On 06 May 2015, at 22:45, Matthieu Lacaton wrote: > > Thanks for your answers, I understand now. > But even if the plugin is not needed it is handy to have because it allows > you to use "OSSDL2Dr

Re: [Pharo-dev] PharoForTheEnterprise: Where are the "MigratedToOtherPlaces" pages?

in entreprisePharo on github Stef Le 5/5/15 11:31, Esteban Lorenzano a écrit : I’m looking for the Voyage chapter… Esteban

Re: [Pharo-dev] external package handling ... a concrete case

but that happens because GTools guys made a mistake: spotterActDefault ^ Smalltalk tools browser openOnPackage: self that’s the correct implementation of that method. Esteban > On 06 May 2015, at 22:14, stepharo wrote: > > Hi guys > > I'm cleaning nautilus model and Spotter is exte

Re: [Pharo-dev] [Pharo-users] SDL plugin ?

actually, the SDL plugin is not being included because until now it was not necessary. There is a difference between the SDL2 dependent functions and the plugin. The plugin provides just two functions: /** * Called by the VM heartbeat if installed, to check for the presence of events. */ sta

[Pharo-dev] nautilusGlobalPackageFixMenu

Hi any idea about this? I want to remove it. packageFixPragma ^ 'nautilusGlobalPackageFixMenu' Stef

[Pharo-dev] external package handling ... a concrete case

Hi guys I'm cleaning nautilus model and Spotter is extended. Now I will not publish the fix in Spotter, I will not update a configuration of a tool I do not know. So what should I do, stop working? No this is not possible. So I will push this changes in the inbox and integrate it and GT people

Re: [Pharo-dev] last time I had insomnia...

> On 06 May 2015, at 21:48, Yuriy Tymchuk wrote: > > But isn’t there another repo with icon vector sources? Because the problem > that I’ve encountered is that small info icon looks like exclamation mark, if > rotated upside down it should be ok. no, there is no repo with vector icons, I neve

Re: [Pharo-dev] last time I had insomnia...

But isn’t there another repo with icon vector sources? Because the problem that I’ve encountered is that small info icon looks like exclamation mark, if rotated upside down it should be ok. Uko > On 06 May 2015, at 21:31, Esteban Lorenzano wrote: > > I added you as contributor :) > >> On 06

Re: [Pharo-dev] RewriteTool

Sean P. DeNigris wrote > http://smalltalkhub.com/#!/~MarkRizun/RewriteTool/ , which is now about 70 > commits ahead of the first! Alarmingly, Mark's repo seems to only be intermittently available. Many times sthub returns 404... - Cheers, Sean -- View this message in context: http://forum.

Re: [Pharo-dev] Package comments

Does this mean that we should focus on adding the comments on this ManifestXXX class? (instead of other implementations)​

[Pharo-dev] RewriteTool

There are two repos: http://smalltalkhub.com/#!/~PharoExtras/RewriteTool , which seems to have been forked some time ago and http://smalltalkhub.com/#!/~MarkRizun/RewriteTool/ , which is now about 70 commits ahead of the first! What should be done? - Cheers, Sean -- View this message in con

Re: [Pharo-dev] Package comments

Kasper our idea is that each package should have meta-data: - default code formatting - false positive for rules - and of course package comment. So for now the simplest thing we did was to add a class called ManifestXXX for packageXXX. This way it is versionned with the classes an

Re: [Pharo-dev] last time I had insomnia...

I added you as contributor :) > On 06 May 2015, at 19:03, Yuriy Tymchuk wrote: > > One question, how can I contribute? > > Uko > > >> On 28 Apr 2015, at 17:28, Nicolai Hess > > wrote: >> >> >> >> 2015-04-28 15:32 GMT+02:00 Yuriy Tymchuk >

Re: [Pharo-dev] Package comments

2015-05-06 13:08 GMT+02:00 Marcus Denker : > > > On 06 May 2015, at 10:53, Christophe Demarey < > christophe.dema...@inria.fr> wrote: > > > > > > Le 5 mai 2015 à 17:14, Kasper Osterbye a écrit : > > > >> Marcus Denker-4 wrote > >>> Right now we do not have yet Package comments. > >>> > >>> But we

Re: [Pharo-dev] last time I had insomnia...

One question, how can I contribute? Uko > On 28 Apr 2015, at 17:28, Nicolai Hess wrote: > > > > 2015-04-28 15:32 GMT+02:00 Yuriy Tymchuk >: > > > On 28 Apr 2015, at 15:20, Esteban Lorenzano > > wrote: > > > > > >> On 28 Apr 2015, at

Re: [Pharo-dev] Class Comment Template Suggestion

stepharo wrote > I have no problem with changing it this is just that we should in > general write much better class comments. This is true for all commentary. :-) One of the most important things to include in comments and which is usually omitted is the rationale. Explain why the class exists

Re: [Pharo-dev] [Pharo-Dev] BDD framework

There's Mocketry [http://www.smalltalkhub.com/#!/~dionisiy/Mocketry]. It does not support the Given-When-Then constructs, but it has its own Spec DSL (nearly natural english indeed:) and I believe it is pretty enough to practice TDD/BDD. -- Best regards, Dennis Schetinin 2015-05-06 18:50 GMT+

Re: [Pharo-dev] [Pharo-Dev] BDD framework

Hi, I have this link but no more information: Kiwi TDD (https://www.youtube.com/watch?v=m2t_MbVAdis) Regards, Christophe Le 6 mai 2015 à 16:50, Maximiliano Taborda a écrit : > Hi people, > Is there some framework for BDD in Pharo? Something like Behave or Cucumber? > > Thanks. > > Regards. >

[Pharo-dev] [Pharo-Dev] BDD framework

Hi people, Is there some framework for BDD in Pharo? Something like Behave or Cucumber? Thanks. Regards. Maxi

Re: [Pharo-dev] tracker.pharo.org

> On 06 May 2015, at 15:52, Sean P. DeNigris wrote: > > How does it work? Is it communicating directly with fogbugz? Are there other yes, though an API > services besides http://tracker.pharo.org/issues-register-service and > http://tracker.pharo.org/issues/name/anIssueNumber? >

[Pharo-dev] [pharo-project/pharo-core] c46d96: 50036

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c46d964682baff465dfc93e0da7c88a2693e873b https://github.com/pharo-project/pharo-core/commit/c46d964682baff465dfc93e0da7c88a2693e873b Author: Jenkins Build Server Date: 2015-05-06 (Wed, 06 May 2015

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50036 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] tracker.pharo.org

How does it work? Is it communicating directly with fogbugz? Are there other services besides http://tracker.pharo.org/issues-register-service and http://tracker.pharo.org/issues/name/anIssueNumber? - Cheers, Sean -- View this message in context: http://forum.world.st/tracker-pharo-org-tp48

Re: [Pharo-dev] Class Comment Template Suggestion

stepharo wrote > I have no problem with changing it this is just that we should in > general write much better class comments. Issue 15498: Improve Class Comment Template https://pharo.fogbugz.com/default.asp?15498 SLICE-Issue-15498-Improve-Class-Comment-Template-SeanDeNigris.1 - Remove class na

[Pharo-dev] Finder Source Search Shows Trait Users

While searching for the class comment template, I did a source search in the finder on a text fragment. Three results came back: TClassDescription, where it is implemented, and both of its users - ClassDescription and TraitDescription. Senders and Implementors seems to handle this correctly - that

Re: [Pharo-dev] GTSpotter > code view > class comment

On Wed, May 6, 2015 at 9:02 PM, Sven Van Caekenberghe wrote: > > > On 06 May 2015, at 14:55, Andrei Chis > wrote: > > > > Hi Ben, > > > > Could you also create 'would be nice issues' for these requests. > > Otherwise they will get lost on the mailinglist. > https://pharo.fogbugz.com/default.asp

Re: [Pharo-dev] GTSpotter > code view > class comment

> On 06 May 2015, at 14:55, Andrei Chis wrote: > > Hi Ben, > > Could you also create 'would be nice issues' for these requests. > Otherwise they will get lost on the mailinglist. > > On Wed, May 6, 2015 at 2:40 PM, Ben Coman wrote: > Just a passing thought and request. When the code view is

Re: [Pharo-dev] GTSpotter > code view > class comment

This one is about having multiple views on an object in spotter :). @Ben: currently, the rendering of Spotter does not support multiple views, but we will work on this. Doru On Wed, May 6, 2015 at 2:55 PM, Andrei Chis wrote: > Hi Ben, > > Could you also create 'would be nice issues' for thes

Re: [Pharo-dev] GTSpotter > code view > class comment

Hi Ben, Could you also create 'would be nice issues' for these requests. Otherwise they will get lost on the mailinglist. On Wed, May 6, 2015 at 2:40 PM, Ben Coman wrote: > Just a passing thought and request. When the code view is open in Spotter > and a class is selected, could the class comm

Re: [Pharo-dev] Rendering morph list items in NewList

Should I use another morph? Uko > On 05 May 2015, at 21:03, Alain Plantec via Pharo-dev > wrote: > > > From: Alain Plantec > Subject: Re : [Pharo-dev] Rendering morph list items in NewList > Date: 5 May 2015 21:03:45 CEST > To: Pharo Development List > > > Hello > I ve the impression that

[Pharo-dev] GTSpotter > code view > class comment

Just a passing thought and request. When the code view is open in Spotter and a class is selected, could the class comment be shown as well its definition. Maybe also show the class-side definition(?). Maybe also show the hierarchy tree as a bread-crumb .e.g. A > B > C (???) cheers -ben

Re: [Pharo-dev] Rendering morph list items in NewList

I use just NewList because I need a plain morph. For items I use a method like: listItemFor: anObject | listItem | listItem := Morph new “setup morph" yourself. “add submorphs" ^ listItem Uko > On 05 May 2015, at 2

Re: [Pharo-dev] Package comments

Le 6 mai 2015 à 13:21, Kasper Osterbye a écrit : > demarey wrote >> If you want to allow package comments in Nautilus, I would display the >> content of the description method of the package manifest if available. > > It would be great to leverage on something already taking place. > Are you ta

Re: [Pharo-dev] Package comments

demarey wrote > If you want to allow package comments in Nautilus, I would display the > content of the description method of the package manifest if available. It would be great to leverage on something already taking place. Are you talking about class PackageManifest? I can see that RPackage h

Re: [Pharo-dev] Package comments

> On 06 May 2015, at 10:53, Christophe Demarey > wrote: > > > Le 5 mai 2015 à 17:14, Kasper Osterbye a écrit : > >> Marcus Denker-4 wrote >>> Right now we do not have yet Package comments. >>> >>> But we should! >>> >>> MBInfo seems to be a private class of Versionner… >>> >>> For package

Re: [Pharo-dev] Package comments

Le 5 mai 2015 à 17:14, Kasper Osterbye a écrit : > Marcus Denker-4 wrote >> Right now we do not have yet Package comments. >> >> But we should! >> >> MBInfo seems to be a private class of Versionner… >> >> For package comments we first need to evaluate the design space… >> e.g. where to stor

Re: [Pharo-dev] Package comments

Sergio Fedi wrote > If you need help, or just a buddy to tag along I can work with you.​ That would likely be very nice Sergio. I have opened a case in FogBugz (https://pharo.fogbugz.com/f/cases/15495/Package-comments) for this. I believe the result of this work will end up as some kind of slice.

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50035 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 054b2e: 50035

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 054b2e2582f5791735d8fbd3759b123cbfc6b608 https://github.com/pharo-project/pharo-core/commit/054b2e2582f5791735d8fbd3759b123cbfc6b608 Author: Jenkins Build Server Date: 2015-05-06 (Wed, 06 May 2015

Re: [Pharo-dev] Package comments

> On 05 May 2015, at 17:14, Kasper Osterbye wrote: > > Marcus Denker-4 wrote >> Right now we do not have yet Package comments. >> >> But we should! >> >> MBInfo seems to be a private class of Versionner… >> >> For package comments we first need to evaluate the design space… >> e.g. where to

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50034 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 83b5ff: 50034

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 83b5ff9889e54d0928b5e7cf6d6b8adc13734ded https://github.com/pharo-project/pharo-core/commit/83b5ff9889e54d0928b5e7cf6d6b8adc13734ded Author: Jenkins Build Server Date: 2015-05-06 (Wed, 06 May 2015