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

Re: [Pharo-dev] New Nautilus side bar buttons

by Nicolai Hess

Really? What was wrong with the old one? 2014-03-28 17:57 GMT+01:00 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: > Hello guys, > > since I do not really like the new buttons introduced in Nautilus, > and since the previous one were broken, I propose this new set > of buttons based on the eclipse theme. > > > Tell me what you think about it :) > Ben > >

March 28, 2014

Re: [Pharo-dev] Release Mode

by Nicolai Hess

2014-03-28 16:58 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 28 Mar 2014, at 16:53, phil(a)highoctane.be wrote: > > > The look of nautilus button isn't "ok to integrate" since there is much > more work needed to get this working properly. > > > > Now, the scrollbars in 2.0 really suck if you ask me. So, I'd vote for > that one. > > > > Welcome back to the fray. > > > > So lets revert all the updates of this week, from the problematic ones > onwards. > > But I can only work on that next week. > > Marcus > > > Please No :) I am happy about any work that is done, even if it is "some" ui enhancement, even if it is in feautre freeze phase. Because, we are a just too small community. Most work is done in developers free time. We are providing some kind of a "product" (Pharo), but it is OUR product, we are mostly "commited to ourself". So, the most important point isn't a release date, but that we are communicating, discussing, talking about that changes. Yes, of course, I know it has to be ready at some point, it won't help if we are working on a pre-release version for years:) Please let us take that changes, hoping they don't introduced new bugs and discussing now everything where we had missed to talk about. Having said that. IF YOU have the time to work on Pharo and would like to do some enhancements now, ok! But try to step back for one minute and think to yourself: are there bugs I can resolve instead? do some code review instead? look at the new or really old (maybe all those forgotten) issues on the buglist. There are plenty of things that have to be done for the release. But of course any other change may be worthwhile as well (first impressions on UI related things may count ten times more then a handfull fixed bugs). And if you really want your changes now, make this explicit on the mailing list: "hey I would include this enhancement now, because ....., would do you think?" Nicolai

March 28, 2014

Font problem identified

by Pharo4Stef

Hi guys I found the problem now I will think about the solution. https://pharo.fogbugz.com/default.asp?13149 Stef

March 28, 2014

Re: [Pharo-dev] funny TIOBE

by Sean P. DeNigris

Stephan Eggermont wrote > Well, I donât know. We keep on fixing bugs and donât get any closer to > release :) Feel like this guy?! http://upload.wikimedia.org/wikipedia/commons/4/43/Punishment_sisyph.jpg ----- Cheers, Sean -- View this message in context: http://forum.world.st/funny-TIOBE-tp4751510p4751535.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Re: [Pharo-dev] Capturing stdout

by Max Leske

Maybeâ¦ Since Pharo now has a command line handler, you could redirect stdout to the vm process? Will probably not work while the image is running I guess. But maybe it will (see for example http://serverfault.com/questions/178457/can-i-send-some-text-to-the-stdin-o…) On 28.03.2014, at 21:56, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Emilio Oca-3 wrote >> I managed to do that in Windows using... ProcessWrapper... > > As it's for a core test, I need to find a way to do it without loading > additional libraries. I could pipe the output to a tmp file if there's > nothing... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Capturing-stdout-tp4751320p4751521.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 28, 2014

Re: [Pharo-dev] funny TIOBE

by Torsten Bergmann

> Von: Pharo4Stef > > On 28 Mar 2014, at 22:00, Sean P. DeNigris wrote: > > > Pavel Krivanek-3 wrote > >> after a very long time I checked the TIOBE index and Smalltalk is not > >> listed there at all... :-) > > > > Maybe we died and don't know it... must be heaven, not hot enough for the > > other place ;) > > :) > <quote_from_tiobe_FAQ> Q: I would like to have the complete data set of the TIOBE index. Is this possible? A: We spent a lot of effort to obtain all the data and keep the TIOBE index up to date. In order to compensate a bit for this, we ask a fee of 5,000 US$ for the complete data set. </quote_from_tiobe_FAQ> I'm sure you paid them more than 5000 bucks to remove it from the data set so Smalltalk can still be kept as a secret... And I guess this is already known: http://astares.blogspot.de/2006/07/stupid-metrics.html Bye T.

March 28, 2014

Re: [Pharo-dev] VistaCursors are killing my LinuxVM (beCursor primitive failing)

by Nicolai Hess

Yes we have this issue: 12960 <https://pharo.fogbugz.com/default.asp?12960> Primitive 101 (Cursor beCursor) fails on Ubuntu we just need someone who can edit the pharo vm build config. 2014-03-28 18:52 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > I moved a windows image with VistaCursors to Linux and the beCursor > primitive failed, leading to a white screen opening. > > Maybe this is because the cursors are bigger than the 16x16 form. > > I saw discussions of this being fixed in Squeak. Are we having this issue > in Pharo? > > Phil >

March 28, 2014

Re: [Pharo-dev] funny TIOBE

by Stephan Eggermont

Sean wrote: >Maybe we died and don't know it... must be heaven, not hot enough for the other place ;) Well, I donât know. We keep on fixing bugs and donât get any closer to release :) Stephan

March 28, 2014

Re: [Pharo-dev] Every class should redefine printOn:

by Pharo4Stef

On 28 Mar 2014, at 22:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I am all for that, but I don't think you can make it that strict, what if there are no instance variables ? ok :) a smart rule > I like custom #printOn:'s especially for debugging. > > On 28 Mar 2014, at 21:45, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> Hi guys >> >> Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying >> because Iâm trying to learn the implementation and it does not help me at all. >> >> I hate the classes that only their implementors understand. >> In Pharo 4.0 I will put a strict rule: >> - no class will be integrated if they do not redefine printOn: >> - I will set a general rules to check printOn: methods. >> >> printOn: methods are the first debugging information. >> >> Stef > >

March 28, 2014

Re: [Pharo-dev] Every class should redefine printOn:

by Sven Van Caekenberghe

I am all for that, but I don't think you can make it that strict, what if there are no instance variables ? I like custom #printOn:'s especially for debugging. On 28 Mar 2014, at 21:45, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Hi guys > > Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying > because Iâm trying to learn the implementation and it does not help me at all. > > I hate the classes that only their implementors understand. > In Pharo 4.0 I will put a strict rule: > - no class will be integrated if they do not redefine printOn: > - I will set a general rules to check printOn: methods. > > printOn: methods are the first debugging information. > > Stef

March 28, 2014