June 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo MIDIPlugin

by StÃ©phane Ducasse

yes. On Jun 19, 2013, at 6:56 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: > Mac OS X? > > > 2013/6/19 jannik laval <jannik.laval(a)gmail.com> > Hi pharoers, > > It seems that MidiPlugin is not loaded in Pharo2.0. > The plugin is present in the repository, but when I try "Smalltalk loadModule: 'MIDIPlugin'" it raises an error. > > In "Smalltalk listLoadedModules" and "Smalltalk listBuiltinModules" there is no MIDIPlugin. > Could someone give me some help to solve this ? > > Jannik > > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

June 19, 2013

Re: [Pharo-dev] you may need to update your configurations

by StÃ©phane Ducasse

> > >> Christophe. >> >> [1] https://pharo.fogbugz.com/default.asp?10801 > > Ouch. Does not bode too well for backporting that to Pharo 2.0. > > I'm feeling a bit down. It's either enduring bugs in 2.0 for a year or so or fighting every few days with 3.0 and knowing that anyway it's not production ready. I had to cope with 1.4 not being able to handle utf8 in the same way. Thierry what we can do is the following: have a look at the fix of nicolas and we can try to add to th 2.0 batch but we should pay attention not to introduce other bugs (because I'm afraid it will). BTW 30 is not that instable. > The window for my next serious developpement with Pharo is around 2014, so I guess I could just sit and wait. > > By the way, why the change in MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ?

June 19, 2013

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

by StÃ©phane Ducasse

can you then send me the issues that I should look at :) Stef On Jun 19, 2013, at 1:10 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > StÃ©phane Ducasse wrote >> I like your browser showing issue. >> What does it show? >> Because I'm always lost with figbuz :) > > Yes, I'm starting to get used to fogbugz, but I've found the interface to be > counter-intuitive :/ Unfortunately the issue browser is not connected to > fogbugz. It simply collects subclasses of SpdPharoIssue, which each have > e.g. #number and #description hard-coded, and then for the status, #isFixed > which checks to see e.g. whether a certain method which is implemented in > the fix is present. It's not a general-purpose browser, but just to make > sure that the configuration loaded the correct fixes. Thanks to Spec, it's > so easy to build little UI's like this ;) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Pharo-dev-ANN-Pharo-x-5-tp4693932p4694117.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

June 19, 2013

Re: [Pharo-dev] Cloud Hosting Tip

by Sven Van Caekenberghe

On 19 Jun 2013, at 20:53, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > Hey! > > On 06/18/2013 04:26 PM, Sven Van Caekenberghe wrote: >> 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. > > Another one that I have filtered out as very interesting is CloudSigma. KVM based and much more flexible than EC2. Yes, those Swiss guys are pretty good. Being in Europe might be important too. Much more comparable to AWS in terms of features. And I see they are SSD based now, very nice. > regards, GÃ¶ran

June 19, 2013

Re: [Pharo-dev] Cloud Hosting Tip

by GÃ¶ran Krampe

Hey! On 06/18/2013 04:26 PM, Sven Van Caekenberghe wrote: > 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. Another one that I have filtered out as very interesting is CloudSigma. KVM based and much more flexible than EC2. regards, GÃ¶ran

June 19, 2013

Re: [Pharo-dev] Pharo MIDIPlugin

by NISHIHARA Satoshi

Mac OS X? 2013/6/19 jannik laval <jannik.laval(a)gmail.com> > Hi pharoers, > > It seems that MidiPlugin is not loaded in Pharo2.0. > The plugin is present in the repository, but when I try "Smalltalk > loadModule: 'MIDIPlugin'" it raises an error. > > In "Smalltalk listLoadedModules" and "Smalltalk listBuiltinModules" there > is no MIDIPlugin. > Could someone give me some help to solve this ? > > Jannik > -- -- "NISHIHARA Satoshi" [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

June 19, 2013

Re: [Pharo-dev] Barcodes

by Gary Chambers

Hi Olivier. For our label/report generation we do draw the barcodes rather than use a Form. Actually we have a Canvas that adapts to generate PDF so it is all WYSIWYG. Therefore no actual dependency in the PDF generation to any barcode objects. Looking to support Arefact instead of the stuff we have. Not looked at the details of Artefact yet though. TTF in PDF is not so bad... a snippet of what's expected in the output: 6 0 obj << /Type /Font /Subtype /TrueType /BaseFont /Arial /FirstChar 0 /LastChar 255 /Widths 8 0 R /FontDescriptor 9 0 R /Encoding /WinAnsiEncoding >> endobj 9 0 obj << /Type /FontDescriptor /FontName /Arial /Flags 32 /FontBBox [-665 -325 2000 1005] /Ascent 905 /Descent -212 /Leading 0 /ItalicAngle 0 >> endobj 8 0 obj [ 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 277 277 354 556 556 889 666 190 333 333 389 583 277 333 277 277 556 556 556 556 556 556 556 556 556 556 277 277 583 583 583 556 1015 666 666 722 722 666 610 777 722 277 500 666 556 833 722 777 666 777 722 666 610 722 666 943 666 666 610 277 277 277 469 556 333 556 556 500 556 556 277 556 556 222 222 500 222 833 556 556 556 556 333 500 277 556 500 722 500 500 500 333 259 333 583 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 750 277 333 556 556 556 556 259 556 333 736 370 556 583 333 736 552 399 548 333 333 333 576 537 333 333 333 365 556 833 833 833 610 666 666 666 666 666 666 1000 722 666 666 666 666 277 277 277 277 722 722 777 777 777 777 777 583 777 722 722 722 722 666 666 610 556 556 556 556 556 556 889 500 556 556 556 556 277 277 277 277 556 556 556 556 556 556 556 548 610 556 556 556 556 500 556 500 ] endobj (actually we now use MacRoman encoding as generally works better). All the data there can be gatherted from the FreeType TTF font in Pharo. Just needs to be present on the end-user's pc. A typical PDF reader will do fallbacks as necessary if not present. (not tackled fully embedded fonts yet). Regards, Gary ----- Original Message ----- From: Olivier Auverlot To: Pharo Development List Sent: Wednesday, June 19, 2013 6:42 AM Subject: Re: [Pharo-dev] Barcodes Hi Gary, yes, I'm interested by help and pointers about TTF. It's a planned evolution of Artefact. About barcodes generation, why don't use Artefact directly ? You can draw barcodes with the PDFDraw elements (PDFLineElement, PDFRectElement, etc.) and print the document on stickers. In the future, it could be cool to have a Artefact-Elements-Barcodes package :) Best regards Olivier Le 18 juin 2013 Ã 18:37, Gary Chambers a Ã©crit : 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 19, 2013

Re: [Pharo-dev] [Ann] VMMaker + Cog building in Pharo20

by Igor Stasenko

On 19 June 2013 16:34, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Yes, but right now moving from FileDirectory to FileSystem will make harder > the merge between VMMaker branches. > And cleaning and removing stuff will make it worse... > > So either we keep the mess or we lose the ability to easily merge :) > i don't think Cog will ever run on riscos in future.. (while on ARM, in general, it will). but it definitely won't use RiscOSVMMaker. I see no reason changing that, especially that Eliot made an effort to use single VMMaker class suitable to be used for building Cog on all platforms. -- Best regards, Igor Stasenko.

June 19, 2013

Re: [Pharo-dev] you may need to update your configurations

by Goubier Thierry

Le 19/06/2013 17:01, Christophe Demarey a Ã©crit : > > Le 19 juin 2013 Ã 16:36, Goubier Thierry a Ã©crit : > >> By the way, why the change in >> MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ? > > Because this change comes from the FileTree branch used fro Pharo3 [1]. > This small change avoid to use a deprecated method in Pharo3. > It should not be used in Pharo2. > > [1] > https://github.com/demarey/filetree/commit/dbdbf30a00bc1f8816773dc18888abe0… Thanks. It's just that the latest filetree-core-pharo20 package has MonticelloFileTree-Core-ChristopheDemarey.97 as ancestor :) Probably me messing a merge in my filetree fork. I'm supposed to branch from the pharo20 branch, and I can see your version as well... Thierry -- 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

June 19, 2013

Re: [Pharo-dev] you may need to update your configurations

by Goubier Thierry

Le 19/06/2013 16:46, Esteban Lorenzano a Ã©crit : > important bugfixes can be integrated in 2.0, is not all white and black :) Thanks, you're right of course :) Thierry > On Jun 19, 2013, at 4:36 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> >> >> Le 19/06/2013 16:17, Christophe Demarey a Ã©crit : >>> >>> Le 19 juin 2013 Ã 14:45, Goubier Thierry a Ã©crit : >>> >>>> Cool. >>>> >>>> Side question: Christophe, are you working on utf8 support for the >>>> Monticello tools? I encountered encoding problems with ZipArchive. >>> >>> Not at all. There is some work from Nicolas integrated [1] but I'm not >>> aware of other work on utf8 support. >> >> Ok. Looks nice :) >> >>> Christophe. >>> >>> [1] https://pharo.fogbugz.com/default.asp?10801 >> >> Ouch. Does not bode too well for backporting that to Pharo 2.0. >> >> I'm feeling a bit down. It's either enduring bugs in 2.0 for a year or so or fighting every few days with 3.0 and knowing that anyway it's not production ready. I had to cope with 1.4 not being able to handle utf8 in the same way. >> >> The window for my next serious developpement with Pharo is around 2014, so I guess I could just sit and wait. >> >> By the way, why the change in MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ? >> >> Thierry >> -- >> 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 >> > > > > -- 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

June 19, 2013