July 2014 - Pharo-dev - lists.pharo.org

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

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

by kilon alios

yes the one I am considering as strong candidate is (BPYObjects at: 'Cube' ) location : #( 0 0 0 ) I would try to simplify bpy ( Blender Python API) and make it a lot more pharo friendly. However plain python string will be kept as well, so you can copy paste existing python code. One thing to note here is that Blender python addons are a huge deal. Python addons are actually full blown python apps. Blender python is basically a regular cpython 3 which is by far the most popular python implementation , meaning not only that you can use blender api object but any python library you can find. As a pharo developer you also can tap into this power via Ephestos. something that I forgot to mention in the video, in the github repo there is a rawcode.py. This is a strip down version of the Blender code that will separate to its own project that I am naming "Atlas". The goal of Atlas, is to create a two way communication socket bridge between cpython (most popular python implementation) and pharo. Very similar to Ephestos but you will no longer need Blender. That means that pharo coders will be able to use python libraries from inside pharo and even mix python with pharo code. So you could make part of your application in python and part in pharo and still function as a single application. If I find the time I would like to expand Atlas to other languages too, so that pharo can take advantage of any library written in any language without the trouble of FFIs. But most likely I will stick to python and let others do the work. But even with just python as you imagine python is extremely popular and quite friendly with the pharo way of thinking. Meaning that in python its all about live objects too. Pharo will be able to tap into thousands of powerful python libraries. ï»¿ I reserve some doubts to the amount of problems I will have to face to accomplish this and I am no way claiming it wont be a long process but so far through these very first steps the idea seems to go well in practice. On Wed, Jul 16, 2014 at 5:55 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Tue, Jul 15, 2014 at 11:09 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > > > > The goal is to expose Blender coders to the power of Pharo and Pharo to > the > > power of Blender. As you can imagine the potential is huge but I rather > talk > > what Ephestos can do already. > > That's great kilon! I can't wait to see how far you could go with > that. I hope you plan to use Pharo syntax instead of plain string for > the messages. A message like this: > > "bpy.data.objects["Cube"].location = (0.0, 0.0, 0.0)" > > could be written like that: > > (EphestosMessage bpy data objects: 'Cube') location: (EphestosLocation > x: 0 y: 0 z: 0) > > or something similar > > -- > 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] [ANN] Ephestos - Using and Coding Blender from inside Pharo

by Esteban A. Maringolo

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

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

by kilon alios

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. On Wed, Jul 16, 2014 at 5:53 PM, Ben Coman <btc(a)openinworld.com> wrote: > I don't have time to play, but this looks very very cool. At a minimum, > its a great demonstration of Pharo/Smalltalk playing-well-with-others. > > Some feedback on the video presentation, zooming in on the workspace to > make the text more readable in low-def video streams, then zooming out just > before it is executed would be useful. > > cheers -ben > > kilon alios wrote: > >> Its far from production ready but I am too excited to keep to myself. I >> present to you Ephestos. >> Ephestos is a socket bridge that communicates with Blender the most >> popular and most powerful open source 3d application. >> http://www.blender.org/ >> >> The goal is to expose Blender coders to the power of Pharo and Pharo to >> the power of Blender. As you can imagine the potential is huge but I rather >> talk what Ephestos can do already. >> Even though Ephestos is in total less than 200 lines of code it can >> already communicate with blender and affect blender properties. Blender >> properties are basically instance variables for any kind of blender object, >> 3d object, material, textures etc So already you can affect a huge deal of >> blender . >> >> Unfortunately Blender operators seem to crash Blender , probably I am >> doing something stupid that I will fix. Blender operators are for >> performing blender actions so they are very important. >> >> I have made a simple video demo of it that can be watched here >> >> https://www.youtube.com/watch?v=8igk9DoY6PU&feature=youtu.be < >> https://www.youtube.com/watch?v=8igk9DoY6PU&feature=youtu.be> >> >> >> To use it you need first the Blender addon which can be found here >> >> https://github.com/kilon/pyEphestos >> >> The code should be inside a folder named "pyEphestos" and placed in >> Blender addons directory which is located for Macos in Application >> Support/Blender/VersionsOfBlender/scripts/addons and in Windows should >> be in App Data/Roaming/..... or you can place it inside the blender folder >> in similar sub directory >> >> You also need the Pharo code which can be found here >> >> http://www.smalltalkhub.com/#!/~kilon/Ephestos/ < >> http://www.smalltalkhub.com/#%21/%7Ekilon/Ephestos/> >> >> >> As I said it is far from production ready , but it works. >> The good news is that the socket communication is blazing fast, at least >> compared to what I expected. I was able to perform 1000 connections under a >> second. And each connection carries a 1024 bytes messages , thats a lot of >> code. Should be possible to pass thousands of lines of code under a second >> to Blender. >> My only worry is blender itself since it tends to be very crashy in the >> areas I am pushing. >> By the way Always press esc after you enable Ephestos in Blender to close >> the socket or else it wont free it and next time you wont be able to open >> the socket and you will have to restart your OS. And do not make an error >> with the string passed . I need to add an exception for it so it wont crash >> blender. >> > > >

July 16, 2014

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

by kilon alios

don't worry more is coming :) On Wed, Jul 16, 2014 at 5:25 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > kilon alios wrote > > The goal is to expose Blender coders to the power of Pharo and Pharo to > > the > > power of Blender > > Cool! I want this :) > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/ANN-Ephestos-Using-and-Coding-Blender-from-inside-Pha… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

July 16, 2014

Pharo Not For The Enterprise

by Stephan Eggermont

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