February 2020 - Pharo-users

Re: [Pharo-users] [Pharo-dev] [ANN] uFFI Booklet v1.0

by ducasse

there was a draft of a chapter and we remove it. So probably for a following version :) S. > On 12 Feb 2020, at 20:34, phil(a)highoctane.be wrote: > > Nice. > > Are callbacks going to be detailed in a future version? > > They are pretty powerful as one can write a pharo callback to a c method and for debugging, it is golden. > > Phil > á§ > > On Wed, Feb 12, 2020 at 6:02 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > Iâm preparing the website :) > >> On 12 Feb 2020, at 10:30, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >> >> Hi all, >> >> We have been working a lot in the last months in the documentation of uFFI, and we are happy to announce a first stable version of it that youâll find in a link below :) >> The booklet talks about uFFI, how to use it, how marshalling works, how to use structures, unions, etc. >> And it is aimed for the version present on Pharo8.0. >> >> https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1 <https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1> >> >> Of course, a v1 does not mean itâs perfect. Future versions will include new chapters/features that are on the pipeline such as callbacks and how to specify string encodings in your bindings. >> Also, so if you find something to fix, to add, to remove, or something hard to follow, let us know >> - by email or >> - by issue (will be easier to track actually than an email) or >> - by PR (and we will have a boost of happiness in addition) >> >> Cheers, >> Guille in behalf of everybody that helped and contributed to this > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

Feb. 12, 2020

Re: [Pharo-users] [Pharo-dev] [ANN] uFFI Booklet v1.0

by phil＠highoctane.be

Nice. Are callbacks going to be detailed in a future version? They are pretty powerful as one can write a pharo callback to a c method and for debugging, it is golden. Phil á§ On Wed, Feb 12, 2020 at 6:02 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Iâm preparing the website :) > > On 12 Feb 2020, at 10:30, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Hi all, > > We have been working a lot in the last months in the documentation of > uFFI, and we are happy to announce a first stable version of it that youâll > find in a link below :) > The booklet talks about uFFI, how to use it, how marshalling works, how to > use structures, unions, etc. > And it is aimed for the version present on Pharo8.0. > > https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1 > > Of course, a v1 does not mean itâs perfect. Future versions will include > new chapters/features that are on the pipeline such as callbacks and how to > specify string encodings in your bindings. > Also, so if you find something to fix, to add, to remove, or something > hard to follow, let us know > - by email or > - by issue (will be easier to track actually than an email) or > - by PR (and we will have a boost of happiness in addition) > > Cheers, > Guille in behalf of everybody that helped and contributed to this > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

Feb. 12, 2020

Re: [Pharo-users] [ANN] uFFI Booklet v1.0

by Steffen MÃ¤rcker

Great! Thanks for the effort of putting this example-driven booklet together! Steffen Guillermo Polito schrieb am Wed Feb 12 2020 10:30:31 GMT+0100 (MitteleuropÃ¤ische Normalzeit): Hi all, We have been working a lot in the last months in the documentation of uFFI, and we are happy to announce a first stable version of it that youâll find in a link below :) The booklet talks about uFFI, how to use it, how marshalling works, how to use structures, unions, etc. And it is aimed for the version present on Pharo8.0. https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1 Of course, a v1 does not mean itâs perfect. Future versions will include new chapters/features that are on the pipeline such as callbacks and how to specify string encodings in your bindings. Also, so if you find something to fix, to add, to remove, or something hard to follow, let us know - by email or - by issue (will be easier to track actually than an email) or - by PR (and we will have a boost of happiness in addition) Cheers, Guille in behalf of everybody that helped and contributed to this

Feb. 12, 2020

Re: [Pharo-users] About DuneSt / ChartJs

by Sven Van Caekenberghe

Hi Pierce, I did actually use the following expression: Metacello new githubUser: 'DuneSt' project: 'ChartJs' commitish: 'master' path: 'src'; baseline: 'ChartJs'; onUpgrade: [ :e | e useIncoming ]; onConflictUseLoaded; onWarningLog; load. Thinking about it, maybe the #onUpgrade: and #onConflictUseLoaded can't used together, I don't know. I normally load Seaside3 as a dependency to Bootstrap: spec baseline: 'Bootstrap' with: [ spec repository: 'github://astares/Seaside-Bootstrap:master/src' ]. which loads Seaside as: seaside3: spec spec baseline: 'Seaside3' with: [ spec loads: #('default' 'REST'); repository: 'github://SeasideSt/Seaside:master/repository' ] while ChartJS uses: seaside3: spec spec baseline: 'Seaside3' with: [ spec repository: 'github://SeasideSt/Seaside:v3.4.x/repository' ] Maybe the differences in URL (the version tag) and maybe also the groups make them incompatible/different ? Sven > On 12 Feb 2020, at 01:10, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > On Tue, Feb 11, 2020 at 05:06:44PM +0100, Sven Van Caekenberghe wrote: >> NeoJSON and Seaside are already in my project's dependencies, but >> Seaside3 seems to never resolve to the same thing, so I would like to >> skip that. Is that possible ? I have this issue often with Seaside. I >> could fork and edit the baseline, but I'd rather not. > > I do the following near the top of my load script: > > Metacello new > baseline: 'Seaside3'; > repository: '...'; > load; > lock. > > And when loading other packages that may want to load another version of > Seaside: > > Metacello new > baseline: 'whatever'; > repository: '...'; > onConflictUseLoaded; > load. > > I tried doing ifTrue:ifFalse: conditional loading in my baseline to test > for Seaside, but it didn't work. > > Pierce > >

Feb. 12, 2020

Re: [Pharo-users] About DuneSt / ChartJs

by Sven Van Caekenberghe

Hi Guillaume, Thank you for your reply. I see that the version supported/implemented in DuneSt/ChartJs is 1.0.2 (from 2015) while the current Chart.js version is 2.0, so it would probably be time for an upgrade. I also don't know the perfect answer to the Seaside dependency, I'll write some more in another reply. I tried making a sub class of ChartBar called ChartHorizontalBar overwriting only forChartJS ^ 'HorizontalBar' and then using that as an argument to #chartType: but alas that did not work. I must admit that I do not really understand how I have to mentally map the official JavaScript documentation to the model in Pharo and how it is implemented (#forChartJS does not seem to be used as argument/value but as a function call). Sven > On 11 Feb 2020, at 20:12, Guillaume Larcheveque <guillaume.larcheveque(a)gmail.com> wrote: > > > > Le mar. 11 fÃ©vr. 2020 Ã 17:07, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > Hi, > > I am trying to use DuneSt / ChartJs [ https://github.com/DuneSt/ChartJs ] and it looks good. Thanks for another nice library. > You're welcome and we are pleased that you use it :-) > > My first question is about loading the code. I would like to load the minimum possible. I guess the stylesheet code is needed, but not the prism code ? > You are totally right, Prism is required by the demo to display the code. You will not load it by using the 'core' group > > NeoJSON and Seaside are already in my project's dependencies, but Seaside3 seems to never resolve to the same thing, so I would like to skip that. Is that possible ? I have this issue often with Seaside. I could fork and edit the baseline, but I'd rather not. > I have the same opinion, if you have a solution to manage it in a nice way i would be pleased to add it. I only see as a solution to create a group that do not load Seaside3 but maybe Cyril know a better way to do it (he is far better than me about baselines) > > I got a Bar chart on 2D data running right away. > > But how can I use 'horizontalBar' as type ? > > var myBarChart = new Chart(ctx, { > type: 'horizontalBar', > data: data, > options: options > }); > > I see that the types are encoded a classes, but the list seems rather limited. > We implemented the minimum that is required for us. It is really easy to add new ones as you already discovered. I will add these as soon as possible or if you already did it, create a pull request. There is many improvement that can be done in this project and it would be great to have your contribution about it. > > We will move to the new version of the ChartJs library when we will have time to improve it. Of course the API of our project will stay the same and changes will not impact your project. > > Thx, > > Sven > > > > > -- > Guillaume Larcheveque >

Feb. 12, 2020

[ANN] uFFI Booklet v1.0

by Guillermo Polito

Hi all, We have been working a lot in the last months in the documentation of uFFI, and we are happy to announce a first stable version of it that youâll find in a link below :) The booklet talks about uFFI, how to use it, how marshalling works, how to use structures, unions, etc. And it is aimed for the version present on Pharo8.0. https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1 <https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1> Of course, a v1 does not mean itâs perfect. Future versions will include new chapters/features that are on the pipeline such as callbacks and how to specify string encodings in your bindings. Also, so if you find something to fix, to add, to remove, or something hard to follow, let us know - by email or - by issue (will be easier to track actually than an email) or - by PR (and we will have a boost of happiness in addition) Cheers, Guille in behalf of everybody that helped and contributed to this

Feb. 12, 2020

Re: [Pharo-users] [ANN] Pharo TechTalk Feb 20: The Colony

by Marcus Denker

> On 11 Feb 2020, at 23:13, Steve Quezadas <steveeq1(a)gmail.com> wrote: > > This is interesting. I will surely go to this tech talk, as I'm always interested in finding new and efficient methods of organizing groups. Will this be a youtube streaming of the demo? Or is it mostly chat? It will be a youtube (or other platform) online streaming demo / introduction with Q/A after. > > What is the best way to use javascript libraries within pharo? amber or pharojs? scarlet? > For now we just want to use colony.io as a website, not from within Pharo. > Are there any front-ends for this project available? It is a website / web application, but build with lots of the Ethereum platform tools (even though the current version is not completely decentralised)â https://colony.io/product/app No Pharo involved at all. Think about it like if we would use meetup.com to orgnize a meetup. Just some website. > Are there any "colonies" out in the wild? > They are just starting, it is very early stage software. There is a Discord where people announce things. I do not know a lot about it myself, so you better ask them directly. Marcus

Feb. 12, 2020

Re: [Pharo-users] About DuneSt / ChartJs

by Pierce Ng

On Tue, Feb 11, 2020 at 05:06:44PM +0100, Sven Van Caekenberghe wrote: > NeoJSON and Seaside are already in my project's dependencies, but > Seaside3 seems to never resolve to the same thing, so I would like to > skip that. Is that possible ? I have this issue often with Seaside. I > could fork and edit the baseline, but I'd rather not. I do the following near the top of my load script: Metacello new baseline: 'Seaside3'; repository: '...'; load; lock. And when loading other packages that may want to load another version of Seaside: Metacello new baseline: 'whatever'; repository: '...'; onConflictUseLoaded; load. I tried doing ifTrue:ifFalse: conditional loading in my baseline to test for Seaside, but it didn't work. Pierce

Feb. 12, 2020

Re: [Pharo-users] Spec2 and Nuklear?

by Pierce Ng

On Tue, Feb 11, 2020 at 01:59:49PM -0500, Offray Vladimir Luna CÃ¡rdenas wrote: > This is not a question, but more like a blue plan thinking about > minimalist native UI toolkits that can talk with Spec 2. I just found > Nuklear[1] and I'm kind of wondering if this could take the place of GTK > in the Spec2 world. > > [1] https://github.com/Immediate-Mode-UI/Nuklear There is also Dear ImGui, written in C++, and cimgui, its C wrapper. https://github.com/ocornut/imgui https://github.com/cimgui/cimgui It will be great to program UIs with one or both of these and Pharo. Pierce

Feb. 12, 2020

Re: [Pharo-users] [ANN] Pharo TechTalk Feb 20: The Colony

by Steve Quezadas

This is interesting. I will surely go to this tech talk, as I'm always interested in finding new and efficient methods of organizing groups. Will this be a youtube streaming of the demo? Or is it mostly chat? What is the best way to use javascript libraries within pharo? amber or pharojs? scarlet? Are there any front-ends for this project available? Are there any "colonies" out in the wild? Are there going to be any physical presentations for this? I am in Los Angeles. On Mon, Feb 10, 2020 at 6:30 AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > A regular chat about Pharo. Happens on Discord. > > This month a bit a special TechTalk, not about Pharo but about a tool that > might be interesting for us to use. > > Topic: The Colony https://colony.io > > Introduction to "The Colony", a new platform to Organize and > Incentivize Collaborators, Contributors, and Communities. > Short demo, followed by some Q&A, help to get people onboarded. > > > https://association.pharo.org/event-3697011 > > 20 Feb 2020 â¢ > 1:30 PM - 2:30 PM (EST) > > NOTE: this is EST time, for Europe, this is 19:30 (the easiest is to > download the calendar entry) >

Feb. 11, 2020