April 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Improving the programmer experience with Pharo (ideas)

by Max Leske

Cool! On 08.04.2013, at 13:08, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > Hi, I'm just starting an internship for 3 months and we were talking about the scope for my time here. This is a summary of what we have discussed: > The main objective it's to improve the AST and use it to implement as many improvements and refactors/transformations as we can to help the programmer. Some ideas: > - distinguish the code scope (for example, when you have lot of blocks all together when you pass over with the mouse that it get special something to understand where you are) +1. The same for the keyboard would be cool (maybe highlight brackets like it's done in some popular text editors) > - make suggestions depending on what you have selected. Example if it's a variable rename it, or find accesses (â¦) You should take a look at Pavels work Periscope (http://smalltalkhub.com/#!/~PavelKrivanek/Periscope) which is his take on LightTable and does some of these things already. > - highlight selectors > - implements some rules to help code improvement, for example if you select some part of the code and it's repeated you can do an: extract method, or extract to variable transformation. > - improve the navigation between static code > - review the refactoring API and evaluate a change for admitting AST nodes and avoid the use of strings... > > Please let me know your thoughts about it and if you have more ideas, they are always welcome. > > > >

April 8, 2013

Re: [Pharo-project] [ANN] Pharo VM packages and PPA for Ubuntu

by Norbert Hartl

Am 08.04.2013 um 13:05 schrieb Damien Cassou <damien.cassou(a)gmail.com>: > On Mon, Apr 8, 2013 at 11:35 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> sudo apt-get download pharo-vm >> sudo dpkg -i --ignore-depends openssl:i386 pharo-* > > > thank you. I wrote that on the PPA web page > I don't even think that it is work-around. It would be a work-around if you don't need any ssl support. Treating it like this you should face complaints of users why Zinc SSL isn't working. I'm not sure if the automatic installation of a broken package is a benefit for anyone. Let's just fix the multiarch build. Norbert > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

April 8, 2013

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

by Martin Dias

pffff thank you. The word 'awesome' is too much, but well, I can put the snippet somewhere in the doc. I don't know if this should be the default behaviour in Fuel, since it will add the dependency to Ring. Also we can discuss about removing the "defensive" error during serialization: as you could see, technically there is no problem to serialize the obsolete class. We decided to raise an error just because as users we found that almost always when you are serializing the obsolete, it was due to some mistake, and you discover that the obsolete was in the .fuel file later when you materialize. Alternatively, we could just raise a "class not found" error during materialization. cheers, Martin ps: I'd like to see the video of Max's presentation in PharoConf! On Sun, Apr 7, 2013 at 2:47 PM, roberto.minelli(a)usi.ch < roberto.minelli(a)usi.ch> wrote: > 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.orgwrote: > > > > > > 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 8, 2013

[Pharo-project] Photos from Pharoconf and Moose day on G+

by Yuriy Tymchuk

Hi, https://plus.google.com/events/crhg5httv7iserrrqv5tulaevhc https://plus.google.com/events/cbi42b525e96tp1gj2bjr9bolns Uko

April 8, 2013

[Pharo-project] [update 3.0] #30025

by Marcus Denker

30025 ----- 7518 ShortPointArray and ShortRunArray not used https://pharo.fogbugz.com/f/cases/7518 6938 Create Collection>>#reject:thenCollect: https://pharo.fogbugz.com/f/cases/6938 10245 Run #cleanUpForRelease on every update https://pharo.fogbugz.com/f/cases/10245 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/UpdateStreamer-Core-MarcusDe… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/CollectionsTests-MarcusDenke… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Collections-Sequenceable-Mar… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Collections-Abstract-MarcusD… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/BalloonTests-MarcusDenker.3 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Balloon-MarcusDenker.93

April 8, 2013

Re: [Pharo-project] Improving the programmer experience with Pharo (ideas)

by Damien Cassou

On Mon, Apr 8, 2013 at 1:08 PM, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > Please let me know your thoughts about it and if you have more ideas, they > are always welcome. 1) when you have a selector with multiple keywords, I would like to navigate easily between the arguments. For example : self doSomething: (1) with: (2) andThen: (3) I would like to be able to easily go in one of the 3 positions (for example typing TAB could go from one to the next). Dolphin had something equivalent. 2) The pretty printer (ALT+SHIFT+u) should keep all comments where they are and be a bit smarter and more configurable 3) I want AST-based text seletion. Lukas has a screencast where he demonstrates the use of CTRL+SHIFT+Up and CTRL+SHIFT+Down to select larger and larger (respectively smaller and smaller) AST nodes in the source code. Something like https://www.youtube.com/watch?v=fTMX1f8Lu5w and http://youtu.be/_RvHz3vJ3kA?t=52s -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 8, 2013

[Pharo-project] Improving the programmer experience with Pharo (ideas)

by Gisela Decuzzi

Hi, I'm just starting an internship for 3 months and we were talking about the scope for my time here. This is a summary of what we have discussed: The main objective it's to improve the AST and use it to implement as many improvements and refactors/transformations as we can to help the programmer. Some ideas: - distinguish the code scope (for example, when you have lot of blocks all together when you pass over with the mouse that it get special something to understand where you are) - make suggestions depending on what you have selected. Example if it's a variable rename it, or find accesses (...) - highlight selectors - implements some rules to help code improvement, for example if you select some part of the code and it's repeated you can do an: extract method, or extract to variable transformation. - improve the navigation between static code - review the refactoring API and evaluate a change for admitting AST nodes and avoid the use of strings... Please let me know your thoughts about it and if you have more ideas, they are always welcome.

April 8, 2013

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

by Ciprian Teodorov

Its strange because with the checkout of libgit2 that I did yesterday I did not have this messages. I was having some - type not found. You should not take the compilation results as reference, since the makefile will have all compile options set correctly, and probably it will use GCC for compilation. You should try to see what are the options that need to be passed to clang, when compiling the header. Looking at the makefile can be a good starting point. I'll try to have a look at this, to identify the correct options. On Apr 7, 2013 10:57 PM, "Max Leske" <maxleske(a)gmail.com> wrote: > BTW: I see two errors from parsing: missing stddef.h and some problem with > one header file. stddef.h is present on the system and since I built > libgit2 myself I know there were no errors during the build. I attached the > Transcript output. > > > > On 07.04.2013, at 22:32, Max Leske <maxleske(a)gmail.com> wrote: > > I'm not sure but this might be a VM problem. I found a segmentation fault > (funny enough the VM didn't quit). I attached the crash report (cc'ing > Esteban, maybe he knows what this is about). > > Max > > <crash.dmp> > > > > On 07.04.2013, at 21:31, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> > wrote: > > > > > On Sun, Apr 7, 2013 at 9:17 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> The replacement video is up now (vimeo.com/maxleske/talkffibindings) >> >> >> On 07.04.2013, at 20:48, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> >> wrote: >> >> >> >> >> On Sun, Apr 7, 2013 at 8:08 PM, Ciprian Teodorov < >> ciprian.teodorov(a)gmail.com> wrote: >> >>> >>> >>> >>> On Sun, Apr 7, 2013 at 7:53 PM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>>> >>>> On 07.04.2013, at 18:28, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> >>>> wrote: >>>> >>>> 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 accidentally loaded your new version and ran it on libgit2. I haven't >>>> done any analysis yet but I had to force quit the image since the >>>> extraction was taking forever. With 1.3 it took only a few seconds (1 to 2 >>>> minutes tops for everything including compilation). I'm doing another run >>>> now to see what happens. >>>> >>>> That's strange, on my side (macos 10.6.8, latest pharo2.0+vm) I get 7 >>> seconds with 1.3 and between 7-9 seconds with 1.4 (but that should be ok, >>> printing in transcript is expected to take some time). >>> >>> you're still on linux I guess? i'll try to check that >>> >> >> on linux I get between 3 and 7 seconds for both 1.3 and 1.4... Yeah and >> these results do not include the compilation of the generated smalltalk... >> but that shouldn't have changed muchâ¦ >> >> >> ubuntu 32 bit vm. Latest Pharo20. Generation works pretty much as >> expected, but I've been letting the compilation (after hitting "accept" in >> the changes browser) running for about 45 minutes and it's still not >> finished. Looks like some kind of infinite loop but I can't interrupt. >> >> I checked vmstat to see if memory / swapping might be an issue but >> there's more than enough memory available. I'll keep checking. >> >> > That's strange because that step relies exclusively on the pharo change > set installation. > In my linux test i don't see any problems... > >> >>>> 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 ;) >>>> >>>> >>>> Uploadingâ¦ ;) >>>> >>>> >>>>> 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 >>>> >>>> >>>> >>> >>> >>> -- >>> 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 >> >> >> > > > -- > 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 8, 2013

Re: [Pharo-project] [ANN] Pharo VM packages and PPA for Ubuntu

by Damien Cassou

On Mon, Apr 8, 2013 at 11:35 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > sudo apt-get download pharo-vm > sudo dpkg -i --ignore-depends openssl:i386 pharo-* thank you. I wrote that on the PPA web page -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 8, 2013

Re: [Pharo-project] Global Apology

by S Krish

This is an intellectual difference of opinion and the emotions involved only show how much Pharo is involving people, deep inside, in its run up to an enterprise worthy platform. On Mon, Apr 8, 2013 at 3:25 PM, kilon <thekilon(a)yahoo.co.uk> wrote: > Who know maybe you and Igor turn out to be best friends. I had a physical > fight with my best friend and we have been unseparable ever since for 19 > years now and till this day he has the art of annoying me deeply :D But > there is more to people that meets the eye, a lot more. > > Afterall we are humans not robots , flawed yet perfect :D > > > > -- > View this message in context: > http://forum.world.st/Global-Apology-tp4680000p4680210.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

April 8, 2013