On 22-Nov-06, at 7:14 AM, Bert Freudenberg wrote: >> Is single mouse button behavior correct? > > Yes. Ok, the problem is the browser, or the hardware driver for the mouse etc, is changing the button pressed (say 2) into button 1 press with modifier key. That is passed to me by the browser, then we pass that to the VM, where it decides which button was pressed based on the modifier keys. MMm perhaps another set of tables is needed in the VM to handle browser mis-mapping. Does this mouse come with software? If so how is it configured? Let me ask if you run the VM standalone do the buttons work as expected? >> Which cmd-key sequences in which browser. > > I'm using Safari. Cmd-m, Cmd-p, etc. invoke the browser's menu items. I'm fairly sure the browser gets the cmd-key menu shortcuts before the browser does, in fact I'll bet cmd-p is never passed on to the plugin because the browser menu logic has eaten it for "print" > >>> SecurityPlugin paths appear not to be fixed, yet. >> >> What should they be? Let me add the parms so you can specify them, then let whomever sort out what they should be. I'll post a new vm,plugin pair later tonight > > Should point into the user's library folder - named "My Squeak", > and "private" maybe. > > IMHO the Right Place for these would be ~/Library/Application > Support/Squeakland, the VM should be /Applications/Squeakland.app, > and the image /Applications/Squeakland.app/Contents/Resources/ > SqueakPlugin.image. > > Not sure if everyone would agree on that, though, I won't fight the > status quo too hard ;) > > - Bert - > > -- ======================================================================== === John M. McIntosh <[hidden email]> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== === |
On Nov 22, 2006, at 20:58 , John M McIntosh wrote: > > On 22-Nov-06, at 7:14 AM, Bert Freudenberg wrote: > >>> Is single mouse button behavior correct? >> >> Yes. > > Ok, the problem is the browser, or the hardware driver for the > mouse etc, is changing the button pressed (say 2) into > button 1 press with modifier key. That is passed to me by the > browser, then we pass that to the VM, where it decides which > button was pressed based on the modifier keys. MMm perhaps another > set of tables is needed in the VM to handle browser mis-mapping. > Does this mouse come with software? If so how is it configured? It's the build-in touch pad of a MacBook Pro - it generates a button-2 click, which is equivalent to a MightyMouse right click (or any 3-button-mouse's right click). > Let me ask if you run the VM standalone do the buttons work as > expected? Yes. I think the actual problem is that Squeak's modifier mapping is wrong. Generally, on Mac OS the way to access the context menu (like, in the Finder) is Ctrl-click. So it's only natural that Apple choose that mapping to deliver a right click. In Squeak the context menu is brought up by Option-click which is rather un-Mac-like, but I'm not sure what outcry we would generate if we changed that. >>> Which cmd-key sequences in which browser. >> >> I'm using Safari. Cmd-m, Cmd-p, etc. invoke the browser's menu items. > > I'm fairly sure the browser gets the cmd-key menu shortcuts before > the browser does, in fact I'll bet cmd-p is never passed > on to the plugin because the browser menu logic has eaten it for > "print" :( >>>> SecurityPlugin paths appear not to be fixed, yet. >>> >>> What should they be? > > Let me add the parms so you can specify them, then let whomever > sort out what they should be. But they have to be relative to each User's home at least, an absolute path won't cut it. > I'll post a new vm,plugin pair later tonight > >> >> Should point into the user's library folder - named "My Squeak", >> and "private" maybe. >> >> IMHO the Right Place for these would be ~/Library/Application >> Support/Squeakland, the VM should be /Applications/Squeakland.app, >> and the image /Applications/Squeakland.app/Contents/Resources/ >> SqueakPlugin.image. >> >> Not sure if everyone would agree on that, though, I won't fight >> the status quo too hard ;) >> >> - Bert - - Bert - |
On 22-Nov-06, at 12:22 PM, Bert Freudenberg wrote: > It's the build-in touch pad of a MacBook Pro - it generates a > button-2 click, which is equivalent to a MightyMouse right click > (or any 3-button-mouse's right click). I've added info.plist entries to remap mouse/modifer key input when running under the browser, versus standalone so that one can figure out what it should be when faced with fancy trackpads, or multi-button mice. Please fiddle with until correct. > >> >> Let me add the parms so you can specify them, then let whomever >> sort out what they should be. > > But they have to be relative to each User's home at least, an > absolute path won't cut it. I've posted a 3.8.14b6 VM to my idisk, via http:// www.smalltalkconsulting.com/squeak.html that provides an entry for the untrusted directory, you can specify a ~ btw to resolve user directory paths. Lastly pending is logic to make the Full screen logic work, don't let me forget this. -- ======================================================================== === John M. McIntosh <[hidden email]> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== === |
On Nov 23, 2006, at 19:02 , John M McIntosh wrote: > > On 22-Nov-06, at 12:22 PM, Bert Freudenberg wrote: > >> It's the build-in touch pad of a MacBook Pro - it generates a >> button-2 click, which is equivalent to a MightyMouse right click >> (or any 3-button-mouse's right click). > > I've added info.plist entries to remap mouse/modifer key input when > running under the browser, versus standalone so that one > can figure out what it should be when faced with fancy trackpads, > or multi-button mice. Please fiddle with until correct. Doesn't work. I set all SqueakBrowserMouseControlButton* to 1 but still get the Ctrl-Menu for second button. I guess it is reported to the VM as Ctrl-Click and you would have to strip the Ctrl modifier before giving it to the image. >>> Let me add the parms so you can specify them, then let whomever >>> sort out what they should be. >> >> But they have to be relative to each User's home at least, an >> absolute path won't cut it. > > I've posted a 3.8.14b6 VM to my idisk, via http:// > www.smalltalkconsulting.com/squeak.html that provides an entry for > the untrusted directory, you can specify a ~ btw to resolve user > directory paths. Yay - this one loads projects without walkbacks :) However, it seems to strip the last component of the path given - the "My Squeak" part is missing. Also, we need the same for the secure user directory - a non-admin user cannot write to /Applications. > Lastly pending is logic to make the Full screen logic work, don't > let me forget this. Btw, I just noticed it does not work in Mail anymore. It was a fun "feature" that you could press Cmd-i from the plugin and have the image running in Mail. Not really useful, I know. - Bert - |
Bert Freudenberg skrev:
> > On Nov 23, 2006, at 19:02 , John M McIntosh wrote: > >> >> On 22-Nov-06, at 12:22 PM, Bert Freudenberg wrote: >> >>> It's the build-in touch pad of a MacBook Pro - it generates a >>> button-2 click, which is equivalent to a MightyMouse right click (or >>> any 3-button-mouse's right click). >> >> I've added info.plist entries to remap mouse/modifer key input when >> running under the browser, versus standalone so that one >> can figure out what it should be when faced with fancy trackpads, or >> multi-button mice. Please fiddle with until correct. > > Doesn't work. I set all SqueakBrowserMouseControlButton* to 1 but > still get the Ctrl-Menu for second button. I guess it is reported to > the VM as Ctrl-Click and you would have to strip the Ctrl modifier > before giving it to the image. > >>>> Let me add the parms so you can specify them, then let whomever >>>> sort out what they should be. >>> >>> But they have to be relative to each User's home at least, an >>> absolute path won't cut it. >> >> I've posted a 3.8.14b6 VM to my idisk, via >> http://www.smalltalkconsulting.com/squeak.html that provides an entry >> for >> the untrusted directory, you can specify a ~ btw to resolve user >> directory paths. > > Yay - this one loads projects without walkbacks :) > > However, it seems to strip the last component of the path given - the > "My Squeak" part is missing. Also, we need the same for the secure > user directory - a non-admin user cannot write to /Applications. > >> Lastly pending is logic to make the Full screen logic work, don't let >> me forget this. > > Btw, I just noticed it does not work in Mail anymore. It was a fun > "feature" that you could press Cmd-i from the plugin and have the > image running in Mail. Not really useful, I know. > > - Bert - > > > > down events on MacOsX. Before you could click and hold and a menu would pop up, now you have to hold down the ctrl button for that to happen. I guess it's because less people have one button mice... Karl |
On Nov 23, 2006, at 22:11 , karl wrote: > For what it's worth, I think Firefox 2 changed the way it handles > mouse down events on MacOsX. > Before you could click and hold and a menu would pop up, now you > have to hold down the > ctrl button for that to happen. I guess it's because less people > have one button mice... I actually did not test on Firefox until 5 minutes ago. Good news - it works, in principle. Bad news - it has a weird mouse offset, which seems to vary when scrolling. In other news, it works perfectly on Opera (apart from the non- existing clipping). - Bert - |
which version of firefox
On 23-Nov-06, at 1:55 PM, Bert Freudenberg wrote: > > On Nov 23, 2006, at 22:11 , karl wrote: >> For what it's worth, I think Firefox 2 changed the way it handles >> mouse down events on MacOsX. >> Before you could click and hold and a menu would pop up, now you >> have to hold down the >> ctrl button for that to happen. I guess it's because less people >> have one button mice... > > I actually did not test on Firefox until 5 minutes ago. > > Good news - it works, in principle. Bad news - it has a weird mouse > offset, which seems to vary when scrolling. > > In other news, it works perfectly on Opera (apart from the non- > existing clipping). > > - Bert - > > > -- ======================================================================== === John M. McIntosh <[hidden email]> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== === |
2.0
Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1) Gecko/ 20061010 Firefox/2.0 - Bert - On Nov 24, 2006, at 3:01 , John M McIntosh wrote: > which version of firefox > > On 23-Nov-06, at 1:55 PM, Bert Freudenberg wrote: > >> >> On Nov 23, 2006, at 22:11 , karl wrote: >>> For what it's worth, I think Firefox 2 changed the way it handles >>> mouse down events on MacOsX. >>> Before you could click and hold and a menu would pop up, now you >>> have to hold down the >>> ctrl button for that to happen. I guess it's because less people >>> have one button mice... >> >> I actually did not test on Firefox until 5 minutes ago. >> >> Good news - it works, in principle. Bad news - it has a weird >> mouse offset, which seems to vary when scrolling. >> >> In other news, it works perfectly on Opera (apart from the non- >> existing clipping). >> >> - Bert - >> >> >> > > -- > ====================================================================== > ===== > John M. McIntosh <[hidden email]> > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > ====================================================================== > ===== > > > |
In reply to this post by Bert Freudenberg
send me the HTML you used for testing
On 23-Nov-06, at 1:55 PM, Bert Freudenberg wrote: > > On Nov 23, 2006, at 22:11 , karl wrote: >> For what it's worth, I think Firefox 2 changed the way it handles >> mouse down events on MacOsX. >> Before you could click and hold and a menu would pop up, now you >> have to hold down the >> ctrl button for that to happen. I guess it's because less people >> have one button mice... > > I actually did not test on Firefox until 5 minutes ago. > > Good news - it works, in principle. Bad news - it has a weird mouse > offset, which seems to vary when scrolling. > > In other news, it works perfectly on Opera (apart from the non- > existing clipping). > > - Bert - > > > -- ======================================================================== === John M. McIntosh <[hidden email]> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== === |
http://squeakland.org/project.jsp?http://www.squeakland.org/
fun_projects/proj_pe_mo/fishing/fisherman.009.pr You have to make the browser windows smaller than the project, and then scroll. - Bert - On Nov 24, 2006, at 16:19 , John M McIntosh wrote: > send me the HTML you used for testing > > On 23-Nov-06, at 1:55 PM, Bert Freudenberg wrote: > >> >> On Nov 23, 2006, at 22:11 , karl wrote: >>> For what it's worth, I think Firefox 2 changed the way it handles >>> mouse down events on MacOsX. >>> Before you could click and hold and a menu would pop up, now you >>> have to hold down the >>> ctrl button for that to happen. I guess it's because less people >>> have one button mice... >> >> I actually did not test on Firefox until 5 minutes ago. >> >> Good news - it works, in principle. Bad news - it has a weird >> mouse offset, which seems to vary when scrolling. >> >> In other news, it works perfectly on Opera (apart from the non- >> existing clipping). >> >> - Bert - |
In reply to this post by Bert Freudenberg
Ok, I've posted a 3.8.14b6 version of the plugin
SqueakBrowserPlugin.plugin.3.8.14b6.zip to my idisk, via http://www.smalltalkconsulting.com/squeak.html That plugin fixes the issue with clipping for safari + firefox, and fixes the scrolled drawing issue for firefox. I did not have to change the VM. I've not yet considered what to do about the mouse issue in the browser since the browser is mapping say button 2 to a keyboard modifier key and button 1, which we later pass to the VM and it maps from that representation to a button and modifier. On 23-Nov-06, at 1:55 PM, Bert Freudenberg wrote: > > On Nov 23, 2006, at 22:11 , karl wrote: >> For what it's worth, I think Firefox 2 changed the way it handles >> mouse down events on MacOsX. >> Before you could click and hold and a menu would pop up, now you >> have to hold down the >> ctrl button for that to happen. I guess it's because less people >> have one button mice... > > I actually did not test on Firefox until 5 minutes ago. > > Good news - it works, in principle. Bad news - it has a weird mouse > offset, which seems to vary when scrolling. > > In other news, it works perfectly on Opera (apart from the non- > existing clipping). > > - Bert - > > > -- ======================================================================== === John M. McIntosh <[hidden email]> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== === |
Yes, clipping is fixed.
However, I see weird drawing artifacts while scrolling in Firefox. The screen appears to be drawn three times for each scroll step - first in the page color (white), then offset, then in the right position. This leads to extreme flickering. Most of the time this only happens while scrolling, but I have seen it once while dragging a sketch about, too. Does not happen on Safari. On both Firefox and Opera, there is a black frame visible, about 20 pixels high and as wide as the plugin, I guess 2 pixels in width. In Firefox, it is centered on the page (seems to be painted on top of the white background, see above), in Opera, it is at the lower edge of the plugin. Not visible in Safari. Both in Safari and in Opera there as a brief white flashing when switching away from the browser to another app. Does not happen with Firefox. - Bert - On Nov 24, 2006, at 22:11 , John M McIntosh wrote: > Ok, I've posted a 3.8.14b6 version of the plugin > SqueakBrowserPlugin.plugin.3.8.14b6.zip > to my idisk, via > http://www.smalltalkconsulting.com/squeak.html > > That plugin fixes the issue with clipping for safari + firefox, and > fixes the scrolled drawing issue for firefox. > I did not have to change the VM. > > I've not yet considered what to do about the mouse issue in the > browser since the browser is mapping > say button 2 to a keyboard modifier key and button 1, which we > later pass to the VM and it maps from > that representation to a button and modifier. > > > On 23-Nov-06, at 1:55 PM, Bert Freudenberg wrote: > >> >> On Nov 23, 2006, at 22:11 , karl wrote: >>> For what it's worth, I think Firefox 2 changed the way it handles >>> mouse down events on MacOsX. >>> Before you could click and hold and a menu would pop up, now you >>> have to hold down the >>> ctrl button for that to happen. I guess it's because less people >>> have one button mice... >> >> I actually did not test on Firefox until 5 minutes ago. >> >> Good news - it works, in principle. Bad news - it has a weird >> mouse offset, which seems to vary when scrolling. >> >> In other news, it works perfectly on Opera (apart from the non- >> existing clipping). >> >> - Bert - |
Free forum by Nabble | Edit this page |