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

using Form

by Ricardo Jacas

Hi all, i have been trying to work with the Form class (Graphics-Display Objects), to get a base 64 "form" (a String) representing the given Form. I already now i can do the oposite, like this: Form fromBinaryStream: (Base64MimeConverter mimeDecodeToBytes: aString readStream). But i cannot find the right way to do it. Right now i am doing this: (Base64MimeConverter mimeEncode: (aForm bits readStream)). Which, surprisingly, gives me a different form. Any ideas what i am doing wrong here? -- lets reign all together

April 14, 2014

Re: [Pharo-dev] Congratulation Doru Tudor GÃ®rba!

by Sergi Reyner

Somehow this got buried amongst other mails :| Congratulations! 2014-04-14 14:54 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hello, > > (I apologize for the late reply but I was offline for a week looking after > a health/family matter) > > Thank you everyone for the kinds words. This award is a complete surprise, > and reading your messages made me realize once again the privilege I had > for all these 12 years. > > Working in a Smalltalk-inspired world is indeed inspiring. But, what makes > it a privilege is working with all of you. And, I am not saying it just for > the sake of it. > > Cheers, > Doru > > > On Thu, Apr 10, 2014 at 4:57 PM, Alexandre Bergel <alexandre.bergel(a)me.com > > wrote: > >> Dear colleges and friends, >> >> It is a great pleasure for me to send this email. >> A couple of days ago AITO officially announced that the junior prize of >> the AITO Dahl-Nygaard Prize Winners is given to Doru, Tudor GÃ®rba. The >> award will be given at the ECOOP conference, this year, in Uppsala, Sweden. >> AITO is the non-profit organization who is behind ECOOP. >> >> The prestigious Dahl-Nygaard award is given to "individuals that have >> made significant technical contributions to the field of >> Object-Orientationâ. ECOOP is the high-caliber European conference on >> object-orientation. The European version of OOPSLA. >> >> I have known Doru for year, when we were doing our PhD in Bern under the >> supervision of StÃ©phane Ducasse and Oscar Nierstrasz. Doruâs work and ideas >> have had a great impact on the Pharo and Smalltalk community. >> >> Doru is member of the Pharo board. Doru authored Glamour, GTToolKit and >> many more applications. Doru is not only a great researcher, a great >> engineer or a great speaker. He is also a great leader. Doru is the main >> architect of the Moose effort, and a great coordinator in the Moose and >> Pharo communities. Doru authored Humane Assessment, "the method for making >> software engineering decisions". >> >> Doruâs work has had a great impact on my personal work. Roassal is an >> extension of the ideas first presented in Mondrian, which was first >> authored by Doru and his student around 2005. Without Doru, Moose would not >> be as it is now. >> >> Doru, we are happy to have you with us! This international recognition >> will drag up all of us. >> >> Links: >> http://www.tudorgirba.com >> http://www.humane-assessment.com >> http://www.aito.org/Dahl-Nygaard/2014.html >> >> Big big clap! >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

April 14, 2014

Re: [Pharo-dev] 13102

by GOUBIER Thierry

Ok, I have been carrying around a fix to that for what? More than a year, in my code. It's a very simple fix. It does require agreement on the fact this is a problem and that a solution is needed, that's all :) (i.e. I see two problems: 1) collision between exactly same shortcuts at global and local level, and 2) collision between single key shortcut and start of multikey shortcut. 1), I have, it's two lines in KMDispatcher. 2) is a bit more complex). Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Tudor Girba [tudor(a)tudorgirba.com] EnvoyÃ© : lundi 14 avril 2014 15:31 Ã : Pharo Development List Objet : Re: [Pharo-dev] 13102 Hi, I agree that the behavior is not ideal, but it only occurs when you have collisions. And of course it would be great to have everything working perfectly, but at this point it is more important to release. That is why, in my book, it is more important to reduce the impact (fast) than it is to solve it properly (slow). The problem was noticed in few cases. I for one only noticed it after the global shortcuts were introduced in the image. Hence, it is very likely to achieve a good enough state with little effort by removing the shortcuts. Of course, if someone else does have a better solution, he can propose it, but it has to be concrete and doubled by the effort that comes with developing and testing it :) Doru On Mon, Apr 14, 2014 at 3:22 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr<mailto:thierry.goubier@cea.fr>> wrote: Tudor, an implementation which randomly determines which shortcut will match is a bug to me, and one worthy of being solved before release. Why wouldn't Moose alone desactivate the global shortcuts if that seems the solution? Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org<mailto:pharo-dev-bounces@lists.pharo.org>] de la part de Tudor Girba [tudor(a)tudorgirba.com<mailto:tudor@tudorgirba.com>] EnvoyÃ© : lundi 14 avril 2014 15:15 Ã : Pharo Development List Objet : Re: [Pharo-dev] 13102 Hi, Sorry for not replying before but I was offline. This issue is not to fix Keymapping at this point. The current solution was designed with intent to work in the current way. We can certainly discuss about fixing it, but the solution is not for Pharo 3. The current discussion is about disabling the global shortcuts for opening the Workspace and other tools. In the Moose image, we disable those shortcuts because with the current implementation of Keymapping having complicated global keybindings simply leads to problems (for example, we cannot use Cmd+o for anything). Do not get me wrong: Keymapping is an excellent contribution that simplified a lot an important area. My suggestion is to remove the global mappings for Pharo 3.0, and then continue to work on getting Keymappings to an even better state. Doru On Mon, Apr 14, 2014 at 2:49 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr<mailto:thierry.goubier@cea.fr>> wrote: Hi Esteban, Marcus, in that particular case, I would propose the following simple fix which could solve the first impression. - Document global shortcuts, ensure that they are single key. - Document an overload (or not) effect when your app redefines a global shortcut. - Change a bit Keymapping so that single key shortcuts match first. This would solve the immediate problem and let us time to consider a more complex solution for Pharo 4. Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org<mailto:pharo-dev-bounces@lists.pharo.org>] de la part de Esteban Lorenzano [estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>] EnvoyÃ© : lundi 14 avril 2014 14:39 Ã : Pharo Development List Objet : Re: [Pharo-dev] 13102 On 14 Apr 2014, at 14:28, Marcus Denker <marcus.denker(a)inria.fr<mailto:marcus.denker@inria.fr>> wrote: > > On 13 Apr 2014, at 11:26, Stephan Eggermont <stephan(a)stack.nl<mailto:stephan@stack.nl>> wrote: > >> Hi Marcus, >> >> I think 13102 is a showstopper. Canât explain this to new users. >> sorry, but I have to disagreeâ¦ this is an important problem, I agree. But fix that will need (AFAIK) a lot of work and probably a revamp of the keybindings in system. Alsoâ¦ this problem was (again, AFAIK) present since pharo2 and we have been able to continue working even with that annoyance. We will always have problems to fix. And we still have many *really important* problem to fix. But if we do not release even with some bugs, we will never release. "Show stopperâ IMO, is a bug that prevents the system to continue working. Explain to students an annoyance in the system is bad, but not show stopper. soâ¦ Iâm with Marcus. We can delay this fix. But I also believe this kind of problems are a âshoot in the footâ, not good for attract newcomers. Thatâs why we are suggesting that Pharo4 should centred on the tooling: we have the feeling that out tools are one (or several) step(s) behind the power that pharo has. Esteban > > The question is do we hold up the release for it? > That is: is not releasing better than releasing with this? > > How long do we stop releasing, considering that we will not find > anyone to fix it? > > Marcus > > -- www.tudorgirba.com<http://www.tudorgirba.com> "Every thing has its own flow" -- www.tudorgirba.com<http://www.tudorgirba.com> "Every thing has its own flow"

April 14, 2014

Re: [Pharo-dev] Congratulation Doru Tudor GÃ®rba!

by Tudor Girba

Hello, (I apologize for the late reply but I was offline for a week looking after a health/family matter) Thank you everyone for the kinds words. This award is a complete surprise, and reading your messages made me realize once again the privilege I had for all these 12 years. Working in a Smalltalk-inspired world is indeed inspiring. But, what makes it a privilege is working with all of you. And, I am not saying it just for the sake of it. Cheers, Doru On Thu, Apr 10, 2014 at 4:57 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Dear colleges and friends, > > It is a great pleasure for me to send this email. > A couple of days ago AITO officially announced that the junior prize of > the AITO Dahl-Nygaard Prize Winners is given to Doru, Tudor GÃ®rba. The > award will be given at the ECOOP conference, this year, in Uppsala, Sweden. > AITO is the non-profit organization who is behind ECOOP. > > The prestigious Dahl-Nygaard award is given to "individuals that have made > significant technical contributions to the field of Object-Orientationâ. > ECOOP is the high-caliber European conference on object-orientation. The > European version of OOPSLA. > > I have known Doru for year, when we were doing our PhD in Bern under the > supervision of StÃ©phane Ducasse and Oscar Nierstrasz. Doruâs work and ideas > have had a great impact on the Pharo and Smalltalk community. > > Doru is member of the Pharo board. Doru authored Glamour, GTToolKit and > many more applications. Doru is not only a great researcher, a great > engineer or a great speaker. He is also a great leader. Doru is the main > architect of the Moose effort, and a great coordinator in the Moose and > Pharo communities. Doru authored Humane Assessment, "the method for making > software engineering decisions". > > Doruâs work has had a great impact on my personal work. Roassal is an > extension of the ideas first presented in Mondrian, which was first > authored by Doru and his student around 2005. Without Doru, Moose would not > be as it is now. > > Doru, we are happy to have you with us! This international recognition > will drag up all of us. > > Links: > http://www.tudorgirba.com > http://www.humane-assessment.com > http://www.aito.org/Dahl-Nygaard/2014.html > > Big big clap! > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

April 14, 2014

Re: [Pharo-dev] 13102

by Tudor Girba

Hi, I agree that the behavior is not ideal, but it only occurs when you have collisions. And of course it would be great to have everything working perfectly, but at this point it is more important to release. That is why, in my book, it is more important to reduce the impact (fast) than it is to solve it properly (slow). The problem was noticed in few cases. I for one only noticed it after the global shortcuts were introduced in the image. Hence, it is very likely to achieve a good enough state with little effort by removing the shortcuts. Of course, if someone else does have a better solution, he can propose it, but it has to be concrete and doubled by the effort that comes with developing and testing it :) Doru On Mon, Apr 14, 2014 at 3:22 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr>wrote: > Tudor, > > an implementation which randomly determines which shortcut will match is a > bug to me, and one worthy of being solved before release. > > Why wouldn't Moose alone desactivate the global shortcuts if that seems > the solution? > > Thierry > > ------------------------------ > *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Tudor > Girba [tudor(a)tudorgirba.com] > *EnvoyÃ© :* lundi 14 avril 2014 15:15 > > *Ã :* Pharo Development List > *Objet :* Re: [Pharo-dev] 13102 > > Hi, > > Sorry for not replying before but I was offline. This issue is not to > fix Keymapping at this point. The current solution was designed with intent > to work in the current way. We can certainly discuss about fixing it, but > the solution is not for Pharo 3. > > The current discussion is about disabling the global shortcuts for > opening the Workspace and other tools. In the Moose image, we disable those > shortcuts because with the current implementation of Keymapping having > complicated global keybindings simply leads to problems (for example, we > cannot use Cmd+o for anything). Do not get me wrong: Keymapping is an > excellent contribution that simplified a lot an important area. My > suggestion is to remove the global mappings for Pharo 3.0, and then > continue to work on getting Keymappings to an even better state. > > Doru > > > On Mon, Apr 14, 2014 at 2:49 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr>wrote: > >> Hi Esteban, Marcus, >> >> in that particular case, I would propose the following simple fix which >> could solve the first impression. >> - Document global shortcuts, ensure that they are single key. >> - Document an overload (or not) effect when your app redefines a global >> shortcut. >> - Change a bit Keymapping so that single key shortcuts match first. >> >> This would solve the immediate problem and let us time to consider a more >> complex solution for Pharo 4. >> >> Thierry >> ________________________________________ >> De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Esteban >> Lorenzano [estebanlm(a)gmail.com] >> EnvoyÃ© : lundi 14 avril 2014 14:39 >> Ã : Pharo Development List >> Objet : Re: [Pharo-dev] 13102 >> >> On 14 Apr 2014, at 14:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> > >> > On 13 Apr 2014, at 11:26, Stephan Eggermont <stephan(a)stack.nl> wrote: >> > >> >> Hi Marcus, >> >> >> >> I think 13102 is a showstopper. Canât explain this to new users. >> >> >> >> sorry, but I have to disagreeâ¦ this is an important problem, I agree. >> But fix that will need (AFAIK) a lot of work and probably a revamp of the >> keybindings in system. >> Alsoâ¦ this problem was (again, AFAIK) present since pharo2 and we have >> been able to continue working even with that annoyance. >> >> We will always have problems to fix. And we still have many *really >> important* problem to fix. But if we do not release even with some bugs, we >> will never release. >> >> "Show stopperâ IMO, is a bug that prevents the system to continue >> working. Explain to students an annoyance in the system is bad, but not >> show stopper. >> >> soâ¦ Iâm with Marcus. We can delay this fix. But I also believe this kind >> of problems are a âshoot in the footâ, not good for attract newcomers. >> Thatâs why we are suggesting that Pharo4 should centred on the tooling: >> we have the feeling that out tools are one (or several) step(s) behind the >> power that pharo has. >> >> Esteban >> >> > >> > The question is do we hold up the release for it? >> > That is: is not releasing better than releasing with this? >> > >> > How long do we stop releasing, considering that we will not find >> > anyone to fix it? >> > >> > Marcus >> > >> > >> >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

April 14, 2014

Re: [Pharo-dev] 13102

by GOUBIER Thierry

Tudor, an implementation which randomly determines which shortcut will match is a bug to me, and one worthy of being solved before release. Why wouldn't Moose alone desactivate the global shortcuts if that seems the solution? Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Tudor Girba [tudor(a)tudorgirba.com] EnvoyÃ© : lundi 14 avril 2014 15:15 Ã : Pharo Development List Objet : Re: [Pharo-dev] 13102 Hi, Sorry for not replying before but I was offline. This issue is not to fix Keymapping at this point. The current solution was designed with intent to work in the current way. We can certainly discuss about fixing it, but the solution is not for Pharo 3. The current discussion is about disabling the global shortcuts for opening the Workspace and other tools. In the Moose image, we disable those shortcuts because with the current implementation of Keymapping having complicated global keybindings simply leads to problems (for example, we cannot use Cmd+o for anything). Do not get me wrong: Keymapping is an excellent contribution that simplified a lot an important area. My suggestion is to remove the global mappings for Pharo 3.0, and then continue to work on getting Keymappings to an even better state. Doru On Mon, Apr 14, 2014 at 2:49 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr<mailto:thierry.goubier@cea.fr>> wrote: Hi Esteban, Marcus, in that particular case, I would propose the following simple fix which could solve the first impression. - Document global shortcuts, ensure that they are single key. - Document an overload (or not) effect when your app redefines a global shortcut. - Change a bit Keymapping so that single key shortcuts match first. This would solve the immediate problem and let us time to consider a more complex solution for Pharo 4. Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org<mailto:pharo-dev-bounces@lists.pharo.org>] de la part de Esteban Lorenzano [estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>] EnvoyÃ© : lundi 14 avril 2014 14:39 Ã : Pharo Development List Objet : Re: [Pharo-dev] 13102 On 14 Apr 2014, at 14:28, Marcus Denker <marcus.denker(a)inria.fr<mailto:marcus.denker@inria.fr>> wrote: > > On 13 Apr 2014, at 11:26, Stephan Eggermont <stephan(a)stack.nl<mailto:stephan@stack.nl>> wrote: > >> Hi Marcus, >> >> I think 13102 is a showstopper. Canât explain this to new users. >> sorry, but I have to disagreeâ¦ this is an important problem, I agree. But fix that will need (AFAIK) a lot of work and probably a revamp of the keybindings in system. Alsoâ¦ this problem was (again, AFAIK) present since pharo2 and we have been able to continue working even with that annoyance. We will always have problems to fix. And we still have many *really important* problem to fix. But if we do not release even with some bugs, we will never release. "Show stopperâ IMO, is a bug that prevents the system to continue working. Explain to students an annoyance in the system is bad, but not show stopper. soâ¦ Iâm with Marcus. We can delay this fix. But I also believe this kind of problems are a âshoot in the footâ, not good for attract newcomers. Thatâs why we are suggesting that Pharo4 should centred on the tooling: we have the feeling that out tools are one (or several) step(s) behind the power that pharo has. Esteban > > The question is do we hold up the release for it? > That is: is not releasing better than releasing with this? > > How long do we stop releasing, considering that we will not find > anyone to fix it? > > Marcus > > -- www.tudorgirba.com<http://www.tudorgirba.com> "Every thing has its own flow"

April 14, 2014

Re: [Pharo-dev] 13102

by Tudor Girba

Hi, Sorry for not replying before but I was offline. This issue is not to fix Keymapping at this point. The current solution was designed with intent to work in the current way. We can certainly discuss about fixing it, but the solution is not for Pharo 3. The current discussion is about disabling the global shortcuts for opening the Workspace and other tools. In the Moose image, we disable those shortcuts because with the current implementation of Keymapping having complicated global keybindings simply leads to problems (for example, we cannot use Cmd+o for anything). Do not get me wrong: Keymapping is an excellent contribution that simplified a lot an important area. My suggestion is to remove the global mappings for Pharo 3.0, and then continue to work on getting Keymappings to an even better state. Doru On Mon, Apr 14, 2014 at 2:49 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr>wrote: > Hi Esteban, Marcus, > > in that particular case, I would propose the following simple fix which > could solve the first impression. > - Document global shortcuts, ensure that they are single key. > - Document an overload (or not) effect when your app redefines a global > shortcut. > - Change a bit Keymapping so that single key shortcuts match first. > > This would solve the immediate problem and let us time to consider a more > complex solution for Pharo 4. > > Thierry > ________________________________________ > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Esteban > Lorenzano [estebanlm(a)gmail.com] > EnvoyÃ© : lundi 14 avril 2014 14:39 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] 13102 > > On 14 Apr 2014, at 14:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > On 13 Apr 2014, at 11:26, Stephan Eggermont <stephan(a)stack.nl> wrote: > > > >> Hi Marcus, > >> > >> I think 13102 is a showstopper. Canât explain this to new users. > >> > > sorry, but I have to disagreeâ¦ this is an important problem, I agree. > But fix that will need (AFAIK) a lot of work and probably a revamp of the > keybindings in system. > Alsoâ¦ this problem was (again, AFAIK) present since pharo2 and we have > been able to continue working even with that annoyance. > > We will always have problems to fix. And we still have many *really > important* problem to fix. But if we do not release even with some bugs, we > will never release. > > "Show stopperâ IMO, is a bug that prevents the system to continue working. > Explain to students an annoyance in the system is bad, but not show stopper. > > soâ¦ Iâm with Marcus. We can delay this fix. But I also believe this kind > of problems are a âshoot in the footâ, not good for attract newcomers. > Thatâs why we are suggesting that Pharo4 should centred on the tooling: we > have the feeling that out tools are one (or several) step(s) behind the > power that pharo has. > > Esteban > > > > > The question is do we hold up the release for it? > > That is: is not releasing better than releasing with this? > > > > How long do we stop releasing, considering that we will not find > > anyone to fix it? > > > > Marcus > > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

April 14, 2014

Re: [Pharo-dev] 13102

by GOUBIER Thierry

Hi Esteban, Marcus, in that particular case, I would propose the following simple fix which could solve the first impression. - Document global shortcuts, ensure that they are single key. - Document an overload (or not) effect when your app redefines a global shortcut. - Change a bit Keymapping so that single key shortcuts match first. This would solve the immediate problem and let us time to consider a more complex solution for Pharo 4. Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Esteban Lorenzano [estebanlm(a)gmail.com] EnvoyÃ© : lundi 14 avril 2014 14:39 Ã : Pharo Development List Objet : Re: [Pharo-dev] 13102 On 14 Apr 2014, at 14:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 13 Apr 2014, at 11:26, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Hi Marcus, >> >> I think 13102 is a showstopper. Canât explain this to new users. >> sorry, but I have to disagreeâ¦ this is an important problem, I agree. But fix that will need (AFAIK) a lot of work and probably a revamp of the keybindings in system. Alsoâ¦ this problem was (again, AFAIK) present since pharo2 and we have been able to continue working even with that annoyance. We will always have problems to fix. And we still have many *really important* problem to fix. But if we do not release even with some bugs, we will never release. "Show stopperâ IMO, is a bug that prevents the system to continue working. Explain to students an annoyance in the system is bad, but not show stopper. soâ¦ Iâm with Marcus. We can delay this fix. But I also believe this kind of problems are a âshoot in the footâ, not good for attract newcomers. Thatâs why we are suggesting that Pharo4 should centred on the tooling: we have the feeling that out tools are one (or several) step(s) behind the power that pharo has. Esteban > > The question is do we hold up the release for it? > That is: is not releasing better than releasing with this? > > How long do we stop releasing, considering that we will not find > anyone to fix it? > > Marcus > >

April 14, 2014

Re: [Pharo-dev] 13102

by Esteban Lorenzano

On 14 Apr 2014, at 14:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 13 Apr 2014, at 11:26, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Hi Marcus, >> >> I think 13102 is a showstopper. Canât explain this to new users. >> sorry, but I have to disagreeâ¦ this is an important problem, I agree. But fix that will need (AFAIK) a lot of work and probably a revamp of the keybindings in system. Alsoâ¦ this problem was (again, AFAIK) present since pharo2 and we have been able to continue working even with that annoyance. We will always have problems to fix. And we still have many *really important* problem to fix. But if we do not release even with some bugs, we will never release. "Show stopperâ IMO, is a bug that prevents the system to continue working. Explain to students an annoyance in the system is bad, but not show stopper. soâ¦ Iâm with Marcus. We can delay this fix. But I also believe this kind of problems are a âshoot in the footâ, not good for attract newcomers. Thatâs why we are suggesting that Pharo4 should centred on the tooling: we have the feeling that out tools are one (or several) step(s) behind the power that pharo has. Esteban > > The question is do we hold up the release for it? > That is: is not releasing better than releasing with this? > > How long do we stop releasing, considering that we will not find > anyone to fix it? > > Marcus > >

April 14, 2014

Re: [Pharo-dev] 13102

by Marcus Denker

On 13 Apr 2014, at 11:26, Stephan Eggermont <stephan(a)stack.nl> wrote: > Hi Marcus, > > I think 13102 is a showstopper. Canât explain this to new users. > The question is do we hold up the release for it? That is: is not releasing better than releasing with this? How long do we stop releasing, considering that we will not find anyone to fix it? Marcus

April 14, 2014