December 2013 - Pharo-users

Pharo on Android - is it available?
by PBK Research Dec. 31, 2013

Dec. 31, 2013

I would like to experiment with Pharo on Android - I have just acquired an Android tablet, and I do not want to learn another development language to produce my own simple apps. After a Google search, I have found http://code.google.com/p/squeakvm-tablet/, which says it is available, at least as a beta. The site says that downloads from there are deprecated, and gives a link to https://ci.lille.inria.fr/pharo/job/PharoDroid/ for the download. This link seems to be dead, however. Is there any source of a download of Pharo for Android (on an ARM-designed processor)? And does it make sense to try to develop apps using Pharo (I know about Dr Geo, so I suppose the answer is yes)? Many thanks for help Peter Kenny

1 0

Re: [Pharo-users] have a question for morphic Designer in pharo.
by Stephan Eggermont Dec. 31, 2013

Dec. 31, 2013

When trying to load Designer in Pharo 3.0 I find uncompilable code in Animations: 'updateCurrentValue: aValue self target ifNil: [^ self]. self target perform: (self property, #:) asSymbol with: aValue.'

4 6

Re: [Pharo-users] Is there any fundamental technical barrier to compiling to JVM byte codes?
by Andy Burnett Dec. 30, 2013

Dec. 30, 2013

<<<From: St?phane Ducasse <stephane.ducasse(a)inria.fr> The fun is important. What we want is well designed and powerful libraries that enabled people. For the JVM question: it is a question of resources + the fact that jvm do not really support well some key smalltalk operations. Now I do not understand why people develop their own vm instead of joining forces. Doing in the long term something and finishing a task are the most difficult things. Stef á§ >>> Thank you to everyone for your comments. I am replying to Stephane's email, just as a catch all. I am curious to know more about the limitations in the JVM. My thinking was sparked - in part - by Mark Roos's work on RTalk. I realised, after my post, that he had actually worked the other way around, i.e. I think he built a Digitalk bytecode layer on top of the JVM, rather than compiling to JVM bytecodes. Either way, what I was vaguely wondering about was how difficult it would be to have a 'compile to JVM' option in Pharo. I could probably live - quite happily - developing in 'real' Pharo, and then deploying an app to e.g. Google App Engine, as a compiled Jar. Obviously, it would be much better to retain all the dynamism of a true Smalltalk environment even when the app has been deployed, but it it gave simple hosting, and scaling, it might be a reasonable trade off. I agree with Stephane, it would be great for people to join forces around a vm. Would make like so much easier. Cheers Andy > >

4 3

[ANN] Seaside 3.1 and 3.0.10 release
by Torsten Bergmann Dec. 30, 2013

Dec. 30, 2013

Details here: http://lists.squeakfoundation.org/pipermail/seaside/2013-December/030350.ht…

4 4

Image starts and closes automatically
by Esteban A. Maringolo Dec. 29, 2013

Dec. 29, 2013

Help please! I closed my image with "Save & Quit" and now everytime I try to open it it opens the window but closes immediately. No error or anything else. It is... the image opens, I can see a couple of workspaces. But then quits. I'm using: /pharo-ui myapp.image I also tried to start it using my startup script, and the same thing happens. Any idea? Regards. Esteban A. Maringolo

4 7

Is someone working with Log4s?
by HernÃ¡n Morales Durand Dec. 29, 2013

Dec. 29, 2013

Because there is a missing method (#currentClassAndMethod) and author didn't replied. Maybe I am using it wrong EsLogManager runForever: '[log4s] debugEnabled=''true'' quietMode=''false'' globalLevel=''All'' ;runForever=() ;runForever=''75'', ''7'' dailyRollingFileAppender=''TestDailyRollingFileAppender'', ''root'', ''dallyRollingFileTopOfDay.log'', ''false'', ''All'', '''', ''%-15d [dailyRollingFileAppenderTopOfDay] %-16m'', ''true'', ''topOfDay'' ' Cheers, HernÃ¡n

3 7

Smalltalk Meetup in ZÃ¼rich, January 6th
by jtuchel＠objektfabrik.de Dec. 28, 2013

Dec. 28, 2013

Hi lists, you may already have seen it, but just in case you haven't: we're going to sit down for some Burgers or Pizza and beer and all things Smalltalk at Restaurant Steinfels in ZÃ¼rich[1] on Monday, January 6th, starting at 7pm. So if you are interested in meeting with other Smalltalk developers or to get in touch with old and new friends, this may be your chance. If you'd like to join us, please let me know so that I can reserve a bigger table for the evening. If you want to drop in last minute, please don't hesitate, we're happy to meet you! Joachim [1] http://www.steinfels-zuerich.ch -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

1 0

Re: [Pharo-users] have a question for morphic Designer in pharo.
by Stephan Eggermont Dec. 28, 2013

Dec. 28, 2013

I was successfull in making Designer start in Pharo 3.0 30659, with some help from Tobias Pape. The following changes were needed (compared to what was needed for Pharo 2.0) - floodfill2:at: is gone from Form. I replaced it with a simple fillColor: That it had gone missing was not clear from issue 11570 - outsetBy: is deprecated and replaced by expandBy: in a lot of places - (some symbol or string or something else, #:) asSymbol is replaced by ... asMutator in a lot of places. - TranslucentColor is replaced by Color TextMorph handleInteraction:forEvent: no longer exists, but gives a different problem in Pharo 2 than in 3 just replacing it by handleInteraction: does not work. That makes a mess of the selection in theUiTextLineMorphs in the object inspector. Stephan

3 2

Event handling in TextMorphs
by Stephan Eggermont Dec. 28, 2013

Dec. 28, 2013

handleInteraction:fromEvent: no longer exists in TextMorph in Pharo 3.0. Just replacing it by handleInteraction: doesn't do the right thing. What should I be doing instead? Stephan mouseDown: evt evt yellowButtonPressed ifTrue: [ ^ self yellowButtonActivity: evt shiftPressed]. self grabKeyboard. editor ifNotNil: [:e | self handleInteraction: [e mouseDown: evt] fromEvent: evt].

1 0

Re: [Pharo-users] have a question for morphic Designer in pharo.
by Stephan Eggermont Dec. 27, 2013

Dec. 27, 2013

Peter Yoo wrote: >1. im look monticello now. can look more version now. 28, 30 Interesting. I still cannot see anything newer than .24 in http://www.hpi.uni-potsdam.de/hirschfeld/squeaksource/MetacelloRepository Are you sure that it is exactly the same repository? There is likely to be a different one for designer itself. >2. email to Marcel Taeumel already. but not receive return mail. mabe into spam? Possible, but unlikely. The last days were the worst time of the year to reach someone in Germany. The weeks around christmas (24-26 december) and newyear are family holidays, so it's likely that he doesn't read his mail. He reacted to your stackoverflow post though. >3. latest squeak is cannot use too. squeak 4.1 image(in squeak 4.4 all in one vm) >with morphic designer standard version can use. but class not same(squeak version >and pharo version). im little panic. It should work in the latest squeak image. It is not used enough/doesn't have enough test coverage that all mistakes are immediately noticed, but Marcel fixes bugs that are found. With the quality of issue report you provide the major problem should be his availability/priorities. The next week he's likely to have holidays. >4. im look already. pharo canvas class not same squeak canvas class. >this problem not easy. i try more now. but im newbie user. maybe so hard work. They started as the same, but Pharo has made more radical and drastic clean-ups. Pharo will break existing applications in order to improve things. The advantage is that innovation can be much faster in Pharo, a disadvantage is that applications need to co-evolve. The support for co-evolving is gradually improving, the continuous integration server provided for Pharo contributions gives fast feedback on consequences of changes. Squeak tries to keep compatible with older applications while gradually making everything unloadable. That is a much slower and more difficult approach. Quite a lot of code that was not used was removed. Once in a while we find out that a project uses that code and needs to be reintroduced. Or should be in a separate extension package, or be moved into the using project. The issue you are now running into seems to be the cleaning up of event handling that has taken place in Pharo and not yet or not in the same way in Squeak. A lot of the code deep in the system was very difficult to understand, so yes, this can be difficult work. >5. im look already another UI project(http://uipainter-gsoc.over-blog.com/). >but not handsome(little joke). maybe can then i want use this project. now im trace >another way(for UiItemViewport class. but mouse event is not same to squeak env). Yes, this years GSoC project did not get as far as Marcel's one. And the event handling has changed since Marcel wrote the Designer. Signals was pretty intrusive. UITreeViewPort doesn't seem to correctly set the source of its dragSpec. I tried to change dragDropSpec in UiItemViewPort to dragDropSpec ^ dragDropSpec source: self; yourself That allowed the drag-and-dropping of a lot of the widgets, but created errors where the dragDropSpec was set to nil (Tree widget). Then I looked at where UiItemViewDragDropSpec was used, and found out that the source was not set in UIDesigner initialize. I can do drag and drop of all widgets with self ui widgetList selectionMode: UiViewSingleSelection; dragDropSpec: (UiItemViewDragDropSpec new source: (self ui widgetList); dropEnabled: false; dragTransferType: #widgetClass). So, in all I needed to make the following changes to make the designer work in 20628 after loading development of ConfigurationOfDesigner-mt.24.mcz: UIDesigner>gridForm | form canvas | form := Form extent: 20@20 depth: 32. form floodFill2: (Color gray: 0.98) at: 0@0. canvas := FormCanvas on: form. form pixelValueAt: 0@0 put: (form pixelValueFor: (Color gray: 0.2)). ^ form UIDesigner>initialize super initialize. self ui setupUi: self. self ui prop addPaneSplitters. self selectDefaultModel. self ui centralScroller borderWidth: 0; fillStyle: (BitmapFillStyle fromForm: self gridForm). "BAD: Viewport should not be accessed from the outside." self ui widgetList viewport dragEnabled: true. self ui widgetList selectionMode: UiViewSingleSelection; dragDropSpec: (UiItemViewDragDropSpec new source: (self ui widgetList); dropEnabled: false; dragTransferType: #widgetClass). self ui filterEdit deferEditSignalTime: 300. propertyTable := self ui propertyScroller widget. self connect: self ui filterEdit signal: #textEdited: toSelector: #nameFilter:. self connect: self ui newBtn signal: #clicked: toSelector: #reset. self connect: self ui saveBtn signal: #clicked: toSelector: #save. self connect: self ui openBtn signal: #clicked: toSelector: #load. UIAbstractWidgetModel>initialize super initialize. self updateWidgets. SystemAnnouncer uniqueInstance on: ClassAdded send: #updateWidgets to: self.

1 0