[OpenSmalltalk/opensmalltalk-vm] 792705: Finish arg parsing work for embedded images on Win...
Branch: refs/heads/Cog Home: https://github.com/OpenSmalltalk/opensmalltalk-vm Commit: 7927053bb7f97cd8bf1059712db17c2d400c53a4 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/7927053bb7f97cd8bf1... Author: Eliot Miranda eliot.miranda@gmail.com Date: 2024-03-22 (Fri, 22 Mar 2024)
Changed paths: M platforms/win32/vm/sqWin32Main.c
Log Message: ----------- Finish arg parsing work for embedded images on Windows. Don't attempt to open argv[1] as an image if there is an embedded image.
To unsubscribe from these emails, change your notification settings at https://github.com/OpenSmalltalk/opensmalltalk-vm/settings/notifications
Hmm. That seems backwards to me; surely the logic would be more useful if a specified image file over-rode the embedded image? Then simply starting the VM would run the embedded image but d-click on an image would run that image.
Log Message:
Finish arg parsing work for embedded images on Windows. Don't attempt to open argv[1] as an image if there is an embedded image.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: WDS: Warp Drive, Scotty!
On Fri, Mar 22, 2024 at 10:10 AM Tim Rowledge tim@rowledge.org wrote:
Hmm. That seems backwards to me; surely the logic would be more useful if a specified image file over-rode the embedded image? Then simply starting the VM would run the embedded image but d-click on an image would run that image.
The use case is for securely distributing applications. So one *doesn't* want to allow a vm with an embedded image to run an arbitrary image. It *must* run the image embedded within it.
Log Message:
Finish arg parsing work for embedded images on Windows. Don't attempt
to open
argv[1] as an image if there is an embedded image.
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: WDS: Warp Drive, Scotty!
Fair enough; I was thinking almost the exact opposite scenario - you can only save an image to a separate file and then you (normally) run that. Sort of a way of having a default image that can't be 'damaged', an idea I think has merit for a normal distribution.
On 2024-03-22, at 11:01 AM, Eliot Miranda eliot.miranda@gmail.com wrote:
On Fri, Mar 22, 2024 at 10:10 AM Tim Rowledge tim@rowledge.org wrote:
Hmm. That seems backwards to me; surely the logic would be more useful if a specified image file over-rode the embedded image? Then simply starting the VM would run the embedded image but d-click on an image would run that image.
The use case is for securely distributing applications. So one *doesn't* want to allow a vm with an embedded image to run an arbitrary image. It *must* run the image embedded within it.
Log Message:
Finish arg parsing work for embedded images on Windows. Don't attempt to open argv[1] as an image if there is an embedded image.
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: WDS: Warp Drive, Scotty!
-- _,,,^..^,,,_ best, Eliot
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: QVC: Question Valid Command
vm-dev@lists.squeakfoundation.org
-
Eliot Miranda -
Eliot Miranda -
Tim Rowledge