March 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Git (gitfiletree) on Pharo vs Windows

by Ben Coman

On Sun, Mar 1, 2015 at 5:19 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 01/03/2015 09:54, Jan B. a Ã©crit : > >> A Pharo gui for git would be an excellent thing. As you (and Alan Kay) >> know, >> simple things should be simple, complex things should be possible... With >> git itself and its command line, there are lots of complex things >> possible, >> but my opinion is that simple thing are far from simple with git. >> > > I do agree with you on that simple things are far from simple with git ;) > and complex things are complex, and things that we shouldn't be doing are > possible :) > > Nice example of git gui I personally like is github for mac (and github >> for >> windows). >> https://mac.github.com https://windows.github.com >> > > :( No mac, no windows here... > > Of course, it is just for github, but it contains all things one usually >> needs for commiting, branching etc. in the gui and if something is not so >> simple, it has command line, too. >> > > I think this 'GUI for usual things', 'command line for the rest' is > probably the pragmatic solution. > > So, just for inspiration of overall design... how hard implementation for >> git in general might be, that is another thing. >> > > There is a possibility there, which is offered by libcgit integration in > Pharo. If one wanted to do a full GUI integration, then it could be easier > to do it that way (i.e. low-level access to git concepts, better mastery of > those concepts since their understanding is needed when integrating into > Pharo).. instead of a high-level flying overhead like GitFileTree does. > > Max, Esteban, what do you think? > > The other one is to focus on VCS overall, and to consider Monticello GUI > refactoring to support concepts such as branches and external merging, so > that it could be portable to other VCS (svn, mercurial, bazaar) and support > whatever flow is needed out there (see my point during PharoDays 2015). > > It could even allow us to let branches appear in .mcz repositories :) > > Thierry > I believe there would be some advantage to having a general git GUI app on Pharo for: * providing a test bed for Pharo libcgit integration * for others to get some familiarity with Pharo libcgit usage, before adapting any core Pharo to make use of it * it would be an app that "I" would have the power to add features to cheers -ben

March 1, 2015

New Pharo Collections: Question about MultiDictionary

by AlexanderBrenchev

Greetings to everyone. Recently i started my pre-bachelor's work called "New Collections for Pharo". ( introduction to my project <http://forum.world.st/New-Pharo-Collections-td4794762.html> ) I decided to start with the MultiDictionary. There is a very basic prototype available on my project page on smalltalkhub <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections> You can also read my post <http://pillarhub.pharocloud.com/hub/brenchev/duntw01nrp9hkz6a00qmi16c5> about this implementation on PillarHub. At this point, i need your help, users and developers of Pharo! Feel free to make your suggestions about functionality of MultiDictionary that you need. Also, I'll really appreciate your suggestions about code style and in programming with Pharo in general. Thank you and best wishes. -- View this message in context: http://forum.world.st/New-Pharo-Collections-Question-about-MultiDictionary-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 1, 2015

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

by Sven Van Caekenberghe

Arg, and on Linux it works too. Below the image layer, the normal Pharo code that we see, both the Socket plugin and the SSL plugin are three totally different implementations. This is really frustrating. The Mac code originates from *before* Mac OS X came on the scene ! Today, Mac OS X could probably use 99% of the Linux version. > On 01 Mar 2015, at 10:29, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > Hi, > > I tried on Windows, there it works. > > Sabine > > > > -- > View this message in context: http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 1, 2015

Re: [Pharo-users] SmaCC: First steps

by Thierry Goubier

Le 21/02/2015 17:36, stepharo a Ã©crit : > yes and I would love to see that documented in the chapter :) Need to make a part on pre-existing parsers in the SmaCC distribution: Smalltalk, C, Java, C#, Python. I've prepared two very limited examples for teaching purposes, illustrating: - symbol table creation and management: this is where some significant Smalltalk expertise is needed, and it hurts for students who haven't got any prior smalltalk knowledge. - if then else conditional evaluation with an AST and a visitor. Thierry

March 1, 2015

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

by Sabine Manaa

Hi, I tried on Windows, there it works. Sabine -- View this message in context: http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 1, 2015

Re: [Pharo-users] Git (gitfiletree) on Pharo vs Windows

by Thierry Goubier

Le 01/03/2015 09:54, Jan B. a Ã©crit : > A Pharo gui for git would be an excellent thing. As you (and Alan Kay) know, > simple things should be simple, complex things should be possible... With > git itself and its command line, there are lots of complex things possible, > but my opinion is that simple thing are far from simple with git. I do agree with you on that simple things are far from simple with git ;) and complex things are complex, and things that we shouldn't be doing are possible :) > Nice example of git gui I personally like is github for mac (and github for > windows). > https://mac.github.com https://windows.github.com :( No mac, no windows here... > Of course, it is just for github, but it contains all things one usually > needs for commiting, branching etc. in the gui and if something is not so > simple, it has command line, too. I think this 'GUI for usual things', 'command line for the rest' is probably the pragmatic solution. > So, just for inspiration of overall design... how hard implementation for > git in general might be, that is another thing. There is a possibility there, which is offered by libcgit integration in Pharo. If one wanted to do a full GUI integration, then it could be easier to do it that way (i.e. low-level access to git concepts, better mastery of those concepts since their understanding is needed when integrating into Pharo).. instead of a high-level flying overhead like GitFileTree does. Max, Esteban, what do you think? The other one is to focus on VCS overall, and to consider Monticello GUI refactoring to support concepts such as branches and external merging, so that it could be portable to other VCS (svn, mercurial, bazaar) and support whatever flow is needed out there (see my point during PharoDays 2015). It could even allow us to let branches appear in .mcz repositories :) Thierry

March 1, 2015

Re: [Pharo-users] Git (gitfiletree) on Pharo vs Windows

by Jan B.

A Pharo gui for git would be an excellent thing. As you (and Alan Kay) know, simple things should be simple, complex things should be possible... With git itself and its command line, there are lots of complex things possible, but my opinion is that simple thing are far from simple with git. Nice example of git gui I personally like is github for mac (and github for windows). https://mac.github.com https://windows.github.com Of course, it is just for github, but it contains all things one usually needs for commiting, branching etc. in the gui and if something is not so simple, it has command line, too. So, just for inspiration of overall design... how hard implementation for git in general might be, that is another thing. Jan Thierry Goubier wrote > Le 28/02/2015 00:49, HernÃ¡n Morales Durand a Ã©crit : > > But I haven't done a GUI over Git. It could be done, but would not be > that easy (and some of the existing Guis for Git, such as gitg, have > serious performance issues). > > Thierry -- View this message in context: http://forum.world.st/Git-gitfiletree-on-Pharo-vs-Windows-tp4806791p4808626… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 1, 2015

Re: [Pharo-users] SQLite3 - External module not found

by Julien Delplanque

Also, it would be great to give more details about the installation on Smalltalkhub (http://smalltalkhub.com/#!/~PharoExtras/NBSQLite3) and there is absolutely no details in http://smalltalkhub.com/#!/~TorstenBergmann/SQLite. I think it would be great to give precisions about the version of the lib etc Maybe also give the exact commands to have it fully working on each platforms? Who do I have to contact if I want to help by writing a little bit more about installation details? I mean no offense, I just want to help next people that will have troubles with that :p Julien

March 1, 2015

Re: [Pharo-users] SmaCC: First steps

by Thierry Goubier

Le 01/03/2015 09:13, kilon alios a Ã©crit : > > > I have this grammar definition in the python parser > > file_input: {{}} > | file_input <NEWLINE> {{}} > | file_input stmt 'statement' {{}} > ; > > So I would expect > a) the class to be name Pyfile_inputNode , instead is named > PyFileInputNode, why ? The naming scheme inside SmaCC removes the _ and capitalize the words :) > b) I would expect a "statement" instance variable in that class and > instead I get "statements" instance variable, why ? Because this two productions define a list of stmt (possibly empty) and the AST generation code notices that, so it adds an s to statement and prepare that instance variable to be an OrderedCollection. When I see the code doing that in SmaCC, I'm allways impressed. Ok, the theory behind is well known and not that complex, but the inference done (cascading through the grammar rules to fetch everything needed) is impressive (and basically fairly hard to master when you write a parser :(). Thierry

March 1, 2015

Re: [Pharo-users] SmaCC: First steps

by kilon alios

I have this grammar definition in the python parser file_input: {{}} | file_input <NEWLINE> {{}} | file_input stmt 'statement' {{}} ; So I would expect a) the class to be name Pyfile_inputNode , instead is named PyFileInputNode, why ? b) I would expect a "statement" instance variable in that class and instead I get "statements" instance variable, why ?

March 1, 2015