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

Re: [Pharo-dev] Where to report bugs?

by Hilaire Fernandes

Le 29/01/2014 12:33, Marcus Denker a Ã©crit : > It has already been concluded that fogbugz was a mistake. Itâs just not made > for an open source project. > > Now moving will be *a lot* of work and we have not even found a replacement > that is scriptable. > > We first need to release Pharo3 before we sink indefinite amounts of time into this. Don't be too hard with yourselves. Once the odd aspect of fogbugz is understood, it is ok. It does the job and you don't have urgency to change, especially if it requires a lot of work. Thanks Hilaire -- Dr. Geo http://drgeo.eu

Jan. 29, 2014

Re: [Pharo-dev] Pharo Success Story: Reflex Vacances

by Sven Van Caekenberghe

Very nice ! And it is fast. Great work. Sven On 29 Jan 2014, at 13:30, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Added to the page > http://www.pharo-project.org/about/success-stories > > > Reflex Vacances > ============= > Reflex Vacances is a website to rent holiday homes all over France. > > The website lists 2000+ houses, and it runs 100% in Pharo + Iliad + MongoDB. > > "Cette plateforme regroupe des milliers d'annonces publiÃ©es par des > propriÃ©taires de toute la France, tous spÃ©cialistes de la location de > vacances. Nous l'avons dotÃ©e d'un logiciel sur mesure dÃ©veloppÃ© > pour permettre Ã la fois aux visiteurs de juger de la qualitÃ© des > annonces et aux propriÃ©taires de valoriser grÃ¢ce Ã un espace > optimisÃ© ou le logement peut-Ãªtre abondamment dÃ©crit." > > Contact http://www.objectfusion.fr for more information. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Jan. 29, 2014

Pharo Success Story: Reflex Vacances

by Marcus Denker

Hi, Added to the page http://www.pharo-project.org/about/success-stories Reflex Vacances ============= Reflex Vacances is a website to rent holiday homes all over France. The website lists 2000+ houses, and it runs 100% in Pharo + Iliad + MongoDB. "Cette plateforme regroupe des milliers d'annonces publiÃ©es par des propriÃ©taires de toute la France, tous spÃ©cialistes de la location de vacances. Nous l'avons dotÃ©e d'un logiciel sur mesure dÃ©veloppÃ© pour permettre Ã la fois aux visiteurs de juger de la qualitÃ© des annonces et aux propriÃ©taires de valoriser grÃ¢ce Ã un espace optimisÃ© ou le logement peut-Ãªtre abondamment dÃ©crit." Contact http://www.objectfusion.fr for more information.

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by kilon alios

I know I am a small fish surrounded by pharo sharks, I know that I code in pharo just for the fun of coding and you guys make a living out of it and pharo is your life but I would like to make some points and please take them with a grain of salt. a) I dont think overworking yourselves will benefit Pharo. I have to only take a look at my father whos even at the age of 70 is still a workaholic to see the negative side of things. And believe me things can seriously get bad. You health is 1000 times more important than Pharo. b) I think its a bad idea that Pharo keeps including new libraries. I dont believe there is enough manpower to maintain a large array of Pharo libraries inside the image. I fear that Pharo is going the direction of Java but you are not Oracle or Sun and we are no Java community to support you. Its my opinion there must be a discussion of cleaning the code and reducing the size and complexity of the existing libraries instead of keep adding new exciting cool features. I love Pharo but I would like to see it doing a similar clean up and reduction as Cuis. I think it will reduce your work. I am closely following your modularation efforts and the effort to make removable part of Pharo that were not removable in the past. We all want a better Pharo but its more important to have an easy to manage Pharo. c) Issue tracker wise, since you already considering moving to Git, I think that Github could make an excellent place for issue reporting. I see amber people using it to a great effect so far. And why not even bring support ( outside pharo as third party library) for bitbucket etc. On Wed, Jan 29, 2014 at 2:02 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > and I answered saying that IMO we should not change before releasing... so > not completely true that you didn't get any answer :) > > On 29 Jan 2014, at 12:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > On 29 Jan 2014, at 12:45, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > > > >> I actually proposed few replacement one month ago inside the RMoD team, > >> nobody answered except "Fogbugz is bad" , and nobody tried what I > proposed. > >> > > > > Of course this was exactly before christmas when I was really dead... I > really couldn't do > > anything anymore. I *needed* to do nothing for a week, there was no > alternative. > > > > And after all the other important things... > > > > Marcus > > >

Jan. 29, 2014

Re: [Pharo-dev] No more MouseWheelEvents?

by kilon alios

yes Nautilus also acts crazy with magic mouse gestures. Also there is weird blue rectangle that surrounds one of the packages that refuses to go away. So I have stopped using gestures at all with Nautilus and instead do manual scrolls dragging the scroll bar. On Wed, Jan 29, 2014 at 12:34 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > There is something about the wheel because often, at least in Nautilus, > you get crazy scrolls you dind't asked for > > Specially if using trackpad, two finger, scroll > > > > On Jan 29, 2014, at 6:09 AM, Hilaire Fernandes < > hilaire.fernandes(a)gmail.com> wrote: > > > I am not exactly sure, but I think mouseWheelEvents were always > > simulated with Ctrl events. > > > > > > Hilaire > > > > > > Le 29/01/2014 00:06, Nicolai Hess a Ã©crit : > >> How it comes we lost the MouseWheelEvents. > >> The SimpleHierarchicalListMorph in FileList does not scroll on > >> MouseWheelEvents. > >> Or at least it worked that way in Pharo2. But now the MouseWheel creates > >> a keyboardevent "<Ctrl->". > >> (Other ListMorphs can handle this, but the ListMorph in FileList can > not.) > >> > >> nicolai > >> > > > > > > -- > > Dr. Geo http://drgeo.eu > > > > > > >

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Esteban Lorenzano

and I answered saying that IMO we should not change before releasingâ¦ so not completely true that you didnât get any answer :) On 29 Jan 2014, at 12:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 29 Jan 2014, at 12:45, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> I actually proposed few replacement one month ago inside the RMoD team, >> nobody answered except âFogbugz is badâ , and nobody tried what I proposed. >> > > Of course this was exactly before christmas when I was really deadâ¦ I really couldnât do > anything anymore. I *needed* to do nothing for a week, there was no alternative. > > And after all the other important thingsâ¦ > > Marcus

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Goubier Thierry

Le 29/01/2014 12:49, Marcus Denker a Ã©crit : > > On 29 Jan 2014, at 12:45, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> I actually proposed few replacement one month ago inside the RMoD team, >> nobody answered except âFogbugz is badâ , and nobody tried what I proposed. >> > > Of course this was exactly before christmas when I was really deadâ¦ I really couldnât do > anything anymore. I *needed* to do nothing for a week, there was no alternative. And luckily for all of us, you weren't really dead ;) Thierry > And after all the other important thingsâ¦ > > Marcus > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Marcus Denker

On 29 Jan 2014, at 12:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 29 Jan 2014, at 12:45, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> I actually proposed few replacement one month ago inside the RMoD team, >> nobody answered except âFogbugz is badâ , and nobody tried what I proposed. >> > > Of course this was exactly before christmas when I was really deadâ¦ I really couldnât do > anything anymore. I *needed* to do nothing for a week, there was no alternative. > > And after all the other important thingsâ¦ > My point is: Yes, this is important, but there are other important things, too, that need to be done yesterday. Regardless of what we do, there will always be something that has to wait. If we switch the issue tracker now, we need to postpone the release by 3 months. Marcus

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Marcus Denker

On 29 Jan 2014, at 12:45, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > I actually proposed few replacement one month ago inside the RMoD team, > nobody answered except âFogbugz is badâ , and nobody tried what I proposed. > Of course this was exactly before christmas when I was really deadâ¦ I really couldnât do anything anymore. I *needed* to do nothing for a week, there was no alternative. And after all the other important thingsâ¦ Marcus

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Benjamin

I actually proposed few replacement one month ago inside the RMoD team, nobody answered except âFogbugz is badâ , and nobody tried what I proposed. Exactly what happened when we had to choose a replacement for Google Issue Tracker. Ben On 29 Jan 2014, at 08:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 29 Jan 2014, at 11:32, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> I hope weâre not making it harder than it should for fear to feedback >> >> > > It has already been concluded that fogbugz was a mistake. Itâs just not made > for an open source project. > > Now moving will be *a lot* of work and we have not even found a replacement > that is scriptable. > > We first need to release Pharo3 before we sink indefinite amounts of time into this. > > Marcus

Jan. 29, 2014