Squeak-dev April 2007

squeak-dev@lists.squeakfoundation.org

151 participants
201 discussions

RE: Package Universe for Squeak 3.9: file for Tric-RefractoringBrowser is no longer there
by Ken Causey 07 Apr '07

07 Apr '07

> -------- Original Message -------- > Subject: Re: Package Universe for Squeak 3.9: file for > Tric-RefractoringBrowser is no longer there > From: Lex Spoon <lex(a)lexspoon.org> > Date: Sat, April 07, 2007 8:15 am > To: squeak-dev(a)lists.squeakfoundation.org > > It would be nice to have a real bug tracker around for this sort of > thing, so that you could post bugs against individual packages, but > nobody has ever set one up. > > > Lex Perhaps I'm misunderstanding. But if you go to http://bugs.squeak.org/ and choose the Squeak Packages project (which can be done from the drop down at the upper right) then you can report a bug and choose the package from the Category list. Admittedly not all packages are listed there. If the one you want to report an issue against is missing, just leave Any as the category, provide enough information in the report so I can figure out which package you mean, and I will fix it. This has been around for years now. Am I in fact misunderstanding what you mean? Ken

1 0

Roadmap proposal for the Squeak Documentation Team in 2007
by Matthew Fulmer 07 Apr '07

07 Apr '07

>From discussions I have had on IRC with Derek O'Connell, Max OrHai, and Paul Bennett, I have decided it is time to propose an official road map for the Squeak Documentation Team for 2007: We are currently in the formative stages, and a clear goal is starting to emerge, along with a path to get there. We would like to see a Squeak where: - Tutorials exist in the main image - All core functionality is documented and up-to-date - The documentation can be viewed and edited both within the image and from a central website - The documentation can be easily maintained indefinitely How can we get there? There are several steps we must take, and they can be done mostly in parallel: - Collect all existing documentation together in one place. -- This is nearly complete. We have assembled a list of nearly all Squeak documentation that exists outside of the image: -- Squeak Tutorials (Links)[1] -- Category Index[2] - Categorize and index all of this documentation. -- We are undertaking this task in the small at Squeak Tutorials[3], where we are concerned only with categorizing and indexing Squeak Tutorials. From there, we will probably use this hierarchy as a basis for our new index. We stand to gain two things from completing this project: --- A strong core Documentation team, willing and capable of facing the larger challenges ahead --- A first-pass at a usable introductory guide to Squeak -- The next step will be to fix the problems listed at Refactoring the Swiki[4], and complete the Documentation Table of Contents[5]. - Implement Magic Book[6], which will allow the Documentation to be kept up-to-date indefinitely. This will draw from the work done by the implementors of Sophie, Pier, SUnit, and perhaps Gjallar - Get permission and republish the documentation in a form suitable for distribution and collaboration -- Paul Bennett has volunteered for this task. - Integrate SUnit tests into the documentation. Thanks to the 3.10 release team, there should be plenty of unit tests by the time we get to this stage. A hyperlinked version of this proposal is on the Doc team home page: http://wiki.squeak.org/squeak/808 With a clear plan and a clear goal, we can eliminate the criticism that Squeak needs better documentation. There are tasks to be done. If this road map seems good to the community, we can start systematically dividing up the tasks and assigning responsibilities. I will divide up the tasks into week-long chunks, so that one can contribute by sacrificing 2 to 10 hours per week. I especially need help from the developers of Sophie, Pier, SUnit, Monticello, and Spoon to evaluate how difficult it will be to: - Create a system for browsing Documentation along side the code - Embed unit tests within documentation so that it can be auto-tested for correctness - Edit from both the image and the web - Distribute this documentation with the image - Distribute such documentation as part of a packages - Edit the documentation locally and commit it to a central (official) image/universe and make it available via the update mechanism (somewhat like a distributed wiki) I know it is late, but tasks 1-4 would make a great Google Summer of Code project. Thank you for reading this proposal, and thanks to all who reminded me how important good documentation really is. You know who you are :) [1] Squeak Tutorials (Links): http://wiki.squeak.org/squeak/792#Links [2] Category Index: http://wiki.squeak.org/squeak/5871 [3] Squeak Tutorials: http://wiki.squeak.org/squeak/792 [4] Refactoring the Swiki: http://wiki.squeak.org/squeak/2352 [5] Documentation Table of Contents: http://wiki.squeak.org/squeak/2983 [6] Magic Book: http://wiki.squeak.org/squeak/3004 -- Matthew Fulmer -- http://mtfulmer.wordpress.com/ Help improve Squeak Documentation: http://wiki.squeak.org/squeak/808

10 15

installing Squeak on linux
by Ralph Boland 07 Apr '07

07 Apr '07

I always have problems installing Squeak on linux and upgrading to Squeak 3.9 from Squeak 3.8 is no different. In fact, so far, this time around I have failed. On the Squeak download page (www.squeak.org/Download) is says to download three files: the virtual machine (done), the image file (done), and the Sources file (I don't see this file anywhere) on this page. (I believe that I can use the 3.8 sources file here but I must need to fetch a changes file somewhere????? Upon downloading the virtual machine file and untaring it I scanned the INSTALL file. It says: " If you don't already have the image/changes files corresponding to version X.Y then you also need to fetch: Squeak-X.Y-image.tar.gz " I don't see this file anywhere. Each previous time I installed Squeak the inisqueak command failed to be installed. I hope at least that this problem is fixed this time around but haven't reached this point yet. Can someone tell me what I am supposed to do now? Thanks. Ralph Boland (Yearning for the day when I can do a confusion free Squeak install)

6 6

Package Universe for Squeak 3.9: file for Tric-RefractoringBrowser is no longer there
by Matthias Berth 07 Apr '07

07 Apr '07

hello, I was just trying to install Tric-RefractoringBrowser through the package universe in the squeak-dev image 95. Entry looks like this: Maintained by: Cees de Groot <cdegroot(a)gmail.com> Downloads from: http://de-1.tric.nl/%7Ecg/mc/Tric-RefractoringBrowser-CdG.7.mcz That URL does not work anymore. The error message is somewhat misleading: can't find EOCD position. I think it would be better to check if that is a zip file up front (first two bytes should be pk?). Cheers Matthias PS. Is there a preferred way of reporting problems with the package universe, or is it OK if I send it to teh whole list?

3 2

problem - very slow "snapshotting methods"
by Cédrick Béler 07 Apr '07

07 Apr '07

Hi all... I just format my PC and now with squeak, I have problem when l encounter the step "snapshotting methods" (when loading a package for instance...). Do you have an idea where it may come from, I'm lost ? Thanks for all Cédrick 7 April 2007 10:41:34 am VM: Win32 - a SmalltalkImage Image: Squeak3.9 [latest update: #7067] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir C:\Documents and Settings\Administrateur\Bureau\DEV\Seaside\seaside2.8 Trusted Dir C:\Documents and Settings\Administrateur\Bureau\DEV\Seaside\seaside2.8\Administrateur Untrusted Dir C:\My Squeak\Administrateur MultiByteFileStream(StandardFileStream)>>register Receiver: MultiByteFileStream: nil Arguments and temporary variables: Receiver's instance variables: MultiByteFileStream(StandardFileStream)>>open:forWrite: Receiver: MultiByteFileStream: nil Arguments and temporary variables: fileName: 'C:\Documents and Settings\Administrateur\Bureau\DEV\Seaside\seaside2...etc... writeMode: false f: 'C:\Documents and Settings\Administrateur\Bureau\DEV\Seaside\seaside2.8\seas...etc... id: a ByteArray(120 1 0 0 208 27 102 4 0 0 0 0 0 0 0 0 155 93 61 0 0 0 0 0 0 0 ...etc... Receiver's instance variables: MultiByteFileStream>>open:forWrite: Receiver: MultiByteFileStream: nil Arguments and temporary variables: fileName: 'C:\Documents and Settings\Administrateur\Bureau\DEV\Seaside\seaside2...etc... writeMode: false result: nil Receiver's instance variables: MultiByteFileStream class(StandardFileStream class)>>readOnlyFileNamed: Receiver: MultiByteFileStream Arguments and temporary variables: fileName: 'C:\Documents and Settings\Administrateur\Bureau\DEV\Seaside\seaside2...etc... fullName: 'C:\Documents and Settings\Administrateur\Bureau\DEV\Seaside\seaside2...etc... f: nil Receiver's instance variables: superclass: StandardFileStream methodDict: a MethodDictionary(#accepts:->a CompiledMethod (238) #ascii->a Comp...etc... format: 152 instanceVariables: #('converter' 'lineEndConvention' 'wantsLineEndConversion') organization: ('accessing' ascii binary converter converter: fileInEncodingName...etc... subclasses: nil name: #MultiByteFileStream classPool: a Dictionary(#Cr->Character cr #CrLf->' ' #Lf->Character lf #LineEn...etc... sharedPools: nil environment: a SystemDictionary(lots of globals) category: #'Multilingual-TextConversion' traitComposition: nil localSelectors: nil --- The full stack --- MultiByteFileStream(StandardFileStream)>>register MultiByteFileStream(StandardFileStream)>>open:forWrite: MultiByteFileStream>>open:forWrite: MultiByteFileStream class(StandardFileStream class)>>readOnlyFileNamed: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MultiByteFileStream(StandardFileStream)>>readOnlyCopy [] in CompiledMethod>>timeStamp {[file readOnlyCopy]} BlockContext>>on:do: CompiledMethod>>timeStamp MethodReference>>timeStamp MCMethodDefinition class>>forMethodReference: MethodReference>>asMethodDefinition [] in MCPackage>>snapshot {[:ea | definitions add: ea asMethodDefinition]} [] in Array(SequenceableCollection)>>do:displayingProgress: {[:each :i | bar value: i. aBlock value: each]} Array(SequenceableCollection)>>withIndexDo: [] in Array(SequenceableCollection)>>do:displayingProgress: {[:bar | self withIndexDo: [:each :i | bar value: i. aBlock value: e...]} [] in ProgressInitiationException>>defaultMorphicAction {[result := workBlock value: progress]} BlockContext>>ensure: ProgressInitiationException>>defaultMorphicAction ProgressInitiationException>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: ProgressInitiationException(Exception)>>signal ProgressInitiationException>>display:at:from:to:during: ProgressInitiationException class>>display:at:from:to:during: ByteString(String)>>displayProgressAt:from:to:during: Array(SequenceableCollection)>>do:displayingProgress: MCPackage>>snapshot MCPackageLoader>>updatePackage:withSnapshot: [] in MCVersionLoader>>load {[:ea | ea canOptimizeLoading ifTrue: [ea patch applyTo: loader] ifFalse:...]} OrderedCollection>>do: MCVersionLoader>>load MCVersionLoader class>>loadVersion: MCVersion>>load [] in MCFileRepositoryInspector(MCVersionInspector)>>load {[self version load]} BlockContext>>ensure: CursorWithMask(Cursor)>>showWhile: MCFileRepositoryInspector(MCVersionInspector)>>load MCFileRepositoryInspector>>load PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction PluggableButtonMorphPlus>>performAction [] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: {[:m | (m containsPoint: evt cursorPoint) ifTrue: [m performAction]]} ...etc...

2 1

PositionnableStream>>back behavior?
by Damien Cassou 06 Apr '07

06 Apr '07

Hi, I don't really understand why #back goes two step backward: stream := ReadStream on: 'abc' copy. stream next. stream next. stream peek. ==> $c stream back. ==> $a If the following character is $c then the previous one should be $b. Don't you think so? Bye -- Damien Cassou

3 4

HttpView2 swiki page
by Giovanni Corriga 05 Apr '07

05 Apr '07

Hi all, I've created a page for Goran's HttpView2 web framework on the Swiki. You may find it here: http://wiki.squeak.org/squeak/HttpView2 . I've moved part of the contents of the old HttpView2 homepage, and will complete the move tomorrow. Ciao, Giovanni

2 1

[ANN] Smalltalk job in Paris
by Bany, Michel 05 Apr '07

05 Apr '07

Pour un de ses clients actif dans le domaine de l'assurance (Paris La Défense) Cincom recherche un développeur Smalltalk pour assurer le développement et la maintenance d'une application VisualWorks, durée minimum un an, pouvant être éventuellement prolongée jusqu'à trois ans. Contact Philippe Valenza mailto:pvalenza@cincom.com

3 4

Web Team March 2007 Report
by karl 05 Apr '07

05 Apr '07

It's been a very quiet month for the Web Team, I can't think of anything to report. Karl

1 0

Doc team March 2007 report
by Matthew Fulmer 05 Apr '07

05 Apr '07

Thanks to the Google Summer of Code initiative and the resulting influx of newbies, there was renewed interest in the documentation team near the end of the month, leading up to a concrete road map based on what others have volunteered for. These ideas have been floating around for some time, and I think it is time we implemented them. This road map was sent to squeak-dev just prior to this report. Other things that happened this month: Aaron Riechow has a series of Squeak screencasts nearly ready for release. I, for one, can't wait to see them. We gained two new members: Max OrHai, who has volunteered to help maintain the Squeak Tutorial List [1]. Paul Bennett has begun to contact previous document authors for the purpose of re-publishing content in a more maintainable and newbie-friendly form I continued evolving the Squeak Tutorial List [1], and finally added a link to it from http://www.squeak.org/Documentation/ Last month, I said I would document ThingLab. This did not happen, as I lost interest in ThingLab due to it being irrelevant for Peek. I encourage everyone to think about how much you would love to completely understand Squeak. With good documentation, this is entirely possible. Please leave comments on the road map proposal; I know your time is limited, but, if I understand what direction the community wants to take Squeak documentation, we can work together to make it possible. By next month, I plan to compile a todo list for the Doc team. This will be detailed enough to allow anyone to make useful contributions to Squeak documentation on a budget of 2-10 hours per week. Small steps are the way to meet a goal. Let's start toward a better, more understandable Squeak. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/ Help improve Squeak Documentation: http://wiki.squeak.org/squeak/808

1 0

Jump to page: