Hi All,
I use a lot of projects, and tend to keep one or two images for a long time. [tangent: I use two images so I can develop in one, using Vanessa's superb partial commit feature, load the clean packages in the second image, and generate VM sources from there. This allows me to have uncommitted changes in my main work image.]
The only glitch in this perfect world is the tension of moving between my large secondary monitor, my standard work context, and the laptop screen, which occurs when I want to work away from home. The image on the secondary monitor is set up with windows laid out according to its dimensions. When I start the image on the laptop away from the secondary monitor it of course doesn't fit.
So how about a preference that - remember's a project's screen extent when it last had a window laid out in it, or perhaps remembers the minimum rectangle enclosing all the windows in the project - on launch (effectively an entry into the current project) and/or entry into a project, if the screen extent is substantially smaller than the project's saved screen extent, all windows are scaled by the transformation from the original to the current size, i.e. they all get smaller and move towards the origin.
_,,,^..^,,,_ best, Eliot
Hi Eliot --
Did your request be somewhat addressed by the the in-image scale factor?
[...] using Vanessa's superb partial commit feature [...]
Uhh, what is that? :-)
Best, Marcel Am 06.11.2021 18:55:43 schrieb Eliot Miranda eliot.miranda@gmail.com: Hi All,
I use a lot of projects, and tend to keep one or two images for a long time. [tangent: I use two images so I can develop in one, using Vanessa's superb partial commit feature, load the clean packages in the second image, and generate VM sources from there. This allows me to have uncommitted changes in my main work image.]
The only glitch in this perfect world is the tension of moving between my large secondary monitor, my standard work context, and the laptop screen, which occurs when I want to work away from home. The image on the secondary monitor is set up with windows laid out according to its dimensions. When I start the image on the laptop away from the secondary monitor it of course doesn't fit.
So how about a preference that - remember's a project's screen extent when it last had a window laid out in it, or perhaps remembers the minimum rectangle enclosing all the windows in the project - on launch (effectively an entry into the current project) and/or entry into a project, if the screen extent is substantially smaller than the project's saved screen extent, all windows are scaled by the transformation from the original to the current size, i.e. they all get smaller and move towards the origin.
_,,,^..^,,,_
best, Eliot
Did your request be somewhat addressed by the the in-image scale factor?
I think Eliot's idea sounds like a brilliant enhancement to the new scaling feature. Smalltalk is already amazing in how you can transfer an image from one computer to another, even across platforms.
Just not different display sizes.. At least, not without awkwardness. IMO, it would be utterly cool if this "just worked". It would even be worth backporting to 6.0, to really showcase that new feature even better.
[...] using Vanessa's superb partial commit feature [...]
Uhh, what is that? :-)
Cmd+Shift+I to "I"gnore any number of changes in the MC save dialog.
Cmd+Shift+I to "I"gnore any number of changes in the MC save dialog.
Ah, I know about that one. :-) The only thing is that it is tricky to revert such a partial commit, for example, after putting it in the inbox. I would like to be able to not have to reset completely to the latest Trunk version of a particular package but just take back those methods that where uploaded in that partial commit.
Just not different display sizes.. At least, not without awkwardness. IMO, it would be utterly cool if this "just worked".
Hmm... yes, it would be nice if morph bounds would react to world-extent changes in a user-friendly way. The underlying concern/task might be related to how the RealEstateAgent tries to position new windows already: - Where to put a new morph/window? - What to do with the existing morphs (or windows) when the world extent grows? - What to do with the existing morphs (or windows) when the world extent shrinks? - ...
Effects might include: - Restore bounds to as they were for that known world extent - Look up a known world extent precisely or rounded (+/- 100 pixels?) - For each morph (or window) record a history of the previous n bounds-world pairs
- ...
Best, Marcel
Am 08.07.2022 06:05:24 schrieb Chris Muller asqueaker@gmail.com: Did your request be somewhat addressed by the the in-image scale factor?
I think Eliot's idea sounds like a brilliant enhancement to the new scaling feature. Smalltalk is already amazing in how you can transfer an image from one computer to another, even across platforms.
Just not different display sizes.. At least, not without awkwardness. IMO, it would be utterly cool if this "just worked". It would even be worth backporting to 6.0, to really showcase that new feature even better.
[...] using Vanessa's superb partial commit feature [...]
Uhh, what is that? :-)
Cmd+Shift+I to "I"gnore any number of changes in the MC save dialog.
squeak-dev@lists.squeakfoundation.org