- Pharo-dev - lists.pharo.org

[Pharo-project] Settings Browser

by Geert Claes

I have to say that the new Settings Browser in 1.1 is a huge improvement over the old Preference Browser. It's just that I can't seem to figure out how to save the settings I have changed? I did noticed the "Style > New/Update/Load/Browse/Remove". I managed to create a new style, but when selecting "Style>Update" I get this tiny window titled "Choose" with a wee white box and a Cancel button? Am I missing something? ps. What is the "Blab email" in the Network section? http://n4.nabble.com/file/n2132539/Settings_Browser.png -- View this message in context: http://forum.world.st/Settings-Browser-tp2132539p2132539.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 6, 2010

Re: [Pharo-project] [Vm-dev] About CompactClasses and their future [WAS] how many free bits we have in Object Header?

by Mariano Martinez Peck

On Thu, May 6, 2010 at 12:14 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > For measuring, I wouldn't look at the current process' memory consumption > because the VM has some headroom to not have to allocate new memory too > often. Depending on when memory is grown or shrunken, this may yield very > different results. What I would do is to GC and save the image to disk and > then compare the size of the .image files. I wouldn't run the tests either. > > Thanks. I have just did that. > Making more classes compact, may make sense. But I doubt that you get 3 or > even 5 MB. That sounds way too good ;) > > hahhaa 3mb was too much, maybe 300kb ;) These are the results: Seaside 3.0 one click: original: 21MB compact: 20.2 Pharo 1.0 original: 15MB compacted: 14.6 PharoCore 1.1 original: 13.6 compacted: 13.3 So...those are the results. If you want I can create an issue and commit the script. Cheers Mariano > Cheers, > Adrian > > > On May 6, 2010, at 11:24 , Mariano Martinez Peck wrote: > > > Hi folks. I was just trying to understand this optimization of the > Compact > > Classes. If I understood correctly, most objects needs a second word > there > > they have 30 bits of OOP of their class and 2 for the header type. > > > > There are classes that have a LOT of instances. For those cases we have > > compact classes where their instances have a number using those 5 bits in > > the first word of the header, and thus, they don't need a second header. > > Then, less memory is used. > > > > So...I understood ok ? > > > > Now, if that is the situation. I have evaluated Smalltalk > > compactClassesArray and I see that in the array there are a lot of nils. > 16 > > classes in Squeak and 15 in Pharo. The rest of the 31, are just nil. > > > > Now I wonder if it is worth to do anything with that : > > > > a) Use 4 bits instead of 5 and free one more bit in the OH > > b) remove completely CompactClasses as Adrian said > > c) Let 5 bits but then add more classes (up to 31) so that we can get > > benefits of that. Do you know if there are side effects of > becomingCompact a > > class ? > > > > If I evaluate SpaceTally new printSpaceAnalysis I get something like > this: > > > > Class code space # instances inst space > percent > > ByteString 2217 71317 3621735 > 19.3 > > CompiledMethod 21064 56057 3517772 > 18.7 > > Bitmap 3893 2256 3424604 > 18.2 > > Array 2478 71108 2198420 > 11.7 > > ByteSymbol 959 37896 962465 > 5.1 > > ByteArray 2778 317 778297 > 4.1 > > MethodDictionary 1819 5964 449252 > 2.4 > > MCVersionInfo 1313 10369 414760 > 2.2 > > DateAndTime 6974 13793 331032 > 1.8 > > WeakArray 827 286 326900 > 1.7 > > Association 749 26784 321408 > 1.7 > > UUID 1528 10370 248880 > 1.3 > > Float 11442 16450 197400 > 1.1 > > ClassOrganizer 1398 5964 190848 > 1.0 > > ODatedEntry 263 7049 169176 > 0.9 > > Time 5530 10369 165904 > 0.9 > > Duration 3025 10290 164640 > 0.9 > > Date 3167 10289 164624 > 0.9 > > LargePositiveInteger 2515 14340 118169 > 0.6 > > Metaclass 4250 2876 115040 > 0.6 > > Point 6404 8476 101712 > 0.5 > > GlyphForm 307 2030 73080 > 0.4 > > FreeTypeCacheEntry 536 2238 71616 > 0.4 > > SpaceTallyItem 651 2509 60216 > 0.3 > > OrderedCollection 5351 2831 56620 > 0.3 > > FreeTypeFileInfo 797 321 30816 > 0.2 > > FreeTypeFontFamilyMember 1274 537 25776 > 0.1 > > Color 21202 1255 25100 > 0.1 > > TraitComposition 2651 2013 24156 > 0.1 > > Set 3510 1358 21728 > 0.1 > > Dictionary 5742 1344 21504 > 0.1 > > RemoteString 1533 1236 19776 > 0.1 > > SparseLargeTable 2376 2 18708 > 0.1 > > WordArray 1821 30 18608 > 0.1 > > SoundBuffer 3299 3 18508 > 0.1 > > Pragma 1558 862 17240 > 0.1 > > Preference 1534 379 16676 > 0.1 > > EventHandler 3216 125 14500 > 0.1 > > MorphExtension 3249 277 14404 > 0.1 > > Character 6428 939 11268 > 0.1 > > SortedCollection 1496 462 11088 > 0.1 > > AdditionalMethodState 2576 859 10304 > 0.1 > > ISOLanguageDefinition 18114 402 9648 > 0.1 > > TimeStamp 861 392 9408 > 0.1 > > > > > > So...for this quick evaluation, maybe we can become compact also the > > following classes for example: > > > > Smalltalk compactClassesArray > > > > #( ByteSymbol ByteArray MethodDictionary "Association" "WeakArray" > > "Metaclass" DateAndTime UUID Time Duration Date "MethodDictionary" > > ClassOrganizer Metaclass Pragma OrderedCollection RemoteString WordArray > > Color Character ) > > do: [:each | (Smalltalk at: each) becomeCompact] > > > > Do this make sense ? How could I measure this? I took a Pharo image and > > compare the memory used by the VM running all test before and after those > > new compact classes. From the "Activity monitor" I noticed between 3 and > 5 > > MB less used with these new compact classes. > > > > Thanks in advance > > > > Mariano > > > > > > On Tue, May 4, 2010 at 2:12 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > > >> > >> Hi Mariano, > >> > >> I see two solutions > >> - make the identityHash (even) smaller > >> - remove compact classes > >> > >> The former would probably not be hard to implement (just change some bit > >> masks and then rehash all sets). I've brought up the idea about the > latter > >> some time ago on this mailing list. The idea is to remove compact > classes to > >> get a larger identityHash (trading memory against speed). After the > removal, > >> only two header types are left and hence you gain a spare bit. I think > this > >> shouldn't be too much work either, but I haven't come around to > implementing > >> it (yet). > >> > >> Good luck ;) > >> Adrian > >> > >> On May 4, 2010, at 13:13 , Mariano Martinez Peck wrote: > >> > >>>>> > >>>>> Now...the question is, is there another free bit in the object header > ? > >> I > >>>>> need another one :( > >>>> > >>>> Based on the comment at the bottom of > Interpreter>>internalIsImmutable: > >>>> I suspect that somebody else has their eye on that last available bit > >>>> also ;-) > >>>> > >>>> > >>> Yes, I know :( But for the moment I don't care to "integrate" my > stuff. > >> I > >>> just want to play and experiment. And even for that, I need 2 bits :( > >>> Of course, if I once make something good to integrate, I will have > double > >>> problem :( > >>> > >>> So...no solution ? > >> > >> > >

May 6, 2010

[Pharo-project] another fun case for Linked>>add:

by StÃ©phane Ducasse

LinkedList>>add: aLinkOrObject "Add aLink to the end of the receiver's list. Answer aLink." ^self addLast: aLinkOrObject LinkedList>>addLast: aLinkOrObject "Add aLink to the end of the receiver's list. Answer aLink." |aLink| aLink := aLinkOrObject asLink. self isEmpty ifTrue: [firstLink := aLink] ifFalse: [lastLink nextLink: aLink]. lastLink := aLink. ^aLink Object>>asLink "Answer a string that represents the receiver." ^ ValueLink value: self In squeak there is no such asLink.... We need a database with all the history to know which change introduced this change. Henrik do you remember why you introduce this change? Stef

May 6, 2010

[Pharo-project] PluggableMenuSpec>>add:

by StÃ©phane Ducasse

It seems that PluggableMenuSpec >> add: aString ^ self add: aString action: nil does not exist in Squeak and since add:action: does not return a String, we should check if we should not remove this method. Stef (in the train - could not add that in the bugtracker)

May 6, 2010

[Pharo-project] Metacello questions

by Torsten Bergmann

Just have a look at ConfigurationOfSQLite3 for a simple example. This one has a "project dependency" on ConfigurationOfFFI. If you want Help system project to be loaded in your configurartion you need to define it in the baselineXXX method and set a specific version of the project in your own #versionXXX method Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 6, 2010

Re: [Pharo-project] Help System

by StÃ©phane Ducasse

In addition to the story around tests, Torsten do you think we could use book.pharo-project.org to populate the help? On May 5, 2010, at 11:45 PM, Torsten Bergmann wrote: > Again, in its current state Help System supports the two options: > > a) class comment/method comment for API help and > b) topic structure mapped to the class hierarchy (CustomHelp books) > > I understand all things said and we all have our points > about pros and cons. But hey, they are JUST two possible ways, nobody > forces you to use them. Since these two are in by default does not > mean you are limited to them. > > The help system is flexible enough to ADDITIONALLY HANDLE VARIOUS OTHER > ways of describing the help contents. So YOU CAN DEFINE AND HAVE YOUR OWN > just by extending the help system itself. > > After this discussion it looks like we all agree that it is a good > direction to check out the pragma/builder approach too and see how far we can go here. > > So please check out the code I attached to my last post. In this simple > example I've shown how you can extend the help system itself to support > other options - here a pragma/builder oriented way of describing the > help contents. > > It is not complete but should give you an idea that you are not limited > to a) and b) ... > > Bye > T. > > > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 6, 2010

[Pharo-project] Metacello questions

by Andreas Raab

Hi - I've been trying to wet my feet with Metacello a little by writing a ConfigurationOfWebClient and in the process I've come across various things that I don't understand or don't know how to express. The configuration itself can be found here: http://www.squeaksource.com/MetacelloRepository Here are the questions I'm having: 1) #includes: vs. #requires: What is the difference between #includes: and #requires:? They sound entirely interchangeable, in particular after reading the tutorial which states: "When you use the #includes: directive, you are not only specifying that the listed packages should be loaded when the parent package is loaded, but that the #included: packages should be loaded _before_ any packages that require the parent package." I would expect that precise behavior for required packages, i.e., if Foo requires: Bar then Bar is loaded before Foo if some other package requires: Foo. What am I missing? 2) Why is HelpSystem not loaded? In my configuration, baseline specifies that HelpSystem is required for WebClient-Help: "Documentation doesn't require Core/Tests, but HelpSystem" spec package: 'WebClient-Help' with:[spec requires: 'HelpSystem']. spec project: 'HelpSystem' with:[ spec className: 'ConfigurationOfHelpSystem'; repository: 'http://www.squeaksource.com/MetacelloRepository' ]. However, when executed, Metacello goes through the motions but doesn't actually *load* any version of HelpSystem (I can see it 'fetch' the packages but not load them). It even calls the postLoadDoIt on it (which fails since nothing was loaded). What am I doing wrong? 3) When exactly is HelpSystem loaded? What I'm wondering about in the above is that HelpSystem should only be loaded if WebClient-Help is being loaded. Is this implicitly part of specifying a 'project' instead of a 'package'? Or is there some other way of specifying that? I guess really the question here is what entities get loaded implicitly simply by declaring them (packages for sure, any others?) and what entities need to be 'required' in order to be loaded? 4) How does one define dependencies that differ based on platform? In WebClient, the WebClient-HTTP package requires WebClient-Core and -only for: #pharo- also WebClient-Pharo. How does one express that there's an additional dependency for WebClient-HTTP that only exists for: #pharo? The config currently specifies: spec for: #common do:[ " ... " spec package: 'WebClient-HTTP' with:[spec requires: 'WebClient-Core']. " ... " ]. spec for: #pharo do:[ "Just the fact it exists; no requirements here" spec package: 'WebClient-Pharo'. ]. Which means that WebClient-Pharo will be loaded on Pharo by default but it's missing the fact that WebClient-Pharo is in fact a requirement for WebClient-HTTP (but only on that platform). How is that best expressed? 5) Bootstrapping Metacello? I found that most of the ConfigurationsOfXXX include some code to 'bootstrap' Metacello in some form. There appear to be variants on the code; is there a "canonical bootstrap method" that should be used? 6) A standard Configuration template? The Metacello tutorial is very useful as far as the configuration goes but it falls short of getting into the details of what it means to provide a 'working' configuration. Testing the configuration isn't covered (is there a way to get back to a 'clean' state?); bootstrapping isn't covered; the meaning of #isMetacelloConfig, #metacelloVesion:loads:, #lastMetacelloVersionLoad and several other -seemingly random- methods that can be found on most -but not all- of the configurations. There is no indication on what these do, if they're required, recommended, or optional. Is there some 'standard' Configuration template that people can use to avoid guessing about which parts of the boilerplate to copy from some other configuration? That's it for now. Thanks for any insights on any of these issues. Cheers, - Andreas

May 6, 2010

Re: [Pharo-project] Help System

by StÃ©phane Ducasse

On May 5, 2010, at 11:45 PM, Torsten Bergmann wrote: > Again, in its current state Help System supports the two options: > > a) class comment/method comment for API help and > b) topic structure mapped to the class hierarchy (CustomHelp books) > > I understand all things said and we all have our points > about pros and cons. But hey, they are JUST two possible ways, nobody > forces you to use them. Since these two are in by default does not > mean you are limited to them. > > The help system is flexible enough to ADDITIONALLY HANDLE VARIOUS OTHER > ways of describing the help contents. So YOU CAN DEFINE AND HAVE YOUR OWN > just by extending the help system itself. Yes this is why I integrate it :) > After this discussion it looks like we all agree that it is a good > direction to check out the pragma/builder approach too and see how far we can go here. Yes so I would like that we agree on the pragma as I mentioned in my previous mail Then we start to tag/adapt some Unit tests and learn. > So please check out the code I attached to my last post. In this simple > example I've shown how you can extend the help system itself to support > other options - here a pragma/builder oriented way of describing the > help contents. > > It is not complete but should give you an idea that you are not limited > to a) and b) ... > > Bye > T. > > > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 6, 2010

Re: [Pharo-project] gettext package

by Philippe Marschall

On 05.05.2010 21:39, Hilaire Fernandes wrote: > Philippe Marschall a Ã©crit : >> On 04/29/2010 10:55 PM, Hilaire Fernandes wrote: >>> I have move in a Gettext package in PharoInbox classes for gettext >>> support. Do not expect it to work. Some of the classes there, are just >>> moved from former categories in pharo System-Localization and >>> Multilingual other are coming from Etoys. >>> >>> I have not yet test to load it in a fresh image. >> >> I'm interested in this for Seaside. I have a couple of notes: >> - Why do you move LocaleID from System-Localization to Gettext? > > This class was modified. It is a temporary action to study this set of > classes. > >> - Do we really need GetTextExporter2 if you don't have a >> GetTextExporter1? >> - Why is there a #translate:in: if it's empty? > > Yes, cleaning is needed and I need to figure out several aspect of the > framework, as do we need InternalTranslator and the LanguageEditor? I am > tempted to think no. > > > >> The protocol I have in mind for Seaside is something like: >> >> html translate: > > aString translated "return the translating in the current locale." Nope sorry, in a server the current locale in the one of the request or session, not a global variable. Seaside can figure this out automatically which is why I need some layer over gettext. But I also need a way to make the gettext exporter aware of this, basically looking for more selectors. >> html translate:to: > > > NaturalLanguageTranslator > translate: 'This point %1' > toLocaleID: (LocaleID isoLanguage: 'fr') > inDomain: 'DrGeoII' > -> 'Ce point %1' > 'DrGeoII' is the name of the catalog to look for the translation. Which would be the Seaside application name. This can be looked up automatically without a need to repeat yourself every time you want to have a string translated. > Wth this message you also avoid some overhead as your directly specify > the translation catalog. The system does not need to figure out the > catalog to search the translation (done by figuring out from which class > - then class category - the String>>translated message was sent). > > > Your register a domain from classes prefix: > TextDomainManager registerCategoryPrefix: 'DrGeoII' domain: 'DrGeoII'. I would need to hock into that. So that a domain has a "scope" of only several class categories and has a given value there. Is there a way to do this? > Then you export the .po file for translation: > GetTextExporter2 exportTemplate. > > Then you compile your .po translation as .mo and move it in > locale/fr/LC_MESSAGES/DrGeo.mo > > > Some documentation in the PBE2 could be written once stuff is stabilized. > In the Etoys ml, Bert proposed to move the domain in the method > properties to get a more efficient translation look-up > >> What would the way to hook into GetTextExporter(2) to make it pick >> that up? Cheers Philippe

May 6, 2010

[Pharo-project] customizing tab looks in watery2

by Tudor Girba

Hi, I would like to change slightly the default Watery2 theme. For starters, I would like to change the tab widget: - to make it look like a group box - use a smaller font However, I did not figure out how to do that. Could anyone point me in the right direction? Cheers, Doru -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

May 5, 2010