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

Re: [Pharo-dev] [Bloc] Getting involved

by kilon alios

and of course it did not occur to me to search is smalltalkhub ! Yeah sorry that was an obvious one. On Sat, Nov 15, 2014 at 11:38 PM, stepharo <stepharo(a)free.fr> wrote: > > is there a place where we can check the code and see what Bloc is all > about ? > > > AlainPlantec > Bloc project > If I get enough time I will write a doc.... now just a empty draft. > > > On Sat, Nov 15, 2014 at 9:59 PM, stepharo <stepharo(a)free.fr> wrote: > >> >> On 11/11/14 00:43, Santiago Bragagnolo wrote: >> >>> Hi Guys, (Alan and Steph punctually) I want to comment I am getting >>> involved with Bloc, since i need to draw several things and i need an >>> Athens canvas. >>> >>> I am checking if it is the best tool for my needs. In any case I am >>> doing some contributions that i would like to commit and to share. Actually >>> i am working on draft a window, a tool bar, a button based on images and >>> animations. >>> >>> Then, there is any mailing list for Bloc? How is the push-request cycle? >>> >> >> Alain told me that you should design a widget and based on the quality >> he will let you commit :) >> I'm confident. So let us know which widget you want to work on. >> >> Stef >> >>> >>> Thanks :). >>> >>> Santiago. >>> >>> >> >> > >

Nov. 15, 2014

Re: [Pharo-dev] Configurations and Github for a specialised configuration browswe

by Dale Henrichs

On Sat, Nov 15, 2014 at 9:54 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > Travis seems like an overkill for me right now. Sure if I was bombarded by > pull requests from other developers but in reality I work alone . But I > will definitely keep it in mind in case my projects become so popular that > people start to send me pull requests regularly. > Makes sense. > > All I wanted was an easy way to install code from github to pharo without > the need to install git and you gave me that. Next step is to see how I > would integrate github with pharo better, should I use Configuration > versions or is it better to use branches ? I am more orientated towards > branches. > With git I think that configurations are really no longer necessary ... I prefer to use branches to isolate development work from the master branch (topic branches) and then use tags to identify release points ... with travis-ci validating the commits, I can do continuous deployment on the master branch ... For Seaside31 we are using tags to stay in sync with the mcz repository so the tags are useful when folks are used to talking about useing a particular version of Seaside31. To replace symbolic versions (like #release3 or #release3.1) we have introduced pattern matching for tags. You can use the following github url to load the latest version of 3.1: github://GsDevKit/Seaside31:3.1.?/repository > I have stared your repos to make sure I get keep updated in any progress > you make. I plan also to go back and re read that metacello chapter to > better understand metacello. > Take a look at the Metacello User Guide[1] as well for information about using the Metacello Scripting API. [1] https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > > Thank you very much for your hard work, keep rocking :) > > Haha, my pleasure! Dale

Nov. 15, 2014

Re: [Pharo-dev] ValueHolder analysis

by stepharo

I get dizzy (may be time to go to sleep) but I wonder why do we need to check first the the window changed and after that it got closed? Especially since whenWindowChanged: presuppose that we have access to window. Am I missing something? self whenWindowChanged: [ :w | w whenClosedDo: [ self clear ] ]. ComposableModel>>whenWindowChanged: aBlock window whenChangedDo: aBlock WindowModel>>whenClosedDo: aBlock isClosedHolder whenChangedDo: [:value | value ifTrue: [ aBlock value ] ]

Nov. 15, 2014

Re: [Pharo-dev] ValueHolder analysis

by stepharo

initializePresenter "Used to specify the subwidgets, and/or to bind them together" "By default, do not do anything" extentHolder whenChangedDo: [:ex | self widget ifNotNil: [:widget | (widget respondsTo: #extent:) ifTrue: [ widget extent: ex ]]]. may be by design the ifNotNil should not be needed and the respondsTo too.... pffff.

Nov. 15, 2014

Re: [Pharo-dev] [NB] NativeBoost and optCoerceNilToNull

by stepharo

Igor Could you document this part of NB? Write one page on your old blog so that after we can turn it into a real doc. Stef On 15/11/14 22:28, Igor Stasenko wrote: > > > On 15 November 2014 15:53, Max Leske <maxleske(a)gmail.com > <mailto:maxleske@gmail.com>> wrote: > > Once again Iâm struggling with NativeBoost. Iâm trying to use > optCoerceNilToNull with this function: > > ^self call: #(LGitReturnCodeEnum git_commit_create( > LGitId * theCommitId, > LGitRepository repo, > String update_ref, > LGitSignature * theAuthor, > LGitSignature * theCommitter, > String message_encoding, > String theMessage, > LGitTree theTree, > int parent_count, > LGitCommit * parentsPointer)) options: #( optCoerceNilToNull ) > > The last argument can be NULL, per documentation, (no parents). > LGitCommit is a subclass of NBExternalObject and apparently > NBExternalObjctType>>pushAsPointer: does *not* use the > optCoerceNilToNull option (the super implementation in > NBExternalType>>pushAsPointer: however does). The upshot of course > is that the call fails with âan instance of LGitCommit expectedâ. > > My questions: > - The documentation says: > > > "#optCoerceNilToNull" > "passing nil as a pointer-type argument, converts it to C NULL â > > but apparently this doesnât apply to every pointer type. Should > the documentation be updated? > - Why does NBExternlObjectType not use optCoerceNilToNull? I donât > want to use tricks to pass null if I donât have to. > > > perhaps because it is not there? :) > So, lets add it. > > - Related: there are instances where even non-pointer arguments > are allowed to be NULL. Why does optCoerceNilToNull only work for > pointer types? > > like what? Suppose the argument type is a structure, e.g > "struct foo bar", that is non-pointer type. What in this case the NULL > value for the structure? > > Igor! Help! :) > > Cheers, > Max > > > > > -- > Best regards, > Igor Stasenko.

Nov. 15, 2014

Re: [Pharo-dev] [Bloc] Getting involved

by stepharo

> is there a place where we can check the code and see what Bloc is all > about ? AlainPlantec Bloc project If I get enough time I will write a doc.... now just a empty draft. > > On Sat, Nov 15, 2014 at 9:59 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > On 11/11/14 00:43, Santiago Bragagnolo wrote: > > Hi Guys, (Alan and Steph punctually) I want to comment I am > getting involved with Bloc, since i need to draw several > things and i need an Athens canvas. > > I am checking if it is the best tool for my needs. In any case > I am doing some contributions that i would like to commit and > to share. Actually i am working on draft a window, a tool bar, > a button based on images and animations. > > Then, there is any mailing list for Bloc? How is the > push-request cycle? > > > Alain told me that you should design a widget and based on the > quality he will let you commit :) > I'm confident. So let us know which widget you want to work on. > > Stef > > > Thanks :). > > Santiago. > > > >

Nov. 15, 2014

Re: [Pharo-dev] [NB] NativeBoost and optCoerceNilToNull

by Igor Stasenko

On 15 November 2014 15:53, Max Leske <maxleske(a)gmail.com> wrote: > Once again Iâm struggling with NativeBoost. Iâm trying to use > optCoerceNilToNull with this function: > > ^self call: #(LGitReturnCodeEnum git_commit_create( > LGitId * theCommitId, > LGitRepository repo, > String update_ref, > LGitSignature * theAuthor, > LGitSignature * theCommitter, > String message_encoding, > String theMessage, > LGitTree theTree, > int parent_count, > LGitCommit * parentsPointer)) options: #( optCoerceNilToNull ) > > The last argument can be NULL, per documentation, (no parents). > LGitCommit is a subclass of NBExternalObject and apparently > NBExternalObjctType>>pushAsPointer: does *not* use the optCoerceNilToNull > option (the super implementation in NBExternalType>>pushAsPointer: however > does). The upshot of course is that the call fails with âan instance of > LGitCommit expectedâ. > > My questions: > - The documentation says: > > > "#optCoerceNilToNull" > "passing nil as a pointer-type argument, converts it to C NULL â > > but apparently this doesnât apply to every pointer type. Should the > documentation be updated? > - Why does NBExternlObjectType not use optCoerceNilToNull? I donât want to > use tricks to pass null if I donât have to. > perhaps because it is not there? :) So, lets add it. - Related: there are instances where even non-pointer arguments are allowed > to be NULL. Why does optCoerceNilToNull only work for pointer types? > > like what? Suppose the argument type is a structure, e.g "struct foo bar", that is non-pointer type. What in this case the NULL value for the structure? > Igor! Help! :) > > Cheers, > Max > > -- Best regards, Igor Stasenko.

Nov. 15, 2014

Re: [Pharo-dev] [Bloc] Getting involved

by kilon alios

is there a place where we can check the code and see what Bloc is all about ? On Sat, Nov 15, 2014 at 9:59 PM, stepharo <stepharo(a)free.fr> wrote: > > On 11/11/14 00:43, Santiago Bragagnolo wrote: > >> Hi Guys, (Alan and Steph punctually) I want to comment I am getting >> involved with Bloc, since i need to draw several things and i need an >> Athens canvas. >> >> I am checking if it is the best tool for my needs. In any case I am doing >> some contributions that i would like to commit and to share. Actually i am >> working on draft a window, a tool bar, a button based on images and >> animations. >> >> Then, there is any mailing list for Bloc? How is the push-request cycle? >> > > Alain told me that you should design a widget and based on the quality he > will let you commit :) > I'm confident. So let us know which widget you want to work on. > > Stef > >> >> Thanks :). >> >> Santiago. >> >> > >

Nov. 15, 2014

Re: [Pharo-dev] How to refresh the pharo window manually

by kilon alios

I tried to search for update method , could not find anything meaningful , there like a gazillion update methods. Another problem is how to get hold of WorldMorph of DisplayScreen or whatever class is responsible for the update. Do I access through the Smalltalk global ? How ? On Sat, Nov 15, 2014 at 9:50 PM, stepharo <stepharo(a)free.fr> wrote: > did you try update? > > > On 15/11/14 13:26, kilon alios wrote: > >> Hello guys I am making a theme manager and I have observed that when I >> choose a background color for pharo windows it does not update properly. >> How I can force the whole pharo window to update ? I have found >> DisplayScreen and WorldMorph but no idea how to use them. >> > > >

Nov. 15, 2014

Re: [Pharo-dev] Who broke my System Preferences ?

by stepharo

The theme design is ot good but getting a good one is difficult. I did some prototype to get a feel of the work to be done but this is still unclear to me. I want to see how we could do that with Bloc. Stef On 10/11/14 16:00, kilon alios wrote: > no worries I would not even dream to blame you and yes I completely > agree that you did not need to wait for a review ,after all its not > that much of a big deal to ping the mailing list as I did and you > fixing it at your own pace , I can always use an older build at any time. > > The Theme classes is kinda strange, I think that Pharo needs a > standard on theme support and that standard must be deeply rooted > inside Morphic so that each morph implements its own theme support. Of > course for that the community will need to sit down and agree what > that standard must be or else you will see theme classes popping > around like mushrooms. > > On Mon, Nov 10, 2014 at 3:46 PM, Marcus Denker <marcus.denker(a)inria.fr > <mailto:marcus.denker@inria.fr>> wrote: > > > > On 10 Nov 2014, at 14:18, kilon alios <kilon.alios(a)gmail.com > <mailto:kilon.alios@gmail.com>> wrote: > > > > looks like latest Pharo 4 40363 broke System Preferences > clicking on Appearance gives me this > > > > Oh, I missed call in fontSizeRowâ¦ I thought I tested it. I will > fix it... > (Hint: I always wait for people to review my changesâ¦ but that > does not happen very often) > > > Marcus > >

Nov. 15, 2014