January 2020 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo image processing library

by Serge Stinckwich

Great work ! We have a math library with a lot code that might help you here: https://github.com/PolyMathOrg/PolyMath On Fri, Jan 24, 2020 at 11:20 PM Pablo Navarro <pablo1n7(a)gmail.com> wrote: > Hi everyone! > > Iâm searching for one library for image processing in Pharo. I couldn't > find anything (only wrappers) so I tried programming one for basic > operations (sum, > subtraction) with images using class âFormâ. > > What do you think about this? > > > For providing a context, I'm studying a PhD. in image processing, but all > of the operations that I do, do it in Python. I try using Pharo for more > fun :D. > > Best Regards Pablo. > -- Serge Stinckwic âhâ Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) âSorbonne University (SU) French National Research Institute for Sustainable Development (IRD)â U âniversity of YaoundÃ© Iâ, Cameroon "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich â

Jan. 24, 2020

Pharo image processing library

by Pablo Navarro

Hi everyone! Iâm searching for one library for image processing in Pharo. I couldn't find anything (only wrappers) so I tried programming one for basic operations (sum, subtraction) with images using class âFormâ. What do you think about this? For providing a context, I'm studying a PhD. in image processing, but all of the operations that I do, do it in Python. I try using Pharo for more fun :D. Best Regards Pablo.

Jan. 24, 2020

Re: [Pharo-users] Migration from Spec to Spec2

by Christophe Demarey

Hi Kasper, > Le 24 janv. 2020 Ã 20:14, Kasper Ãsterbye <kasper.osterbye(a)gmail.com> a Ã©crit : > Do not silently delete features. Be brave and include a method oddRowColor with a comment saying it is not going to be implemented in this version, and why I add the same issue and I wrote a small fix for TablePresenter. See https://github.com/pharo-project/pharo-launcher/commit/28fb65151a6341f26b91… I have only a few changes but I add to copy FTTableContainerMorph and FTSelectableMorph to add an instance variable on each. Except that, I had 4 methods to implement a basic row color alternance. You can use it as follow in an SpPresenter: self newTable items: #(1 2 3); whenBuiltDo: [ :table | table widget alternateRowsColor ] I will try to do a PR next week for this. Regards, Christophe.

Jan. 24, 2020

Re: [Pharo-users] Migration from Spec to Spec2

by Todd Blanchard

Thank you for blazing that trail. > On Jan 24, 2020, at 11:14 AM, Kasper Ãsterbye <kasper.osterbye(a)gmail.com> wrote: > > Cheers all, > > There was a mail about Spec2 documentation on this list in the last few days. I had a Spec program, and wanted to see how to migrate it to Spec2. > The before and after is the master and the Spec2Migration branches of: https://github.com/kasperosterbye/ovina <https://github.com/kasperosterbye/ovina> > > I decided to write down an account of all my struggles in making this migration. That account is on: https://github.com/kasperosterbye/ovina/blob/Spec2Migration/SpectoSpec2.md <https://github.com/kasperosterbye/ovina/blob/Spec2Migration/SpectoSpec2.md> > > Beware - it is LONG. > > In the end, I draw the following conclusions: > Class comments on which classes to use instead of the depricated ones should be mandatory! > Spotter is a real help > Changing terminology is a true pest - in particular since the terminology of a library is used in the applications - in my case Tab became Page. > The new library has not yet implemented all parts of the old one (but I am sure it has implemented new stuff as well). > The SpDemo class is not only good, it is a template for others to follow. > Do not silently delete features. Be brave and include a method oddRowColor with a comment saying it is not going to be implemented in this version, and why. > Some of them refer to specifics of the code. > > Overall I can say, that earlier today, Estaban wrote: > "Widgets API is more or less compatible, chances are that your components will work out of the box or it will be rewritten by a deprecation rule. > What is not compatible and there I not auto migration is the layout. You will need to rewrite those.â > > I am afraid to say, that was not my experience :-) > > Best, > > Kasper

Jan. 24, 2020

Migration from Spec to Spec2

by Kasper Ãsterbye

Cheers all, There was a mail about Spec2 documentation on this list in the last few days. I had a Spec program, and wanted to see how to migrate it to Spec2. The before and after is the master and the Spec2Migration branches of: https://github.com/kasperosterbye/ovina I decided to write down an account of all my struggles in making this migration. That account is on: https://github.com/kasperosterbye/ovina/blob/Spec2Migration/SpectoSpec2.md Beware - it is LONG. In the end, I draw the following conclusions: - Class comments on which classes to use instead of the depricated ones should be mandatory! - Spotter is a real help - Changing terminology is a true pest - in particular since the terminology of a library is used in the applications - in my case Tab became Page. - The new library has not yet implemented all parts of the old one (but I am sure it has implemented new stuff as well). - The SpDemo class is not only good, it is a template for others to follow. - Do not silently delete features. Be brave and include a method oddRowColor with a comment saying it is not going to be implemented in this version, and why. Some of them refer to specifics of the code. Overall I can say, that earlier today, Estaban wrote: "Widgets API is more or less compatible, chances are that your components will work out of the box or it will be rewritten by a deprecation rule. What is not compatible and there I not auto migration is the layout. You will need to rewrite those.â I am afraid to say, that was not my experience :-) Best, Kasper

Jan. 24, 2020

Re: [Pharo-users] Willow documentation

by TomaÅ¾ Turk

Dear Maximiliano, thanks for checking, I'll try once again, step by step. Best wishes, Tomaz ------ Original Message ------ From: "Maximiliano Tabacman" <mtabacman(a)yahoo.com> To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>; "TomaÅ¾ Turk" <tomaz.turk(a)ef.uni-lj.si> Sent: 24.1.2020 13:53:42 Subject: Re: [Pharo-users] Willow documentation >Hi there. >I just tried reproducing all the steps in the tutorials, then adding >the onTrigger for the button, exactly as you wrote in your mail, and it >works for me. >I don't get any errors in the console. I implemented it in a clean >installation of Pharo with the latest release of Willow-Playground, on >Windows 10, rendering with Opera. > >Could you check if those same steps give you the result you mention? > >Thanks for your interest in Willow! > >>

Jan. 24, 2020

Re: [Pharo-users] spec 2 documentation

by Steve Quezadas

Great, I learn a lot by playing around with the demos On Fri, Jan 24, 2020 at 1:56 AM Kasper Ãsterbye <kasper.osterbye(a)gmail.com> wrote: > Hi > > Just to make sure - you guys know about the class SpDemo (part of the > image), it has examples of a lot of things. It is seriously a treasure > trove of how-to. > > Best, > > Kasper > > > > >

Jan. 24, 2020

Re: [Pharo-users] Extracting MP3 metadata

by sergio ruiz

THIS! is exactly what I need. Thank you so much! > On Jan 24, 2020, at 4:05 AM, VERHAEGHE Benoit <badetitou(a)gmail.com> wrote: > > To read mp3 metadata you should rely on an id3 parser (https://en.wikipedia.org/wiki/ID3 <https://en.wikipedia.org/wiki/ID3>). > I use/develop this one: https://github.com/pharo-media-center/id3-pharo <https://github.com/pharo-media-center/id3-pharo> ---- peace, sergio photographer, journalist, visionary Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV @sergio_101@mastodon.social https://sergio101.com http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Jan. 24, 2020

Re: [Pharo-users] Willow documentation

by Maximiliano Tabacman

Hi there.I just tried reproducing all the steps in the tutorials, then adding the onTrigger for the button, exactly as you wrote in your mail, and it works for me.I don't get any errors in the console. I implemented it in a clean installation of Pharo with the latest release of Willow-Playground, on Windows 10, rendering with Opera. Could you check if those same steps give you the result you mention? Thanks for your interest in Willow! On Monday, January 20, 2020, 02:02:31 PM GMT-3, TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: #yiv3242684405 blockquote.yiv3242684405cite {margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left:1px solid #cccccc;}#yiv3242684405 blockquote.yiv3242684405cite2 {margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left:1px solid #cccccc;margin-top:3px;padding-top:0px;}#yiv3242684405 a img {border:0px;}#yiv3242684405 #yiv3242684405 #yiv3242684405 #yiv3242684405 , #yiv3242684405 #yiv3242684405 #yiv3242684405 #yiv3242684405 {list-style-position:inside;}#yiv3242684405 body {font-family:Segoe UI;font-size:12pt;}Dear Gabriel, Yes, I followed the steps from the blog - my code is here:Â https://github.com/eftomi/willow-tryout/blob/master/Poskusi-Willow/ToDoAppl…. Maybe I misunderstood something. Many thanks for additional explanations about Willow coding.Â Best wishes,Tomaz ------ Original Message ------From: "Gabriel Cotelli" <g.cotelli(a)gmail.com>To: "TomaÅ¾ Turk" <tomaz.turk(a)ef.uni-lj.si>; "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>Sent: 20.1.2020 12:49:37Subject: Re: [Pharo-users] Willow documentation Hi Tomas, Comments inline. On Sun, Jan 19, 2020 at 2:59 PM TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: Dear all, I'm trying out Willow which looks very interesting, however I'm struggling with simple examples ...Â I basically follow the blogs (here). I loaded Willow with Bootstrap and prepared the To-Do app as described in blog series. This works OK, however when I try to do something more, like Â Â button := AsynchronicButtonWebView labeled: 'Now it''s time to click'. Â Â button onTrigger executeOnClient: [ :canvas | canvas javascript alert: 'You just clicked a button' ] the browser's javascript gives no response, and its console reports some errors: I will check because this looks like a problem in the online version of the jquery library. You've got this error following just the tutorial steps? It looks like problems with libraries. I checked the examples in WillowPlayground (which works OK, BTW), and found out that some basic things are way richer than described in the blogs. For instance, component supplier is not just componentSupplierForApplication Â Â ^ Bootstrap4ComponentSupplier online as in the blog, but: componentSupplierForApplication Â Â ^ BootstrapComponentSupplier Â Â Â Â withBootstrapLibrary: (self deploymentMode libraryFor: Bootstrap3MetadataLibrary) withoutOptionalTheme Â Â Â Â selectLibrary: ((self deploymentMode libraryFor: BootstrapSelectLibrary) using: self language) Â Â Â Â datepickerLibrary: ((self deploymentMode libraryFor: BootstrapDatepickerLibrary) using: self language) Â Â Â Â typeaheadLibrary: (self deploymentMode libraryFor: BootstrapTypeaheadLibrary) new There are two operations modes for the component supplier. - If your application will be online on the open internet you can useÂ Bootstrap4ComponentSupplier online, and this will get the required JS libraries from the official CDNs. - The second option is to self-serve the libraries (this case is more common for applications that will run in a closed environment like a company intranet, or a heavy regulated environment where the access to open resources on the internet are probably forbidden or require a lot of bureaucracy and approvals). Â My question is - is there a better documentation available for Willow? It's quite hard to study all bits and pieces from scratch. The doc available is the one in the repo under /docs, the blog posts and the sample applications in Willow-Playground. If you have some ideas on missing docs or parts of the documentation that can be improved please fill an issue inÂ https://github.com/ba-st/Willow/issues The second question is about the suggested "architecture" or design pattern that should be followed when using Willow. The blog mixes Seaside components (e.g. #PendingTask as a subclass of WAPainter) that engages Seaside rendering elements (e.g. Â html paragraph on one hand, with the components supplier's components (e.g. singleLineTextField ...) implemented directly in the Willow Application on the other hand. This probably isn't the way things should be done Mixing standard Seaside rendering with Willow components it's Ok. The rule to follow here is: - if the component will need some kind of interaction from the user, a Willow component will suit your needs better. Usually this gets initialized once in the component containing it and then it's rendered many times. In this way you can access the component state easily. - for elements that are more like presentation parts and will not have any state nor interactions associated it's perfectly Ok to use standard Seaside rendering. The exception here is in the case of containers (divs, spans, etc) that you want to get replaced dynamically, for that cases it's better to use GenericContainerWebView or PhrasingContainerWebView. Since some versions Willow extended standard Seaside facilities so you can use the command-like interface with standard Seaside brushes. Take a look at WATagBrush Willow extensions. So you can do something like:html div with: [ html text: 'Hi!'] applying: [:container | container addClass bootstrap backgroundInfo]Â Where the block in applying: allows the same command-like interface available for components. Best wishes,Tomaz Regards,Gabriel

Jan. 24, 2020

by Marcus Denker

The Pharo Consortium is very happy to announce that ÃTS MontrÃ©al has joined the Consortium as an Academic Member. About - ÃTS MontrÃ©al: https://www.etsmtl.ca/en/Home - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

Jan. 24, 2020