- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Playground

by phil＠highoctane.be

Solution is more engineers. You are not targeted as a person, nor do I expect you to solve this in any way. And you are astounding in how much work you tackle. It is a systemic issue, this is just a symptom. Phil On Fri, Oct 3, 2014 at 1:12 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 03 Oct 2014, at 13:03, phil(a)highoctane.be wrote: > > > I just tell you what the feeling is. This has happened for a lot of what > I reported. > > > > And what is the solution? I fixed *HUNDRETS* of issues. > > maybe I should stop. > > > Do not mistake me, Pharo is usable and I haven't been encountering > blocking issues in 3.0. > > > > yes, maybe this is because some idiot (me) is going through *THOUSANDS* of > reports of problems, > tries to recreate them, fixes those he canâ¦ and close those where I can do > nothing so I can focus on the > others. > > Alternatively, I can just let all the issue tracker entries open. Will > that lead to a system that is as stable? > > Marcus > >

Oct. 3, 2014

Re: [Pharo-dev] "Browser" on a single class

by Nicolai Hess

Am 03.10.2014 12:34 schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com>: > > Hi. > > I want to make something like a browser on a single class. I.e. just use 2 last lists out if 4 in standard browser. > > Is there already something like that? If not, should I use existing widgets, or implement my own using spec? > > Cheers! > Uko > > Sent from my iPhone I think that is pretty easy with some spec models. Maybe there is already an example. Hilaire asked for a simple Method editor and i wrote a simple example build with DynamicComposableModel, search the Mailingliste.

Oct. 3, 2014

Re: [Pharo-dev] Playground

by Sven Van Caekenberghe

Everybody, please remember that Pharo is an open-source project. People contribute because they want to, not because they have to. This also means that users cannot demand something, they can only ask. I think it is also natural that users make their own customisations and their own selections of which version of Pharo they are using combined with certain packages. You would be surprised at the silent (majority of) users out there, doing their own thing. That being said, 'it is your Pharo' ... Sven On 03 Oct 2014, at 13:03, phil(a)highoctane.be wrote: > I just tell you what the feeling is. This has happened for a lot of what I reported. > > Do not mistake me, Pharo is usable and I haven't been encountering blocking issues in 3.0. > > Phil > > > > On Fri, Oct 3, 2014 at 12:46 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 03 Oct 2014, at 12:21, phil(a)highoctane.be wrote: > >> Frankly, I see fogbugz issues closed with some ignore/cannot reproduce status, so, I am not creating any of them anymore. Why bother, except for blocking bugs? >> > Tell me: What is the difference between a bug that it fixed and one that can not be reproduced? > >> I have a set of adjustments on my side and work with them. >> >> https://gist.github.com/philippeback is where I store them, an in HOExtras in my SmalltalkHub account. >> >> Sad attitude, but I tell you how it is for me. >> > > I think I should take the same attitude. I will just fix stuff for me from now on. > > Marcus > >

Oct. 3, 2014

Re: [Pharo-dev] Playground

by phil＠highoctane.be

One that cannot be reproduced right off the bat is one which is more complex than meets the eye. Heisenbugs? Still, bugs. Easy to say, of course. Now, maybe putting things as "closed" when you cannot reproduce is not okay with me. I understand the scale of the issues list and that you do your best. And, as much I do want to help the community, I first want to help me first in delivering projects for clients. That is what will help in putting money back in the community after all. I can live with the current state of things, no issue (pun intended). Phil On Fri, Oct 3, 2014 at 12:52 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 03 Oct 2014, at 12:46, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 03 Oct 2014, at 12:21, phil(a)highoctane.be wrote: > > Frankly, I see fogbugz issues closed with some ignore/cannot reproduce > status, so, I am not creating any of them anymore. Why bother, except for > blocking bugs? > > Tell me: What is the difference between a bug that it fixed and one that > can not be reproduced? > > > I wonder if people have an idea of the scale of thingsâ¦ > > - We closed 107 issues the last 7 days > - there are 618 open issues > - There where 11268 issues reported for Pharo since we started. > > So when I look at an issue i try to reproduce it. If I can not, I close > it. Else this is not possible to do, sorry. Even if I wanted to: If we keep > all non-reproducible cases open we soon will be paralysed. (And that by > issues that to 99% are fixed). > > Marcus > >

Oct. 3, 2014

Re: [Pharo-dev] Playground

by Marcus Denker

On 03 Oct 2014, at 13:03, phil(a)highoctane.be wrote: > I just tell you what the feeling is. This has happened for a lot of what I reported. > And what is the solution? I fixed *HUNDRETS* of issues. maybe I should stop. > Do not mistake me, Pharo is usable and I haven't been encountering blocking issues in 3.0. > yes, maybe this is because some idiot (me) is going through *THOUSANDS* of reports of problems, tries to recreate them, fixes those he canâ¦ and close those where I can do nothing so I can focus on the others. Alternatively, I can just let all the issue tracker entries open. Will that lead to a system that is as stable? Marcus

Oct. 3, 2014

Re: [Pharo-dev] Playground

by phil＠highoctane.be

I just tell you what the feeling is. This has happened for a lot of what I reported. Do not mistake me, Pharo is usable and I haven't been encountering blocking issues in 3.0. Phil On Fri, Oct 3, 2014 at 12:46 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 03 Oct 2014, at 12:21, phil(a)highoctane.be wrote: > > Frankly, I see fogbugz issues closed with some ignore/cannot reproduce > status, so, I am not creating any of them anymore. Why bother, except for > blocking bugs? > > Tell me: What is the difference between a bug that it fixed and one that > can not be reproduced? > > I have a set of adjustments on my side and work with them. > > https://gist.github.com/philippeback is where I store them, an in > HOExtras in my SmalltalkHub account. > > Sad attitude, but I tell you how it is for me. > > > I think I should take the same attitude. I will just fix stuff for me from > now on. > > Marcus > >

Oct. 3, 2014

Re: [Pharo-dev] "Browser" on a single class

by Camille Teruel

On 3 oct. 2014, at 12:34, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi. > > I want to make something like a browser on a single class. I.e. just use 2 last lists out if 4 in standard browser. > > Is there already something like that? If not, should I use existing widgets, or implement my own using spec? > You can parametrize Nautilus with a RBBrowserEnvironment if that fits your needs: Nautilus openInEnvironment: (RBClassEnvironment class: YourClass) Camille > Cheers! > Uko > > Sent from my iPhone

Oct. 3, 2014

Re: [Pharo-dev] Playground

by Marcus Denker

On 03 Oct 2014, at 12:46, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 03 Oct 2014, at 12:21, phil(a)highoctane.be wrote: > >> Frankly, I see fogbugz issues closed with some ignore/cannot reproduce status, so, I am not creating any of them anymore. Why bother, except for blocking bugs? >> > Tell me: What is the difference between a bug that it fixed and one that can not be reproduced? I wonder if people have an idea of the scale of thingsâ¦ - We closed 107 issues the last 7 days - there are 618 open issues - There where 11268 issues reported for Pharo since we started. So when I look at an issue i try to reproduce it. If I can not, I close it. Else this is not possible to do, sorry. Even if I wanted to: If we keep all non-reproducible cases open we soon will be paralysed. (And that by issues that to 99% are fixed). Marcus

Oct. 3, 2014

Re: [Pharo-dev] Playground

by Marcus Denker

On 03 Oct 2014, at 12:21, phil(a)highoctane.be wrote: > Frankly, I see fogbugz issues closed with some ignore/cannot reproduce status, so, I am not creating any of them anymore. Why bother, except for blocking bugs? > Tell me: What is the difference between a bug that it fixed and one that can not be reproduced? > I have a set of adjustments on my side and work with them. > > https://gist.github.com/philippeback is where I store them, an in HOExtras in my SmalltalkHub account. > > Sad attitude, but I tell you how it is for me. > I think I should take the same attitude. I will just fix stuff for me from now on. Marcus

Oct. 3, 2014

Re: [Pharo-dev] "Browser" on a single class

by Esteban Lorenzano

If just in a class, it will be a lot simpler doing it with glamour, I think > On 3 Oct 2014, at 12:34, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi. > > I want to make something like a browser on a single class. I.e. just use 2 last lists out if 4 in standard browser. > > Is there already something like that? If not, should I use existing widgets, or implement my own using spec? > > Cheers! > Uko > > Sent from my iPhone

Oct. 3, 2014