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

Re: [Pharo-dev] Loading GitHub repositories in Pharo 4

by Sven Van Caekenberghe

> On 13 Jul 2017, at 15:00, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 13/07/2017 Ã 11:34, Sven Van Caekenberghe a Ã©crit : >>> On 13 Jul 2017, at 11:10, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi, >>> >>> Like others I seem to have trouble loading GitHub repositories, in Pharo 4 in my case. >>> >>> Basically, the following fails: >>> >>> Metacello new >>> baseline: 'P3'; >>> repository: 'github://svenvc/P3'; >>> load. >>> >>> But it also fails as dependency when specified like this: >>> >>> baseline: 'P3' with: [ >>> spec repository: 'github://svenvc/P3' ]; >>> >>> The problem seems to be related to the version info and meta data. (This project was created with Iceberg). >>> >>> MCFileTreeStCypressReader>>#loadVersionInfo >>> self hasMonticelloMetadata >>> ifTrue: [ ^ info := self extractInfoFrom: (self parseMember: 'version') ]. >>> ... >>> >>> The test #hasMonticelloMetadata succeeds, but 'version' is not found in /Users/sven/Tmp/pharo4/github-cache/svenvc/P3/master/svenvc-P3-6897866/BaselineOfP3.package/monticello.meta/version >>> >>> In the above method, there seems to be code to handle missing meta data, but it is not reached. >>> >>> Is this supposed to work ? >>> Is there a way around this ? >> I copied the following from a Pharo 6 image to the Pharo 4 image, Thierry's newer version: >> MCFileTreeAbstractReader>>#hasMonticelloMetadata >> ^ (self fileUtils >> filePathExists: 'version' >> relativeTo: >> (self fileUtils >> directoryFromPath: MCFileTreeStCypressWriter monticelloMetaDirName >> relativeTo: packageDirectory)) >> or: >> [ (self fileUtils >> filePathExists: 'version' >> relativeTo: packageDirectory) >> and: >> [ self fileUtils >> filePathExists: 'package' >> relativeTo: packageDirectory ] ] >> Which does the trick ! (It tests for 'version' explicitly). > > Yes, I added that to handle the switch to the Metadata-less format. > >> Is there a clean way to get this newer code in a 4.0 image ? > > Yes. Load FileTree from its repository. > >> Where does MonticelloFileTree-Core live when not integrated ? > > github, where else? > > (https://github.com/dalehenrich/filetree) Thanks for the reply. After some trial and error, the simplest way to get your patch in a Pharo 4 image is by doing Metacello new baseline: 'FileTree'; repository: 'github://dalehenrich/filetree:pharo4.0/repository'; load. After that, I can do meta-data-less code loading. > Regards, > > Thierry > >>> Thx, >>> >>> Sven

July 13, 2017

Re: [Pharo-dev] Loading GitHub repositories in Pharo 4

by Thierry Goubier

Le 13/07/2017 Ã 11:34, Sven Van Caekenberghe a Ã©crit : > >> On 13 Jul 2017, at 11:10, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> Like others I seem to have trouble loading GitHub repositories, in Pharo 4 in my case. >> >> Basically, the following fails: >> >> Metacello new >> baseline: 'P3'; >> repository: 'github://svenvc/P3'; >> load. >> >> But it also fails as dependency when specified like this: >> >> baseline: 'P3' with: [ >> spec repository: 'github://svenvc/P3' ]; >> >> The problem seems to be related to the version info and meta data. (This project was created with Iceberg). >> >> MCFileTreeStCypressReader>>#loadVersionInfo >> self hasMonticelloMetadata >> ifTrue: [ ^ info := self extractInfoFrom: (self parseMember: 'version') ]. >> ... >> >> The test #hasMonticelloMetadata succeeds, but 'version' is not found in /Users/sven/Tmp/pharo4/github-cache/svenvc/P3/master/svenvc-P3-6897866/BaselineOfP3.package/monticello.meta/version >> >> In the above method, there seems to be code to handle missing meta data, but it is not reached. >> >> Is this supposed to work ? >> Is there a way around this ? > > I copied the following from a Pharo 6 image to the Pharo 4 image, Thierry's newer version: > > MCFileTreeAbstractReader>>#hasMonticelloMetadata > ^ (self fileUtils > filePathExists: 'version' > relativeTo: > (self fileUtils > directoryFromPath: MCFileTreeStCypressWriter monticelloMetaDirName > relativeTo: packageDirectory)) > or: > [ (self fileUtils > filePathExists: 'version' > relativeTo: packageDirectory) > and: > [ self fileUtils > filePathExists: 'package' > relativeTo: packageDirectory ] ] > > Which does the trick ! (It tests for 'version' explicitly). Yes, I added that to handle the switch to the Metadata-less format. > Is there a clean way to get this newer code in a 4.0 image ? Yes. Load FileTree from its repository. > Where does MonticelloFileTree-Core live when not integrated ? github, where else? (https://github.com/dalehenrich/filetree) Regards, Thierry >> Thx, >> >> Sven > > >

July 13, 2017

Re: [Pharo-dev] Loading GitHub repositories in Pharo 4

by Sven Van Caekenberghe

> On 13 Jul 2017, at 11:10, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > Like others I seem to have trouble loading GitHub repositories, in Pharo 4 in my case. > > Basically, the following fails: > > Metacello new > baseline: 'P3'; > repository: 'github://svenvc/P3'; > load. > > But it also fails as dependency when specified like this: > > baseline: 'P3' with: [ > spec repository: 'github://svenvc/P3' ]; > > The problem seems to be related to the version info and meta data. (This project was created with Iceberg). > > MCFileTreeStCypressReader>>#loadVersionInfo > self hasMonticelloMetadata > ifTrue: [ ^ info := self extractInfoFrom: (self parseMember: 'version') ]. > ... > > The test #hasMonticelloMetadata succeeds, but 'version' is not found in /Users/sven/Tmp/pharo4/github-cache/svenvc/P3/master/svenvc-P3-6897866/BaselineOfP3.package/monticello.meta/version > > In the above method, there seems to be code to handle missing meta data, but it is not reached. > > Is this supposed to work ? > Is there a way around this ? I copied the following from a Pharo 6 image to the Pharo 4 image, Thierry's newer version: MCFileTreeAbstractReader>>#hasMonticelloMetadata ^ (self fileUtils filePathExists: 'version' relativeTo: (self fileUtils directoryFromPath: MCFileTreeStCypressWriter monticelloMetaDirName relativeTo: packageDirectory)) or: [ (self fileUtils filePathExists: 'version' relativeTo: packageDirectory) and: [ self fileUtils filePathExists: 'package' relativeTo: packageDirectory ] ] Which does the trick ! (It tests for 'version' explicitly). Is there a clean way to get this newer code in a 4.0 image ? Where does MonticelloFileTree-Core live when not integrated ? > Thx, > > Sven

July 13, 2017

Loading GitHub repositories in Pharo 4

by Sven Van Caekenberghe

Hi, Like others I seem to have trouble loading GitHub repositories, in Pharo 4 in my case. Basically, the following fails: Metacello new baseline: 'P3'; repository: 'github://svenvc/P3'; load. But it also fails as dependency when specified like this: baseline: 'P3' with: [ spec repository: 'github://svenvc/P3' ]; The problem seems to be related to the version info and meta data. (This project was created with Iceberg). MCFileTreeStCypressReader>>#loadVersionInfo self hasMonticelloMetadata ifTrue: [ ^ info := self extractInfoFrom: (self parseMember: 'version') ]. ... The test #hasMonticelloMetadata succeeds, but 'version' is not found in /Users/sven/Tmp/pharo4/github-cache/svenvc/P3/master/svenvc-P3-6897866/BaselineOfP3.package/monticello.meta/version In the above method, there seems to be code to handle missing meta data, but it is not reached. Is this supposed to work ? Is there a way around this ? Thx, Sven

July 13, 2017

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

by Mariano Martinez Peck

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- > td4819786.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

July 13, 2017

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

by Mariano Martinez Peck

BTW, thanks for creating the ycombinator post! https://news.ycombinator.com/item?id=14756598#14757008 Cheers, On Wed, Jul 12, 2017 at 4: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 > -td4819786.html > [3] http://www.debrispublishing.com/ > [4] https://www.youtube.com/watch?list=PLfTMPTPc22sGNrm2rXt8 > kD-9iFTgqbAUG&v=zdm4CVse2Hc > > Thanks, > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

July 13, 2017

Re: [Pharo-dev] Pharo Launcher

by Sean P. DeNigris

Stephane Ducasse-3 wrote > where can I find the pharo launcher for the latest version of Pharo? Yes, it seems like the CI has been failing for weeks, or am I missing something? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-Launcher-tp4952930p4954660.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 13, 2017

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

by Stephane Ducasse

Hi mariano what kind of help do you want? 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-td4819786.html > [3] http://www.debrispublishing.com/ > [4] > https://www.youtube.com/watch?list=PLfTMPTPc22sGNrm2rXt8kD-9iFTgqbAUG&v=zdm… > > Thanks, > > -- > Mariano > http://marianopeck.wordpress.com

July 12, 2017

[OFFTOPIC] Update: Debris Publishing / Quuve Research & Portfolio Management Platform

by Mariano Martinez Peck

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-td4819786.html [3] http://www.debrispublishing.com/ [4] https://www.youtube.com/watch?list=PLfTMPTPc22sGNrm2rXt8 kD-9iFTgqbAUG&v=zdm4CVse2Hc Thanks, -- Mariano http://marianopeck.wordpress.com

July 12, 2017

[pharo-project/pharo-core] a80076: 60508

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: a800763b1b40483a518db73a2bf2ec75d8b502dd https://github.com/pharo-project/pharo-core/commit/a800763b1b40483a518db73a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-07-12 (Wed, 12 Jul 2017) Changed paths: A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/README.md A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/definition.st A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/instance/initialization/initialize.st A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/instance/stepping and presenter/currentIcon.st A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/instance/stepping and presenter/step.st A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/instance/stepping and presenter/stepTime.st R Morphic-Widgets-Tabs.package/TabMorph.class/instance/protocol/createAnimationProcess.st M Morphic-Widgets-Tabs.package/TabMorph.class/instance/protocol/retrieveMorph_.st M Morphic-Widgets-Tabs.package/TabMorph.class/instance/protocol/softRetrieveMorph.st M Polymorph-Widgets.package/MorphicUIManager.class/instance/debug/lowSpaceWatcherDefaultAction_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60507.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60508.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60507.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60508.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60508 20226 TabMorph should use stepping mechanism for animating background building https://pharo.fogbugz.com/f/cases/20226 20238 Run out of memory the image hangs without out of memory warning https://pharo.fogbugz.com/f/cases/20238 http://files.pharo.org/image/60/60508.zip

July 12, 2017