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

[Hernán Morales Durand]

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 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 committed via fast-import.
>>
>
> I will check again with another project, but at first didn't see
> anything uploading after the fast-import.
> I will let you know, thank you.
>
> Hernán
>
>
>> Peter
>>
>> On Wed, Jan 24, 2018 at 2:17 PM, Hernán Morales Durand
>>  wrote:
>>>
>>> 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:
>>>
>>> Metacello new
>>> baseline: 'GitMigration';
>>> repository: 'github://peteruhnak/git-migration/repository';
>>> load
>>>
>>> 2) From (GitBash) command-line:
>>>
>>> cd /c/Users/{your_git_project_directory}
>>> git log --oneline -n 1
>>>
>>> 3)  Execute this script:
>>>
>>> | migration |
>>> migration := GitMigration on: '{your_sthub_user}/{project_name}'.
>>> migration cacheAllVersions.
>>> migration authors: { 'Your_Name' -> #('Your_Name'
>>> '')}.
>>> migration
>>> fastImportCodeToDirectory: 'repository'
>>> initialCommit: '' " copy/paste the id from the git log command in step
>>> 2)"
>>> to: 'import.txt'
>>>
>>> 4)
>>>
>>> git fast-import < /.../import.txt
>>> git reset --hard master
>>> git add *
>>> git commit -m "fast-import from SmalltalkHub"
>>> git push {project_name}
>>>
>>> or
>>>
>>> git push
>>>
>>>
>>> Let me know if there's something you would add to the workflow.
>>> Cheers,
>>>
>>> Hernán
>>>
>>

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

[Hernán Morales Durand]

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 committed via fast-import.
>

I will check again with another project, but at first didn't see
anything uploading after the fast-import.
I will let you know, thank you.

Hernán


> Peter
>
> On Wed, Jan 24, 2018 at 2:17 PM, Hernán Morales Durand
>  wrote:
>>
>> 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:
>>
>> Metacello new
>> baseline: 'GitMigration';
>> repository: 'github://peteruhnak/git-migration/repository';
>> load
>>
>> 2) From (GitBash) command-line:
>>
>> cd /c/Users/{your_git_project_directory}
>> git log --oneline -n 1
>>
>> 3)  Execute this script:
>>
>> | migration |
>> migration := GitMigration on: '{your_sthub_user}/{project_name}'.
>> migration cacheAllVersions.
>> migration authors: { 'Your_Name' -> #('Your_Name'
>> '')}.
>> migration
>> fastImportCodeToDirectory: 'repository'
>> initialCommit: '' " copy/paste the id from the git log command in step
>> 2)"
>> to: 'import.txt'
>>
>> 4)
>>
>> git fast-import < /.../import.txt
>> git reset --hard master
>> git add *
>> git commit -m "fast-import from SmalltalkHub"
>> git push {project_name}
>>
>> or
>>
>> git push
>>
>>
>> Let me know if there's something you would add to the workflow.
>> Cheers,
>>
>> Hernán
>>
>

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

[Stephane Ducasse]

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 Pharo in the context of IoT. The focus of this job is "Pharo on
>> embedded and mobile devices for the internet of things"
>>
>> With Pharo, we have developed over the last two years an interactive,
>> remote development environment. It allows embedded, headless software
>> running on typical raspberry pi class hardware to be developed and debugged
>> in an interactive way. It allows programmers to explore and change running
>> headless embedded programs from their desktop development machine.
>>
>> The next step will be to extend this infrastructure to cover the use case
>> of industrial use: Deployment. We want to build a middle-ware to manage,
>> authenticate and script deployed Pharo embedded installations.
>>
>> The engineer will help to develop the Pharo IoT infrastructure, especially
>> with a focus on industrial use:
>>
>> • Improve Pharo for a platform with an industrial focus.
>> • Work on a middleware to manage deployed Pharo instances.
>> • Realize two small demos: First, as an industrial IoT example, a
>> demo deployed on 20+ devices.
>>Demo 2: Pharo deployed on multiple mobile autonomous robots.
>> • Help with creating a website for PharoIOT.
>>
>>
>> We are looking for a candidate with some prior experience with Pharo.
>> In addition:
>>
>> • Knowledge in Dynamic Languages (Pharo is a plus but not
>> required)
>> • Experience with embedded development is a plus but not required
>> • English
>>
>> Work in a research lab, but no paper writing, no teaching, no
>> administration. In addition:
>>
>> • Centrally located (one hour from Paris, 1h20 from London, 35 min
>> from Brussels)
>> • Try a lot of good beer (our office is just 10km from the border
>> to Belgium)
>> • Program with Pharo all day!
>> • Lille is an active city but not expensive (lot of students...),
>> centrally located with good connections by train to everywhere (including
>> CDG and Brussels airports).
>> • Duration: 12 Month
>> • Starting date:  As soon as possible (Spring 2018)
>> • Salary: 2600-3200 euros brut / month, depending on experience
>> • Explanation Salary: french brutto = money after social charges
>> (and base health insurance) before income tax, which is max one month income
>> payed
>>   yearly, depending on family situation (can be 0 for a family
>> with kids)
>> • Location: Lille (no remote job possible))
>>
>> More about
>>
>> • Pharo: http://www.pharo.org
>> • PharoThings: https://github.com/pharo-iot/PharoThings
>> • INRIA RMOD: http://rmod.lille.inria.fr
>> • INRIA Lille: http://www.inria.fr/lille
>> • INRIA in General: http://www.inria.fr
>> • Lille:
>> • http://en.wikipedia.org/wiki/Lille
>> • http://wikitravel.org/en/Lille
>>
>> Do not hesitate to contact us for more information.
>> Permanent Link to this call: https://rmod.inria.fr/web/blog/2017-10-20

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

[Stephane Ducasse]

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 most collection libraries I know there is the "take" function coming from 
>> the functional world that does that:
>>
>> #(1 2 3 4 5 6 7 8) take: 5
>>   => #(1 2 3 4 5)
>>
>> #(1 2 3 4) take: 5
>>   => #(1 2 3 4)
>>
>> Now, I understand there are two different things in here.
>>  - First is the fact that we would like to apply this iterator to more than 
>> sequenceable collections. I think that the name "take" is order agnostic in 
>> that sense.
>>  - The other thing is that people would like to not calculate the 
>> sub-collection... The problem is that we will end up with ugly combinations 
>> of selectors like
>>
>> take:thenDo:
>> take:thenCollect:
>> take:thenSelect:
>> ...
>>
>> And that pattern already exists also for:
>>
>> select:thenCollect:
>> select:thenDo:
>>
>> collect:as:
>> select:as:
>>
>> ...
>>
>> I think I would like to have a more composable kind of 
>> iterators/collections. There are Transducers that make "iterators" kind of 
>> command objects that you can apply on a collection. Personally I don't like 
>> the API choice but the idea behind is nice:
>>
>> https://github.com/Pharophile/Transducers
>>
>> sum := #+ init: 0.
>> sum1 := #(1 1 1) reduce: sum.
>> sum2 := (1 to: 1000) transduce: #odd filter reduce: sum.
>>
>>
>> And there are XTreams that allows one to work on a collection as a stream 
>> and then compose decorators on top. This means however that we need to 
>> create a stream and "close" it to obtain the resulting collection on every 
>> manipulation.
>>
>> https://github.com/mkobetic/Xtreams
>> https://code.google.com/archive/p/xtreams/wikis/Core.wiki
>>
>> ((aCollection reading collect: [ ... ]) select: [ ... ]) rest.
>>
>> Guille
>>
>> On Mon, Jan 22, 2018 at 4:11 AM, Ben Coman  wrote:
>> On 22 January 2018 at 00:47, Stephane Ducasse  
>> wrote:
>> > Hi Ben and Clement
>> >
>> > I have a collection (a dictionary in my case) and I want to get
>> > maximum 5 bindings out of it and iterate on them.
>> > I want keysAndValuesDo: or do: but only up to 5 elements.
>> >
>> > aDict atMax: 5 do: [:each | ]
>>
>> "atMax" sound a bit like comparison rather than counting. Perhaps
>> better would be...
>> aDict atMost: 5 do: [:each | ]   "or"
>> aDict for: 5 do: [:each | ]
>>
>> but rather than introduce three or more messages...
>> aDict atMost: 5 do: [:each| ... ]
>> aDict atMost: 5 select: [:each| ... ]
>> aDict atMost: 5 collect: [:each| ... ]
>>
>> why not introduce just one method?
>> (aDict any: 5) do: [:each| ... ]
>> (aDict any: 5) select: [:each| ... ]
>> (aDict any: 5) collect: [:each| ... ]
>>
>>
>> cheers -ben
>>
>>
>> > So I learned from:to:do:
>> >
>> > aCollection atMax: 5 do: [:each | ]
>> >
>> > Does it make sense?
>> >
>> > Stef
>> >
>> > On Sun, Jan 21, 2018 at 1:16 PM, Clément Bera  
>> > wrote:
>> >> I don't think we do. Do you need it on SequenceableCollection or
>> >> HashedCollection too ?
>> >>
>> >> Recently I was trying to iterate over the first N elements of a collection
>> >> and since there was no #first:do: I used #from:to:do:. I guess you could 
>> >> use
>> >> that too:
>> >>
>> >> aCollection from: 1 to: (aCollection size min: 1000) do: aBlock
>> >>
>> >> Which guarantees you iterate at max over 1000 elements. But that API is
>> >> SequenceableCollection specific.
>> >>
>> >> On Sun, Jan 21, 2018 at 11:44 AM, Ben Coman  wrote:
>> >>>
>> >>> On 21 January 2018 at 18:36, Stephane Ducasse 
>> >>> wrote:
>> >>> > Hi
>> >>> >
>> >>> > I would like to iterate at max on a certain amount of elements in a
>> >>> > collection.
>> >>> > And I was wondering if we have such iterator.
>> >>>
>> >>> I'm not clear what functionality your asking for.  Could you present
>> >>> it as code & result if you assumed the iterator you want was
>> >>> available?
>> >>>
>> >>> cheers -ben
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Clément Béra
>> >> Pharo consortium engineer
>> >> https://clementbera.wordpress.com/
>> >> Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
>> >
>>
>>
>>
>>
>> --
>>
>> Guille Polito
>> Research Engineer
>>
>> Centre de Recherche en Informatique, Signal et Automatique de Lille
>> CRIStAL - UMR 9189
>> French National Center for Scientific Research - http://www.cnrs.fr
>>
>> Web: http://guillep.github.io
>> Phone: +33 06 52 70 66 13
>
>

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

[Stephane Ducasse]

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 composable
> and do not generate intermediate representations.
> The bad news are, that the Pharo port is incomplete and I won't have the
> time until April to finish it.

oh there is not stress.
What I would like to see is
- what is the API in terms of vocabulary (ie drop the same as reject)
- can we reexpress some of our iterators? what is the cost?

Stef

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

[Ben Coman]

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 or fashion languages were
>> included.
>> I wrote a message to add Pharo Smalltalk to the list so let's see...
>>
>>
> Thank you Hernan.
> ​Let's see !​
>
>
> By the way, there are problems available on http://rosalind.info/problems/
> list-view/
> if you want to use Pharo on BioInformatics problems.
>
> Is this possible to rename the #adventofcode channel on Discord to
> #code-contests so be can use this channel
> with all code contests ?
>

Good idea. Its done.
Might be good to pin a link to a wiki page listing upcoming contests.

cheers -ben

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

[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 committed via fast-import.

Peter

On Wed, Jan 24, 2018 at 2:17 PM, Hernán Morales Durand <
hernan.mora...@gmail.com> wrote:

> 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:
>
> Metacello new
> baseline: 'GitMigration';
> repository: 'github://peteruhnak/git-migration/repository';
> load
>
> 2) From (GitBash) command-line:
>
> cd /c/Users/{your_git_project_directory}
> git log --oneline -n 1
>
> 3)  Execute this script:
>
> | migration |
> migration := GitMigration on: '{your_sthub_user}/{project_name}'.
> migration cacheAllVersions.
> migration authors: { 'Your_Name' -> #('Your_Name' ' >')}.
> migration
> fastImportCodeToDirectory: 'repository'
> initialCommit: '' " copy/paste the id from the git log command in step
> 2)"
> to: 'import.txt'
>
> 4)
>
> git fast-import < /.../import.txt
> git reset --hard master
> git add *
> git commit -m "fast-import from SmalltalkHub"
> git push {project_name}
>
> or
>
> git push
>
>
> Let me know if there's something you would add to the workflow.
> Cheers,
>
> Hernán
>
>

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

[Serge Stinckwich]

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 let's see...
>
>
Thank you Hernan.
​Let's see !​


By the way, there are problems available on http://rosalind.info/problems/
list-view/
if you want to use Pharo on BioInformatics problems.

Is this possible to rename the #adventofcode channel on Discord to
#code-contests so be can use this channel
with all code contests ?

​Regards,​

-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

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

[Hernán Morales Durand]

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 :

> 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: serge.stinckw...@gmail.com
>
>
>
> 
>
> Dear SergeStinckwich,
>
> This year the Bioinformatics Contest 2018  will
> start on February 3. Mark your calendars and compete with thousands of
> people worldwide in bioinformatics problem solving!
>
>
> [image: Bioinformatics Contest 2018] 
>
> *Important dates:*
>
>- *Feb 3-11*: Qualification Round. You need to solve a couple of
>problems anytime during this week to qualify for the finals.
>- *Feb 24*: Final Round. 24 hours to solve as many problems as you can!
>
> *Participate:*
>
> Both rounds will be organized online on Stepik platform. Registration is
> already open! 
>
> You can also subscribe to the contest news and updates on
> http://bioinf.me/contest.
>
> Last year more than 3000 participants from 86 countries all over the world
> had participated in the contest. Last year problem sets —
> https://stepik.org/course/945/, final standings —
> http://bioinf.me/online/contest2017/standings.
>
> Good luck and have fun!
>
> <3,
> Rosalind Team
> http://rosalind.info
> 
> To stop receiving similar future emails from Rosalind, please click here
> .
> Please do not reply directly to this email.
>
>
>
> --
> Serge Stinckwich
> UMI UMMISCO 209 (IRD/UPMC/UY1)
> "Programs must be written for people to read, and only incidentally for
> machines to execute."http://www.doesnotunderstand.org/
>

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

[Hernán Morales Durand]

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:

Metacello new
baseline: 'GitMigration';
repository: 'github://peteruhnak/git-migration/repository';
load

2) From (GitBash) command-line:

cd /c/Users/{your_git_project_directory}
git log --oneline -n 1

3)  Execute this script:

| migration |
migration := GitMigration on: '{your_sthub_user}/{project_name}'.
migration cacheAllVersions.
migration authors: { 'Your_Name' -> #('Your_Name' '')}.
migration
fastImportCodeToDirectory: 'repository'
initialCommit: '' " copy/paste the id from the git log command in step 2)"
to: 'import.txt'

4)

git fast-import < /.../import.txt
git reset --hard master
git add *
git commit -m "fast-import from SmalltalkHub"
git push {project_name}

or

git push


Let me know if there's something you would add to the workflow.
Cheers,

Hernán

[Pharo-users] Fwd: Bioinformatics Contest 2018

[Serge Stinckwich]

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: serge.stinckw...@gmail.com




Dear SergeStinckwich,

This year the Bioinformatics Contest 2018  will
start on February 3. Mark your calendars and compete with thousands of
people worldwide in bioinformatics problem solving!


[image: Bioinformatics Contest 2018] 

*Important dates:*

   - *Feb 3-11*: Qualification Round. You need to solve a couple of
   problems anytime during this week to qualify for the finals.
   - *Feb 24*: Final Round. 24 hours to solve as many problems as you can!

*Participate:*

Both rounds will be organized online on Stepik platform. Registration is
already open! 

You can also subscribe to the contest news and updates on
http://bioinf.me/contest.

Last year more than 3000 participants from 86 countries all over the world
had participated in the contest. Last year problem sets —
https://stepik.org/course/945/, final standings — http://bioinf.me/online/
contest2017/standings.

Good luck and have fun!

<3,
Rosalind Team
http://rosalind.info

To stop receiving similar future emails from Rosalind, please click here
.
Please do not reply directly to this email.



-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

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

[Esteban A. Maringolo]

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

[Stephan Eggermont]

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:
If you don't have problems that Iceberg would solve now, wait and use
Monticello. There are significant improvements coming in the Iceberg
workflow. 

Stephan

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

[Esteban Lorenzano]

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 available.

You should use Iceberg. 

Esteban

> 
> thanks
> Sanjay
> 
> 
> 
> 
> 
> -
> ---
> Regards, Sanjay
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 

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

[Sanjay Minni]

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: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html