- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Levente Uzonyi

On Sun, 27 Sep 2015, Ferlicot D. Cyril wrote: > Le 27/09/2015 12:11, Dimitris Chloupis a Ã©crit : >> we have more than a nice Git integration. I have been using Github for >> my pharo project for over a year now without any issue, the last few >> months I have been using gitfiltree which is making it even easier. >> Definitely beats the alternatives . >> > > Hi! > > Did you try to use git on a big project with a team? Did you try to > merge .st files ? > I heard it's really annoying to merge files with meta informations on git. > > An other point is that git file tree will not work on Windows if we do > not fix the problem of the stdio. And a lot of people out of the > community use Windows, so this is not a issue we should forget. Most of > the people I know in company use Windows, so if we want to attract > people this problem need to be corrected. If there are so many windows users, then how can it be that none of them managed to explain what the actual problem with stdio handling is. I had asked about the problem a while ago, but I still haven't got an answer: http://forum.world.st/Google-Code-Shutdown-tt4814760.html#a4840937 . Levente > >> On Sun, Sep 27, 2015 at 12:58 PM Alexandre Bergel >> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> â¦ Pharo may be within the 30 most popular languages on Earth. >> The 30th languages has 3,253 repository. There are 2,635 on >> SmalltalkHub. >> >> I wish we had a nice Git integration. >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- > Cheers > Cyril > >

Sept. 28, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by phil＠highoctane.be

Well, there is some kind of but I was tired and the stream broke as my internet connection went bust. (and I should have done the full setup). Ah these things pile up. Still, one can see the trainwreck over here: https://www.livecoding.tv/philippeback/videos/ Pick the things with "git" in the tile. Phil On Mon, Sep 28, 2015 at 10:59 AM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > philippe.back(a)highoctane.be <philippe.back(a)gmail.com> writes: > > > It isn't. It is actually very easy to use git. > > > > Time for a video :-) > > > > Expect that for tomorrow. > > tomorrow is today :-). We expect it! > > Thanks Philippe > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

Sept. 28, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Dale Henrichs

On 9/27/15 11:53 PM, stepharo wrote: > > > Le 27/9/15 15:33, Peter UhnÃ¡k a Ã©crit : >> >> Because to me git is **really** complex. I do not talk about add >> push commit but rebase remote.... >> >> >> Git allows you to do complex things if you need them. >> But you can easily use git without ever needing rebase, filter-branch >> or whatnot. >> >> Everything that Monticello can do can be done with git easily >> (commit, push, pull, merge). >> It just gives you much more powerful tools. > > sure except that suddenly you do not know why you have to know the > arcanes part. > I think that git is not layered so you get exposed to a lot of details > even when you avoid. > May be having a set of git macros would help. Stef, I have been working on this problem for several years now with tODE and in tODE I've been able to build a project tool that handles the mundane everyday, commit/checkout/branch/push/pull operations using menu items ... this approach means that folks can choose to use a git workflow that matches their whims/needs --- without having to become intimately familiar with the more arcane bits of git. I did find that it is absolutely necessary to have a Smalltalk gui based git merge tool ... there are non-smalltalk merge tools out there, but I prefer to do my merges in the comfort of my Smalltalk development environment:) ... Another tool that is important is what I call `skew diff` and `skew merge` ... `skew` happens when a git repository on disk is checked out to a commit that differs from the commit when the packages were loaded into an image (think of an image that has been sitting unused for a couple of months). Metacello has features for making it possible to record the SHA of the commit present when a project is loaded from a git repository and my project tool compares this SHA with the current SHA of the git repository and notices when SHA skew occurs ... `skew diff` and `skew merge` were invented to help a developer understand the implications and repair (if necessary) - more often than not a simple load (or ignoring the skew) sufficient, but it is imperative that a developer be notified that this skew is present ... Sooooo, I think that Pharo-based tools can be built so that developers can go about there daily work without ever having to drop down to the git command-line (macros or no macros)... Dale

Sept. 28, 2015

Re: [Pharo-dev] PharoTouch Demo Video

by Stephan Eggermont

On 28-09-15 16:22, Marcus Denker wrote: > Pharo touch demo with the new OSWindows architecture, touch events, vector graphics using Athens and libsdl2. > > Thanks the people involved (specifically for the touch project Christopher Coat, Mervan Ougdane, Jan-Baptiste Arnaud, > Eric Lepors and Mathieu Lacaton) and to Thales for sponsoring this project. > > https://www.youtube.com/watch?v=ksyoGItedVg <https://www.youtube.com/watch?v=ksyoGItedVg> Nice. What kind of hardware do you need for this? Is it just a capacitive multi touch screen monitor that supports windows 8/10? Stephan

Sept. 28, 2015

Re: [Pharo-dev] Reflectivity: Links that de-install themselves (oneShot)

by Marcus Denker

> On 20 Sep 2015, at 16:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 19 Sep 2015, at 01:10, stepharo <stepharo(a)free.fr> wrote: >> >> Marcus I have a API design question >> >> when you offer >> >> options: #(optionOneShot); >> >> versus >> >> optionOneShot >> >> Do you do a perform of the arrays selectors? >> What is the benefit of options: > > I needed a mechanism for flags (stored not each in an ivar, as they normally > not active). As we have this mechanism in Opal already, I decided to use the > same pattern. > As in Opal, for all the pre-defined options we should not rely on perform: but > have explicit #optionOneShot getter/setter methods. I will add those later.. > DONE: https://pharo.fogbugz.com/f/cases/16654/test-for-optionOneShot-and-accessor… <https://pharo.fogbugz.com/f/cases/16654/test-for-optionOneShot-and-accessor…> Marcus

Sept. 28, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 28, 2015

[pharo-project/pharo-core] 306d76: 50345

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 306d7616cbcc0f10b4931ae71c3dc296869a8d35 https://github.com/pharo-project/pharo-core/commit/306d7616cbcc0f10b4931ae7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-28 (Mon, 28 Sep 2015) Changed paths: M Polymorph-Widgets.package/ThemeSettings.class/instance/menu/menuColor.st A Refactoring-Critics.package/PharoCriticRules.class/README.md A Refactoring-Critics.package/PharoCriticRules.class/class/accessing/pharoIntegrationLintRule.st A Refactoring-Critics.package/PharoCriticRules.class/class/default rules/pharoHardLintRules.st A Refactoring-Critics.package/PharoCriticRules.class/class/default rules/pharoSoftLintRules.st A Refactoring-Critics.package/PharoCriticRules.class/definition.st R Refactoring-Critics.package/RBCompositeLintRule.class/class/default rules/pharoHardLintRules.st R Refactoring-Critics.package/RBCompositeLintRule.class/class/default rules/pharoSoftLintRules.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50344.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50345.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50344.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50345.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/class/instance creation/openWithEnvironment_removeTestCase_.st R Tool-CriticBrowser.package/SelectRuleBrowser.class/class/instance creation/pharoIntegrationRules.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/definition.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/instance/accessing/items_.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/instance/api/addAllItems.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/instance/api/addItems.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/instance/api/nextAction.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/instance/api/removeAllItems.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/instance/api/removeItems.st M Tool-CriticBrowser.package/SelectRuleBrowser.class/instance/initialization/initialize.st A Tool-CriticBrowser.package/SelectRuleBrowser.class/instance/private/isSelected_.st Log Message: ----------- 50345 16652 Menues now have a very strange reddish color https://pharo.fogbugz.com/f/cases/16652 16631 Move integration rules to a PharoCriticRules class https://pharo.fogbugz.com/f/cases/16631 http://files.pharo.org/image/50/50345.zip

Sept. 28, 2015

PharoTouch Demo Video

by Marcus Denker

Pharo touch demo with the new OSWindows architecture, touch events, vector graphics using Athens and libsdl2. Thanks the people involved (specifically for the touch project Christopher Coat, Mervan Ougdane, Jan-Baptiste Arnaud, Eric Lepors and Mathieu Lacaton) and to Thales for sponsoring this project. https://www.youtube.com/watch?v=ksyoGItedVg <https://www.youtube.com/watch?v=ksyoGItedVg>

Sept. 28, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 07c9a0: 50344

by Marcus Denker

Yes, debug code left. I fixed it alreadyâ¦ I should have seen it when going through the diff... > On 28 Sep 2015, at 15:57, Henrik Nergaard <henrin10(a)student.uia.no> wrote: > > Yeah, that might be my mistake. > Looking into it now -> loading 16648 changes the color. > > Best regards, > Henrik > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Marcus Denker > Sent: Monday, September 28, 2015 3:44 PM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] [pharo-project/pharo-core] 07c9a0: 50344 > > There is some strange side effect that now the menus have a very odd reddish color. > > I guess this is caused somehow by 16648 or maybe even 16647? > > I added a new issue tracker entry for that: > > https://pharo.fogbugz.com/f/cases/16652/Menues-now-have-a-very-strange-redd… > > >> Log Message: >> ----------- >> 50344 >> 16647 Nautilus Variable Menu Improvement >> https://pharo.fogbugz.com/f/cases/16647 >> >> 16648 ThemeSettings protocol cleanup >> https://pharo.fogbugz.com/f/cases/16648 >> >> 16649 Links of Globals and Class Vars: implement all reifications + extend for Globals >> https://pharo.fogbugz.com/f/cases/16649 >> >> http://files.pharo.org/image/50/50344.zip >> >> > > >

Sept. 28, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 07c9a0: 50344

by Henrik Nergaard

Yeah, that might be my mistake. Looking into it now -> loading 16648 changes the color. Best regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Marcus Denker Sent: Monday, September 28, 2015 3:44 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] [pharo-project/pharo-core] 07c9a0: 50344 There is some strange side effect that now the menus have a very odd reddish color. I guess this is caused somehow by 16648 or maybe even 16647? I added a new issue tracker entry for that: https://pharo.fogbugz.com/f/cases/16652/Menues-now-have-a-very-strange-redd… > Log Message: > ----------- > 50344 > 16647 Nautilus Variable Menu Improvement > https://pharo.fogbugz.com/f/cases/16647 > > 16648 ThemeSettings protocol cleanup > https://pharo.fogbugz.com/f/cases/16648 > > 16649 Links of Globals and Class Vars: implement all reifications + extend for Globals > https://pharo.fogbugz.com/f/cases/16649 > > http://files.pharo.org/image/50/50344.zip > >

Sept. 28, 2015