- Pharo-users - lists.pharo.org

Re: [Pharo-users] Scrolling in a Morphic game

by Tudor Girba

I am interested, too :) Perhaps you want to take a look at the ScrollPane or GeneralScrollPane implementation. Cheers, Doru On 26 Jan 2011, at 10:28, Benjamin wrote: > I do not know if an API exist for this kind of stuff, but it could be really cool to add one ^^ > > I think that you should basically add a drawing method which take a rectangle as a parameter and display this rectangle from your original world's representation. > For scrolling, just adjust the rectangle. > > I'm really interested in this kind of work, so let me know how your work progress :) > > Good luck, > Ben > > On Jan 26, 2011, at 2:11 AM, Aidan Gauland wrote: > >> Hello, >> >> I am developing a game in Morphic -- nothing serious; just a spare >> time project -- and I have come to a tricky part: the viewport. So >> far, I have just put my Morphs in a PasteUpMorph for testing, but now >> I need to have a viewport to a (game) world that is larger than the >> screen, and be able to pan/scroll the view around the world. I really >> have no idea how I could or should do this in Morphic. Maybe subclass >> PasteUpMorph and override #drawSubmorphs? Can anyone here offer any >> advice with this? >> >> Regards, >> Aidan > > -- www.tudorgirba.com "When people care, great things can happen."

Jan. 26, 2011

Re: [Pharo-users] Scrolling in a Morphic game

by Benjamin

I do not know if an API exist for this kind of stuff, but it could be really cool to add one ^^ I think that you should basically add a drawing method which take a rectangle as a parameter and display this rectangle from your original world's representation. For scrolling, just adjust the rectangle. I'm really interested in this kind of work, so let me know how your work progress :) Good luck, Ben On Jan 26, 2011, at 2:11 AM, Aidan Gauland wrote: > Hello, > > I am developing a game in Morphic -- nothing serious; just a spare > time project -- and I have come to a tricky part: the viewport. So > far, I have just put my Morphs in a PasteUpMorph for testing, but now > I need to have a viewport to a (game) world that is larger than the > screen, and be able to pan/scroll the view around the world. I really > have no idea how I could or should do this in Morphic. Maybe subclass > PasteUpMorph and override #drawSubmorphs? Can anyone here offer any > advice with this? > > Regards, > Aidan

Jan. 26, 2011

TestMock v-9 published; now works with Pharo 1.1.1

by Anindya Haldar

Dear Smalltalkers, I am glad to make an updated version (v9) of the mocking framework TestMock available with added Pharo 1.1.1 support. Previously reported v8 issues arising from the deprecation of KeyedSet and some other changes with TestCase and Boolean classes in Pharo 1.1.1 have been fixed. This version continues to work with Pharo 1.0 and Seaside-2.8 dev images as before. Here is the link to the project: http://www.squeaksource.com/TestMock.html Happy smalltalking! Regards, - Anindya Haldar

Jan. 26, 2011

Scrolling in a Morphic game

by Aidan Gauland

Hello, I am developing a game in Morphic -- nothing serious; just a spare time project -- and I have come to a tricky part: the viewport. So far, I have just put my Morphs in a PasteUpMorph for testing, but now I need to have a viewport to a (game) world that is larger than the screen, and be able to pan/scroll the view around the world. I really have no idea how I could or should do this in Morphic. Maybe subclass PasteUpMorph and override #drawSubmorphs? Can anyone here offer any advice with this? Regards, Aidan

Jan. 26, 2011

Re: [Pharo-users] Minimal pharo

by Mariano Martinez Peck

On Mon, Jan 10, 2011 at 11:07 AM, Annick Fron <info(a)afceurope.com> wrote: > Hi, > > I have tried the minimal pharo, yet on Linux it opens a blank window. How > is it possible to get rid of it ? > Did you manage you make it work? if true, let us know how. > Annick > Le 5 janv. 2011 Ã 09:16, Luc Fabresse a Ã©crit : > > Hi all, > > Yes, I agree with Adrian, all cleanings should be integrated. > Perhaps in #cleanUpForProduction that already integrates some elements > pointed by Mariano. > > #Luc > > > 2011/1/5 Adrian Lienhard <adi(a)netstyle.ch> > >> >> On Jan 4, 2011, at 22:42 , Mariano Martinez Peck wrote: >> >> > ps: I wonder if any of those scripts should be added to ScriptLoader >> >> Yes, that would be good! Like this we can improve them and other people >> can contribute. >> >> Esteban, could you share your experience with unloading packages? I assume >> you had to also reorganize packages to make them cleanly unloadable? If yes >> these changes should be integrated to improve the modularization. >> >> Cheers, >> Adrian >> > > >

Jan. 26, 2011

Re: [Pharo-users] Polymorph example

by laurent laffont

I've written a post on the subject: http://magaloma.blogspot.com/2011/01/pharo-gui-with-polymorph.html Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ On Mon, Jan 24, 2011 at 1:45 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Thank you very much Gary > > Laurent > > > On Mon, Jan 24, 2011 at 12:48 PM, Gary Chambers <gazzaguru2(a)btinternet.com > > wrote: > >> Hi, >> >> just a few observations ;-) >> >> The openModal might be better like this (so the text fields align nicely): >> >> openModal >> |builder dialog content firstName| >> >> builder := UITheme builder. >> content := (builder newLabelGroup: { >> 'First name' -> (firstName := (builder >> newTextEntryFor: contact getText: #firstName setText: #firstName: help: >> 'Enter the first name of the contact') >> acceptOnCR: false; >> minWidth: 200). >> 'Last name' -> ((builder >> newTextEntryFor: contact getText: #lastName setText: #lastName: help: >> 'Enter the last name of the contact') >> acceptOnCR: false; >> minWidth: 200). >> }). >> >> dialog := builder newPluggableDialogWindow:'Edit contact' for: content. >> dialog rememberKeyboardFocus: firstName. >> builder openModal: dialog. >> >> dialog cancelled ifFalse: [self doOnOK]. >> >> >> The #useDefaultOKButton was redundant (since model was set before sending >> (the #for: bit)). >> Resetting the model after chosing the buttons would work though. That's >> why you get the default >> OK/Cancel (rather than the single OK you would have had via >> #useDefaultOKButton). >> Disabling the acceptOnCR for each text frield allows the default dialog >> handling for the return key (defaults to OK). >> Normally the initial keyboard focus for a dialog is the default button, if >> specified. Remembering the first name field >> prior to opening will give that field focus. >> >> >> It might be nice to use the enablement feature for the buttons on the main >> contact list: >> >> >> contactSelectedIndex >> ^ selectedContactIndex ifNil: [selectedContactIndex := 0] >> >> >> >> contactSelectedIndex: aSmallInteger >> >> selectedContactIndex := aSmallInteger. >> self >> changed: #contactSelectedIndex; >> changed: #hasSelectedContact >> >> >> >> hasSelectedContact >> >> ^selectedContactIndex > 0 >> >> >> addButtonClick >> |newContact| >> newContact := Contact new. >> >> ContactEditor new >> contact: newContact; >> onOK: [ Contact database add: newContact. >> self changed: #contacts. >> self contactSelectedIndex: Contact database size ]; >> openModal >> >> >> removeButtonClick >> >> [Contact database removeAt: selectedContactIndex] >> on: Error >> do: [UITheme builder alert: 'Cannot remove selected contact.']. >> self >> contactSelectedIndex: (self contactSelectedIndex min: Contact database >> size); >> changed: #contacts >> >> >> >> open >> |builder content| >> builder := UITheme builder. >> content := builder newColumn: { >> builder >> newListFor: self >> list: #contacts >> selected: #contactSelectedIndex >> changeSelected: #contactSelectedIndex: >> help: 'contacts'. >> builder newRow: { >> builder newButtonFor: self action: #addButtonClick label: 'Add' help: >> 'Create a new contact'. >> builder newButtonFor: self action: #removeButtonClick getEnabled: >> #hasSelectedContact label: 'Remove' help: 'Remove selected contact'. >> builder newButtonFor: self action: #editButtonClick getEnabled: >> #hasSelectedContact label: 'Edit' help: 'Edit selected contact' }}. >> >> (content openInWindowLabeled: 'Contacts') extent: 400@500. >> >> >> >> >> Nice example. Good luck. >> >> Regards, Gary >> >> ----- Original Message ----- >> *From:* laurent laffont <laurent.laffont(a)gmail.com> >> *To:* A friendly place where any question about pharo is welcome<pharo-users(a)lists.gforge.inria.fr> >> *Cc:* gazzaguru2(a)btinternet.com >> *Sent:* Sunday, January 23, 2011 1:39 PM >> *Subject:* Polymorph example >> >> Hi, >> >> I've written a tiny little application to prepare a screencast on >> Polymorph / GUI. As I'm far from being expert on this, can someone check >> that it is done "the right way" (especially on how to manage OK/Cancel ) ? >> >> Gofer it >> squeaksource: 'LaurentLSandbox'; >> package: 'AddressBook'; >> load. >> (Smalltalk at:#ContactListEditor) open. >> >> >> Thanks. >> >> >> Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ >> >> >

Jan. 26, 2011

Re: [Pharo-users] Multiple Worlds for Pharo *stable*

by Igor Stasenko

On 24 January 2011 22:33, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > It is on my todo to have a look but quite busy right now > Keep improving the systems. > Hehe.. especially if remember that you cut this out once. Ironically, it went back , behind your spine :) > Stef > -- Best regards, Igor Stasenko AKA sig.

Jan. 25, 2011

Re: [Pharo-users] Multiple Worlds for Pharo *stable*

by Aidan Gauland

On Tue, Jan 25, 2011 at 03:53:36PM +1300, Aidan Gauland wrote: > If anyone wants to have the same background in their other worlds as > the first one, this should do it... > > wm := WorldManager instance. > bgm := (wm worldNamed: 'Pharo') backgroundMorph. > (wm worldNamed: 'AnotherWorld') backgroundMorph: bgm. Oops! I just noticed that the result of that code is less than ideal, as bgm also becomes a submorph of AnotherWorld. What's a better way to give new worlds the same background as the first world? --Aidan

Jan. 25, 2011

Re: [Pharo-users] Multiple Worlds for Pharo *stable*

by Tony Fleig

I set up different backgrounds in my different worlds so I could tell which one I was in. ;) TF On Mon, Jan 24, 2011 at 6:53 PM, Aidan Gauland <aidalgol(a)no8wireless.co.nz>wrote: > On Mon, Jan 24, 2011 at 08:51:55AM -0800, Tony Fleig wrote: > > I noticed the taskbar was missing in the new worlds, so I evaluate the > > following when I create a new world: > > > > World taskbars ifEmpty: [ > > TaskbarMorph new openInWorld: World. > > (World systemWindows select: [ :each | > > each isCollapsed]) do: [ :wnd | wnd restore; minimize ]]] > > Thanks! That worked perfectly for me. > > If anyone wants to have the same background in their other worlds as > the first one, this should do it... > > wm := WorldManager instance. > bgm := (wm worldNamed: 'Pharo') backgroundMorph. > (wm worldNamed: 'AnotherWorld') backgroundMorph: bgm. > > Regards, > Aidan > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAk0+Oy8ACgkQjyzTRvYJmaWbnACfWD9WKfQ/7nm2aJAVDYbX/LXl > mkEAnjsDv0S+0upvBpXkeFaBZs9l3Dve > =GgPD > -----END PGP SIGNATURE----- > >

Jan. 25, 2011

Re: [Pharo-users] Multiple Worlds for Pharo *stable*

by Aidan Gauland

On Mon, Jan 24, 2011 at 08:51:55AM -0800, Tony Fleig wrote: > I noticed the taskbar was missing in the new worlds, so I evaluate the > following when I create a new world: > > World taskbars ifEmpty: [ > TaskbarMorph new openInWorld: World. > (World systemWindows select: [ :each | > each isCollapsed]) do: [ :wnd | wnd restore; minimize ]]] Thanks! That worked perfectly for me. If anyone wants to have the same background in their other worlds as the first one, this should do it... wm := WorldManager instance. bgm := (wm worldNamed: 'Pharo') backgroundMorph. (wm worldNamed: 'AnotherWorld') backgroundMorph: bgm. Regards, Aidan

Jan. 25, 2011