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

Re: [Pharo-project] [update 1.1] #11310

by Henrik Johansen

Me neither, I just looked at the method changed in the .cs Torsten created based on Squeak changes and checked what was appropriate :) Btw, a "bad" side-effect is you Are no konger able to close a hung image with the close button, since it noe gets sent to the image side for handling. Cheers, Henry Den 9. apr. 2010 kl. 21.54 skrev StÃ©phane Ducass <stephane.ducasse(a)inria.f r>: > > 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 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 9, 2010

Re: [Pharo-project] Canvas transform bug when rendering text?

by Chris Muller

Thank you Henrik, it looks like a huge improvement! The attached screen shots help explain why I only said "improvement" instead of "perfect". Look at the color of my translucent morph when it is upright vs. rotated. The translucency is now preserved, which is great! However, do you know why the color seems to lose so much saturation? 2010/4/8 Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no>: > On 07.04.2010 14:26, Henrik Johansen wrote: > > On Apr 7, 2010, at 1:45 49PM, David Harvey wrote: > > Hi list, > I'm writing a little charting morph, and while playing with rotating text > for axis labels came across something which I've noted in Morphs text > handling a couple of times. > If I apply a transform in a drawing operation, rotated text _appears_ to be > drawn twice, slightly offset, giving a scrappy bold look. It seems only to > do this when drawing on a form canvas that's backed onto the display: if you > pick and drag the morph, the text is rendered beautifully. > The test morph attached isolates the problem. The transcript logging is an > attempt to see what might be happening: looking at the output it appears > that there are circumstances in which the during: block is invoked twice. > Any thoughts? > David > > http://n4.nabble.com/Problem-with-TransformationMorph-td1691811.html#a16918… > Basically, transform doesn't work with depth 32. > Workarounds are described in the thread. > Cheers, > Henry > > David, Lukas, whomever else it may concern. > > Of course I turned out to be (partly) wrong when looking into it. > Transform does indeed not work with alpha, but not because of bugs in > WarpBlt as I assumed, but because FormCanvas always uses the Paint rule when > rotating... > Try the attached code, and you should get better results. (you probably want > to use smoothing > 1 if displaying text with rotation other than a multiple > of 90 degrees). > > This seems to be more of a generic problem though, looking at the number of > places a= 32 ifTrue: [] check is made, I'll try to come up with a more > consistent solution for a system-wide patch. (which amongst other things > would also fix the black border appearing around a window while zooming back > to old position when you drag and drop it outside main window) > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 9, 2010

Re: [Pharo-project] Initial experience coming from Squeak

by Chris Muller

> * 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) Ha, the "click-for-focus" mosquito finally bit someone besides me. Sean, to live happily ever after, in Preferences, just enable mouseOverForKeyboardFocus. It solves all of the problems you mentioned above, reduces the overall effort needed to use the system because merely "pointing" at an object endows it with 100+ "mouse buttons" (left, middle, right, + the whole keyboard). It is more becoming of an object-oriented system, and if you can keep it on long enough to get used to it, I'll bet you'll never want to go back..

April 9, 2010

[Pharo-project] [update 1.1] #11310

by StÃ©phane Ducasse

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

April 9, 2010

Re: [Pharo-project] Initial experience coming from Squeak

by Sean P. DeNigris

I filed bugs for these: Issue 2288: http://code.google.com/p/pharo/issues/detail?id=2288 : Sean P. DeNigris wrote: > > * 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) > Issue 2289: http://code.google.com/p/pharo/issues/detail?id=2289 : Sean P. DeNigris wrote: > > * 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. > Issue 2290 : http://code.google.com/p/pharo/issues/detail?id=2290 : Sean P. DeNigris wrote: > > * 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. > Sean P. DeNigris -- View this message in context: http://n4.nabble.com/Initial-experience-coming-from-Squeak-tp1799044p181979… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 9, 2010

[Pharo-project] Communication with VM guys (part three)

by StÃ©phane Ducasse

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 >

April 9, 2010

[Pharo-project] bizarre window cycling behavior

by Sean P. DeNigris

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.

April 9, 2010

[Pharo-project] new windows (e.g. workspaces) appear wherever they feel like

by Sean P. DeNigris

It seems to flow better if they appeared where the user is already looking i.e. where the active hand is. Issue 2290 : http://code.google.com/p/pharo/issues/detail?id=2290. Sean -- View this message in context: http://n4.nabble.com/new-windows-e-g-workspaces-appear-wherever-they-feel-l… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 9, 2010

[Pharo-project] Communication with VM guys (part two)

by StÃ©phane Ducasse

Begin forwarded message: > From: Ian Piumarta <piumarta(a)speakeasy.net> > Date: April 9, 2010 12:35:16 PM GMT+02:00 > To: stephane ducasse <stephane.ducasse(a)gmail.com> > Cc: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > Subject: Re: [Vm-dev] Questions, communication and process > > Hi Stef, > > On Apr 9, 2010, at 2:23 AM, stephane ducasse wrote: > >> - How do people report problems? Just sending an email in the mailing-list is enough? > > Here are the options, necessarily biased towards my preference which is to try to avoid having to poll for outstanding issues. > > If it's a general problem of installation or bizarre behaviour that differs between platforms, ask for help on the Squeak VM mailing list. > > http://lists.squeakfoundation.org/mailman/listinfo/vm-dev > > Pharo and Squeak users are EQUALLY WELCOME to report VM issues on that list. Squeak has several people who regularly take the time to forward things from squeak-dev to vm-dev when appropriate. You might want to encourage the same thing on the Pharo list. I know for a fact that there are several vm-dev subscribers that monitor the Pharo list. (You might want to make it clear that Pharo uses the Squeak VM too. This does not necessarily appear to be universally understood.) > > If it's a Unix-specific problem that you think might be a bug, report it to the above mailing list AND send me email. Fixes are best submitted as complete modified files (not 'diffs'). (There might well be a way to tell ediff to use diff output directly, but that does not guarantee that your 'original' and my 'original' are in any way related. Sending whole files is MUCH more robust.) > > If it's Windows-specific, try the above list and Andreas Raab. For Mac-specific, the above list and John McIntosh. If it's common code shared by all platforms, especially code generated by VMMaker, send to Dave Lewis and the above list. > > VM bugs can fed to mantis here: bugs.squeak.org > > The people mentioned above probably look at mantis on a regular basis. Anything with more than four legs gives me the heebie-jeebies, which isn't why I don't regularly trawl mantis but it'll do. > >> - How a fix in one OS is propagated to the others? > > Fixes that affect more than one OS are very often in the common code that is generated automatically and shared between all the platforms. There is no explicit manual propagation required. (That being said, the people mentioned above are often in contact on a daily basis. When co-ordination is required, it will happen.) > > The exception is that some code is shared between Unix and Mac. John is good at spotting commits from me that affect him, and is good at bugging me when necessary into fixing anything Unixy that might affect him. > >> - How the user can know that? > > Watch vm-dev for discussions or commit reports that say the issue was fixed. If it is in mantis, it might even get closed too. > > The above reflects how I like to work, and I can only speak for myself. MPG from the others mentioned above might not be comparable. > > Cheers, > Ian > > (Feel free to forward, re-post, etc., the above as you see fit.) >

April 9, 2010

[Pharo-project] Communication with VM guys (part one)

by stephane ducasse

Hi guys I will send a following mail. We should probably synthetize and put them some summary on the web. Stef Begin forwarded message: > From: Ian Piumarta <ian(a)vpri.org> > Date: April 9, 2010 11:43:33 AM GMT+02:00 > To: laurent laffont <laurent.laffont(a)gmail.com> > Cc: stephane ducasse <stephane.ducasse(a)free.fr>, stephane ducasse <stephane.ducasse(a)gmail.com> > Subject: Re: [Vm-dev] Fwd: loading library with FFI fails (was [Pharo-project] Linux vm: assertions and strategy) > > Hi Laurent, > >> I've just seen you reply me in private. Do you mind if I forward your mail to Pharo & VM mailing lists, to see how we can improve communication and collaboration between projects ? I don't want to start a "counterproductive" flame war, I hate this, so maybe we can write another mail which doesn't offense people ? Maybe you have ideas on this ? > > How about we just say this... > >> It seems there is a complete lack of communication within the Pharo community regarding the virtual machine and its development/support. VM development and support (including bug reports and fixes) are discussed on the vm-dev mailing list. Both Pharo users and Squeak users are equally welcome there (and both communities should avoid discussing VM problems on their respective developer lists, since the people who should see those VM bug reports are more likely reading vm-dev than the other lists). Problems that appear to be platform-independent should always be reported to the vm-dev list. Problems specific to a particular platform should be sent to the maintainer of the platform whose e-mail address is included in the release notes or in the download area on squeakvm.org. > > Nobody could be offended by that? :) > > Cheers, > Ian >

April 9, 2010