- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Barcodes

by Gary Chambers

Well, hoping to work with Torsten on barcodes in general, given we have support for canvas based drawing of a few formats here at Pinesoft. Also, if Olivier would like some help with TTF in PDFs I can give some pointers etc. Regards, Gary ----- Original Message ----- From: Chris Cunningham To: Pharo Development List Sent: Tuesday, June 18, 2013 5:23 PM Subject: Re: [Pharo-dev] Barcodes You should be able to create a form, paint it white, draw on it with a barcode TTF font, export that form to JPEG, and then use that JPEG into Artefact. Not really straight-forward, but it should work. *Note: I've found that writing JPEG's in Pharo, it assumes that the background is BLACK if it isn't isn't specifically painted with something else first. Unlike PNG and GIF, which assume WHITE. -Chris On Tue, Jun 18, 2013 at 1:44 AM, Olivier Auverlot <olivier.auverlot(a)gmail.com> wrote: Hi Torsten, Artefact don't support TTF fonts for the moment but it's planned in futures versions. Best regards Olivier :-) Le 14 juin 2013 Ã 16:16, Milan Mimica a Ã©crit : You just need a TTF font. Does Artefact support TTF? hpdf does. On 14 June 2013 13:58, Torsten Bergmann <astares(a)gmx.de> wrote: Do we have some barcode stuff available for Pharo? Something "Form" based that can be used with Artefact? Thx T. -- Milan Mimica http://sparklet.sf.net

June 18, 2013

Re: [Pharo-dev] Cloud Hosting Tip

by Sven Van Caekenberghe

On 18 Jun 2013, at 17:24, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > I did some tests with AWS EC2, and it is good to know to know Pharo is so simple to install in this provider. > > It looks more like a VPS provider, or am I missing something? Because I haven't seen an autoscaling (up or out) option there. > Do you know if they support something similar to Elastic IP? No, you just get a simple machine ('VPS', but they are all virtual, right) of some size and then you are on your own. AWS has lots and lots of more options, API's and services. > Regards, > > Esteban A. Maringolo > > > 2013/6/18 Sven Van Caekenberghe <sven(a)stfx.eu> > Hi, > > I am a fan of Amazon AWS's Cloud Services. But it is not perfect. > > Enter Digital Ocean (https://www.digitalocean.com) an easier to use, simpler cloud hosting provider, that is cheaper and seems faster. You get a raw machine, so you still need some basic Unix admin skills, but apart from that it cannot get much easier. > > For just $5 a month you get this: > > <Screen Shot 2013-06-18 at 16.00.41.png> > As an SSD based machine, it feels very fast. I did some quick benchmarks at the Pharo level which show that this virtualised hardware is up to 10x faster than an Amazon AWS EC2 micro instance, and up to 3x faster than an Amazon AWS EC2 small instance. Its just a bit slower than my top of the line MacBook Air: > > root@stfx:~# ./pharo Pharo.image eval '1 tinyBenchmarks' > '764749813 bytecodes/sec; 94679619 sends/sec' > > To get started on the empty machine, just do > > root@stfx:~# curl get.pharo.org/30+vm | bash > > If you picked a 32 bit Ubuntu, you only need to do > > root@stfx:~# apt-get install libssl0.9.8 > > Starting a Zn server is dead easy: > > root@stfx:~# ./pharo Pharo.image eval --no-quit 'ZnServer startDefaultOn: 1701' & > > Have a look at: > > http://82.196.12.54:1701 > > Which is a single vm+image instance. > > Local network performance is quite good: > > root@stfx:~# ab -k -n 1024 -c 4 http://localhost:1701/bytes > > Server Software: Zinc > Server Hostname: localhost > Server Port: 1701 > > Document Path: /bytes > Document Length: 64 bytes > > Concurrency Level: 4 > Time taken for tests: 0.584 seconds > Complete requests: 1024 > Failed requests: 0 > Write errors: 0 > Keep-Alive requests: 1024 > Total transferred: 243712 bytes > HTML transferred: 65536 bytes > Requests per second: 1753.68 [#/sec] (mean) > Time per request: 2.281 [ms] (mean) > Time per request: 0.570 [ms] (mean, across all concurrent requests) > Transfer rate: 407.59 [Kbytes/sec] received > > I also tried a big config based build that downloaded and compiled about 1Gb worth of .mcz and that took less than 4 minutes which is also quite fast. > > Of course, you get way fewer features than with Amazon AWS (the total ecosystem). But for the price it seems hard to beat. > > Have fun ! > > Sven > > PS: Feel free to do me a favour by using this link https://www.digitalocean.com/?refcode=6a0334a169dc > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > >

June 18, 2013

Re: [Pharo-dev] Barcodes

by Chris Cunningham

You should be able to create a form, paint it white, draw on it with a barcode TTF font, export that form to JPEG, and then use that JPEG into Artefact. Not really straight-forward, but it should work. *Note: I've found that writing JPEG's in Pharo, it assumes that the background is BLACK if it isn't isn't specifically painted with something else first. Unlike PNG and GIF, which assume WHITE. -Chris On Tue, Jun 18, 2013 at 1:44 AM, Olivier Auverlot < olivier.auverlot(a)gmail.com> wrote: > Hi Torsten, > > Artefact don't support TTF fonts for the moment but it's planned in > futures versions. > > Best regards > Olivier :-) > > Le 14 juin 2013 Ã 16:16, Milan Mimica a Ã©crit : > > You just need a TTF font. Does Artefact support TTF? hpdf does. > > > On 14 June 2013 13:58, Torsten Bergmann <astares(a)gmx.de> wrote: > >> Do we have some barcode stuff available for Pharo? >> Something "Form" based that can be used with Artefact? >> >> Thx >> T. >> >> > > > -- > Milan Mimica > http://sparklet.sf.net > > >

June 18, 2013

Re: [Pharo-dev] on:do: for shortcuts?

by Esteban A. Maringolo

2013/6/18 ClÃ©ment Bera <bera.clement(a)gmail.com> > On Javascript, there are : > > onkeypress > onkeydown > onkeyup > > > I think we should have same API than other languages, especially popular ones. So 1 of these 3 would be the best for me. > > Why not onKeyPress:do: ? +1 to each of the last two statements.

June 18, 2013

Re: [Pharo-dev] [ANN]: Pharo x.5

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote >> * ZnNetworkingUtils>>isPortAvailable: (doesn't take ip6 into account) > > I am interested in this one but I can't open the package named: > 'ZnNetworkingUtils>>usedPorts', can you ? No, I can't either... but it's okay because I moved the method into Zinc-HTTPSpd ;) I was experimenting with packaging each method individually, but didn't see the point, so I changed to mirroring the packages being extended... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-ANN-Pharo-x-5-tp4693932p4693967.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 18, 2013

Re: [Pharo-dev] on:do: for shortcuts?

by ClÃ©ment Bera

On Javascript, there are : - onkeypress - onkeydown - onkeyup I think we should have same API than other languages, especially popular ones. So 1 of these 3 would be the best for me. Why not onKeyPress:do: ? 2013/6/18 Goubier Thierry <thierry.goubier(a)cea.fr> > Additionally, this is processing on a shortcut, that is possibly on a > sequence of keys... > > So, onKey:do: isn't very good. > > The replacement of asShortcut by asKeyCombination in 3.0 wasn't too good, > either. > > But, to be coherent, it should certainly be: > > onKeyCombination:do: > > Thierry > > > Le 18/06/2013 16:44, Igor Stasenko a Ã©crit : > > On 18 June 2013 15:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> >>> Hi guillermo >>> >>> I thought that we decided to change and not use >>> on: do: for shortCuts (I'm happy that we change because for me >>> it took me a while to understand that the key was not an exception. >>> >>> Could we deprecate on:do: on KMDispatcher? >>> What is the replacement? >>> >>> onKey: do: >>> >>> >>> initializeShortcuts >>> "initialize the inspector' shortcuts with the dictionary >>> defined in self shortCuts" >>> >>> self shortCuts keysAndValuesDo: [ :key :value | >>> list on: key do: value ] >>> >>> => >>> >>> initializeShortcuts >>> "initialize the inspector' shortcuts with the dictionary >>> defined in self shortCuts" >>> >>> self shortCuts keysAndValuesDo: [ :key :value | >>> list onHold: key do: value ] >>> >>> hold or press? >> >> you *press* the key, *hold* it for a while and then *release*. >> >> usually you receive 2 events - press and release. >> and you don't receive 'hold' event, since it is assumed that key is >> being held until it released. >> >> then on top of that, there is a key repeat functionality, is when user >> holds key it starts repeating >> (but again, ideally you don't receive a 'press' event, but you receive >> a synthetic 'keyChar' event) >> >> >>> Stef >>> >> >> >> >> > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 18, 2013

Re: [Pharo-dev] [ANN]: Pharo x.5

by Sean P. DeNigris

Marcus Denker-4 wrote > Keep in mind that we can integrate important fixes in 2.0â¦. someone just > needs to take initiative. Thanks for the reminder! I'm clear about that after all the work we did together getting 2.0 issues backported to 1.4 :) And... my understanding is that we have a policy to only backport bug fixes. The features in this project are either: - fixes waiting to be integrated - enhancements that do not fit the backporting policy - extensions that I find extremely useful, but I'm not clear how useful they'd be to others ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-ANN-Pharo-x-5-tp4693932p4693966.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 18, 2013

Re: [Pharo-dev] Cloud Hosting Tip

by Esteban A. Maringolo

I did some tests with AWS EC2, and it is good to know to know Pharo is so simple to install in this provider. It looks more like a VPS provider, or am I missing something? Because I haven't seen an autoscaling (up or out) option there. Do you know if they support something similar to Elastic IP? Regards, Esteban A. Maringolo 2013/6/18 Sven Van Caekenberghe <sven(a)stfx.eu> > Hi, > > I am a fan of Amazon AWS's Cloud Services. But it is not perfect. > > Enter Digital Ocean (https://www.digitalocean.com) an easier to use, > simpler cloud hosting provider, that is cheaper and seems faster. You get a > raw machine, so you still need some basic Unix admin skills, but apart from > that it cannot get much easier. > > For just $5 a month you get this: > > As an SSD based machine, it feels very fast. I did some quick benchmarks > at the Pharo level which show that this virtualised hardware is up to 10x > faster than an Amazon AWS EC2 micro instance, and up to 3x faster than > an Amazon AWS EC2 small instance. Its just a bit slower than my top of the > line MacBook Air: > > root@stfx:~# ./pharo Pharo.image eval '1 tinyBenchmarks' > '764749813 bytecodes/sec; 94679619 sends/sec' > > To get started on the empty machine, just do > > root@stfx:~# curl get.pharo.org/30+vm | bash > > If you picked a 32 bit Ubuntu, you only need to do > > root@stfx:~# apt-get install libssl0.9.8 > > Starting a Zn server is dead easy: > > root@stfx:~# ./pharo Pharo.image eval --no-quit 'ZnServer > startDefaultOn: 1701' & > > Have a look at: > > http://82.196.12.54:1701 > > Which is a single vm+image instance. > > Local network performance is quite good: > > root@stfx:~# ab -k -n 1024 -c 4 http://localhost:1701/bytes > > Server Software: Zinc > Server Hostname: localhost > Server Port: 1701 > > Document Path: /bytes > Document Length: 64 bytes > > Concurrency Level: 4 > Time taken for tests: 0.584 seconds > Complete requests: 1024 > Failed requests: 0 > Write errors: 0 > Keep-Alive requests: 1024 > Total transferred: 243712 bytes > HTML transferred: 65536 bytes > Requests per second: 1753.68 [#/sec] (mean) > Time per request: 2.281 [ms] (mean) > Time per request: 0.570 [ms] (mean, across all concurrent requests) > Transfer rate: 407.59 [Kbytes/sec] received > > I also tried a big config based build that downloaded and compiled about > 1Gb worth of .mcz and that took less than 4 minutes which is also quite > fast. > > Of course, you get way fewer features than with Amazon AWS (the total > ecosystem). But for the price it seems hard to beat. > > Have fun ! > > Sven > > PS: Feel free to do me a favour by using this link > https://www.digitalocean.com/?refcode=6a0334a169dc > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > >

June 18, 2013

Re: [Pharo-dev] Cloud Hosting Tip

by phil＠highoctane.be

I have been looking into that as well and it is indeed very nice. DO is growing very fast. Phil Le 18 juin 2013 16:27, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > Hi, > > I am a fan of Amazon AWS's Cloud Services. But it is not perfect. > > Enter Digital Ocean (https://www.digitalocean.com) an easier to use, > simpler cloud hosting provider, that is cheaper and seems faster. You get a > raw machine, so you still need some basic Unix admin skills, but apart from > that it cannot get much easier. > > For just $5 a month you get this: > > As an SSD based machine, it feels very fast. I did some quick benchmarks > at the Pharo level which show that this virtualised hardware is up to 10x > faster than an Amazon AWS EC2 micro instance, and up to 3x faster than > an Amazon AWS EC2 small instance. Its just a bit slower than my top of the > line MacBook Air: > > root@stfx:~# ./pharo Pharo.image eval '1 tinyBenchmarks' > '764749813 bytecodes/sec; 94679619 sends/sec' > > To get started on the empty machine, just do > > root@stfx:~# curl get.pharo.org/30+vm | bash > > If you picked a 32 bit Ubuntu, you only need to do > > root@stfx:~# apt-get install libssl0.9.8 > > Starting a Zn server is dead easy: > > root@stfx:~# ./pharo Pharo.image eval --no-quit 'ZnServer > startDefaultOn: 1701' & > > Have a look at: > > http://82.196.12.54:1701 > > Which is a single vm+image instance. > > Local network performance is quite good: > > root@stfx:~# ab -k -n 1024 -c 4 http://localhost:1701/bytes > > Server Software: Zinc > Server Hostname: localhost > Server Port: 1701 > > Document Path: /bytes > Document Length: 64 bytes > > Concurrency Level: 4 > Time taken for tests: 0.584 seconds > Complete requests: 1024 > Failed requests: 0 > Write errors: 0 > Keep-Alive requests: 1024 > Total transferred: 243712 bytes > HTML transferred: 65536 bytes > Requests per second: 1753.68 [#/sec] (mean) > Time per request: 2.281 [ms] (mean) > Time per request: 0.570 [ms] (mean, across all concurrent requests) > Transfer rate: 407.59 [Kbytes/sec] received > > I also tried a big config based build that downloaded and compiled about > 1Gb worth of .mcz and that took less than 4 minutes which is also quite > fast. > > Of course, you get way fewer features than with Amazon AWS (the total > ecosystem). But for the price it seems hard to beat. > > Have fun ! > > Sven > > PS: Feel free to do me a favour by using this link > https://www.digitalocean.com/?refcode=6a0334a169dc > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > >

June 18, 2013

Re: [Pharo-dev] Object>>#if:then:else:

by ClÃ©ment Bera

I don't like this new structure. Then people coming from non object language using all the time control structure will do : #someRandomObject if: then: else: thinking of doing a C style condition and not using at all the receiver. I like how it is now. 2013/6/18 kilon <thekilon(a)yahoo.co.uk> > Very few things are truly necessary in life, programming languages are not > amongst them. > > As I said , for me how already things work in pharo is fine concerning > ifTrue: and friends . > > > > -- > View this message in context: > http://forum.world.st/Pharo-dev-Object-if-then-else-tp4693871p4693952.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 18, 2013