September 2016 - Pharo-users

Re: [Pharo-users] [Pharo-dev] [ANN] FFI Tutorial, Pharo5 / Libclang

by Esteban Lorenzano

this is super goodâ¦ thanks for doing this. once finished I would like to use it as tutorial reference :) cheers, Esteban > On 24 Sep 2016, at 19:25, Ben Coman <btc(a)openInWorld.com> wrote: > > hi all, > > Just announcing that I'm writing a series of posts on using FFI in > Pharo 5 to interface to libclang, the interface library for the LLVM C > compiler. > > http://blog.openinworld.com/2016/09/pharo-libclang-ffi-part-1-preamble/ > > I'm writing this from the perspective of a FFI newbie progressively > learning the system. I've left in a few mis-steps since I think it > can be useful seeing what didn't work. > > cheers -ben >

Sept. 25, 2016

Re: [Pharo-users] [ANN] FFI Tutorial, Pharo5 / Libclang

by Ben Coman

On Sun, Sep 25, 2016 at 1:46 AM, stepharo <stepharo(a)free.fr> wrote: > Did you let > > > LibC class >> ticksSinceStart > ^ self ffiCall: #( uint clock () ) module: LibC > and in Playground inspect followingâ¦ > > FFIPlay ticksSinceStart > "==> 32709046 (or something similar)" > > FFIPlay on purpose? It was unclear to me how this is related to LibC An error. Thanks for picking that up. When I first was trying it I had created that class to hold experiements, but it wsa shorter for the post to put in on the existing class. cheers -ben > > > > Le 24/9/16 Ã 20:25, Ben Coman a Ã©crit : >> >> hi all, >> >> >> Just announcing that I'm writing a series of posts on using FFI in >> Pharo 5 to interface to libclang, the interface library for the LLVM C >> compiler. >> >> http://blog.openinworld.com/2016/09/pharo-libclang-ffi-part-1-preamble/ >> >> I'm writing this from the perspective of a FFI newbie progressively >> learning the system. I've left in a few mis-steps since I think it >> can be useful seeing what didn't work. >> >> cheers -ben > > >

Sept. 24, 2016

Re: [Pharo-users] [ANN] FFI Tutorial, Pharo5 / Libclang

by stepharo

Did you let LibC class >> ticksSinceStart ^ self ffiCall: #( uint clock () ) module: LibC and in Playground inspect followingâ¦ FFIPlay ticksSinceStart "==> 32709046 (or something similar)" FFIPlay on purpose? It was unclear to me how this is related to LibC Le 24/9/16 Ã 20:25, Ben Coman a Ã©crit : > hi all, > > Just announcing that I'm writing a series of posts on using FFI in > Pharo 5 to interface to libclang, the interface library for the LLVM C > compiler. > > http://blog.openinworld.com/2016/09/pharo-libclang-ffi-part-1-preamble/ > > I'm writing this from the perspective of a FFI newbie progressively > learning the system. I've left in a few mis-steps since I think it > can be useful seeing what didn't work. > > cheers -ben

Sept. 24, 2016

Re: [Pharo-users] [ANN] FFI Tutorial, Pharo5 / Libclang

by stepharo

Excellent! Tx for writing that. Le 24/9/16 Ã 20:25, Ben Coman a Ã©crit : > hi all, > > Just announcing that I'm writing a series of posts on using FFI in > Pharo 5 to interface to libclang, the interface library for the LLVM C > compiler. > > http://blog.openinworld.com/2016/09/pharo-libclang-ffi-part-1-preamble/ > > I'm writing this from the perspective of a FFI newbie progressively > learning the system. I've left in a few mis-steps since I think it > can be useful seeing what didn't work. > > cheers -ben > >

Sept. 24, 2016

[ANN] FFI Tutorial, Pharo5 / Libclang

by Ben Coman

hi all, Just announcing that I'm writing a series of posts on using FFI in Pharo 5 to interface to libclang, the interface library for the LLVM C compiler. http://blog.openinworld.com/2016/09/pharo-libclang-ffi-part-1-preamble/ I'm writing this from the perspective of a FFI newbie progressively learning the system. I've left in a few mis-steps since I think it can be useful seeing what didn't work. cheers -ben

Sept. 24, 2016

Re: [Pharo-users] Script to migrate all mcz packages to git?

by Holger Freyther

> On 02 Aug 2016, at 13:23, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > >> Hi Peter, > At the time of the (post) writing it did preserve commit dates, but there was no metadata-less yet. > > In any case, I don't see a reason why it shouldn't preserve commit dates with metadata-less â it goes mcz by mcz and recommits it with given date, no? I have modified >>#basicStoreVersion: to pass the --date option to git and now date/time is preserved. I am copying multiple related packages into the same git repository and would like to "interleave" (based on date) the different packages. In your script you first have: filesSorted := fileBlocks asSortedCollection: sortBlock. files := (filesSorted collect: [ :x | x first ]) asArray. to select which files to actually copy (as Gofer allResolved has a lot more). but after the: goSource fetch. "downloads all mcz on your computer" I would like to mix the different packages based on their date. Would you know which Gofer(?) API I can use to get a version info (?) so I can access the date? holger

Sept. 24, 2016

Re: [Pharo-users] Essential Documentation

by stepharo

Have a look at the Spec video by Johan Fabry during the Pharo days on youtube. Le 23/9/16 Ã 23:32, julius a Ã©crit : > Thanks for you answers! > > I'm aware of the books on the pharo.org/documentation page. But for me that > is not sufficient. I'm currently playing around while programming my fist own and > unguided application. It will be quite simple, just a reminder application where > notes can be added, removed, edited and all of them should trigger a notification when > they are due. I plan to save all notes in a SQLite database, display is done with > spec. I'm interested by your result. It will be a nice example. > While this is basic stuff I often have to go into the source and search for > the correct messages to send and to see what kind of return objects I get. For > example I wanted to use a SortedCollection as data structure for my notes > (consisting of a > string and a date) that should be ordered by date, so since this is not > really described > in the Pharo by Example book I looked at the implementation and searched > online > > It would be definitely better to just have only or in the image a full > documentation > for SortedCollection which links to a full documentation of > OrderedCollection. This is call a class :). Now may be the class comments should be improved. > I have to confess I didn't read Pharo in depth and Pharo for Enterpise yet > but I also don't think its convenient to have all the books open and search there for > documentation. > > Since I think a full searchable documentation would be very helpful > especially for > beginners and I definitely would like to have one I would be happy to > contribute. The books that are based on pillar are in pdf and html. In the past we got a pharodoc but it was just the pharo comments on the web so it was not really useful. > Are there already some efforts toward it or does somebody has an idea how to > accomplish > that? Right now I imagine the best thing would be to have an automated > workflow to read out > the comments of the current release somehow and presenting them online. > Maybe it would > need to write a parser to get them well formatted (so that example code > looks like code and so > on). So if there is any way that I can contribute, I will do. Point us to the point you have problems and tell us what are the class comments that are poor. Finish your project and write a little chapter. This will really help. The chapter does not have to be complete. Did you read the chapter of Sven on developing a reddit application in 10 classes? Because having something like that with your project would be great and I can participate if you want. > Best, > Julius > > > > -- > View this message in context: http://forum.world.st/Essential-Documentation-tp4916861p4916904.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Sept. 24, 2016

Re: [Pharo-users] Essential Documentation

by julius

Thanks for you answers! I'm aware of the books on the pharo.org/documentation page. But for me that is not sufficient. I'm currently playing around while programming my fist own and unguided application. It will be quite simple, just a reminder application where notes can be added, removed, edited and all of them should trigger a notification when they are due. I plan to save all notes in a SQLite database, display is done with spec. While this is basic stuff I often have to go into the source and search for the correct messages to send and to see what kind of return objects I get. For example I wanted to use a SortedCollection as data structure for my notes (consisting of a string and a date) that should be ordered by date, so since this is not really described in the Pharo by Example book I looked at the implementation and searched online. It would be definitely better to just have only or in the image a full documentation for SortedCollection which links to a full documentation of OrderedCollection. I have to confess I didn't read Pharo in depth and Pharo for Enterpise yet but I also don't think its convenient to have all the books open and search there for documentation. Since I think a full searchable documentation would be very helpful especially for beginners and I definitely would like to have one I would be happy to contribute. Are there already some efforts toward it or does somebody has an idea how to accomplish that? Right now I imagine the best thing would be to have an automated workflow to read out the comments of the current release somehow and presenting them online. Maybe it would need to write a parser to get them well formatted (so that example code looks like code and so on). So if there is any way that I can contribute, I will do. Best, Julius -- View this message in context: http://forum.world.st/Essential-Documentation-tp4916861p4916904.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 23, 2016

Re: [Pharo-users] Essential Documentation

by Sven Van Caekenberghe

Hi Julius, Have a look at http://books.pharo.org These should certainly get you started. Sven > On 23 Sep 2016, at 18:16, julius <julius(a)wokabulary.com> wrote: > > Probably this is a very beginners question but is there a documentation > online > or within the Pharo image for all the base-framework components like all > collections, Morphic, Numbers and so on? > > I know Pharo uses a lot the 'see and discover yourself' approach but > sometimes, > especially for beginners it would be nice to have a documentation for most > classes > and also have programming guides. Coming from macOS and iOS development I > think about something like Swift or Objective-C has. For example you have > every > class there documented but also you have programming guides for how to draw > graphics. It would be really helpful to have somthing like that for example > for > Voyage (maybe it's there but I did not found it). > > Thanks for helping me out! > Julius > > > > -- > View this message in context: http://forum.world.st/Essential-Documentation-tp4916861.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Sept. 23, 2016

Re: [Pharo-users] Essential Documentation

by Serge Stinckwich

On Fri, Sep 23, 2016 at 6:16 PM, julius <julius(a)wokabulary.com> wrote: > Probably this is a very beginners question but is there a documentation > online > or within the Pharo image for all the base-framework components like all > collections, Morphic, Numbers and so on? > > I know Pharo uses a lot the 'see and discover yourself' approach but > sometimes, > especially for beginners it would be nice to have a documentation for most > classes > and also have programming guides. Coming from macOS and iOS development I > think about something like Swift or Objective-C has. For example you have > every > class there documented but also you have programming guides for how to draw > graphics. It would be really helpful to have somthing like that for example > for > Voyage (maybe it's there but I did not found it). Yes I agree with the fact to have all classes/methods documented. Can you contribute in that direction ? -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 23, 2016