- Pharo-dev - lists.pharo.org

[Pharo-project] [update 3.0] #30037
by Marcus Denker April 12, 2013

April 12, 2013

1 0

[Pharo-project] how to publish screen capture of a nice hands-on ?
by StÃ©phane Ducasse April 12, 2013

April 12, 2013

Hi guys yesterday I coded a small DSL with the students here and I would like to publish it somewhere. Any idea how to proceed? Stef

3 2

[Pharo-project] draft of a videos :)
by StÃ©phane Ducasse April 12, 2013

April 12, 2013

Hi guys I recorded a teaching session yesterday of how to code (2 D20 + 3 D10) roll http://stephane.ducasse.free.fr/Videos/2013-04-10-DiceDraft.mov I will redo it completely but here is a draft version. Stef

1 0

[Pharo-project] [GSoC] Call for students
by Janko MivÅ¡ek April 12, 2013

April 12, 2013

Dear Students, Now it is your turn! You will have to register in our website first [1], put there some information, show interest for the projects and contact the project mentors. After the registration step you will get all the mentors information in order to contact them. By pressing the button on the project, you will show your interest. This is not something formal yet. Of course you can propose your own project too. In this case write a proposal in a format other projects have and send it to admins (see the email on the bottom). Our mentors will vote for the most interesting projects and in the middle of the voting Google will tell us, how many projects will actually be funded. Voting will happen in May, with final results expected at the end of May. At that time you will finally know if you are accepted or not. Of course, there can be many students interested per project. This means that interest for this project is high, but on the other side a chance that you will be chosen is lower. It is up to you to convince a mentor that you are the best! Note also that the Ideas page is deprecated. On ideas page just the project ideas were collected. Now, we are preparing the real projects. So, please from now on always refer to this link for the projects: http://gsoc2013.esug.org/projects So, your initial steps are: 1. Register on our special Smalltalk GSoC website (with your Google account!): http://gsoc2013.esug.org/admin?view=loginGoogle 2. Edit your profile to get some more contact information for mentors to let you know, 3. Fulfill your brief Biography page (see Biography tab on profile), 4. Go to Projects page, choose up to three projects and click there 'I'm interested' button, 5. Contact and discuss with project mentors about your interest. Subscribe also to a special mailing list [2] where we will help you with further steps. Deadline: as soon as possible, because the deadline to register on official GSoC website [3] is 3.May, which is, well, soon! But about that later... Finally, we will really appreciate if you can help us to distribute this call for students. One of our goals is to increase the Smalltalk community. Those who have access to universities can distribute this among the students. Distribute also our poster [4] in many languages, English one attached. [1] http://gsoc2013.esug.org [2] Students mailing list: http://groups.google.com/group/smalltalk-gsoc-students [3] Official GSoC website http://www.google-melange.com [4] Poster in PDF and image format, in many languages http://gsoc2013.esug.org/poster Good luck! Janko & Serge --- GSoC Admin Team smalltalk.gsoc(a)gmail.com http://gsoc2013.esug.org -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

2 1

[Pharo-project] Test of patch needed for Linux users
by Damien Cassou April 11, 2013

April 11, 2013

Linux users, please try the slice and comment at https://pharo.fogbugz.com/default.asp?5819#73545 This patch will give you a way to get the user directories for standard places ('preferences' should point to '~/.config', 'documents' should point to '~/Documents', 'desktop should point to '~/Desktop') Thank you -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

4 10

Re: [Pharo-project] [Moose-dev] roassal + athens
by stephane ducasse April 11, 2013

April 11, 2013

Hi guys I crosspost because I hate when I get complains without having mails sent to the right forum. On Apr 11, 2013, at 3:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> If I understand correctly, if we would get ConfigurationOfRoassal to load Athens only in Pharo 2.0, you would be satisfied, right? > > No, because if I download the Pharo from http://www.pharo-project.org/home (by clicking on the download button), install Roassal, then errors will show up, and this is what I want to avoid above everything else. Sure do not report it to the mailing-listâ¦â¦. frankly I do not understand. How can we address problems if people do not report them? > I am a fierce advertiser of Athens. Thanks to Igor tutorial, my developing environment is Athens-based. you know everything was in the examples since months. > I would like to see Athens widely used, yes. > > However, if I go a step further, such as making Roassal depends on Athens, sorry but I do not get how you can get roassal working with athens without having it depend on it because it would solve a lot of our modularity problem. > then we will have to deal with: > - students who simply clicked on the download webpage and see bugs appearing because the lib are not installed we cannot do magic. May be then you should prepare a virtual image OS with the lib installed. We cannot install lib on all the platform of earth. Sorry but if there is not cairo installed what can we do? May be the install of Damien will handle such case. But if you use an OS for your lecture or students you should also have a look at it. Or do not use Pharo 2.0 but then you will use software that is one year old with around 1000 fixes not available. > - telling where to download and how to install Igor's VM the DEFAULT Pharo VM works with cairo. so I do not get what you mean. > - telling the world how to install the free type fonts else Roassal will lamentably crash On which platform? I do not get what you are saying. On mac I press the settings and it works. Alain is developing on linux so it should work too. > - have to test myself cairo on Ubuntu May be damien will address your problem. but again why do not create a virtualize image containing a well install OS? > - fiddling ConfigurationOfRoassal to make it sure it works with 1.4 and trying to not get nervous because I will surely won't be able to save Roassal using Versionner anymore. For versionner again, even in 1.4 I cannot use it because most of the time I need handling of projects. > - Answering complains that loading Roassal takes too much time This will be fixed but not now. Really? Not the moose people. The moose people complain about the speed of roassal not its loading. > Alexandre > >> >> This should be pretty fast, too. >> >> Cheers, >> Doru >> >> >> >> On Thu, Apr 11, 2013 at 2:50 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> I do not understand the problem. >>> Athens loads perfectly and all the VM are working. >>> >>> Now if you prefer to wait for about a year, it simply means that you do not need vector graphics. >> >> Roassal needs to be loadable in a 1.4 image. >> >> Alexandre >> >>> >>> On Apr 10, 2013, at 10:48 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>>> Hi, >>>> >>>> I do not quite understand your worries. >>>> >>>> Athens-Cairo has two parts: >>>> - the VM side: the plugin is already nicely bundled with the Pharo VM on all operating systems. >>>> - the image side: the Athens canvas and Cairo binding are essentially working, but were not yet added to Pharo 2.0 because it was not tested enough at the time of the release. >>>> >>>> To me, the largest problem is on the VM-side, and that was nicely solved. The image-side is solid already and will get into Pharo 3.0. But, in the meantime, I do not want to wait for another year until we can start to benefit from the nice capabilities of Athens. >>>> >>>> Can you be more explicit as to why we should not make this default in Pharo Morphic? >>>> >>>> Btw, it is not enough to just load Athens. Here is what I reverse engineered: >>>> Gofer new >>>> squeaksource: 'Athens'; >>>> package: 'ConfigurationOfAthens'; >>>> load. >>>> (Smalltalk at: #ConfigurationOfAthens) loadVersion: '2.0'. >>>> Gofer new >>>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal'; >>>> package: 'RoassalAthens'; >>>> load. >>>> ROPlatform setCurrent: 'athens'. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On Apr 10, 2013, at 9:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> >>>>>> I would like to start adopting Athens behind Roassal. I believe there already is a binding. The question is what keeps us from adding Athens as a dependency to RoassalMorphic? >>>>> >>>>> Well... The way I see this is slightly different. Athens should be part of the runtime (i.e., included in Pharo) and not use as a library. I am not sure what we will gain to consider Athens as a separate Library. >>>>> >>>>> The Roassal<-->Athens bindings works well I think. We haven't spotted any problem. Just load Athens before loading Moose while Athens is not part of Pharo. >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "There are no old things, there are only old ways of looking at them." >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

2 1

[Pharo-project] [update 3.0] #30036
by StÃ©phane Ducasse April 11, 2013

April 11, 2013

30036 ----- Issue 5188 Stage 3: Announcement>> handlesAnnouncement: Cleaning after the changes. https://pharo.fogbugz.com/default.asp?5188 Move ui code of SmallDictionary to Tools package. Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Tools-StephaneDucasse.1073 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Collections-Unordered-Stepha… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Announcements-Core-StephaneD… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Announcements-Tests-Core-Ste… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Collections-Strings-Stephane…

1 0

April 11, 2013

30035 ----- Issue 5602: LinkedList at: index putLink: aLink https://pharo.fogbugz.com/default.asp?5602 Issue 5188-Stage 2: Announcement>> handlesAnnouncement: Now we use the new protocol that was introduced in previous stage. https://pharo.fogbugz.com/default.asp?5188 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/CollectionsTests-StephaneDuc… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Announcements-Core-StephaneD… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Collections-Sequenceable-Ste…

1 0

April 11, 2013

30034 ----- 10177 Deprecate accept* in visitor https://pharo.fogbugz.com/f/cases/1017 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/FileSystem-Core-StephaneDuca… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Announcements-Core-StephaneD… Stef and Igor (from Lviv)

1 0

[Pharo-project] [update 3.0] #30033
by Marcus Denker April 11, 2013

April 11, 2013

30033 ----- 10177 Deprecate accept* in visitor https://pharo.fogbugz.com/f/cases/10177 Deprecate the wrong protocol for AST visitors. Visitors do not accept they visit. - Clean also the messages send but not implemented - rationalize the API now methods are named * Node The code to automatically rewrite all visitors is this (we tested with Opal): m := (RBProgramNodeVisitor allSubclasses gather: #methods) select: [ :e | e selector beginsWith: 'accept' ]. m do: [ :e | e methodClass compile: (e sourceCode copyReplaceAll: 'accept' with: 'visit'). e methodClass removeSelector: e selector ]. (self systemNavigation allSendersOf: #acceptInlinedBlockNode:) do: [ :e | e methodClass compile: (e sourceCode copyReplaceAll: 'acceptInlinedBlockNode:' with: 'visitInlinedBlockNode:')

2 1