- Pharo-dev - lists.pharo.org

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

[pharo-project/pharo-core]

by GitHub

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

July 12, 2017

Re: [Pharo-dev] integrating FileDialog into Pharo 7

by Stephane Ducasse

lovely :) On Mon, Jul 10, 2017 at 8:34 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Can you try to prepare a pull requeast that will integrate it? The PR will > need to: > - add the packages into the repository > - add them into the baseline (BaselineOfUI) > - remove old FileDialogWindow (becuase when we add something, we should > remove something too ;-)) > > If you need help, let me know > > -- Pavel > > 2017-07-10 20:01 GMT+02:00 Peter Uhnak <i.uhnak(a)gmail.com>: >> >> Done. What next? >> >> Peter >> >> >> On Mon, Jul 10, 2017 at 12:46:50PM +0200, Pavel Krivanek wrote: >> > We should work on integration of it. Firstly please move tests to a >> > separate package. >> > >> > Cheers, >> > -- Pavel >> > >> > 2017-07-10 12:34 GMT+02:00 Peter Uhnak <i.uhnak(a)gmail.com>: >> > >> > > Hi, >> > > >> > > some people expressed interest in integrating File Dialog >> > > https://github.com/peteruhnak/file-dialog into Pharo as the default >> > > file >> > > dialog. >> > > >> > > Is it something people are interested in, or is the current solution >> > > sufficient for them? >> > > >> > > Peter >> > > >> > > >> >

July 12, 2017

Re: [Pharo-dev] No Metadata in 7.0

by Stephane Ducasse

Hi nicolai we should really fix that. I know that it is painful because we got out our confort zone. I really hope that we will be able to do something better. Now what we should do is incrementally rebuild a better system. About the git support on windows. I thought it was working what is the problem on your side? Stef On Mon, Jul 10, 2017 at 11:32 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2017-07-10 11:22 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: >> >> On Mon, Jul 10, 2017 at 11:15:27AM +0200, Nicolai Hess wrote: >> > >> > 2017-07-10 10:31 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> > >> > However the real question is if we need them in the form we had them >> > until >> > now because they are flattened as soon as a new changes file >> > (release) is >> > created and it stores only information about the last person who >> > touched >> > the method, not about the author nor wider history. >> > >> > For me, YES! >> > >> > I always take this data as a hint to track down bugs. Especially in >> > this community were different people do bug fixes or introduce >> > something new /change something, it is really helpfull and valueable >> > to track this changes by the method history. (not only *who* did the >> > change, but also, in what context, what else had changed. And I think >> > it is much easier to do this from within the image instead of looking >> > at the git diff). >> >> Are the two really mutually exclusive? Given the move to Iceberg >> wouldn't it make sense to extend Iceberg to be able to analyse the git >> history from within the image? > > > > No, they are not mutually exclusive, it is just that you can not see the > history now. > Maybe iceberg will solve this, but for now you can not see the history > (and as a windows user, I can not even use iceberg). > > >> >> >> >> > That hte history is already lost when we created a new changes/sources >> > for release is something that always disturbed me. And I hoped there >> > would be some way to reload the "real" history with all intermediate >> > changes. >> >> Cheers, >> Alistair >> >> >

July 11, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Stephane Ducasse

Tx Uko. We should improve. On Tue, Jul 11, 2017 at 7:07 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > This is actually fun. For pharo contributions I just used Iceberg ui without > scripting anything and it works absolutely fine. Iceberg has a default > location for cloned repositories, and it puts pharo there too > > Uko > > On 4 Jul 2017, at 11:52, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > A small update: > > You are not forced to use a 'pharo-core' repository in your image folder if > you provide a path to your own clone to the working copies of the > bootstrapped packages. This way you can more easily share one local clone of > the pharo-project/pharo repository. > For the registration of your local repository use this script: > > target := 'path/to/my/local/repository' asFileReference. > > repository := IceRepositoryCreator new > location: target; > subdirectory:'src'; > createRepository. > repository register. > > fork := repository remotes detect: [ :remote | remote remoteName = #myFork > ]. > repository pushRemote: fork. > repository pullRemote: repository origin. > > repository checkoutBranch: 'development'. > repository backend pullFrom: repository origin. > repository push. > > repository checkoutBranch: (SystemVersion current commitHash). > > fileTreeRepository := (MCFileTreeRepository new directory: target / #src; > yourself). > repositoryGroup := MCRepositoryGroup withRepositories: { fileTreeRepository. > MCCacheRepository uniqueInstance. }. > MCWorkingCopy allManagers > select: [ :wc | (wc repositoryGroup repositories reject: [ :repo | repo > isCache ]) isEmpty ] > thenDo: [ :wc | wc repositoryGroup: repositoryGroup ] > > > 2017-06-26 13:14 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> >> Hi, >> >> this mail describes how to start to send pull requests to Pharo 7 Github >> repository from Pharo 7. >> >> Preparations >> ===================== >> >> - you need to have a Github account and set SSH keys. See >> https://help.github.com/articles/connecting-to-github-with-ssh/ >> - create own pharo-project/pharo repository fork. Go to >> https://github.com/pharo-project/pharo, click on "Fork" button and follow >> the instructions >> >> Get Pharo 7 image >> ===================== >> >> The CI jobs for the Pharo 7 defelopment are currently not fully set and we >> still do not publish Pharo 7 image to files.pharo.org so you cannot get it >> using zero-conf scripts. But we have a provisional CI job that bootstraps >> the Pharo 7 image. >> >> https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ >> >> There download a file named like Pharo7.0-32bit-hash.zip and decompress >> it. Unlike Pharo 6 images, the archive contains three files. Image, changes >> and sources. In Pharo 7 you have the sources file for every bootstrapped >> version. It has a commit hash in the name and it cannot be shared between >> different Pharo 7 imges, however it can be shared between images that were >> created as snapshots with the same bootstrapped image as ancestor. >> >> Create local clone >> ===================== >> >> You need a local clone of the Pharo repository. Because it contains a lot >> of small files, it is not a good idea to have own clone for every image. You >> can have only one and share them between images. But because of some current >> Monticello constraints you need to have the clone placed in the image >> directory in a folder with name 'pharo-core'. >> >> In this step we will clone the Pharo repository from pharo-project/pharo >> Github repository and add your fork as default pull target. We will update >> your fork repository to contain all latest commits from the Pharo repository >> in the branch named 'development'. For latest stable version (Pharo 6) we >> use the master branch. >> In the end we will checkout the repository to a particular commit from >> which the downloaded Pharo 7 image was bootstrapped. Imagine that you have a >> Pharo 7 image that is several days old and the development branch has >> already some commits that change code. If you would take this older image, >> checkout to the development branch and then do your commit, your would >> revert all changes done in not-loaded commits. The other option is to update >> your image to correspond to the repository latest commit which requires >> packages reloading. >> If you checkout to a particular commit, you are in detached HEAD state. In >> this state you cannot do commits directly. You need to firstly create new a >> new branch which we will do anyway. >> >> Evaluate the following code. This functionality will be later direct part >> of Iceberg UI. Do not forget to change the user name. >> >> username := 'YOUR-USER-NAME'. >> repository := IceRepositoryCreator new >> url: 'git@github.com:pharo-project/pharo.git'; >> location: ('pharo-core' asFileReference ensureCreateDirectory); >> subdirectory:'src'; >> createRepository. >> repository checkoutBranch: 'development'. >> repository register. >> >> fork := (IceRemote name: 'myFork' url: ('git@github.com:{1}/pharo.git' >> format: {username})). >> repository addRemote: fork. >> repository pushRemote: fork. >> repository pullRemote: repository origin. >> >> "update fork" >> repository backend pullFrom: repository origin. "use this low-level form >> to prevent packages reloading" >> repository push. >> >> "checkout to the commit from which the image was bootstrapped" >> repository checkoutBranch: (SystemVersion current commitHash). >> >> Use already created clone >> ===================== >> >> This is alternative to the previous step. Let's suppose that you already >> have your local clone. You take some Pharo 7 image and you want to create >> commits. Then you need to create a symlink or move/copy the repository into >> your image directory. Remember, it must be named pharo-core (we do not use >> the name 'pharo' to avoid collision with VM executable). >> >> In this step we will register an existing Pharo repository clone, set your >> fork as the push target, update your fork and then switch to the particular >> commit. >> >> repository := IceRepositoryCreator new >> location: ('pharo-core' asFileReference); >> subdirectory:'src'; >> createRepository. >> repository register. >> >> fork := repository remotes detect: [ :remote | remote remoteName = #myFork >> ]. >> repository pushRemote: fork. >> repository pullRemote: repository origin. >> >> repository checkoutBranch: 'development'. >> repository backend pullFrom: repository origin. >> repository push. >> >> repository checkoutBranch: (SystemVersion current commitHash). >> >> Issue processing >> ===================== >> >> - create new case on FogBugz to get the issue number >> - open Iceberg and from the context menu on the 'pharo' repository do: >> Pharo - Create new branch from FogBugz issue, enter the issue ID and it will >> fill the full branch name for you >> - create your changes (you can do it before the creation of the branch >> too) >> - commit and push your changes in Iceberg, this way you will commit your >> branch to your fork repository. Remember that the Iceberg commit window has >> two buttons, one for local commit, the second for commit with immediate >> push. They can be very long because they contain the full branch (issue) >> name >> - in Iceberg in the 'pharo' repository context menu do: Pharo - Create >> pull request, fill your >> - fill your Github credentials >> - leave the PR title, comment is not required, check the pull request head >> and base. The base MUST be pharo-project/pharo development. Create the pull >> requests >> - go to https://github.com/pharo-project/pharo/pulls, check your pull >> requests and put URL of it into the issue record on FogBugz (as a comment). >> Resolve the issue as Fix review needed >> >> Cheers, >> -- Pavel >> > >

July 11, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Yuriy Tymchuk

This is actually fun. For pharo contributions I just used Iceberg ui without scripting anything and it works absolutely fine. Iceberg has a default location for cloned repositories, and it puts pharo there too Uko > On 4 Jul 2017, at 11:52, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: > > A small update: > > You are not forced to use a 'pharo-core' repository in your image folder if you provide a path to your own clone to the working copies of the bootstrapped packages. This way you can more easily share one local clone of the pharo-project/pharo repository. > For the registration of your local repository use this script: > > target := 'path/to/my/local/repository' asFileReference. > > repository := IceRepositoryCreator new > location: target; > subdirectory:'src'; > createRepository. > repository register. > > fork := repository remotes detect: [ :remote | remote remoteName = #myFork ]. > repository pushRemote: fork. > repository pullRemote: repository origin. > > repository checkoutBranch: 'development'. > repository backend pullFrom: repository origin. > repository push. > > repository checkoutBranch: (SystemVersion current commitHash). > > fileTreeRepository := (MCFileTreeRepository new directory: target / #src; yourself). > repositoryGroup := MCRepositoryGroup withRepositories: { fileTreeRepository. MCCacheRepository uniqueInstance. }. > MCWorkingCopy allManagers > select: [ :wc | (wc repositoryGroup repositories reject: [ :repo | repo isCache ]) isEmpty ] > thenDo: [ :wc | wc repositoryGroup: repositoryGroup ] > > > 2017-06-26 13:14 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>>: > Hi, > > this mail describes how to start to send pull requests to Pharo 7 Github repository from Pharo 7. > > Preparations > ===================== > > - you need to have a Github account and set SSH keys. See https://help.github.com/articles/connecting-to-github-with-ssh/ <https://help.github.com/articles/connecting-to-github-with-ssh/> > - create own pharo-project/pharo repository fork. Go to https://github.com/pharo-project/pharo <https://github.com/pharo-project/pharo>, click on "Fork" button and follow the instructions > > Get Pharo 7 image > ===================== > > The CI jobs for the Pharo 7 defelopment are currently not fully set and we still do not publish Pharo 7 image to files.pharo.org <http://files.pharo.org/> so you cannot get it using zero-conf scripts. But we have a provisional CI job that bootstraps the Pharo 7 image. > > https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ <https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/> > > There download a file named like Pharo7.0-32bit-hash.zip and decompress it. Unlike Pharo 6 images, the archive contains three files. Image, changes and sources. In Pharo 7 you have the sources file for every bootstrapped version. It has a commit hash in the name and it cannot be shared between different Pharo 7 imges, however it can be shared between images that were created as snapshots with the same bootstrapped image as ancestor. > > Create local clone > ===================== > > You need a local clone of the Pharo repository. Because it contains a lot of small files, it is not a good idea to have own clone for every image. You can have only one and share them between images. But because of some current Monticello constraints you need to have the clone placed in the image directory in a folder with name 'pharo-core'. > > In this step we will clone the Pharo repository from pharo-project/pharo Github repository and add your fork as default pull target. We will update your fork repository to contain all latest commits from the Pharo repository in the branch named 'development'. For latest stable version (Pharo 6) we use the master branch. > In the end we will checkout the repository to a particular commit from which the downloaded Pharo 7 image was bootstrapped. Imagine that you have a Pharo 7 image that is several days old and the development branch has already some commits that change code. If you would take this older image, checkout to the development branch and then do your commit, your would revert all changes done in not-loaded commits. The other option is to update your image to correspond to the repository latest commit which requires packages reloading. > If you checkout to a particular commit, you are in detached HEAD state. In this state you cannot do commits directly. You need to firstly create new a new branch which we will do anyway. > > Evaluate the following code. This functionality will be later direct part of Iceberg UI. Do not forget to change the user name. > > username := 'YOUR-USER-NAME'. > repository := IceRepositoryCreator new > url: 'git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git'; > location: ('pharo-core' asFileReference ensureCreateDirectory); > subdirectory:'src'; > createRepository. > repository checkoutBranch: 'development'. > repository register. > > fork := (IceRemote name: 'myFork' url: ('git(a)github.com <mailto:git@github.com>:{1}/pharo.git' format: {username})). > repository addRemote: fork. > repository pushRemote: fork. > repository pullRemote: repository origin. > > "update fork" > repository backend pullFrom: repository origin. "use this low-level form to prevent packages reloading" > repository push. > > "checkout to the commit from which the image was bootstrapped" > repository checkoutBranch: (SystemVersion current commitHash). > > Use already created clone > ===================== > > This is alternative to the previous step. Let's suppose that you already have your local clone. You take some Pharo 7 image and you want to create commits. Then you need to create a symlink or move/copy the repository into your image directory. Remember, it must be named pharo-core (we do not use the name 'pharo' to avoid collision with VM executable). > > In this step we will register an existing Pharo repository clone, set your fork as the push target, update your fork and then switch to the particular commit. > > repository := IceRepositoryCreator new > location: ('pharo-core' asFileReference); > subdirectory:'src'; > createRepository. > repository register. > > fork := repository remotes detect: [ :remote | remote remoteName = #myFork ]. > repository pushRemote: fork. > repository pullRemote: repository origin. > > repository checkoutBranch: 'development'. > repository backend pullFrom: repository origin. > repository push. > > repository checkoutBranch: (SystemVersion current commitHash). > > Issue processing > ===================== > > - create new case on FogBugz to get the issue number > - open Iceberg and from the context menu on the 'pharo' repository do: Pharo - Create new branch from FogBugz issue, enter the issue ID and it will fill the full branch name for you > - create your changes (you can do it before the creation of the branch too) > - commit and push your changes in Iceberg, this way you will commit your branch to your fork repository. Remember that the Iceberg commit window has two buttons, one for local commit, the second for commit with immediate push. They can be very long because they contain the full branch (issue) name > - in Iceberg in the 'pharo' repository context menu do: Pharo - Create pull request, fill your > - fill your Github credentials > - leave the PR title, comment is not required, check the pull request head and base. The base MUST be pharo-project/pharo development. Create the pull requests > - go to https://github.com/pharo-project/pharo/pulls <https://github.com/pharo-project/pharo/pulls>, check your pull requests and put URL of it into the issue record on FogBugz (as a comment). Resolve the issue as Fix review needed > > Cheers, > -- Pavel > >

July 11, 2017