- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40384 Home: https://github.com/pharo-project/pharo-core

Nov. 24, 2014

Re: [Pharo-dev] changing MC repository url display

by Thierry Goubier

2014-11-24 16:13 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > https://pharo.fogbugz.com/f/cases/14523 > > and there is a SLICE there with an initial version but honestly, I'm not > happy (names are still lost in the path). > of course, it would be better if we can add repository types in other > font/size/color so they do not interfere, but that is a lot of work and I > cannot tackle it now... if someone wants to take the glove. it would be super > cool :) > Not bad. File paths can be made logic or relative (~ instead of /Users/esteban), and we can have a small database of typical repository ( http://smalltalkhub.com could be replaced by smalltalkhub). Pharo/Pharo40(Smalltalkhub) is nice. Or maybe reversed (Smalltalkhub)Pharo/Pharo40 (if you know that the window is large enough) because you can classify starting with the type. I'll try to do the same on the gitfiletree entries (and it will apply on Pharo3 as well :)). Thierry > (maybe is time to replace mc browser with glamour/spec version... I know > there is an experimental spec version, which is broken) > > > > Esteban > > On 24 Nov 2014, at 15:23, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > 2014-11-24 15:20 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> It will certainly help. Ideally, we should have this string displaying >> method in the MCRepository hierarchy. >> > > It already is in that hierarchy, along with the creation info and edit. > Each repository type can customize it. > > Thierry > > > >> Cheers, >> Doru >> >> >> On Mon, Nov 24, 2014 at 3:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> yes you are right, but also you are digressing :) >>> my question is simple: do you think this small change can help or is >>> useless? >>> >>> Esteban >>> >>> > On 24 Nov 2014, at 14:54, kilon alios <kilon.alios(a)gmail.com> wrote: >>> > >>> > to be fair the pharo windows in general are tiny. I can imagine them >>> being ok on 1-2 decades old monitors but for modern monitors they are just >>> too small. I think it makes sense to display only the name of the >>> repository instead of its web location . I would like now that pharo offers >>> good support for git, separate icons for diffirent kinds of repos. Actually >>> talking about icons I think I will start a new thread on it. >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > >

Nov. 24, 2014

Re: [Pharo-dev] changing MC repository url display

by Esteban Lorenzano

https://pharo.fogbugz.com/f/cases/14523 <https://pharo.fogbugz.com/f/cases/14523> and there is a SLICE there with an initial version but honestly, Iâm not happy (names are still lost in the path). of course, it would be better if we can add repository types in other font/size/color so they do not interfere, but that is a lot of work and I cannot tackle it nowâ¦ if someone wants to take the glove. it would be super cool :) (maybe is time to replace mc browser with glamour/spec versionâ¦ I know there is an experimental spec version, which is broken) Esteban > On 24 Nov 2014, at 15:23, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2014-11-24 15:20 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>>: > It will certainly help. Ideally, we should have this string displaying method in the MCRepository hierarchy. > > It already is in that hierarchy, along with the creation info and edit. Each repository type can customize it. > > Thierry > > > > Cheers, > Doru > > > On Mon, Nov 24, 2014 at 3:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > yes you are right, but also you are digressing :) > my question is simple: do you think this small change can help or is useless? > > Esteban > > > On 24 Nov 2014, at 14:54, kilon alios <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > > > > to be fair the pharo windows in general are tiny. I can imagine them being ok on 1-2 decades old monitors but for modern monitors they are just too small. I think it makes sense to display only the name of the repository instead of its web location . I would like now that pharo offers good support for git, separate icons for diffirent kinds of repos. Actually talking about icons I think I will start a new thread on it. > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow" >

Nov. 24, 2014

Re: [Pharo-dev] editing the default window size of glamour inspector

by Thierry Goubier

2014-11-24 16:00 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > > > 2014-11-24 15:54 GMT+01:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > >> >> >> 2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor(a)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(a)web.de> >>> wrote: >>> >>>> 2014-11-12 15:14 GMT+01:00 ClÃ©ment Bera <bera.clement(a)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" >>> >> >> >

Nov. 24, 2014

Re: [Pharo-dev] editing the default window size of glamour inspector

by Thierry Goubier

2014-11-24 15:54 GMT+01:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > > > 2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor(a)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(a)web.de> >> wrote: >> >>> 2014-11-12 15:14 GMT+01:00 ClÃ©ment Bera <bera.clement(a)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" >> > >

Nov. 24, 2014

Re: [Pharo-dev] editing the default window size of glamour inspector

by ClÃ©ment Bera

2014-11-24 13:11 GMT+01:00 Tudor Girba <tudor(a)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(a)web.de> wrote: > >> 2014-11-12 15:14 GMT+01:00 ClÃ©ment Bera <bera.clement(a)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" >

Nov. 24, 2014

Re: [Pharo-dev] [ANN] OnScreenKeyboard

by J.F. Rick

Well, that is a part I haven't gotten to. I only have the looks of it done. Plus it is only for Athens graphics. I do plan on making it work with multi-touch, but that's also something that will probably take some work. Currently, I don't have a multi-touch machine to make progress. Once I get it, we'll see. Cheers, Jeff On Mon, Nov 24, 2014 at 9:34 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > where can I find your code? > > I would like to see the emulation of touchpad too (where whole device > screen acts as a touchpad. Something like TouchMousePointer > application [1]). Because this is currently the only usable way how to > control Pharo on tablets. > > ...And Pharo is usable on tablets because this OnScreenKeyboard > package was WHOLE created on a small 8" tablet and partly in a bus > without any attached additional hardware ;-) > > [1] http://www.lovesummertrue.com/touchmousepointer/en-us/ > > Cheers, > -- Pavel > > 2014-11-24 15:13 GMT+01:00 J.F. Rick <self(a)je77.com>: > > Awesome. I've been working on an onscreen keyboard as well. Perhaps we > can > > join forces, though it will be a while before I can continue to work on > it. > > > > Cheers, > > > > Jeff > > > > On Sat, Nov 22, 2014 at 2:55 PM, Pavel Krivanek < > pavel.krivanek(a)gmail.com> > > wrote: > >> > >> Hi, > >> > >> I created the first version of a virtual keyboard morph for Pharo. To > >> try it, evaluate: > >> > >> Gofer it > >> url: > >> 'http://www.smalltalkhub.com/mc/PavelKrivanek/OnScreenKeyboard/main'; > >> package: 'OnScreenKeyboard'; > >> load. > >> > >> OnScreenKeyboard new open. > >> > >> Currently it doesn't work well together with completion morphs so > >> please disable code completion. > >> > >> Features: > >> - splitted int two parts > >> - compact look > >> - swipe up to write uppercase letter > >> - swipe left to do backspace > >> - swipe down to write special character > >> - swipe right to write numbers and other special characters > >> - swipe up right to press combination with ctrl (e.g. ctrl+p) > >> - swipe down right to press combination with alt > >> - press Kb button to move the keyboard up and down on the screen > >> - press shift/alt/ctrl keys to hold them (e.g. for selecting text with > >> cursor keys and shift) > >> > >> Feel free to send patches and improvements directly to the project > >> repository :-) > >> > >> Cheers, > >> -- Pavel > > > > > > > > > > -- > > Jochen "Jeff" Rick, Ph.D. > > http://www.je77.com/ > > Skype ID: jochenrick > > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Nov. 24, 2014

Re: [Pharo-dev] [ANN] OnScreenKeyboard

by Pavel Krivanek

Hi, where can I find your code? I would like to see the emulation of touchpad too (where whole device screen acts as a touchpad. Something like TouchMousePointer application [1]). Because this is currently the only usable way how to control Pharo on tablets. ...And Pharo is usable on tablets because this OnScreenKeyboard package was WHOLE created on a small 8" tablet and partly in a bus without any attached additional hardware ;-) [1] http://www.lovesummertrue.com/touchmousepointer/en-us/ Cheers, -- Pavel 2014-11-24 15:13 GMT+01:00 J.F. Rick <self(a)je77.com>: > Awesome. I've been working on an onscreen keyboard as well. Perhaps we can > join forces, though it will be a while before I can continue to work on it. > > Cheers, > > Jeff > > On Sat, Nov 22, 2014 at 2:55 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: >> >> Hi, >> >> I created the first version of a virtual keyboard morph for Pharo. To >> try it, evaluate: >> >> Gofer it >> url: >> 'http://www.smalltalkhub.com/mc/PavelKrivanek/OnScreenKeyboard/main'; >> package: 'OnScreenKeyboard'; >> load. >> >> OnScreenKeyboard new open. >> >> Currently it doesn't work well together with completion morphs so >> please disable code completion. >> >> Features: >> - splitted int two parts >> - compact look >> - swipe up to write uppercase letter >> - swipe left to do backspace >> - swipe down to write special character >> - swipe right to write numbers and other special characters >> - swipe up right to press combination with ctrl (e.g. ctrl+p) >> - swipe down right to press combination with alt >> - press Kb button to move the keyboard up and down on the screen >> - press shift/alt/ctrl keys to hold them (e.g. for selecting text with >> cursor keys and shift) >> >> Feel free to send patches and improvements directly to the project >> repository :-) >> >> Cheers, >> -- Pavel > > > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick

Nov. 24, 2014

Re: [Pharo-dev] changing MC repository url display

by Thierry Goubier

2014-11-24 15:20 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > It will certainly help. Ideally, we should have this string displaying > method in the MCRepository hierarchy. > It already is in that hierarchy, along with the creation info and edit. Each repository type can customize it. Thierry > Cheers, > Doru > > > On Mon, Nov 24, 2014 at 3:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> yes you are right, but also you are digressing :) >> my question is simple: do you think this small change can help or is >> useless? >> >> Esteban >> >> > On 24 Nov 2014, at 14:54, kilon alios <kilon.alios(a)gmail.com> wrote: >> > >> > to be fair the pharo windows in general are tiny. I can imagine them >> being ok on 1-2 decades old monitors but for modern monitors they are just >> too small. I think it makes sense to display only the name of the >> repository instead of its web location . I would like now that pharo offers >> good support for git, separate icons for diffirent kinds of repos. Actually >> talking about icons I think I will start a new thread on it. >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 24, 2014

Re: [Pharo-dev] changing MC repository url display

by Tudor Girba

It will certainly help. Ideally, we should have this string displaying method in the MCRepository hierarchy. Cheers, Doru On Mon, Nov 24, 2014 at 3:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yes you are right, but also you are digressing :) > my question is simple: do you think this small change can help or is > useless? > > Esteban > > > On 24 Nov 2014, at 14:54, kilon alios <kilon.alios(a)gmail.com> wrote: > > > > to be fair the pharo windows in general are tiny. I can imagine them > being ok on 1-2 decades old monitors but for modern monitors they are just > too small. I think it makes sense to display only the name of the > repository instead of its web location . I would like now that pharo offers > good support for git, separate icons for diffirent kinds of repos. Actually > talking about icons I think I will start a new thread on it. > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 24, 2014