hi john
I hope your travel back was good. It was good to have you around at ESUG. I wanted to know if this would be possible that when we double click on an image and that there is already one squeak running, we get another one. Because now we are all copying VM around.
Stef
Did we ever fix this?
I would say the ground work is there to allow you to change the drag and drop logic to see that the file incoming is a squeak image, then invoke an applescript command which invokes a bsd shell to startup the squeak VM with the incoming image name. I had added support to allow you to specific an image name when you launch squeak from a shell a few versions back.
On 18-Sep-04, at 10:27 AM, stéphane ducasse wrote:
hi john
I hope your travel back was good. It was good to have you around at ESUG. I wanted to know if this would be possible that when we double click on an image and that there is already one squeak running, we get another one. Because now we are all copying VM around.
Stef
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
You mean we need in-image support for that? All other VMs just do it on their own ...
- Bert -
Am 12.09.2005 um 19:09 schrieb John M McIntosh:
Did we ever fix this?
I would say the ground work is there to allow you to change the drag and drop logic to see that the file incoming is a squeak image, then invoke an applescript command which invokes a bsd shell to startup the squeak VM with the incoming image name. I had added support to allow you to specific an image name when you launch squeak from a shell a few versions back.
On 18-Sep-04, at 10:27 AM, stéphane ducasse wrote:
hi john
I hope your travel back was good. It was good to have you around at ESUG. I wanted to know if this would be possible that when we double click on an image and that there is already one squeak running, we get another one. Because now we are all copying VM around.
Stef
Well the problem is that when you double click on an image in the finder, *IT* looks in it's magic table of file types or file suffixes and say's mmm that Squeak application over there says it handles files of type Squeak or suffixes of .image and look one is running already, so let's do an Apple Event open document request to it. This incorrectly assumes of course you run one copy of your application which handles multiple open documents.
Then again if someone could figure out how to convince the Finder it must start another instance of the application on an open document request that would be welcome.
On 12-Sep-05, at 2:53 PM, Bert Freudenberg wrote:
You mean we need in-image support for that? All other VMs just do it on their own ...
- Bert -
Am 12.09.2005 um 19:09 schrieb John M McIntosh:
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
John M McIntosh wrote:
Well the problem is that when you double click on an image in the finder, *IT* looks in it's magic table of file types or file suffixes and say's mmm that Squeak application over there says it handles files of type Squeak or suffixes of .image and look one is running already, so let's do an Apple Event open document request to it. This incorrectly assumes of course you run one copy of your application which handles multiple open documents.
But that would be okay if, say, the VM handled the open document event and spawns a new VM with the image in question, no? It might be somewhat confusing if you actually drop an image onto another running Squeak and expect it to be handled inside Squeak itself but my guess is that most people would prefer this to the current situation and it could also be controlled via some (VM-level) preference.
Cheers, - Andreas
Well yes I could attempt to handle it in the VM, but that's quite a bit of C code that has minimal folks supporting, and in case of bugs few folks that would fix it, plus of course the upgrade path isn't automatic, one must download a new VM from somewhere.
If everything is in the image then fixing it becomes a bit easier, plus you then can handle the case of what you want it to do, open a new application, start the simulated interpreter, look at the bytes? On the other hand perhaps I'll put some C code together just to understand the complexity.
On 12-Sep-05, at 3:48 PM, Andreas Raab wrote:
John M McIntosh wrote:
Well the problem is that when you double click on an image in the finder, *IT* looks in it's magic table of file types or file suffixes and say's mmm that Squeak application over there says it handles files of type Squeak or suffixes of .image and look one is running already, so let's do an Apple Event open document request to it. This incorrectly assumes of course you run one copy of your application which handles multiple open documents.
But that would be okay if, say, the VM handled the open document event and spawns a new VM with the image in question, no? It might be somewhat confusing if you actually drop an image onto another running Squeak and expect it to be handled inside Squeak itself but my guess is that most people would prefer this to the current situation and it could also be controlled via some (VM-level) preference.
Cheers,
- Andreas
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
John M McIntosh wrote:
Well yes I could attempt to handle it in the VM, but that's quite a bit of C code that has minimal folks supporting, and in case of bugs few folks that would fix it, plus of course the upgrade path isn't automatic, one must download a new VM from somewhere.
Agreed. Yet ...
If everything is in the image then fixing it becomes a bit easier, plus you then can handle the case of what you want it to do, open a new application, start the simulated interpreter, look at the bytes?
... with this solution the reaction to a double-click depends on the image you are currently running. In other words, double clicking on another image while running Squeak 3.9 would work but double clicking on an image while running Croquet or Squeakland (3.8 based) would not. Ouch ;-)
Cheers, - Andreas
John M McIntosh johnmci@smalltalkconsulting.com wrote:
Well yes I could attempt to handle it in the VM, but that's quite a bit of C code
Shouldn't it just be a test to look at the filetype, followed by a rejection of the load if it is a Squeak image which then surely ought to make the system start a new VM?
Please tell me Apple didn't make it insanely complicated...
tim -- Tim Rowledge, tim@rowledge.org, http://www.rowledge.org/tim Useful Latin Phrases:- Furnulum pani nolo = I don't want a toaster.
Nope, by the time you get the apple event to say open this document everyone has decided you the squeak VM are responsible for opening the document.
On 12-Sep-05, at 10:30 PM, Tim Rowledge wrote:
John M McIntosh johnmci@smalltalkconsulting.com wrote:
Well yes I could attempt to handle it in the VM, but that's quite a bit of C code
Shouldn't it just be a test to look at the filetype, followed by a rejection of the load if it is a Squeak image which then surely ought to make the system start a new VM?
Please tell me Apple didn't make it insanely complicated...
tim
Tim Rowledge, tim@rowledge.org, http://www.rowledge.org/tim Useful Latin Phrases:- Furnulum pani nolo = I don't want a toaster.
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
squeak-dev@lists.squeakfoundation.org