December 2015 - Pharo-users

Re: [Pharo-users] Fossil and Filetree

by SaÅ¡a JaniÅ¡ka

On Sri, 2015-12-23 at 09:20 -0500, Offray Vladimir Luna CÃ¡rdenas wrote: > In a computing monoculture of overcomplex ways of doing programmingÂ > and DVCS is refreshing to find a community where alternative ideas > like Pharo and fossil and listened and used. Indeed...now I'm into learning Pharo trying to adjust to some alternatives, but those will require to ask some additional questions. Sincerely, Gour --Â Even if you are considered to be the most sinful of all sinners, when you are situated in the boat of transcendental knowledge you will be able to cross over the ocean of miseries.

Dec. 25, 2015

Re: [Pharo-users] AgileVisualization - call for reviewers

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 23/12/15 16:54, Offray Vladimir Luna CÃ¡rdenas wrote: > Ps: I have a "philosophical problem" with the "Hello World" example > everywhere, and a particular place where it seems uninteresting is in > data visualization where a lot of introductory visualization are far > more powerful, yet simple, but I think that would need a proper blog > post instead of a margin comment. > And here it is ;-): http://mutabit.com/offray/blog/en/entry/dumb-hello-world Cheers, Offray

Dec. 24, 2015

Re: [Pharo-users] #storeOn: question

by Tudor Girba

Hi, It would certainly not be in Core. I was thinking it to be in Ring. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow" > On 21 Dec 2015, at 23:03, stepharo <stepharo(a)free.fr> wrote: > > How this method is packaged? Because I do not want to have in the core like that especially if it add dependencies to MC > > Stef > > Le 16/12/15 22:47, Tudor Girba a Ã©crit : >> Hi, >> >> I wanted to have an easy way to distinguish between a class that ships with Pharo and another class that is built on top. Unfortunately, I did not find a good enough heuristic (I used to rely on the repository of the package where the class is defined as being the Pharo one), so this was not added until we find a different solution. >> >> This is useful in several situations. The one I am in very often is to use extra tools that are in Moose to analyze Pharo. This was the case below where we needed to get the list of the storeOn: senders more accurately. >> >> Cheers, >> Doru >> >> >>> On Dec 16, 2015, at 10:41 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> hi doru >>> >>> what is isPharoClass? >>> Why do you need it? >>> >>> Stef >>> >>> Le 9/12/15 21:49, Tudor Girba a Ã©crit : >>>> I created an issue with a slice: >>>> https://pharo.fogbugz.com/f/cases/17224/TBehavior-isPharo >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>>> On Dec 9, 2015, at 3:33 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> Hi again, >>>>> >>>>>> On Dec 9, 2015, at 3:30 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Thanks for the question. I am at a conference, and I just took this problem to explain someone what code querying can mean :). >>>>>> >>>>>> Here is the result: >>>>>> http://ws.stfx.eu/CCSNJVWX3JKS >>>>> I just realized that isPharoClass only exists in my image for the moment :) >>>>> >>>>> Doru >>>>> >>>>> >>>>>> <storeOn.png> >>>>>> >>>>>> I think this is how we should document our communication because now we have the tools. >>>>>> >>>>>> Cheers, >>>>>> Doru >>>>>> >>>>>> >>>>>>> On Dec 3, 2015, at 7:00 AM, Werner Kassens <wkassens(a)libello.com> wrote: >>>>>>> >>>>>>> Hi Stephane, >>>>>>> there are 89 senders of #storeOn: minus around 30 implementations of #storeOn: minus around 10 tests, also things like the PharoChangesCondenser use it. then there are 26 senders of #storeString (essentially the same functionality implemented via #storeOn:, but returns a string) eg used by the StartupPreferencesLoader. and there are several senders of #store: that are not implementations of #storeOn:. iow deprecating #storeOn: looks a bit complicated to me and is obviously way above my head. >>>>>>> werner >>>>>>> >>>>>>>> On 11/30/2015 09:42 PM, stepharo wrote: >>>>>>>> It would be good to check who is using that and evaluate if we can >>>>>>>> remove it. >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> >>>>>> "Every thing should have the right to be different." >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "One cannot do more than one can do." >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Yesterday is a fact. >>>> Tomorrow is a possibility. >>>> Today is a challenge." >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "It's not what we do that matters most, it's how we do it." > >

Dec. 24, 2015

Re: [Pharo-users] [Moose-dev] AgileVisualization - call for reviewers

by Tudor Girba

Great work! Doru -- www.tudorgirba.com "Every thing has its own flow" > On 23 Dec 2015, at 19:57, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Dear All, > > As you may have heard, AgileVisualization is a book about the Roassal visualization engine. > We hope to have the book released soon, within a couple of months. It would be fantastic to have feedback: > > http://agilevisualization.com > > The book is a fantastic result of the community. You guys made this possible, and we wish to thank you very much for this. > > Beers will flow at ESUG for everybody who comment on the chapters :-) > We also have live discussion on Slack, channel #Roassal (see http://pharo.org/community on how to join Slack) > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Dec. 24, 2015

Re: [Pharo-users] AgileVisualization - call for reviewers

by Alexandre Bergel

Thanks Offray once more. I took your comments into account Alexandre > On Dec 23, 2015, at 6:54 PM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> wrote: > > Hi Alexandre, > > This are exiting news! I have been using Roassal and it has been a pleasure. I don't know if I'll have the time for a complete review, but what I'm going to do is to go to the book when I think I need a better understanding of the code I'm trying to write for a particular visualization and made comments. I have already started and I'm using hypothesis[1] to make my first annotations on the book web pages. Look at [2] to see the first one(s). By the way, hypothesis has been chosen in an academic and publishers alliance to promote open comments on the web[3] > > [1] https://hypothes.is/ > [2] https://via.hypothes.is/https://dl.dropboxusercontent.com/u/31543901/AgileV… > [3] https://hypothes.is/blog/a-coalition-of-over-40-scholarly-publishers/ > > Cheers, > > Offray > > Ps: I have a "philosophical problem" with the "Hello World" example everywhere, and a particular place where it seems uninteresting is in data visualization where a lot of introductory visualization are far more powerful, yet simple, but I think that would need a proper blog post instead of a margin comment. > > On 23/12/15 12:57, Alexandre Bergel wrote: >> Dear All, >> >> As you may have heard, AgileVisualization is a book about the Roassal visualization engine. >> We hope to have the book released soon, within a couple of months. It would be fantastic to have feedback: >> >> http://agilevisualization.com >> >> The book is a fantastic result of the community. You guys made this possible, and we wish to thank you very much for this. >> >> Beers will flow at ESUG for everybody who comment on the chapters :-) >> We also have live discussion on Slack, channel #Roassal (see http://pharo.org/community on how to join Slack) >> >> Cheers, >> Alexandre > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 24, 2015

Re: [Pharo-users] AgileVisualization - call for reviewers

by S Krish

The video is an excellent work of art not just the content it conveys of a better world with Open Annotations..!.. On Thu, Dec 24, 2015 at 3:57 AM, Offray Vladimir Luna CÃ¡rdenas < offray(a)riseup.net> wrote: > > > On 23/12/15 17:00, Alexandre Bergel wrote: > > Thanks Offray! > > > No problem. > > I am able to see your annotation. I did not know about hypothes.is. This > is very nice! > > > That's part of the tools you put under your "bat belt" when trying to make > open/citizen/garage science & research ;-). > > Cheers, > > Offray >

Dec. 24, 2015

Re: [Pharo-users] Teapot Cache Bug

by Attila Magyar

Haven't you forgot to stop the old server? If you use the latest Teapot then there will be a Teapot menu item in the world menu where you can check how many instances are currently running. You can stop them from the context menu. Or try to evaluate Teapot stopAll to stop all of them. -- View this message in context: http://forum.world.st/Teapot-Cache-Bug-tp4868426p4868427.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 24, 2015

Teapot Cache Bug

by ATTIOGBE Damessi Douwonou

Hi, All I'm from AFRICA/TOGO, I use Teapot, its Works, but the Routes cache stores the last Teapot routes, When i remove the route and restart Teapot server, after one requets, Teapot Report ERROR and show the route which i removed. Egg. GET:/name/<name> -> [ :req | req at:#name ] GET:/user/<name> -> [ :req | req at:#username ] after remove the first route and do: ZnEasy get:' http://localhost:8080/name/John', Its works the first time. After if I do: GET:/user/<name> -> [ :req | req at:#username ] *Have this Error: TeaNoSuchParam: Param 'name' not found * *rrefer to the first route. if i remove the route, the message persist.* -- *John ATTIOGBE.*

Dec. 24, 2015

Joyeux NoÃ«l, FrÃ¶hliche Weihnachten, Buon Natale, Feliz Navidad, vrolijk kerstfeest, glÃ¦delig jul, ÎºÎ±Î»Î¬ Î§ÏÎ¹ÏÏÎ¿ÏÎ³ÎµÎ½Î½Î±

by Richard Eng

https://medium.com/smalltalk-talk/why-no-language-innovations-e1dfed0a7a62 Cheers, Richard

Dec. 23, 2015

Re: [Pharo-users] AgileVisualization - call for reviewers

by Offray Vladimir Luna CÃ¡rdenas

On 23/12/15 17:00, Alexandre Bergel wrote: > Thanks Offray! > No problem. > I am able to see your annotation. I did not know about hypothes.is > <http://hypothes.is>. This is very nice! > That's part of the tools you put under your "bat belt" when trying to make open/citizen/garage science & research ;-). Cheers, Offray

Dec. 23, 2015