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

Re: [Pharo-dev] GUI question

by Alain Plantec

On 28 juin 2014, at 09:45, stepharo <stepharo(a)free.fr> wrote: > >> Hi all, >> >> is there a rationale for the world menu on left mouse button only in Pharo 4? (and world contents on the right mouse button) > > Simplifying mouseDown: following the cleaning made on Bloc by alain. > It was strange to have two different ways to show the list of windows and also wht left and right should do the same. > In Pharo 3.0 I get the same (see attachement) menu. So I do not understand how useful it is. > This idea of meta and operate looks a bit old fashioned to me (totgther with the defaultYellowButtonPressed kind of code :) > > Morphic is a gigantic beast and removing complexity is the only way. Now if you have an good argument post of fix. Stephane, I think Thierry is right, and the menu invocation button can be easily changed. We should follow the user interface standards. right button -> world menu (contextual menu) left button -> selection/multi-selection/dragging Cheers Alain > > Stef >> >> Mine would be: >> - if I press a pull down menu (press a menu bar item or a pull down menu), it's the left mouse button. >> - If I look for a menu on a non-button thing, it's the right mouse button, i.e. contextual menu. >> >> Now, should I consider that the Pharo background is a huge pull-down menu button to understand the rationale behind having the world menu on the left-mouse button? >> >> Thierry > > <Screen Shot 2014-06-28 at 09.44.06.pdf>

June 28, 2014

Re: [Pharo-dev] Contact of HwaJong Oh

by NISHIHARA Satoshi

or follow on twitter and send message. https://twitter.com/Daliot 2014-06-28 17:27 GMT+09:00 Max Leske <maxleske(a)gmail.com>: > Copied from one of his messages on the list: daliot.oh(a)gmail.com > > > On 28.06.2014, at 09:56, stepharo <stepharo(a)free.fr> wrote: > >> Hi guys >> >> I'm looking for the email of HwaJong Oh. Does anybody of you have it? >> >> Stef >> > > -- -- "NISHIHARA Satoshi" [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

June 28, 2014

Re: [Pharo-dev] Contact of HwaJong Oh

by Max Leske

Copied from one of his messages on the list: daliot.oh(a)gmail.com On 28.06.2014, at 09:56, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > I'm looking for the email of HwaJong Oh. Does anybody of you have it? > > Stef >

June 28, 2014

Re: [Pharo-dev] How to get started with Git and Pharo?

by stepharo

thanks Now is there a tutorial? Beause http://forum.world.st/Pharo-git-td4693999.html scared me. On 27/6/14 15:53, Goubier Thierry wrote: > > > Le 26/06/2014 19:11, Yuriy Tymchuk a Ã©crit : >> I can only suggest you to read my blogpost about configurations and >> versioning: >> http://sleepycoders.blogspot.ch/2014/04/how-to-distribute-your-github-pharo… >> >> I usually mix filetree and gitfiletree. Last one is better, because >> you donât have to remember to commit in git each time you commit in >> pharo. >> (Also I think that gitfiletree is not working with Pharo4) > > Now it works with Pharo4! > > Thierry

June 28, 2014

Re: [Pharo-dev] How to get started with Git and Pharo?

by stepharo

I use git for my books. Now the simple fact that a tool has to help me to do simple action is a sign of strange design. This is the same as Java design and eclipse. When you code without eclipse you will a real pain :) I found the git API far to low level from my developer perspective and this is what I would like the pharo abstraction to protect our users (while getting the benefits from git). And this is why when esteban is telling that this is what newbies expect I cannot believe such kind of statements because there are simply bullshit. :) Stef > Stef, > > You need to cut your teeth for a decent couple hours to get to terms > with Git. > Especially when using a workflow with branches, with merges, and > several contributors. > I knew of quite a couple of SCMs (including Hg) but Git is a special > beast. > > I liked Git Recipes: A Problem Solution Approach as it was very pragmatic. > > HTH > Phil > > > On Thu, Jun 26, 2014 at 7:09 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > I read > > http://www.stic.st/wp-content/conferences/2012/Wednesday/1415-Practical_Git… > and I found > http://forum.world.st/Pharo-git-td4693999.html > > But is there something that works and it simple? > > Stef > > > On 26/6/14 18:27, stepharo wrote: > > Hi > > I do not know the dif between git file tree, file tree.... and > I would like to know how to get > started with git in Pharo? > > What should I read? > > Stef > > > >

June 28, 2014

Re: [Pharo-dev] How to get started with Git and Pharo?

by stepharo

Esteban My old age taught me to be suspicious when everything is so black and white. I do not think that everything will be so nice. And for me git is not github. Stef On 26/6/14 20:52, Esteban Lorenzano wrote: > On 26 Jun 2014, at 14:56, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 26 Jun 2014, at 19:07, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >> >>> I think that it is possible to most if not all of the git work support into the Smalltalk development environment ... I am doing that for GemStone with tODE[6] and I do find myself going to the go to the command line much less frequently ... but in tODE I have built a git merge tool and a git diff tool ... you can get the git history of a method from the browser, etc. >>> >>> Without a relatively high degree of tool integration it can be clunky to use git ... I am very willing to share what I've done/learned in tODE with Pharo tool builders and of course I think Thierry Goubier has actually been ahead of me in several different areas ... >> That is my analysis: it works today, 'perfectly', but there is not enough tools support to make it as easy as Monticello as a whole is today. >> >> If these tools exist, or we can build them quickly based Dale's code, that would be cool (I guess its all OSProcess underneath, which I find so/so, a direct integration is better) that would be good. >> >> Would having this change our world fundamentally ? No, IMHO >> Is it worth the effort, is the ROI there ? I don't think so > I disagree here. I think moving our development to git will change deeply (for good) our community processes and then I think it totally worths the effort. > Of course, important part of the advantages came from the tools around git (like github) more than git itself, but all is one and the same :) > A couple of examples of what I think will improve our work: > - pull requests instead SLICES > - submodules (with different people taking care of them) > - traceability: you can map an issue with a pull requests directly making it a lot better to query > > Then there is other kind of advantages like: > - better entry-point for newbies to the community (they all expect something like git this days) > - better visibility > - confidence. This is subjective but important: companies feel more confident with something like git than a specific tool to keep their sources. > - we can stop maintaining things like smalltalkhub and important parts of monticello itself and concentrate our efforts in other, more interesting areas > > â¦ and there are more. > > In conclusion, I think expending time in git integration is one of the best ways to contribute to the develop of Pharo nowadays. > > Esteban > >> Anyway, it is a delicate subject as it also touches on the representation of the file format. >> >> > >

June 28, 2014

Re: [Pharo-dev] How to get started with Git and Pharo?

by stepharo

thank dale. I'm using thunderbid and sometimes I have some mails that I do not see and I have to query explicitly. I will read this full thread and the doc. stef On 26/6/14 19:07, Dale Henrichs wrote: > Stef, > > My introduction to git came largely from reading "A successful Git > branching model"[1]. I tried to think how to map this particular git > work flow to Metacello and long story short, decided to adapt > Metacello to git:) > > It is also probably worth reading "What is a good Git workflow?"[2]. > This article is more about how to use GitHub, but frankly the appeal > of git to me goes hand in hand with a good collaboration model and > GitHub does a good job supporting that. > > The first time you read these articles don't pay attention to the > details, but try to get the overall flow/functionality and try to draw > parallels to the work the you do with Monticello and Metacello ... let > the thoughts marinate, ask some questions. > > "Pro Git"[3] is a book/web site and would recommend that you take a > run through Chapter 2[4] to get a taste of git in action at the > command line and virtually everything that you need to know to work on > your own with git is covered in this chapter. Chapter 3[5] is on the > nitty gritty of branching ... but again at this stage you want to just > skim through the docs and get a feel of what is possible ... if > something doesn't make sense at this stage ... > ignore it:) > > Now go back to the "What is a good Git workflow?"[2] paper and read > it in detail ... if you see a command/operation that you don't > understand google it or look it up in "Pro Git" or ask questions ... > > Basically I am recommending that for your first foray into Git and > Smalltalk you will be trying to follow the "What is a good Git > workflow?"[2] model. > > FileTree allows you save Monticello packages into a git repository, > but with FileTree you have to do all of the git commands from the > command line. > > I'll let Thierry Goubier describe GitFileTree because I think it that > package does a bit of remote control .... > > I think that it is possible to most if not all of the git work support > into the Smalltalk development environment ... I am doing that for > GemStone with tODE[6] and I do find myself going to the go to the > command line much less frequently ... but in tODE I have built a git > merge tool and a git diff tool ... you can get the git history of a > method from the browser, etc. > > Without a relatively high degree of tool integration it can be clunky > to use git ... I am very willing to share what I've done/learned in > tODE with Pharo tool builders and of course I think Thierry Goubier > has actually been ahead of me in several different areas ... > > Of course there are other git workflows out there and other git > collaboration sites besides GitHub...but is worth keeping things > simple at first (I think) and when you have mastered git/github basics > both personally and from a tool level, then it is a perfectly good > time to start looking at other workflows and tools, because then you > are able to make informed judgements ... > > HTH, > > Dale > > [1] http://nvie.com/posts/a-successful-git-branching-model/ > [2] https://help.github.com/articles/what-is-a-good-git-workflow > [3] http://git-scm.com/book > [4] http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository > [5] http://git-scm.com/book/en/Git-Branching > [6] https://github.com/dalehenrich/tode > > > On Thu, Jun 26, 2014 at 9:27 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > I do not know the dif between git file tree, file tree.... and I > would like to know how to get > started with git in Pharo? > > What should I read? > > Stef > >

June 28, 2014

Contact of HwaJong Oh

by stepharo

Hi guys I'm looking for the email of HwaJong Oh. Does anybody of you have it? Stef

June 28, 2014

Re: [Pharo-dev] GUI question

by stepharo

> Hi all, > > is there a rationale for the world menu on left mouse button only in > Pharo 4? (and world contents on the right mouse button) Simplifying mouseDown: following the cleaning made on Bloc by alain. It was strange to have two different ways to show the list of windows and also wht left and right should do the same. In Pharo 3.0 I get the same (see attachement) menu. So I do not understand how useful it is. This idea of meta and operate looks a bit old fashioned to me (totgther with the defaultYellowButtonPressed kind of code :) Morphic is a gigantic beast and removing complexity is the only way. Now if you have an good argument post of fix. Stef > > Mine would be: > - if I press a pull down menu (press a menu bar item or a pull down > menu), it's the left mouse button. > - If I look for a menu on a non-button thing, it's the right mouse > button, i.e. contextual menu. > > Now, should I consider that the Pharo background is a huge pull-down > menu button to understand the rationale behind having the world menu > on the left-mouse button? > > Thierry

June 28, 2014

Re: [Pharo-dev] Spec TreeModel

by stepharo

For your info, I'm slowly going all the polymorph widget examples and truning them into single example to identify what are the widgets that we should - improve - remove Having 3 versions of the same is killing us. Ben fixed a lot of problems like merging multi/single selection but there is still a lot of work to do. So I started to reorganize the packages to help us finding our way doing this analysis. Stef On 27/6/14 11:28, Yuriy Tymchuk wrote: > Hi, > > Iâd like to improve the TreeModel of Spec, but I need some help. > > Fist of all UI breaks when different theme is used: > > When you deselect checkbox and at that moment item is not highlighted. > This happens when checkbox is clicked, the item is not highlighted and > so itâs original color is not stored, but when you uncheck item it IS > unhighlighted for some reason, and as default color is not stored, > black one is used. First of all we can replace black color by theme > color, and also I think that we should handle checkbox and list clicks > in a separate manner. Now the other thing is related. I can turn on > checkbox, but can I turn off the list selection? Are the selected > items distinguished is any way, or all items with checked checkboxes > and highlights merged into one list? > > Uko >

June 28, 2014