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

Re: [Pharo-project] Flaw in SocketStream>>peek detected
by Igor Stasenko Jan. 13, 2010

Jan. 13, 2010

http://bugs.squeak.org/view.php?id=7446 -- Best regards, Igor Stasenko AKA sig.

2 1

[Pharo-project] [update 1.1] #11156
by StÃ©phane Ducasse Jan. 13, 2010

Jan. 13, 2010

11156 ----- - Issue 1811: FreeType fix for better integration of Rome Tx Mike :) - Issue 1151: RFC2047MimeConverter>>#readWord is broken, and this may be part of a larger issue tx Peter :) (it was not marked as fixed nor 1.1 so skipped our radar) - Issue 1751: allPairsDo: aBinaryBlock self do: [:first| self do: [:second| aBinaryBlock value: first value: second]] - Issue 1769: TestRunner author while running tests so we will have popup menu problems and in such case should fix the tests ;) Stef

1 0

[Pharo-project] [update 1.1] #11155
by StÃ©phane Ducasse Jan. 13, 2010

Jan. 13, 2010

11155 ----- - Issue 1805: Bitmap fonts need reinitialization StrikeFont installDejaVu - Merged CompilerTests.lr.17.mcz merged Compiler-cwp.73.mcz from Colin "The compiler now uses notifications to signal that a correctable error has been found in the method source, rather than interacting directly with the user." - Issue 332: Arithmetic protocol should be removed from Collections and Strings I took the decision to remove the arithmetic protocol from collections and if people want it back we still can but if was not really complete and well done. Stef

1 0

[Pharo-project] I cannot believe that Browser is relying on Object>>initialExtent
by StÃ©phane Ducasse Jan. 13, 2010

Jan. 13, 2010

argh....... May be not putting everything in Object would help. Stef

5 10

Re: [Pharo-project] Comments on Metacello and ConfigurationOfExternalWebBrowser
by Dale Henrichs Jan. 13, 2010

Jan. 13, 2010

----- "Torsten Bergmann" <astares(a)gmx.de> wrote: | >And the other thing is that you put everything under spec for: | #common | | Depends on the meaning of common (only Pharo and other Squeak | Distributions) or does it include other Smalltalks (VW, VAST) too? | If Metacello gets ported then you are right. | | The tutorial only says: | "In addition to #common, there are pre-defined attributes for each of | the | platforms upon which Metacello runs (#pharo, #squeak, #gemstone and | #squeakCommon)." | | However FFI (which is definitely limited to Squeak derivates) | is also #common and I used it as a template. | | Maybe #squeakCommon is right for FFI and ExternalWebBrowser | since this is what is used in the seaside, swazoo, ... configs. Torsten, My opinion on the platform attributes (#pharo, #squeak, #gemstone and #squeakCommon) is that attribute should reflect intention. If the code that is being configured is intended to run on all platforms, then using the #common attribute is fine. In the MetacelloRepository, the primary motivation for the configurations is to specify the packages and versions that are to be loaded into the Pharo environment and reflects the decisions made by the Pharo developers. Therefore, it makes a lot of sense to use the #pharo platform for those configurations, because the target environment for the configuration _is_ Pharo. The ConfigigurationOfOmniBrowser is an interesting example. OmniBrowser runs on GemStone, Pharo and Squeak, but the choice of which specific packages to load is likely to be different for each platform (for a variety of reasons). So I don't think there is an absolutely right answer to the question. Besides, even though code is intended to run on all three platforms, over time changes may be made that make in non-portable to one or more platforms, so even with the best intentions... Much like the underlying code base, if the configuration is actively used and maintained, each configuration will eventually find a steady state answer that works. Dale

1 0

Re: [Pharo-project] [Metacello] Re: Comments on Metacello and ConfigurationOfExternalWebBrowser
by Dale Henrichs Jan. 13, 2010

Jan. 13, 2010

Torsten, Thanks for the feedback! It is much appreciated. I've interspersed comments below. ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | On Wed, Jan 13, 2010 at 2:41 PM, Torsten Bergmann <astares(a)gmx.de> | wrote: | | > Played with Metacello: | > | | First, there is a Metacello mailing list, which I think would be more | accurated that this one. The groups is: | http://groups.google.com/group/metacello | | | > 1. there are various typos in the lessons of the tutorial | > (looks like it was really written in a hurry) | > | > | They are doing an excellent work. You cannot ask more. In addition, | if you | saw the typos, an if it was even versioned code, why didn't you fix | them and | commit ? I appreciate the feedback. I am not a professional writer, but basic documentation is required for Metacello, so I have been doing my best. The best way to deal with issues that you find in the code (including the tutorial) is to submit a bug report (http://code.google.com/p/metacello/issues/entry) If you are motivated to work on Metacello, let me know and I will add you as a developer to the repository as well as add you to the Metacello code project (http://code.google.com/p/metacello/) | | | | > 2. there are two special groups introduced in lesson10 | > "default" and "ALL" - why in a different case? | > | > | I don't know. If you read through earlier Metacello communication, you will find that I have admitted that I am poor at naming things (I am not a professional namer either:). For the most part I have listened to and changed things based on feedback. With that said, I have no good reason for the difference. They are two special strings. I prefer bug reports for issues that you deem important, then I won't lose track of them and will be able to address them in due time. | | | > 3. if these are special then it would be nice to | > have | > | > (MetacelloTutorialConfig project version: '1.0') loadAll. | > (MetacelloTutorialConfig project version: '1.0') loadDefault. | > | > | +1 I think I already told this to Dale at my beginning with | Metacello. #loadDefault is already handled. When you send #load to a version, the 'default' group is loaded (if defined), otherwise all of the packages are loaded. I've been holding off adding too many helper methods, not because they aren't useful, but because Metacello is still fairly new. With the Loader in the pipeline, it may turn out that normal users will never have to send messages directly to the configuration...over time if the usage patterns demand helper methods I will definitely add them. | | | > 4. lesson11Author | > Is the author the initials or the full name? | > | > | Which is the difference between Author and Full name ? Don't put | initials. This part of the code was developed while initials were still used on all three platforms (gemstone, pharo and squeak). Pharo has moved to Full Name and on Pharo, the Full name is used ... I happen to do my development with the full name set to my initials so I understand the confusion (see Issue 44: http://code.google.com/p/metacello/issues/detail?id=44) | | | > In Java's Maven POM (Project Object Model, an XML style | > with project infos) one can specify full developer | > informations, which is good when working in a large team: | > http://maven.apache.org/pom.html#Developers | > That is a very good point. The first order priority for Metacello is to take of the functionality first, if it doesn't do the primary job, then it doesn't matter whether the important, but secondary information is included. I agree that there is a lot of useful information that can be added to the project specs and over time it will be added. Dale

1 0

[Pharo-project] Comments on Metacello and ConfigurationOfExternalWebBrowser
by Torsten Bergmann Jan. 13, 2010

Jan. 13, 2010

>Come on!!! That's not an excuse Yes it is - maybe there is already a better or fixed version in a private repo of dale or the tutorial is not maintained anymore since according to http://code.google.com/p/metacello/wiki/Tutorial there is a real tutorial in preparation. Who knows without asking... >#commonSqueak or something like that , which is for pharo and squeak (but >not gemstone) It's called "squeakCommon" and I have no idea if "gemstone" means the pharo based gemstone image or the server. Anything I see is that FFI config also uses #common and developers for it are Esteban, you and Dale. So you should know ;) However - what if Metacello gets ported. Do we have an "commercialSmalltalksCommon", "vastAndVW", ... or any other combination or do we have to maintain a spec for any each platform. Would'nt it be better to have a spec and tell on which (multiple) targets it is able to run. Questions over Questions ... Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

4 4

[Pharo-project] Comments on Metacello and ConfigurationOfExternalWebBrowser
by Torsten Bergmann Jan. 13, 2010

Jan. 13, 2010

FFI now has squeakCommon and external web browser has #pharo For further changes the repo is open ;) Bye T. -- Preisknaller: GMX DSL Flatrate fÃ¼r nur 16,99 Euro/mtl.! http://portal.gmx.net/de/go/dsl02

1 0

[Pharo-project] Issue 1807: Preferences color picker becomes uncontrollable.
by Stan Shepherd Jan. 13, 2010

Jan. 13, 2010

Dev 10505 Ubuntu 9.04 and Xubuntu 9.10 system preference preference browser window colors click a color opens a preference browser, that is uncontrollable. (enter and/or escape) regains control ...Stan -- View this message in context: http://n2.nabble.com/Issue-1807-Preferences-color-picker-becomes-uncontroll… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 2

[Pharo-project] Comments on Metacello and ConfigurationOfExternalWebBrowser
by Torsten Bergmann Jan. 13, 2010

Jan. 13, 2010

>They are doing an excellent work +1 >if you saw the typos, an if it was even versioned code, why didn't you >fix them and commit ? It's in package "Metacello-Tutorial" and the repo http://seaside.gemstone.com/ss/metacello is READ only >Don't put initials. But the examples in the lesson use initials "dkh". Thats why I asked and recommended more infos (name, initials, contact) like in Java Maven POM's. >I have two erros Dont know about your image, config and changes - I just tried in a clean udated core image #10506 >you are using for FFI '1.0-baseline' Thats by intention since I dont think there will be another baseline and I want the latest. But since I use it with transitive dependency in a release version of ExternalWebBrowser you are right. It's fixed now. >And the other thing is that you put everything under spec for: #common Depends on the meaning of common (only Pharo and other Squeak Distributions) or does it include other Smalltalks (VW, VAST) too? If Metacello gets ported then you are right. The tutorial only says: "In addition to #common, there are pre-defined attributes for each of the platforms upon which Metacello runs (#pharo, #squeak, #gemstone and #squeakCommon)." However FFI (which is definitely limited to Squeak derivates) is also #common and I used it as a template. Maybe #squeakCommon is right for FFI and ExternalWebBrowser since this is what is used in the seaside, swazoo, ... configs. Bye T. -- Preisknaller: GMX DSL Flatrate fÃ¼r nur 16,99 Euro/mtl.! http://portal.gmx.net/de/go/dsl02

2 1