- Pharo-dev - lists.pharo.org

Re: [Pharo-project] CollabActive book :)

by Tudor Girba

Hi Simon, On 7 Apr 2010, at 10:36, Simon Denier wrote: > > On 7 avr. 2010, at 09:17, Lukas Renggli wrote: > >>> I see what you mean, but I don't like the way it is displayed, >>> because it makes navigating from section to section cumbersome and >>> just skimming a chapter to get an overview is difficult. >> >> While writing/editing the Seaside book we figured out the following >> simple guidelines that worked out quite well: >> >> http://book.seaside.st/system/howto > > > Thanks! That's helpful. > > Adding +value:book.contents+ to create a mini-toc for the chapter > works ok, although perhaps this should go in the column. Please do not use that there. It will make everything complex afterwards. You can always use the key navigations to switch between pages: - "j" or left arrow: previous book part - "k" or right arrow: next book part - "i": table of contents - "p": parent book part > Doru, another missing thing in the current config is the == syntax > for Smalltalk highlighting > See http://book.pharo-project.org/book/announcements/client Ahh, my bad again. I will look into it. Cheers, Doru > > -- > Simon > > > > > _______________________________________________ > 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 "Sometimes the best solution is not the best solution."

April 7, 2010

Re: [Pharo-project] CollabActive book :)

by Simon Denier

On 7 avr. 2010, at 09:17, Lukas Renggli wrote: >> I see what you mean, but I don't like the way it is displayed, because it makes navigating from section to section cumbersome and just skimming a chapter to get an overview is difficult. > > While writing/editing the Seaside book we figured out the following > simple guidelines that worked out quite well: > > http://book.seaside.st/system/howto Thanks! That's helpful. Adding +value:book.contents+ to create a mini-toc for the chapter works ok, although perhaps this should go in the column. Doru, another missing thing in the current config is the == syntax for Smalltalk highlighting See http://book.pharo-project.org/book/announcements/client -- Simon

April 7, 2010

Re: [Pharo-project] Handle Close Event in Image - necessary for 1.0?

by Henrik Johansen

On Apr 6, 2010, at 10:48 19PM, StÃ©phane Ducasse wrote: > Torsten I appreciate your effort but we can only do what can be done in the time > we can allocate to do a task if you see what I mean. > I cannot test on windows because we do not have a windows machine. We are doing an incredible > amount of work but we cannot do more than it is reasonable to do. > > Then in freeze time this is freeze time. we will try to get shorter iteration cycles and this is not > by delaying 1.0 that we are making progress on that front. > > And this is not by saying that pharo "will be less quality than" ... more or less that it helps. > > So 1.0 will be like it can. And if people bash us this is ok too. > You remember a while ago one guy asked who is ready to pay 10 Euros per month to have a > better pharo and we got 6 persons.... > >> However I still believe that fixing this in 1.0 would not only >> be a plus - it will also prevent questions regarding this >> new problem since people WILL use newer VM's after the >> first 1.0 release of Pharo and then instantly step into the problem! >> >> >> And it is not a Windows specific problem as Stef thinks it is. >> >> Bert requested John today (see [1]) to change the default for Mac too ... > > TODAY. Imagine I was painting my house.... and this evening this would have to be fixed? > When is the last time that a bug that annoys you on windows got fixed in one day? > because for me on mac so far it took months. > >> so if you upgrade your Mac VM for whatever reason (maybe to do >> 1.1 work or since you need a newer VM for a commercial project) >> then you will step into this with the 1.0 image. > > Yes and since you are a good pharoers you will know and you will understand > and help us and help yourself. I've put some slices based on the .cs in the inbox, one for 1.0 and one for 1.1. (quitSession was moved to WorldState in 1.1, and some other minor diffs) I've also tested and can confirm they work with the newest Windows VM, not sure about the behavior on Linux, which apparently was updated as well. Cheers, Henry

April 7, 2010

Re: [Pharo-project] CollabActive book :)

by Tudor Girba

Hi, The toolbar is now available. Cheers, Doru On 7 Apr 2010, at 01:14, Simon Denier wrote: > > Also what is missing is the handy toolbar which provides buttons to > decorate the text with Pier syntax. Useful when you are not a pro of > the syntax. But I don't know how to install this widget. > -- www.tudorgirba.com "Value is always contextual."

April 7, 2010

Re: [Pharo-project] Linux Pharo VM on Pharo website

by laurent laffont

On Wed, Apr 7, 2010 at 10:05 AM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > laurent laffont a Ã©crit : > > > The tinyBenchmarks are not as good as Exupery one, but this vary a lot >> depending on the CPU. >> > > Any reason not to propose Exupery? > The idea is to propose the squeak vm 2151 I provide (source) + Exupery VM (binary - alternate link). The major problem with Exupery VM is that nobody but Bryce (as far as I know) can build it. I'm still not able to do it:(. That means no package for Linux distributions. Another one is failing tests. Laurent Laffont > > Hilaire > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 7, 2010

Re: [Pharo-project] Linux Pharo VM on Pharo website

by Hilaire Fernandes

laurent laffont a Ã©crit : > The tinyBenchmarks are not as good as Exupery one, but this vary a lot > depending on the CPU. Any reason not to propose Exupery? Hilaire

April 7, 2010

Re: [Pharo-project] CollabActive book :)

by Lukas Renggli

> I see what you mean, but I don't like the way it is displayed, because it makes navigating from section to section cumbersome and just skimming a chapter to get an overview is difficult. While writing/editing the Seaside book we figured out the following simple guidelines that worked out quite well: http://book.seaside.st/system/howto Lukas -- Lukas Renggli www.lukas-renggli.ch

April 7, 2010

Re: [Pharo-project] Linux Pharo VM on Pharo website

by laurent laffont

On Wed, Apr 7, 2010 at 9:07 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > thanks laurent > > Do you have an account in the inria gforge? > No Laurent Laffont > > On Apr 7, 2010, at 8:34 AM, laurent laffont wrote: > > > Hi, > > > > I've prepared the following archive. It may replace the "Unix (3.11-3)" > download link. > > > > > http://lolgzs.free.fr/pharo/squeak-vm/squeak-3.11.3.2151-pharo-src.tar.gz > > > > In this archive: > > > > - patched squeak-vm rev. 2151. (The 2 patches are for FT2Plugin build and > multiple options in CFLAGS to work. Patchs in archive). > > - awk gnuification > > - README with instructions to build and regenerate this source from > VMMaker > > - All Pharo-1.0 tests green (on my machine ...) > > - it has been built/tested by several people in order to send me > tinyBenchmark results :) > > > > The tinyBenchmarks are not as good as Exupery one, but this vary a lot > depending on the CPU. > > > > Cheers, > > > > Laurent Laffont > > _______________________________________________ > > 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 7, 2010

Re: [Pharo-project] Linux Pharo VM on Pharo website

by StÃ©phane Ducasse

thanks laurent Do you have an account in the inria gforge? On Apr 7, 2010, at 8:34 AM, laurent laffont wrote: > Hi, > > I've prepared the following archive. It may replace the "Unix (3.11-3)" download link. > > http://lolgzs.free.fr/pharo/squeak-vm/squeak-3.11.3.2151-pharo-src.tar.gz > > In this archive: > > - patched squeak-vm rev. 2151. (The 2 patches are for FT2Plugin build and multiple options in CFLAGS to work. Patchs in archive). > - awk gnuification > - README with instructions to build and regenerate this source from VMMaker > - All Pharo-1.0 tests green (on my machine ...) > - it has been built/tested by several people in order to send me tinyBenchmark results :) > > The tinyBenchmarks are not as good as Exupery one, but this vary a lot depending on the CPU. > > Cheers, > > Laurent Laffont > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 7, 2010

Re: [Pharo-project] Redline Smalltalk

by StÃ©phane Ducasse

On Apr 6, 2010, at 11:01 PM, Dan Ingalls wrote: > Hi, Stef - > >> This is fun because I was rereading the miniimage contents and started to think in terms of package reorganization to support a mini image. >> I reread also Spoon a bit and I was looking at the nuturning. >> Dan it would be nice if you could merge the potatoe change into Jsqueak? > > Potato is JSqueak. I don't get it. I know :) Now having two different repositories with not synchronized code is not really good. This is was I thought that either you put a pointer to potatoe on your page or better you merge their changes. >> Dan, Mariano for his PhD did some analysis about number of object used during typical coding session and we got around 17 %. >> So mariano would like to see how we can get something like LOOM to dispose unused objects :) > > Are you aware of the work I did that enables class fault detection in Squeak? Yes :) MDFault that hijack the method category > If a class has a nil methodDictionary, it causes a fault (ie it sends recoverFromMDFault to the class). That code then restores the MD in addition to any anyalysis you want. I never cleaned it up for posterity, but it enabled lots of interesting work... The problem is that we did some experiences (not too advance with mathieu) and we got all the classes touched after a couple of seconds. > By nilling all but a few MDs, and then running some application, you could > tell exactly what classes were needed and which were not. > See the method discoverActiveClasses. > A special feature even recorded the call stack that caused each class to be > touched. ok this one I was not aware. > What I was doing was restructuring the entire system as a bunch of > image segments that could be swapped out and brought in > on demand -- a sort of user-programmable swapping memory. What mariano did so far is to - read all the image segments code /c included - find it dangerous - clean the project and etoy related code (for me the simple fact that you have all the special cases for projects reveals that there is a deeper fundamental problem. I do not have the answer but normally the "swapouter" should be generic and may be provide hooks for specific cases but not do that in the logic itself. - define some primitive to use the extra bit to collect some measure of object used. - read / understand loom + the same in Java in OOPSLA 2008 next steps - getting married - build some tools to collect thiner grained information One problem we saw with IS is that as soon as you have a reference from outside the root graph to inside your graph, this subgraph does not get saved (because not marked) and this may led to brittle system. Another problem was the size of array which may be double or triple than what you want to save mariano will be more precise than me. > This all worked at one point. Swapping of projects was a bit flakier > because of our weak discipline on pointer scope, but it > even worked in many cases. > > Where I was going with the whole "reorganizeEverything" project was that the SystemDictionary would be partitioned into many separate dictionaries in each project, and that namespaces would be the same as the project swapping unit, and the whole thing would be simple and fast. It actually worked once (;-) also. this is interesting. I'm not convinced that I would unify namespace and project (but this is the case in a module system). Now the question is how to dynamically modularize a system. Because are static organization (which are good for code management) doomed to failed when we look at them from a use point of view? > > Loom was cool, but it could never come close to the speed of imageSegments. I played around with swapping out the entire VM Support category with all classes and methods, and it would swap in the entirety in less than 200 milliseconds, and this was a decade ago. > > Sorry for the long digression, but maybe some of this thinking or even the actual mechanism can be of use to your experiments. Yes now we were thinking that imageSegments should not rely on the internal C organization of objects. > > - Dan > >> >>> James Ladd <james_ladd(a)hotmail.com> wrote... >>>>> Hi Pharo-ites, >>>>> >>>>> I'm working on a port of Pharo to the Java Virtual Machine called Redline Smalltalk. >>>>> (read more here: http://jamesladdcode.com/?p=323) >>>>> >>>>> I'm wanting to port every single class over time, but initially enough to get the >>>>> compiler working and have a minimum runtime. >>>>> >>>>> Of the 1600+/- classes which are those necessary to make a small workable compiler >>>>> and runtime environment? >>> >>> Hi, James - >>> >>> Bert Freudenberg forwarded this along to me, as I'm not on a Pharo mailing list. >>> >>> I think you know of my JSqueak project (a.k.a. Potato) -- a Squeak VM written in Java. The image that I used with it, is the same that I always use for this kind of experiment -- mini.image built in Squeak 2.2. >>> >>> The reason it is so cool is that it includes browser, editor, compiler, inspector debugger, and files -- everything you need for self-support. Plus it has the decompiler, and special temp-name hack, so you can actually browse sources with temp names before any file system works. My favorite thing about this image is that although it is only 600k, if you decompile all its sources, it comprises over 850k of Smalltalk, so it's like a compressed version of the sources with a full-function IDE thrown in for free ;-). >>> >>> As I said, the image is about 600k, of which 240k is code -- 202 classes (x2 if you count the metas) with 4590 methods. This should be a good guide for you in choosing classes to start with. >>> >>> You can actually run this image live in JSqueak on the web if you have Java installed and the planets are aligned correctly... >>> http://Weather-dimensions.com/Dan/JSqueak.jnlp >>> Another interesting statistic is that the Java .jar file is only 433k, including not only the VM, but also the entire image! This is possible because the image is so small that the pointers in it are mostly zeroes, so it compresses nicely. I just checked that this runs, and was happy to see that it putts along at 21 million bytecodes/sec on my laptop. >>> >>> I haven't looked recently, but I think you'll find Mini2.2.image or something like it in the same place where all the historical releases of Squeak are kept. Let me know if you can't find it. >>> >>> Have fun with your project! I hope this helps >>> >>> - Dan >>> _______________________________________________ >>> 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 7, 2010