August 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] About v4 strike fonts

by StÃ©phane Ducasse

Hi john I downloaded the vm from your web site and I got 1.0. So I removed all the 4.4.1beta2U vm and replaced them by the latest one. This is really strange. Stef On Aug 9, 2009, at 7:33 PM, John M McIntosh wrote: > Ok, yesterday I had grabbed the Pharo1.0beta latest update: #10401 > from the download link on the pharo > page in order to rebuild the iPhone ebook st80docs (I'll say more > once Apple approves). > > So this morning I fired up the image using a macintosh carbon > 4.1.1beta2U vm then executed > >>> | f1 f2 | >>> f1 := Form extent: 8@8 depth: 32. >>> f1 fillColor: (Color r: 1.0 g: 1.0 b: 0.7 alpha: 0.6). >>> f2 := Form extent: 8@8 depth: 32. >>> f2 fillColor: (Color r: 0.5 g: 1.0 b: 0.7 alpha: 0.7). >>> (BitBlt toForm: f1) sourceForm: f2; combinationRule: 20; copyBits. >>> (f1 colorAt: 2@2) alpha > > > and I get 1.0 > > > I note http://article.gmane.org/gmane.comp.lang.smalltalk.sapphire.devel/8433 > Maybe you have the 2007 BitBltPlugin.bundle loaded? > > > > On 9-Aug-09, at 9:37 AM, Juan Vuletich wrote: > >> StÃ©phane Ducasse wrote: >>> >>> >>> >>> >>> So I do not know what to think. I have the latest vm and this is >>> the one which executed the image. >>> Of course we will have to change this vmVersion to write the exact >>> pharo image >>> number which is here 10413 >>> >>> Stef >>> >>> >> Neither do I. The attach is what I get. John, can you shed some >> light on this? >> >> BTW, leaving now. Will be back in about 8 hours, and check mail then. >> >> Cheers, >> Juan Vuletich >> <display.png> > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > >

Aug. 9, 2009

Re: [Pharo-project] [ANN] 10412

by StÃ©phane Ducasse

Adrian if the behavior in MethodAuthorship is better we can just removed what I integrated. There is no problem. Let me know. Stef On Aug 9, 2009, at 5:17 PM, Adrian Lienhard wrote: >> - Issue 1054: Cuis code author CUIS code author checking code >> SystemNavigation default contributorsNotSignatories >> SystemNavigation default allContributors >> SystemNavigation default contributionsOf: ... > > Stef, what is the difference to the Methodauthorships package that > we've use for the license cleaning [1]? It seems that now we have a > duplicated and obsolete list of signatories in the image. Or did you > merge? > > Cheers, > Adrian > > http://code.google.com/p/pharo/wiki/LicenseCleanEffort > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 9, 2009

Re: [Pharo-project] a process to maintain non core package

by Keith Hodges

Keith Hodges wrote: > Adrian Lienhard wrote: > >> Hi, >> >> I really think we need a package management system and a process to >> maintain it. >> >> The goal is that loading and using non-core packages "just >> works" Same goal as for Sake/Packages, and it works for me. >> (unlike for instance SqueakMap, where loading more often fails >> than succeeds because there are a lot of obsolete packages and a >> dependency mechanism is missing). >> >> - There should be a responsible maintainer for each package >> Not a realistic proposition. Better to be open to all to maintain on behalf of the community. >> - For each package there should be a known way to discuss and report >> problems >> That's just arbitrary metadata in the package definition, for more general topics we use the packages(a)squeakfoundation.org mailing list >> - A gate keeper includes and removes packages from the set depending >> on their status >> Probably too complicated to be practical. >> This limits the set of included packages (at least initially) but >> would increase the quality and hence the user experience. >> >> Maybe there could be two sets, a stable and an unstable set. New >> Sake/Packages supports a stable and a beta release of each package. >> packages would first go to the unstable set and then move up to the >> stable set after a while. >> >> An automated build process could load packages into new builds and >> report the result of the tests. >> Bob does that. >> The package management system does not need to be very sophisticated, >> Sake is as simple as possible for defining actions with dependencies. >> but it should manage dependencies and have a simple GUI (to search for >> packages and see what is already loaded). >> Sake/Packages uses the class browser as is, no extra GUI is required. Packages provided explore shows you what is loaded, and this should be merged into PackageOrganization. Keith

Aug. 9, 2009

Re: [Pharo-project] Wiki for Pharo future work [WAS] preparing 1.1

by Adrian Lienhard

Thanks a lot, Mariano! I did a quick pass making some items more descriptive and deleting obsolete ones. I added a "(?)" at the end of items that I do not understand. I deleted the now obsolete wiki pages. Regarding http://code.google.com/p/pharo/wiki/Milestones I think we should move all items in milestone 2 and below into the IdeasToImplement page as well. Adrian On Aug 9, 2009, at 20:19 , Mariano Martinez Peck wrote: > Hi folks. I have integrated and merged all those links for future > things for > Pharo in this page: > > http://code.google.com/p/pharo/wiki/IdeasToImplement > > There are a lot of items I really don't know what they are and they > have > very little information. Sometimes only a single world. I don't know > who > wrote those things, but it would be wonderful people could take 5 > minutes > and try to give more information about the items: explanations, > details, > links, whatever. Because perhaps the one who wrote that understands > it but > the others don't. If you don't have edit permissons just ask or let > me know > and I write it. > > Finally, we should update the milestones page. However I don't have > the > knowledge neither the authority to do this. Please the board or > someone > update this. > > Best, > > Mariano > > > > > ---------- Forwarded message ---------- > From: Adrian Lienhard <adi(a)netstyle.ch> > Date: Thu, Aug 6, 2009 at 8:21 AM > Subject: Re: [Pharo-project] preparing 1.1 > To: Pharo-project(a)lists.gforge.inria.fr > > > There are also the following related wiki pages: > > http://code.google.com/p/pharo/wiki/Milestones > http://code.google.com/p/pharo/wiki/HaveALookAt > http://code.google.com/p/pharo/wiki/PlanToUse > http://code.google.com/p/pharo/wiki/ToDoBetterOnLongTerm > http://code.google.com/p/pharo/wiki/BetterMop > > (We should consolidate these pages.) > > If you have feature requests for 1.1, please post them here. > > Adrian > > On Aug 6, 2009, at 12:30 , StÃ©phane Ducasse wrote: > >> Hi guys >> >> we would like also to get a list of items for 1.1 >> >> http://code.google.com/p/pharo/wiki/IdeasToImplement >> >> >> â¢ MethodReference? and CompiledMethod? >> â¢ Clean category / comments (some package are totally wrong) >> â¢ First class packages >> â¢ Files: Cleaning file/directory (Gnu + rio rewrite) >> â¢ Streams >> â¢ Remove projects and other >> â¢ Clean ImageSegments? >> â¢ MethodReference?/CompiledMethod? >> â¢ NewCompiler? >> â¢ Better browser >> â¢ Cleaning Morphic (better integration of Polymorph) >> â¢ Rome and other Sophie library >> â¢ Preferences using pragmas >> â¢ Checking CUIS enhancement >> â¢ Checking Squeak enhancement >> â¢ Enhancement Strike Fonts >> â¢ underscore in selector >> - test server >> _______________________________________________ >> 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

Aug. 9, 2009

[Pharo-project] New Pharo based on core 10413 - Win32 Setup

by Torsten Bergmann

The win32 full installer for this version is now up on: http://pharo-project.org/pharo-download Have fun Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Aug. 9, 2009

Re: [Pharo-project] About v4 strike fonts

by Mariano Martinez Peck

Yes. This is a known problem by Juan. He told me: "You need a newer VM, with a fix I did in April. For Windows you need SqueakVM-Win32-3.11.3-bin.zip. For Mac, I'm not sure, but it needs that patch. With an older VM, the symptoms are those Mariano said. Oh, a workaround in case you don't have an updated VM is to set Display depth to 16 bits." I don't know which is the VM fix. I cannot test it because I am in Linux. Best, Mariano 2009/8/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > When I move a window I get the following visual effect with strike font > loaded > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 9, 2009

[Pharo-project] Wiki for Pharo future work [WAS] preparing 1.1

by Mariano Martinez Peck

Hi folks. I have integrated and merged all those links for future things for Pharo in this page: http://code.google.com/p/pharo/wiki/IdeasToImplement There are a lot of items I really don't know what they are and they have very little information. Sometimes only a single world. I don't know who wrote those things, but it would be wonderful people could take 5 minutes and try to give more information about the items: explanations, details, links, whatever. Because perhaps the one who wrote that understands it but the others don't. If you don't have edit permissons just ask or let me know and I write it. Finally, we should update the milestones page. However I don't have the knowledge neither the authority to do this. Please the board or someone update this. Best, Mariano ---------- Forwarded message ---------- From: Adrian Lienhard <adi(a)netstyle.ch> Date: Thu, Aug 6, 2009 at 8:21 AM Subject: Re: [Pharo-project] preparing 1.1 To: Pharo-project(a)lists.gforge.inria.fr There are also the following related wiki pages: http://code.google.com/p/pharo/wiki/Milestones http://code.google.com/p/pharo/wiki/HaveALookAt http://code.google.com/p/pharo/wiki/PlanToUse http://code.google.com/p/pharo/wiki/ToDoBetterOnLongTerm http://code.google.com/p/pharo/wiki/BetterMop (We should consolidate these pages.) If you have feature requests for 1.1, please post them here. Adrian On Aug 6, 2009, at 12:30 , StÃ©phane Ducasse wrote: > Hi guys > > we would like also to get a list of items for 1.1 > > http://code.google.com/p/pharo/wiki/IdeasToImplement > > > â¢ MethodReference? and CompiledMethod? > â¢ Clean category / comments (some package are totally wrong) > â¢ First class packages > â¢ Files: Cleaning file/directory (Gnu + rio rewrite) > â¢ Streams > â¢ Remove projects and other > â¢ Clean ImageSegments? > â¢ MethodReference?/CompiledMethod? > â¢ NewCompiler? > â¢ Better browser > â¢ Cleaning Morphic (better integration of Polymorph) > â¢ Rome and other Sophie library > â¢ Preferences using pragmas > â¢ Checking CUIS enhancement > â¢ Checking Squeak enhancement > â¢ Enhancement Strike Fonts > â¢ underscore in selector > - test server > _______________________________________________ > 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

Aug. 9, 2009

Re: [Pharo-project] a process to maintain non core package

by Miguel Enrique CobÃ¡ Martinez

El dom, 09-08-2009 a las 10:29 -0700, Dale Henrichs escribiÃ³: > - Package to package dependencies. One can declare required packages > like the > following: > 'Example-Core-anon.9' > 'Example-Tests-anon.3' requires: 'Example-Core' > 'Example-AddOn-anon.1' requires: 'Example-Tests' > 'Example-UI-anon.1' requires: { 'OB'. 'Example-AddOn'. } > From the above statements, the package load order is derived and used when you > load the project: > (ExampleProject version: '0.3') load > It is also used to determine _which_ packages should be loaded when an > expression like the following is executed: > (ExampleProject version: '0.3') load: 'Example-AddOn' > This statement causes 'Example-Core-anon.9', 'Example-Tests-anon.3', > 'Example-AddOn-anon.1' to be loaded in order. This is very good, one thing that the package management system of Debian has is that you can indicate a minimal version for a required package: for example, following your code snippet: 'Example-Core-anon.9' 'Example-Tests-anon.3' requires: 'Example-Core' minVersion: 9 'Example-AddOn-anon.1' requires: 'Example-Tests' minVersion: 1 maxVersion: 3 'Example-UI-anon.1' requires: { 'OB' . 'Example-AddOn'. } This way, the package system doesn't have to install a exact version if a group of versions of the package required can equally work. This permits to have a package, say 5 of a package that have a new feature that I need in my image and not be overwrote by a dependency of other package that needs exactly version 3 that doesn't have the feature that I need. Maybe Metacello has this functionality, but if not, it would be, I think, easy to add it, just a comparation that the version available in the system meets the criteria stated by the package dependency. Also, a form to force the install a package even if not all the dependencies are met is good, in particular to test some experimental package. For more information you can refer to the dpkg/deb/aptitude tools in the debian system. Of course that tools do a lot more but we don't need, at least for now, all the features. http://en.wikipedia.org/wiki/Aptitude_(program) http://en.wikipedia.org/wiki/Deb_(file_format) http://en.wikipedia.org/wiki/Dpkg All of them are GPL but I think that a new implementation, without use the code, and in another language, using only the ideas, is permited and can be integrated in Pharo as MIT code.

Aug. 9, 2009

[Pharo-project] 64bit

by Carlos Crosetti

I havent`t seen 64-bit in the milestones... why not?

Aug. 9, 2009

Re: [Pharo-project] preparing 1.1

by Stan Shepherd

StÃ©phane Ducasse-2 wrote: > > Hi guys > > we would like also to get a list of items for 1.1 > > http://code.google.com/p/pharo/wiki/IdeasToImplement > > I don't know if the following is already possible? For useability, it would be nice to have the option that 'save as new version' creates a version numbered copy on disk, but retains the current image name. So if I use the Seaside one click image, I can periodically take a save (Seaside.1.image, Seaside.1.changes, etc) but the launcher still sends me to the latest version at Seaside.image. ...Stan -- View this message in context: http://n2.nabble.com/preparing-1.1-tp3397488p3413472.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 9, 2009