January 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] unplanned outage: http://ss3.gemstone.com/ and http://seaside.gemtalksystems.com/ss

by Dale Henrichs

The datacenter network came back on-line about a 1/2 hour ago ... Dale On 1/18/16 3:10 PM, Dale Henrichs wrote: > The datacenter where the sites http://ss3.gemstone.com/ and > http://seaside.gemtalksystems.com/ss are hosted lost their primary > router, while the backup router was being repaired ... the machines > hosting the two sites are up and running, so no data loss is expected. > > They are working on getting another router in=place, but no ETA is > known at this time ... > > Dale

Jan. 19, 2016

Re: [Pharo-users] unplanned outage: http://ss3.gemstone.com/ and http://seaside.gemtalksystems.com/ss

by Stephan Eggermont

On 19/01/16 00:10, Dale Henrichs wrote: > The datacenter where the sites http://ss3.gemstone.com/ and > http://seaside.gemtalksystems.com/ss are hosted lost their primary > router, while the backup router was being repaired ... the machines > hosting the two sites are up and running, so no data loss is expected. > > They are working on getting another router in=place, but no ETA is known > at this time ... Looks up from here (Netherlands) now. Thanks for the notification Stephan

Jan. 19, 2016

Re: [Pharo-users] unplanned outage: http://ss3.gemstone.com/ and http://seaside.gemtalksystems.com/ss

by Mariano Martinez Peck

Hi Dale, Thanks for letting me know. Could you please ping me once it is back again? Thanks! On Mon, Jan 18, 2016 at 8:10 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > The datacenter where the sites http://ss3.gemstone.com/ and > http://seaside.gemtalksystems.com/ss are hosted lost their primary > router, while the backup router was being repaired ... the machines hosting > the two sites are up and running, so no data loss is expected. > > They are working on getting another router in=place, but no ETA is known > at this time ... > > Dale > > -- Mariano http://marianopeck.wordpress.com

Jan. 19, 2016

unplanned outage: http://ss3.gemstone.com/ and http://seaside.gemtalksystems.com/ss

by Dale Henrichs

The datacenter where the sites http://ss3.gemstone.com/ and http://seaside.gemtalksystems.com/ss are hosted lost their primary router, while the backup router was being repaired ... the machines hosting the two sites are up and running, so no data loss is expected. They are working on getting another router in=place, but no ETA is known at this time ... Dale

Jan. 18, 2016

a new version of gtdebugger

by Tudor Girba

Hi, A new version of GTDebugger was just integrated. Several issues were addressed. Some more notable things are: - the stack shows columns for class, method, other info - there are new keybindings in place that do not collide with the text editor - the accept/cancel buttons are in the contextual menu at least for Pharo 5 - the variables pane received a label There are still some things todos left like: - the columns in the stack should be resizable - thisContext, stackTop - perhaps make the key bindings controllable through settings We kindly invite everyone to test it and provide feedback. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Jan. 18, 2016

Re: [Pharo-users] Fogbuz issues

by Ben Coman

I've found this one useful, when I've been browsing and am looking for something I saw but can't exactly remember. All cases viewed by me sorted by Last viewed by me (reversed) On Tue, Jan 19, 2016 at 5:19 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > * you can easily review configuration of all filters and their exact meaning > here https://pharo.fogbugz.com/default.asp?pg=pgManageFilters > * FogzBugz offers a rich ad-hoc filtering capability, so if you wan't > something specific, it's easy to get. > * any complex tool will be usually confusing to newcomers; if you've lived > in a small town your whole life and go to a metropolis you will be > overwhelmed, even though the metropolis is probably more ordered and > systematic than the town > > Finally, I've added the filter specifically to filter cases in which I am > somehow involved â e.g. I was going through random issues and when I > couldn't replicate the issue, or it was already resolved, etc. I commented > on it and requested confirmation/more info from the original poster, then I > wanted to get back to the issues later. Or simply I participated in a > resolution of an issue as a second pair of eyes. > > In any case, I've renamed it to "Cases I am Involved In". Hopefully that > will be more self-explanatory. > > Peter > > On Sun, Jan 17, 2016 at 6:04 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: >> >> ah ok did not know that is a common practice for pro devs , well if fogbuz >> is a pro approved tool and it works very well I am perfectly ok with using >> it and documenting it for newcomers. >> >> On Sun, Jan 17, 2016 at 4:40 PM Ben Coman <btc(a)openinworld.com> wrote: >>> >>> On Sun, Jan 17, 2016 at 7:06 PM, Dimitris Chloupis >>> <kilon.alios(a)gmail.com> wrote: >>> > You can indeed interpret My Cases as "assigned to me" but my first >>> > thought >>> > was when I saw "My Cases" is to assume that is the cases i opened. >>> > >>> > In any case I created my own custom filter with openedBy:me and saved >>> > it as >>> > "My Opened Cases" and I also used the Henrik suggestion to subscribe to >>> > all >>> > relevant opened and closed case I am interested for. So hopefully this >>> > is >>> > the end of my frustration though I am sure I will find something to >>> > complain >>> > about :D >>> > >>> > So yes fogbuz is not that bad once you figure out how it works, but is >>> > confusing for newcomers to say the least. >>> >>> This impedance mismatch is because its a professional tool designed >>> for commercial in-house bug tracking, where users have no access to >>> it. So the "my" is "my cases" is always a developer working on >>> someone else's bug. In our case there is little distinction between >>> our users and our developers. For this reason, Fogbugz doesn't always >>> exactly match our needs, but I think it is sufficient, and we are >>> lucky to have the free access to it that we have. It would be a big >>> job moving, which we should delay as long as reasonably possible. >>> >>> cheers -ben >>> >>> > >>> > On Sun, Jan 17, 2016 at 1:01 PM Nicolai Hess <nicolaihess(a)gmail.com> >>> > wrote: >>> >> >>> >> >>> >> 2016-01-17 11:43 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >>> >>> >>> >>> Ok let me explain >>> >>> >>> >>> if you go to My Cases it has already setup a filter for you that >>> >>> shows >>> >>> issues assigned to you, the problem is that when you open a bug >>> >>> report it is >>> >>> not assigned to you, it actually assigned to our lovely victim , >>> >>> Esteban and >>> >>> anyone else that cares to set the report assigned to him so even if >>> >>> you add >>> >>> additional filter like opened by you or edited by you it will show >>> >>> you zero >>> >>> result if you have not been assigned any of those issues which will >>> >>> be the >>> >>> case. >>> >> >>> >> >>> >> Yes it is confusing but not wrong. You can interpret "My Cases" as >>> >> "assigned to me". >>> >> >>> >>> >>> >>> >>> >>> Instead you need to change the existing filter to assigned to >>> >>> Everybody >>> >>> so it included all bug reports and then you can add the filters you >>> >>> mentioned and yes then it will work. >>> >> >>> >> >>> >> You can define you own filters, like >>> >> openedBy:me status:open >>> >> >>> >>> >>> >>> >>> >>> On Sun, Jan 17, 2016 at 12:39 PM Nicolai Hess <nicolaihess(a)gmail.com> >>> >>> wrote: >>> >>>> >>> >>>> 2016-01-17 11:32 GMT+01:00 Dimitris Chloupis >>> >>>> <kilon.alios(a)gmail.com>: >>> >>>>> >>> >>>>> Or the alternative is just go down, down , down the list to My Open >>> >>>>> Cases. Which by the way it does not just show the cases opened by >>> >>>>> you but >>> >>>>> also cases you have commented on >>> >>>> >>> >>>> >>> >>>> >>> >>>> Yes, that is why I showed you the filter >>> >>>> editedBy:theKilon >>> >>>> instead of >>> >>>> alsoEditedBy: >>> >>>> >>> >>>> >>> >>>>> >>> >>>>> >>> >>>>> Welcome to the land of endless WTF :D >>> >>>>> >>> >>>>> And by the way your solution does not work either because there is >>> >>>>> a >>> >>>>> catch , you have to change assigned to Everybody >>> >>>> >>> >>>> >>> >>>> I don't understand this one. >>> >>>> >>> >>>> >>> >>>>> >>> >>>>> >>> >>>>> so lets all sing >>> >>>>> >>> >>>>> WTF dancing in the rain >>> >>>>> WTF dancing in the rain .... >>> >>>>> >>> >>>>> On Sun, Jan 17, 2016 at 12:25 PM Nicolai Hess >>> >>>>> <nicolaihess(a)gmail.com> >>> >>>>> wrote: >>> >>>>>> >>> >>>>>> 2016-01-17 11:00 GMT+01:00 Dimitris Chloupis >>> >>>>>> <kilon.alios(a)gmail.com>: >>> >>>>>>> >>> >>>>>>> Since I am on a complaining spree lately let me complain once >>> >>>>>>> more. >>> >>>>>>> >>> >>>>>>> I really dont like Fogbuz and in order not to bore with blah blah >>> >>>>>>> lets get to 2 big issues >>> >>>>>>> >>> >>>>>>> 1) If you open a bug report it does not subscribe you to it, WTF >>> >>>>>>> !!! >>> >>>>>>> Who else could be more interested in my bug report than I ? >>> >>>>>>> >>> >>>>>>> 2) If I go to My Cases its shows none of the reports I opened , >>> >>>>>>> actually it shows nothing, none, zero , empty space WTF^2 >>> >>>>>> >>> >>>>>> >>> >>>>>> Yes this is confusing, "My Cases" only shows issues "assigned to >>> >>>>>> you". >>> >>>>>> >>> >>>>>> Instaed, you can filter all cases by >>> >>>>>> >>> >>>>>> editedBy:theKilon >>> >>>>>> or >>> >>>>>> openedBy:theKilon >>> >>>>>> >>> >>>>>> >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> And people then wonder why on earth I keep pushing for github >>> >>>>>>> integration, thats why ! >>> >

Jan. 18, 2016

Re: [Pharo-users] Fogbuz issues

by Peter UhnÃ¡k

* you can easily review configuration of all filters and their exact meaning here https://pharo.fogbugz.com/default.asp?pg=pgManageFilters * FogzBugz offers a rich ad-hoc filtering capability, so if you wan't something specific, it's easy to get. * any complex tool will be usually confusing to newcomers; if you've lived in a small town your whole life and go to a metropolis you will be overwhelmed, even though the metropolis is probably more ordered and systematic than the town Finally, I've added the filter specifically to filter cases in which I am somehow involved â e.g. I was going through random issues and when I couldn't replicate the issue, or it was already resolved, etc. I commented on it and requested confirmation/more info from the original poster, then I wanted to get back to the issues later. Or simply I participated in a resolution of an issue as a second pair of eyes. In any case, I've renamed it to "Cases I am Involved In". Hopefully that will be more self-explanatory. Peter On Sun, Jan 17, 2016 at 6:04 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > ah ok did not know that is a common practice for pro devs , well if fogbuz > is a pro approved tool and it works very well I am perfectly ok with using > it and documenting it for newcomers. > > On Sun, Jan 17, 2016 at 4:40 PM Ben Coman <btc(a)openinworld.com> wrote: > >> On Sun, Jan 17, 2016 at 7:06 PM, Dimitris Chloupis >> <kilon.alios(a)gmail.com> wrote: >> > You can indeed interpret My Cases as "assigned to me" but my first >> thought >> > was when I saw "My Cases" is to assume that is the cases i opened. >> > >> > In any case I created my own custom filter with openedBy:me and saved >> it as >> > "My Opened Cases" and I also used the Henrik suggestion to subscribe to >> all >> > relevant opened and closed case I am interested for. So hopefully this >> is >> > the end of my frustration though I am sure I will find something to >> complain >> > about :D >> > >> > So yes fogbuz is not that bad once you figure out how it works, but is >> > confusing for newcomers to say the least. >> >> This impedance mismatch is because its a professional tool designed >> for commercial in-house bug tracking, where users have no access to >> it. So the "my" is "my cases" is always a developer working on >> someone else's bug. In our case there is little distinction between >> our users and our developers. For this reason, Fogbugz doesn't always >> exactly match our needs, but I think it is sufficient, and we are >> lucky to have the free access to it that we have. It would be a big >> job moving, which we should delay as long as reasonably possible. >> >> cheers -ben >> >> > >> > On Sun, Jan 17, 2016 at 1:01 PM Nicolai Hess <nicolaihess(a)gmail.com> >> wrote: >> >> >> >> >> >> 2016-01-17 11:43 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >> >>> >> >>> Ok let me explain >> >>> >> >>> if you go to My Cases it has already setup a filter for you that shows >> >>> issues assigned to you, the problem is that when you open a bug >> report it is >> >>> not assigned to you, it actually assigned to our lovely victim , >> Esteban and >> >>> anyone else that cares to set the report assigned to him so even if >> you add >> >>> additional filter like opened by you or edited by you it will show >> you zero >> >>> result if you have not been assigned any of those issues which will >> be the >> >>> case. >> >> >> >> >> >> Yes it is confusing but not wrong. You can interpret "My Cases" as >> >> "assigned to me". >> >> >> >>> >> >>> >> >>> Instead you need to change the existing filter to assigned to >> Everybody >> >>> so it included all bug reports and then you can add the filters you >> >>> mentioned and yes then it will work. >> >> >> >> >> >> You can define you own filters, like >> >> openedBy:me status:open >> >> >> >>> >> >>> >> >>> On Sun, Jan 17, 2016 at 12:39 PM Nicolai Hess <nicolaihess(a)gmail.com> >> >>> wrote: >> >>>> >> >>>> 2016-01-17 11:32 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com >> >: >> >>>>> >> >>>>> Or the alternative is just go down, down , down the list to My Open >> >>>>> Cases. Which by the way it does not just show the cases opened by >> you but >> >>>>> also cases you have commented on >> >>>> >> >>>> >> >>>> >> >>>> Yes, that is why I showed you the filter >> >>>> editedBy:theKilon >> >>>> instead of >> >>>> alsoEditedBy: >> >>>> >> >>>> >> >>>>> >> >>>>> >> >>>>> Welcome to the land of endless WTF :D >> >>>>> >> >>>>> And by the way your solution does not work either because there is a >> >>>>> catch , you have to change assigned to Everybody >> >>>> >> >>>> >> >>>> I don't understand this one. >> >>>> >> >>>> >> >>>>> >> >>>>> >> >>>>> so lets all sing >> >>>>> >> >>>>> WTF dancing in the rain >> >>>>> WTF dancing in the rain .... >> >>>>> >> >>>>> On Sun, Jan 17, 2016 at 12:25 PM Nicolai Hess < >> nicolaihess(a)gmail.com> >> >>>>> wrote: >> >>>>>> >> >>>>>> 2016-01-17 11:00 GMT+01:00 Dimitris Chloupis < >> kilon.alios(a)gmail.com>: >> >>>>>>> >> >>>>>>> Since I am on a complaining spree lately let me complain once >> more. >> >>>>>>> >> >>>>>>> I really dont like Fogbuz and in order not to bore with blah blah >> >>>>>>> lets get to 2 big issues >> >>>>>>> >> >>>>>>> 1) If you open a bug report it does not subscribe you to it, WTF >> !!! >> >>>>>>> Who else could be more interested in my bug report than I ? >> >>>>>>> >> >>>>>>> 2) If I go to My Cases its shows none of the reports I opened , >> >>>>>>> actually it shows nothing, none, zero , empty space WTF^2 >> >>>>>> >> >>>>>> >> >>>>>> Yes this is confusing, "My Cases" only shows issues "assigned to >> you". >> >>>>>> >> >>>>>> Instaed, you can filter all cases by >> >>>>>> >> >>>>>> editedBy:theKilon >> >>>>>> or >> >>>>>> openedBy:theKilon >> >>>>>> >> >>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> And people then wonder why on earth I keep pushing for github >> >>>>>>> integration, thats why ! >> >>

Jan. 18, 2016

Re: [Pharo-users] Updated Pharo by Example

by stepharo

Jan. 18, 2016

Re: [Pharo-users] Creation form from PNG file very slow on Pharo 4 and 5

by stepharo

Pay attention the JPEG reader is getting old and does not support latest version. Stef Le 17/1/16 21:17, Tudor Girba a Ã©crit : > Hi, > >> On Jan 17, 2016, at 8:27 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 17 Jan 2016, at 19:58, Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>> On 16-01-16 13:50, Dimitris Chloupis wrote: >>>> Seems that creating forms and morph from pngs is super slow >>> Put the forms in one fuel file and materialize that >>> >>> Stephan >> That is exactly what I showed him in https://pharo.fogbugz.com/f/cases/17403/Creating-Forms-from-PNGs-is-very-sl… > That is actually a very cool idea. Thank you both :) > > Doru > >> The speedup was massive and it was so easy to do. >> >> But the fact remains that the PNG parser itself, being written in pure Pharo, could use a Plugin counterpart, like in the JPG case. >> >> Sven > -- > www.tudorgirba.com > www.feenk.com > > "Sometimes the best solution is not the best solution." > > >

Jan. 18, 2016

Re: [Pharo-users] Generating a binary package like PharoLauncher

by Serge Stinckwich

On Mon, Jan 18, 2016 at 6:31 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > If it exists, please check the windows installer of Pharo-Launcher, it > complains about an integrity check failure. :) > > If you can access the scrips, this is the CI for it: > https://ci.inria.fr/pharo/view/Launcher/job/Launcher/ Yes, I have access to the CI, but I could not find the scripts. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 18, 2016