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

Re: [Pharo-project] Test of patch needed for Linux users

by Igor Stasenko

+1 we should think how we could have some object in system which represents a platform which currently image runs on, with nice API and such. <btw> if you know NativeBoost also have some platform-dependent code and also has class hierarchy to represent each platform).. but of course most of API there is highly NB-specific.. still there could be found some common parts/logic which can be unified with that system-wide object which represents current platform. </btw> On 11 April 2013 20:21, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Yes and it should because this is not a good idea to have two hierarchies > doing the same. > > > On Thu, Apr 11, 2013 at 3:10 PM, stephane ducasse <stephane.ducasse(a)free.fr> > wrote: >> >> we have a factory that create an object of each platform at startup. >> look t OSPlatform. > > > it looks like FileSystem don't use that > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing > enthusiasm." > Winston Churchill > > -- Best regards, Igor Stasenko.

April 11, 2013

Re: [Pharo-project] [Moose-dev] roassal + athens

by Igor Stasenko

(i am not subscribed to moose list , so my reply is on pharo list only). On 11 April 2013 21:49, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > 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. > Yes, but only with release of Pharo 2.0 we got VMs fully ready for use by Athens. (yes VMs was available more than half of the year before, but you had to use special VMs and know where to take it and other boring details... and before you had to install cairo by yourself).. But with 2.0 we got an integrated solution where VM and Image both ready for Athens. On all platformz. >> 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. > AFAIK, Roassal provides own abstraction layer(s) and can use Athens as one of backends.. I don't see compelling reasons why one cannot solve the modularity problems by checking what is available on system before going and blowing up with errors. >> 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. That's not needed anymoar. VMs are Athens-ready since release of Pharo 2.0. > 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. > Settings>>appearance>>enable freetype (btw, why we do not enabling it by default??? i think it is time to reconsider what is good defaults for new Pharo release) >> - 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 >> -- Best regards, Igor Stasenko.

April 11, 2013

Re: [Pharo-project] [Moose-dev] roassal + athens

by stephane ducasse

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

April 11, 2013

[Pharo-project] [GSoC] Call for students

by Janko MivÅ¡ek

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

April 11, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by Igor Stasenko

On 11 April 2013 10:44, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: > > > > 2013/4/11 Igor Stasenko <siguctua(a)gmail.com> >> >> On 11 April 2013 08:55, Tristan Bourgois <tristan.bourgois(a)gmail.com> >> wrote: >> > >> > >> > >> > 2013/4/10 Igor Stasenko <siguctua(a)gmail.com> >> >> >> >> >> >> >> >> On 10 April 2013 09:14, Tristan Bourgois <tristan.bourgois(a)gmail.com> >> >> wrote: >> >>> >> >>> >> >>> >> >>> >> >>> 2013/4/9 Igor Stasenko <siguctua(a)gmail.com> >> >>>> >> >>>> Yes, this is a known bug actually, which i demonstrated to audience >> >>>> during >> >>>> tutorial presentation.. >> >>>> i/cairo miss the correct font matrix setup.. and i need to see what's >> >>>> there. >> >>>> Cairo caching the glyphs in a strange way (so if you never drawn >> >>>> anything with given font before and your first drawing will use some >> >>>> rotation >> >>>> then everything will be rendered correctly, but if you already drawn >> >>>> anything >> >>>> it will render them like you shown).. >> >>>> I'm going to fix that issue when i come back from Lviv. >> >>>> >> >>> >> >>> Super :) >> >>> >> >>> Did you also see the cairo_text_path() method? It's very interesting >> >>> if >> >>> you want to stroke the letter! >> >> >> >> >> >> Yes but this is more for fancy artistic text. For rendering large >> >> amounts >> >> of text (like big lists/source code) you don't want to do that, >> >> because it will be too slow. >> >> >> > >> > Thanks for the advice I will share it to my team because they want >> > performance and use text_path instead of show_text. >> > >> >> yes, the freetype library (and i guess you using it) is highly >> optimized for font rendering. >> sure thing, cairo path rendering is fast as well, but it is not as >> specialized for just font rendering as freetype, >> therefore, i have no doubts that it will be slower. >> >> > > > I only use Athens to rendering the graphics framework :) And I try to not > use directly some AthensCairo object to benefit of futur new backend of > Athens :) and sincerely you really make a good job of the Athens interface! > It's very easy to use it! In one case I use AthensCairo object. I have to > use AthensCairoMatrix instead of AthensAffineTransform to represent the > transformation of a shape because I have to make an inversion of the matrix > to make a global position to the local position of the shape. > Ah, you mean this: AthensAffineTransform>>inverted "answer an inverse transformation of receiver" self notYetImplemented yes, someone has to implement it ;) But actually you can just use #inverseTransform: aPoint i.e. if: pt := m transform: somePoint. then somePoint closeTo: (m inverseTransform: pt) ==> true. (close to instead of #= because of float rounding errors) -- Best regards, Igor Stasenko.

April 11, 2013

Re: [Pharo-project] Test of patch needed for Linux users

by stephane ducasse

Yes and it should because this is not a good idea to have two hierarchies doing the same. > > On Thu, Apr 11, 2013 at 3:10 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > we have a factory that create an object of each platform at startup. > look t OSPlatform. > > it looks like FileSystem don't use that > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing enthusiasm." > Winston Churchill

April 11, 2013

[Pharo-project] [update 3.0] #30036

by StÃ©phane Ducasse

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…

April 11, 2013

Re: [Pharo-project] [Pharo-users] [ANN] Pharo VM packages and PPA for Ubuntu (v2)

by Sven Van Caekenberghe

On 11 Apr 2013, at 16:34, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > Norbert Hartl and I are proud to announce that: > > - the pharo-vm package can now be installed on 64bits systems > - the pharo-vm package can now be installed on older Ubuntu releases Great and important work, thanks ! > Todo list: > -- > > - clean the package to avoid many warnings > - automate the process of building these packages > - create a server-only version which do not depend on graphical libraries (like X11 and libGL) Yes, a pharo-nox version is really important (for me at least). > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing enthusiasm." > Winston Churchill -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

April 11, 2013

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

by Sean P. DeNigris

Damien Cassou wrote > - the pharo-vm package can now be installed on 64bits systems > - the pharo-vm package can now be installed on older Ubuntu releases Hooray! Great work :) Will this package continue to track the latest or stable vm version, or is at locked at the current version? ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Pharo-VM-packages-and-PPA-for-Ubuntu-v2-tp4680867… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 11, 2013

[Pharo-project] [update 3.0] #30035

by StÃ©phane Ducasse

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…

April 11, 2013