January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] What about killing PharoWeb images?

by Mariano Martinez Peck

Ok....so, after reading all answers and comments I see the following possible actions: 1) Do nothing and keep things as now 2) Like 1) but change PharoWeb name to PharoSeaside. 3) Don't create PharoWeb images any more but gives the user the possibilities to use Seaside + Pharo. Now, my final point of view: 1) I don't like it because of what I have already said. 2) I like it more than 1) but anyway I don't like it. 3) For me it is the best solution. We can do, the following things: 3.a) Put in www.pharo-project.org/download a text among these lines: "There are few ways to develop Web application using Pharo. The most important and common framework is Seaside. Seaside is the web framework for building sophisticated applications in Smalltalk. Seaside provides what it is called "one click image" which is a compressed file that you only need to uncompress and double click to have a complete IDE to develop with seaside (even with web browser!!!). The link is... Take into account that this image may have different look and feel, preferences and tools from our one PharoDev image. This image is recommended for beginners and new comers. However, there is another way to use Seaside with Pharo and it is installing it by yourself in a PharoDev image. To do this, the best approach is to use the Metacello configuration. To do that, just evaluate the following code in a PharoDev image: Gofer....ConfiguratioOfSeaside...etc This apprach is recommended for people who already have a little of knoweldege with Pharo and Seaside. " 3.b) Using this way, we encourage people to use the Metacello configuration for Seaside and that's the most important thing because we can give feedback on it, fix issues, etc. And this is also shared for example with Gemstone. They will give feedback on us and us on them. We will probable make even simpler the move for applications from Pharo to Gemstone. 3.c) Those beta testers that said that they would test Web images, can just install Seaside exactly the same way a final user will do (use the metacello configuration). So...we are also testing that. 3.d) Not now, but maybe in a future we can even use the Esteban Lorenzano's Loader for Metacello. That would be even simpler. They will be able to take a PharoDev image and just evaluate: Loader load:'Seaside 2.8.4' and wala! So...I don't know how this kind of big decisions are taken. The borad decides? We do a poll ? I don't know. What do we do ? On Tue, Jan 5, 2010 at 11:01 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Tue, Jan 5, 2010 at 12:34 AM, Adrian Kuhn <akuhn(a)iam.unibe.ch> wrote: > >> Lukas Renggli <renggli@...> writes: >> >> > If you are really into building images, you should build them for YOU >> > and not for anybody else. Otherwise, I think, they are never going to >> > fly. >> >> +1 >> >> > > But the concern about this emails was final users, maybe even beginners and > new comers. Most of us (who have some time with Pharo) use our own build > images, but they do not. > > > >> --AA >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

Jan. 5, 2010

Re: [Pharo-project] ImageSegment fixes in Inbox

by Mariano Martinez Peck

Stef: I commited the merged version in Inbox: Name: SLICE-FixToImageSegmentMerged-MarianoMartinezPeck.1 Author: MarianoMartinezPeck Time: 5 January 2010, 2:07:03 pm UUID: eb5d6921-054b-4fb6-b62c-c545a7aec3ad Ancestors: Dependencies: System-Object Storage-MarianoMartinezPeck.50 Fix to ImageSegment merged On Tue, Dec 29, 2009 at 10:15 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > Sheridan is in holidays. As I will start with the cleaning and refactor > soon I wanted to commit a version that at least fixes the current problems. > > I imagine. > > > However, I wouldn't commit them in 1.0, just 1.1. > > Yes 1.0 should only accept a fix for the double past problem. > > > But.....I have been testing this in 1.0. The problem is that in 1.1 > ImageSegment doesn't work anymore because of the Issue 1075: Clean > officialClass and isSystemDefined > > Search senders for isSystemDefined and you will see several. I don't know > how to fix them :( > > indeed we should not have senders of them in the image if we removed the > behavior. > > > I should check that. > > Please > > > > It would be cool if Adrian could also give some feedback, but I think he > is in Holidays too. I cc him just in case. > > > > I have written 20 unit tests also that I can commit if you want. Only one > is yellow in 1.0. > > cool. > It would be probably good too. > > Stef > > > > Cheers > > > > Mariano > > > > On Dec 29, 2009, at 9:19 PM, Mariano Martinez Peck wrote: > > > > > Hi! After several days of surfing the beatiful ImageSegment code, I > fixed several issues. I commit to Inbox the SLICE-FixesToImageSegment. > > > > > > > > > This are the changes in my commit: > > > > > > - Removed Beeper beepPrimitive from ImageSegment >> install > > > - Fix to writeToFile. See issue 1204 > > > http://code.google.com/p/pharo/issues/detail?id=1204 > > > - Now ImageSegment >> discoverActiveClasses answer the number of them > > > - New method ImageSegment >> unActiveClasses > > > - Fix to ImageSegment >> swapOutInactiveClasses. I have to hold the > allSymbols and to > > > exclude the Multilingual and Kernel package from the swap. This should > fix issues > > > 1203 and 1204. > > > - The errors for wrong states now print the current state and also the > expected one. > > > - Fix issue 207. > > > > > > > > > Take a clean image and evaluate: > > > > > > Smalltalk at: #MDFaultDict put: Dictionary new. > > > > > > Then > > > > > > | count | > > > count := ImageSegment discoverActiveClasses. > > > Transcript show: 'Classes forced: ', count asString. > > > > > > Do something > > > > > > And finally evaluate > > > > > > | count | > > > count := ImageSegment activeClasses size. > > > Transcript show: 'Classes active ', count asString. > > > > > > or > > > > > > | count | > > > count := ImageSegment unActiveClasses size. > > > Transcript show: 'Classes active ', count asString. > > > > > > Whit this, there is no trace. Even if puting the dictionary. > > > A simple hack to see this is to change activeClasses to use > > > recoverFromMDFaultWithTrace instead of recoverFromMDFault > > > If you do that, you will be able to inspect Smalltalk at: #MDFaultDict > > > > > > > > > I also fixed the swapOutInactiveClasses. The image have several > emergency windows before this. > > > > > > > > > > > > > > > _______________________________________________ > > > 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 >

Jan. 5, 2010

Re: [Pharo-project] [Seaside] Mac VM 5.2b1 ships

by Nicolas Cellier

Hi John, I noticed that control + arrow does not work in text editors (it used to skip to next/previous word) Nicolas 2010/1/4 Mariano Martinez Peck <marianopeck(a)gmail.com>: > John: Another problem I found is that I cannot open more than one image at > the same time with this VM. Is this expected? > > Cheers > > Mariano > > On Sun, Jan 3, 2010 at 9:28 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: >> >> Hi >> >> I asked abotu alien because at Amsterdam eliot used bird names to refer to >> FFI >> implementation. So I was thinking that building on top of Alien was a move >> into the future. >> May be you should talk with eliot. >> >> Stef >> > >> > 64-bit FFI will work on Unix and Windows with these fixes. I have not >> > tried Mac, but I expect that some work would be needed. The changes >> > are not trivial, and will affect the plugin, the VM itself, and the >> > Pharo/Squeak images. >> > >> > The next big fix on our VM-team "to-do list" is to get sound working >> > on 64-bit platforms, and FFI will come after that. >> > >> > I do not know the status of alien now, but my understanding is that >> > it is limited to intel processors and 32-bit platforms. My guess is >> > that it would be good to fix the old FFI first because those changes >> > would likely have an impact on alien also. But I do not know much >> > about alien, so I am not the best person to say. >> > >> > Dave >> > >> > >> > _______________________________________________ >> > 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 >

Jan. 5, 2010

Re: [Pharo-project] What about killing PharoWeb images?

by Schwab,Wilhelm K

My big concern is that either testing of Pharo will suffer (things that are made difficult tend not to happen), or that a bunch of us will end up with ad-hoc build processes rather than having it done in one place with a chance of getting it right. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Tuesday, January 05, 2010 5:02 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] What about killing PharoWeb images? On Tue, Jan 5, 2010 at 12:34 AM, Adrian Kuhn <akuhn(a)iam.unibe.ch<mailto:akuhn@iam.unibe.ch>> wrote: Lukas Renggli <renggli@...> writes: > If you are really into building images, you should build them for YOU > and not for anybody else. Otherwise, I think, they are never going to > fly. +1 But the concern about this emails was final users, maybe even beginners and new comers. Most of us (who have some time with Pharo) use our own build images, but they do not. --AA _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 5, 2010

Re: [Pharo-project] Thanks Danny :)

by Mariano Martinez Peck

Stef is not laying. Right now I am seeing Stef lesson at Ecole de Mines and I swear that in his presentation (he is projecting his notebook) he has the picture scanned as wallscreen. On Mon, Jan 4, 2010 at 10:32 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > I put the stamp into > https://gforge.inria.fr/frs/?group_id=1299 > I will add the mp4 (apparently it did not make it). > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 5, 2010

Re: [Pharo-project] What about killing PharoWeb images?

by Mariano Martinez Peck

On Tue, Jan 5, 2010 at 12:34 AM, Adrian Kuhn <akuhn(a)iam.unibe.ch> wrote: > Lukas Renggli <renggli@...> writes: > > > If you are really into building images, you should build them for YOU > > and not for anybody else. Otherwise, I think, they are never going to > > fly. > > +1 > > But the concern about this emails was final users, maybe even beginners and new comers. Most of us (who have some time with Pharo) use our own build images, but they do not. > --AA > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 5, 2010

[Pharo-project] Documentation (was Re: about DependencyBrowser)

by Stan Shepherd

Mariano Martinez Peck wrote: > > On Sat, Dec 26, 2009 at 10:06 PM, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: >> >> Colors were originally for idenfitying dependency types of external >> packages, but the package infos names aren't normalized, E.g. >> Normalized name = "Collections", Un-normalized name = >> "Collections-Strings", hence you will see a lot of false external >> packages colorized. >> >> Orange -> Dependecy of class reference of "external" package, or class >> reference in un-normalized package name. >> Brown -> Dependency of external package loose method, or loose method >> in un-normalized package name. >> Red -> Dependency of inheritance, or inheritance in un-normalized package >> name. >> Blue -> Dependency of a unsolved binding (like a class not present in >> the image). >> > > Thanks for the explanation. Now, as a good programmer you can reuse this > explanation and put it in the website :) > > Hmm, wouldn't it be handy if the documentation were maintained in a Wiki, so the receiver of the reply could just paste it into the correct place, and it would be loaded into the image ;) Otherwise, this could end up in the 'tacit knowledge' bucket. see http://n2.nabble.com/Solving-the-documentation-problem-Capturing-tacit-know… http://n2.nabble.com/Solving-the-documentation-problem-Capturing-tacit-know… ...Stan -- View this message in context: http://n2.nabble.com/about-DependencyBrowser-tp4218735p4254322.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 5, 2010

Re: [Pharo-project] Building Pharo and Plugins for Mac OS X and Linux

by StÃ©phane Ducasse

this is cool! Stef On Jan 5, 2010, at 5:21 AM, David T. Lewis wrote: > On Mon, Jan 04, 2010 at 09:04:26PM +0100, St?phane Ducasse wrote: >> David >> check the squeak documentation on how to invoke external library with FFI. >> In pharo you have also alien (not tested on non intel - works on mac). >> >> You do not have to recompile the vm to invoke external library. You define methods with specific pragmas >> annotations and the plugin code can be invoked. >> >> One if these days we should write a better doc >> >> http://wiki.squeak.org/squeak/2426 >> http://www.is.titech.ac.jp/~ohshima/squeak/DShowVideo/index.html >> http://www.visoracle.com/squeak/faq/ffi-windows.html >> http://wiki.squeak.org/squeak/356 >> >> VMMaker is published on SqueakSource. >> May be people with more experience will comment. > > Tim Rowledge's explanation of VMMaker is here: > http://wiki.squeak.org/squeak/2105 > > You will also find detailed instructions for VM builders along > with the platform source code, which is maintained in a Subversion > source code repository at squeakvm.org: > http://squeakvm.org/cgi-bin/viewcvs.cgi/trunk/platforms/ > > For example, documentation on building for Unix (Linux) will > be found here: > http://squeakvm.org/cgi-bin/viewcvs.cgi/trunk/platforms/unix/doc/HowToBuild… > > And for Windows: > http://squeakvm.org/cgi-bin/viewcvs.cgi/trunk/platforms/win32/docs/?rev=2147 > which points to: > http://squeakvm.org/win32/ > > And for Mac OS: > http://squeakvm.org/cgi-bin/viewcvs.cgi/trunk/platforms/Mac%20OS/vm/Documen… > as well as other documents that John mentioned in his reply. > > In other words, after you download the platform source code from the > Subversion repository, you will find detailed documentation in the > subdirectory for each of the major platforms. > > There is also a mailing list for the VM: > http://lists.squeakfoundation.org/mailman/listinfo/vm-dev > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 5, 2010

Re: [Pharo-project] Beginner question :) search and replace in String

by Douglas Brebner

On 05/01/2010 00:02, Adrian Kuhn wrote: > > I won't comment on the rest, some prefer concise language, some like to keep it > verbose. My point is that a language should offer short aliases for common > terms, and I guess all of my examples are common enough to qualify for a > shorter aliases based on that criterion--if you want to mimic the evolution of > abbreviations in natural language. > > Please bear in mind that natural languages have much more redundancy and less precision than programming languages. In addition, programming languages have handy tools like autocompletion that natural languages don't, making abbreviations less useful :)

Jan. 5, 2010

[Pharo-project] Gofer broken in PharoCore 1.0

by Miguel CobÃ¡

Reported as http://code.google.com/p/pharo/issues/detail?id=1741 Gofer is broken on PharoCore 1.0. Can't run code like: Gofer it renggli: 'unsorted'; package: 'RFB'; load. and when updated with: Gofer gofer update. fails with an error. The fix is the same as http://code.google.com/p/pharo/issues/detail?id=1680

Jan. 5, 2010