Squeak-dev April 2010

squeak-dev@lists.squeakfoundation.org

122 participants
595 discussions

Float storage as Double?
by Lawson English 02 May '10

02 May '10

I've been playing around with the Mandelbrot set and I noticed that the implementation using Float looked somewhat vague. After researching a while, it turns out (corrections welcome) that while Float performs 64-bit FP calculations, only a limited number of decimal places are stored for subsequent calculations. Is there a way around this? I can work up a "fixed" point Complex number simply by writing over the internal ScaledDecimal representation using using z real: (z real) asString , but this is rather a lot of overhead and for precision less than 15ish decimal places, it would be nice to use hardware. Any relatively easy way to do this (store native precision floating point)? is there a faster way to truncate a ScaledDecimal than the above? Lawson

8 22

Squeak All-in-One
by Bert Freudenberg 01 May '10

01 May '10

(resending with proper subject) 29.04.2010, at 01:07, Andreas Raab wrote: > On 4/28/2010 3:38 PM, Igor Stasenko wrote: >> On 29 April 2010 01:05, Ian Trudel<ian.trudel(a)gmail.com> wrote: >>> Squeak is a product but it just happen to be free-of-charge. Having >>> multiple downloads to get Squeak running and going is a major hurdle >>> for newcomers. It will make the curious go away. Curiosity is often >>> not strong enough to be persistent and go through the hurdles. Then it >>> turns in a no sale. >>> >>> It may not be the most practical approach but it's a hell of a good >>> thing to get newcomers. >>> >> >> Indeed. Easy and fast acquaintance is what a one-click images should serve for. >> Everything else is secondary and can be explained/uncovered once you >> hooked in the user. > > Given that everyone seems to agree, can someone take a stab for providing such an installation for 4.1? It'd be easy enough to put up on Squeak.org for first-time users. > > Cheers, > - Andreas Agreed. Let's build it. But Amazon marketing be damned, please don't call it "1-click". Makes me cringe every time. Actually ... I just made one. Only tested on Mac and Linux-i686, but chances are it works on Windows, too: http://ftp.squeak.org/Experiments/Squeak-4.1-All-in-One.zip - Bert -

14 32

[Documentation] Spell checking within Squeak - suggestion of a method
by Hannes Hirzel 01 May '10

01 May '10

On 4/30/10, Ian Trudel <ian.trudel(a)gmail.com> wrote: > 2010/4/30 Casey Ransberger <casey.obrien.r(a)gmail.com>: >> Ian, thanks. Comments inline. > >> I don't know of a spell checker implementation for Squeak. Is there one >> out >> there? If not, can you implement one and then get back to me right away? >> :P > > Neither do I know. > Contrariwise to general word-processing our spell checking needs are simpler. We are writing technical documentation and the number of word forms is more limited (my estimate - something between 3000...5000). This means a simple dictionary of allowed word forms could do the job? How do we get that dictionary? Method 1) We create a Bag of all word forms in the existing comments. The words which are infrequent are candidates for being misspelt. They can be flagged and put into a another collection. Method 2) We paste the list of words obtained from the comments into a regular word processor and run a spell check there. A diff to the original word list gives then the misspelt words. We paste the result back into the Squeak image, Within the Squeak image resides a collection of acceptable word forms (as part of the HelpSystem-Tools). Before accepting a comment this list is consulted. This process has to be repeated for a few versions maybe until we have a comprehensive wordlist. Additional benefit. We limit the number of words used thus making the texts easier to understand and more consistent. The idea here is 'controlled language' - i.e. "Squeak Technical English" :-) --Hannes ------------------------------------------------------------------------------------ http://en.wikipedia.org/wiki/Controlled_language Controlled natural languages (CNLs) are subsets of natural languages, obtained by restricting the grammar and vocabulary in order to reduce or eliminate ambiguity and complexity. Traditionally, controlled languages fall into two major types: those that improve readability for human readers (e.g. non-native speakers), and those that enable reliable automatic semantic analysis of the language. The first type of languages (often called "simplified" or "technical" languages), for example ASD Simplified Technical English, Caterpillar Technical English, IBM's Easy English, are used in the industry to increase the quality of technical documentation, and possibly simplify the (semi-)automatic translation of the documentation. These languages restrict the writer by general rules such as "write short and grammatically simple sentences", "use nouns instead of pronouns", "use determiners", and "use active instead of passive".[1]

2 3

RE: [squeak-dev] [documentation] HelpSystem, revision control, and process
by Ken Causey 01 May '10

01 May '10

I haven't been following the HelpSystem discussion very closely so there is no limit to what I don't know on this subject. That said I would be perfectly happy setting up a HelpSystem repository on source.squeak.org. In general I feel we need to start limiting the contents of the trunk repository to those packages that compose 'core' Squeak and start considering add-ons used to build 'basic' Squeak as separate packages installed into 'core'. I'm assuming that HelpSystem is something we would want to include in a 'basic' image, but not a 'core' image. (Of course a 'core' ZIP might include ready to load optional packages including HelpSystem.) Ken > -------- Original Message -------- > Subject: [squeak-dev] [documentation] HelpSystem, revision control, and > process > From: Casey Ransberger <casey.obrien.r(a)gmail.com> > Date: Fri, April 30, 2010 3:22 pm > To: The general-purpose Squeak developers list > <squeak-dev(a)lists.squeakfoundation.org> > > > Folks, > > I'd like to get a process going around HelpSystem. It doesn't have to be a > perfect process. We can tweak it as we go. > > How do people feel about having help in the Trunk? It'll allow us to > document things right along side of our software development. > > One thing worth noting: we can have our HelpSystem "book" in Trunk without > necessarily having HelpSystem itself in the Trunk; however, if we do it that > way, we run the risk of changes in HelpSystem on SqueakSource making our > help content impossible to load. I think having both in the Trunk is a > really good idea. > > If folks aren't comfortable with having some documentation and HelpSystem in > Trunk, I'd like to propose opening up a 'docs' SS repository on > source.squeak.org. We'd lose the ability to track the evolution of our docs > in the context of the evolution of Squeak, but we'd still have the keys to > the kingdom (license, code, content.) > > I'd rather not go with squeaksource.com, as I'd like to think that our docs > should live with the other things on squeak.org. > > As always, feedback is appreciated. > > -- > Casey Ransberger<hr>

3 3

RE: [squeak-dev] [documentation] HelpSystem, revision control, and process
by Ken Causey 01 May '10

01 May '10

> -------- Original Message -------- > Subject: Re: [squeak-dev] [documentation] HelpSystem, revision control, > and process > From: Ian Trudel <ian.trudel(a)gmail.com> > Date: Fri, April 30, 2010 5:20 pm > To: The general-purpose Squeak developers list > <squeak-dev(a)lists.squeakfoundation.org> > > > Quick question, Ken (and Casey). > > How will the core related documentation will be transfered to the core > image assuming what you wrote will define our process? HelpSystem > includes classes and methods comments. > > Ian. Well, this is exactly why I have that leading sentence. ;) I have no idea how content distribution (which is what I assume you are asking about) is meant to work in HelpSystem. I have to assume from Casey's question that it can be distributed in a mcz. As such it can be retrieved via any method desired and from any location. What triggers loading any particular content? I don't know, is there meant to be a catalog something like SqueakMap or Package Universes? Or is help for a particular package an optional dependency? Clearly, as I stated, I have no end of questions. Ken > 2010/4/30 Ken Causey <ken(a)kencausey.com>: > > I haven't been following the HelpSystem discussion very closely so there > > is no limit to what I don't know on this subject. That said I would be > > perfectly happy setting up a HelpSystem repository on source.squeak.org. > > > > In general I feel we need to start limiting the contents of the trunk > > repository to those packages that compose 'core' Squeak and start > > considering add-ons used to build 'basic' Squeak as separate packages > > installed into 'core'. I'm assuming that HelpSystem is something we > > would want to include in a 'basic' image, but not a 'core' image. (Of > > course a 'core' ZIP might include ready to load optional packages > > including HelpSystem.) > > > > Ken > > > >> -------- Original Message -------- > >> Subject: [squeak-dev] [documentation] HelpSystem, revision control, and > >> process > >> From: Casey Ransberger <casey.obrien.r(a)gmail.com> > >> Date: Fri, April 30, 2010 3:22 pm > >> To: The general-purpose Squeak developers list > >> <squeak-dev(a)lists.squeakfoundation.org> > >> > >> > >> Folks, > >> > >> I'd like to get a process going around HelpSystem. It doesn't have to be a > >> perfect process. We can tweak it as we go. > >> > >> How do people feel about having help in the Trunk? It'll allow us to > >> document things right along side of our software development. > >> > >> One thing worth noting: we can have our HelpSystem "book" in Trunk without > >> necessarily having HelpSystem itself in the Trunk; however, if we do it that > >> way, we run the risk of changes in HelpSystem on SqueakSource making our > >> help content impossible to load. I think having both in the Trunk is a > >> really good idea. > >> > >> If folks aren't comfortable with having some documentation and HelpSystem in > >> Trunk, I'd like to propose opening up a 'docs' SS repository on > >> source.squeak.org. We'd lose the ability to track the evolution of our docs > >> in the context of the evolution of Squeak, but we'd still have the keys to > >> the kingdom (license, code, content.) > >> > >> I'd rather not go with squeaksource.com, as I'd like to think that our docs > >> should live with the other things on squeak.org. > >> > >> As always, feedback is appreciated. > >> > >> -- > >> Casey Ransberger<hr> > > > > > > > > > > -- > http://mecenia.blogspot.com/

4 5

Search bar, or is it?
by Ian Trudel 30 Apr '10

30 Apr '10

Y'all, I hereby demand that we rename the search bar to fun bar! 'Cause it's a lot of fun. :) Ian. -- http://mecenia.blogspot.com/

7 19

[documentation] HelpSystem, revision control, and process
by Casey Ransberger 30 Apr '10

30 Apr '10

Folks, I'd like to get a process going around HelpSystem. It doesn't have to be a perfect process. We can tweak it as we go. How do people feel about having help in the Trunk? It'll allow us to document things right along side of our software development. One thing worth noting: we can have our HelpSystem "book" in Trunk without necessarily having HelpSystem itself in the Trunk; however, if we do it that way, we run the risk of changes in HelpSystem on SqueakSource making our help content impossible to load. I think having both in the Trunk is a really good idea. If folks aren't comfortable with having some documentation and HelpSystem in Trunk, I'd like to propose opening up a 'docs' SS repository on source.squeak.org. We'd lose the ability to track the evolution of our docs in the context of the evolution of Squeak, but we'd still have the keys to the kingdom (license, code, content.) I'd rather not go with squeaksource.com, as I'd like to think that our docs should live with the other things on squeak.org. As always, feedback is appreciated. -- Casey Ransberger

1 0

[Question] ToolBuilder in Squeak 4.1 and Pharo 1.0 compatible?
by Hannes Hirzel 30 Apr '10

30 Apr '10

Hello A question: Art the ToolBuilder in Squeak 4.1 and Pharo 1.0 the same? Or if there is a difference what is the impact of it? Or put the question in another way. If I code an UI using the ToolBuilder in Squeak 4.1 will it run in Pharo? Regards Hannes

8 13

[NativeBoost] New update available
by Igor Stasenko 30 Apr '10

30 Apr '10

Hello all. The main direction of work during last days, were introducing a new function formal specification format. With new format, NativeBoost jumps on a next level of flexibility and much less error prone to use!! Here is the old format: primGetModuleFileName: hModule with: lpFileName with: nSize <primitive: #primitiveNativeCall module: #NativeBoostPlugin> ^ NBFFICallout apiCall: #(DWORD 'GetModuleFileNameA' ("in" HMODULE "out"LPCSTR "in"DWORD) ) module: #Kernel32 options: #( - coerceNilToNull ) and here is new: primGetModuleFileName: hModule with: lpFileName with: nSize <primitive: #primitiveNativeCall module: #NativeBoostPlugin> ^ NBFFICallout apiCall: #( DWORD GetModuleFileName ( HMODULE hModule, LPTSTR lpFilename, DWORD nSize)) module: #Kernel32 options: #( - coerceNilToNull ) A new format matching very closely to C syntax.. so , for most C functions you can just do a copy-paste! Also, see that formal spec includes an argument names. They are not a dummy ones, but instead should match the argument names of method. In that way, the formal spec can check the argument names and also, takes in account their order on ST stack. So, you can push arguments in different order as you specified in smalltalk method. But that's not all. Besides a formal argument names, a new format also accepts constants , instance variables and special variable - self. Here: alloc: numberOfBytes <primitive: #primitiveNativeCall module: #NativeBoostPlugin> ^ NBFFICallout apiCall: #( LPVOID HeapAlloc (self , 0 , SIZE_T numberOfBytes) ) module: #Kernel32 a windoze function takes 3 arguments LPVOID HeapAlloc( HANDLE hHeap, DWORD dwFlags, SIZE_T dwBytes ); but your method takes just one, while other two is 'self' and 0 constant. Instead of just integer literal, you can also use a class variables or pool variables, to make things more convenient and readable: zalloc: numberOfBytes "same as #alloc: but additionally zero-fill the allocated memory" <primitive: #primitiveNativeCall module: #NativeBoostPlugin> ^ NBFFICallout apiCall: #( LPVOID HeapAlloc (self , HEAP_ZERO_MEMORY , SIZE_T numberOfBytes) ) module: #Kernel32 And the last thing, is instance variable access. Point>>nbX <primitive: #primitiveNativeCall module: #NativeBoostPlugin > ^ NBFFICallout cdecl: #( sbyte (long x) ) emitCall: [:gen | gen asm pop: gen asm EAX ] here, primitive reads x ivar of Point instance, as a 'long' C value, but on return, converts it to a signed byte value, so: (127@5) nbX 127 (128@5) nbX -128 (-200@5) nbX 56 (5000@5) nbX -120 P.S. Thanks Henrik for a suggestion to change the format! It is now roxxx! :) -- Best regards, Igor Stasenko AKA sig.

1 0

Daily Commit Log
by commits＠source.squeak.org 30 Apr '10

30 Apr '10

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2010-April/003326.html Name: Tools-hmm.236 Ancestors: Tools-ar.235 Display image files (graphics) in FileList ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003327.html Name: ShoutCore-ul.16 Ancestors: ShoutCore-laza.15 - a few minor performance tweaks ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003328.html Name: ShoutCore-ul.17 Ancestors: ShoutCore-ul.16 - accept symbols as arguments of #primitive: and #primitive:module: pragmas ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003329.html Name: ShoutCore-ul.18 Ancestors: ShoutCore-ul.17 - fix: SHMCClassDefinition should also understand #allowUnderscoreSelectors and #allowUnderscoreAssignments ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003330.html Name: ShoutCore-laza.19 Ancestors: ShoutCore-ul.18 Make Shout display symbols with underscores correctly if allowUnderscoreSelectors is true ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003331.html Name: GraphicsTests-wiz.23 Ancestors: GraphicsTests-ar.22 This adds a test demonstrating that rectangles will change shape when their dimensions are rounded if the origin and corner are in different quadrants. See Mantis 2453 http://bugs.squeak.org/view.php?id=2453 The condition for this to happen occurs anytime a morph with odd extent is rendered by a transformation morph. Yours in curiosity and service, --Jerome Peace ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003332.html Name: ToolBuilder-Morphic-fbs.58 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. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003333.html Name: Kernel-fbs.448 Ancestors: Kernel-ul.447 Support for Mantis 7517: a spawned workspace has no context menu. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003334.html Name: Tools-bf.237 Ancestors: Tools-hmm.236, Tools-fbs.236 merge Tools-fbs.236: Support for Mantis 7517: a spawned workspace has no context menu. (Make the View update when the Model changes.) ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003335.html Name: Sound-wiz.18 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. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003336.html Name: System-bf.323 Ancestors: System-ul.322, System-sbw.320 Merge System-sbw.320: Sets default condition for Annotations Preference to true if undefined. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2010-April/003337.html Name: Tools-bf.238 Ancestors: Tools-bf.237, Tools-fbs.234 merge Tools-fbs.234 M7511: MessageNames uses Browser's better-named Frame creation methods. =============================================

1 0

← Newer
1
2
3
4
5
6
7
...
60
Older →

Jump to page: