- Pharo-dev - lists.pharo.org

[Pharo-project] Error when passing file (without full path) at startup
by StÃ©phane Ducasse Jan. 3, 2010

Jan. 3, 2010

Hi Can somebody confirm that he gets the same error than me with the following code expression /Applications/Squeak/Squeak\ 4.2.2beta1U.app/Contents/MacOS/Squeak\ VM\ Opt PharoCore-1.0-10503rc1.1.image test.st where test.st is deadline Beeper beep I get Error: No content to install I also get the same error with PharoCore1.1ALPHA Latest update: #11131 Now if I use /Applications/Squeak/Squeak\ 4.2.2beta1U.app/Contents/MacOS/Squeak\ VM\ Opt PharoCore-1.0-10503rc1.1.image /Users/ducasse/Workspace/FirstCircle/ActiveResearch/Pharo/Pharo/Coral/test.st it is working I thought that the passed argument was resolved using the current directory. John I remember that you change that is it true? Stef

2 3

[Pharo-project] Worth squeak changes
by StÃ©phane Ducasse Jan. 3, 2010

Jan. 3, 2010

Here is a list of features that we should avoid to reinvent/reimplement. If you want to help there is space. Stef > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: January 2, 2010 2:32:10 PM GMT+01:00 > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > Subject: [squeak-dev] Updated trunk image (Squeak3.11-8720-alpha.zip) > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > Folks - > > After a whole batch of changes, I'v put an updated trunk image up at > > http://ftp.squeak.org/trunk/Squeak3.11-8720-alpha.zip > > Loads of great new stuff in there as you can see from the summary of changes below. Since the summary is getting a bit too long for my taste, I'm starting to only include the three most recent updates in email - if you want the full list please download the image and refer to the full summary in the "What's new" window. And if people disagree with this policy I'd be happy to change it again - I'm just trying to cut down on the spam factor a little. So let me know what you think. > > Cheers, > - Andreas > > (for the full history refer to the "What's new" section in the image) > > [------------------------- updated 01/02/10 ---------------------------] > > NanoTraits > ---------- > A new traits implementation has been added. The implementation is significantly smaller and simpler than the old version and can be unloaded and reloaded without loss of information (i.e., traits flattened during unload are restored during traits reloading). To unload traits simply execute: > Trait unloadTraits. > To restore traits load the traits package from the repository at source.squeak.org. > **** already in the bugtracker => TextDiffBuilder > --------------- > A new algorithm for producing text diffs has been added. The algorithm is smaller, faster, and provides better results compared to the previous implementation. > **** we should have a look => Source / Changes Files > > ---------------------- > Sources and changes files are no longer limited to 32MB max size. ExpandedSourceFileArray provides an implementation for source files of arbitrary length, based on the CompiledMethodTrailer changes. > **** already in Pharo => CompiledMethodTrailer > > --------------------- > Handling compiled method trailers for storing source code has been generalized. The new representation deals more explicitly with various forms of encodings (source pointer, temps-only, etc) and has room for future extensions (i.e., retrieval from other sources). > > Future Messages > --------------- > Support for the future/future: keywords has been added. Future messages enable sending messaging at a later point in time. Timed futures allow sending messages a specific number of miliseconds into the future, futures without arguments are executed at the earliest convenience. For example a message like: > > MyMorph>>mouseDown: event > self color: Color red. > (self future: 1000) color: Color white. > > will turn the given morph red and one second later back to white. > > [------------------------- updated 12/12/09 ---------------------------] > > Image Version > ------------- > The new version scheme is now active. The image version number is the sum of all package versions. A stub package "Squeak-Version" has been added to define the "base" number for the version. This image is designated as "Squeak3.11.alpha". > In general we should have a look at ToolBuilder improvements > Morphic > ------- > New window resizers better in tone with the general UI look. A new UserDialogBoxMorph for simple modal inform/confirm dialogs. > **** we should have a look => Files > > ----- > StandardFilestream now performs read-buffering, dramatically speading up some operations like "Object compileAll" (2x improvement) as well as various other operations (scanning change lists etc). > **** we should have a look => Numbers > > ------- > Implementations for Float #predecessor, #successor etc. Update to the compact class indexes of LargePositiveInteger and LargeNegativeInteger for Cog. Additional tests for all of the new features. > > **** already in Pharo => Exceptions > ---------- > OutOfMemory has been added as a standard exception being signaled when an allocation fails, replacing the previous signaling of the low space semaphore. **** we should have a look => > Improved #ensure: performance avoiding remote context manipulation (via #tempAt:put:) in the default case. > > SUnit > ----- > Faster execution by speeding up some low level operations (like allTestSelectors). Fixes for thumbnail creation which would leave open morphs around after some tests. > **** Martin is working on that I imagine => Kernel > > ------ > The default hash for all objects is now a scaled identity has to avoid extreme degradations in speed when using large numbers of objects without explicit hash implementation in Dictionary and Set. > > [------------------------- updated 11/28/09 ---------------------------] > > Menu Bar > -------- > Squeak now has a standard menu bar to make it easier to discover its contents for new users, replacing the World menu as the prime source for launching tools and other activities. > **** from pharo => Compiler > -------- > Support for literal ByteArray syntax has been added. Byte arrays can now be written as #[1 2 3 "..."] instead of #(1 2 3) asByteArray avoiding the need for conversion and a more compact default representation. > > *** in pharo => Numbers > ------- > Some prime related changed: Integer>>isPrime is now a deterministic test, Integer>>isProbablyPrime a probabilistic variant. Intger>>highBit and Integer>>lowBit have been sped up significantly. > *** in pharo => CRLF Handling > > ------------- > CR and LF are now treated interchangeably in rendering. Both cause a line break and both are not displayed. Various line related methods have been updated to deal with both CR and LF. > > Collections > ----------- > Dictionary is no longer a subclass of Set. HashedCollection is the new superclass for both Set and Dictionary. ***Normally in pharo but not sure > Conversion of OrderedCollection and SortedCollection to Arrays has been sped up significantly. > >

1 0

[Pharo-project] Pharo based "Web Velocity"
by Geert Claes Jan. 2, 2010

Jan. 2, 2010

Just wondering if anyone here knows about Cincom's WebVelocity Seaside based web development environment. Are there any open source Pharo alternatives? -- View this message in context: http://n2.nabble.com/Pharo-based-Web-Velocity-tp4240702p4240702.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 4

Re: [Pharo-project] Pharo based "Web Velocity"
by Dale Henrichs Jan. 2, 2010

Jan. 2, 2010

3 3

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols
by David RÃ¶thlisberger Jan. 2, 2010

Jan. 2, 2010

> May be you can contact david probably on holidays to see how we can > make progress? > I know that we can publish in david repository so may be a lot of > the problems are simple glicth. > Having a configuration for O2 would be good. > What I am not sure, David, can you confirm this ? is if what we talk > in our private email a about the O2-Refactory (the problem we still > have) is the same problem we are talking here. Because, in my opinion, > one thing is just to depend and another thing is to depend and override. > If there are overrides, it matters the order and a lot more stuff. > That's why I am asking you :) > > Is it the same? I hope so :) I do not know, I cannot reproduce this bug (1721) in pharo1.0-10502-rc1web09.12.2. You say in the bug report you can reproduce it neither? So what is the problem you get and how can I reproduce it? I see in the attached stack trace from the creator of 1721 that his bug has something to do with dynamic protocols, but I cannot see the cause from the strack trace. I need to know which Pharo version, which browser version and which packages are loaded to reproduce and locate the problem. It might or might not be related to the problem we discussed, I can't tell yet. Cheers, David

4 4

[Pharo-project] Access to RoelTyper
by Mariano Martinez Peck Jan. 2, 2010

Jan. 2, 2010

Hi folks. What do you think about puting global read write to the RoelTyper project in SqueakSource? Can someone do that ? If you don't want, can someone please add me as developer ? I want to move the tests to a separate package as I have just done with OCompletion. This will let people using Metacello configuration to load just the core but also the core and the tests. As it is now, the tests are always! Thanks Mariano

1 0

[Pharo-project] [update 1.0] #10503
by Adrian Lienhard Jan. 2, 2010

Jan. 2, 2010

Issue 1433: ByteSymbol DNU #hasWideCharacterFrom:to: Issue 1638: MNU when Package Browser is opened via Method Finder Issue 1639: VB-Regex upgrade to latest version Issue 1728: FontChooser open leads to an error Issue 1719: After running all tests, mac menus for tools and debug are gone note, the last two are not in 1.1 yet. ___________________ http://www.adrian-lienhard.ch/

1 0

[Pharo-project] Solving the documentation problem. Capturing tacit knowledge. Knowledge reuse.
by Stan Shepherd Jan. 2, 2010

Jan. 2, 2010

Situation ----------- Pharo/Squeak is potentially a very productive development environment. It has not achieved the widespread use in production systems that we feel it deserves. Complication ----------------- The Pharo world relies on a few people with a lot of knowledge. Starting to use Pharo means relying on those people to provide the knowledge they have. The knowledge that is transferred this way is not captured for reuse. Lack of documentation is usually cited by people evaluating Pharo/Squeak for new projects. For example "#addScript: and #addStyle: are actually ment for internal use. It is currently used by the methods WAComponent>>#styles and WAComponent>>#scripts." http://n4.nabble.com/Script-in-head-tag-td98415.html This is not in the comments. It is tacit knowledge. I'm sure you know of similar examples; they are not rare. Resolution ------------- If documentation maintenance were separated from code maintenance, this tacit knowledge could be captured immediately, by the person who requested it. Maintaining documentation then becomes largely a task for the users of the system. Action -------- One possible mechanism would be to place comments in a wiki. For each class, and each method of that class, there would be a corresponding wiki section. Any user could update the comment at any time. The developer/maintainer of that class could revert any inaccurate edits with one click. Incorrect edits would not affect the function of a method, hence no requirements to unit test / integration test. Commits of code would ideally also update the wiki comment section. There is obviously potential for some problems here, but a wiki structure would make it easy to identify/reconcile parallel edits. When a build happens, a process would update the source with latest comments from the wiki. Plan ---- I'd be willing to put some time into a proof of concept, if people agree that it's worthwhile and they would use it. Any thoughts? ...Stan P.S. Other areas that could be maintained this way: Welcome information workspace on download images. Known problems. (Examples of class use) ... -- View this message in context: http://n2.nabble.com/Solving-the-documentation-problem-Capturing-tacit-know… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

9 22

[Pharo-project] where can I see the slices that were removed from inbox?
by Mariano Martinez Peck Jan. 1, 2010

Jan. 1, 2010

I need to load a slice in 1.0 which was integrated in 1.1 and removed from PharoInbox. Where can I find it? thanks mariano

2 2

[Pharo-project] I still don't understand how this work
by Mariano Martinez Peck Jan. 1, 2010

Jan. 1, 2010

I took a clean pharo1.0-10502-rc1dev09.12.2. I open Monticello Browser, and of course, there is no dirty (modified) package. I select the package OB-Standard, then select the repo http://source.wiresong.ca/ob , and click on changes 1) First, I would expect to have no changes with an Image I have just downloaded, without doing nothing and even when Monticello Browser showed me there is no dirty package. But.....this showed me several changes!!!

3 8