Squeak-dev April 2010

squeak-dev@lists.squeakfoundation.org

122 participants
595 discussions

Right-click on workspace stops functioning
by Igor Stasenko 29 Apr '10

29 Apr '10

Hello, i found a little annoyance. In focused workspace window, press alt-o. I'm not sure what it does, but sometimes, i pressing wrong keys (instead of alt-p, or alt-i) and got my workspace duplicated. It copies a contents of a modified text into a new workspace, while in original one cancels all changes. So, since a copy contains your actual text, i closing the original workspace and happily continuing working in a new one, except one small detail: right clicks in this copy NOT working. So, i can't get a context menu for it and issue my lovely 'debug it' command :) -- Best regards, Igor Stasenko AKA sig.

4 9

World Menu Registry
by Stephan Wessels 28 Apr '10

28 Apr '10

I have published this morning to Squeak Source a package that provides broader menu registry capability to the World Menu. The package is WorldMenuRegistry-sbw.1.mcz. With this package installed into Squeak 4.1, a developer can easily extend, and later on remove if required, menus entries for the following World menus using a registry system: open - Already existed and works with this package without changing existing entries appearance changes project help There is also a unit test which exercises each of these menus and can be perused for examples of menu registry use. The next step is to enhance the new menu/world dock to add registry support. When all of that is working, I'll publish an update to the Desktop Background Screens package that will use the new menu registries dynamically. Cheers, - Steve

12 36

RE: [squeak-dev] SqueakSource indexability (aka should we just ask crawlers to desist?)
by Ken Causey 28 Apr '10

28 Apr '10

> -------- Original Message -------- > Subject: Re: [squeak-dev] SqueakSource indexability (aka should we just > ask crawlers to desist?) > From: Bert Freudenberg <bert(a)freudenbergs.de> > Date: Wed, April 28, 2010 2:59 pm > To: The general-purpose Squeak developers list > <squeak-dev(a)lists.squeakfoundation.org> > > > On 28.04.2010, at 21:07, Ken Causey wrote: > > > > At times access to source.squeak.org becomes slower, as has been the > > case today. I can see in the logs that various web-crawlers are the > > likely culprit. Having the information there accessible via search > > engines is a wornderful thing but I have to suspect that the Seaside > > session IDs eliminate this option. (Of course when URLs like > > http://source.squeak.org/trunk.html are found on other sites they then > > become indexed.) > > Which URLs are the bots accessing? Well, without detailed analysis it seems to be everything. Feel free to look at ~squeaksource/apachelogs/. > > > Unless I'm mistaken about this, and I would appreciate any guidance, it > > seems like we need to add a robots.txt to the site which guides or > > simply asks crawlers to stay away. Thoughts? I'm no SEO export. > > We do have a robots.txt: > http://source.squeak.org/robots.txt Aha. Well, I know little about this subject. But if this means what I think it means it seems that the crawlers are ignoring it. > > - Bert -

3 2

RE: [squeak-dev] SqueakSource indexability (aka should we just ask crawlers to desist?)
by Ken Causey 28 Apr '10

28 Apr '10

1 0

The Inbox: Kernel-fbs.448.mcz
by commits＠source.squeak.org 28 Apr '10

28 Apr '10

A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-fbs.448.mcz ==================== Summary ==================== Name: Kernel-fbs.448 Author: fbs Time: 28 April 2010, 10:30:41.538 pm UUID: f46f80a9-5492-9542-9826-80a936a01df8 Ancestors: Kernel-ul.447 Support for Mantis 7517: a spawned workspace has no context menu. =============== Diff against Kernel-ul.447 =============== Item was changed: ----- Method: StringHolder class>>open (in category 'instance creation') ----- open + ^ (Smalltalk at: #Workspace ifAbsent:[self]) new openLabel: 'Workspace' - (Smalltalk at: #Workspace ifAbsent:[self]) new openLabel: 'Workspace' "Not to be confused with our own class var 'Workspace'"!

1 0

The Inbox: Tools-fbs.236.mcz
by commits＠source.squeak.org 28 Apr '10

28 Apr '10

A new version of Tools was added to project The Inbox: http://source.squeak.org/inbox/Tools-fbs.236.mcz ==================== Summary ==================== Name: Tools-fbs.236 Author: fbs Time: 28 April 2010, 10:31:34.895 pm UUID: c306e740-cfad-aa4b-b620-2c7f159b5e94 Ancestors: Tools-ar.235 Support for Mantis 7517: a spawned workspace has no context menu. (Make the View update when the Model changes.) =============== Diff against Tools-ar.235 =============== Item was added: + ----- Method: Workspace>>contents: (in category 'accessing') ----- + contents: textOrString + super contents: textOrString. + self changed: #contents.!

1 0

The Inbox: ToolBuilder-Morphic-fbs.58.mcz
by commits＠source.squeak.org 28 Apr '10

28 Apr '10

A new version of ToolBuilder-Morphic was added to project The Inbox: http://source.squeak.org/inbox/ToolBuilder-Morphic-fbs.58.mcz ==================== Summary ==================== Name: ToolBuilder-Morphic-fbs.58 Author: fbs Time: 28 April 2010, 10:32:38.987 pm UUID: 5f1f5812-f1d8-824f-8aed-a884428b9fdd Ancestors: ToolBuilder-Morphic-ar.57 Support for Mantis 7517: a spawned workspace has no context menu. Instead of building the Workspace's model by hand, just ask the Workspace to do it itself. =============== Diff against ToolBuilder-Morphic-ar.57 =============== Item was changed: ----- Method: MorphicUIManager>>edit:label:accept: (in category 'ui requests') ----- edit: aText label: labelString accept: anAction "Open an editor on the given string/text" + | window | + window := Workspace open. + window model acceptContents: aText. + window model acceptAction: anAction. + ^window.! - | window holder text | - holder := Workspace new. - holder contents: aText. - holder shouldStyle: false. - text := PluggableTextMorphPlus - on: holder - text: #contents - accept: #acceptContents: - readSelection: nil - menu: nil. - text useDefaultStyler. - text acceptAction: anAction. - window := SystemWindow new. - labelString ifNotNil:[window setLabel: labelString]. - window model: holder . - window addMorph: text frame: (0@0 extent: 1@1). - window openInWorld. - ^window!

1 0

SqueakSource indexability (aka should we just ask crawlers to desist?)
by Ken Causey 28 Apr '10

28 Apr '10

At times access to source.squeak.org becomes slower, as has been the case today. I can see in the logs that various web-crawlers are the likely culprit. Having the information there accessible via search engines is a wornderful thing but I have to suspect that the Seaside session IDs eliminate this option. (Of course when URLs like http://source.squeak.org/trunk.html are found on other sites they then become indexed.) Unless I'm mistaken about this, and I would appreciate any guidance, it seems like we need to add a robots.txt to the site which guides or simply asks crawlers to stay away. Thoughts? I'm no SEO export. Ken

3 2

The Inbox: Sound-wiz.18.mcz
by commits＠source.squeak.org 28 Apr '10

28 Apr '10

A new version of Sound was added to project The Inbox: http://source.squeak.org/inbox/Sound-wiz.18.mcz ==================== Summary ==================== Name: Sound-wiz.18 Author: wiz Time: 28 April 2010, 4:08:23.052 pm UUID: 234c49bf-dace-4b55-83b1-beee75a189de Ancestors: Sound-nice.15 Ok this is a resubmission of String>>sound now names String>>#asSound in compliance with Bert's preference. I have fixed the nits. I have discussed why I believe this is the right word rather than asSound on the mailing list. Squeak-dev 2010. I have not heard back from Bert. He still is in favor of this form over my preference. Authority matters so we are now in compliance. Usage: "'click' asSound play" will play a click sound from the sound library. Any name missing from the sound library will return a default sound to be played. Currently the default is the same as Beeper default. The purpose of the selector is to be a facade to allow access to sounds by name. Currently this only covers the Sampled Sound sound library and the default sound. However, the contract is only that " 'name' asSound " return a playable object. So in the future this could be expanded to check other sound libraries as well before relying on the default. =============== Diff against Sound-nice.15 =============== Item was added: + ----- Method: String>>asSound (in category '*sound-synthesis') ----- + asSound + "Return a sound. Either from the sound library via SampleSound or + else the Beeper default" + ^ SampledSound + soundNamed: self + ifAbsent: [Beeper default]!

1 0

Re: [Pharo-project] [squeak-dev] Re: Menu Registries
by Hannes Hirzel 28 Apr '10

28 Apr '10

On 4/28/10, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > On 28.04.2010 17:47, Brent Pinkney wrote: >> Hi all,+ >> >> Could those in the know comment on how this<...> proposal is (or is not) >> consistent with the fundamental Smalltalk principles >> that: >> >> 1. "an object is send a message and responds with an object" >> 2. there is no other "magic" in the system. >> > Take 15 mins to read the code dealing with Pragma preferences, and you'd > have your answer. > The short answer is no, they just provide a different way of dynamically > deciding what message you want to send. > The closest equivalent would be the logic used to decide which > ImageReadWriter subclass to actually use. > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > Henry I took your piece of advice of using 15 minutes to check out what Pharo pragma/method annotation wise and below is what I discovered. You might want directly to jump to the end for 3 questions --Hannes OK, 15 minutes 1. I open the Pharo 1.0 One-click image and type 'Pragma' in the search browser. (Note: it is not pristine, I have loaded Pier2 into it) 2 .There are five classes which contain 'Pragma'. Only Pragma has a class comment. It is very similar to the one in Squeak 4.1. 3. In this comment I am offered to evaluate a) SystemNavigation default browseAllSelect: [:m| m pragmas notEmpty] and to browse all nonprimitive methods with pragmas evaluate b) SystemNavigation default browseAllSelect: [:m| m primitive isZero and: [m pragmas notEmpty]] a) gives me 971 methods with pragmas in it, b) 219 - these are the ones of interest - the non primitive ones 4) Looking at the 219 pragmas reveals the following examples a) Very frequent ones - they deal with configuration managment <version: '1.0-baseline'> <version: '2.0' imports: #('2.0-baseline')> b) The ones of interest for the current discussion <cleanup> <value: 'children' comment: 'Display immediate children of the current structure.'> <sanitize> <systemsettings> <lint: 'Unnecessary "= true"' rationale: 'Property can be nil I imagine' author: 'stephane.ducasse'> <ignoreForCoverage> 5) I realize that the ones in group 4b) are very few. I have not found any pragma yet related to the menu definition. 6) I decide to go search for 'World' I find the classes TheWorldMenu, TheWorldMenuProvider,TheWorldMenuMainDockingbar which are of interest. They all have class comments which is fine. In addition I find TheWorldMainDockingBar instance openDockingBar which I execute and to my suprise I realize that Pharo has as well a regular menu though with funny cartoon icons. The entries are however not worked out yet and this is probably the reason why it is not activated by default. 7) Looking at the menu construction code of TheWorldMenu and TheWorldMenuMainDockingbar I do not find anything interesting regarding pragmas. All is hard wired. 8) You wrote that you had the pragma discussion one year ago, so I was expecting something more to be in 1.0. Maybe I should have checked out 1.1 alpha? 9) As the 15 minutes are nearly over I start to use the time for some final questions. QUESTIONS A. The fact that you refer me to Google and the Nabble list to find out the result of your pragma discussion has to be read as - there is no such document yet. Is this correct? B. Is there a list of pragmas and how they are supposed to be used? C. How do you want to handle the menus with pragmas? (It seems that Pharo is not much further advanced in this area).

2 1

← Newer
1
...
5
6
7
8
9
10
11
...
60
Older →

Jump to page: