[Pharo-project] Workspace Enhancement
Dear List, Added history to Workspace. When you close a workspace now you will not be bothered with a popup window asking you whether you sure you want to close the window. In the workspace you have access to the historic of the last 5 previous contents.. Click on the right top icon of a workspace to get access to the previous contents. Tools-AlexandreBergel.137 in PharoInbox Issue #449 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try). What about contents of workspace variables? Are those stored in the history as well?
thanks. Stef On Jan 19, 2009, at 8:42 PM, Chris Cunningham wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well? _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables? Thanks for your words, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I would not bother there are inspectors for this kind of things. You create an object and get several snippets Else you write a class, no? On Jan 19, 2009, at 11:23 PM, Alexandre Bergel wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
It happened to me more than once, that I accidently had some huge objects hanging in a workspace leading to a memory leak. So remembering the variables can be a dangerous thing. However, just remembering the string isn't that useful either. I often build objects that I keep around in a workspace to play with. Without remembering these instances the code snippets in the workspace are useless. So I don't know ;-) Lukas On Tue, Jan 20, 2009 at 8:46 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I would not bother there are inspectors for this kind of things. You create an object and get several snippets
Else you write a class, no?
On Jan 19, 2009, at 11:23 PM, Alexandre Bergel wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
On Jan 20, 2009, at 9:03 AM, Lukas Renggli wrote:
It happened to me more than once, that I accidently had some huge objects hanging in a workspace leading to a memory leak. So remembering the variables can be a dangerous thing.
yes :)
However, just remembering the string isn't that useful either. I often build objects that I keep around in a workspace to play with. Without remembering these instances the code snippets in the workspace are useless.
So I don't know ;-)
a class :) Stef
Lukas
On Tue, Jan 20, 2009 at 8:46 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I would not bother there are inspectors for this kind of things. You create an object and get several snippets
Else you write a class, no?
On Jan 19, 2009, at 11:23 PM, Alexandre Bergel wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
The history for workspace contents has 5 slots. Slots are filled upon workspace deletion: when you close a workspace, its content is inserted in the history. Only the last 5 contents are remembered. Other are forgotten. It is easy to increase this limit although. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
why don't you use a "circular" array using atWrap atWrap: index put: value "Store value into the index'th element of the receiver. If index is out of bounds, let it wrap around from the end to the beginning until it is in bounds. Answer value." ^ self at: index - 1 \\ self size + 1 put: value :) On Jan 20, 2009, at 9:44 AM, Alexandre Bergel wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
The history for workspace contents has 5 slots. Slots are filled upon workspace deletion: when you close a workspace, its content is inserted in the history. Only the last 5 contents are remembered. Other are forgotten.
It is easy to increase this limit although.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Humm... Ideally, the history should contains the most recent workspace contents doesn't it? Alexandre On 20 Jan 2009, at 10:17, Stéphane Ducasse wrote:
why don't you use a "circular" array using atWrap
atWrap: index put: value "Store value into the index'th element of the receiver. If index is out of bounds, let it wrap around from the end to the beginning until it is in bounds. Answer value."
^ self at: index - 1 \\ self size + 1 put: value
:)
On Jan 20, 2009, at 9:44 AM, Alexandre Bergel wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
The history for workspace contents has 5 slots. Slots are filled upon workspace deletion: when you close a workspace, its content is inserted in the history. Only the last 5 contents are remembered. Other are forgotten.
It is easy to increase this limit although.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
yes so you always add to your collection but you do not have to have 5 instance variables and have a counter and also always add at the icunter value or simply do a modulo: 5 + 1 stef On Jan 20, 2009, at 10:24 AM, Alexandre Bergel wrote:
Humm... Ideally, the history should contains the most recent workspace contents doesn't it?
Alexandre
On 20 Jan 2009, at 10:17, Stéphane Ducasse wrote:
why don't you use a "circular" array using atWrap
atWrap: index put: value "Store value into the index'th element of the receiver. If index is out of bounds, let it wrap around from the end to the beginning until it is in bounds. Answer value."
^ self at: index - 1 \\ self size + 1 put: value
:)
On Jan 20, 2009, at 9:44 AM, Alexandre Bergel wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
The history for workspace contents has 5 slots. Slots are filled upon workspace deletion: when you close a workspace, its content is inserted in the history. Only the last 5 contents are remembered. Other are forgotten.
It is easy to increase this limit although.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
What I currently do, is something like: history addFirst: workspace content. history := history copyFrom: 1 to: (history size min: 5). Alexandre On 20 Jan 2009, at 11:15, Stéphane Ducasse wrote:
yes so you always add to your collection but you do not have to have 5 instance variables and have a counter and also always add at the icunter value or simply do a modulo: 5 + 1
stef
On Jan 20, 2009, at 10:24 AM, Alexandre Bergel wrote:
Humm... Ideally, the history should contains the most recent workspace contents doesn't it?
Alexandre
On 20 Jan 2009, at 10:17, Stéphane Ducasse wrote:
why don't you use a "circular" array using atWrap
atWrap: index put: value "Store value into the index'th element of the receiver. If index is out of bounds, let it wrap around from the end to the beginning until it is in bounds. Answer value."
^ self at: index - 1 \\ self size + 1 put: value
:)
On Jan 20, 2009, at 9:44 AM, Alexandre Bergel wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
The history for workspace contents has 5 slots. Slots are filled upon workspace deletion: when you close a workspace, its content is inserted in the history. Only the last 5 contents are remembered. Other are forgotten.
It is easy to increase this limit although.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
i see and I have the impression that with a counter and modulo you would not have to copy. On Jan 20, 2009, at 12:54 PM, Alexandre Bergel wrote:
What I currently do, is something like:
history addFirst: workspace content. history := history copyFrom: 1 to: (history size min: 5).
Alexandre
On 20 Jan 2009, at 11:15, Stéphane Ducasse wrote:
yes so you always add to your collection but you do not have to have 5 instance variables and have a counter and also always add at the icunter value or simply do a modulo: 5 + 1
stef
On Jan 20, 2009, at 10:24 AM, Alexandre Bergel wrote:
Humm... Ideally, the history should contains the most recent workspace contents doesn't it?
Alexandre
On 20 Jan 2009, at 10:17, Stéphane Ducasse wrote:
why don't you use a "circular" array using atWrap
atWrap: index put: value "Store value into the index'th element of the receiver. If index is out of bounds, let it wrap around from the end to the beginning until it is in bounds. Answer value."
^ self at: index - 1 \\ self size + 1 put: value
:)
On Jan 20, 2009, at 9:44 AM, Alexandre Bergel wrote:
Neat behaviour - I'll have to try it out (like, what happens when you have 5 open workspaces - do they all have access to the same list of history? Just something to try).
What about contents of workspace variables? Are those stored in the history as well?
Actually, I seldom reuse variables across workspaces and have no more than 2 or 3 workspace at the same time. What would be the ideal scenario for variables?
Thanks for your words, Alexandre
The history for workspace contents has 5 slots. Slots are filled upon workspace deletion: when you close a workspace, its content is inserted in the history. Only the last 5 contents are remembered. Other are forgotten.
It is easy to increase this limit although.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Tue, Jan 20, 2009 at 12:03 AM, Lukas Renggli <renggli@gmail.com> wrote:
It happened to me more than once, that I accidently had some huge objects hanging in a workspace leading to a memory leak. So remembering the variables can be a dangerous thing.
Mainly I was checking to see if there would be issues like this. I often do researchy things in workspaces which grab only large amounts of memory (100's of MB), and forget to nil them out afterwards. Then, weeks (or months) later I need to shrink the image, and eventually find my way back to the workspace where a simple nil clears them out. I was worried that if they were held onto in history, this would be a problem. Keeping the strings around would be useful for me - my current image has about 20 workspaces open (and in 3.10 dev, this results in lots of minimized window title bars). Being able to store them off in history would be nice. -Chris
s them out. I was worried that if they were held onto in history, this would be a problem.
Keeping the strings around would be useful for me - my current image has about 20 workspaces open (and in 3.10 dev, this results in lots of minimized window title bars). Being able to store them off in history would be nice.
-Chris Sounds like a job for ScriptManager
Keith
Maybe we could discard Workspace content that are more than 10 days old Just an idea... Alexandre On 21 Jan 2009, at 01:44, Chris Cunningham wrote:
On Tue, Jan 20, 2009 at 12:03 AM, Lukas Renggli <renggli@gmail.com> wrote: It happened to me more than once, that I accidently had some huge objects hanging in a workspace leading to a memory leak. So remembering the variables can be a dangerous thing.
Mainly I was checking to see if there would be issues like this. I often do researchy things in workspaces which grab only large amounts of memory (100's of MB), and forget to nil them out afterwards. Then, weeks (or months) later I need to shrink the image, and eventually find my way back to the workspace where a simple nil clears them out. I was worried that if they were held onto in history, this would be a problem.
Keeping the strings around would be useful for me - my current image has about 20 workspaces open (and in 3.10 dev, this results in lots of minimized window title bars). Being able to store them off in history would be nice.
-Chris _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
participants (6)
-
Alexandre Bergel -
Alexandre Bergel -
Chris Cunningham -
Keith Hodges -
Lukas Renggli -
Stéphane Ducasse