- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] funny TIOBE

by phil＠highoctane.be

On Fri, Mar 28, 2014 at 10:27 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > 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 > > > Don't pithy the martyrs, they actually enjoy the job. > > ----- > 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 29, 2014

Re: [Pharo-dev] Capturing stdout

by phil＠highoctane.be

On Windows, there is work to do on the VM platform sources to get the command line output to work properly. There are a set of MsgBox calls in there where one could use a nice little printf/puts. I've been looking at it but there is more than meets the eye there. Phil On Fri, Mar 28, 2014 at 10:23 PM, Max Leske <maxleske(a)gmail.com> wrote: > 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 29, 2014

Re: [Pharo-dev] Release Mode

by Tudor Girba

+1 On Sat, Mar 29, 2014 at 7:34 AM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > great mail :) > > On 28 Mar 2014, at 23:03, Nicolai Hess <nicolaihess(a)web.de> wrote: > > 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 > > > -- www.tudorgirba.com "Every thing has its own flow"

March 29, 2014

Re: [Pharo-dev] Release Mode

by Pharo4Stef

great mail :) On 28 Mar 2014, at 23:03, Nicolai Hess <nicolaihess(a)web.de> wrote: > 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 29, 2014

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

by Benjamin

On 28 Mar 2014, at 23:16, Nicolai Hess <nicolaihess(a)web.de> wrote: > Really? > > What was wrong with the old one? They look 70â :) And the B button misses a butt :) Ben

March 28, 2014

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