- Pharo-users - lists.pharo.org

Re: [Pharo-users] Creating class with empty Catagory!

by stepharo

Marcus I would simply not put empty we have unpackaged let us use it by default. The empty category is a bad idea and we should address it because many people are getting burned. > Yes, this could definitely be inmproved. An idea would be a dialog with a pre-filled class definition that has > useful defaults. > This way when demoing, you can just accept the empty and nevertheless a class is created just by pressing âokâ > in this dialog. > > >> On 08 Sep 2015, at 11:28, Volkert <volkert(a)komponentenwerkstatt.de> wrote: >> >> Would it be nicer to open a Altert box? >> >> BW, >> Volkert >> >> <gabhajcb.png> > >

Sept. 8, 2015

Re: [Pharo-users] "Create initializer with inst vars" is broken

by stepharo

Thanks we never use this feature. We will have a look. Le 8/9/15 11:35, Volkert a Ã©crit : > Done > > https://pharo.fogbugz.com/f/cases/16514/Create-initializer-with-inst-vars-i… > > > > On 08.09.2015 10:25, Marcus Denker wrote: >> I donât tjhink soâ¦ can you add an issue to the issue tracker? >> >>> On 08 Sep 2015, at 09:34, Volkert <volkert(a)komponentenwerkstatt.de> >>> wrote: >>> >>> >>> >>> Is this a known bug? >>> >>> <iffeijhg.png> >>> >>> >>> leads to ... >>> >>> <egjiahcj.png> >>> >>> Pharo 4.0 / build 40621 >>> >>> BW, >>> Volkert >>> >>> >>> >> > > >

Sept. 8, 2015

Re: [Pharo-users] New Pharo based solution in the wild

by stepharo

Hi Esteban Two points: - I'm sad for you. - You still have a success story. This is not because one guy got fired and another came into the place and administratively killed your project that this is a failure from Pharo perspective. We are really happy that our techno helped you. Stef Le 8/9/15 17:16, Esteban A. Maringolo a Ã©crit : > Hi all, > > I'm bumping this thread with sad news. > > Unfortunately this solution was decommissioned more than two months > ago, after more than one and a half year of perfect uptime and no > technical nor user-requested features shortcomings. > > The reasons given weren't technical, it had more to do with a change > of our customer's top manager, who also was it's internal sponsor. The > new management "inherited" this ongoing project which wasn't fully > deployed at that moment, and their stance regarding it wasn't as > proactive as with the previous one. That plus the local economic woes > during the last years created the ideal scenario for a budget cut that > let us hanging. > > Had the project been fully deployed earlier, I guess the story would > have been different. Also we heard that the new manager tried to > replace our solution with one that "he brought" without success until now. > > I'm sharing this with you in order to update the Success section of > Pharo's website. We still have the other small project, but it's > future doesn't look promising either, the current context for it is > similar with the added decline of sales (it's a mobile sales app). > > Regards, > > Esteban A. Maringolo > > ps: On the personal level these bad news were overly compensated with > the birth of my first daughter two months ago. :) > > > 2014-01-04 18:33 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>>: > > Great, impressive work, Esteban, thanks for sharing. > > I wish you luck in completing your pilot. > > Let us known if you need help in critical areas. > > Sven > > On 04 Jan 2014, at 20:16, Esteban A. Maringolo > <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: > > > Hi all, > > > > After one year of negotiations (demos, quotes, etc.) and a couple of > > months of development, by the end of December we released a pilot > > version of our pharo based solution. > > The solution consists of a native mobile app (Android), with > Pharo 2.0 > > servers, using Seaside for the web UI, Seaside-REST for the > mobile app > > API and Zinc Websockets to certain "live" features of the web. The > > persistence is GLORP using the native PostgreSQL driver. > > > > I can't disclose much more about the customer or the solution > yet, it > > is a private solution for a multinational consumer goods company > > operating in Argentina. > > > > But I can comment on the numbers: > > * The pilot will end in ~40 days > > * It involves 50 mobile users of the Android app using it daily. > > * An nginx frontend for static files and http proxying to the > pharo app servers > > * Two pharo images as servers, one for the web interface, and > one for > > the REST API. The image is the same, they work as two separate app > > servers to make use of each server and for improved reliability (I > > don't want the seaside failures, which has been none yet, to affect > > the REST API). > > * Everything running in DigitalOcean droplets based in NYC (they add > > ~180ms of latency from here but their price/value equations is > > unmatched). > > > > Some performance numbers: > > * The Pharo server uptime has been no less than perfect, the > first 10 > > days with uninterrupted uptime. Only shutdown to upgrade the image > > (yesterday night). > > * The load is minor, with peaks of ~30 concurrent mobile users > during > > a few "business" moments of the day, the server never passed 15% of > > CPU use. The disk I/O is also small, but the database is small too > > (growing daily). > > > > If the pilot succeeds the plan is to extend the user base to ~1000 > > mobile users. But some water must pass under the bridge before > > thinking of that. And if it ever happens, it is going to be gradual. > > > > Some anecdotal info > > I quit my Smalltalk full time job at InfOil (after 9 years of > > employment) to dedicate 100% to my new company. So I'm betting > big on > > this. By now I'm the sole Smalltalk developer (devops?) of the > > company. Time has never been more scarce than nowadays. > > > > Why Pharo? > > * Because it is the best open source Smalltalk ("inspired") out > there. > > * Because I have 10+ years of experience with Smalltalk I can't > throw > > away in the context of rapid prototyping and business domain > modelling > > (emphasis on this). > > * It was a key advantage during the negotiations, we could show a > > wireframed live app even before our competition prepared a > PowerPoint > > presentation. > > > > The development process with Pharo has been rudimentary, only > > Monticello packages and a couple of workspace scripts to > provision new > > images. > > I still can't get my head around Metacello. But honestly I haven't > > dedicated as much time as it needs to be learnt. Having used VAST > > ENVY's ConfigurationMaps successfully in the past is a proof I can > > learn Metacello. > > > > During the last years at InfOil we were using git with Dolphin > > Smalltalk, with CI after every git push to the main repo. This was > > also linked with our issue tracking system, in order to know in > which > > build a certain issue was fixed. We used Dolphin's PAX's files (CVS > > friendly), Gitlab, JetBrain's TeamCity and YouTrack > > I'd like to do the same using Monticello's FileTree, BitBucket and > > JIRA (CI server to be defined). > > > > Hopefully with some time, I'll be able to dive deeper into this. > > My learning of Pharo tooling hasn't been straightforward, but maybe > > because I'm old and spoiled with other Smalltalk dialects (VSE, > VAST, > > Dolphin). > > I was managing the Android code (java) with git branching and > merging > > way before I learnt how to use Monticello. Managing the code (files) > > was the only advantage of working with Eclipse/Java. Everything else > > was a burden compared with Pharo. > > > > I wanted to share my experiences through a blog, but haven't had > time > > to set it up as I'd like, and by now this email is going to be all I > > can share. After the pilot, we can talk about reporting a success > > story for Pharo. I felt like this during the last week: > > > http://devopsreactions.tumblr.com/post/68251866244/successful-deployment-at… > > > > > > Best regards, > > > > Esteban A. Maringolo > > CTO (aka DevOps), http://trentosur.com > > > > >

Sept. 8, 2015

Re: [Pharo-users] Mathex: Generating latex math from Pharo.

by Julien Delplanque

On 08/09/15 21:20, Offray Vladimir Luna CÃ¡rdenas wrote: > Hi, > > On 08/09/15 13:02, Julien Delplanque wrote: >> >> >> On 08/09/15 16:36, Damien Cassou wrote: >>> Julien Delplanque <julien(a)tamere.eu> writes: >>> >>>> On 07/09/15 13:56, Damien Cassou wrote: >>>>> Julien Delplanque <julien(a)tamere.eu> writes: >>>>>> (Phi equal: ((1 asMathex + 5 asMathex sqrt) // 2)) equation >>>>>> asString. >>>>>> >>>>>> and get: >>>>>> >>>>>> \begin{equation} >>>>>> \phi=\frac{ 1 +\sqrt{ 5 }}{ 2 }\end{equation} >>>>> I think that's great news! One of Pillar's feature requests is to let >>>>> users write LaTeX (e.g., formulas) in their pillar document and >>>>> get nice >>>>> results in all exports (LaTeX, HTML, ePub...): >>>>> https://github.com/pillar-markup/pillar/issues/18. I'm not sure >>>>> how this >>>>> request fits in your work, but there might be some intersection. >>>>> >>>> I guess if a latex math parser is created, it is possible to use >>>> objects >>>> from Mathex to represent an equation as Mathex objects. >>>> >>>> After that the translation to html should be easy. >>>> >>>> Maybe I'll give a try if I have some time. >>> we could ask the Pillar users to write using Mathex directly so we >>> don't >>> have to write a LaTeX parser. The only remaining thing is to generate >>> png pictures from Mathex objects for inclusion in HTML. >>> >> Oh yeah, it would be easier to set up I guess :) >> >> > > Or maybe use mathjax instead of png to generate math on HTML: > > https://www.mathjax.org/ > > Cheers, > > Offray > > > Yes or even directly generate MathML it should not be difficult to implement as an extension of Mathex.

Sept. 8, 2015

Re: [Pharo-users] Flattr added to pharo.org

by Offray Vladimir Luna CÃ¡rdenas

Thanks! I now will update my profile... any way to recover the password? (Sorry :-P) Cheers, Offray On 08/09/15 02:31, Marcus Denker wrote: > Hello, > > Sorry, I activated it! > > Marcus > >> On 08 Sep 2015, at 04:04, Offray Vladimir Luna CÃ¡rdenas >> <offray(a)riseup.net <mailto:offray@riseup.net>> wrote: >> >> Hi, >> >> In a related matter, I have donated to the association and became a >> member, but my name is not listed in its web page. There is any way >> to verify that the association went fine? Which is the procedure? >> >> Cheers, >> >> Offray >> >> On 01/09/15 07:39, Marcus Denker wrote: >>> Hi, >>> >>> We added at Flattr button: >>> >>> http://pharo.org/contribute >>> >>> Direkt link is: https://flattr.com/thing/4606474/Pharo-Welcome-to-Pharo >>> >>> >>> Marcus >> >

Sept. 8, 2015

Re: [Pharo-users] Mathex: Generating latex math from Pharo.

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 08/09/15 13:02, Julien Delplanque wrote: > > > On 08/09/15 16:36, Damien Cassou wrote: >> Julien Delplanque <julien(a)tamere.eu> writes: >> >>> On 07/09/15 13:56, Damien Cassou wrote: >>>> Julien Delplanque <julien(a)tamere.eu> writes: >>>>> (Phi equal: ((1 asMathex + 5 asMathex sqrt) // 2)) equation asString. >>>>> >>>>> and get: >>>>> >>>>> \begin{equation} >>>>> \phi=\frac{ 1 +\sqrt{ 5 }}{ 2 }\end{equation} >>>> I think that's great news! One of Pillar's feature requests is to let >>>> users write LaTeX (e.g., formulas) in their pillar document and get >>>> nice >>>> results in all exports (LaTeX, HTML, ePub...): >>>> https://github.com/pillar-markup/pillar/issues/18. I'm not sure how >>>> this >>>> request fits in your work, but there might be some intersection. >>>> >>> I guess if a latex math parser is created, it is possible to use >>> objects >>> from Mathex to represent an equation as Mathex objects. >>> >>> After that the translation to html should be easy. >>> >>> Maybe I'll give a try if I have some time. >> we could ask the Pillar users to write using Mathex directly so we don't >> have to write a LaTeX parser. The only remaining thing is to generate >> png pictures from Mathex objects for inclusion in HTML. >> > Oh yeah, it would be easier to set up I guess :) > > Or maybe use mathjax instead of png to generate math on HTML: https://www.mathjax.org/ Cheers, Offray

Sept. 8, 2015

Re: [Pharo-users] Mathex: Generating latex math from Pharo.

by Julien Delplanque

On 08/09/15 16:36, Damien Cassou wrote: > Julien Delplanque <julien(a)tamere.eu> writes: > >> On 07/09/15 13:56, Damien Cassou wrote: >>> Julien Delplanque <julien(a)tamere.eu> writes: >>>> (Phi equal: ((1 asMathex + 5 asMathex sqrt) // 2)) equation asString. >>>> >>>> and get: >>>> >>>> \begin{equation} >>>> \phi=\frac{ 1 +\sqrt{ 5 }}{ 2 }\end{equation} >>> I think that's great news! One of Pillar's feature requests is to let >>> users write LaTeX (e.g., formulas) in their pillar document and get nice >>> results in all exports (LaTeX, HTML, ePub...): >>> https://github.com/pillar-markup/pillar/issues/18. I'm not sure how this >>> request fits in your work, but there might be some intersection. >>> >> I guess if a latex math parser is created, it is possible to use objects >> from Mathex to represent an equation as Mathex objects. >> >> After that the translation to html should be easy. >> >> Maybe I'll give a try if I have some time. > we could ask the Pillar users to write using Mathex directly so we don't > have to write a LaTeX parser. The only remaining thing is to generate > png pictures from Mathex objects for inclusion in HTML. > Oh yeah, it would be easier to set up I guess :)

Sept. 8, 2015

Re: [Pharo-users] New Pharo based solution in the wild

by Sven Van Caekenberghe

> On 08 Sep 2015, at 19:51, Hilaire <hilaire(a)drgeo.eu> wrote: > > Le 08/09/2015 17:16, Esteban A. Maringolo a Ã©crit : >> >> ps: On the personal level these bad news were overly compensated with >> the birth of my first daughter two months ago. :) >> > Congratualtion! Yeah ! > Hilaire > > -- > Dr. Geo > http://drgeo.eu > http://google.com/+DrgeoEu > > >

Sept. 8, 2015

Re: [Pharo-users] New Pharo based solution in the wild

by Hilaire

Le 08/09/2015 17:16, Esteban A. Maringolo a Ã©crit : > > ps: On the personal level these bad news were overly compensated with > the birth of my first daughter two months ago. :) > Congratualtion! Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

Sept. 8, 2015

Re: [Pharo-users] New Pharo based solution in the wild

by phil＠highoctane.be

Hi Esteban, Sad news about the app indeed. It is true that time to market is key to adoption. Nevertheless, I wish you well for the future. Keep in touch via other channels. Phil On Tue, Sep 8, 2015 at 5:16 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Hi all, > > I'm bumping this thread with sad news. > > Unfortunately this solution was decommissioned more than two months ago, > after more than one and a half year of perfect uptime and no technical nor > user-requested features shortcomings. > > The reasons given weren't technical, it had more to do with a change of > our customer's top manager, who also was it's internal sponsor. The new > management "inherited" this ongoing project which wasn't fully deployed at > that moment, and their stance regarding it wasn't as proactive as with the > previous one. That plus the local economic woes during the last years > created the ideal scenario for a budget cut that let us hanging. > > Had the project been fully deployed earlier, I guess the story would have > been different. Also we heard that the new manager tried to replace our > solution with one that "he brought" without success until now. > > I'm sharing this with you in order to update the Success section of > Pharo's website. We still have the other small project, but it's future > doesn't look promising either, the current context for it is similar with > the added decline of sales (it's a mobile sales app). > > Regards, > > Esteban A. Maringolo > > ps: On the personal level these bad news were overly compensated with the > birth of my first daughter two months ago. :) > > > 2014-01-04 18:33 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > >> Great, impressive work, Esteban, thanks for sharing. >> >> I wish you luck in completing your pilot. >> >> Let us known if you need help in critical areas. >> >> Sven >> >> On 04 Jan 2014, at 20:16, Esteban A. Maringolo <emaringolo(a)gmail.com> >> wrote: >> >> > Hi all, >> > >> > After one year of negotiations (demos, quotes, etc.) and a couple of >> > months of development, by the end of December we released a pilot >> > version of our pharo based solution. >> > The solution consists of a native mobile app (Android), with Pharo 2.0 >> > servers, using Seaside for the web UI, Seaside-REST for the mobile app >> > API and Zinc Websockets to certain "live" features of the web. The >> > persistence is GLORP using the native PostgreSQL driver. >> > >> > I can't disclose much more about the customer or the solution yet, it >> > is a private solution for a multinational consumer goods company >> > operating in Argentina. >> > >> > But I can comment on the numbers: >> > * The pilot will end in ~40 days >> > * It involves 50 mobile users of the Android app using it daily. >> > * An nginx frontend for static files and http proxying to the pharo app >> servers >> > * Two pharo images as servers, one for the web interface, and one for >> > the REST API. The image is the same, they work as two separate app >> > servers to make use of each server and for improved reliability (I >> > don't want the seaside failures, which has been none yet, to affect >> > the REST API). >> > * Everything running in DigitalOcean droplets based in NYC (they add >> > ~180ms of latency from here but their price/value equations is >> > unmatched). >> > >> > Some performance numbers: >> > * The Pharo server uptime has been no less than perfect, the first 10 >> > days with uninterrupted uptime. Only shutdown to upgrade the image >> > (yesterday night). >> > * The load is minor, with peaks of ~30 concurrent mobile users during >> > a few "business" moments of the day, the server never passed 15% of >> > CPU use. The disk I/O is also small, but the database is small too >> > (growing daily). >> > >> > If the pilot succeeds the plan is to extend the user base to ~1000 >> > mobile users. But some water must pass under the bridge before >> > thinking of that. And if it ever happens, it is going to be gradual. >> > >> > Some anecdotal info >> > I quit my Smalltalk full time job at InfOil (after 9 years of >> > employment) to dedicate 100% to my new company. So I'm betting big on >> > this. By now I'm the sole Smalltalk developer (devops?) of the >> > company. Time has never been more scarce than nowadays. >> > >> > Why Pharo? >> > * Because it is the best open source Smalltalk ("inspired") out there. >> > * Because I have 10+ years of experience with Smalltalk I can't throw >> > away in the context of rapid prototyping and business domain modelling >> > (emphasis on this). >> > * It was a key advantage during the negotiations, we could show a >> > wireframed live app even before our competition prepared a PowerPoint >> > presentation. >> > >> > The development process with Pharo has been rudimentary, only >> > Monticello packages and a couple of workspace scripts to provision new >> > images. >> > I still can't get my head around Metacello. But honestly I haven't >> > dedicated as much time as it needs to be learnt. Having used VAST >> > ENVY's ConfigurationMaps successfully in the past is a proof I can >> > learn Metacello. >> > >> > During the last years at InfOil we were using git with Dolphin >> > Smalltalk, with CI after every git push to the main repo. This was >> > also linked with our issue tracking system, in order to know in which >> > build a certain issue was fixed. We used Dolphin's PAX's files (CVS >> > friendly), Gitlab, JetBrain's TeamCity and YouTrack >> > I'd like to do the same using Monticello's FileTree, BitBucket and >> > JIRA (CI server to be defined). >> > >> > Hopefully with some time, I'll be able to dive deeper into this. >> > My learning of Pharo tooling hasn't been straightforward, but maybe >> > because I'm old and spoiled with other Smalltalk dialects (VSE, VAST, >> > Dolphin). >> > I was managing the Android code (java) with git branching and merging >> > way before I learnt how to use Monticello. Managing the code (files) >> > was the only advantage of working with Eclipse/Java. Everything else >> > was a burden compared with Pharo. >> > >> > I wanted to share my experiences through a blog, but haven't had time >> > to set it up as I'd like, and by now this email is going to be all I >> > can share. After the pilot, we can talk about reporting a success >> > story for Pharo. I felt like this during the last week: >> > >> http://devopsreactions.tumblr.com/post/68251866244/successful-deployment-at… >> > >> > >> > Best regards, >> > >> > Esteban A. Maringolo >> > CTO (aka DevOps), http://trentosur.com >> > >> >> >> >

Sept. 8, 2015