December 2017 - Pharo-users

Re: [Pharo-users] Metacello with Git

by Dale Henrichs

On 12/20/17 2:53 AM, Vitor Medina Cruz wrote: > > These days, we are getting to the point where I am beginning to > flip the question on it's head and begin thinking that it should > be possible forÂ a developer to choose to have have the github:// > url interpreted as "create a local clone of the remote repository" > instead of "download a tarball of the remote repository" . With > this approach it should be possible to include gitlab url support > as well since the gitlab issue is related to the specific handling > of repository tarballs.. > > > UsingÂ 'git clone --depth=1'Â don't do the trick and leave the process > both efficient and general accross all git repos? At the time that github:// was added (5 years ago now?) git could not be counted upon to be installed by the folks who may be interested in depending upon a project hosted on github, so the tarball approach was used so that those brave souls interested in using git and github could do so without forcing everyone elseÂ to start using git ... nowadays with git becoming part of the mainstream dev env for Smalltalk, git (or libgit2 in the case of pharo) can be counted on to be available ... > > > > On Tue, Dec 19, 2017 at 4:49 PM, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> wrote: > > BitBucket is supported with like Github with: > butbucket://<butbucket_path>/<srcpath>. > > With regards to GitLab, their download zip format is/was different > enough from BitBucket/Github to make it difficult to provide the > same level of support. See the series of comments here[1]. > > When the github:// was first introduced it was done in such a way > that users of projects on GitHub did not have to have git > installed on their local computers ... it was a way to make it > possible for folks to begin using git without requiring everyone > to install git ... > > These days, we are getting to the point where I am beginning to > flip the question on it's head and begin thinking that it should > be possible forÂ a developer to choose to have have the github:// > url interpreted as "create a local clone of the remote repository" > instead of "download a tarball of the remote repository" . With > this approach it should be possible to include gitlab url support > as well since the gitlab issue is related to the specific handling > of repository tarballs... > > ... there are current discussions in this area on these two issues > [2] and [3]. > > Dale > > [1] > https://github.com/Metacello/metacello/issues/287#issuecomment-59815235 > <https://github.com/Metacello/metacello/issues/287#issuecomment-59815235> > > [2] https://github.com/Metacello/metacello/issues/474 > <https://github.com/Metacello/metacello/issues/474> > > [3] https://github.com/Metacello/metacello/issues/475 > <https://github.com/Metacello/metacello/issues/475> > > > > On 12/19/17 10:25 AM, Vitor Medina Cruz wrote: > > Hello, > > Using github://<github_path>/<srcpath> metacello works fine, > but is there another more general way of refering to a remote > git repo? From BitBucket or Gitlab for example. > > Regards, > Vitor > > > >

Dec. 20, 2017

Re: [Pharo-users] Metacello with Git

by Pierce Ng

On Tue, Dec 19, 2017 at 07:07:16PM -0800, Dale Henrichs wrote: > I am under the impression that iceberg is able to authenticate with > SSH keys .... I am not a pharo/iceberg user myself, but it seems > that iceberg should be able to fill that gap. Iceberg does, with RSA keys. Iceberg didn't work for me with ED25519 keys. Pierce

Dec. 20, 2017

Re: [Pharo-users] [ANN] OpenSSL-Pharo works on Windows

by Pierce Ng

On Wed, Dec 20, 2017 at 09:03:36AM +0100, Sven Van Caekenberghe wrote: > Inevitable question: what is the plan for the other platforms ? I started on Linux, have now gotten it working on Windows, and expect to do MacOS next. I've also just mirrored the code onto GH. It is now at https://github.com/PierceNg/OpenSSL-Pharo. Pierce

Dec. 20, 2017

Re: [Pharo-users] Metacello with Git

by Tudor Girba

Hi, We also use private GitHub projects with Iceberg and it works fine. Cheers, Doru > On Dec 20, 2017, at 10:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 20.12.2017 um 04:02 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: >> >> CyrilFerlicot wrote >>> For bitbucket you can use bitbucket://. >>> I don't know for gitlab. >> >> Unless something has changed, the cool git URLs only work for public >> projects. In any case, it was not possible to authenticate with SSH keys >> last time I checked (so I could not use them)â¦ >> >> > Au contraire! It works really good with SSH keys. I work all day with it. I added support for bitbucket to iceberg because Iâm using bitbucket private repos in my company. > > Norbert > -- www.tudorgirba.com www.feenk.com "We cannot reach the flow of things unless we let go."

Dec. 20, 2017

Re: [Pharo-users] Metacello with Git

by Vitor Medina Cruz

> > These days, we are getting to the point where I am beginning to flip the > question on it's head and begin thinking that it should be possible for a > developer to choose to have have the github:// url interpreted as "create a > local clone of the remote repository" instead of "download a tarball of the > remote repository" . With this approach it should be possible to include > gitlab url support as well since the gitlab issue is related to the > specific handling of repository tarballs.. Using 'git clone --depth=1' don't do the trick and leave the process both efficient and general accross all git repos? On Tue, Dec 19, 2017 at 4:49 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > BitBucket is supported with like Github with: > butbucket://<butbucket_path>/<srcpath>. > > With regards to GitLab, their download zip format is/was different enough > from BitBucket/Github to make it difficult to provide the same level of > support. See the series of comments here[1]. > > When the github:// was first introduced it was done in such a way that > users of projects on GitHub did not have to have git installed on their > local computers ... it was a way to make it possible for folks to begin > using git without requiring everyone to install git ... > > These days, we are getting to the point where I am beginning to flip the > question on it's head and begin thinking that it should be possible for a > developer to choose to have have the github:// url interpreted as "create a > local clone of the remote repository" instead of "download a tarball of the > remote repository" . With this approach it should be possible to include > gitlab url support as well since the gitlab issue is related to the > specific handling of repository tarballs... > > ... there are current discussions in this area on these two issues [2] and > [3]. > > Dale > > [1] https://github.com/Metacello/metacello/issues/287#issuecomme > nt-59815235 > > [2] https://github.com/Metacello/metacello/issues/474 > > [3] https://github.com/Metacello/metacello/issues/475 > > > > On 12/19/17 10:25 AM, Vitor Medina Cruz wrote: > >> Hello, >> >> Using github://<github_path>/<srcpath> metacello works fine, but is >> there another more general way of refering to a remote git repo? From >> BitBucket or Gitlab for example. >> >> Regards, >> Vitor >> > > >

Dec. 20, 2017

Re: [Pharo-users] Pharo things analog reads ?

by Steven Costiou

Thanks for the link, also ;) Le 2017-12-20 05:20, K K Subbu a Ã©crit : > On Wednesday 20 December 2017 03:50 AM, Steven Costiou wrote: > >> So connecting an Arduino-like device to the raspberry that is >> configured as an i2c slave, Pharo can ask for analog values. I will >> try tomorrow with analog sensors, I will share if i manage to build >> nice examples. >> >> Seems to be even easier using a special chip: https://learn.adafruit.com/reading-a-analog-in-and-controlling-audio-volume… > > An Arduino would be an overkill. Also, there is no need for bitbanging. MCP3008 is are directly supported by the IIO subsystem and its channel data is demuxed in /sys/bus/iio/devices/iio:device<n> > > http://www.jumpnowtek.com/rpi/Using-mcp3008-ADCs-with-Raspberry-Pis.html > > HTH .. Subbu

Dec. 20, 2017

Re: [Pharo-users] Metacello with Git

by Norbert Hartl

> Am 20.12.2017 um 04:02 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: > > CyrilFerlicot wrote >> For bitbucket you can use bitbucket://. >> I don't know for gitlab. > > Unless something has changed, the cool git URLs only work for public > projects. In any case, it was not possible to authenticate with SSH keys > last time I checked (so I could not use them)â¦ > > Au contraire! It works really good with SSH keys. I work all day with it. I added support for bitbucket to iceberg because Iâm using bitbucket private repos in my company. Norbert

Dec. 20, 2017

Re: [Pharo-users] Pharo things analog reads ?

by Denis Kudriashov

Thank's for links. I will look 2017-12-19 23:20 GMT+01:00 Steven Costiou <steven.costiou(a)kloum.io>: > hi, > > i've tried i2c and added ffi calls in WiringPiLibrary. > > *wiringPiI2cSetup: devId* > > ^self ffiCall: #(int wiringPiI2CSetup (int devId) ) > > *readI2C: fd* > > ^self ffiCall: #(int wiringPiI2CRead (int fd)) > > Then the following script is able to read a byte from a connected device > (i tried with a trinket https://learn.adafruit.com/introducing-trinket/ > introduction): > <https://learn.adafruit.com/introducing-trinket/introduction)> > > |lib addr val| > > lib := WiringPiLibrary uniqueInstance. > > addr := self wiringPiSetupI2C: 4. *âSetup the i2c to the 0x04 addressâ* > val := self readI2C: addr. *âRead a byte from the i2c addressâ* > > val inspect > > So connecting an Arduino-like device to the raspberry that is configured > as an i2c slave, Pharo can ask for analog values. I will try tomorrow with > analog sensors, I will share if i manage to build nice examples. > > Seems to be even easier using a special chip: https://learn.adafruit.com/ > reading-a-analog-in-and-controlling-audio-volume-with- > the-raspberry-pi?view=all > > but it uses more pins on the board. > > Steven. > > > > Le 2017-12-17 19:48, Denis Kudriashov a Ã©crit : > > Hi Steven > > 2017-12-17 12:40 GMT+01:00 Steven Costiou <steven.costiou(a)kloum.io>: > >> Hi, >> >> For what i know, raspberry pi boards cannot read analog sensors (which >> are the most interesting imo), except by connecting to some kind of bridges >> or to Arduino boards. >> >> In the PharoTHings code i see that there are Arduino classes, and also it >> is based on wiringpi and wiringpi provides support for i2c which is needed >> to connect to an Arduino and perform analog reads. >> >> I'm exploring the wiringpi doc to see if there is an example for that, >> but in the meantime, would someone already have an example of analog reads >> with PharoThings, with working code (even simple) ? >> > It is in my todo. I need to build example with temperature sensor. I will > continue work on it next year. > Now feel free to contribute to the project. > > About Arduino: it is not finished. Problem that I use Mac but serial port > is not working there (it is required for Firmata) > >> >> >> Steven. >> >

Dec. 20, 2017

Re: [Pharo-users] Pharo things analog reads ?

by Steven Costiou

Yeah i know this exists, but i have none of these and i have plenty of trinkets, and i need to do analog reads. I2c is interesting anyway, some devices need it i believe. Le 2017-12-20 05:20, K K Subbu a Ã©crit : > On Wednesday 20 December 2017 03:50 AM, Steven Costiou wrote: > >> So connecting an Arduino-like device to the raspberry that is >> configured as an i2c slave, Pharo can ask for analog values. I will >> try tomorrow with analog sensors, I will share if i manage to build >> nice examples. >> >> Seems to be even easier using a special chip: https://learn.adafruit.com/reading-a-analog-in-and-controlling-audio-volume… > > An Arduino would be an overkill. Also, there is no need for bitbanging. MCP3008 is are directly supported by the IIO subsystem and its channel data is demuxed in /sys/bus/iio/devices/iio:device<n> > > http://www.jumpnowtek.com/rpi/Using-mcp3008-ADCs-with-Raspberry-Pis.html > > HTH .. Subbu

Dec. 20, 2017

Re: [Pharo-users] [ANN] OpenSSL-Pharo works on Windows

by Sven Van Caekenberghe

> On 20 Dec 2017, at 08:55, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > Hi all, > > OpenSSL-Pharo now works on Windows. Tested on Windows 10 with a fresh 32-bit > Pharo 6.1 zip package downloaded from pharo.org. On Windows this library uses > libeay.dll which is bundled with the Pharo VM. > > Metacello new > baseline: 'OpenSSL'; > smalltalkhubUser: 'PierceNg' project: 'OpenSSL-Pharo'; > load. > > Pierce Great work, I am eager to look/try. Inevitable question: what is the plan for the other platforms ? Sven

Dec. 20, 2017