- Pharo-users - lists.pharo.org

Roassal2, navigate in your view with scrollbars

by Pierre CHANSON

Hi all, new version of smooth scrollbars and pads is available, it allows you to navigate with scalability in the view, check this out: https://vimeo.com/122758568 try out: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | b | b := RTMondrian new. b shape rectangle withBorder; width: [ :cls | cls numberOfVariables * 5]; height: #numberOfMethods; linearFillColor: #numberOfLinesOfCode within: RTObject withAllSubclasses. b nodes: RTObject withAllSubclasses. b edges connectFrom: #superclass. b layout tree. b build. b view @ RTDoubleScrollBar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= More examples in RTScrollBarBuilderExamples â Cheers, Pierre

March 20, 2015

Re: [Pharo-users] SystemBrowser feature request / bug report

by Sebastian Heidbrink

Thank you! Will do! Sebastian On 2015-03-20 9:51 AM, Ben Coman wrote: > Sounds reasonable. Actually perhaps the behaviour should be that > subsequent presses of the key moves to the next match. Please log an > issue at pharo.fobgugz.com <http://pharo.fobgugz.com> with your idea. > cheers -ben > > On Fri, Mar 20, 2015 at 11:15 PM, Sebastian Heidbrink > <sheidev(a)yahoo.de <mailto:sheidev@yahoo.de>> wrote: > > Hi! > > I think it is a mix of a feature and a bug. > > When ever one implements a Magritte, Moose or Morphic project the > functionality to select the package list and enter/hit key "m" > does not fast scroll down to those packages but rather selects the > "Most Viewed Classes" entry. > > I propose to catch "m" and ignore "Most Viewd Classes" for this > fast scroll/find functionality. > > Sebastian > >

March 20, 2015

Re: [Pharo-users] SystemBrowser feature request / bug report

by Ben Coman

Sounds reasonable. Actually perhaps the behaviour should be that subsequent presses of the key moves to the next match. Please log an issue at pharo.fobgugz.com with your idea. cheers -ben On Fri, Mar 20, 2015 at 11:15 PM, Sebastian Heidbrink <sheidev(a)yahoo.de> wrote: > Hi! > > I think it is a mix of a feature and a bug. > > When ever one implements a Magritte, Moose or Morphic project the > functionality to select the package list and enter/hit key "m" does not > fast scroll down to those packages but rather selects the "Most Viewed > Classes" entry. > > I propose to catch "m" and ignore "Most Viewd Classes" for this fast > scroll/find functionality. > > Sebastian >

March 20, 2015

Confusing ZeroDivide

by webwarrior

Why this: [ 1/0 ] on: ZeroDivide do: [:ex | ex resume: 1 ]. returns 1, but this: [ 1.0/0 ] on: ZeroDivide do: [:ex | ex resume: 1 ]. hangs (causes infinite loop) ? -- View this message in context: http://forum.world.st/Confusing-ZeroDivide-tp4813627.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 20, 2015

SystemBrowser feature request / bug report

by Sebastian Heidbrink

Hi! I think it is a mix of a feature and a bug. When ever one implements a Magritte, Moose or Morphic project the functionality to select the package list and enter/hit key "m" does not fast scroll down to those packages but rather selects the "Most Viewed Classes" entry. I propose to catch "m" and ignore "Most Viewd Classes" for this fast scroll/find functionality. Sebastian

March 20, 2015

Re: [Pharo-users] practices in storing users application level variables

by jtuchel＠objektfabrik.de

Giving this another thought, you may want to think about dividing between user-specific and "global" state in general. This is not so important if you don't want to persist the data, but if you do, you can store user-specific data seperately. So this is not only helpful when multiple users can use the application in parallel (web apps), but also if people use it one after the other. So make it two objects: one associated to the app, one for each user. In some cases, there may not be "global" state, everything is probably user-specific Then we're back to your initial idea ;-) Joachim Am 20.03.15 um 14:58 schrieb jtuchel(a)objektfabrik.de: > Sanjay, > > I am not a big fan of Dictionaries for these kinds of things, but if > you need "named slots" for a previously unknown list of settings, the > approach you describe is perfectly okay, IMO. > This approach can also be extended into a database or any other kind > of storage and also stands the test of web apps, in so far as you can > distribute things between an application centric (global) and > user-centric (session) objects. > > Joachim > > Am 20.03.15 um 14:14 schrieb Sanjay Minni: >> Hi >> >> What is the usual practices in storing values of variables / >> parameters the >> persist through an users usage of an application. >> >> e.g. say the user logs in and then selects a current printer, current >> company, accounting year and then moves between various application >> options >> and eventually logs out. What is a good practice of storing the values >> >> ... one way could be to keep a separate application level object with a >> dictionary for all the variables ... would that be ok or there are other >> better ways >> >> regards >> Sanjay >> >> >> >> >> >> >> ----- >> --- >> Regards, Sanjay >> -- >> View this message in context: >> http://forum.world.st/practices-in-storing-users-application-level-variable… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > > >

March 20, 2015

Re: [Pharo-users] practices in storing users application level variables

by jtuchel＠objektfabrik.de

Sanjay, I am not a big fan of Dictionaries for these kinds of things, but if you need "named slots" for a previously unknown list of settings, the approach you describe is perfectly okay, IMO. This approach can also be extended into a database or any other kind of storage and also stands the test of web apps, in so far as you can distribute things between an application centric (global) and user-centric (session) objects. Joachim Am 20.03.15 um 14:14 schrieb Sanjay Minni: > Hi > > What is the usual practices in storing values of variables / parameters the > persist through an users usage of an application. > > e.g. say the user logs in and then selects a current printer, current > company, accounting year and then moves between various application options > and eventually logs out. What is a good practice of storing the values > > ... one way could be to keep a separate application level object with a > dictionary for all the variables ... would that be ok or there are other > better ways > > regards > Sanjay > > > > > > > ----- > --- > Regards, Sanjay > -- > View this message in context: http://forum.world.st/practices-in-storing-users-application-level-variable… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

March 20, 2015

practices in storing users application level variables

by Sanjay Minni

Hi What is the usual practices in storing values of variables / parameters the persist through an users usage of an application. e.g. say the user logs in and then selects a current printer, current company, accounting year and then moves between various application options and eventually logs out. What is a good practice of storing the values ... one way could be to keep a separate application level object with a dictionary for all the variables ... would that be ok or there are other better ways regards Sanjay ----- --- Regards, Sanjay -- View this message in context: http://forum.world.st/practices-in-storing-users-application-level-variable… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 20, 2015

Re: [Pharo-users] ZeroConf: Download Specific Update

by Marcus Denker

> On 20 Mar 2015, at 13:17, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Is there a way to get e.g. #40556 specifically? > no

March 20, 2015

Re: [Pharo-users] ZeroConf: Download Specific Update

by Peter UhnÃ¡k

This? http://files.pharo.org/image/40/ Peter On Fri, Mar 20, 2015 at 1:17 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Is there a way to get e.g. #40556 specifically? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/ZeroConf-Download-Specific-Update-tp4813583.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

March 20, 2015