Squeak-dev September 2007

squeak-dev@lists.squeakfoundation.org

150 participants
157 discussions

Start a nNew thread

[ANN] UI Enahncements released
by Gary Chambers 04 Sep '07

04 Sep '07

Available on the development universe under the "User Interface" category.

11 21

FreeType Plus / Mac
by Ramiro Diaz Trepat 04 Sep '07

04 Sep '07

Hello, I have just installed the package FreeType Plus on a Sq 3.10 beta from Damien Cassou. The UI Enhancements look very good and with the FreeType Plus fonts it is also a great UI improvement. But, whenever I set the default text font to some non default font from Squeak, the workspace turns red, with a thin yellow diagonal cross over it and an error pops up as soon as I type anything into it. The workspace is unusable from then on. Context: - This happens only on Mac, same test on windows does not fail. - This happens only with the workspace that you drag from the toolbar flap, if I open a workspace using Alt-k, the problem does not happen. But the workspace that you get with Alt-k does not have Shout in it, this is the only difference that I see between the two.

4 4

Simplest mock objects DSL
by Denis Kudriashov 04 Sep '07

04 Sep '07

Hi, all I released new version of new mock objects framework BehaviorMockup ( http://www.squeaksource.com/BehaviorMockup or cincom public repository). Just see very simplest syntax: [:mockA :mockB | mockA someMessage. mockB someMessage2] should strictly satisfy: [:mockB :mockA :mockC| mockA someMessage willReturn: 'some result'. mockB someMessage2 willReturn: mockC]. First block is tested behavior. Its args is required mock objects for this behavior. Second block is behavior specification. Its args is all mock objects which are needed for modelling real objects behavior. Args in first block must have names which are equal for second block args. In debugger mock objects will have same names. Best regards. Denis

1 0

"Through" button in Debugger
by Denis Kudriashov 04 Sep '07

04 Sep '07

Hi all "Through" button in Debugger does not work correct for expressions like: [:a | a + 2] valueWithArguments: #(4 ). this block is executed. But expression: [:a | a + 2] value: 4. works ok - block will start to debug. I found reason in ContextPart>>doPrimitive: primitiveIndex method: meth receiver: receiver args: argument "Simulate a primitive method whose index is primitiveIndex. The simulated receiver and arguments are given as arguments to this message." | value | <primitive: 19> "Simulation guard" "If successful, push result and return resuming context, else ^ PrimitiveFailToken" (primitiveIndex = 19) ifTrue:[ ToolSet debugContext: self label:'Code simulation error' contents: nil]. (primitiveIndex = 80 and: [receiver isKindOf: ContextPart]) ifTrue: [^self push: ((BlockContext newForMethod: receiver home method) home: receiver home startpc: pc + 2 nargs: (arguments at: 1))]. (primitiveIndex = 81 and: [receiver isMemberOf: BlockContext]) ifTrue: [^receiver pushArgs: arguments from: self]. primitiveIndex = 83 "afr 9/11/1998 19:50" ifTrue: [^ self send: arguments first to: receiver with: arguments allButFirst super: false]. primitiveIndex = 84 "afr 9/11/1998 19:50" ifTrue: [^ self send: arguments first to: receiver with: (arguments at: 2) super: false]. primitiveIndex = 186 ifTrue: [ "closure value" | m | m _ receiver method. arguments size = m numArgs ifFalse: [^ PrimitiveFailToken]. ^ self activateMethod: m withArgs: arguments receiver: receiver class: receiver class]. primitiveIndex = 187 ifTrue: [ "closure valueWithArguments:" | m args | m _ receiver method. args _ arguments first. args size = m numArgs ifFalse: [^ PrimitiveFailToken]. ^ self activateMethod: m withArgs: args receiver: receiver class: receiver class]. primitiveIndex = 188 ifTrue: [ "object withArgs:executeMethod:" | m args | args _ arguments first. m _ arguments second. args size = m numArgs ifFalse: [^ PrimitiveFailToken]. ^ self activateMethod: m withArgs: args receiver: receiver class: receiver class]. arguments size > 6 ifTrue: [^ PrimitiveFailToken]. primitiveIndex = 117 ifTrue:[value _ self tryNamedPrimitiveIn: meth for: receiver withArgs: arguments] ifFalse:[value _ receiver tryPrimitive: primitiveIndex withArgs: arguments]. value == PrimitiveFailToken ifTrue: [^ PrimitiveFailToken] ifFalse: [^ self push: value] It checks primitive index for method under debug and choose how it must be performed. But index 82 (#valueWithArguments primitive) is absent. I try correct method and add new line: (primitiveIndex = 82 and: [receiver isMemberOf: BlockContext]) ifTrue: [^receiver pushArgs: arguments first from: self]. And now debugging by though button works right for expression "[:a | a + 2] valueWithArguments: #(4 )". But maybe it fix kills other part of system. I work in last Squeak.3.9.dev...image

2 2

Getting double semi as sequencer harvested
by Jerome Peace 04 Sep '07

04 Sep '07

Getting double semi as sequencer harvested. Hi All, This thread has gotten long and diverse. It would help if those who are talking about traits branch that topic off to its own thread. I do want to point out that the context of my original post was that it was a cced copy of a note sent to vassili asking for his help in preparing the sequencer for harvesting. Without at least that much effort, the nays have the day by default. Then it is up to finding an amenable release team (or not). I am following thru on this because 1) As Ramon points out in: http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-September/12007… It seems to have Alan Kays blessing. Alan is one of the few certifiable geniuses amoung us. His opinions count with me more than many. If he had wanted squeak to remain static I would have thought no further about it. 2) I am curious to try it. There are several annoyances that it may halt. I long to write: 1 to: 10 ;; collect: [ :each | each square ] ;; explore . on the fly. And yes, squares := ( 1 to: 10 ) collect: [ :each | each square ] . squares explore. is nice too. But choices are nicer. 3) Jason, my modest claim is that it will help me read code more easily. This is a marginal improvement. However, partial progress counts. And marginal improvements count well in evolutionary matters. 4) If it turns out to prove harmful. Reversions are possible. People clever enough to write asPipe can certainly write as-if-pipe-never-existed. Indeed, until a decompiler decides to use the new sequencer it will disappear in decompiled code. ---- on the form double-semi Several people in the pipe thread mentioned this seemed cleanest to them. For me it helps to remind me it is a sequencer similar to semi for cascade. On printout the indenting should provide the clue that semi and double semi are different. The indenting would be different for double semi because it would be different if the syntactic sugar were not there. >From the (some what contrived*) example previously used: nonHermsOlderThanTensMothersNames := lotsOfPeople selecting: [ :each | each age > 10] ;; rejecting: [:each |each sex = #unknown ] ;; collecting: [:each | each mother] ;; selecting: [:each | each notNil] ;; collecting: [:each | each name] ;; asOrderedCollection (It occurs to me between my word processor an the edit non-abilities that come with the mail composer you may not see things in the right fashion. imagine each ;; indented one more tab stop). contrast with PolygonMorph new ; color: Color red ; borderColor: Color black ; borderWidth: 1 . I suspect the flexibility of showing the code in this alternate form will catch on. At least enough to justify my effort and support behind it. That effort is to talk about it a little here; and prepare it for inclusion in an Alpha release image. I ask all of you who have spoken positively to help get this to the doorstep of inclusion. And those of you who have spoken negatively to keep an open mind. Yours in service and curiosity, --Jerome Peace * in practice collecting some of this into temp variables for readability would be good practice. --------- The difference between idiocy and genius is a matter of time. In the end few listen to idiocy. In the beginning few listen to genius. ____________________________________________________________________________________Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/

1 0

Squeak on BlackBerry device
by glpunzi＠lordzealon.com 03 Sep '07

03 Sep '07

Hi all, Probably, for many people, this question will sound stupid, but...for me, is important.. Someone knows if could be possible to get a Squeak image running on BlackBerry devices? Now, blackberry devices has a trackball that works like a mouse (well, some apps like eOffice shows a pointer and use it like this) Yes,blackberry has free web navigation , and a web could be possible for an app, but could be interesting to get "native" apps, more fast.. Cheers and thanks. Enviado desde mi dispositivo inalámbrico BlackBerry®

4 6

Re: Getting double semi as sequencer harvested.
by Ralph Boland 03 Sep '07

03 Sep '07

For those who care, my opinions on this subject: 1) I once proposed the idea of pipes (I don't like the name pipe and didn't use it) so I am obviously biased in favor of pipes and am confident that, once implemented, pipes will gain popular acceptance. Nevertheless, I think it would be irresponsible to just add pipes to Squeak. I suggest, instead, that the next release of Squeak be paired with an experimental version containing pipes that people can play with. The experimental version release will be delayed by the amount of time needed to implement the pipe operator and use it in a few conspicuous places. 2) I am not worried about Squeak becoming too different from other versions of Smalltalk. If the pipe operator is as successful as I expect it to be then the other versions of Smalltalk will eventually adopt it as well. Then this issue will go away. In fact, perhaps this discussion should be occurring with the entire Smalltalk community. 3) I am against the use of ;; as the pipe operator. It will have all the same problems as = vs. == in C. ; and ;; are similar enough to be mistyped and it will be difficult to find the problem once the typo is made. I much prefer :: or even :-:. Beginners may have problems remembering which is which between ; and ;;. 4) I think we need to review the current code in Squeak to find examples where the pipe operator can be used. One should note that this is not simply a matter of finding places where lots of parentheses are used. Often, instead, the coder has avoided using excessing parentheses by introducing temporary variables. Thus, there may be places in the code where: | a b c ... | ... a := expression1. b := a expression2. c := b expression3 can be replaced by: | c ... | ... c := expression1 :-: expression2 :-: expression3. Finding all the places where such code can be cleaned up will not be easy and have to be done gradually once the pipe operator has been accepted. 5) I don't like the 'then' or 'and_then' name for the pipe operator. To me these names sound more appropriate for the cascade operator. How about 'ForwardResult' or 'ForwardResultTo' or just 'ForwardTo' as the name for the operator. Too bad we can't use 'Cascade'. Ralph Boland

1 0

[ANN][Squeak-dev Beta Image] Version sq3.10-7143dev07.09.1
by Damien Cassou 03 Sep '07

03 Sep '07

Hi, I've just uploaded a new squeak-dev beta image based on Squeak3.10-7143 which contains the new UI from Gary Chambers. If the new UI doesn't work well, please let the ui team know. In a few days, you can expect a new release with OmniBrowser changes. Changes in this version: --------------------------- - DynamicProtocols has been updated. You can now drop methods to a dynamic protocol, this will categorize the method as 'as yet unclassified'. Also, the different progress bars have been replaced by just one. - SUnit and SUnitGUI are now the ones of Keith Hodges. - The Universe now points to each SqueakMap entry. Contained packages: ------------------------ This image contains the following packages: AST version 149 AutomaticMethodCategorizer version 0.24 AutomaticMethodCategorizerServices version 0.2 ClassSelectorSets version 1 DynamicProtocols version 0.60 eCompletion version 0.88 eCompletion-Traits version 0.1 eCompletionOmniBrowser version 0.2 Installer version 1.0.130 OmniBrowser version 0.382 OmniBrowser-Full version 0.25 OmniBrowser-Morphic version 0.28 OmniBrowser-Refactory version 0.30 OmniBrowser-Standard version 0.282 OmniBrowser-SUnitIntegration version 0.5 OmniBrowser-TraitsIntegration version 0.1 Refactoring Engine version 37 RoelTyper version 0.60 ScriptManager version 0.6 Shout version 3.15-tween.70 ShoutWorkspace version 1-tween.1 SmaCC runtime version 13 Squeak dev packages version 0.14 SUnit version 0.33 SUnit-improved version 4.0 SUnitGUI-improved version 4.0 ToolBuilder integration for UI Themes version 0.51 UI Themes and Standard Widgets version 0.5 Universes version 36 Universes OmniBrowser version 0.32 YAXO version 9 Updating the image: ------------------------- You are not obliged to download a new image if you don't want. You can always update your image. To upgrade your already existing squeak-dev image: 1) World menu->open...->Package Universe Browser 2) Update list from network 3) Select all upgrades 4) Install selection 5) Execute: 'DEVImageCreator default install' (all windows will be closed) Prepared packages: -------------------------- There are a lot of packages prepared for you in this image. They are not loaded in the image, but they can be easily. - Open Package Universe Browser (world->open...->Package Universe Browser). - Click on "Update list from network" - Wait a few seconds - Select your packages - Install them -- Damien Cassou

1 0

Doc team August Report
by Matthew Fulmer 03 Sep '07

03 Sep '07

For the month of August, I released SqueakSource commit emails. [1] With this patch, I am trying a different approach to Squeak documentation than I have been; I want to help establish simple procedures that result in more useful documentation being generated by the community. The best way to generate documentation is to discuss something, and that is what this patch is all about. Development in an open-source project is often quite isolated, and this is especially true with Squeak. I believe that this patch will lower the barrier to asking questions about the code that makes up Squeak, and questions lead to discussion and answers, which can then be harvested into documentation. Speaking of harvesting documentation, I havn't done much of that this month. [1]: Release announcement for SqueakSource commit emails: http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-August/119637.h… -- Matthew Fulmer -- http://mtfulmer.wordpress.com/ Help improve Squeak Documentation: http://wiki.squeak.org/squeak/808

1 0

Squeak By Example beta one coming soon...
by stephane ducasse 02 Sep '07

02 Sep '07

Hi guys, We announced it at ESUG last week so the information should be in the report of Niall and may be on some blogs around. We will be releasing soon a new book Squeak By Example (beta version) in the coming week. The book is totally free and open-source. We hope that you will like it and that you may want to contribute. http://www.iam.unibe.ch/~scg/SBE/ Stef (Oscar, Andrew, Damien, Damien, Marcus)

4 3

Jump to page: