July 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Tim Mackinnon

Phil - I think your message ended up in the wrong thread? You should try and attend ESUG though - its a great conference. I found a cheap hotel on Booking.com - but I bet there might a YMC or something in Cambridge that might make it more affordable (I recall people doing something similar in the past). Even if your accommodate is far away - it looks quite cheap to rent a bicycle for the week and cycle in. Tim On 11 Jul 2014, at 13:57, philippeback [via Smalltalk] <ml-node+s1294792n4767516h76(a)n4.nabble.com> wrote: > I'd like to come but hotel/accomodation rates looked prohibitive to me. > > Are there affordable options ? > > Phil > > > On Fri, Jul 11, 2014 at 12:47 PM, Nicolai Hess <[hidden email]> wrote: > > > > 2014-07-11 12:15 GMT+02:00 Tim Mackinnon <[hidden email]>: > Nicolai - I have just seen that you have a fix for one of the Nautilus issues > I raised (awesome). > > Forgive me - but I don't yet know how to load up a slice and test it (but am > willing to learn, so I can perhaps help more in the future). > > I've loaded up the latest Pharo 4.0 image - luanched monticello - but how do > I load a slice? > > select repository "http://smalltalkhub.com/mc/Pharo/Pharo40Inbox/main" in the right pane. > -open that repository. > -enter the slice number in the left or right field. > -select the slice in the list on the right side (there may be different slices for one issue) > -and choose "Load" for loading this slice or > "Merge" If you want to see the diff before loading. > > > > If its written up somewhere - I'm happy to go and read. > > I'm assuming the idea is that when you report a bug, if someone fixes it - > you try and verify it and then I can mark it resolved in Fogbugz? > > Yes, we need people testing and reviewing the bug fixes. > > Just write a note if it is working. > If it is not working or has other issues, change the status back to "work needed" > > Status description: > https://pharo.fogbugz.com/?W65 > > > Nicolai > > > Tim > > > > -- > View this message in context: http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… > To unsubscribe from Should I be reporting bugs in Pharo 3.0?, click here. > NAML -- View this message in context: http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 11, 2014

Re: [Pharo-users] Voyage: default class to collection mapping

by Esteban Lorenzano

you also can change the collection name without overriding the method, you just need to declare a <mongoContainer> method: MyClass class>>#mongoContainer <mongoContainer> ^ VOMongoContainer new collectionName: âmynameâ; yourself the purpose of the method is, as Gaston says, just to sanitize the name (and yes, I just copied the pier implementation). cheers, Esteban On 11 Jul 2014, at 15:43, GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> wrote: > Hi Torsten. > > May not be the case, but I've seen do that elsewhere (in Pier I think) and the reason is simply remove (sanitize) the namespace of the class (the first two letters in uppercase). > > Best. > > > 2014-07-09 17:12 GMT-03:00 Torsten Bergmann <astares(a)gmx.de>: > Voyage by default provides this: > > voyageCollectionName > "This method can be overridden with a more meaningful collection name" > ^ ((self persistentClass name first: 3) allSatisfy: #isUppercase) > ifTrue: [ (self persistentClass name allButFirst: 2) asLegalSelector ] > ifFalse: [ self persistentClass name asLegalSelector ] > > > So a class name like Association will end up in a mongo collection > like "association". > > But a class name with a prefix like "PDFLetter" will end up in a mongo > collection name like "fLetter". > > Is there a reason for this specific default behavior and not having the > class name (by default) as the collection name in mongo? I know I can override > the method - but I wonder why it is treated specially also leading to potential > conflicts: > > PDFLetter voyageCollectionName -> #fLetter > FLetter voyageCollectionName -> #fLetter > > Thx > T. > > >

July 11, 2014

Re: [Pharo-users] Voyage: default class to collection mapping

by GastÃ³n Dall' Oglio

Hi Torsten. May not be the case, but I've seen do that elsewhere (in Pier I think) and the reason is simply remove (sanitize) the namespace of the class (the first two letters in uppercase). Best. 2014-07-09 17:12 GMT-03:00 Torsten Bergmann <astares(a)gmx.de>: > Voyage by default provides this: > > voyageCollectionName > "This method can be overridden with a more meaningful collection > name" > ^ ((self persistentClass name first: 3) allSatisfy: #isUppercase) > ifTrue: [ (self persistentClass name allButFirst: 2) > asLegalSelector ] > ifFalse: [ self persistentClass name asLegalSelector ] > > > So a class name like Association will end up in a mongo collection > like "association". > > But a class name with a prefix like "PDFLetter" will end up in a mongo > collection name like "fLetter". > > Is there a reason for this specific default behavior and not having the > class name (by default) as the collection name in mongo? I know I can > override > the method - but I wonder why it is treated specially also leading to > potential > conflicts: > > PDFLetter voyageCollectionName -> #fLetter > FLetter voyageCollectionName -> #fLetter > > Thx > T. > > >

July 11, 2014

Re: [Pharo-users] Using FFI

by Annick Fron

Actually the problem was I had forgotten to put the right number of arguments in the Smalltalk method â¦ Too bad â¦ Le 10 juil. 2014 Ã 11:54, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > On 10 Jul 2014, at 02:32, Andres Valloud <avalloud(a)smalltalk.comcastbiz.net> wrote: > >> On 64 bit Windows a long is 32 bits and pointers are 64 bits, so that type of replacement is not going to work in the long runâ¦ > > Of course, but letâs take care about that problem when actually become a problem :) > Hopefully, for when we finally have a 64bits with FFI, we will have a proper ** interpretation, but the workaround is the fastest solution you can have for now. > > Esteban > >> >> On 7/9/14 8:20 , Esteban Lorenzano wrote: >>> yes, FFI does not handle ** arguments. >>> I always replace it by ulong instead (it is the same, after all) >>> >>> Esteban >>> >>> On 09 Jul 2014, at 17:17, ClÃ©ment Bera <bera.clement(a)gmail.com >>> <mailto:bera.clement@gmail.com>> wrote: >>> >>>> Hello, >>>> >>>> This bug happen both with the old and new compiler. >>>> >>>> The error tells you that the number of arguments of your smalltalk >>>> method does not match the number of argument of the C method you want >>>> to call (but it seemsthe number of arguments is correct). >>>> >>>> This works fine: >>>> >>>> <apicall: int 'gst_init_check' (int char* int) module: >>>> 'libgstreamer1.0-0.so <http://libgstreamer1.0-0.so/>'> >>>> ^self externalCallFailed >>>> >>>> This works fine too: >>>> >>>> <apicall: int 'gst_init_check' (int* char* int*) module: >>>> 'libgstreamer1.0-0.so <http://libgstreamer1.0-0.so/>'> >>>> ^self externalCallFailed >>>> >>>> So it seems the bug comes from the parser missparsing ** . I am not >>>> familiar with C enough to help, I don't know what means ** (Is it a >>>> pointer pointing to a pointer pointing to the actual data ?). >>>> >>>> Perhaps someone who knows how to use FFI can give a better answer. >>>> >>>> Esteban ? Guille ? >>>> >>>> >>>> 2014-07-09 16:39 GMT+02:00 Annick Fron <info(a)afceurope.com >>>> <mailto:info@afceurope.com>>: >>>> >>>> >>>> Hi, >>>> >>>> >>>> >>>> I am trying to use FFI on linux with pharo 3 using version >>>> 31 of FFI. >>>> >>>> I have written the following method : >>>> >>>> >>>> <apicall: int 'gst_init_check' (int* char** int*) module: >>>> 'libgstreamer1.0-0.so <http://libgstreamer1.0-0.so/>'> >>>> >>>> ^self externalCallFailed >>>> >>>> >>>> ==== >>>> >>>> but when accepting it I get a syntax error Â« matching number of >>>> arguments Â» >>>> Annick Fron >>>> >>>> >>> >> > >

July 11, 2014

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by phil＠highoctane.be

I'd like to come but hotel/accomodation rates looked prohibitive to me. Are there affordable options ? Phil On Fri, Jul 11, 2014 at 12:47 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2014-07-11 12:15 GMT+02:00 Tim Mackinnon <tamackinnon(a)gmail.com>: > >> Nicolai - I have just seen that you have a fix for one of the Nautilus >> issues >> I raised (awesome). >> >> Forgive me - but I don't yet know how to load up a slice and test it (but >> am >> willing to learn, so I can perhaps help more in the future). >> >> I've loaded up the latest Pharo 4.0 image - luanched monticello - but how >> do >> I load a slice? >> > > select repository "http://smalltalkhub.com/mc/Pharo/Pharo40Inbox/main" in > the right pane. > -open that repository. > -enter the slice number in the left or right field. > -select the slice in the list on the right side (there may be different > slices for one issue) > -and choose "Load" for loading this slice or > "Merge" If you want to see the diff before loading. > > > >> >> If its written up somewhere - I'm happy to go and read. >> >> I'm assuming the idea is that when you report a bug, if someone fixes it - >> you try and verify it and then I can mark it resolved in Fogbugz? >> > > Yes, we need people testing and reviewing the bug fixes. > > Just write a note if it is working. > If it is not working or has other issues, change the status back to "work > needed" > > Status description: > https://pharo.fogbugz.com/?W65 > > > Nicolai > > >> >> Tim >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >

July 11, 2014

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Nicolai Hess

2014-07-11 12:15 GMT+02:00 Tim Mackinnon <tamackinnon(a)gmail.com>: > Nicolai - I have just seen that you have a fix for one of the Nautilus > issues > I raised (awesome). > > Forgive me - but I don't yet know how to load up a slice and test it (but > am > willing to learn, so I can perhaps help more in the future). > > I've loaded up the latest Pharo 4.0 image - luanched monticello - but how > do > I load a slice? > select repository "http://smalltalkhub.com/mc/Pharo/Pharo40Inbox/main" in the right pane. -open that repository. -enter the slice number in the left or right field. -select the slice in the list on the right side (there may be different slices for one issue) -and choose "Load" for loading this slice or "Merge" If you want to see the diff before loading. > > If its written up somewhere - I'm happy to go and read. > > I'm assuming the idea is that when you report a bug, if someone fixes it - > you try and verify it and then I can mark it resolved in Fogbugz? > Yes, we need people testing and reviewing the bug fixes. Just write a note if it is working. If it is not working or has other issues, change the status back to "work needed" Status description: https://pharo.fogbugz.com/?W65 Nicolai > > Tim > > > > -- > View this message in context: > http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

July 11, 2014

FFI on Linux

by Annick Fron

What should be the name of the module in FFI on Linux ? For instance, if there is a shared lib under /usr/lib named gstreamer-1.0 should it be the name of the shared lib or of a module like libgstreamer-1.0.so ? Do I need to put the full path to the lib or is /usr/lib understood by the call ? Annick

July 11, 2014

Re: [Pharo-users] Working with timezones

by Sven Van Caekenberghe

Exactly ! On 11 Jul 2014, at 11:26, Stephan Eggermont <stephan(a)stack.nl> wrote: > Esteban wrote: >> Anyhow this is too much to add to my app without giving it proper thinking. So let's KISS. > > If you only work with a single server/all servers in the same timezone that translates to: > - Do everything in local time or UTC, have one place where you know your zone, > - Store all time/date without timezone. > - Have in your session timezone information you get from the browser. > - Store in the user info their preferred/last used timezone > - Translate on the outside > > Stephan

July 11, 2014

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Tim Mackinnon

Nicolai - I have just seen that you have a fix for one of the Nautilus issues I raised (awesome). Forgive me - but I don't yet know how to load up a slice and test it (but am willing to learn, so I can perhaps help more in the future). I've loaded up the latest Pharo 4.0 image - luanched monticello - but how do I load a slice? If its written up somewhere - I'm happy to go and read. I'm assuming the idea is that when you report a bug, if someone fixes it - you try and verify it and then I can mark it resolved in Fogbugz? Tim -- View this message in context: http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 11, 2014

Re: [Pharo-users] Working with timezones

by Stephan Eggermont

Esteban wrote: >Anyhow this is too much to add to my app without giving it proper thinking. So let's KISS. If you only work with a single server/all servers in the same timezone that translates to: - Do everything in local time or UTC, have one place where you know your zone, - Store all time/date without timezone. - Have in your session timezone information you get from the browser. - Store in the user info their preferred/last used timezone - Translate on the outside Stephan

July 11, 2014