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

Re: [Pharo-dev] Recursively downloading Pharo packages / Building images with Nix

by Luke Gorrie

On 23 June 2017 at 18:58, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Workable? Yes. Fatal flaws? None. > There did seem to be a fatal flaw. Metacello doesn't seem to want to run without network access. Pre-populating the package cache with .mcz files doesn't seem to be sufficient. I'm sure it's possible to achieve but it was beyond my skills and patience. I have found a reasonably comfortable compromise now though. I build my image in two steps now. First a "base" image is built in the Jenkins universe using Metacello and the stable versions de jour of all the dependencies. Second the base image is imported into the Nix universe and extended using very low-brow Smalltalk scripts to force a reload of my own packages and setup the settings that I want. This seems fine. The base image can be updated by Jenkins every month or more: Just when I need to add a dependency or pull fixes to an existing one. The derived image can then be built many times per day within the same workflow as the rest of my application. Just in case anybody is curious here is the Nix code that I'm using to import the base image, add my extensions, and create a startup script that runs the image under vncserver+ratpoison for easy remote access to the GUI: https://github.com/studio/studio/blob/master/nixpkgs/studio/frontend/defaul…

July 18, 2017

Epicea applying multiple changes

by Andrei Chis

Hi, Is there some known bug in Epicea when applying multiple changes at once in Pharo 6? I had a few crashes lately and each time when recovering the changes by selecting multiple changes at once some changes are skipped. If I apply manually each change it works. Cheers, Andrei

July 18, 2017

Re: [Pharo-dev] Automatic Refactoring Disranging Seaside Rest Methods

by Max Leske

As Gabriel notes, it looks like your missing the .sources file. I don't know what pharocloud supports, but you could try packaging your image and your .sources file into the same ZIP archive. Cheers, Max On 18 July 2017 at 02:21:54, lionelakue (lionelakue(a)gmail.com) wrote: Now I can remember reading about this somewhere(wrongly remembered it as automatic refactoring)... I have this problem when I have to copy my image to pharocloud by example. You need to zip your .image file and load it to the cloud. what I am doing now is to replace my in-uri string parameters with the excepted arg1, arg2 etc. So is this the only solution? since the behavior is not voluntary. gcotelli wrote > I saw this happening only when the image cannot find the sources file, so > it has to decompile the methods. > > On Mon, Jul 17, 2017 at 7:34 PM, lionelakue < > lionelakue@ > > wrote: > >> Hello everyone, >> >> When you copy an image or sometimes when you make a Metacello commit, >> your >> methods are automatically refactored. >> >> This uncleanse the code (replacing context meaningfull variable names >> with >> gereric identifiers) and prevents seaside request parameters . Which are >> mapped to method parameters by uri strings: >> >> ToDoHandler>>searchFor: aString >> > <get> >> > <path: '/search?query={aString}'> >> >> ^ String streamContents: [ :stream | >> ToDoList default items do: [ :each | >> (each title includesSubString: aString) >> ifTrue: [ stream nextPutAll: each title; crlf ] ] ] >> >> >> will become: >> >> >> ToDoHandler>>searchFor: arg1 >> > <get> >> > <path: '/search?query={aString}'> >> ^ String streamContents: [ :arg2| >> ToDoList default items do: [ :arg3| >> (each title includesSubString: aString) >> ifTrue: [ arg2 nextPutAll: arg3 title; crlf ] ] ] >> >> >> So will end having a Parameter not found exception because arg1 and >> aString >> mismatche. >> >> >> Is there a way to disable automatic refactoring? >> >> Lionel >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Automatic-Refactoring- >> Disranging-Seaside-Rest-Methods-tp4955422.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> -- View this message in context: http://forum.world.st/Automatic-Refactoring-Disranging-Seaside-Rest-Methods… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 18, 2017

Re: [Pharo-dev] Automatic Refactoring Disranging Seaside Rest Methods

by lionelakue

Now I can remember reading about this somewhere(wrongly remembered it as automatic refactoring)... I have this problem when I have to copy my image to pharocloud by example. You need to zip your .image file and load it to the cloud. what I am doing now is to replace my in-uri string parameters with the excepted arg1, arg2 etc. So is this the only solution? since the behavior is not voluntary. gcotelli wrote > I saw this happening only when the image cannot find the sources file, so > it has to decompile the methods. > > On Mon, Jul 17, 2017 at 7:34 PM, lionelakue < > lionelakue@ > > wrote: > >> Hello everyone, >> >> When you copy an image or sometimes when you make a Metacello commit, >> your >> methods are automatically refactored. >> >> This uncleanse the code (replacing context meaningfull variable names >> with >> gereric identifiers) and prevents seaside request parameters . Which are >> mapped to method parameters by uri strings: >> >> ToDoHandler>>searchFor: aString >> > <get> >> > <path: '/search?query={aString}'> >> >> ^ String streamContents: [ :stream | >> ToDoList default items do: [ :each | >> (each title includesSubString: aString) >> ifTrue: [ stream nextPutAll: each title; crlf ] ] ] >> >> >> will become: >> >> >> ToDoHandler>>searchFor: arg1 >> > <get> >> > <path: '/search?query={aString}'> >> ^ String streamContents: [ :arg2| >> ToDoList default items do: [ :arg3| >> (each title includesSubString: aString) >> ifTrue: [ arg2 nextPutAll: arg3 title; crlf ] ] ] >> >> >> So will end having a Parameter not found exception because arg1 and >> aString >> mismatche. >> >> >> Is there a way to disable automatic refactoring? >> >> Lionel >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Automatic-Refactoring- >> Disranging-Seaside-Rest-Methods-tp4955422.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> -- View this message in context: http://forum.world.st/Automatic-Refactoring-Disranging-Seaside-Rest-Methods… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 18, 2017

Re: [Pharo-dev] Automatic Refactoring Disranging Seaside Rest Methods

by Gabriel Cotelli

I saw this happening only when the image cannot find the sources file, so it has to decompile the methods. On Mon, Jul 17, 2017 at 7:34 PM, lionelakue <lionelakue(a)gmail.com> wrote: > Hello everyone, > > When you copy an image or sometimes when you make a Metacello commit, your > methods are automatically refactored. > > This uncleanse the code (replacing context meaningfull variable names with > gereric identifiers) and prevents seaside request parameters . Which are > mapped to method parameters by uri strings: > > ToDoHandler>>searchFor: aString > <get> > <path: '/search?query={aString}'> > > ^ String streamContents: [ :stream | > ToDoList default items do: [ :each | > (each title includesSubString: aString) > ifTrue: [ stream nextPutAll: each title; crlf ] ] ] > > > will become: > > > ToDoHandler>>searchFor: arg1 > <get> > <path: '/search?query={aString}'> > ^ String streamContents: [ :arg2| > ToDoList default items do: [ :arg3| > (each title includesSubString: aString) > ifTrue: [ arg2 nextPutAll: arg3 title; crlf ] ] ] > > > So will end having a Parameter not found exception because arg1 and aString > mismatche. > > > Is there a way to disable automatic refactoring? > > Lionel > > > > -- > View this message in context: http://forum.world.st/Automatic-Refactoring- > Disranging-Seaside-Rest-Methods-tp4955422.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

July 17, 2017

Automatic Refactoring Disranging Seaside Rest Methods

by lionelakue

Hello everyone, When you copy an image or sometimes when you make a Metacello commit, your methods are automatically refactored. This uncleanse the code (replacing context meaningfull variable names with gereric identifiers) and prevents seaside request parameters . Which are mapped to method parameters by uri strings: ToDoHandler>>searchFor: aString <get> <path: '/search?query={aString}'> ^ String streamContents: [ :stream | ToDoList default items do: [ :each | (each title includesSubString: aString) ifTrue: [ stream nextPutAll: each title; crlf ] ] ] will become: ToDoHandler>>searchFor: arg1 <get> <path: '/search?query={aString}'> ^ String streamContents: [ :arg2| ToDoList default items do: [ :arg3| (each title includesSubString: aString) ifTrue: [ arg2 nextPutAll: arg3 title; crlf ] ] ] So will end having a Parameter not found exception because arg1 and aString mismatche. Is there a way to disable automatic refactoring? Lionel -- View this message in context: http://forum.world.st/Automatic-Refactoring-Disranging-Seaside-Rest-Methods… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2017

Re: [Pharo-dev] [OFFTOPIC] Update: Debris Publishing / Quuve Research & Portfolio Management Platform

by Mariano Martinez Peck

On Sat, Jul 15, 2017 at 10:50 AM, Ben Coman <btc(a)openinworld.com> wrote: > How are you approaching marketing? Do you have any "lite" version thats > free? > It seems to me that products doing this end up having the broadest reach. > > For example take my history with PDFXchange. I first used it because I was > searching for a free alternative to Adobe Acrobat with simple features and > it had a good review. Two years later I forked over money for the family > install (five PCs) since my requirements expanded, and PDFXchange was what > I knew and loved. > > If its a "good" lite product, people will be *very* happy to tell friends > and colleges to get the kudos of sharing their "free" find, and you lower > the perceived friction of people trying it out. You will only covnert a > small percentage of those to paid customers, but were those that don't > convert ever going to buy your product in the first place? > > Hi Ben, We cannot agree more with you. The fact of allowing beta testers doesn't mean there won't be free licenses. Its just that as of today, we wanted some control over who gets in (mostly for security etc). We have discussed internally and we are willing to provide a free (limited) service and of course a "PRO" version to which you could upgrade. We are still defining this but this is in our short term list. Best, > cheers -ben > > On Thu, Jul 13, 2017 at 10:19 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Wed, Jul 12, 2017 at 5:22 PM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> >>> Hi mariano >>> >>> what kind of help do you want? >>> >>> >> Hi Stef, >> >> We are now at the stage where we are ready to solicit individual and >> institutional beta users to provide feedback on the features and help with >> quality control. And after several years of self-funding the project, we >> are also actively seeking funding in order to expand our development team. As >> you can hopefully tell from our videos, we built Quuve from the bottom-up, >> and our goal is to build the premiere investment management platform for >> investors of all sizes. Though Quuve is already quite powerful, indeed far >> more so than most tools on the market, we have a long-term vision we wish >> to see through, and this requires partnering with an institutional user >> and/or raising outside capital in the near future. >> >> Whether it be email blasts, reblogging about our software, or reaching >> out to technology investors you may know personally, we would appreciate >> any help you could provide that would assist us in finding these beta >> testers and institutional partners/investors. >> >> Thanks, >> >> >> >>> Stef >>> >>> >>> On Wed, Jul 12, 2017 at 9:53 PM, Mariano Martinez Peck >>> <marianopeck(a)gmail.com> wrote: >>> > Hi all, >>> > >>> > A while back our team presented Quuve [1], a customizable investment >>> > management ecosystem for professional investors. We also discussed the >>> > technologies employed to build it [2] (it is developed on Pharo and >>> deployed >>> > on GemStone). We are reaching out again because we recently revamped >>> our >>> > website [3] and created a number of promotional videos that demonstrate >>> > Quuve's power [4]. We would appreciate your help in marketing our >>> wares! >>> > >>> > Quuve is the world's first fully integrated and customizable research >>> and >>> > portfolio management platform. The system offers powerful features >>> never >>> > before seen by the investment community and it empowers users to tailor >>> > tools in ways that accommodate their idiosyncratic investment style. >>> In the >>> > coming years, customization, data-inheritance, shared databases, >>> > machine-learning, and robo-trading will become standard among >>> investors of >>> > all sizes, and we expect Quuve will blaze the trail. >>> > >>> > If you have any questions about Quuve please let us know. >>> > >>> > [1] http://pharo.org/success/Quuve >>> > [2] http://forum.world.st/Fwd-Debris-Quuve-Technologies-used-td4 >>> 819786.html >>> > [3] http://www.debrispublishing.com/ >>> > [4] >>> > https://www.youtube.com/watch?list=PLfTMPTPc22sGNrm2rXt8kD-9 >>> iFTgqbAUG&v=zdm4CVse2Hc >>> > >>> > Thanks, >>> > >>> > -- >>> > Mariano >>> > http://marianopeck.wordpress.com >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- Mariano http://marianopeck.wordpress.com

July 17, 2017

Re: [Pharo-dev] [Seaside] [OFFTOPIC] Update: Debris Publishing / Quuve Research & Portfolio Management Platform

by Mariano Martinez Peck

On Mon, Jul 17, 2017 at 11:10 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 12 Jul 2017, at 21:53, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > Hi all, > > > > A while back our team presented Quuve [1], a customizable investment > management ecosystem for professional investors. We also discussed the > technologies employed to build it [2] (it is developed on Pharo and > deployed on GemStone). We are reaching out again because we recently > revamped our website [3] and created a number of promotional videos that > demonstrate Quuve's power [4]. > > I finally watched the first video and I must say this is really > impressive. So cool to see Smalltalk code in scripting boxes ! > > Thanks Sven, Yes, the rule engine is with Smalltalk code. The user can write their own rules (for fundamentals, algorithms, quants, screening filters, etc). The code of these rules can be simple keys or Smalltalk blocks. When blocks, these are something like this: [ :aProcessorProxy | aProcessorProxy revenues / aProcessorProxy price ] and things like that. Basically, in general we pass by a "proxy" to a processor which then dynamically understands keys and ends up evaluating rules. Sure, we have problems with mathematical operators and their precedence etc. But we try to document this and provide many many examples. There is also a kind of debugger with some call stack about the called keys etc. See attached (all violet are links that open popups to see more info) And if you liked to see Smalltalk, did you see the rules browser? hahah. See attached. How large is the technical team that built / is building this ? It looks > like a really deep/wide application. > > The product started like a single-man project in 1996. It started with Python, then moved to Smalltalk. It has no UI back then. I joined them about 5 years ago and have been working for them since then. In these last years we started a new UI using Seaside and Bootstrap, start using Ajax everywhere, we started using GemStone for deploy, etc etc. The team was/is really small..... I cannot even believe myself how much we were able to do with the team size we had. And...I cannot stop thinking what we COULD do with a bigger team... I can give you more details privately if you wish. > Anyway, great work. I hope you can make a living out of this. > > Thanks Sven for your nice words. > > We would appreciate your help in marketing our wares! > > > > Quuve is the world's first fully integrated and customizable research > and portfolio management platform. The system offers powerful features > never before seen by the investment community and it empowers users to > tailor tools in ways that accommodate their idiosyncratic investment style. > In the coming years, customization, data-inheritance, shared databases, > machine-learning, and robo-trading will become standard among investors of > all sizes, and we expect Quuve will blaze the trail. > > > > If you have any questions about Quuve please let us know. > > > > [1] http://pharo.org/success/Quuve > > [2] http://forum.world.st/Fwd-Debris-Quuve-Technologies- > used-td4819786.html > > [3] http://www.debrispublishing.com/ > > [4] https://www.youtube.com/watch?list=PLfTMPTPc22sGNrm2rXt8kD- > 9iFTgqbAUG&v=zdm4CVse2Hc > > > > Thanks, > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > _______________________________________________ > > seaside mailing list > > seaside(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Mariano http://marianopeck.wordpress.com

July 17, 2017

Re: [Pharo-dev] [Seaside] [OFFTOPIC] Update: Debris Publishing / Quuve Research & Portfolio Management Platform

by Sven Van Caekenberghe

> On 12 Jul 2017, at 21:53, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Hi all, > > A while back our team presented Quuve [1], a customizable investment management ecosystem for professional investors. We also discussed the technologies employed to build it [2] (it is developed on Pharo and deployed on GemStone). We are reaching out again because we recently revamped our website [3] and created a number of promotional videos that demonstrate Quuve's power [4]. I finally watched the first video and I must say this is really impressive. So cool to see Smalltalk code in scripting boxes ! How large is the technical team that built / is building this ? It looks like a really deep/wide application. Anyway, great work. I hope you can make a living out of this. > We would appreciate your help in marketing our wares! > > Quuve is the world's first fully integrated and customizable research and portfolio management platform. The system offers powerful features never before seen by the investment community and it empowers users to tailor tools in ways that accommodate their idiosyncratic investment style. In the coming years, customization, data-inheritance, shared databases, machine-learning, and robo-trading will become standard among investors of all sizes, and we expect Quuve will blaze the trail. > > If you have any questions about Quuve please let us know. > > [1] http://pharo.org/success/Quuve > [2] http://forum.world.st/Fwd-Debris-Quuve-Technologies-used-td4819786.html > [3] http://www.debrispublishing.com/ > [4] https://www.youtube.com/watch?list=PLfTMPTPc22sGNrm2rXt8kD-9iFTgqbAUG&v=zdm… > > Thanks, > > -- > Mariano > http://marianopeck.wordpress.com > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

July 17, 2017

CI: Downtime tomorrow

by Marcus Denker

Hi, The ci.inria.fr <http://ci.inria.fr/> infrastructure will be down tomorrow: > Tomorrow the OS of the servers hosting the Jenkins services will be upgraded. > This will result in service downtime during the whole day; we are sorry for the convenience. > > The maintenance is planned tomorrow, Tuesday 18. > > Everything should come back to normal at the end of the day.

July 17, 2017