- Pharo-dev - lists.pharo.org

[Pharo-project] Dictionary as a Set
by nicolas cellier Dec. 30, 2008

Dec. 30, 2008

Sorry to repost, seems that gmane did not like my first attempt... StÃ©phane Ducasse <stephane.ducasse@...> writes: > > > On Dec 29, 2008, at 12:23 PM, Alexandre Bergel wrote: > > > Dear List, > > > > I was wondering whether I am the only one shocked when I see this: > > > > (Set new add: #b -> 'B'; yourself) includes: #b -> 'B' ====> true > > (Set new add: #b -> 'B'; yourself) includes: 'B' ====> false > > this is correct > > > (Dictionary new add: #b -> 'B'; yourself) includes: #b -> 'B' > > ====> false > > (Dictionary new add: #b -> 'B'; yourself) includes: 'B' ====> true > > we should check the semantics of includes: > > > Dictionary inherits from Set. This means that if Set would have a > > contract, it would break in Dictionary. > > IMO, we should have > > (Dictionary new add: #b -> 'B'; yourself) includes: #b -> 'B' ====> > > true > > (Dictionary new add: #b -> 'B'; yourself) includes: 'B' ====> false > > > > No? > > Dictionary and Set relationship is subclassing so a lot can be strange. > We should fix that in Bloc. > From the st80 origin, Dictionary is a Bag of values. Each value of this Bag is indexed with a unique key. It is a Bag because: a) multiple values can be in the dictionary: (Dictionary new) at: 'one' put: 1; at: 'first' put: 1; yourself. b) values are unordered: | d1 d2 | (d1 := Dictionary new: 3) at: 'one' put: 1; at: 'two' put: 2. (d2 := Dictionary new: 4) at: 'one' put: 1; at: 'two' put: 2. stream := (String new: 64) writeStream. d1 do: [:v | stream print: v; cr]. d2 do: [:v | stream print: v; cr]. stream contents. And as you can see, #do: does apply on values, as would #collect: #select: #reject: #includes: etc... The fact that Dictionary is implemented with Associations could be seen as a private implementation-defined feature. Though, by tradition, associationsDo: has been made a public interface, so as the possibility to directly add an Association. But semantically, Dictionary is not a Set of Associations. Example: (Set new) add: $a->65; add: $a->1; yourself. (Dictionary new) add: $a->65; add: $a->1; yourself. Dictionary could be viewed as a Set of keys. From that POV, it shared enough property with Set to be implemented as a subclass. That's all. I proposed once to detach Set and Dictionary and derive them from a common ancestor just for clarity... Nicolas

3 2

[Pharo-project] About the merging tool and "affordance"
by Simon Denier Dec. 30, 2008

Dec. 30, 2008

Hi all With Stef today, we kept scratching our head about how the new merging tool works. Sure it looks cool, but it is not 100% intuitive. A few suggestions: - above the compare panels, show which version is displayed (or which one is the current, which one is the incoming) - the direction of the arrow left/right, depending on whether we keep the current or the incoming, seems wrong. Inverse it? -- Simon

4 4

[Pharo-project] [ANN] Seaside 2.9 Alpha 2
by Lukas Renggli Dec. 30, 2008

Dec. 30, 2008

Over a month has passed since the last release of Seaside 2.9. We are very pleased to announced Seaside 2.9 Alpha 2 as a next step towards the release of Seaside 2.9. We've mainly worked on two things: (1) closing critical issues that have been collected in the bug tracker, and (2) making different configurations of Seaside a snap to load. 1. Closed Issues ================ - Issue 3: A RESTful configuration editor would be very useful - Issue 87: ColorValue>>hex fixes - Issue 126: review request handler documentation - Issue 165: consider WAPainter refactoring - Issue 193: do we really need #vmStatisticsReportString? - Issue 200: Seaside 2.9 project page on SqueakSource outdated - Issue 206: check weird #value call on block in WADebugErrorHandler - Issue 211: deprecate the scriptcaulous convenience methods on Canvas - Issue 216: RSS Changes demo produces invalid XML - Issue 218: WADispatcherEditor doing a #call: in #initialRequest: - Issue 219: Why does WADecorationTask override #updateStates: ? - Issue 227: #halt should always halt - Issue 228: Move the Swazoo server adapter over to WAServerAdaptor - Issue 234: Source code view is broken after painter refactoring - Issue 240: JSJsonTests are not portable - Issue 241: WANumberPrinter>>#digitsOf:base: uses a Float as an Array index - Issue 242: Using a niladic actionBlock with on:do: in not portable - Issue 245: WAHalo Source View is broken - Issue 246: Anchor callbacks should not accept blocks with one argument - Issue 249: WATree broken in example browser - Issue 250: JQuery Droppable does not seem to work right - Issue 251: Accepting code in the browser opens a deprecation warning in Pharo - Issue 254: Sourceview via halo does not seem to work - Issue 256: Setting the default entry point does not seem to work - Issue 258: Bad XHTML for versionuploader - Issue 259: Request modification to WAPlatformTest>>#testIsResumable ... and uncounted enhancements to the core code and various other optional packages such as JQuery, JQuery-UI, Swazoo Server Adapters, etc. We've further improved portability to other Smalltalk dialects, in this round we mostly focused on VA Smalltalk. 2. The Seaside Builder ====================== We are proud to announce the Seaside Builder, the tool that makes it a snap to load a specific set of Seaside 2.9 packages into any recent Pharo or Squeak image: http://builder.seaside.st The Seaside Builder lets you either select a predefined configuration of Seaside packages or manually choose the packages you need. The builder automatically ensures that all prerequisites are selected and loaded in the right order. For the first time it is possible to conveniently choose between the MIT licensed Comanche or the LGPL licensed Swazoo web server. At the bottom of the page there are two download options available: "Load Script" creates a change-set that can be dragged onto any image causing it to load the selected Seaside packages. There is also the possibility to download a "Monticello Configuration" of the selected packages. In the future more download options might become available. 3. Things to be aware of ======================== First of all, it is important to remember that this is an Alpha release and therefore might not be suited to be used in production. We are however rapidly approaching the beta phase and disruptive changes are unlikely. Some of the core team members are already using Seaside 2.9 in production. You'll find a list of current migration issues at http://seaside.st/documentation/migration/28to29. 4. When things go wrong ======================= If you run into problems or encounter problems, please let us know using the issue tracker at http://code.google.com/p/seaside/issues/list or through the mailing list. We are especially interested into feedback concerning "The Seaside Builder". -- Lukas Renggli http://www.lukas-renggli.ch

1 0

Re: [Pharo-project] focus and moving windows
by Bill Schwab Dec. 30, 2008

Dec. 30, 2008

FWIW, I frequently have had troubles like that with graphical systems that were mixing current cursor position with positions from the events. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> Alexandre.Bergel(a)inria.fr 12/19/2008 12:42 PM >>> Dear List, The cursor position when I grab a window and move it around is not the same than the position where I clicked first. I do not know whether this is clear or not. Sadly, I do not have enough expertise on this to effectively produce a fix. Issue #420 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

4 4

[Pharo-project] FreeType scanning Font folders
by Hilaire Fernandes Dec. 30, 2008

Dec. 30, 2008

Hello all, I am preparing a new istoa public release with latest Pharo. I am only using two fonts and I would like FreeType to only scan the Font folder along the .image. Can someone point me where to look to prevent FreeType scanning the host system folders at start up? Thanks -- http://blog.ofset.org/hilaire

6 8

[Pharo-project] Polymorph sound theme
by Gary Chambers Dec. 30, 2008

Dec. 30, 2008

Any interest in having some concrete sound themes via Polymorph? Default is "no sound" at present. Mostly no examples due to effort required to produce open-source friendly copyright sound clips. Currently supported are window events (open/close/restore-up/restore-down/minimise/maximise) plus specific support for dialog window opening (abort/alert/deny/message/question). FM synthesis is, of course, an option. Sound themes are orthogonal to the ui theme in use. Regards, Gary.

7 7

[Pharo-project] the button of the last watery are gorgeous!
by StÃ©phane Ducasse Dec. 30, 2008

Dec. 30, 2008

It is amazing as a nice look already change a lot. Now I have a question? do you plan to get the buttons (pkgs hier. Smart groups a bit bigger). Stef

2 1

[Pharo-project] On not unnecessarily closing down the language
by Lukas Renggli Dec. 30, 2008

Dec. 30, 2008

Seaside depends on external packages, that we don't have control over. For example there the Swazoo package contains a class-instance variable that is uppercase. Unfortunately Pharo throws a notification (instance variables should begin with a lower case characters) when loading that code. This is awkward, because it makes it impossible to load code automatically and gives us additional work. In my opinion a programming language should be as open as possible, and if possible not restrict the user in any way, even if this is against best practices. Unfortunately many of those restrictions are built into our language that wouldn't be necessary: - class names and class-variable names are enforced to be uppercase - class instance-variable names are enforced to be lowercase - it is not possible to assign a new value to a method argument - variable names are enforced to be unique in all scopes In my opinion the language should be as open as possible. It is the purpose of Code Critics to point out smells, not the task of the compiler to reject code that doesn't follow best practices. I am slightly frustrated trying to work around these restrictions ... Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

17 53

[Pharo-project] Morphic Halos
by Rob Rothwell Dec. 29, 2008

Dec. 29, 2008

So...how do I bring up a Morph's halo in Pharo now? Something between 10196 and 10201 made the Alt-click quit working...! Take care, Rob

2 3

[Pharo-project] Introducing Mars 0.1
by Esteban Lorenzano Dec. 27, 2008

Dec. 27, 2008

Hi, I'm introducing Mars (just another world) Mars is a world for Squeak (and all it's forks) builded as an MVC on top of Cocoa (OSX framework) and OmniBrowser. For that reason, Mars just runs on OSX environments. While this project has some similariries with SqueakGTK and wxSqueak, it has big differences: 1) Mars is not a port of Cocoa for squeak, is just an MVC implementation who uses Cocoa. Why that "subtle" distinction? well, SqueakGTK is a full port of GTK+ library and for that reason, a little big a and a little too complex. I'm following simplicity as one of the project goals. 2) Mars is a plugin, and will run in any fork of squeak, and OB-Mars (Mars world) will run in any fork of squeak who can load OmniBrowser. This is a big difference with wxSqueak, wich is a fork it self (and requires an special VM) And of course, while both efforts (SqueakGTK and wxWidgets) are cool, none of them can be executed (and won't ever be) in small environments, like the iphone, which is one of my main objectives (using John's new VM and Edgar's work on minimal image building) Mars is MIT and can be downloaded following instructions from here: http://www.smallworks.com.ar/productos/Mars/Download For more details (history, blog, etc.), you can go to: http://www.smallworks.com.ar/productos/Mars DISCLAIMER: Right now, Mars is vere-very alpha stage (though it runs and can be used) and I would love any contribution in the form of: bug reports (there will be a lot now), feature requests, comments, and of course, code :) Cheers, Esteban -- "Querer es suscitar las paradojas" Camus. El mÃto de SÃsifo.

5 11