editing the default window size of glamour inspector
Hello, I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large. How can I do it ? For example I would like something like that: MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000 Clement
2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
Hello,
I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large.
How can I do it ?
For example I would like something like that:
MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000
Clement
I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance) gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30> instead of gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30> this way you have access to the glamour inspector. Unfortunately it does not have any window extent property. Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument. Nicolai
Hi, Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail. The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else. The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones. But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account. I am even considering having this size cached by the class of the object (not sure yet if that makes sense). What do you think? Cheers, Doru On Mon, Nov 24, 2014 at 12:57 PM, Nicolai Hess <nicolaihess@web.de> wrote:
2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
Hello,
I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large.
How can I do it ?
For example I would like something like that:
MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000
Clement
I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance)
gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30>
instead of
gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30>
this way you have access to the glamour inspector. Unfortunately it does not have any window extent property.
Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument.
Nicolai
-- www.tudorgirba.com "Every thing has its own flow"
Tudor Girba wrote:
Hi,
Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail.
The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else.
The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones.
But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account.
I am even considering having this size cached by the class of the object (not sure yet if that makes sense).
As I was reading, I was thinking to myself that remembering last size per class would make a lot of sense. Could there be a button in Preferences to save initialExtents to file, so these carry over to new images? cheers -ben
2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail.
The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else.
The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones.
But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account. I am even considering having this size cached by the class of the object (not sure yet if that makes sense). What do you think?
Hello Doru, If we have a mechanism to remember the last size of the inspector per class, it would be nice to provide in addition APIs to change this value. Perhaps I could put on a start-up script something like: MyClass initialInspectorSize: 1000@1000. My issue is that on specific classes the inspector shows a big roassal visualization. When I inspect in a new window one of these objects, I need each time to enlarge the window to see the full visualization. If the previous size is saved or I can set the size somehow, it's fine for me. Cheers, Clement
Cheers, Doru
On Mon, Nov 24, 2014 at 12:57 PM, Nicolai Hess <nicolaihess@web.de> wrote:
2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
Hello,
I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large.
How can I do it ?
For example I would like something like that:
MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000
Clement
I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance)
gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30>
instead of
gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30>
this way you have access to the glamour inspector. Unfortunately it does not have any window extent property.
Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument.
Nicolai
-- www.tudorgirba.com
"Every thing has its own flow"
2014-11-24 15:54 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail.
The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else.
The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones.
But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account. I am even considering having this size cached by the class of the object (not sure yet if that makes sense). What do you think?
Hello Doru,
If we have a mechanism to remember the last size of the inspector per class, it would be nice to provide in addition APIs to change this value. Perhaps I could put on a start-up script something like: MyClass initialInspectorSize: 1000@1000.
My issue is that on specific classes the inspector shows a big roassal visualization. When I inspect in a new window one of these objects, I need each time to enlarge the window to see the full visualization. If the previous size is saved or I can set the size somehow, it's fine for me.
Maybe calling focusOnCenterScaled on the Roassal visualisation could be a solution? Because setting a size may be problematic (think of switching from
Cheers,
Clement
Cheers, Doru
On Mon, Nov 24, 2014 at 12:57 PM, Nicolai Hess <nicolaihess@web.de> wrote:
2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
Hello,
I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large.
How can I do it ?
For example I would like something like that:
MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000
Clement
I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance)
gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30>
instead of
gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30>
this way you have access to the glamour inspector. Unfortunately it does not have any window extent property.
Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument.
Nicolai
-- www.tudorgirba.com
"Every thing has its own flow"
2014-11-24 16:00 GMT+01:00 Thierry Goubier <thierry.goubier@gmail.com>:
2014-11-24 15:54 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail.
The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else.
The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones.
But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account. I am even considering having this size cached by the class of the object (not sure yet if that makes sense). What do you think?
Hello Doru,
If we have a mechanism to remember the last size of the inspector per class, it would be nice to provide in addition APIs to change this value. Perhaps I could put on a start-up script something like: MyClass initialInspectorSize: 1000@1000.
My issue is that on specific classes the inspector shows a big roassal visualization. When I inspect in a new window one of these objects, I need each time to enlarge the window to see the full visualization. If the previous size is saved or I can set the size somehow, it's fine for me.
Maybe calling focusOnCenterScaled on the Roassal visualisation could be a solution? Because setting a size may be problematic (think of switching from laptop mode
.. to a 5K external screen or a VGA projector (especially the 5K to macbook air switch ;)). Thierry
Cheers,
Clement
Cheers, Doru
On Mon, Nov 24, 2014 at 12:57 PM, Nicolai Hess <nicolaihess@web.de> wrote:
2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
Hello,
I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large.
How can I do it ?
For example I would like something like that:
MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000
Clement
I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance)
gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30>
instead of
gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30>
this way you have access to the glamour inspector. Unfortunately it does not have any window extent property.
Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument.
Nicolai
-- www.tudorgirba.com
"Every thing has its own flow"
Hi, Ok. Can you open a ticket about finding a solution for custom Inspector window size? Doru On Mon, Nov 24, 2014 at 3:54 PM, Clément Bera <bera.clement@gmail.com> wrote:
2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail.
The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else.
The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones.
But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account. I am even considering having this size cached by the class of the object (not sure yet if that makes sense). What do you think?
Hello Doru,
If we have a mechanism to remember the last size of the inspector per class, it would be nice to provide in addition APIs to change this value. Perhaps I could put on a start-up script something like: MyClass initialInspectorSize: 1000@1000.
My issue is that on specific classes the inspector shows a big roassal visualization. When I inspect in a new window one of these objects, I need each time to enlarge the window to see the full visualization. If the previous size is saved or I can set the size somehow, it's fine for me.
Cheers,
Clement
Cheers, Doru
On Mon, Nov 24, 2014 at 12:57 PM, Nicolai Hess <nicolaihess@web.de> wrote:
2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
Hello,
I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large.
How can I do it ?
For example I would like something like that:
MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000
Clement
I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance)
gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30>
instead of
gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30>
this way you have access to the glamour inspector. Unfortunately it does not have any window extent property.
Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument.
Nicolai
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
2014-11-25 8:35 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Ok. Can you open a ticket about finding a solution for custom Inspector window size?
Done: https://pharo.fogbugz.com/f/cases/14541/Editing-the-default-inspector-window... Thanks Doru
Doru
On Mon, Nov 24, 2014 at 3:54 PM, Clément Bera <bera.clement@gmail.com> wrote:
2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail.
The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else.
The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones.
But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account. I am even considering having this size cached by the class of the object (not sure yet if that makes sense). What do you think?
Hello Doru,
If we have a mechanism to remember the last size of the inspector per class, it would be nice to provide in addition APIs to change this value. Perhaps I could put on a start-up script something like: MyClass initialInspectorSize: 1000@1000.
My issue is that on specific classes the inspector shows a big roassal visualization. When I inspect in a new window one of these objects, I need each time to enlarge the window to see the full visualization. If the previous size is saved or I can set the size somehow, it's fine for me.
Cheers,
Clement
Cheers, Doru
On Mon, Nov 24, 2014 at 12:57 PM, Nicolai Hess <nicolaihess@web.de> wrote:
2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
Hello,
I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large.
How can I do it ?
For example I would like something like that:
MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000
Clement
I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance)
gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30>
instead of
gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30>
this way you have access to the glamour inspector. Unfortunately it does not have any window extent property.
Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument.
Nicolai
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
Thanks. Doru On Fri, Nov 28, 2014 at 9:59 AM, Clément Bera <bera.clement@gmail.com> wrote:
2014-11-25 8:35 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Ok. Can you open a ticket about finding a solution for custom Inspector window size?
Done:
https://pharo.fogbugz.com/f/cases/14541/Editing-the-default-inspector-window...
Thanks Doru
Doru
On Mon, Nov 24, 2014 at 3:54 PM, Clément Bera <bera.clement@gmail.com> wrote:
2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail.
The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else.
The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones.
But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account. I am even considering having this size cached by the class of the object (not sure yet if that makes sense). What do you think?
Hello Doru,
If we have a mechanism to remember the last size of the inspector per class, it would be nice to provide in addition APIs to change this value. Perhaps I could put on a start-up script something like: MyClass initialInspectorSize: 1000@1000.
My issue is that on specific classes the inspector shows a big roassal visualization. When I inspect in a new window one of these objects, I need each time to enlarge the window to see the full visualization. If the previous size is saved or I can set the size somehow, it's fine for me.
Cheers,
Clement
Cheers, Doru
On Mon, Nov 24, 2014 at 12:57 PM, Nicolai Hess <nicolaihess@web.de> wrote:
2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
Hello,
I would like for specific objects to change the default window size of the glamour inspector (Basically a bigger window will be opened by default for these objects). This is because I extended my inspectors to provide roassal visualization that are quite large.
How can I do it ?
For example I would like something like that:
MyObject>>#gtInitialWindowExtent < gtInitialWindowExtent > ^ 800@1000
Clement
I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance)
gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30>
instead of
gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30>
this way you have access to the glamour inspector. Unfortunately it does not have any window extent property.
Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument.
Nicolai
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
participants (5)
-
Ben Coman -
Clément Bera -
Nicolai Hess -
Thierry Goubier -
Tudor Girba