November 2014 - Pharo-dev - lists.pharo.org

Pharo is mine

by kilon alios

>> I'm certainly a good example of that. My Pharo is mine! (and I have an IDE I like which is truly >> mine :P) >> And I can only encourage you to do the same ;) what you mean ? you have customised pharo for your needs ? care to share , I am very interested :)

Nov. 24, 2014

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

by Thierry Goubier

Le 24/11/2014 17:24, kilon alios a Ã©crit : > >> yes you are right, but also you are digressing :) > >> my question is simple: do you think this small change can help or is > useless? > > is it not enough that I said " I think it makes sense to display only > the name of the repository instead of its web location " ? > > My philosophy on GUI design is to keep it as simple as possible (noob > friendly )and make as customisable as possible (experienced user friendly). > > So in this case a section displaying paths can be made hidden by default > and the user will be able to make it unhidden. This way none will > complain or have a good reason to complain about the change and should > not be difficult to implement. Honestly, I don't see the point (and I'm an expert). A shortened (but complete) description is both good for the novice and the expert, it makes the code simpler, it makes the GUI aesthetically pleasing, it fasten the workflow of both novice and expert alike, and it helps the novice to become an expert. > I don't like the approach of monticello of "let put everything in a > single GUI " , its near impossible to understand it without > documentation and frankly its not that complex to justify this difficulty. I'd say that the main problem of Monticello is on its left side, not on the right... > >> For laptops monitors (i.e. the 1366x768 and 1440x900 that are fairly > common), some are too large: Nautilus, >>> GTPlayground. > > >> (But for GTPlayground, it may be on purpose :)) > > I happen to have such a laptop the 2010 macbook air. Lets be sincere > most coders have normal sided monitors (20''+ for desktop , 15''+ > laptop) and a FULL HD resolution is the standard nowdays. I have an air > but my main work is with retina 27'' 2013 imac. I use air when I am in > the move or just in the bed before going to sleep hacking pharo. I use that kind of setup (11.6" and 24"), but, still, in most laptops you have to consider that they are stuck at 1366x768 (what is the market share of retina macbooks?). > > I know coders that also love working with 2 monitors. I do, but they are hard to carry in a plane or in a train :P > Its impossible to create a design that fits all unless the gui is highly > dynamic like what modern websites are doing nowdays. Well, we had the techno in GUI more than 20 years ago, but the web is only now reinventing that (and badly at that). > So there is definetly a lot of room for improvement on GUI design for > Pharo and small size monitors is not the main reason to change the > design. A good excuse would be as Stef puts it most of time "we dont > have the people or the money to do this in the near future". > But even for me with retina display and 27'' the gui design is a big > issues because I end up opening tons of pharo windows. And that's why I'd say if you make it ok to deal with multiple windows on a 11"6 screen, then going to a 27" becomes pure bliss. > I hope I do my small part to help the overall gui experience with pharo > and maybe others will join too to make "pharo is yours" reality. I'm certainly a good example of that. My Pharo is mine! (and I have an IDE I like which is truly mine :P) And I can only encourage you to do the same ;) Thierry

Nov. 24, 2014

Re: [Pharo-dev] How to import an icon inside Pharo

by Esteban Lorenzano

nononoâ¦. Iâm not the guy behind that code! I just made some adapts to make it work (probably in the time of FileSystem migration and Eclipse icon set) but I do not take responsibility of itâ¦ in the good and (specially) in the bad :) ahhâ¦ and I also move them to instance side (all logic of those classes were in class side, making the idea of âexchangeâ a bitâ¦ difficult) > On 24 Nov 2014, at 17:37, kilon alios <kilon.alios(a)gmail.com> wrote: > > ok I see also you are the guy behind the code. So now I know who to blame. > > By looking at the code it looks like it requires the size of the icon to be 64x64 and createIconMethodsFromFile reads a png file containing the icon and uses base64ContentsofFileNamed to create the string that contains the contents of the png icon file. > > Looks easy enough, clean code too. Apart from base64ContentsOfFileNamed: comment " "Private - convenient method"" :D at least you bother to comment. > > I dont understand this comment "self exportAllIconsAsGif" in the same name method, are the comments automatically generated this comments looks strange. that might be a remaining of older methods :/ Esteban > > On Mon, Nov 24, 2014 at 4:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > look in > > ThemeIcons around âprivate - utilitiesâ protocol. > > Esteban > > > On 24 Nov 2014, at 14:55, kilon alios <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > > > > Hey guys any idea how to import a icon inside pharo and how to use it ? I have seen that pharo uses a sort of string representation of the icon image . Anyone has experience with this ? > > >

Nov. 24, 2014

Re: [Pharo-dev] How to import an icon inside Pharo

by kilon alios

ok I see also you are the guy behind the code. So now I know who to blame. By looking at the code it looks like it requires the size of the icon to be 64x64 and createIconMethodsFromFile reads a png file containing the icon and uses base64ContentsofFileNamed to create the string that contains the contents of the png icon file. Looks easy enough, clean code too. Apart from base64ContentsOfFileNamed: comment " "Private - convenient method"" :D at least you bother to comment. I dont understand this comment "self exportAllIconsAsGif" in the same name method, are the comments automatically generated this comments looks strange. On Mon, Nov 24, 2014 at 4:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > look in > > ThemeIcons around âprivate - utilitiesâ protocol. > > Esteban > > > On 24 Nov 2014, at 14:55, kilon alios <kilon.alios(a)gmail.com> wrote: > > > > Hey guys any idea how to import a icon inside pharo and how to use it ? > I have seen that pharo uses a sort of string representation of the icon > image . Anyone has experience with this ? > > >

Nov. 24, 2014

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

by kilon alios

>> yes you are right, but also you are digressing :) >> my question is simple: do you think this small change can help or is useless? is it not enough that I said " I think it makes sense to display only the name of the repository instead of its web location " ? My philosophy on GUI design is to keep it as simple as possible (noob friendly )and make as customisable as possible (experienced user friendly). So in this case a section displaying paths can be made hidden by default and the user will be able to make it unhidden. This way none will complain or have a good reason to complain about the change and should not be difficult to implement. I don't like the approach of monticello of "let put everything in a single GUI " , its near impossible to understand it without documentation and frankly its not that complex to justify this difficulty. >> For laptops monitors (i.e. the 1366x768 and 1440x900 that are fairly common), some are too large: Nautilus, >> GTPlayground. >> (But for GTPlayground, it may be on purpose :)) I happen to have such a laptop the 2010 macbook air. Lets be sincere most coders have normal sided monitors (20''+ for desktop , 15''+ laptop) and a FULL HD resolution is the standard nowdays. I have an air but my main work is with retina 27'' 2013 imac. I use air when I am in the move or just in the bed before going to sleep hacking pharo. I know coders that also love working with 2 monitors. Its impossible to create a design that fits all unless the gui is highly dynamic like what modern websites are doing nowdays. So there is definetly a lot of room for improvement on GUI design for Pharo and small size monitors is not the main reason to change the design. A good excuse would be as Stef puts it most of time "we dont have the people or the money to do this in the near future". But even for me with retina display and 27'' the gui design is a big issues because I end up opening tons of pharo windows. I hope I do my small part to help the overall gui experience with pharo and maybe others will join too to make "pharo is yours" reality.

Nov. 24, 2014

[pharo-project/pharo-core] 27151e: 40384

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 27151ed904db256d72e83d85722db500969b23b9 https://github.com/pharo-project/pharo-core/commit/27151ed904db256d72e83d85… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-24 (Mon, 24 Nov 2014) Changed paths: A Kernel.package/SmallInteger.class/class/class initialization/initialize.st A Kernel.package/SmallInteger.class/class/class initialization/startUp_.st M Kernel.package/SmallInteger.class/class/constants/maxVal.st M Kernel.package/SmallInteger.class/class/constants/minVal.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script384.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40384.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SmalltalkImage.class/class/initialization/initializeStartUpList.st Log Message: ----------- 40384 14506 Add class inst vars to hold SmallInteger class>>minVal and maxVal. https://pharo.fogbugz.com/f/cases/14506 http://files.pharo.org/image/40/40384.zip

Nov. 24, 2014

[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