- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Screencast: Creating C library bindings with TalkFFI for libgit2

by Ciprian Teodorov

Hi Max, I've just integrated some of my latest changes into a new version 1.4 of TalkFFI. Amongst others it prints clang erros in the transcript. On my libgit2 checkout there are some compilation errors. I've moved the development version to this one, so if you want to try it just do the typical: Gofer it smalltalkhubUser: 'CipT' project: 'TalkFFI'; package: 'ConfigurationOfTalkFFI'; load. (Smalltalk at: #ConfigurationOfTalkFFI) loadDevelopment. TalkFFIExamples libgit2Mapping version 1.4 - clang diagnostic messages on header loading - added the possibility to filter the functions in a headerFile using a user defined block - added option to check the function availability in a dynamic library specified during conversion. - added simple generator that pulls functions into type classes. Instance side, if the first function argument matches the type class. Class side of the return type, if the function's first argument does not match any known type class, but if the return type match a type class. - changed the NativeBoost generator so that instead of NBCharacterType * it generates NBExternalString, to facilitate string passing - fixed uniqueInstance issue On Sun, Apr 7, 2013 at 6:18 PM, Max Leske <maxleske(a)gmail.com> wrote: > Wow! This is embarrassing! I just noticed that the video on Vimeo is the > wrong one (no wonder you kept talking about a premature endingâ¦)! I'm > replacing it right now. > > Sorry for that. > Can't wait to see it ;) > > Max > > > On 06.04.2013, at 23:38, Max Leske <maxleske(a)gmail.com> wrote: > > > On 06.04.2013, at 23:09, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> > wrote: > > Hi Max, > > your video is good, too bad that it stops prematurely. > > It helped me to spot a tiny issue with the libgit2 generation script. The > C compile options ( '-D__STDC_CONSTANT_MACROS' '-D__STDC_LIMIT_MACROS') > that are present there are just a copy paste error, since when created that > method I've modified the one I've used for generating llvm bindings (which > really needs them). > > > For libgit2 i don't now, I think they aren't needed. I've just tried on my > machine with options := {('-I' , includeDir fullName)}. > and it seems to work > > > I also think they're not necessary. > > > Now libclang is the reason that in some cases we need such options. Since > we use libclang to parse the header files we should make sure that we pass > it everything it needs to successfully process the header. > So if anyone has a hard time generating bindings with talkffi for a > library X, then a starting point might be to try understanding what are the > options needed by clang to compile the headers. > > In the future I plan to add some kind of script editor for writing the > bindings, which will show the messages from libclang. so that in case of > compilation error (due to missing options, or c syntax errors) we can see > them in the image. > > About generating the bindings directly on a mac, I've done it using a hand > compiled version of libclang configured with (../configure > --enable-optimized --enable-jit --target=i686-apple-darwin10). So if you > are willing to download libclang and compile it, maybe you don't need a > linux vm. > > > Thanks for the explanations. > > > Ok, that's it for now. Thanks again for the great video > > > My pleasure :) > > Ciprian > > > > > On Sat, Apr 6, 2013 at 10:02 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> >> On 06.04.2013, at 20:21, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: >> >> > Hi: >> > >> > On 06 Apr 2013, at 19:30, Max Leske wrote: >> > >> >> I recorded a new screencast with a short tutorial on how bindings for >> libgit2 (or any other library for that matter) can be created using TalkFFI. >> >> >> >> http://vimeo.com/maxleske/talkffibindings >> > >> > I skimmed through it. Looks good. >> > But, I noticed that the video actually stops before generating the >> bindings :) >> > That makes it feel like there is something missing. >> >> Damn! Got me :) I realized that straight after I had hit stop. >> Still, for me the hard part was the compilation and setup. I figured out >> the bindings pritty quickly. >> >> Maybe I'll add short bit at the end tomorrow. >> >> Max >> >> > >> > Best regards >> > Stefan >> > >> > >> > >> > -- >> > Stefan Marr >> > Software Languages Lab >> > Vrije Universiteit Brussel >> > Pleinlaan 2 / B-1050 Brussels / Belgium >> > http://soft.vub.ac.be/~smarr >> > Phone: +32 2 629 2974 >> > Fax: +32 2 629 3525 >> > >> > >> >> >> > > > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro > > > > -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

April 7, 2013

Re: [Pharo-project] Screencast: Creating C library bindings with TalkFFI for libgit2

by Max Leske

Wow! This is embarrassing! I just noticed that the video on Vimeo is the wrong one (no wonder you kept talking about a premature endingâ¦)! I'm replacing it right now. Sorry for that. Max On 06.04.2013, at 23:38, Max Leske <maxleske(a)gmail.com> wrote: > > On 06.04.2013, at 23:09, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: > >> Hi Max, >> >> your video is good, too bad that it stops prematurely. >> >> It helped me to spot a tiny issue with the libgit2 generation script. The C compile options ( '-D__STDC_CONSTANT_MACROS' '-D__STDC_LIMIT_MACROS') that are present there are just a copy paste error, since when created that method I've modified the one I've used for generating llvm bindings (which really needs them). >> >> For libgit2 i don't now, I think they aren't needed. I've just tried on my machine with options := {('-I' , includeDir fullName)}. >> and it seems to work > > I also think they're not necessary. > >> >> Now libclang is the reason that in some cases we need such options. Since we use libclang to parse the header files we should make sure that we pass it everything it needs to successfully process the header. >> So if anyone has a hard time generating bindings with talkffi for a library X, then a starting point might be to try understanding what are the options needed by clang to compile the headers. >> >> In the future I plan to add some kind of script editor for writing the bindings, which will show the messages from libclang. so that in case of compilation error (due to missing options, or c syntax errors) we can see them in the image. >> >> About generating the bindings directly on a mac, I've done it using a hand compiled version of libclang configured with (../configure --enable-optimized --enable-jit --target=i686-apple-darwin10). So if you are willing to download libclang and compile it, maybe you don't need a linux vm. > > Thanks for the explanations. > >> >> Ok, that's it for now. Thanks again for the great video > > My pleasure :) > >> Ciprian >> >> >> >> >> On Sat, Apr 6, 2013 at 10:02 PM, Max Leske <maxleske(a)gmail.com> wrote: >> >> On 06.04.2013, at 20:21, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: >> >> > Hi: >> > >> > On 06 Apr 2013, at 19:30, Max Leske wrote: >> > >> >> I recorded a new screencast with a short tutorial on how bindings for libgit2 (or any other library for that matter) can be created using TalkFFI. >> >> >> >> http://vimeo.com/maxleske/talkffibindings >> > >> > I skimmed through it. Looks good. >> > But, I noticed that the video actually stops before generating the bindings :) >> > That makes it feel like there is something missing. >> >> Damn! Got me :) I realized that straight after I had hit stop. >> Still, for me the hard part was the compilation and setup. I figured out the bindings pritty quickly. >> >> Maybe I'll add short bit at the end tomorrow. >> >> Max >> >> > >> > Best regards >> > Stefan >> > >> > >> > >> > -- >> > Stefan Marr >> > Software Languages Lab >> > Vrije Universiteit Brussel >> > Pleinlaan 2 / B-1050 Brussels / Belgium >> > http://soft.vub.ac.be/~smarr >> > Phone: +32 2 629 2974 >> > Fax: +32 2 629 3525 >> > >> > >> >> >> >> >> >> -- >> Dr. Ciprian TEODOROV >> IngÃ©nieur DÃ©veloppement CAO >> >> tÃ©l : 06 08 54 73 48 >> mail : ciprian.teodorov(a)gmail.com >> www.teodorov.ro >

April 7, 2013

Re: [Pharo-project] How to define a ConfigurationOf with a #development version that depends on a baseline?

by Sabine KnÃ¶fel

I also worked with Envy for more than 10 years and after getting used to it (which took a certain time), it was the stable base for my daily work. Now I am learning to work with metacello/monticello. I find myself regularly thinking "hm, in Envy it was ...". I think that taking some of the principles of Envy would make sense. Sabine Von meinem iPad gesendet Am 07.04.2013 um 10:12 schrieb Marten Feldtmann <marten(a)schrievkrom.de>: > Alexandre, > > I had the same feeling, when I had to use it starting around 1997 in our company :-) > > We are now C#'pers, but it is interesting to see, that one item is remembered by all persons in our team from the Smalltalk-epoche in our company in a friendly way: ENVY. > > This was the item, which seem to impressed most of the people - especially *after* switching to VS. > > Marten > > On 07.04.2013 04:48, Alexandre Bergel wrote: >> Hi Marten, >> >> Frankly speaking, I find Envy way too complicated. I am using it these days and I am really not happy with. If I have to read a book to understand how it works, than there is no way I can teach students on how to use it in a reasonable amount of time. >> Configuration Map, Application, edition, scratch version and many more are way too many concepts, in my opinion. > <marten.vcf>

April 7, 2013

Re: [Pharo-project] How to define a ConfigurationOf with a #development version that depends on a baseline?

by stephane ducasse

This is not a question of wanting or not. The key question is - does it scale - do we have the manpower to maintain it - is it key for the future Stef > Hi. > > And what you think about OOSCM which was presented at last ESUG (and maybe at 2010 too)? > > Does Pharo wants such kind of technology? > > > 2013/4/6 Alexandre Bergel <alexandre.bergel(a)me.com> > Just a question: Is there any plan for a Metacello 2? > We have learnt a lot and we have a clear idea on a number of versioning scenarios. What do we want the future of packaging in Pharo to look like? > > Alexandre > > > On Apr 2, 2013, at 7:15 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > > http://stackoverflow.com/questions/15762706/how-to-define-a-configurationof… > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Success is the ability to go from one failure to another without > > losing enthusiasm." > > Winston Churchill > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

April 7, 2013

Re: [Pharo-project] get.pharo.org is unreachable

by Marcus Denker

On Apr 7, 2013, at 1:18 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Just in case you did not see it, it seems that http://get.pharo.org is unreachable at the moment. Is anyone looking into this? > Seems to work againâ¦ strange, but the good thing is that starting next week it will point directly to a server (no forwarding anymore). Marcus

April 7, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Ben Coman

Esteban A. Maringolo wrote: > 2013/4/7 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: > >> Experienced that too ( a lot ) >> > > Me too. > > I have other comments regarding "first use experiences" of > smalltalkers and non-smalltalkers. > Once I contribute something, I'll make them public. :-) > > Regards! > > Esteban > > > That would be interesting.

April 7, 2013

Re: [Pharo-project] Collect all references to AnObsoleteFoo

by roberto.minelli＠usi.ch

I'd say that handling obsolete reference this way is very good! I'd put this behavior in Fuel! Cheers, R On Apr 6, 2013, at 2:27 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Martin, should be manage obsolete always that way (meaning to put such behavior directly inside Fuel)? > If not, could be write your awesome code in the Fuel website? > > Thanks!!! :) > > > > > On Sat, Apr 6, 2013 at 8:26 AM, roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> wrote: > Martin, your solution is awesome. > > I've seen the presentation at Pharoconf about setting an analyzer to the serializer and I was thinking in that direction. > > Thanks a lot, > R > > On Apr 5, 2013, at 4:59 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > > > As Fernando said, probably is better for you to substitute the obsolete class by a ring definition. Look here: > > > > http://ws.stfx.eu/OAVG8IXKWOYA > > > > Don't need to filein the workaround of my previous email. > > > > Martin > > > > > > On Fri, Apr 5, 2013 at 4:47 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > > Hi, > > I'm sorry for my delay. I didn't stop to think a good solution. There were interesting answers before mine. But if it's a prototype... maybe this workaround helps you. I played with this code: > > > > http://ws.stfx.eu/HYWM1ZB9R45K > > > > (the first time I use the shared workspace :-) > > > > if you file in the attached file, it materializes the new A class. > > > > But this will be not useful for you, if either: > > - you don't have the "original class" at materialization time > > - you don't want to know if the class was obsolete at serialization time > > > > HTH > > Martin > > > > > > > > On Tue, Apr 2, 2013 at 7:33 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > > On 02/04/13 12:50 AM, roberto.minelli-BHDiRLqP7qo(a)public.gmane.org wrote: > > > > Is there any way to "browse" through such references to understand where are they? > > > > From an inspector, choose the "Explore pointers", making sure you've selected the object that you're trying to understand what is referencing it. > > > > It takes trial & error, and intuition on which pointers to follow. This method has often been unsuccessful for me. > > > > Another approach (my memory is fuzzy), was to put a halt at a suitable place during the Fuel serialization. Then explore the intermediate structures used by Fuel, to try to find out why Fuel thinks it needs to serialize that object. > > > > Yet another approach is to put a halt in the Fuel materialization, and explore the intermediate structures used by Fuel. You might even set up a mapping of the obsolete class to some temporary class, which allows Fuel to fully materialize the saved objects. You can then explore the Fuel intermediate structures, as well as the final de-serialized object structure. > > > > > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com

April 7, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Esteban A. Maringolo

2013/4/7 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: > Experienced that too ( a lot ) Me too. I have other comments regarding "first use experiences" of smalltalkers and non-smalltalkers. Once I contribute something, I'll make them public. :-) Regards! Esteban

April 7, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Benjamin

Experienced that too ( a lot ) Ben On Apr 7, 2013, at 2:20 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > oh... I taught smalltalk for 3 years, using Pharo every lesson. > > During those years, I didn't met any single student that didn't tried to press enter the first N times to get a completion. > And every time the student complained, until I repeated (often several times) that they should use tab instead. > And every time they make the same question "why is not like in [put your favorite IDE here]?"... still today, I do not have an answer, that's why I think is better not to provoke the question :) > > cheers, > Esteban > > > On Apr 7, 2013, at 2:03 PM, Ben Coman <btc(a)openInWorld.com> wrote: > >> Sounds like a good classroom assignment for a class incorporating Usability Testing :) >> >> Esteban Lorenzano wrote: >>> I still think useEnterToAccept has to be true >>> I sustain the idea of lower the entry level for the newcomers, instead supporting as default the use-workflow of power users (they have a settings browser there). We took this decision last year and I think it was a good one... not that we cannot change, but I would stick with it for now. >>> I think the current completion functionality has some other problems that makes it sometimes uncomfortable to use... >>> >>> On Apr 7, 2013, at 12:16 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>> >>> >>>> On Apr 6, 2013, at 11:44 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>>> >>>> >>>>> If everybody likes it, maybe we should consider putting this configuration as default, no ? >>>>> >>>> yes but first I would like to see the difference because I do not like it :) >>>> >>>> >>>> >>>>> Ben >>>>> >>>>> On Apr 6, 2013, at 8:59 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >>>>> >>>>> >>>>>> stephane ducasse wrote >>>>>> >>>>>>> would it be possible to get a couple of settings that you use? >>>>>>> >>>>>> NECPreferences >>>>>> enabled: true; >>>>>> caseSensitive: true; >>>>>> expandPrefixes: true; >>>>>> useEnterToAccept: false; >>>>>> smartCharacters: true; >>>>>> smartCharactersWithDoubleSpace: '[]{}'; >>>>>> spaceAfterCompletion: false; >>>>>> popupAutomaticDelay: 100. >>>>>> >>>>>> >>>>>> >>>>>> ----- >>>>>> Cheers, >>>>>> Sean >>>>>> -- >>>>>> View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… >>>>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>>>>> >>>>>> >>> >>> >>> >> >> > >

April 7, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Esteban Lorenzano

oh... I taught smalltalk for 3 years, using Pharo every lesson. During those years, I didn't met any single student that didn't tried to press enter the first N times to get a completion. And every time the student complained, until I repeated (often several times) that they should use tab instead. And every time they make the same question "why is not like in [put your favorite IDE here]?"... still today, I do not have an answer, that's why I think is better not to provoke the question :) cheers, Esteban On Apr 7, 2013, at 2:03 PM, Ben Coman <btc(a)openInWorld.com> wrote: > Sounds like a good classroom assignment for a class incorporating Usability Testing :) > > Esteban Lorenzano wrote: >> I still think useEnterToAccept has to be true >> I sustain the idea of lower the entry level for the newcomers, instead supporting as default the use-workflow of power users (they have a settings browser there). We took this decision last year and I think it was a good one... not that we cannot change, but I would stick with it for now. >> I think the current completion functionality has some other problems that makes it sometimes uncomfortable to use... >> >> On Apr 7, 2013, at 12:16 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >> >>> On Apr 6, 2013, at 11:44 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>> >>> >>>> If everybody likes it, maybe we should consider putting this configuration as default, no ? >>>> >>> yes but first I would like to see the difference because I do not like it :) >>> >>> >>> >>>> Ben >>>> >>>> On Apr 6, 2013, at 8:59 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >>>> >>>> >>>>> stephane ducasse wrote >>>>> >>>>>> would it be possible to get a couple of settings that you use? >>>>>> >>>>> NECPreferences >>>>> enabled: true; >>>>> caseSensitive: true; >>>>> expandPrefixes: true; >>>>> useEnterToAccept: false; >>>>> smartCharacters: true; >>>>> smartCharactersWithDoubleSpace: '[]{}'; >>>>> spaceAfterCompletion: false; >>>>> popupAutomaticDelay: 100. >>>>> >>>>> >>>>> >>>>> ----- >>>>> Cheers, >>>>> Sean >>>>> -- >>>>> View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… >>>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>>>> >>>>> >> >> >> > >

April 7, 2013