August 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [squeak-dev] [ANN] SimpleLogger released

by GÃ¶ran Krampe

Hi all! I wonder a few things: - Why was SimpleLog deemed "hard"? The class comment on SLLog etc is pretty straight forward IMHO! - Also SimpleLog has some quite nice features: - A really nice Morph to keep an eye on the logging going on, and to easily filter it etc, although it needs some love for Pharo to compile. - A log to file class with rotation. - Ability to use syslog like Ramon posted, in fact, I think SimpleLog was first with that. I just... wonder why we need to reinvent so many things over and over? Toothpick IMHO was a bit complex, I agree - that was the reason for creating SimpleLog, but hey, SimpleLog is *not* complex. regards, GÃ¶ran

Aug. 19, 2010

[Pharo-project] [update 1.2] #12099

by StÃ©phane Ducasse

12099 ----- - Removed possiblyChanged sent but not implemented methods in NewEditor. Issue 2827: remove all the senders of possiblyChanged - Issue 2829: Improve Watery2 theme drop list appearance. Thanks Gary Chambers. Progress is a step at a time and a lot of time. S. Ducasse the Wise

Aug. 19, 2010

Re: [Pharo-project] CogVM binaries!!! {WAS} Re: [squeak-dev] Re: CogVM on the Mac

by StÃ©phane Ducasse

The fixes of henrik where at the VM level. stef On Aug 19, 2010, at 10:34 AM, Tudor Girba wrote: > That is great, indeed! > > I was not aware of the socket fixes. Are these in the image or in the VM? > > Is there an official site for the change set that should be applied to Pharo 1.1? I only know the change set produced by Lukas. > > Cheers, > Doru > > > On 19 Aug 2010, at 09:45, Mariano Martinez Peck wrote: > >> >> >> On Thu, Aug 19, 2010 at 6:23 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> >> On Wed, Aug 18, 2010 at 8:14 PM, Chris Cunnington <smalltalktelevision(a)gmail.com> wrote: >> Wow. Have I been looking in the wrong place. >> I've been downloading trunk build files from svn listed on the squeakvm.org/unix pages, but *sigh* I didn't see the trove of stuff you just pointed out. And there are specific instructions for Mac and Unix builds. This is what I should be looking at. Thank you for pointing there. >> >> For folks' convenience I've just put up some unofficial builds (essentially the same builds I use for testing) under http://www.mirandabanda.org/files/Cog/VM >> >> >> HTH >> >> >> Hi Eliot. This, this HELPS A LOT. This is awesome. Seriously. This is really cool. Now we could start to create a Pharo one click based on Cog. >> Having the binaries will increase people using it, reporting bugs, and submitting fixes. >> >> Two questions: >> >> 1) why "unofficial" builds? >> >> 2) Do these binaries include the fixes from henrik to avoid the crash tha happens sometime? >> >> Thanks >> >> Mariano >> >> Eliot >> >> >> Chris >> >> >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Not knowing how to do something is not an argument for how it cannot be done." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 19, 2010

Re: [Pharo-project] CogVM binaries!!! {WAS} Re: [squeak-dev] Re: CogVM on the Mac

by Tudor Girba

It also looks like: - OSProcess works well on Mac - the bug related to the window preview in the Watery theme works with the latest VM (I am talking about the preview of the window when hovering over the task bar from Pharo) This is really great! Cheers, Doru On 19 Aug 2010, at 10:57, Lukas Renggli wrote: >> 2) Do these binaries include the fixes from henrik to avoid the >> crash tha >> happens sometime? > > Yes, looks like it. Seaside does not immediately crash the VM. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

Aug. 19, 2010

Re: [Pharo-project] CogVM binaries!!! {WAS} Re: [squeak-dev] Re: CogVM on the Mac

by Lukas Renggli

> 2) Do these binaries include the fixes from henrik to avoid the crash tha > happens sometime? Yes, looks like it. Seaside does not immediately crash the VM. Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 19, 2010

Re: [Pharo-project] CogVM binaries!!! {WAS} Re: [squeak-dev] Re: CogVM on the Mac

by Tudor Girba

That is great, indeed! I was not aware of the socket fixes. Are these in the image or in the VM? Is there an official site for the change set that should be applied to Pharo 1.1? I only know the change set produced by Lukas. Cheers, Doru On 19 Aug 2010, at 09:45, Mariano Martinez Peck wrote: > > > On Thu, Aug 19, 2010 at 6:23 AM, Eliot Miranda <eliot.miranda(a)gmail.com > > wrote: > > > On Wed, Aug 18, 2010 at 8:14 PM, Chris Cunnington <smalltalktelevision(a)gmail.com > > wrote: > Wow. Have I been looking in the wrong place. > I've been downloading trunk build files from svn listed on the > squeakvm.org/unix pages, but *sigh* I didn't see the trove of stuff > you just pointed out. And there are specific instructions for Mac > and Unix builds. This is what I should be looking at. Thank you for > pointing there. > > For folks' convenience I've just put up some unofficial builds > (essentially the same builds I use for testing) under http://www.mirandabanda.org/files/Cog/VM > > > HTH > > > Hi Eliot. This, this HELPS A LOT. This is awesome. Seriously. This > is really cool. Now we could start to create a Pharo one click based > on Cog. > Having the binaries will increase people using it, reporting bugs, > and submitting fixes. > > Two questions: > > 1) why "unofficial" builds? > > 2) Do these binaries include the fixes from henrik to avoid the > crash tha happens sometime? > > Thanks > > Mariano > > Eliot > > > Chris > > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

Aug. 19, 2010

Re: [Pharo-project] We want your photo

by StÃ©phane Ducasse

don't get under the charm she is a tiger :) Stef

Aug. 19, 2010

Re: [Pharo-project] FW: FW: [Seaside] Changes file too big

by StÃ©phane Ducasse

I took a 1.1 oneClickImage and did Smalltalk condenseChanges and I got no problem. So may be one of the packages you loaded got a problem. Stef On Aug 19, 2010, at 4:57 AM, Robert Sirois wrote: > > > From: watchlala(a)hotmail.com > To: watchlala(a)hotmail.com > Subject: RE: [Pharo-project] FW: [Seaside] Changes file too big > Date: Wed, 18 Aug 2010 20:56:37 -0600 > > Ok... I was running "pharo1.0-10505-rc1dev10.01.2". > > I decided to time machine back to last night, so I only lost a couple hours of work. Somehow Gofer, maybe? added tons of lines of random code to all the methods in the packages I was trying to save out via Monticello and erased all the code I had in them. > > If you need more information I can pull the image out of time machine from this morning again. > > Thanks, > RS > > How do I clear the changes or make the max bigger? I would think it would be easy. > > From: watchlala(a)hotmail.com > To: pharo-project(a)lists.gforge.inria.fr > Subject: RE: [Pharo-project] FW: [Seaside] Changes file too big > Date: Wed, 18 Aug 2010 17:22:46 -0600 > > I can't say for sure until I get home but it was the something dot 505 from a little earlier this year. > > Thanks, > RS > > Oh, also.. that condenseChanges messed up monticello, too. > > > From: stephane.ducasse(a)inria.fr > > Date: Wed, 18 Aug 2010 22:58:32 +0200 > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] FW: [Seaside] Changes file too big > > > > Oops. > > Robert can you tell us which version you are using? > > > > Stef > > > > > How do I clear my changes file? Smalltalk condenseChanges. just brings up a PositionalStream error. > > > > > > Thanks, RS > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 19, 2010

Re: [Pharo-project] HTML parser (again)

by StÃ©phane Ducasse

Yes we should do something. Now the question is how to do something that we can actually implement. I think that we should - start to identify package of interest (quality/topics////) - check their license status - check the author and get access - create an inbox Stef > > > laurent laffont wrote: >> >> Sean, could you put your package there ? >> > > The wonderful world of Squeak packages... The package I fixed is Todd > Blanchard's HTML & CSS Validating Parser at > http://www.squeaksource.com/htmlcssparser/, not the Scamper HTML from > http://www.squeaksource.com/HTML, although both packages are called "HTML." > > However, this is a lovely opportunity to repeat my call for either (or maybe > both): > * (my favorite) create an inbox for each project on SqS, just like for > Squeak and Pharo trunk, so users can choose between the bleeding edge (which > would include contributions like this one) or the last officially blessed > one; but they would all be in the same place and obvious to find. > * or, send an email to all SqS emails saying that if they don't affirm > responsibility for their project within X amount of time, the repo will be > released to the community i.e. made w/r. > > I also seem to remember a suggestion at one point to have a list of people > that were approved to commit to any repo on SqS. > > The point is, make it easy to contribute and people will. It is a downer to > go through the work of fixing packages, only to put them in my own repo > where they may never be found by users, because the repo is read-only and I > can't get in touch with the admins. > > <rant> > Also, adding oneself to each repo is RUBBISH!!!!! Even though I usually > take the time, I shudder at the thought of all the community fixes that were > kept personally or thrown away because it was a hassle to share them. I'm > sure many people, like me, just fix things that are broken. This is the > whole beauty of a live system that's turtles all the way down - my system's > menus are broken, great, I just spend 20 minutes fixing them for every user > on the planet vs. the typical X months (if ever) for an OS vendor to get > around to a fix > </rant> > > Sean > -- > View this message in context: http://forum.world.st/HTML-parser-again-tp2329387p2330466.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 19, 2010

Re: [Pharo-project] HTML parser (again)

by StÃ©phane Ducasse

The problem is how do you control because people published code that I do not like in my breakout project for example. I think that the idea of inbox and community contributors is the way to go, this is open and you can control. In any case as a community we will have to work to identify packages that are of interest. I also suggest that we put two forges in the future one call "sandbox" where students can publish their trials and exercises and one where the more consequent project are Stef On Aug 19, 2010, at 8:12 AM, laurent laffont wrote: > Yes Sean, actually SqueakSource is not really "Share Friendly". I wonder if a solution is not having only one repository for all as Monticello seems to handle branches itself. It seems INRIA will start working on this starting from sept. / oct. > > The automatic inbox is a solution too. But it doesn't mean packages will be integrated mainstream. > > I like public writable repository. > > I also wonder why SS is free for private repository, should be paying (so it can pay someone to manage / evolve SqueakSource). > > Laurent > > > On Thu, Aug 19, 2010 at 12:30 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > laurent laffont wrote: > > > > Sean, could you put your package there ? > > > > The wonderful world of Squeak packages... The package I fixed is Todd > Blanchard's HTML & CSS Validating Parser at > http://www.squeaksource.com/htmlcssparser/, not the Scamper HTML from > http://www.squeaksource.com/HTML, although both packages are called "HTML." > > However, this is a lovely opportunity to repeat my call for either (or maybe > both): > * (my favorite) create an inbox for each project on SqS, just like for > Squeak and Pharo trunk, so users can choose between the bleeding edge (which > would include contributions like this one) or the last officially blessed > one; but they would all be in the same place and obvious to find. > * or, send an email to all SqS emails saying that if they don't affirm > responsibility for their project within X amount of time, the repo will be > released to the community i.e. made w/r. > > I also seem to remember a suggestion at one point to have a list of people > that were approved to commit to any repo on SqS. > > The point is, make it easy to contribute and people will. It is a downer to > go through the work of fixing packages, only to put them in my own repo > where they may never be found by users, because the repo is read-only and I > can't get in touch with the admins. > > <rant> > Also, adding oneself to each repo is RUBBISH!!!!! Even though I usually > take the time, I shudder at the thought of all the community fixes that were > kept personally or thrown away because it was a hassle to share them. I'm > sure many people, like me, just fix things that are broken. This is the > whole beauty of a live system that's turtles all the way down - my system's > menus are broken, great, I just spend 20 minutes fixing them for every user > on the planet vs. the typical X months (if ever) for an OS vendor to get > around to a fix > </rant> > > Sean > -- > View this message in context: http://forum.world.st/HTML-parser-again-tp2329387p2330466.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 19, 2010