- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: Re: Handle Close Event in Image - necessary for 1.0?
by Torsten Bergmann April 16, 2010

April 16, 2010

Cool, this would also allow us to use newer VM's with "old" 1.0 pharo images. >The in-image close-event that is now generated by default in the Windows >VM has always been a settable entity. In your original announcements you wrote that the old behavior can be influenced by using SHIFT (see [1]), so I did'nt notice that one can also get the old behavior back using the .ini file. Thanks for your post. Next time I will crosspost to vm-dev. Bye Torsten [1] http://lists.squeakfoundation.org/pipermail/vm-dev/2010-March/004142.html -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

Re: [Pharo-project] [squeak-dev] Re: iPhone OS 4 SDK, section 3.3.1
by Igor Stasenko April 16, 2010

April 16, 2010

On 15 April 2010 22:13, stephane ducasse <stephane.ducasse(a)gmail.com> wrote: > Hi andreas > > I think that indeed this is the only possible reaction to Apple stupidity (I'm using a mac since 92 and I feel sick). > ouch.. Luckily, i never used macs. I have been considering to buy a macbook lately, but now, i'd rather buy something else. I letting Apple to live and die w/o me :) > Stef > > On Apr 15, 2010, at 8:59 PM, Andreas Raab wrote: > >> On 4/15/2010 11:50 AM, Juan Vuletich wrote: >>> Andreas Raab wrote: >>>> On 4/8/2010 2:43 PM, Sean Malloy wrote: >>>>> Anyone have any thoughts on this change to the agreement? >>>> >>>> Just in case anyone had any illusions on this: >>>> >>>> http://computinged.wordpress.com/2010/04/15/apple-removes-scratch-from-ipad… >>>> >>>> >>>> Cheers, >>>> - Andreas >>> >>> Oh! How silly then can be! >> >> Indeed. Well, I'm looking forward to a nice Android tablet. >> BTW, we can use some help and you won't even have to sign an NDA: >> >> http://code.google.com/p/squeak-android-vm/ >> >> Cheers, >> Â - Andreas >> > > > -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Fwd: Re: Handle Close Event in Image - necessary for 1.0?
by Andreas Raab April 15, 2010

April 15, 2010

Whoops. Accidentally sent to the wrong list :-) - A. -------- Original Message -------- Subject: Re: Handle Close Event in Image - necessary for 1.0? Date: Thu, 15 Apr 2010 15:56:59 -0700 From: Andreas Raab <andreas.raab(a)gmx.de> To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> Hi - Just as a reminder when you discuss VM stuff, make it a habit to include vm-dev(a)lists.squeakfoundation.org. I don't read the Pharo list regularly (I only checked it today due to the unfortunate Scratch development). This whole issue was entirely unnecessary and could've been solved with one message to vm-dev. Here is why: The in-image close-event that is now generated by default in the Windows VM has always been a settable entity. If you'll compare the 4.0.2 vs. 3.11.8 VMs the only difference in this area is that the preference "EnableAltF4Quit" is now unset by default. To change it, edit your .ini file to have: EnableAltF4Quit = 1 and you will be back to the previous behavior. You can add this trivially to your one-click (or other) setup. In fact, I'd recommend going carefully through the other relevant vm settings and decide how they should be set for your releases. They are documented here: http://squeakvm.org/win32/settings.html So next time, do include vm-dev when you have a vm issue. Thanks for listening, - Andreas On 4/6/2010 3:22 AM, Torsten Bergmann wrote: > I think I've found something that should be fixed > before releasing 1.0 since it is meanwhile a major problem on Windows. > > In "old" Squeak/Pharo you could close the native world window > using the "X" or hit ALT+F4 on Windows and the system > asked you if you really want to close the whole Smalltalk system > using a native dialog which was provided by the VM. > > With the new VM's (4.0.1 and 4.0.2 on Windows, see [1]) the native > "window close event" is now dispatched from the VM into > the image so it could be handled by Smalltalk code. > This is currently not done/handled in Pharo. Only in Squeak so far. > > The recent Squeak trunk/release candidate already handles the > event within the image and now provides an in-image dialog > to ask the user to quit. > > So: in Pharo now NOTHING happens when you try to close the window > using "X", you can only quit using the world menu - which is IMHO really > a show stopper since you cant close using "X" or ALT+F4 (the key combination to close any windows program). > > Two possible options: > > A) we should handle the event now in-image similar to Squeak > by fixing and integration issue 2131 (see [2]), so not only > for 1.1. but also for 1.0 > > B) release and distribute Pharo 1.0 with an old VM< 4.0 > > > BTW: > You can get the old behavior on Windows by additionally using SHIFT, so > SHIFT + ALT + F4 allows to close. > But this is not very convinient, doesnt follow what the typical > Windows user expects and one has to know about it... > > Bye > T. > > [1] http://lists.squeakfoundation.org/pipermail/vm-dev/2010-March/004142.html > [2] http://code.google.com/p/pharo/issues/detail?id=2131 >

1 0

[Pharo-project] starting specific image in one-click Pharo?
by Lawson English April 15, 2010

April 15, 2010

How does one choose to use a different image in Pharo, at least on a Mac? I can't find a preference setting or menu option to load an earlier version, though I can go into the .app directory and manually start a specific image. Also, is there any way of working with different versions of the same package/classes in the same image? In other words, if I want to follow two different development paths, could I "sandbox" versions of package(s) in different projects and automatically switch between them when I switch projects? Or is there some other way of accomplishing this? The most obvious route is to reload or at least choose an image during the startup process, but I don't see how to even do that. Thanks. lawson

3 5

[Pharo-project] Rome and Rome plugin
by StÃ©phane Ducasse April 15, 2010

April 15, 2010

Hi mike and john We started to play with Rome with cyrille. Alain published a version that he started to clean in the Miro repository on squeaksource and we got the following behavior When we tried the car demo with sophie dev it works When we tried the car demo on the latest untable on mac with 4.2.2 it does not work we get a RomePlugin primitive Apparently it works with alain on linux Now if we take the sophie image and execute it with 4.2.2 it works. So do you have any idea how to fix that? Cyrille can you execute Smalltalk listLoadedModules SmalltalkImage listBuiltinModules Stef

4 8

[Pharo-project] Note about the release of Cuis 2.3, Pharo 1.0, Squeak 4.1
by Hannes Hirzel April 15, 2010

April 15, 2010

Hello It is exciting to see the nearly simultaneous release of Cuis 2.3, Pharo 1.0 and Squeak 4.1. This gives a lot of choice and gives signals of being a healthy ecosystem. The advances in the last year have been tremendous. CONGRATULATIONS. It think having different 'distributions' running on the SqueakVM helps to grow as different needs can be more easily met. Regards Hannes Hirzel

1 0

[Pharo-project] ConfigurationOfCitezen
by Schwab,Wilhelm K April 15, 2010

April 15, 2010

Stef, ConfigurationOfCitezen loads Seaside. Is that intentional and likely to continue into the future? Any answer is ok; I am simply trying to get comfortable with Metacello and wondering what to expect. Bill

2 1

Re: [Pharo-project] iPhone OS 4 SDK, section 3.3.1
by Andreas Raab April 15, 2010

April 15, 2010

On 4/15/2010 11:50 AM, Juan Vuletich wrote: > Andreas Raab wrote: >> On 4/8/2010 2:43 PM, Sean Malloy wrote: >>> Anyone have any thoughts on this change to the agreement? >> >> Just in case anyone had any illusions on this: >> >> http://computinged.wordpress.com/2010/04/15/apple-removes-scratch-from-ipad… >> >> >> Cheers, >> - Andreas > > Oh! How silly then can be! Indeed. Well, I'm looking forward to a nice Android tablet. BTW, we can use some help and you won't even have to sign an NDA: http://code.google.com/p/squeak-android-vm/ Cheers, - Andreas

1 0

[Pharo-project] iPhone OS 4 SDK, section 3.3.1
by Sean Malloy April 15, 2010

April 15, 2010

The old version: 3.3.1 â Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. The new version: 3.3.1 â Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited). Anyone have any thoughts on this change to the agreement?

2 1

Re: [Pharo-project] Issue with PRFullTextSearch - WideString
by Lukas Renggli April 15, 2010

April 15, 2010

This is likely a problem of the server adaptor you selected in your seaside setup. Do you use WAKomEncoded in Seaside 2.8 or the UTF-8 codex in Seaside 3? Lukas On 15 April 2010 17:54, Reza RAZAVI <razavi(a)acm.org> wrote: > Hi, > > Congratulations for the release of Pharo 1.0! > > I'd also like to report a confusing issue encountered in following setting: > - VM: Win32 - IX86 - NT - Squeak3.10.2 of '5 June 2008' [latest update: > #7179] > - Image: PharoCore1.0rc1 [Latest update: #10505] > > In the stack traces, I can see the following string 'Ambient Activity > Systems ???????????????? > > However, that string is in reality 'Ambient Activity Systems â Key > Features', which I can re-obtain by copying & pasting the string above to > any other text processor, like Word. But, if I copy & past it into another > editor in Pharo, it shows 'Ambient Activity Systems ? Key Features'. Now > again, if I copy & past this latter string to another editor, it shows the > original one, that is 'Ambient Activity Systems â Key Features'. > > The full stack is copied below. I tried to report this issue via "Mister > Postman" so as you get the full details of the stack, but got a > *ConnectionTimeOut*, raised via SMTPClient >> fetchNextResponse, then > SocketStream nextLine. If more details are needed, please tell me. > > How the above differences could be explained, and could they explain the > "subscript is out of bounds: 8212" error? > Regards, > Reza Razavi > > > --- The full stack --- > ByteArray(Object)>>error: > ByteArray(Object)>>errorSubscriptBounds: > ByteArray(Object)>>at: > WideString(String)>>findSubstring:in:startingAt:matchTable: > WideString(String)>>findString:startingAt:caseSensitive: > WideString(String)>>includesSubstring:caseSensitive: > [] in [] in PRFullTextSearch>>visitStructure: > [] in Set(Collection)>>anySatisfy: > Set>>do: > Set(Collection)>>anySatisfy: > [] in PRFullTextSearch>>visitStructure: > SortedCollection(OrderedCollection)>>do: > MAPriorityContainer(MAContainer)>>do: > PRFullTextSearch>>visitStructure: > PRFullTextSearch(PRVisitor)>>visitCase: > PRFullTextSearch(PRVisitor)>>visitPage: > PRPage>>accept: > PRPage(Object)>>acceptDecorated: > [] in PRPage(PRDecorated)>>acceptDecorated: > PRPage(PRDecorated)>>decorationsDo:ownerDo: > PRPage(PRDecorated)>>acceptDecorated: > PRFullTextSearch(PRVisitor)>>visit: > [] in PRFullTextSearch(PRVisitor)>>visitAll: > Array(SequenceableCollection)>>do: > PRFullTextSearch(PRVisitor)>>visitAll: > PRFullTextSearch>>visitChildren: > PRChildren>>accept: > PRChildren(Object)>>acceptDecorated: > PRFullTextSearch(PRVisitor)>>visit: > [] in PRPage(PRDecorated)>>acceptDecorated: > [] in PRPage(PRDecorated)>>decorationsDo:ownerDo: > Array(SequenceableCollection)>>do: > PRPage(PRDecorated)>>decorationsDo:ownerDo: > PRPage(PRDecorated)>>acceptDecorated: > PRFullTextSearch(PRVisitor)>>visit: > [] in PRFullTextSearch(PRVisitor)>>visitAll: > Array(SequenceableCollection)>>do: > PRFullTextSearch(PRVisitor)>>visitAll: > PRFullTextSearch>>visitChildren: > - - - - - - - - - - - - - - - > - - - - - - - - - - - - - - - - - - > PRChildren>>accept: > PRChildren(Object)>>acceptDecorated: > PRFullTextSearch(PRVisitor)>>visit: > [] in PRPage(PRDecorated)>>acceptDecorated: > [] in PRPage(PRDecorated)>>decorationsDo:ownerDo: > Array(SequenceableCollection)>>do: > PRPage(PRDecorated)>>decorationsDo:ownerDo: > PRPage(PRDecorated)>>acceptDecorated: > PRFullTextSearch(PRVisitor)>>visit: > PRFullTextSearch(PRVisitor)>>start: > PRFullTextSearch>>start: > PRFullTextSearch(PREnumerableVisitor)>>do: > [] in PRFullTextSearch(PREnumerableVisitor)>>collect: > Array class(SequenceableCollection class)>>streamContents: > PRFullTextSearch(PREnumerableVisitor)>>collect: > PRFullTextSearch(PREnumerableVisitor)>>contents > PRAjaxSearchWidget>>findItems > PRAjaxSearchWidget>>unfilteredItems > PRAjaxSearchWidget(PRStructuresWidget)>>items > [] in PRAjaxSearchWidget>>renderItemsOn:for: > BlockClosure>>renderOn: > WARenderCanvas(WARenderer)>>render: > WARenderCanvas(WACanvas)>>render: > [] in WAUnorderedListTag(WATagBrush)>>with: > BlockClosure>>renderOn: > WARenderCanvas(WARenderer)>>render: > WARenderCanvas(WACanvas)>>render: > WARenderCanvas(WACanvas)>>nest: > WAUnorderedListTag(WABrush)>>with: > WAUnorderedListTag(WATagBrush)>>with: > WARenderCanvas(WAHtmlCanvas)>>unorderedList: > PRAjaxSearchWidget>>renderItemsOn:for: > GRUnboundDelayedSend>>valueWithArguments: > [] in SUAutocompleter(PTUpdater)>>processOn:with: > BlockClosure>>renderOn: > WARenderCanvas(WARenderer)>>render: > WARenderCanvas(WACanvas)>>render: > [] in SUAutocompleter(JSObject)>>render:on: > [] in WARenderContext>>document:during: > BlockClosure>>ensure: > WARenderContext>>document:during: > SUAutocompleter(JSObject)>>render:on: > SUAutocompleter(PTUpdater)>>processOn:with: > [] in SUAutocompleter(PTAjax)>>processWith: > WARequestContext>>respond: > SUAutocompleter(PTAjax)>>processWith: > [] in SUAutocompleter>>registerCallbackIn: > BlockClosure>>valueWithPossibleArguments: > JSAjaxCallback>>evaluateWithArgument: > JSAjaxCallback(WACallback)>>evaluateWithFieldValues: > [] in WACallbackRegistry>>handle: > Array(SequenceableCollection)>>do: > WACallbackRegistry>>handle: > [] in [] in WAActionPhaseContinuation>>runCallbacks > BlockClosure>>on:do: > WAActionPhaseContinuation(WARenderLoopContinuation)>>withNotificationHandlerDo: > [] in WAActionPhaseContinuation>>runCallbacks > BlockClosure>>ensure: > WAActionPhaseContinuation>>runCallbacks > WAActionPhaseContinuation>>handleRequest > [] in WAActionPhaseContinuation(WASessionContinuation)>>basicValue > BlockClosure>>on:do: > WAActionPhaseContinuation(WASessionContinuation)>>withUnregisteredHandlerDo: > WAActionPhaseContinuation(WASessionContinuation)>>basicValue > WAActionPhaseContinuation(WASessionContinuation)>>value > WASession>>handleFiltered: > PRContextFilter(WARequestFilter)>>handleFiltered: > [] in PRContextFilter>>handleFiltered: > BlockClosure>>on:do: > PRCurrentContext class>>use:during: > PRContextFilter>>handleFiltered: > WAMutualExclusionFilter(WARequestFilter)>>handleFiltered: > [] in WAMutualExclusionFilter>>handleFiltered: > BlockClosure>>ensure: > [] in WAMutex>>critical: > [] in Semaphore>>critical: > BlockClosure>>ensure: > Semaphore>>critical: > WAMutex>>critical: > WAMutualExclusionFilter>>handleFiltered: > [] in WASession(WARequestHandler)>>handle: > BlockClosure>>on:do: > WACurrentRequestContext class(WADynamicVariable class)>>use:during: > [] in WARequestContext>>push:while: > BlockClosure>>ensure: > WARequestContext>>push:while: > WASession(WARequestHandler)>>handle: > WAApplication(WARegistry)>>dispatch:to: > WAApplication(WARegistry)>>handleKeyed:with: > WAApplication(WARegistry)>>handleFiltered: > WAApplication>>handleFiltered: > WAAuthenticationFilter(WARequestFilter)>>handleFiltered: > WAAuthenticationFilter>>handleFiltered: > WAExceptionFilter(WARequestFilter)>>handleFiltered: > [] in WAExceptionFilter>>handleFiltered: > BlockClosure>>on:do: > WAWalkbackErrorHandler(WAExceptionHandler)>>handleExceptionsDuring: > WAWalkbackErrorHandler class(WAExceptionHandler > class)>>handleExceptionsDuring:context: > WAExceptionFilter>>handleFiltered: > [] in WAApplication(WARequestHandler)>>handle: > BlockClosure>>on:do: > WACurrentRequestContext class(WADynamicVariable class)>>use:during: > [] in WARequestContext>>push:while: > BlockClosure>>ensure: > WARequestContext>>push:while: > WAApplication(WARequestHandler)>>handle: > WADispatcher>>handleFiltered:named: > WADispatcher>>handleFiltered: > [] in WADispatcher(WARequestHandler)>>handle: > BlockClosure>>on:do: > WACurrentRequestContext class(WADynamicVariable class)>>use:during: > [] in WARequestContext>>push:while: > BlockClosure>>ensure: > WARequestContext>>push:while: > WADispatcher(WARequestHandler)>>handle: > WADispatcher>>handleFiltered:named: > WADispatcher>>handleFiltered: > [] in WADispatcher(WARequestHandler)>>handle: > BlockClosure>>on:do: > WACurrentRequestContext class(WADynamicVariable class)>>use:during: > [] in WARequestContext>>push:while: > BlockClosure>>ensure: > WARequestContext>>push:while: > WADispatcher(WARequestHandler)>>handle: > [] in WAComancheAdaptor(WAServerAdaptor)>>handleRequest: > BlockClosure>>on:do: > WAComancheAdaptor(WAServerAdaptor)>>handleRequest: > WAComancheAdaptor(WAServerAdaptor)>>handle: > [] in WAComancheAdaptor(WAServerAdaptor)>>process: > BlockClosure>>ensure: > WAComancheAdaptor(WAServerAdaptor)>>process: > WAComancheAdaptor>>processHttpRequest: > HttpService>>processHttpRequest: > [] in HttpAdaptor>>dispatchRequest: > BlockClosure>>on:do: > HttpService>>handleDispatchErrorsIn: > HttpAdaptor>>dispatchRequest: > [] in [] in HttpAdaptor>>beginConversation > BlockClosure>>on:do: > BlockClosure>>valueWithBindingsContext: > BlockClosure>>valueWithBindings: > BindingsAccessor>>clamp: > [] in HttpAdaptor>>beginConversation > BlockClosure>>ensure: > HttpAdaptor>>beginConversation > HttpAdaptor class>>readAndWriteTo:service: > HttpAdaptor class>>readAndWriteToSocket:service: > HttpService>>serve: > [] in HttpService(TcpService)>>value: > BlockClosure>>on:do: > BlockClosure>>valueWithBindingsContext: > BlockClosure>>valueWithBindings: > BindingsAccessor>>clamp: > [] in BlockClosure>>newProcessWithClampedBindings: > BlockClosure>>on:do: > BlockClosure>>valueWithBindingsContext: > BlockClosure>>valueWithBindings: > [] in BlockClosure>>newProcessWithBindings: > [] in BlockClosure>>newProcess > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch

1 0