November 2013 - Pharo-users

Re: [Pharo-users] ProfStef, Lesson 25 - Unknown selector

by StÃ©phane Ducasse

I do not understand I got many old mails (may be just did not read during the sprint and after I was flying). Stef On Nov 9, 2013, at 8:28 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 09 Nov 2013, at 01:30, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> marcus >> >> did you open an entry? >> > > It is already fixed in 3.0 and 2.0 :-) > >> Stef >> >> On Nov 5, 2013, at 9:51 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> (Object compiledMethodAt: #halt) valueWithReceiver: nil arguments: #() >>> >>> >>> We should update ProfStef >>> >>> Marcus >> >

Nov. 9, 2013

Re: [Pharo-users] Spec - Tutorial Series

by Bahman Movaqar

On 11/09/2013 12:23, btc(a)openinworld.com wrote: > Some minor nit-picks... > > > "please do so as we are going to iterate over what was done there." > I don't understand what you mean by 'iterate over'? Do you me 'build on'? Yes, that's what I meant: "improve". If you find it hard to understand, let me know. > > > "let's first settle for a target design. For the rest of this > episode, we will try to achieve the following design. " > I get to the bottom and the last snapshot it doesn't look the same as > the one at the top. At the top you should mention that your target > design is achieved over several posts (if that is the case). No wonder it doesn't match :-) Figure 1 is not a snapshot from the system. It is the UI design done in LibreOffice draw. I'll mention that. > > > "Note lines 9, 10, 17 and 18." > "Note new lines 9, 10, 17 and 18." > > * At the top you should specify what version of Pharo the tutorial > relates to. Information on the web hangs around for a very long time > and someone could get trapped later trying your tutorial on a later > version of Pharo. Correct. That's why at the beginning of this episode the reader is asked to first proceed to episode 1 if he hasn't done so already and in episode one in Prerequisites section (http://www.bahmanm.com/blogs/spec-part-1-basics#section-1) it is mentioned that for this series Pharo 2.0 will be used. > > * Regarding #defaultSpec, I happen to like what is used in PharoLauncher > specLayout > <spec: #default> > ^ SpecLayout composed ...etc I don't understand your point. Could you elaborate a bit more on this? > > Overall it a nice next step introducing just a bit more > functionality. It reads very well. I look forward to the next one. Your comments are much appreciated. It's always very useful to have another couple of eyes, QC a document :-) Thanks. -- Bahman Movaqar (http://BahmanM.com) ERP Evaluation, Implementation & Deployment Consultant PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Nov. 9, 2013

Re: [Pharo-users] Using FFI

by btc＠openinworld.com

Nov. 9, 2013

Re: [Pharo-users] Spec - Tutorial Series

by btc＠openinworld.com

Bahman Movaqar wrote: > Hi all, > > A new episode is availabe: > Spec - Part II: The Layout (http://www.bahmanm.com/blogs/spec-part-2-layout) > > I'd appreciate any comments/hints. TIA, > > Some minor nit-picks... > "please do so as we are going to iterate over what was done there." I don't understand what you mean by 'iterate over'? Do you me 'build on'? > "let's first settle for a target design. For the rest of this episode, we will try to achieve the following design. " I get to the bottom and the last snapshot it doesn't look the same as the one at the top. At the top you should mention that your target design is achieved over several posts (if that is the case). > "Note lines 9, 10, 17 and 18." "Note new lines 9, 10, 17 and 18." * At the top you should specify what version of Pharo the tutorial relates to. Information on the web hangs around for a very long time and someone could get trapped later trying your tutorial on a later version of Pharo. * Regarding #defaultSpec, I happen to like what is used in PharoLauncher specLayout <spec: #default> ^ SpecLayout composed ...etc Overall it a nice next step introducing just a bit more functionality. It reads very well. I look forward to the next one. cheers -ben P.S. Some questions for Spec gurus... * looking at #defaultSpec from this episode, if the pattern is always... mainColumn newRow: [ :aRow | aRow doStuff; otherStuff... ] what is gained over a pattern like... mainColumn newRow doStuff ; otherStuff. * is #defaultSpec always going to return a SpecLayout? In which case #defaultSpec feels like is should be #defaultSpecLayout. cheers -ben

Nov. 9, 2013

Re: [Pharo-users] Spec - Grid/Table Layout

by btc＠openinworld.com

Nov. 9, 2013

Re: [Pharo-users] Why won't my Pharo download run?

by btc＠openinworld.com

Nov. 9, 2013

Re: [Pharo-users] Repository of petit parser

by Tudor Girba

Agreed. But, the ConfigurationOfPetitParser is up to date. It has groups to distinguish between between core and gui. The only problem that Norbert raised is that when using Snapshotcello, the groups are lost due to flattening of the entire configuration. Doru On Sat, Nov 9, 2013 at 2:12 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Guys > > even if one day we may integrate petitparser (so far I do not see why - > but do not comment). We need an up to date configuration > because we want everything with configuration because we want to bootstrap > 4.0. > > Stef > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 9, 2013

Re: [Pharo-users] ProfStef, Lesson 25 - Unknown selector

by ClÃ©ment Bera

This bug is fixed and integrated in Pharo 3. 2013/11/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > marcus > > did you open an entry? > > Stef > > On Nov 5, 2013, at 9:51 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > (Object compiledMethodAt: #halt) valueWithReceiver: nil arguments: #() > > > We should update ProfStef > > Marcus > > >

Nov. 9, 2013

Re: [Pharo-users] ProfStef, Lesson 25 - Unknown selector

by Marcus Denker

On 09 Nov 2013, at 01:30, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > marcus > > did you open an entry? > It is already fixed in 3.0 and 2.0 :-) > Stef > > On Nov 5, 2013, at 9:51 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> (Object compiledMethodAt: #halt) valueWithReceiver: nil arguments: #() >> >> >> We should update ProfStef >> >> Marcus >

Nov. 9, 2013

Re: [Pharo-users] Using FFI

by Annick Fron

I have answered I think EnvoyÃ© de mon iPod > Le 9 nov. 2013 Ã 02:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a Ã©crit : > > Annick > > You cannot expect people to respond to you if you do not provide > full context + information. > On the long term people will stop to reply to you. > Repeat after me: > which image? > which OS version? > which vm version? > > I think that we are pretty nice people but do not force us to always ask the same questions. > We are all busy. > > > Stef > > >> On Nov 6, 2013, at 6:15 PM, Annick Fron <info(a)afceurope.com> wrote: >> >> I am using the latest download from version 2 >> Annick >> >>> Le 31 oct. 2013 Ã 18:47, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : >>> >>> ok... then we have a problem. >>> but we need more data... >>> >>> which image version are you using? >>> and which vm version? >>> >>> cheers, >>> Esteban >>> >>>> On Oct 31, 2013, at 11:24 AM, Annick Fron <info(a)afceurope.com> wrote: >>>> >>>> I hÃ¢ve thÃ© error on Windows >>>> >>>> EnvoyÃ© de mon iPod >>>> >>>>> Le 31 oct. 2013 Ã 14:51, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : >>>>> >>>>> >>>>> >>>>> >>>>>> On 31 October 2013 11:23, Annick Fron <info(a)afceurope.com> wrote: >>>>>> Hi Igor >>>>>> >>>>>> I have done that, but still gets an error, do I need to remove NativeBoost ? >>>>>> Annick >>>>> >>>>> FFI not supported on ARM >>>>> >>>>>>> Le 30 oct. 2013 Ã 14:12, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : >>>>>>> >>>>>>> AFAIK, it should be in Configurations browser. >>>>>>> Else try this: >>>>>>> >>>>>>> Gofer new >>>>>>> squeaksource: 'MetacelloRepository'; >>>>>>> >>>>>>> package: 'ConfigurationOfFFI'; >>>>>>> load. >>>>>>> (Smalltalk at: #ConfigurationOfFFI) project lastVersion load >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On 30 October 2013 09:41, Annick Fron <info(a)afceurope.com> wrote: >>>>>>>> My problem is that the Raspberry does not support native boost (as yet !). >>>>>>>> Where can I load the old FFI ? >>>>>>>> >>>>>>>>> Le 29 oct. 2013 Ã 16:57, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 29 October 2013 16:27, Annick Fron <info(a)afceurope.com> wrote: >>>>>>>>>> Hi >>>>>>>>>> >>>>>>>>>> I want to launch a simple init with the following C signature : >>>>>>>>>> >>>>>>>>>> void gst_init (int *argc, char **argv[]) >>>>>>>>>> >>>>>>>>>> If I write >>>>>>>>>> >>>>>>>>>> <apicall: void 'gst_init' (int*, char**) module: 'blabla'> >>>>>>>>>> >>>>>>>>>> I get a Smalltalk syntax error >>>>>>>>>> >>>>>>>>>> Annick Fron >>>>>>>>> >>>>>>>>> To use this syntax, you must load old FFI implementation. >>>>>>>>> Or use NativeBoost: >>>>>>>>> >>>>>>>>> init: intarg with: chararg >>>>>>>>> <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> self nbCall: 'void gst_init (int * intarg, char ** chararg)' module: 'blaba' >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Best regards, >>>>>>>>> Igor Stasenko. >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Igor Stasenko. >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko. >

Nov. 9, 2013