- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo Not For The Enterprise

by stepharo

> Can we have another book? LaserGame would fit in fine too. I started Fun With Pharo :) https://github.com/SquareBracketAssociates/FunWithPharo I want to write about fun project like Boids, WebCam in Japan with Zinc and other fun stuff :) I'm converting my old tex svn into pillar git :) Feel free to add **fun** chapters :) Stef > > I've started writing a chapter explaining PhlappyBird excellent idea. > > !PhlappyBird > > PhlappyBird is a smalltalk clone of the well-known little game. It is a nice example of building a small Morphic application and well suited for a tutorial. > +file://figures/PhlappyBird.png+ > > !! The top level window > > The top level window is a SystemWindow containing a game scene and a button to restart the game. The scene will be recreated when the button is pressed, and it is easiest to just have an instance variable refering to it. > > [[[ > SystemWindow subclass: #PhlappyBirdGame > instanceVariableNames: 'scene' > classVariableNames: '' > category: 'PhlappyBird' > ]]] > > The game can be started by typing ==PhlappyBirdGame play <DoIt>==. That creates a new game, opens it window in te world and sets its width and height. > > [[[ > PhlappyBirdGame class>>play > PhlappyBirdGame new > openInWorld; > extent: 298@510. > ]]] > > In Pharo, ==new== calls ==initialize==. In the initialization, the scene is created, the window is given a title and made unresizable, the scene is told that when the space key is pressed the bird should flap its wings and the restart button is added. > > [[[ > PhlappyBirdGame>>initialize > super initialize. > scene := self newScene. > self > setLabel: 'Phlappy Bird'; > beUnresizeable; > on: Character space do: [ scene flapTheBird ]; > addMorph: self createRestartButton > frame: (0(a)0.92 corner: 1@1) > ]]]. > > The ==addMorph:frame:== message is the morphic implementation of the composite pattern. All Morphs can be composites. Most Morphs use ==addMorph:fullFrame:== where the frame provides a layout object, but a SystemWindow adds a simpler variant where a proportional layout can be used with a rectangle with values between 0 and 1 for the relative size. The button takes the 8% of the bottom part of the user-draw area of the window. > The scene takes the rest. > > [[[ > PhlappyBirdGame>>newScene > | newScene | > newScene := Scene new. > self > addMorph: newScene > frame: (0@0 corner: 1(a)0.92) > ^ newScene > ]]] > > !!! The restart button > The button is a ==PluggableButtonMorph==. A PluggableButtonMorph is a themeable button, that takes colors, borders and corner radius from the currently selected theme. > > ;SystemWindow is also a theme-aware object. > > [[[ > PhlappyBirdGame>>createRestartButton > ^ PluggableButtonMorph > on: self > getState: nil > action: #restartPressed > label: #restartButtonLabel > ]]] > > The PluggableButtonMorph will react to being clicked by performing the ==restartPressed== action method on its model (self), and gets its label from the ==restartButtonLabel== method. The label is just a string. A PluggableButtonMorph can show a binary value, and by ==setState: nil== it is indicated that this is just a plain button. > > [[[ > PhlappyBirdGame>>restartButtonLabel > ^ 'New Game' > ]]] > > When the button is pressed, the current scene is removed as submorph from the window and a new one is created and added. > [[[ > PhlappyBirdGame>>restartPressed > scene delete. > scene := self newScene. > ]]] >

July 16, 2014

Re: [Pharo-dev] Current maintainer of PharoExtras/LDAP?

by stepharo

On 16/7/14 19:02, Udo Schneider wrote: > All, > > I'm currently making some changes to the LDAP package to make it play > nicer with ActiveDirectory and SSL. Up to now all those changes were > non-intrusive to the current packages. But I'm hitting a few issues > now which would change the base packages. > > What's the policy on this? Improving :) We need stronger and better libraries. > Keeping those changes in my own fork or submitting them to a > maintainer (who?). I gave you access to the PharoExtras repo. Just add tests and build the best LDAP you want :) Make sure that everything work well and suits your needs. I'm not sure that current design is good. At least when olivier auverlot showed to me I was skeptical about the chapter we/he wrote on it. > In addition ... as far as I can see the current package is Pharo only > (was Squeak). > If "Pharo-only" is o.k. I could for instance integrate my stuff for > LDAP-over-SSL in there directly (based on Zodiac). Excellent idea. Our goal is to make sure that people can make business. > > Thanks, > > Udo > > >

July 16, 2014

Re: [Pharo-dev] About Cocoa delegate

by stepharo

Thanks I will have a look. Esteban my point is that it looks like delegates are like strategy but I wonder why all the strategies for a given facet would not have to implement the protocol. To me having isKindOf: respondTo: sucks so when a framework forces it this is even worse. Stef On 16/7/14 11:04, Esteban Lorenzano wrote: > btwâ¦ while I think cocoa fundamentals is good reading, it is marked as > a retired document. > I think the replace doc is this one: > > https://developer.apple.com/library/mac/documentation/general/conceptual/Co… > > (but since I still do not read it, I donât know if is a good replacement) > > Esteban > > On 16 Jul 2014, at 10:58, stepharo <stepharo(a)free.fr> wrote: > >> I found strange to force user to write >> >> Before invoking a delegation method, make sure the delegate >> implements it by sending it a >> >> respondsToSelector: message. >> >> Cocoa Fundamentals Guide (TP40002974 6.0.0) >> - (void)someMethod { >> >> if ( [delegate respondsToSelector:@selector(operationShouldProceed)] ){ >> >> if ( [delegate operationShouldProceed] ) { >> // do something appropriate >> >> } } >> >> } >> >> I'm reading also on bindings (could be like valueHolder) and >> targetAction. >> I think that I will have to read that several times :) >> >> https://developer.apple.com/legacy/library/documentation/Cocoa/Conceptual/C… >> >> Stef >> >> Cocoa Fundamentals Guide (TP40002974 6.0.0) >> On 16/7/14 10:48, stepharo wrote: >>> Hi >>> >>> In the quest for a better UI framework :), I was re rereading about >>> delegate in Cocoa. >>> A delegating object will delegate certain operations to a delegate >>> object (check the attachment). >>> Now I was wondering why this is not a simple delegation they wrote: >>> >>> The delegating object sends a message only if the delegate >>> implements the method. It makes this discovery by invoking the >>> NSObject method respondsToSelector: in the delegate first. >>> >>> Cocoa Fundamentals Guide (TP40002974 6.0.0) >>> >> >

July 16, 2014

Current maintainer of PharoExtras/LDAP?

by Udo Schneider

All, I'm currently making some changes to the LDAP package to make it play nicer with ActiveDirectory and SSL. Up to now all those changes were non-intrusive to the current packages. But I'm hitting a few issues now which would change the base packages. What's the policy on this? Keeping those changes in my own fork or submitting them to a maintainer (who?). In addition ... as far as I can see the current package is Pharo only (was Squeak). If "Pharo-only" is o.k. I could for instance integrate my stuff for LDAP-over-SSL in there directly (based on Zodiac). Thanks, Udo

July 16, 2014

A great quote from the creator of C programming language

by kilon alios

*At least for the people who send me mail about a new language that they're designing, the general advice is: do it to learn about how to write a compiler. Don't have any expectations that anyone will use it, unless you hook up with some sort of organization in a position to push it hard. It's a lottery, and some can buy a lot of the tickets. There are plenty of beautiful languages (more beautiful than C) that didn't catch on. But someone does win the lottery, and doing a language at least teaches you something.* Dennis Ritchie <http://en.wikipedia.org/wiki/Dennis_Ritchie> (1941-2011) Creator of the C <http://en.wikipedia.org/wiki/C_language> programming language and of Unix <http://en.wikipedia.org/wiki/Unix> But then being non popular does not mean that you are not very useful.

July 16, 2014

Memory limit problems on Windows VM

by Oscar E. A. CallaÃº

Hi guys, I'm running some experiments in Pharo. My data is aprox. 1.3GB. When I load my image on Mac, everything works perfectly. But, when I try to load the same image on Windows, I get this error: Unable to commit memory (1326649344 bytes requested) I tried the Pharo VM, cogMT and NBcog with and without the option AddressSpaceLimit = 2048 in the ini file Please help. Cheers

July 16, 2014

Re: [Pharo-dev] Pharo Not For The Enterprise

by Damien Cassou

On Wed, Jul 16, 2014 at 5:03 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Can we have another book? LaserGame would fit in fine too. I would vote to put your chapter in an existing book for now: either UpdatedPharoByExample or EnterprisePharo. That way you benefit from the architecture in place (the jenkins job for example). Then, we can always move the chapter someplace else. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 16, 2014

Re: [Pharo-dev] Pharo Not For The Enterprise

by Torsten Bergmann

Hi Stephan, Maybe you should use http://pillarhub.pharocloud.com/hub/pillarhub/about to write and share it. Pharo and Smalltalk is nice for simulations and gaming - maybe a book is suitable. For instance Marco Leberfing from Germany will soon finish his game written in Smalltalk. The game is about ... writing games and the life of game developers. It is written in Dolphin Smalltalk http://gamersgomakers.com Also "Aura - Fate of the Ages" was written with the help of SmalltalkMT. Dont know what happened to it, the site http://www.auragame.com is now gone but the wayback machine still knows about it https://web.archive.org/web/20070202123316/http://www.auragame.com/ Also there is Ludus - a game framework for Amber Smalltalk http://lists.gforge.inria.fr/pipermail/pharo-project/2013-April/077133.html Gaming is interesting, also the part of writing emulators like the existing Nintendo emulator so you can run them on Pharo: http://www.jarober.com/blog/blogView?entry=3555679919 So a book for my library is appreciated and if your time permits to write one ... Thanks Torsten > Gesendet: Mittwoch, 16. Juli 2014 um 17:03 Uhr > Von: "Stephan Eggermont" <stephan(a)stack.nl> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] Pharo Not For The Enterprise > > Can we have another book? LaserGame would fit in fine too. > > I've started writing a chapter explaining PhlappyBird > > !PhlappyBird > > PhlappyBird is a smalltalk clone of the well-known little game. It is a nice example of building a small Morphic application and well suited for a tutorial. > +file://figures/PhlappyBird.png+ > > !! The top level window > > The top level window is a SystemWindow containing a game scene and a button to restart the game. The scene will be recreated when the button is pressed, and it is easiest to just have an instance variable refering to it. > > [[[ > SystemWindow subclass: #PhlappyBirdGame > instanceVariableNames: 'scene' > classVariableNames: '' > category: 'PhlappyBird' > ]]] > > The game can be started by typing ==PhlappyBirdGame play <DoIt>==. That creates a new game, opens it window in te world and sets its width and height. > > [[[ > PhlappyBirdGame class>>play > PhlappyBirdGame new > openInWorld; > extent: 298@510. > ]]] > > In Pharo, ==new== calls ==initialize==. In the initialization, the scene is created, the window is given a title and made unresizable, the scene is told that when the space key is pressed the bird should flap its wings and the restart button is added. > > [[[ > PhlappyBirdGame>>initialize > super initialize. > scene := self newScene. > self > setLabel: 'Phlappy Bird'; > beUnresizeable; > on: Character space do: [ scene flapTheBird ]; > addMorph: self createRestartButton > frame: (0(a)0.92 corner: 1@1) > ]]]. > > The ==addMorph:frame:== message is the morphic implementation of the composite pattern. All Morphs can be composites. Most Morphs use ==addMorph:fullFrame:== where the frame provides a layout object, but a SystemWindow adds a simpler variant where a proportional layout can be used with a rectangle with values between 0 and 1 for the relative size. The button takes the 8% of the bottom part of the user-draw area of the window. > The scene takes the rest. > > [[[ > PhlappyBirdGame>>newScene > | newScene | > newScene := Scene new. > self > addMorph: newScene > frame: (0@0 corner: 1(a)0.92) > ^ newScene > ]]] > > !!! The restart button > The button is a ==PluggableButtonMorph==. A PluggableButtonMorph is a themeable button, that takes colors, borders and corner radius from the currently selected theme. > > ;SystemWindow is also a theme-aware object. > > [[[ > PhlappyBirdGame>>createRestartButton > ^ PluggableButtonMorph > on: self > getState: nil > action: #restartPressed > label: #restartButtonLabel > ]]] > > The PluggableButtonMorph will react to being clicked by performing the ==restartPressed== action method on its model (self), and gets its label from the ==restartButtonLabel== method. The label is just a string. A PluggableButtonMorph can show a binary value, and by ==setState: nil== it is indicated that this is just a plain button. > > [[[ > PhlappyBirdGame>>restartButtonLabel > ^ 'New Game' > ]]] > > When the button is pressed, the current scene is removed as submorph from the window and a new one is created and added. > [[[ > PhlappyBirdGame>>restartPressed > scene delete. > scene := self newScene. > ]]] >

July 16, 2014

Re: [Pharo-dev] Pharo Not For The Enterprise

by kilon alios

Well not everything in there is an Enterprise solution so I think it would be better if renamed to "Pharo Bible" or "Pharo Encyclopedia" , for example Pharo Sound is not exactly Enterprise material, though its my favorite chapter :) By the way great work and thanks for reminding to try this out now, I keep forgetting. This can go also inside our Updated PBE as a nice chapter, its after all ... an example ;) On Wed, Jul 16, 2014 at 6:03 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Can we have another book? LaserGame would fit in fine too. > > I've started writing a chapter explaining PhlappyBird > > !PhlappyBird > > PhlappyBird is a smalltalk clone of the well-known little game. It is a > nice example of building a small Morphic application and well suited for a > tutorial. > +file://figures/PhlappyBird.png+ > > !! The top level window > > The top level window is a SystemWindow containing a game scene and a > button to restart the game. The scene will be recreated when the button is > pressed, and it is easiest to just have an instance variable refering to it. > > [[[ > SystemWindow subclass: #PhlappyBirdGame > instanceVariableNames: 'scene' > classVariableNames: '' > category: 'PhlappyBird' > ]]] > > The game can be started by typing ==PhlappyBirdGame play <DoIt>==. That > creates a new game, opens it window in te world and sets its width and > height. > > [[[ > PhlappyBirdGame class>>play > PhlappyBirdGame new > openInWorld; > extent: 298@510. > ]]] > > In Pharo, ==new== calls ==initialize==. In the initialization, the scene > is created, the window is given a title and made unresizable, the scene is > told that when the space key is pressed the bird should flap its wings and > the restart button is added. > > [[[ > PhlappyBirdGame>>initialize > super initialize. > scene := self newScene. > self > setLabel: 'Phlappy Bird'; > beUnresizeable; > on: Character space do: [ scene flapTheBird ]; > addMorph: self createRestartButton > frame: (0(a)0.92 corner: 1@1) > ]]]. > > The ==addMorph:frame:== message is the morphic implementation of the > composite pattern. All Morphs can be composites. Most Morphs use > ==addMorph:fullFrame:== where the frame provides a layout object, but a > SystemWindow adds a simpler variant where a proportional layout can be used > with a rectangle with values between 0 and 1 for the relative size. The > button takes the 8% of the bottom part of the user-draw area of the window. > The scene takes the rest. > > [[[ > PhlappyBirdGame>>newScene > | newScene | > newScene := Scene new. > self > addMorph: newScene > frame: (0@0 corner: 1(a)0.92) > ^ newScene > ]]] > > !!! The restart button > The button is a ==PluggableButtonMorph==. A PluggableButtonMorph is a > themeable button, that takes colors, borders and corner radius from the > currently selected theme. > > ;SystemWindow is also a theme-aware object. > > [[[ > PhlappyBirdGame>>createRestartButton > ^ PluggableButtonMorph > on: self > getState: nil > action: #restartPressed > label: #restartButtonLabel > ]]] > > The PluggableButtonMorph will react to being clicked by performing the > ==restartPressed== action method on its model (self), and gets its label > from the ==restartButtonLabel== method. The label is just a string. A > PluggableButtonMorph can show a binary value, and by ==setState: nil== it > is indicated that this is just a plain button. > > [[[ > PhlappyBirdGame>>restartButtonLabel > ^ 'New Game' > ]]] > > When the button is pressed, the current scene is removed as submorph from > the window and a new one is created and added. > [[[ > PhlappyBirdGame>>restartPressed > scene delete. > scene := self newScene. > ]]] >

July 16, 2014

Re: [Pharo-dev] [ANN] Ephestos - Using and Coding Blender from inside Pharo

by kilon alios

I am a huge fan of Truespace and ZBrush, so sad to see it die :( Another big love was Softimage XSI, dead too. I started using Blender as soon as Autodesk bought Softimage because I predicted that its days were numbered. I completely agree on the format of the video, next time I will have separate video for installation and another for features so it is shorter and to the point. On Wed, Jul 16, 2014 at 6:27 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2014-07-16 12:16 GMT-03:00 kilon alios <kilon.alios(a)gmail.com>: > > I am apologize about the video , I recorded it in 720p and forgot to > > increase the pharo font size. But worry not, Ephestos will come with an > > array of examples to help you understand the whole process and get you > > started. I will upload shortly the examples used in the videos. > > One suggestion about the edition of the video. Show some of the > results during the first 30 seconds, and then explain the whole > process to get there. > It's like the cooking shows, where they show the cake already made, > and then the whole process to make it. > Otherwise it gets longwinded, because you don't know when the "peak > moment" will take place. > > Having said that. What you did is really cool. I used to 3D in the > past (with Caligari trueSpace), and back then I'd love to have > something like Pharo to program it (trueSpace started used Phyton > too). > > Regards! > >

July 16, 2014