- Pharo-dev - lists.pharo.org

Re: [Pharo-project] About the collaborative pier

by Tudor Girba

Hi Stef, No, I cannot :). There really is nothing magic, just one single rule: whenever you want to add something, you will always add a child to the current page. So, if you want to add a page/or whatever, just go to the place you want to add it under and invoke add. That is it. What part of it is unclear? Now, when it comes to section/subsection, you should not care about that. Adding a child to a chapter creates a section. Adding a child to a section creates a subsection. And so on. Cheers, Doru On 17 Apr 2010, at 18:26, stephane ducasse wrote: > Hi doru > > > Can you change the setup of the pier to have a clear distinction > between chapter and section? >> because it is really counter intuitive >> we never know if we are editing a new table of contents, chapter or >> section. >> Just now I edited again an entry in the table of contents and added >> a subsection when I wanted a section. > Thanks. I would like to avoid losing time all the time. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Live like you mean it."

April 17, 2010

[Pharo-project] About the collaborative pier

by stephane ducasse

Hi doru Can you change the setup of the pier to have a clear distinction between chapter and section? > because it is really counter intuitive > we never know if we are editing a new table of contents, chapter or section. > Just now I edited again an entry in the table of contents and added a subsection when I wanted a section. Thanks. I would like to avoid losing time all the time. Stef

April 17, 2010

Re: [Pharo-project] Really Important message (tm)

by StÃ©phane Ducasse

>> > Looking at the + and - lines in the diff, it seems like the test has two added assertions. > First, make sure those assertions actually make sense, in that they test something you would expect. > Then, try adding them to the image, and see if tests still pass. > If they do, submit a slice with the added tests. > If they do not, see if modifying the code to what is pasted in the issue make them pass. > If it does, submit a slice with tests + modified method. > If not, figure out a way to make the tests pass on Pharo, then submit :) > have a look at squeak to see if the tests pass there and not in pharo or inverse. The idea is to see if they make sense in pharo context and help us to make the system better. Often I read also the other tests and often I improve things (even like putting a good category instead of as yet unclassified) Now in the present case this is not clear that =============== Diff against Kernel-jcg.439 =============== Item was changed: ----- Method: Duration class>>milliSeconds: (in category 'squeak protocol') ----- + milliSeconds: milliCount - milliSeconds: milliCount "Since seconds is 0 we can call the instance directly." + ^ self + seconds: milliCount // 1000 + nanoSeconds: (milliCount \\ 1000)*NanosInMillisecond! - - ^ self basicNew seconds: 0 nanoSeconds: milliCount * NanosInMillisecond! is really better and may be the suggestion of nicolas should be taken into account. Thanks German. You see a lot of little details :) stef

April 17, 2010

Re: [Pharo-project] Really Important message (tm)

by Henrik Sperre Johansen

On 17.04.2010 17:34, GermÃ¡n Arduino wrote: > Ok, I'm back asking :) > > I started having an updated 1.1 version (PharoCore1.1ALPHA Latest > update: #11317). > > Then, checked the issues on google page and selected one qualified as Easy :) > http://code.google.com/p/pharo/issues/detail?id=2297&sort=-id&colspec=ID%20… > > I saw the things posted and the comments of NicolÃ¡s Cellier, but I > can't understand what is supposed to do with this. > > I run the DurationTest on the image and the 41 tests runs ok. > > Then, what is needed to do? I saw also that the method > #testAsMilliSeconds in the image is different that the method posted > by Stef on the issue page. > > Well, sorry with the questions, but I need to understand to have the > possibility of help. > > Cheers. > GermÃ¡n. Looking at the + and - lines in the diff, it seems like the test has two added assertions. First, make sure those assertions actually make sense, in that they test something you would expect. Then, try adding them to the image, and see if tests still pass. If they do, submit a slice with the added tests. If they do not, see if modifying the code to what is pasted in the issue make them pass. If it does, submit a slice with tests + modified method. If not, figure out a way to make the tests pass on Pharo, then submit :) Cheers, Henry

April 17, 2010

Re: [Pharo-project] Really Important message (tm)

by GermÃ¡n Arduino

Ok, I'm back asking :) I started having an updated 1.1 version (PharoCore1.1ALPHA Latest update: #11317). Then, checked the issues on google page and selected one qualified as Easy :) http://code.google.com/p/pharo/issues/detail?id=2297&sort=-id&colspec=ID%20… I saw the things posted and the comments of NicolÃ¡s Cellier, but I can't understand what is supposed to do with this. I run the DurationTest on the image and the 41 tests runs ok. Then, what is needed to do? I saw also that the method #testAsMilliSeconds in the image is different that the method posted by Stef on the issue page. Well, sorry with the questions, but I need to understand to have the possibility of help. Cheers. GermÃ¡n. 2010/4/16 GermÃ¡n Arduino <garduino(a)gmail.com>: > Thanks by the explanations. I'm already checking the issues and the 1.1 version. > > Will be back with more questions, be sure! > > > 2010/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> On Apr 16, 2010, at 12:02 AM, GermÃ¡n Arduino wrote: >> >>> The letter is on the way. >>> >>> A first question, to help with unstable I should use it as it comes >>> (with no added packages) or I can install somethings to make the >>> environment more comfortable (as shout for example) ? >> >> the way you want but if you load packages you should pay attention that you changes do not impact them by accident. >> Ideally we would like to have metacello to manage core and the process would be >> >> Â Â Â Â - take latest core >> Â Â Â Â - update >> Â Â Â Â Â Â Â Â -> get Pharo with maintained Pharo package: sound >> Â Â Â Â ------------------------------------------------------- this phase should be done for us on a server with a hudson cron like job >> >> Â Â Â Â - you change >> Â Â Â Â - you publish changes >> Â Â Â Â -------------------------------------------------------- >> Â Â Â Â we take the current unstable core + packages >> Â Â Â Â - integrate your changes >> Â Â Â Â -> produce new version of packages + new metacello configuration >> >> Now since loading code is too slow we have to pay attention and avoid to frantically remove packages from the image >> because they can desync too easily when we do system wide changes. >> >> So for simple things just take the latest unstable and publish changes >> >> >> >> >>> GermÃ¡n. >>> >>> 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> Thanks! >>>> As I said, 30 min are enough >>>> Stef >>>> >>>> On Apr 15, 2010, at 9:25 PM, GermÃ¡n Arduino wrote: >>>> >>>>> ok, my signed agreement is leaving today for France. >>>>> >>>>> I will try to start understanding how is the contribution process in >>>>> Pharo and playing a bit with unstable. >>>>> >>>>> Unfortunately I've very little free time, but still, will try to help. >>>>> >>>>> Cheers. >>>>> >>>>> >>>>> 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>> Hi guys >>>>>> >>>>>> Let me reiterate it: >>>>>> >>>>>> Â Â Â Â - We need you! >>>>>> Â Â Â Â - 75 % of the issues on the bug tracker are simple. >>>>>> Â Â Â Â - BTW how did we learn stuff, by reading code and learning. I'm not smart I'm just a tedious learner >>>>>> Â Â Â Â I can any opportunity to learn something new. >>>>>> Â Â Â Â - if you spend 30 min a week, YOU CAN get an IMPACT! >>>>>> Â Â Â Â - if pharo is important for you then 30 min in a good investment >>>>>> Â Â Â Â - every single LITTLE bugs fixed and improvement is IMPORTANT >>>>>> Â Â Â Â - we do not want the final latest coolest superhyper cool and hyper clever fixes! >>>>>> Â Â Â Â - we accept little improvement >>>>>> Â Â Â Â - in UNSTABLE we have the right to push not 100% finish code >>>>>> >>>>>> Now think what YOU can do for pharo. Because Yes YOU can >>>>>> Â Â Â Â - screencast >>>>>> Â Â Â Â - checking tests (yesterday I moved CompiledMethodAsStringTest>>testPrint to CompiledMethodTest>>testPrint) Yeah hyper difficult >>>>>> Â Â Â Â - Class comments: look at the URI class comment >>>>>> Â Â Â Â - blogging >>>>>> Â Â Â Â - tweeting >>>>>> >>>>>> >>>>>> We should slowly change our process so that Pharo continue to evolve even if we disappear on the moon. >>>>>> >>>>>> Now I asked marcus to focus on the newcompiler and stop fixing little bugs because we want to make progress on other fronts. >>>>>> >>>>>> We want newcompiler - Â we want the newcompiler - Â we want the newcompiler and fixing it and fixing its interface. >>>>>> We want Helvetia hooks -We want Helvetia hooks. >>>>>> We want a new package object (but I do not find time to code argh). >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> ================================================= >>>>> GermÃ¡n S. Arduino Â <gsa @ arsol.net> Â Twitter: garduino >>>>> Arduino Software & Web Hosting Â http://www.arduinosoftware.com >>>>> PasswordsPro Â http://www.passwordspro.com >>>>> ================================================= >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

April 17, 2010

Re: [Pharo-project] we need help for rome

by David T. Lewis

On Sat, Apr 17, 2010 at 11:30:41AM +0200, Michael Rueger wrote: > On 4/17/2010 11:06 AM, St?phane Ducasse wrote: > >Thanks john oops I learned something. Now the problem is that I did > >not touch them. I just loaded code. So I wonder where they got lost > >or changed. > > I suspect those got removed when integrating or because of Freetype > support in Pharo? > > Although I don't think these inst vars are actually essential for the > plugin to function. > So maybe the plugin should be changed to cover just the necessary inst vars? If you change the plugin, you will end up with with an image that fails when someone runs it on the wrong version of the VM. Dave

April 17, 2010

[Pharo-project] Text at an angle

by Schwab,Wilhelm K

Hello all, I am trying to reproduce something that I did in Dolphin. It is a grid of colored squares (got that part) with horizontal and vertial text labels on the rows and columns, respectively. How to create the vertical text is not clear to me. One approach would be to draw the text horizontally and then rotate the resulting form. Is there a better way? Bill

April 17, 2010

[Pharo-project] Fwd: [Vm-dev] CMake for Windows?

by StÃ©phane Ducasse

Excellent! > >> From: Geoffroy Couprie <geo.couprie(a)gmail.com> >> Date: April 17, 2010 1:23:00 AM GMT+02:00 >> To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> >> Subject: Re: [Vm-dev] CMake for Windows? >> Reply-To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> >> >> >> Hello, >> >> You'll find my work on the CMake files at >> http://eleves.ec-lille.fr/~couprieg/divers/patches.zip >> >> I put a CMakeLists.txt file just under the platforms/ directory, along >> with the cmake/ directory. These files are based on the unix ones. I >> modified them to change the source directory depending on the >> platform. I also modified the configure file accordingly, but i >> commented the code using subversion for my convenience during >> development (feel free to change it back). >> >> These CMake files are not perfect, it's just the beginning. First, I >> want to make sure that the unix port still builds with my file, and >> then, I'll go on with the config.cmake and build.cmake files for the >> plugins, and I'll clean CMakeLists.txt a bit. >> >> Feel free to comment, but note that I'm beginning with CMake, and that >> I don't write bash code very often. And please, try it with the unix >> port. I don't want to break everything :) >> >> Anyway, it works for me here (I can build a VM on Windows with the >> File, Security, LargeIntegers and MiscPrimitive plugins using >> MSYS+MinGW). >> >> Best regards, >> >> Geoffroy > > > >

April 17, 2010

Re: [Pharo-project] we need help for rome

by StÃ©phane Ducasse

Yes any solution that would make it easier to support changes at the image level would be great. Stef On Apr 17, 2010, at 11:30 AM, Michael Rueger wrote: > On 4/17/2010 11:06 AM, StÃ©phane Ducasse wrote: >> Thanks john oops I learned something. Now the problem is that I did >> not touch them. I just loaded code. So I wonder where they got lost >> or changed. > > I suspect those got removed when integrating or because of Freetype support in Pharo? > > Although I don't think these inst vars are actually essential for the plugin to function. > So maybe the plugin should be changed to cover just the necessary inst vars? > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 17, 2010

Re: [Pharo-project] we need help for rome

by Michael Rueger

On 4/17/2010 11:06 AM, StÃ©phane Ducasse wrote: > Thanks john oops I learned something. Now the problem is that I did > not touch them. I just loaded code. So I wonder where they got lost > or changed. I suspect those got removed when integrating or because of Freetype support in Pharo? Although I don't think these inst vars are actually essential for the plugin to function. So maybe the plugin should be changed to cover just the necessary inst vars? Michael

April 17, 2010