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

[Pharo-project] [Slightly OT] Integers smarter than me today
by Schwab,Wilhelm K Feb. 17, 2010

Feb. 17, 2010

Hello all, I am trying to make a recognizer for a communication protocol that has very likely been errantly documented. Such tasks can be difficult enough with good docs, but I'm not even sure what is supposed to be happening, so it is really interesting. One of the things that I **think** is happening, is that 12-bit two's complement data is included at one point in the stream. The bits are spread over a 16 bit word. Let's assume that I can correctly gather the 12 bits together. Could some kind soul suggest how to go from the resulting SmallInteger to the correct signed value? Smalltalk is adding a wrinkle that I am not sure how to handle: should I set the "missing" bits to 1? Out to bit 31? Any pointers/suggestions would be greatly appreciated. Bill

3 4

[Pharo-project] New version of XMLParser
by Alexandre Bergel Feb. 17, 2010

Feb. 17, 2010

Dear List, I incorporated some changes of XMLParser proposed by jaayer(a)zoho.com These changes may break some existing applications. For example, I had to adapt CAnalyzer. ConfigurationOfXMLSupport has now #version102: Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

[Pharo-project] [update 1.1] #11212
by Marcus Denker Feb. 17, 2010

Feb. 17, 2010

11212 ----- - Issue 1962: remove FileDirectory #st and #cs - Issue 1977: fix for MethodFinder - Issue 1976: remove left over Futures code from Compiler - Issue 1975: remove more unsent etoy methods in Morph - Issue 1971: small cleanup of sort: - Issue 1972: clean ResourceCollector, ResourceManager and ResouceLocator (somehow this was not posted...) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] FileSystem question
by stephane ducasse Feb. 17, 2010

Feb. 17, 2010

|working cache| working := FSDiskFilesystem current working. cache := working / 'package-cache'. cache entry cache entry creation. "--> 2010-02-14T10:34:31+00:00" cache entry modification. "--> 2010-02-14T10:34:31+00:00" cache entry size give me access to the file descriptor now I was wondering why we could not have the API of description at the level of FSreference to avoid that navigation code. cache creation. "--> 2010-02-14T10:34:31+00:00" cache modification. "--> 2010-02-14T10:34:31+00:00" cache size I like the way FSFilePluginPrims encapsulate the primitive calls. Stef

4 4

[Pharo-project] About new inspector
by StÃ©phane Ducasse Feb. 17, 2010

Feb. 17, 2010

there is a really nice discussion on supporting (not having an inspector breaking) when browsing proxy. Can you have a look? http://code.google.com/p/pharo/issues/detail?id=1970 "What happens is the inspector asks for "self class allInstVarNames" and then tries to get each value with "self instVarNamed: aName". The problem is, self class allInstVarNames answers the instVars of the future class, but "self instVarNamed: aName" gets passed up to the MIMEDocument by #doesNotUnderstand: and the MIMEDocument throws an error because of course it doesn't have the correct instant vars. The old inspectors weren't as intrusive and worked, these new tools clearly still have some bugs. Since ProtoObject, the superclass for any such proxies doesn't do #instVarNamed:, such code in the inspector will blow up anytime one attempts to inspect any kind of proxy. I would report this as a bug to whoever is maintaining the new inspector tools." So the only way I know to produce the 'bug' is to load the SFuture class he describes in the blogpost I mention above then run the example I posted in step two. If this is the wrong place to report this then let me know and I'll keep looking for the correct place. Delete commentComment 4 by pdebruic, Today (14 hours ago) The default, I think. I haven't changed anything. SystemBrowser default Ctrl-p gives OBSystemBrowserAdaptor Delete commentComment 5 by marcus.denker, Today (11 hours ago) I think the problem is this: -> ProtoObject implements a *minimal* object. This way, Proxies or Futures can use #doesNotUnderstand to implement what they implement. That is, for the example of the Proxy, every message is forwarded to the remote object. -> Now we do not know what exactly you want to forward. Should an inspector inspect the local proxy? Ot the remote object? You decide. Your subclass of ProtoObject copies as many objects from Object as you want. (often all that are needed to inspect the *proxy* vs. the remote object). I think Ramon fine-tuned his implementation for the normal old inspector. Now when you use another one, it uses other methods in addition to the one implemented in the Future --> confusion. Chaos. Bug. But: We can not fix this. this is purely the responsibility of the implementor of the subclass of ProtoObject. So. next action: -> We fix (uhm, remove) the croquet Future code that is just plain confusing. -> We think hard if it's really a problem in the new inspector vs. a missing method on the Future. (and, yes, all this sucks anyway.... we are hard at work to make reflection better and solve all this in a *much* nicer way... but that's research...) Delete commentComment 6 by ramon.leon, Today (10 hours ago) It's not just the Future proxy that'll have problems, it's proxies in general. The way the current inspector is written won't work with any proxy I see in my image, SoapHref, SFuture, MAProxyObject, MADynamicObject, probably the Glorp record proxy, because it assume it can use #instVarNamed: on an instance using values from "anInstance class allInstVarNames" which in the case of *any* proxy won't work unless the proxy implements a version of #instVarNamed:. This is confusing because now the proxy is no longer behaving as a proxy, now reflectively it's answering values for itself rather than the instance being proxied. Another solution would be if the proxy overrode #class to return the class of the proxied instance, but I've always assumed all hell would break loose if you overrode #class, I didn't think it safe to do, and I've not seen any other proxy class do this. Regardless of the ultimate solution, the inspector shouldn't blow up, it should catch the exception and have some default rendering behavior for when it can't inspect an object for some reason. Do you not agree? Delete commentComment 7 by stephane.ducasse, Today (moments ago) Yes I agree. We should contact frederick. I think that the inspector should know that it is browsing a proxy and pay attention.

4 8

[Pharo-project] adding traits programatically
by Esteban Lorenzano Feb. 16, 2010

Feb. 16, 2010

Hi, I'm trying to add/remove traits from a class programatically and I have a problem... What I'm doing is, for instance: NSProxy traitCompostition: TNSLogConsole. and NSProxy traitComposition: TNSLogNone. (as a way to replace logging strategies)... but nothing happens... bah... in the browser the class definition is affected, but the application still works as if none changed... do I need to force a class recompilation after changing trait composition? what I'm doing wrong? Cheers, Esteban

2 1

[Pharo-project] About String empty and others
by StÃ©phane Ducasse Feb. 16, 2010

Feb. 16, 2010

Hi guys chris mueller proposed in squeak to have Exception>>messageText "Return an exception's message text." + ^ messageText ifNil: [ String empty ]! - - ^messageText! - Added Array class>>#empty and String class>>#empty to provide applications with canonicalized instances of these oft-used objects; since they are embedded as literals in the CompiledMethod. =============== Diff against Collections-ar.304 =============== Item was added: + ----- Method: Array class>>empty (in category 'instance creation') ----- + empty + "A canonicalized empty Array instance." + ^ #()! Item was added: + ----- Method: String class>>empty (in category 'instance creation') ----- + empty + "A canonicalized empty String instance." + ^ ''! Item was removed: - ----- Method: String>>asDefaultDecodedString (in category 'converting') ----- - asDefaultDecodedString - - ^ self http://code.google.com/p/pharo/issues/detail?id=1961

4 8

[Pharo-project] ProfStef
by Torsten Bergmann Feb. 16, 2010

Feb. 16, 2010

Hi, I like the "browser" version of ProfStef more than the simple "workspace" based version. Especially since it allows us to provide more tutorials in the dev image just by loading. The tutorial browser could be one access point (accessible from world menu) and is extensible by loading a package with an own tutorial (like Metacello, ...) Unfortunately "ConfigurationOfProfStef" currently only uses the simple workspace version. What's the plan here? A vision for the future: - a generalized help system maybe similar to what we know from Eclipse [1], KDE [2], or Windows [3] - nested tutorials with deeper structure than (currently) one - the ability to use "help" in a tool which opens a specific chapter and show people how to use Monticello, TestRunner, ... - tutorials/help descriptions managed like code (no pointers to outdated wiki pages from Squeak) - an active help system with live code samples and maybe based on a cleaned up Bookmorph? ;) We are already halfway there, arent we? Thx T. [1] http://www.ibm.com/developerworks/cn/linux/opensource/os-echelp/eclipse-hel… [2] http://www.lrz-muenchen.de/services/compute/linux-cluster/intro/khelpcenter… [3] http://www.knopf.com/resources/help/screenshots/winhelp2k.gif -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

4 4

Feb. 16, 2010

Hi guys I had this draft in my drafts for some weeks now and I would like to share that with you. I'm really convinced that we could do a better job to build better tools and process to bring our software to the next level. I would like to have share with you some thoughts and analysis and also request for ideas and code of course :) - Bug tracking we are doing that but can we dream - would be nice to have the stack/image and that we could get back in the bug - scripting code.google.com would be nice too - to publish code - to manipulate script bug entries (any taker of that) - Integration server: we are getting there and I thank all the hudson experimentations. - we should get more of that. - Package Management: Metacello - I would like to have Pharo1.0 certified metacello configs. the ideas is that people can publish in a repositories the configs that they know are working for 1.0, then in another for 1.1.... -> once we have configurations + integration server we should burn servers running and testing -> what/how do we manage results - I would like to manage pharo (core + maintained packages with metacello) as well as pharo-dev - Profiling We got MessageTally (BTW in Squeak 3.xx all the code was in... SystemDictionary) cleaned Now it would be good to have better way to profile applications something like .... :) http://www.bootchart.org/images/bootchart.png - Documentation I hope to get some students to produce a way to script UMLish class diagrams that could be displayed at the level of a package. Package level doc Package class comments overview browser. I think that this is really important to get nice comments, nice instance variables, nice temporary variables. Now we should find a way to make sure that comments are well in sight. Any idea / code? - SmallLint Better UI and process using SmallLint Would be nice to have a sanity package checking process. Will probably come one of these days - Better Unit Test support We should look at Adrian fixes and enhancements Better reporting of tests - Better merging tools Seeing the impact of a delta between two versions on the image for example on that topic From VW mailing-list "1. Please make the engine highly configurable and disjoint from the UI. 2. Please make the UI itself pluggable, extensible, augmentable, etc. 3. To support automated merges, please allow rules for handling unresolved conflicts." I'm sure that there is more. We should get to the next level ;)

8 12

Feb. 16, 2010

Hi guys do you have the same problem than me loading Rio? Gofer new squeaksource: 'Rio'; package: 'File-Kernel'; package: 'File-Base'; load. Any idea where it is coming? Missing FFI? Stef

3 3