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

Re: [Pharo-dev] [Esug-list] Award.... new process :)

by Esteban A. Maringolo

Cool. The video could compete in some trailer award too. :) Esteban A. Maringolo 2014-08-15 8:37 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > Here is our submission for the ESUG Innovation Awards: > > Title: GT Inspector > Submitter: Andrei Chis, Tudor Girba, Alex Syrel > Smalltalk Dialect: Pharo > Affiliation: University of Bern, tudorgirba.com > Country: Switzerland > Website: http://gt.moosetechnology.org > Trailer: http://vimeo.com/103463364 > Keywords: Pharo, IDE, Moose, Visualization > Licence: MIT > > Cheers, > The Glamorous Team > > > > On Thu, Aug 14, 2014 at 1:24 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> Hi smalltalkers >> >> for the awards it seems that the registration server has still a problem. >> I suggest that you prepare your video and that you send a title and a >> little description of your project >> as a reply to this mail. We will manage it differently but we will do this >> great competition. >> >> Stef >> _______________________________________________ >> Esug-list mailing list >> Esug-list(a)lists.esug.org >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 15, 2014

Re: [Pharo-dev] [Esug-list] Award.... new process :)

by Tudor Girba

Hi, Here is our submission for the ESUG Innovation Awards: Title: GT Inspector Submitter: Andrei Chis, Tudor Girba, Alex Syrel Smalltalk Dialect: Pharo Affiliation: University of Bern, tudorgirba.com Country: Switzerland Website: http://gt.moosetechnology.org Trailer: http://vimeo.com/103463364 Keywords: Pharo, IDE, Moose, Visualization Licence: MIT Cheers, The Glamorous Team On Thu, Aug 14, 2014 at 1:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi smalltalkers > > for the awards it seems that the registration server has still a problem. > I suggest that you prepare your video and that you send a title and a > little description of your project > as a reply to this mail. We will manage it differently but we will do this > great competition. > > Stef > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 15, 2014

Re: [Pharo-dev] [ANN] New Woden Video

by stepharo

when can we get a tetris in 3d based on woden :) On 15/8/14 09:10, Ronie Salgado wrote: > Hello, > > In a previous email I presented an early video of Woden, my new > graphics engine written in Pharo. Here I have a new video in which I > show some of the features of Woden: > https://www.youtube.com/watch?v=1Nze9tnwYxY&feature=youtu.be > > With Alex, we started rewriting Roassal 3D using Woden, which can be > seen in the second half of the video. > > I will try to show many more demos in ESUG. > > It also should be possible now to load Woden using the following script: > > Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: > 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) > loadBleedingEdge > > Later I will make a stable configuration version. > > Greetings, > Ronie

Aug. 15, 2014

Re: [Pharo-dev] [ANN] New Woden Video

by stepharo

thanks ronie :) http://pharoweekly.wordpress.com/2014/08/15/new-woden-video/ On 15/8/14 09:10, Ronie Salgado wrote: > Hello, > > In a previous email I presented an early video of Woden, my new > graphics engine written in Pharo. Here I have a new video in which I > show some of the features of Woden: > https://www.youtube.com/watch?v=1Nze9tnwYxY&feature=youtu.be > > With Alex, we started rewriting Roassal 3D using Woden, which can be > seen in the second half of the video. > > I will try to show many more demos in ESUG. > > It also should be possible now to load Woden using the following script: > > Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: > 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) > loadBleedingEdge > > Later I will make a stable configuration version. > > Greetings, > Ronie

Aug. 15, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30854 Home: https://github.com/pharo-project/pharo-core

Aug. 15, 2014

[pharo-project/pharo-core] 2d6882: 30854

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 2d6882036cc387f362c91afb1291b1abaf9535e4 https://github.com/pharo-project/pharo-core/commit/2d6882036cc387f362c91afb… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-15 (Fri, 15 Aug 2014) Changed paths: M Collections-Strings.package/String.class/instance/converting/findSelector.st M Morphic-Base.package/MorphTreeListManager.class/instance/selection change/noteRemovalOfAll_.st M Morphic-Base.package/MorphTreeMorph.class/instance/updating/noteRemovalOfAll_.st M Morphic-Base.package/MorphTreeNodeMorph.class/instance/initialization/initWithContents_prior_forList_indentLevel_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script116.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30854.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30854 13680 [Backport 3.0] receiver of NodeModel is Nil https://pharo.fogbugz.com/f/cases/13680 13844 Extended search... fooled by block arguments (backport) https://pharo.fogbugz.com/f/cases/13844 http://files.pharo.org/image/30/30854.zip

Aug. 15, 2014

[ANN] New Woden Video

by Ronie Salgado

Hello, In a previous email I presented an early video of Woden, my new graphics engine written in Pharo. Here I have a new video in which I show some of the features of Woden: https://www.youtube.com/watch?v=1Nze9tnwYxY&feature=youtu.be With Alex, we started rewriting Roassal 3D using Woden, which can be seen in the second half of the video. I will try to show many more demos in ESUG. It also should be possible now to load Woden using the following script: Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) loadBleedingEdge Later I will make a stable configuration version. Greetings, Ronie

Aug. 15, 2014

Re: [Pharo-dev] [Pharo-business] [Pharo-users] [ANN] HelloPharo - webapp deployment tool

by Sven Van Caekenberghe

On 14 Aug 2014, at 22:40, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Ah ! I was also thinking about a cookie to keep user identity, I hate to re-login because of an expired session. I was looking for a good name, "login-token" sounds good :) It works pretty well in practice (this is a mobile app mostly), even if the Seaside session expires, your login survives and you are moved to some sensible state (but that has to be programmed explicitly). > Why do you keep it 14 days only ? Is there a reason ? I planned to make it valid much longer than that... Allowing a login to remain valid forever feels like a bad idea, but I guess the number is not necessarily fixed and should not be the same for everyone. Now, after 14 days not touching the web app from an open browser/tab you will have to do a new login, that is not that bad IMO. I would even say the UX says (implicitly) 'we closed your session for security reasons'. > On Thu, Aug 14, 2014 at 10:27 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 14 Aug 2014, at 15:21, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > > Good idea, I add monit as one of the next step. > > > > Load balancing is not supported at all. But we could change the nginx config file to load balance between two images. And maybe make something for Seaside and its state (sticky sessions?). I haven't done enough of this to actually take an informed decision. > > Here is some information on how I did it recently using nginx and Seaside: > > http://forum.world.st/Nginx-Load-Balancing-Experiences-td4750823.html > > The stickiness is by client IP. > > It is also possible to do route based stickiness in Seaside and using Zinc (see ZnServer>>#route:), but I know only how to do that with Apache 2 (it is a paying option for nginx sadly). > > Of course, in most cases you will have to do some session state sharing between instances. I used memcached for that. > > > I'll update the README to be more clear about what is done behind the scene. Showing the tree of directories created by HelloPharo will be worth a thousand words (especially if you've used capistrano before). > > > > > > On Thu, Aug 14, 2014 at 3:13 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 14 Aug 2014, at 13:08, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > > > > Oh, I forgot to mention Sven. He wrote the original http://stfx.eu/pharo-server/ > > > We basically stole all his Bash-fu to build the main script: > > > > > > https://github.com/fstephany/hello-pharo/blob/master/app > > > > > > Thanks a lot Sven! > > > > You're welcome, FranÃ§ois. BTW, I am still using that script for all my deploys. > > > > I didn't immediately see it, but does your solution include something for process monitoring and automatic restarts (like monit) and/or some basic load balancing ? In my experience the combination of these two makes for a more robust solution. Maybe that is the next step ;-) > > > > Sven > > > > > On Thu, Aug 14, 2014 at 1:02 PM, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > > Hello, > > > > > > At Ta MÃ¨re, we are used to deploy Ruby/Rails application with Heroku or on VPS with Capistrano. Almost everybody uses the same tools and techniques in the Rails community so deployment is quite easy once you grasp the process. > > > > > > The same process was quite frustrating with Pharo. To solve that, we've built HelloPharo. It is a tool to deploy small apps to a Linux VPS/VM. > > > > > > It is heavily inspired by Capistrano, it prones convention over configuration and it wants to be full stack (e.g., serve the assets, restart the processes). It is built with Ansible. > > > > > > We haven't released a fixed version yet but the tool starts to be in a good-enough shape to be shown. We want to grab some feedback and fix the most obvious limitations (see the README for more) before releasing version 0.1.0. > > > > > > If you or your company uses a well defined process to deploy pharo webapps, we are all ears. We think that having a canonical way to deploy simple apps is a must if we want to see wider Pharo adoption for small web companies. This process *must* be Unix friendly if we want to attract Python or Ruby people. Most of them are Devops anyway, the command line is their friend, NOT something they want to avoid. > > > > > > Pull requests (for code or instructions in the README) are more than welcome. The code and the documentation are MIT licensed. > > > > > > https://github.com/fstephany/hello-pharo/ > > > > > > Cheers, > > > Francois > > > > > > > > > > > _______________________________________________ > > Pharo-business mailing list > > Pharo-business(a)lists.pharo.org > > http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org > >

Aug. 14, 2014

Re: [Pharo-dev] [Pharo-business] [Pharo-users] [ANN] HelloPharo - webapp deployment tool

by FranÃ§ois Stephany

Ah ! I was also thinking about a cookie to keep user identity, I hate to re-login because of an expired session. I was looking for a good name, "login-token" sounds good :) Why do you keep it 14 days only ? Is there a reason ? I planned to make it valid much longer than that... On Thu, Aug 14, 2014 at 10:27 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 14 Aug 2014, at 15:21, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> > wrote: > > > Good idea, I add monit as one of the next step. > > > > Load balancing is not supported at all. But we could change the nginx > config file to load balance between two images. And maybe make something > for Seaside and its state (sticky sessions?). I haven't done enough of this > to actually take an informed decision. > > Here is some information on how I did it recently using nginx and Seaside: > > http://forum.world.st/Nginx-Load-Balancing-Experiences-td4750823.html > > The stickiness is by client IP. > > It is also possible to do route based stickiness in Seaside and using Zinc > (see ZnServer>>#route:), but I know only how to do that with Apache 2 (it > is a paying option for nginx sadly). > > Of course, in most cases you will have to do some session state sharing > between instances. I used memcached for that. > > > I'll update the README to be more clear about what is done behind the > scene. Showing the tree of directories created by HelloPharo will be worth > a thousand words (especially if you've used capistrano before). > > > > > > On Thu, Aug 14, 2014 at 3:13 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > On 14 Aug 2014, at 13:08, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> > wrote: > > > > > Oh, I forgot to mention Sven. He wrote the original > http://stfx.eu/pharo-server/ > > > We basically stole all his Bash-fu to build the main script: > > > > > > https://github.com/fstephany/hello-pharo/blob/master/app > > > > > > Thanks a lot Sven! > > > > You're welcome, FranÃ§ois. BTW, I am still using that script for all my > deploys. > > > > I didn't immediately see it, but does your solution include something > for process monitoring and automatic restarts (like monit) and/or some > basic load balancing ? In my experience the combination of these two makes > for a more robust solution. Maybe that is the next step ;-) > > > > Sven > > > > > On Thu, Aug 14, 2014 at 1:02 PM, FranÃ§ois Stephany < > tulipe.moutarde(a)gmail.com> wrote: > > > Hello, > > > > > > At Ta MÃ¨re, we are used to deploy Ruby/Rails application with Heroku > or on VPS with Capistrano. Almost everybody uses the same tools and > techniques in the Rails community so deployment is quite easy once you > grasp the process. > > > > > > The same process was quite frustrating with Pharo. To solve that, > we've built HelloPharo. It is a tool to deploy small apps to a Linux VPS/VM. > > > > > > It is heavily inspired by Capistrano, it prones convention over > configuration and it wants to be full stack (e.g., serve the assets, > restart the processes). It is built with Ansible. > > > > > > We haven't released a fixed version yet but the tool starts to be in a > good-enough shape to be shown. We want to grab some feedback and fix the > most obvious limitations (see the README for more) before releasing version > 0.1.0. > > > > > > If you or your company uses a well defined process to deploy pharo > webapps, we are all ears. We think that having a canonical way to deploy > simple apps is a must if we want to see wider Pharo adoption for small web > companies. This process *must* be Unix friendly if we want to attract > Python or Ruby people. Most of them are Devops anyway, the command line is > their friend, NOT something they want to avoid. > > > > > > Pull requests (for code or instructions in the README) are more than > welcome. The code and the documentation are MIT licensed. > > > > > > https://github.com/fstephany/hello-pharo/ > > > > > > Cheers, > > > Francois > > > > > > > > > > > _______________________________________________ > > Pharo-business mailing list > > Pharo-business(a)lists.pharo.org > > http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org > >

Aug. 14, 2014

Re: [Pharo-dev] [Pharo-business] [Pharo-users] [ANN] HelloPharo - webapp deployment tool

by Sven Van Caekenberghe

On 14 Aug 2014, at 15:21, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Good idea, I add monit as one of the next step. > > Load balancing is not supported at all. But we could change the nginx config file to load balance between two images. And maybe make something for Seaside and its state (sticky sessions?). I haven't done enough of this to actually take an informed decision. Here is some information on how I did it recently using nginx and Seaside: http://forum.world.st/Nginx-Load-Balancing-Experiences-td4750823.html The stickiness is by client IP. It is also possible to do route based stickiness in Seaside and using Zinc (see ZnServer>>#route:), but I know only how to do that with Apache 2 (it is a paying option for nginx sadly). Of course, in most cases you will have to do some session state sharing between instances. I used memcached for that. > I'll update the README to be more clear about what is done behind the scene. Showing the tree of directories created by HelloPharo will be worth a thousand words (especially if you've used capistrano before). > > > On Thu, Aug 14, 2014 at 3:13 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 14 Aug 2014, at 13:08, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > > Oh, I forgot to mention Sven. He wrote the original http://stfx.eu/pharo-server/ > > We basically stole all his Bash-fu to build the main script: > > > > https://github.com/fstephany/hello-pharo/blob/master/app > > > > Thanks a lot Sven! > > You're welcome, FranÃ§ois. BTW, I am still using that script for all my deploys. > > I didn't immediately see it, but does your solution include something for process monitoring and automatic restarts (like monit) and/or some basic load balancing ? In my experience the combination of these two makes for a more robust solution. Maybe that is the next step ;-) > > Sven > > > On Thu, Aug 14, 2014 at 1:02 PM, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > Hello, > > > > At Ta MÃ¨re, we are used to deploy Ruby/Rails application with Heroku or on VPS with Capistrano. Almost everybody uses the same tools and techniques in the Rails community so deployment is quite easy once you grasp the process. > > > > The same process was quite frustrating with Pharo. To solve that, we've built HelloPharo. It is a tool to deploy small apps to a Linux VPS/VM. > > > > It is heavily inspired by Capistrano, it prones convention over configuration and it wants to be full stack (e.g., serve the assets, restart the processes). It is built with Ansible. > > > > We haven't released a fixed version yet but the tool starts to be in a good-enough shape to be shown. We want to grab some feedback and fix the most obvious limitations (see the README for more) before releasing version 0.1.0. > > > > If you or your company uses a well defined process to deploy pharo webapps, we are all ears. We think that having a canonical way to deploy simple apps is a must if we want to see wider Pharo adoption for small web companies. This process *must* be Unix friendly if we want to attract Python or Ruby people. Most of them are Devops anyway, the command line is their friend, NOT something they want to avoid. > > > > Pull requests (for code or instructions in the README) are more than welcome. The code and the documentation are MIT licensed. > > > > https://github.com/fstephany/hello-pharo/ > > > > Cheers, > > Francois > > > > > > _______________________________________________ > Pharo-business mailing list > Pharo-business(a)lists.pharo.org > http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

Aug. 14, 2014