- Pharo-dev - lists.pharo.org

[Pharo-project] How to remove Monticello?
by Hilaire Fernandes Aug. 1, 2010

Aug. 1, 2010

Dear all, I tried this: (MCPackage named: 'MonticelloGUI') unload. (MCPackage named: 'MonticelloConfiguration') unload. (MCPackage named: 'Monticello') unload. but the third line did not work. Any experiences to share on that topic? Thanks Hilaire

1 1

[Pharo-project] Make PackageOrganizer>>packageOfClass:ifNone: and PackageOrganizer>>packageOfMethod:ifNone: return the most specific package it can find
by StÃ©phane Ducasse Aug. 1, 2010

Aug. 1, 2010

Hi I like the suggestion of daniel in Make PackageOrganizer>>packageOfClass:ifNone: and PackageOrganizer>>packageOfMethod:ifNone: return the most specific package it can find http://code.google.com/p/pharo/issues/detail?id=1752 Now I would like to have another pair of eyes on it. This is related to my idea of non overlapping package. Stef Fixed in: http://www.squeaksource.com/PharoInbox/PackageInfo-DanieRoux.35.mcz Took the fix from, and deprecated #mostSpecificPackageOfMethod:ifNone: and #mostSpecificPackageOfClass:ifNone: Background of problem: In theory it should not be possible for packages to overlap. Every class, and every method should belong to only one Category. In reality packaging bugs and other actions does cause packages to be created that overlap. An example in PharoCore, 10505 is this: (PackageOrganizer default packageNamed: 'Collections' ifAbsent: [ self error: 'hmm']) includesClass: Text. " true " (PackageOrganizer default packageNamed: 'Collections-Text' ifAbsent: [ self error: 'hmm']) includesClass: Text. " also true! " In the old implementation, #packageOfClass: would have returned the first category that matches. It will now return the more specific 'Collections-Text'. I suggest that #mostSpecificPackageOfClass* and #mostSpecificPackageOfMethod* methods be removed?

1 0

[Pharo-project] CogVM as official Pharo VM?
by Mariano Martinez Peck Aug. 1, 2010

Aug. 1, 2010

Hi folks. Hope Eliot is reading this thread. It is time to think in Pharo 1.2 and we need to discuss if we want to have CogVM as the standard Pharo VM. Most of us have tried it and found it incredible fast. So it would be very good to take advantage of it. But I think there are a couple of things to be discussed: 1) Cog VM seems to be aimed for x86 and 32 bits. You can read Eliot quotes: "The Cog VM is a just-in-time compiler that currently supports only x86 No effort has been made to maintain 64-bit compatibility. Apologies, this was unaffordable." So...how much important is this for us? do we care? and if we want to do it, is it "doable" ? is it less doable than the normal squeak VM ? I really would like to have 64bits VM + 64bits images in a near future...but hat's just my thoguhts. 2) The status of the external plugins. Are they working with Cog ? Not only the "core plugings" but FFI, OSProcess (I read some problems with it), TrueType, etc... 3) Is it stable for production use? For example, I read that with seaside there are some crashes. 4) Depends on heroes. I never liked this idea. It has nothing to do with Eliot. He is very cool and helpful. But I wonder, do we understand the new VM and the changes? are we able to handle and fix it even without eliot ? 5) Integration to VMMaker. I saw that they started to merge cog (actually, I think only stack vm?) to the trunk of VMMaker. This is really good news. I hope everything is there and merged. 6) Binaries. It seems the official released didn't come with binaries. So we should compile it for each OS. Ok..that's all my thoughts. I would really like to have a discussion here and see what to do.....grrrrrr you are all in holidays, aren't you? hahah cheers Mariano

9 15

[Pharo-project] More on autotest
by Alexandre Bergel Aug. 1, 2010

Aug. 1, 2010

Hi Laurent! One thing with autotest. When I compile a method, even though it is not covered by the tests, the tests are run again. This does not always make sense I feel since it slow down the way I code... For example, when I am defining a meta-model, then running the test each time I add some business method it makes sense. However, when I define a mondrian visualization, all #visualize have to be excluded by autotest. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

Re: [Pharo-project] [Pharo-users] Couple of newbie questions
by Mariano Martinez Peck July 31, 2010

July 31, 2010

Grrrr I know you were going to bother with that ;) I couldn't scape jahahaha ok...here it is: http://book.pharo-project.org/book/FAQ/ BUT I HATE MY STYLE. I cannot put a nice CSS or display of the page. If someone can help me, please....it is ugly. In addition, I didn't add it to http://www.pharo-project.org/documentation/faq because I think they are different kinds of FAQ. what do you think? I still hope someone has time to migrate the techincal stufff from SCG to the new book. It would be awesome. http://scg.unibe.ch/wiki/faq/pharo Cheers Mariano On Sat, Jul 31, 2010 at 6:35 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > mariano > > we should turn that into an FAQ and add it to the collabactive book? > > Stef > > On Jul 24, 2010, at 8:09 PM, Mariano Martinez Peck wrote: > > > > > > > On Sat, Jul 24, 2010 at 2:29 PM, Thomas Worthington < > thomas(a)2worthingtons.net> wrote: > > Hi everyone, > > > > > > Hi and welcome! > > > > Two questions: > > > > 1) How do I get my Pharo 1.0 to "upgrade" to the 1.1 image? > > > > > > The system update is disabled in purpose. The Pharo image cannot be > updated anymore. Only PharoCore images can be updated. So..what you have to > do is to just download a Pharo 1.1 image :) > > > > If you are curious why updates were disable, read: > http://forum.world.st/update-1-1-11371-tp2229126p2231195.html > > > > Just FYI the latest 1.1 release is here: > https://gforge.inria.fr/frs/download.php/27254/Pharo-1.1-11409-rc4dev10.07.… > > > > as you can see in http://www.pharo-project.org/pharo-download > > > > 2) How do I make a "one-click" image that will start my app when clicked? > > > > > > Very easy. Two options: > > > > - Take your new image (both .image and .changes), put exactly the same > file names, and override the original files that can be found in > /Contents/Resources . I think they are named Pharo-1.0.image and > Pharo-1.0.changes > > > > - This option is the proper one. It depends on the OS you are using. If > you are in Linux, just edit the Pharo.sh file so that it points to your new > image (where it says "$RES/Pharo-1.0.image"). If you are in Windows, edit > the Pharo.ini file where it says > "ImageFile=Contents\Resources\Pharo-1.0.image". > > > > Sorry if these are FAQs, but I couldn't find answers via Google. > > > > > > We should add it to FAQ or book. > > > > Where you aware of http://book.pharo-project.org/ and > http://pharobyexample.org/ ? > > > > Cheers > > > > Mariano > > > > TW > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

1 0

[Pharo-project] Pharo 1.1/1.2 and class names in Chinese
by empty July 31, 2010

July 31, 2010

In 1.1 and 1.2, without setting a language environment for Chinese, I am able to use Chinese by setting fonts. It seems to work except for accepting a class named in Chinese will end in a ClassBuilder error of 'Class names must be capitalized'. Well is it a feature(requires language environment being set correctly) or bug? The code located being: validateClassName: aString "Validate the new class name" aString isSymbol ifFalse: [ ^ false ]. aString first canBeGlobalVarInitial ifFalse:[ self error: 'Class names must be capitalized'. ^false]. environ at: aString ifPresent:[:old| (old isKindOf: Behavior) ifFalse:[ self notify: aString asText allBold, ' already exists!\Proceed will store over it.' withCRs]]. ^ true and following the code the problemic method is #canBeGlobalVarInitial: which is found in two classes: in EncodedCharSet class side: canBeGlobalVarInitial: char | leadingChar | leadingChar := char leadingChar. leadingChar = 0 ifTrue: [^ self isUppercase: char]. ^ self isLetter: char. and in LanguageEnvironment canBeGlobalVarInitial: char ^ Unicode canBeGlobalVarInitial: char. I didn't set a Chinese environment and the exception is occured in in EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought to be lowercased. ----- åç¡ä½ åç¡æ³ åç¡å§ -- View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

11 17

[Pharo-project] copying always the .sources ??? [WAS] Re: PharoCore 1.1 comments
by Mariano Martinez Peck July 31, 2010

July 31, 2010

2010/7/30 Miguel Enrique CobÃ¡ MartÃnez <miguel.coba(a)gmail.com> > Hi all, > > some things I noticed in PharoCore 1.1 release: > > > - This PharoCore-1.1.zip doesn't include a sources file. It was good to > have it included in the zip as before. Can be included for every > PharoCore release? > > - The page says that PharoV10.sources is for use with 1.0, 1.1 and 1.2. > Shouldn't be better to have a different one for each release? (even if > 1.1 is a copy of 1.0, the different name avoids doubts about numbering > scheme): > > PharoCore-1.0.image > PharoCore-1.0.changes > PharoV10.sources > > PharoCore-1.1.image > PharoCore-1.1.changes > PharoV10.sources (???) > > I also thought about this and that could be confusing with newcomers. But if .sources didn't change in 1.1 and 1.2, is it necessary to have them? or the note saying that PharoV10.sources works for all is enought ? Cheers Mariano > ... > > PharoCore-1.7.image > PharoCore-1.7.changes > PharoV10.sources (bigger ???) > > Just a suggestion. ;) > > - SystemVersion current majorMinorVersion prints: > > PharoCore 1.0: 'PharoCore1.0' > > PharoCore 1.1: 'Pharo1.1' > > Maybe this should be in the script preparing the image so that correctly > set the version string for PharoCore images and for Pharo images (or > maybe already is there but wasn't executed?) > > Other than that, the new image is *very* fast! > > Cheers > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] Conflic between Shout and PluggableTextMorph in Pharo 1.2
by Mariano Martinez Peck July 31, 2010

July 31, 2010

Hi. If you try to load Shout, you will have the error: 'styler is already defined in PluggableTextMorph' The problem is that the Shut class PluggableShoutMorph subclass PluggableTextMorph. PluggableShoutMorph has its own instVar 'styler' which PluggableTextMorph doesn't have in Pharo 1.1 But in Pharo 1.2 (I don't know why) PluggableTextMorph has its own instVar 'styler'....thus, the problem. Of course, if I remove the instVar 'styler' from PluggableShoutMorph it shoud load...but I am not sure if this is the correct action. Thanks for the help in advance Mariano

2 3

July 31, 2010

12071 ----- - Issue 2732: Paste Up Clean up post actions required - Issue 2731: SystemNavigation cleaning - Issue 2730: Dialog cleaning - Issue 2728: MCSubDirectoryRepository should not use / but - Issue 2709: printStringHex for Character Stef

1 0

[Pharo-project] SqueakSSL fails...
by Andrei Stebakov July 31, 2010

July 31, 2010

I've downloaded the SqueakSSL.dll plugin and put it in the root folder. Also I've downloaded SqueakSSL-Core SqueakSSL-Plugin SqueakSSL-Tests All tests passed. Now when I try to execute "SqueakSSL google: 'Squeak'." It fails creating the module in primitiveSSLCreate "Primitive. Creates and returns a new SSL handle" <primitive: 'primitiveCreate' module: 'SqueakSSL'> ^self primitiveFailed How can I fix it? Thank you, Andrei

4 7