February 2017 - Pharo-users

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

by Offray Vladimir Luna CÃ¡rdenas

Hi Thierry, What I'm using is the Fossil JSON API as described in [1]. Managing Grafoscopio documentation with it is pretty easy and yes I believe it could help in bringing a unified API across several repositories (I have not tested that though). [1] http://fossil.wanderinghorse.net/repos/fwiki/index.cgi/wiki/README Cheers, Offray On 28/02/17 10:26, Thierry Goubier wrote: > Hi Offray, > > is your FossilRepo object using a JSON over HTTP API to Fossil? It > could make Fossil an interesting candidate, because it could mean a > single http API (and not one API per git hosting provider...) > > Regards, > > Thierry > > 2017-02-28 16:09 GMT+01:00 Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>>: > > I'm also curious about iceberg integration. I'm also an advocate > for fossil: I like its lightness as process and software, offering > full stack distributed collaboration in just 2 Mb (wiki, tickets, > DVCS, etc.) I can not catch up with upcoming Pharo 6, but > hopefully after being released I will be able to test fossil > stuff, particularly because is the chosen collaboration backend > for Grafoscopio. > > BTW, when installing Grafoscopio you get a FossilRepo object that > is used to query Fossil repositories via the JSON API and update > documentation. Still in early stages, but I will experiment how > Pierce's Fossil support give a more cohesive user experience when > working with publication and collaboration of interactive notebooks. > > Cheers, > > Offray > > > > On 28/02/17 02:12, stepharong wrote: > > This is cool. > I'm curious to see if we could manage fossil back-end via iceberg. > > Stef > > > On Tue, 28 Feb 2017 01:19:50 +0100, Pierce Ng > <pierce(a)samadhiweb.com <mailto:pierce@samadhiweb.com>> wrote: > > Hi all, > I have written a simple integration of FileTree with > Fossil to avoid the 2-step > Pharo- and shell-level work to add/delete/commit files. > At the operating system command prompt, init a new Fossil > project: > os% mkdir ~/repo > os% cd ~/repo > os% fossil init myproject.fossil > project-id: 3c05c3016eeabf8e87816ee218c6a86d3c87b950 > server-id: ff42bc86dba1a26b1d94b64685f7c09d02581617 > admin-user: laptop-user (initial password is "1fe2ff") > Open the repository: > os% mkdir ~/myproject > os% cd ~/myproject > os% fossil open ~/repo/myproject.fossil > In a fresh Pharo 6 image - I used v60411 - install > FossilFileTree: > Metacello new > baseline: 'FossilFileTree'; > repository: 'github://PierceNg/FossilFileTree'; > load. > Write code in Pharo. Open Monticello Browser. Add a > "fossilfiletree" > repository, using ~/myproject as the directory. Save to > said repository > from within Monticello Browser. Done. > Full blog post here: > http://www.samadhiweb.com/blog/2017.02.28.fossil.filetree.html > <http://www.samadhiweb.com/blog/2017.02.28.fossil.filetree.html> > Pierce > > > > > >

Feb. 28, 2017

Re: [Pharo-users] suggestions mini-pane shut up

by Raffaello Giulietti

Thanks Peter, this does it for me. > 1. Open settings > 2. Type in quality > 3. Uncheck nautilus plugin > > (or remove the plugin via top-right corner of nautilus window -> plugins manager -> remove QA) > > Peter

Feb. 28, 2017

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

by Thierry Goubier

Hi Offray, is your FossilRepo object using a JSON over HTTP API to Fossil? It could make Fossil an interesting candidate, because it could mean a single http API (and not one API per git hosting provider...) Regards, Thierry 2017-02-28 16:09 GMT+01:00 Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com>: > I'm also curious about iceberg integration. I'm also an advocate for > fossil: I like its lightness as process and software, offering full stack > distributed collaboration in just 2 Mb (wiki, tickets, DVCS, etc.) I can > not catch up with upcoming Pharo 6, but hopefully after being released I > will be able to test fossil stuff, particularly because is the chosen > collaboration backend for Grafoscopio. > > BTW, when installing Grafoscopio you get a FossilRepo object that is used > to query Fossil repositories via the JSON API and update documentation. > Still in early stages, but I will experiment how Pierce's Fossil support > give a more cohesive user experience when working with publication and > collaboration of interactive notebooks. > > Cheers, > > Offray > > > > On 28/02/17 02:12, stepharong wrote: > >> This is cool. >> I'm curious to see if we could manage fossil back-end via iceberg. >> >> Stef >> >> >> On Tue, 28 Feb 2017 01:19:50 +0100, Pierce Ng <pierce(a)samadhiweb.com> >> wrote: >> >> Hi all, >>> I have written a simple integration of FileTree with Fossil to avoid the >>> 2-step >>> Pharo- and shell-level work to add/delete/commit files. >>> At the operating system command prompt, init a new Fossil project: >>> os% mkdir ~/repo >>> os% cd ~/repo >>> os% fossil init myproject.fossil >>> project-id: 3c05c3016eeabf8e87816ee218c6a86d3c87b950 >>> server-id: ff42bc86dba1a26b1d94b64685f7c09d02581617 >>> admin-user: laptop-user (initial password is "1fe2ff") >>> Open the repository: >>> os% mkdir ~/myproject >>> os% cd ~/myproject >>> os% fossil open ~/repo/myproject.fossil >>> In a fresh Pharo 6 image - I used v60411 - install FossilFileTree: >>> Metacello new >>> baseline: 'FossilFileTree'; >>> repository: 'github://PierceNg/FossilFileTree'; >>> load. >>> Write code in Pharo. Open Monticello Browser. Add a "fossilfiletree" >>> repository, using ~/myproject as the directory. Save to said repository >>> from within Monticello Browser. Done. >>> Full blog post here: >>> http://www.samadhiweb.com/blog/2017.02.28.fossil.filetree.html >>> Pierce >>> >> >> >> > >

Feb. 28, 2017

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

by Thierry Goubier

2017-02-28 8:12 GMT+01:00 stepharong <stepharong(a)free.fr>: > This is cool. > I'm curious to see if we could manage fossil back-end via iceberg. > It is a nice use case to check on an architecture for Iceberg with multiple back-ends. Thierry > > Stef > > > > On Tue, 28 Feb 2017 01:19:50 +0100, Pierce Ng <pierce(a)samadhiweb.com> > wrote: > > Hi all, >> I have written a simple integration of FileTree with Fossil to avoid the >> 2-step >> Pharo- and shell-level work to add/delete/commit files. >> At the operating system command prompt, init a new Fossil project: >> os% mkdir ~/repo >> os% cd ~/repo >> os% fossil init myproject.fossil >> project-id: 3c05c3016eeabf8e87816ee218c6a86d3c87b950 >> server-id: ff42bc86dba1a26b1d94b64685f7c09d02581617 >> admin-user: laptop-user (initial password is "1fe2ff") >> Open the repository: >> os% mkdir ~/myproject >> os% cd ~/myproject >> os% fossil open ~/repo/myproject.fossil >> In a fresh Pharo 6 image - I used v60411 - install FossilFileTree: >> Metacello new >> baseline: 'FossilFileTree'; >> repository: 'github://PierceNg/FossilFileTree'; >> load. >> Write code in Pharo. Open Monticello Browser. Add a "fossilfiletree" >> repository, using ~/myproject as the directory. Save to said repository >> from within Monticello Browser. Done. >> Full blog post here: >> http://www.samadhiweb.com/blog/2017.02.28.fossil.filetree.html >> Pierce >> > > > -- > Using Opera's mail client: http://www.opera.com/mail/ > >

Feb. 28, 2017

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

by Thierry Goubier

2017-02-28 1:19 GMT+01:00 Pierce Ng <pierce(a)samadhiweb.com>: > Hi all, > > I have written a simple integration of FileTree with Fossil to avoid the > 2-step > Pharo- and shell-level work to add/delete/commit files. > > At the operating system command prompt, init a new Fossil project: > > os% mkdir ~/repo > os% cd ~/repo > os% fossil init myproject.fossil > project-id: 3c05c3016eeabf8e87816ee218c6a86d3c87b950 > server-id: ff42bc86dba1a26b1d94b64685f7c09d02581617 > admin-user: laptop-user (initial password is "1fe2ff") > > Open the repository: > > os% mkdir ~/myproject > os% cd ~/myproject > os% fossil open ~/repo/myproject.fossil > > In a fresh Pharo 6 image - I used v60411 - install FossilFileTree: > > Metacello new > baseline: 'FossilFileTree'; > repository: 'github://PierceNg/FossilFileTree'; > load. > > Write code in Pharo. Open Monticello Browser. Add a "fossilfiletree" > repository, using ~/myproject as the directory. Save to said repository > from within Monticello Browser. Done. > > Full blog post here: > > http://www.samadhiweb.com/blog/2017.02.28.fossil.filetree.html > > Pierce > > > Congratulations! This was one of my objectives with GitFileTree: open up the Pharo infrastructure to other DVCS such as Fossil. How does Fossil handles merging the FileTree format? Regards, Thierry

Feb. 28, 2017

Re: [Pharo-users] Fwd: GSoC 2017: Pharo Consortium has been accepted as a mentor organization!

by Offray Vladimir Luna CÃ¡rdenas

Do you mean, besides the form filled out for the Grafoscopio proposal?[1] If I need to register some where else, just point me. I'm all in :-). [1] http://gsoc.pharo.org/#topic-grafoscopio-literate-computing-and-reproducibl… Cheers, Offray On 28/02/17 01:19, serge.stinckwich(a)gmail.com wrote: > Hi Offray, > You will register as a student ? > See you > > EnvoyÃ© de mon iPhone > > Le 28 fÃ©vr. 2017 Ã 04:30, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> a Ã©crit : > >> Congratulations for this and thanks for all the work behind... this >> will be an interesting summer! >> >> Cheers, >> >> Offray >> >> >> >> On 27/02/17 12:07, Serge Stinckwich wrote: >>> Great news ! >>> >>> Thank you Jigyasa, Uko, Peter and Alex for your great work this year ! >>> >>> >>> ---------- Forwarded message ---------- >>> From: *Google Summer of Code* <summerofcode-noreply(a)google.com >>> <mailto:summerofcode-noreply@google.com>> >>> Date: Mon, Feb 27, 2017 at 6:00 PM >>> Subject: GSoC 2017: Pharo Consortium has been accepted as a mentor >>> organization! >>> To: sergestinckwich(a)gmail.com <mailto:sergestinckwich@gmail.com> >>> >>> >>> >>> >>> Google Summer of Code >>> >>> Congratulations! Pharo Consortium has been selected as a Google >>> Summer of Code 2017 mentor organization. >>> >>> You can now invite mentors and update your organization profile. >>> >>> Please click here to visit your dashboard: >>> https://summerofcode.withgoogle.com/dashboard/ >>> <https://summerofcode.withgoogle.com/dashboard/> >>> >>> >>> >>> >>> >>> >>> This email was sent to serge.stinckwich(a)gmail.com >>> <http://serge.stinckwich@gmail.com>. >>> >>> You are receiving this email because of your participation in Google >>> Summer of Code 2017. >>> https://summerofcode.withgoogle.com >>> <https://summerofcode.withgoogle.com> >>> >>> To leave the program and stop receiving all emails, you can go to >>> your profile >>> <https://summerofcode.withgoogle.com/dashboard/profile/> and request >>> deletion of your program profile. >>> >>> For any questions, please contact gsoc-support(a)google.com >>> <mailto:gsoc-support@google.com>. Replies to this message go to an >>> unmonitored mailbox. >>> >>> Â© 2017 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA >>> 94043, USA >>> >>> >>> >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UCBN & UMI UMMISCO 209 (IRD/UPMC) >>> Every DSL ends up being Smalltalk >>> http://www.doesnotunderstand.org/ >>

Feb. 28, 2017

Re: [Pharo-users] Proof of Concept: FileTree and Fossil

by Offray Vladimir Luna CÃ¡rdenas

I'm also curious about iceberg integration. I'm also an advocate for fossil: I like its lightness as process and software, offering full stack distributed collaboration in just 2 Mb (wiki, tickets, DVCS, etc.) I can not catch up with upcoming Pharo 6, but hopefully after being released I will be able to test fossil stuff, particularly because is the chosen collaboration backend for Grafoscopio. BTW, when installing Grafoscopio you get a FossilRepo object that is used to query Fossil repositories via the JSON API and update documentation. Still in early stages, but I will experiment how Pierce's Fossil support give a more cohesive user experience when working with publication and collaboration of interactive notebooks. Cheers, Offray On 28/02/17 02:12, stepharong wrote: > This is cool. > I'm curious to see if we could manage fossil back-end via iceberg. > > Stef > > > On Tue, 28 Feb 2017 01:19:50 +0100, Pierce Ng <pierce(a)samadhiweb.com> > wrote: > >> Hi all, >> I have written a simple integration of FileTree with Fossil to avoid >> the 2-step >> Pharo- and shell-level work to add/delete/commit files. >> At the operating system command prompt, init a new Fossil project: >> os% mkdir ~/repo >> os% cd ~/repo >> os% fossil init myproject.fossil >> project-id: 3c05c3016eeabf8e87816ee218c6a86d3c87b950 >> server-id: ff42bc86dba1a26b1d94b64685f7c09d02581617 >> admin-user: laptop-user (initial password is "1fe2ff") >> Open the repository: >> os% mkdir ~/myproject >> os% cd ~/myproject >> os% fossil open ~/repo/myproject.fossil >> In a fresh Pharo 6 image - I used v60411 - install FossilFileTree: >> Metacello new >> baseline: 'FossilFileTree'; >> repository: 'github://PierceNg/FossilFileTree'; >> load. >> Write code in Pharo. Open Monticello Browser. Add a "fossilfiletree" >> repository, using ~/myproject as the directory. Save to said repository >> from within Monticello Browser. Done. >> Full blog post here: >> http://www.samadhiweb.com/blog/2017.02.28.fossil.filetree.html >> Pierce > >

Feb. 28, 2017

Pharo TechTalk starting in one hour (16UTC) (LINKS)

by Esteban Lorenzano

Hi, So, techtalk will be here: https://www.youtube.com/watch?v=H52MAu_ISgU <https://www.youtube.com/watch?v=H52MAu_ISgU> and discussion channel will be through discord, as always, here: http://discord.gg/Sj2rhxn <http://discord.gg/Sj2rhxn> See you there! Esteban

Feb. 28, 2017

Re: [Pharo-users] suggestions mini-pane shut up

by Peter Uhnak

1. Open settings 2. Type in quality 3. Uncheck nautilus plugin (or remove the plugin via top-right corner of nautilus window -> plugins manager -> remove QA) Peter On Tue, Feb 28, 2017 at 03:16:31PM +0100, Raffaello Giulietti wrote: > I'm using the latest "official" release, namely Pharo 5. I have no > gut to experiment with Pharo 6. > > If not by the GUI, there still must be a way to evaluate some > expression to achieve the same effect, even in Pharo 5. > > > > > > On 2017-02-28 15:11, Sven Van Caekenberghe wrote: > >What Pharo version are you using ? > > > >The screenshot was from Pharo 6. > > > >>On 28 Feb 2017, at 15:06, Raffaello Giulietti <raffaello.giulietti(a)lifeware.ch> wrote: > >> > >>Hi Sven, > >> > >>I already searched in the settings. > >> > >>Here is what I see in the Nautilus Browser settings: > >> > >>Code Browsing > >> Nautilus Browser > >> Show hierarchy by default? > >> Use old style keys? > >> > >>nothing else. > >> > >> > >> > >> > >> > >>On 2017-02-28 14:55, Sven Van Caekenberghe wrote: > >>> > >>>>On 28 Feb 2017, at 14:49, Raffaello Giulietti <raffaello.giulietti(a)lifeware.ch> wrote: > >>>> > >>>>Hi, > >>>> > >>>>I find the suggestions mini-pane that appears under a method code rather useless and distracting. > >>>> > >>>>I perfectly know that I'm an idiot, so there's no need for the tool to keep reminding me how smart it is instead. > >>>> > >>>>Is there a way to get rid of it? > >>> > >>>Experiment with the Nautilus Settings: > >>> > >>><Mail Attachment.png> > >>> > >>>In particular 'Show critique list at the bottom' and 'Show source code annotation pane'. > >>> > >>>Sven > >>> > >> > > > > > >

Feb. 28, 2017

Re: [Pharo-users] suggestions mini-pane shut up

by Raffaello Giulietti

On 2017-02-28 15:12, Dimitris Chloupis wrote: > which version of Pharo you use ? > > PS: I do not need QA to remind me I am an idiot, coding is doing that > to me every day just fine for 30 years now :D > Fully agree with you ;-) Anyway, I want to be in control of the tools.

Feb. 28, 2017