Re: [Pharo-users] Positive experience report porting from StHub to GitHub

Ok, checked again with a new repo at https://github.com/hernanmd/ISO3166 And yes, the commit command is unnecessary, the fast-import and push did it. Thanks, Hernán 2018-01-24 18:08 GMT-03:00 Hernán Morales Durand : > Hi Peter, > > 2018-01-24 11:50 GMT-03:00 Peter

Re: [Pharo-users] Positive experience report porting from StHub to GitHub

Hi Peter, 2018-01-24 11:50 GMT-03:00 Peter Uhnák : > Hi Hernan, this should be in principle sufficient for the migration. > > I just wonder, why these two lines? >> git add * >> git commit -m "fast-import from SmalltalkHub" > > ...normally all the code should've been already

Re: [Pharo-users] [JOB] Engineer 1 year: Pharo IoT platform

We have also a PhD on the same topics!!! On Mon, Jan 22, 2018 at 2:08 PM, Miguel Campusano wrote: > > On Mon, Jan 22, 2018 at 6:17 AM Marcus Denker > wrote: >> >> Inria RMoD are looking for a full-time engineer for helping with >> developing

Re: [Pharo-users] looking for another iterator :)

I like the pharophile :) On Mon, Jan 22, 2018 at 10:57 AM, Sven Van Caekenberghe wrote: > yes, we need composition to avoid API explosion (things are already very bad > in this respect) > >> On 22 Jan 2018, at 10:38, Guillermo Polito wrote: >> >> In

Re: [Pharo-users] looking for another iterator :)

On Mon, Jan 22, 2018 at 11:26 AM, Steffen Märcker wrote: > Hi! > > this is straightforward with Transducers, e.g., > >> (Take n: 5) <~ #(1 2 3 4 5 6 7 8). > > or >> >> #(1 2 3 4 5 6 7 8) transduce take: 5. > > > The different primitives like take, drop, map, filter, etc. are

Re: [Pharo-users] Fwd: Bioinformatics Contest 2018

On 24 January 2018 at 21:30, Serge Stinckwich wrote: > > > On Wed, Jan 24, 2018 at 2:25 PM, Hernán Morales Durand < > hernan.mora...@gmail.com> wrote: > >> Hi Serge, >> >> Thanks for sharing, didn't knew about the contest. >> I saw the language list. Only mainstream

Re: [Pharo-users] Positive experience report porting from StHub to GitHub

Hi Hernan, this should be in principle sufficient for the migration. I just wonder, why these two lines? > git add * > git commit -m "fast-import from SmalltalkHub" ...normally all the code should've been already committed via fast-import. Peter On Wed, Jan 24, 2018 at 2:17 PM, Hernán Morales

Re: [Pharo-users] Fwd: Bioinformatics Contest 2018

On Wed, Jan 24, 2018 at 2:25 PM, Hernán Morales Durand < hernan.mora...@gmail.com> wrote: > Hi Serge, > > Thanks for sharing, didn't knew about the contest. > I saw the language list. Only mainstream or fashion languages were > included. > I wrote a message to add Pharo Smalltalk to the list so

Re: [Pharo-users] Fwd: Bioinformatics Contest 2018

Hi Serge, Thanks for sharing, didn't knew about the contest. I saw the language list. Only mainstream or fashion languages were included. I wrote a message to add Pharo Smalltalk to the list so let's see... Cheers, Hernán 2018-01-24 10:16 GMT-03:00 Serge Stinckwich

[Pharo-users] Positive experience report porting from StHub to GitHub

Hi guys, I just want to report that I started to migrate some of my projects from to GitHub (for example https://github.com/hernanmd/ApplicationSecurity and https://github.com/hernanmd/StringExtensions) in Pharo 6.x Basically the steps are: 1) Install the Peter Uhnak git-migration package:

[Pharo-users] Fwd: Bioinformatics Contest 2018

There is a new code contest, this time about BioInformatics, but unfortunately the list of languages supported does not include Pharo ... -- Forwarded message -- From: Rosalind Team Date: Wed, Jan 24, 2018 at 9:15 AM Subject: Bioinformatics Contest 2018 To:

Re: [Pharo-users] looking for another iterator :)

2018-01-22 6:57 GMT-03:00 Sven Van Caekenberghe : > yes, we need composition to avoid API explosion (things are already very bad > in this respect) And the names of the proposed selectors suggests it could be even worst. +1 to composition. Esteban A. Maringolo

Re: [Pharo-users] Monticello or Iceberg ... which to use

Sanjay Minni wrote: > How to decide between which one to use - Monticello or Iceberg. > > We have code in bitbucket. > at this time code is being shared only between a small developer group. > It is not intended to be publicly available. If you are talking production code:

Re: [Pharo-users] Monticello or Iceberg ... which to use

Hi, > On 24 Jan 2018, at 11:57, Sanjay Minni wrote: > > Hi > > How to decide between which one to use - Monticello or Iceberg. > > We have code in bitbucket. > at this time code is being shared only between a small developer group. > It is not intended to be publicly

[Pharo-users] Monticello or Iceberg ... which to use

Hi How to decide between which one to use - Monticello or Iceberg. We have code in bitbucket. at this time code is being shared only between a small developer group. It is not intended to be publicly available. thanks Sanjay - --- Regards, Sanjay -- Sent from: