Re: [Pharo-users] [ANN] HelloPharo - webapp deployment tool
François, Thanks for providing this. I am setting this up for my own environment (CentOS) and it is very useful to have your sample. I'll have to -m yum a bit but definitely a super starting point. Phil On Thu, Aug 14, 2014 at 10:42 PM, François Stephany tulipe.mouta...@gmail.com wrote: Just sent it to the Seaside ML, thanks for mentioning it ;) On Thu, Aug 14, 2014 at 5:13 PM, stepharo steph...@free.fr wrote: On 14/8/14 13:02, François Stephany 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. Excellent! I love infrastructure. Keep pushing that. Did you announce it on the seaside mailing-list 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
Re: [Pharo-users] [ANN] HelloPharo - webapp deployment tool
There are still some rough edges but I'm glad you find it useful. We can maybe work together to make the default recipe working on both Ubuntu and CentOS? If I remember well, you told me that there are no public RPM available for Pharo. Is this something that we should do? Or should we package the VM with the app? So if we install many apps on one server, we can use different VM for each app... On Mon, Sep 1, 2014 at 3:21 PM, p...@highoctane.be p...@highoctane.be wrote: François, Thanks for providing this. I am setting this up for my own environment (CentOS) and it is very useful to have your sample. I'll have to -m yum a bit but definitely a super starting point. Phil On Thu, Aug 14, 2014 at 10:42 PM, François Stephany tulipe.mouta...@gmail.com wrote: Just sent it to the Seaside ML, thanks for mentioning it ;) On Thu, Aug 14, 2014 at 5:13 PM, stepharo steph...@free.fr wrote: On 14/8/14 13:02, François Stephany 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. Excellent! I love infrastructure. Keep pushing that. Did you announce it on the seaside mailing-list 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
Re: [Pharo-users] [ANN] HelloPharo - webapp deployment tool
I've got a VM for CentOS which works ok. Frankly, I'd package the VM with the app, it is much easier. Now educating myself on RPMs and yum. But Ansible is fine now :-) Maybe you can come over one day and we can hack this together (I've beer in the fridge!) Phil
[Pharo-users] GUI construction under Pharo
Hi For what I've read and study Smalltalk was great a RAD, it was infact used a lot in financial services for that reason. Now I see that most commercial versions of Smalltalk have a GUI builder, but non of the open source. Wouldn't have a GUI building tool be a priority? Perhaps this is already done? best Ichiro -- View this message in context: http://forum.world.st/GUI-construction-under-Pharo-tp4775654.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] GUI construction under Pharo
There has been attempts to do that and Spec (htttp://spec.st) provides a declarative model. The spec (check implementors of defaultSpec for a couple samples) is basically what a GUI builder would produce and use to deifne the UI. As far as I know, VisualWorks uses such a spec approach as well. http://www.cincomsmalltalk.com/main/documentation/VisualWorks/GUIDevGuide.pdf (search for windowSpec in the text) Frankly, for a moderately complex UI, you need to understand what's going on and I think a GUI builder isn't going to offer any benefit vs development time. The best thing I've seen is Matisse in Netbeans but it wasn't really useful for an app we wrote in Java/Swing with a lot of weird controls and interdependent fields. This is especially true when one has dynamic layouts to do. And that's why a webbrowser has a lot of advantages these days (Maybe not to write CAD software but it will come). HTH Phil On Mon, Sep 1, 2014 at 5:40 PM, Ichiseki is...@outlook.com wrote: Hi For what I've read and study Smalltalk was great a RAD, it was infact used a lot in financial services for that reason. Now I see that most commercial versions of Smalltalk have a GUI builder, but non of the open source. Wouldn't have a GUI building tool be a priority? Perhaps this is already done? best Ichirt) -- View this message in context: http://forum.world.st/GUI-construction-under-Pharo-tp4775654.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] GUI construction under Pharo
For Java ; JavaFx seems more the future for desktop UI.. Swing and SWT gets subsumed and interact well too. Nice XML descriptor but gets fairly complex code punting for anything moderately complex UI.. But charting and the UI capabilities are significantly nicer in JavaFx overall.. On Mon, Sep 1, 2014 at 10:39 PM, p...@highoctane.be p...@highoctane.be wrote: There has been attempts to do that and Spec (htttp://spec.st) provides a declarative model. The spec (check implementors of defaultSpec for a couple samples) is basically what a GUI builder would produce and use to deifne the UI. As far as I know, VisualWorks uses such a spec approach as well. http://www.cincomsmalltalk.com/main/documentation/VisualWorks/GUIDevGuide.pdf (search for windowSpec in the text) Frankly, for a moderately complex UI, you need to understand what's going on and I think a GUI builder isn't going to offer any benefit vs development time. The best thing I've seen is Matisse in Netbeans but it wasn't really useful for an app we wrote in Java/Swing with a lot of weird controls and interdependent fields. This is especially true when one has dynamic layouts to do. And that's why a webbrowser has a lot of advantages these days (Maybe not to write CAD software but it will come). HTH Phil On Mon, Sep 1, 2014 at 5:40 PM, Ichiseki is...@outlook.com wrote: Hi For what I've read and study Smalltalk was great a RAD, it was infact used a lot in financial services for that reason. Now I see that most commercial versions of Smalltalk have a GUI builder, but non of the open source. Wouldn't have a GUI building tool be a priority? Perhaps this is already done? best Ichirt) -- View this message in context: http://forum.world.st/GUI-construction-under-Pharo-tp4775654.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
[Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes
Hi, I published another introduction/tutorial article Reddit.st - In 10 Cool Pharo Classes Implementing a Reddit style web application in Pharo using Seaside, Glorp and PostgreSQL https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 The focus is not so much on the smaller size or the higher developer productivity in Pharo, but more on the fact that we can cover so much ground using such powerful frameworks, as well as the natural development flow from model over tests and persistence to web GUI. This is a more intermediate level article that assumes basic knowledge about Pharo (language and IDE). https://ci.inria.fr/pharo-contribution/job/Reddit/ http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Reddit Enjoy! Sven PS: This article is actually an update of an article that I wrote in 2010 and that became unavailable/outdated. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org
Re: [Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes
Nice! Doru On Mon, Sep 1, 2014 at 11:18 PM, Sven Van Caekenberghe s...@stfx.eu wrote: Hi, I published another introduction/tutorial article Reddit.st - In 10 Cool Pharo Classes Implementing a Reddit style web application in Pharo using Seaside, Glorp and PostgreSQL https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 The focus is not so much on the smaller size or the higher developer productivity in Pharo, but more on the fact that we can cover so much ground using such powerful frameworks, as well as the natural development flow from model over tests and persistence to web GUI. This is a more intermediate level article that assumes basic knowledge about Pharo (language and IDE). https://ci.inria.fr/pharo-contribution/job/Reddit/ http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Reddit Enjoy! Sven PS: This article is actually an update of an article that I wrote in 2010 and that became unavailable/outdated. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes
Sven, This is really an excellent piece. You must have put a lot of thought into making it that short and concise. It's hard to belíeve someone can cover glorp, seaside and even a domain in such a short article! There is very little in the code that's Pharo specific. The only component that will need significant changes is the captcha. String formattíng and #asWords come to my mind. For a Smalltalker, this shouldnt be too hard. Thanks for sharing; Joachim Sven Van Caekenberghe s...@stfx.eu schrieb: Hi, I published another introduction/tutorial article Reddit.st - In 10 Cool Pharo Classes Implementing a Reddit style web application in Pharo using Seaside, Glorp and PostgreSQL https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 The focus is not so much on the smaller size or the higher developer productivity in Pharo, but more on the fact that we can cover so much ground using such powerful frameworks, as well as the natural development flow from model over tests and persistence to web GUI. This is a more intermediate level article that assumes basic knowledge about Pharo (language and IDE). https://ci.inria.fr/pharo-contribution/job/Reddit/ http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Reddit Enjoy! Sven PS: This article is actually an update of an article that I wrote in 2010 and that became unavailable/outdated. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org
