- Pharo-users - lists.pharo.org

Re: [Pharo-users] Starting with Pharo Issue Tracker

by Jigyasa Grover

Exactly my question. Thanks for the help :) -- View this message in context: http://forum.world.st/Starting-with-Pharo-Issue-Tracker-tp4814883p4815016.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 25, 2015

Re: [Pharo-users] Git overriding repo load from different source

by Jan B.

Hello I was able to get by those warnings automatically by adding onLock: [ :ex | ex disallow ]; in addition to onConflict Metacello new baseline: '...' repository: 'gitfiletree:///.../repository' onConflict: [ :ex | ex allow ]; onLock: [ :ex | ex disallow ]; load I'm not sure whether it couldn't cause any problems, but it seems to be working. Jan Peter UhnÃ¡k wrote >> If so then the trick is to use the Metacello `lock` ... Do the following >> BEFORE loading the project that depends upon you sample project: >> > Combined with onConflict: mentioned by Thierry this works like a charm, > thanks a lot. :) > > >> (a Warning is dumped to the transcript) ... >> > I got a warning prompt which I had confirm ("proceed") couple of times, > but > that's just a detail. > > Thanks a lot! > > Peter -- View this message in context: http://forum.world.st/Git-overriding-repo-load-from-different-source-tp4813… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 25, 2015

Re: [Pharo-users] Collection with memory?

by Sven Van Caekenberghe

OK, I get your point now, #read and #read: are a better combination than #get and #read: About #++ and friends, yes I think they are so uncommon that they do not warrant a special selector, what is the point ? > On 25 Mar 2015, at 09:12, stepharo <stepharo(a)free.fr> wrote: > >> Stef, >> >> Like Denis said, there is no #next: in Xtreams, AFIACT. > > Yes but this is the same > we should get read and read: and not get and read: > This is my point. >> >> There are >> >> XTReadStream>>#get >> "Read an object from self. >> If there aren't any elements left in the stream, the Incomplete exception is raised." >> >> and >> >> XTReadStream>>#read: anInteger >> "Read anInteger's worth of elements from self and return them in a collection. >> If full anInteger number of elements cannot be read from the source, the Incomplete exception is raised." >> >> Like I said, these selector names were chosen to prevent confusion, on purpose. I think that is good. I also think that a lot of though went into the design. > I personally think that > get and read: are bad and irregular. > > XTReadStream>>#read > "Read an object from self. > If there aren't any elements left in the stream, the Incomplete exception is raised." > > XTReadStream>>#read: anInteger > "Read anInteger's worth of elements from self and return them in a collection. > If full anInteger number of elements cannot be read from the source, the Incomplete exception is raised." > > > funny how the comments are good. No need to change them. This is a sign.

March 25, 2015

Re: [Pharo-users] new link to query all projects in smalltalkhub

by Stephan Eggermont

On 24/03/15 17:36, Merwan Ouddane wrote: > Thanks for the instructions, > > I'll do it as soon as I can :) > > There is an issue that i'd like to report too, I have a team with a > non-ascii character, and i can't remove team members nor delete the > entire team, I'll try to fix it too. That sounds like a good issue to experiment with on your own installation first :) Thanks for picking this up. Stephan

March 25, 2015

Re: [Pharo-users] Boardician (board game framework)

by stepharo

Hi laura I would do a massive rename :) EDirector new play. does not tell me anything BPDirector new play. DPDirector new play. GDirector new play. neither :) Stef Le 24/3/15 15:41, Laura Risani a Ã©crit : > Hi all, > > A time ago i posted two board games on the list and StÃ©phane said that > he would like to extract from these and other ones he has gathered a > framework for doing board games. So i developed a little one called > 'Boardician' and implemented four little example games through it. > > DOCUMENTATION > http://boardician.blogspot.com.ar/2015/03/boardician.html > > DOWNLOAD <https://www.blogger.com/null> > You can install configuration BgBoardician from Configuration Browser > on 3.0 and 4.0 . This will download packages of framework > (BgBoardician) and example games (BgBoxPush, BgEatBullet, BgDropPiece, > BgEatElongating) > > To run example games send > > EDirector new play. > BPDirector new play. > DPDirector new play. > GDirector new play. > > > FEEDBACK <https://www.blogger.com/null> > If you like (i would really like you to) to send any feedback comments > on design / names / implementation / functionalities to add / > questions you can post a comment on the blog / mail me. > > Next i'll be adding tests and uploading development history to > project's repo. > > Best, > Laura

March 25, 2015

Re: [Pharo-users] Boardician (board game framework)

by stepharo

We should help laura and do a code review. Laura I do not know if you change it in the latext version but I would not subclass from Matrix but use composition instead. Le 24/3/15 15:41, Laura Risani a Ã©crit : > Hi all, > > A time ago i posted two board games on the list and StÃ©phane said that > he would like to extract from these and other ones he has gathered a > framework for doing board games. So i developed a little one called > 'Boardician' and implemented four little example games through it. > > DOCUMENTATION > http://boardician.blogspot.com.ar/2015/03/boardician.html > > DOWNLOAD <https://www.blogger.com/null> > You can install configuration BgBoardician from Configuration Browser > on 3.0 and 4.0 . This will download packages of framework > (BgBoardician) and example games (BgBoxPush, BgEatBullet, BgDropPiece, > BgEatElongating) > > To run example games send > > EDirector new play. > BPDirector new play. > DPDirector new play. > GDirector new play. > > > FEEDBACK <https://www.blogger.com/null> > If you like (i would really like you to) to send any feedback comments > on design / names / implementation / functionalities to add / > questions you can post a comment on the blog / mail me. > > Next i'll be adding tests and uploading development history to > project's repo. > > Best, > Laura

March 25, 2015

Re: [Pharo-users] Collection with memory?

by stepharo

> Stef, > > Like Denis said, there is no #next: in Xtreams, AFIACT. Yes but this is the same we should get read and read: and not get and read: This is my point. > > There are > > XTReadStream>>#get > "Read an object from self. > If there aren't any elements left in the stream, the Incomplete exception is raised." > > and > > XTReadStream>>#read: anInteger > "Read anInteger's worth of elements from self and return them in a collection. > If full anInteger number of elements cannot be read from the source, the Incomplete exception is raised." > > Like I said, these selector names were chosen to prevent confusion, on purpose. I think that is good. I also think that a lot of though went into the design. I personally think that get and read: are bad and irregular. XTReadStream>>#read "Read an object from self. If there aren't any elements left in the stream, the Incomplete exception is raised." XTReadStream>>#read: anInteger "Read anInteger's worth of elements from self and return them in a collection. If full anInteger number of elements cannot be read from the source, the Incomplete exception is raised." funny how the comments are good. No need to change them. This is a sign. > > #++ could be aliased to #seekForward: and #-- to #seekBackward: I guess. I also do not really like the look of them. I will not aliased them. Just deprecate them :) I do not want to have to always scratch my head to understand the code seekForward and seekBackward is much much nicer. > > BTW, I think that the compatibility layer/wrapper is not good (I would be very surprised if it could hide all the semantic differences). What is the point to switch to a new stream API if you hide it ? Incremental migration. > > Also, the current stream API is 'too wide', there are too many methods, too much is expected from streams. To change that, the users must be changed. Yes we will do that. > > Sven > >> On 23 Mar 2015, at 22:06, stepharo <stepharo(a)free.fr> wrote: >> >> >>>>>> Yes but with >>>>>> r next. >>>>>> r next >>>>> The choice for different selector names was intentional, by design. To avoid confusion, because #next and #get are not 100% identical (semantically). This is an important point. >>>> No I asked martin personally. This is the real reason. There were also experimenting to offer an API closer to other language. >>>> So that we have >>>> r get. >>>> r next: 4 >>> IIRC, one difference between #get and #next is that >>> >>> get cannot return nil and will throw an Incomplete exception when EOF >>> next can return nil and might throws an Exception >>> >>> Changing the meaning of an existing selector will cause many problems and discussions. People will think they do not have to change anything and they will be wrong. >> Indeed now this is still not a nice API. >> So what would be a nice name for get >> >> I do not get it. I'm probably too tired >> >> get so it is named get and not next. >> get cannot return nil and will throw an Incomplete exception when EOF >> but >> next: that could be confused with next >> can return nil and might throws an Exception (because it should follow next) :) >> No stupid stef. >> next: is from xtreams so it should follow get >> get cannot return nil and will throw an Incomplete exception when EOF >> Ahhhhhhhh this is probably clear. >> >> So could we be consistent >> >> nextItem >> nextItems: >> putItem: >> >> >> Now since in anyways people will have to revisit they wrapping of next calls >> which should probably wraped into and Exception. >> I do not see the problem. It is because there is a wrapper that would turn an Xstream stream into a old API (then again I do not understand >> because since the wrapper is another class it can have a next method that delegates to the correct wrapped xstream which may have or not the same api. >> So what is the point? >> >> I mean once xtream will replace the old one it will be for about 10 years so >> I'm sorry but we should get the api right (and yes I know that ++ -= are correct smalltalk still they SUCK). >> >> Stef >> >> >> > >

March 25, 2015

Re: [Pharo-users] Starting with Pharo Issue Tracker

by stepharo

Thanks! We are busy with deadlines these weeks :) Stef Le 25/3/15 00:14, Ben Coman a Ã©crit : > > > On Wed, Mar 25, 2015 at 2:33 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>> wrote: > > http://pharo.org/contribute-propose-fix > > > Thats great Jigyasa. Always good to have more contributors. Now for > those of us who have been doing it a while, it is not always obvious > where there are gaps to get new people started off. So please ask > plenty of question if you get stuck. > > Is your question that you don't have a particular bug to work on and > would like a suggestion? > * Check that reported bugs include have suitable steps-to-reproduce. > If not, then ask the submitter for more details and report on the > issue if you are able to reproduce it. > > * Start by reviewing other people fixes. Sometimes these are in deep > places that are daunting at first, but I learnt an immense amount > doing this when I started, and continue to do so. Do the first step > of merging in a SLICE from the Pharo4Inbox (soon to be Pharo5Inbox) > but don't complete it - keep it as a reference. Open the Inbox again > and do the merge for real. Then throw a few halts into the modified > methods and try to reproduce the bug. You learn Pharo best by > watching it run, not just looking at code. > > * In an image without the bug fix, put halts in the same methods, then > single step both images in sync until you can observe differences - > and that is where you learn the most. > > Tip: At the link above, where it says... "Take the latest stable or > latest development system, ideally using the latest virtual machine > (check the _downloads_)" - I'd suggest using PharoLauncher > (http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher > <http://www.smalltalkhub.com/#%21/%7EPharo/PharoLauncher>) which makes > it very easy to grab the latest build. > > cheers -ben > >

March 25, 2015

Re: [Pharo-users] How to depend on another Github repo from the baseline ?

by kilon alios

Thank you both, I changed my code accordingly to load SmaCC as the example of Thierry.

March 25, 2015

Re: [Pharo-users] XClipboard

by Peter UhnÃ¡k

I know how frustrating this can be (frustrating enough that I found the courage to dive into VM :)). Also in case you want to use pharo launcher you need to set it there too (since Launcher launches a new process). In PhLImage>>launch: change last line to ^OSProcess command: vmCommand , ' --textenc UTF-8 "' , imagePath, '"'. Peter On Wed, Mar 25, 2015 at 7:16 AM, Julien Delplanque <julien(a)tamere.eu> wrote: > Ho thanks for pointing me this solution it works well. I will use it > because I don't like the fact I had to touch to the System for my solution. > > You're saving me from a lot of Chromium->Sublime Text, Sublime > Text->Pharo :) > > Thank you once again! > > Julien > > On 24/03/15 21:30, Peter UhnÃ¡k wrote: > > Hi, > > > > this is brutal indeed; have you tried the previously mentioned workaround > > with setting the encoding: > > > http://forum.world.st/Pharo-and-X11-primary-selection-aka-middle-mouse-butt… > > > > Interestingly enough I posted an answer to the original (your) thread but > > somehow it created a new one instead. > > > http://forum.world.st/Re-Copy-past-doesn-t-work-sometimes-in-Chrome-semifix… > > > > I saw that it's possible to get the content of x11 clipboard in C using > >> x11 libs > > That's what the VM does inside (there's a link to the VM code in the > first > > link above). > > > > Peter > > > > >

March 25, 2015