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

[Pharo-project] Context reflection regression?
by Igor Stasenko April 11, 2010

April 11, 2010

I just found that a: a b: b c: c ^ thisContext sender stackPtr answers 0 :( while, in order to call the above method , a caller, obviously needs to push 4 values on stack: - push receiver - push a - push b - push c - send #a:b:c: so, a method's caller context stack _should_ contain at least 4 elements. So, either i wrong, or VM doesn't tracking the context's sp value correctly anymore. -- Best regards, Igor Stasenko AKA sig.

2 2

[Pharo-project] [update 1.1] #11311
by StÃ©phane Ducasse April 11, 2010

April 11, 2010

11311 ----- - Issue 1842: Make the System -> Software update a preference for 1.1. Thanks alain. - Issue 991: Polymorph text entry dialog is ugly . Thanks alain - Issue 2287: Menu Selection Color. Thanks gary.

1 0

Re: [Pharo-project] [squeak-dev] Re: SqueakSource is unusable
by Igor Stasenko April 11, 2010

April 11, 2010

On 11 April 2010 00:18, stephane ducasse <stephane.ducasse(a)gmail.com> wrote: > thanks. My thanks too. It is just GREAT improvement! Keep moving guys! :) -- Best regards, Igor Stasenko AKA sig.

1 0

Re: [Pharo-project] [squeak-dev] Re: SqueakSource is unusable
by Bert Freudenberg April 11, 2010

April 11, 2010

On 10.04.2010, at 21:19, stephane ducasse wrote: > > > On Apr 10, 2010, at 7:16 PM, Bert Freudenberg wrote: > >> Thanks. >> >> I just merged the stuff I developed lately > > which is? Most importantly, projects can have parent projects now (only if a site-wide setting is enabled). This is to support "inbox" style use - when mailing out diffs, the diff based is searched in a project's parent project too. Also, you can enable developers to move versions, not just admins. This is a per-project setting, again to enable developers to clean out an "inbox" repository. There can also be a default target project for moves. Since SSProject grew too many instance variables, I added a properties dictionary just like we have for versions and repositories. Refactoring might be in order but I just copied and pasted. Sorry ;) There are a few minor changes, see the version history :) - Bert -

2 1

[Pharo-project] SqueakSource is unusable
by jaayer April 10, 2010

April 10, 2010

or if not that, then nearly so. The biggest problem is the overall smallness of each page. The site is far too narrow and apparently was designed for monitors with 800x600 screen resolutions. This was unacceptable five years ago and is even more unacceptable now. Further, the fonts are tiny, and worse, they and almost every other sized property are specified using hard-coded pixel widths. For scalable, cross-platform design, percentages and em-widths should be preferred. Links should display some sort of text-decoration when moused-over so it is always clear which link will be selected when the user clicks, even when two or more links are especially close together. SqueakSource is, after the primary home pages, the public face of the Squeak and Pharo projects. It is crucial then that it look--if not great--at least decent. Enclosed is prettified CSS that fixes some of these defects. (Note that Image url() references need to be filled in, and it still probably needs some tweaking.) body { border:0; background:gray; text-align:center; margin:0; padding:10px; font-size:0.9em; } body,div,table,tr,td,th,form input,form submit { font-family:Geneva, Arial, Helvetica, sans-serif; } table,tr,td,th,form { border:0; margin:0; padding:0; } th { text-align:left; } a,a:visited { color:#360484; text-decoration:none; } a:hover,a:active { text-decoration:underline; } #container { width:90%; background:white url(/inserturl) repeat-y 4%; border:1px solid black; border-top:5px solid black; border-bottom:5px solid black; text-align:left; margin:auto; } #top { width:100%; height:50px; background:url(/inserturl) no-repeat; border-bottom:1px solid black; font-size:0.7em; text-align:right; } #sstoolbar { height:2em; border-bottom:1px solid black; background:white; } #sstoolbar a { display:block; float:left; margin-left:-1px; border-left:1px solid black; border-right:1px solid black; line-height:2em; height:2em; letter-spacing:1px; text-decoration:none; padding:0px 10px; } #sstoolbar a:hover,#sstoolbar a:active { background-color:#360484; color:white; text-decoration: none; } #page { padding:0; } #page td,#page th { padding-right:5px; vertical-align:top; } #navigation { float:left; width:12%; padding:0 10px 10px 10px; } #navigation .title { margin-top:11px; font-weight:bold; } #contents { width:70%; height:auto; text-align:justify; margin:0 0 0 16%; padding:5px 10px 10px; } #contents h1 { margin-top:0; font-size:20px; } #contents h2 { margin-bottom:5px; font-size:15px; } #contents h3 { margin-bottom:5px; font-size:13px; } #contents hr { border:none; border-bottom:1px dotted black; } #contents p { width:90%; } #bottom { padding-left:5px; padding-right:5px; clear:both; border-top:1px solid black; background:white; margin:0; } .TabSelected { background-color:#360484; color:white; width:95px; text-align:center; } .TabUnselected { background-color:#D0C4E2; width:95px; text-align:center; } .TabSpacer { width:5px; } .TabLine { background-color:#360484; } #batch { text-align:center; margin-top:8px; } .evenRow { background-color:#E7E1F0; } .largeLabel { width:120px; } .mediumLabel { width:100px; } .smallLabel { width:80px; } .activityTable { margin-left:auto; margin-right:auto; } #window-titlebar { background-color:#D0C4E2; margin-bottom:10px; width:100%; } #window-title { text-align:right; width:66%; } #window-close { text-align:right; } .column-choice select { min-width:15em; }

5 5

[Pharo-project] Initial experience coming from Squeak
by Sean P. DeNigris April 10, 2010

April 10, 2010

I love the clean look with all the great developer features pre-installed (shout, OCompletion, etc.). It's been a pleasure to work with. And, a few things stood out that didn't seem to work as well. I'm sharing them here because I wonder what your opinions are. Also, what is the policy about contributing "good ideas" i.e. new/altered features that are not bug fixes? Is it best to discuss them on the list like this, or submit a changeset right off the bat per http://code.google.com/p/pharo/wiki/HowToContribute? Suggestions: * Why shift for meta? On a Macbook (with one button), it's awkward to press shift+alt+click, and also disorienting to go back and forth from Squeak which is just alt+click. Is there a reason to not keep the convention? * what is with the workflow of the default browser? When you click on a protocol, the method template appears in the bottom pane, all highlighted and ready to be replaced. But because hovering over the pane doesn't give it the keyboard focus (like Squeak), you have to click in it, which unselects the template, which you then have to reselect manuallyâ¦ Certainly not a big deal, but weird. I though of a few possible fixes: - automatically give the bottom pane the keyboard focus when working in the protocol column (which doesn't seem to need it (I like this one - fewest steps for the user) - don't have the template pre-selected, so that clicking in the pane below the template selects it (easiest fix, requires one more user click) * bizarre window changing - the (on Mac) Cmd+(hold arrow) to rotate through the open windows is pretty cool, but when you tap the arrow key (instead of holding it), it just goes back and forth between two windows, which I can't see a use for. It seems it would be more useful to have the behavior to be: if you hold down the Cmd key and repeatedly tap the arrow hit, the windows rotate one after the other until you get through them all and recycle and v.v. for the opposite direction arrow. * new windows e.g. workspaces appear wherever they feel like (is it a standard location?). It seems to flow better if they appeared where the user is already looking i.e. where the active hand is. * Single/multi-line popups - when you're extracting a method via "refactor source," you get a huge multi-line popup window, which eats crs, so after you enter the name and hit return, you are still in the popup and must take your hands off the keyboard to click "ok." Now, fair enough, this might actually be a good thing in other circumstances, but - when you reference an unknown class, you get an "unknown variable" popup, choose "define new class," click through the category selection, you get a one-line popup to edit a paragraph-long class definition, lol! So: - "refactor source->extract method" should be a single-line popup - and, "define new class->edit class definition" should be a multi-liner. Thanks for an awesome environment, and I will continue to contribute any way I can :) Sean P. DeNigris -- View this message in context: http://n4.nabble.com/Initial-experience-coming-from-Squeak-tp1799044p179904… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

6 12

[Pharo-project] potential bugfix for orphan OCompletion menus
by Romain Robbes April 10, 2010

April 10, 2010

Dear list, I just published a version of OCompletion with a possible fix for the bug in which OCompletion menus would stay on the screen after a browser is closed. The issue here is inherited from eCompletion: the menu morph is not a child of the window, but a top-level morph. To adress this, I implemented a timeout mechanism: if their was no keystroke in the editor which spawned the menu for the last 5 seconds, the menu will close automatically. You can hence try Ocompletion-RomainRobbes.54 on squeaksource, and tell me what you think of the solution, or of the length of the timeout (I tried to stay conservative, maybe something like 3 seconds would work better). Cheers, Romain -- Romain Robbes http://romain.robb.es rrobbes(a)dcc.uchile.cl

5 12

April 9, 2010

11310 ----- - Issue 2286: Class definition while compiling method - Issue 2131: Handling Window events. Thanks Henrik - I looked at the code and I would not be able to fix that. again some stuff to learn. Stef

2 1

April 9, 2010

Begin forwarded message: > From: "David T. Lewis" <lewis(a)mail.msen.com> > Date: April 9, 2010 2:52:27 PM GMT+02:00 > To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > Subject: Re: [Vm-dev] Questions, communication and process > Reply-To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > > On Fri, Apr 09, 2010 at 11:23:18AM +0200, stephane ducasse wrote: >> >> Hi vm guys, >> >> I would like to know the process to report problems, issues, enh to the vm because people asked me >> and I have no idea how this is done. I read the web site but I could not find a bugtracker. > > Hi Stef, > > In addition to Ian's explanations, I'll add couple of points. > >> >> Several questions: >> - How do people report problems? Just sending an email in the mailing-list is enough? > > The bugtracker is Mantis at bugs.squeak.org. Use category "VM" when > reporting or searching for problems. For any problems or enhancement > requests that may time time to resolve, it is very helpful to use > the bugtracker because it provides a process for ensuring that issues > are addressed or at least not forgotten, and also a reference for > people who run into an issue that someone else has addressed. > > I try to catch issues that I see on the Pharo and squeak-dev lists > and enter them on Mantis if they will need follow up, but I'm sure > that I miss things from time to time. > > Follow Ian's instructions for reporting problems to vm-dev and the > platform developer. That is the way that problems get noticed, > discussed, and addressed. But to ensure follow-up, please also > use the bugtracker. > >> - How a fix in one OS is propagated to the others? >> - How the user can know that? > > For issues that affect the VM overall, the change history of the > VMMaker package on squeaksource is helpful. You can use Monticello > of course, but I like to point a web browser at www.squeaksource.com, > project VMMaker, and browse through the entries under the "News" tab. > > A remaining problem is that that the VM user cannot always tell if > their VM actually contains a particular fix or feature. To some extent > you can figure it out from the name of the VM file, but we need a better > run time check. We (or I) will probably add a way to check this through > a primitive, but for now it remains confusing. > > Dave >

1 0

[Pharo-project] bizarre window cycling behavior
by Sean P. DeNigris April 9, 2010

April 9, 2010

On the (on Mac) Cmd+(hold arrow) to rotate through the open windows is pretty cool, but when you tap the arrow key (instead of holding it), it just goes back and forth between two windows, which I can't see a use for. It seems it would be more useful to have the behavior to be: if you hold down the Cmd key and repeatedly tap the arrow hit, the windows rotate one after the other until you get through them all and recycle and v.v. for the opposite direction arrow. Issue 2289: http://code.google.com/p/pharo/issues/detail?id=2289 -- View this message in context: http://n4.nabble.com/bizarre-window-cycling-behavior-tp1819783p1819783.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0