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

lovely :) On Mon, Jul 10, 2017 at 8:34 PM, Pavel Krivanek 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

Re: [Pharo-dev] latest 70 and vm

In fact I cannot access it. So when esteban is back and fix the web site we should not forget to update this. On Sun, Jul 9, 2017 at 2:04 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > Tx pavel I will update the website. > > > On Sat, Jul 8, 2017 at 10:06

Re: [Pharo-dev] wrong file on the download

Yes I think so too. So may be we should disable it and put a link to where we can find the latest 70. I still do not find it. On Sun, Jul 9, 2017 at 3:04 AM, Cyril Ferlicot D. <cyril.ferli...@gmail.com> wrote: > Le 08/07/2017 à 20:21, Stephane Ducasse a écrit : >> http://pharo.o

Re: [Pharo-dev] latest 70 and vm

> We are currently not uploading Pharo 7 images to files.pharo.org. They can > can be found here (32-bits): > https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ > > -- Pavel > > > 2017-07-08 21:25 GMT+02:00 Stephane Ducasse <stepharo.s...@gmail.com>: >> &

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Tx Uko. We should improve. On Tue, Jul 11, 2017 at 7:07 PM, Yuriy Tymchuk 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

Re: [Pharo-dev] No Metadata in 7.0

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

Re: [Pharo-dev] Discussing the roadmap

t; >> On Jul 6, 2017, at 1:55 AM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: >> >> We would like to share this list with you and get your feedback and inputs. >> It will be presented and discussed again at ESUG. >> >> Stef on the behalf of the eng

Re: [Pharo-dev] Discussing the roadmap

ath it, or we can add more intellisense > options that match some of the things we see in IntelliJ). > > Tim > > On 6 Jul 2017, at 13:00, Pavel Krivanek <pavel.kriva...@gmail.com> wrote: > > > TxText removal is already done too. > > -- Pavel > > 2017-07

Re: [Pharo-dev] Ideas wanted: "Patterns to sustain feedback loops"

Eliot this is why we created the consortium and are working hard to make sure that the community can pay its engineers. Now marcus is probably looking for feedback patterns in the dev process, idea generation process. Stef On Thu, Jul 6, 2017 at 6:53 PM, Eliot Miranda

Re: [Pharo-dev] Discussing the roadmap

; Hi Stef, > >> On Jul 6, 2017, at 1:55 AM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: >> >> We would like to share this list with you and get your feedback and inputs. >> It will be presented and discussed again at ESUG. >> >> Stef on the

Re: [Pharo-dev] Discussing the roadmap

will be huge. > Of course some things are at the whim of what itches to scratch, but others > we may be able to rally around? > > Tim > > Sent from my iPhone > >> On 7 Jul 2017, at 06:11, Stephane Ducasse <stepharo.s...@gmail.com> wrote: >> >>> On Thu, Jul

Re: [Pharo-dev] Ideas wanted: "Patterns to sustain feedback loops"

> I think this is the major disconnect between the consortium and the > community. Eliot you should pay attention to what you write on public forum. Because this is your perception. For the record, this is since 2012 and previously with the squeak foundation that we created with marcus that we

Re: [Pharo-dev] Pharo contribute page still points to Pharo50Inbox

Thanks hernan. We should update it to refer to github and I do not really know how to update it. On Sat, Jul 8, 2017 at 6:45 PM, Hernán Morales Durand wrote: > http://pharo.org/contribute-propose-fix > > - Also the text to the mailing list is not linked. > - "Select the

Re: [Pharo-dev] Pharo contribute page still points to Pharo50Inbox

I update it to at least make sure that people know that we are in flux :) On Sat, Jul 8, 2017 at 8:04 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > Thanks hernan. > We should update it to refer to github and I do not really know how to > update it. > > On Sat, J

[Pharo-dev] latest 70 and vm

Hi I realized that I forgot where I could find the latest 70 and vm. So I could not update the web site Stef

[Pharo-dev] how to issue a PR that changes package structure?

Hi guys I would like to split or/and create packages. Should I update the Pharo baseline. Stef

[Pharo-dev] wrong file on the download

http://pharo.org/web/download Pharo 7.0 image & changes latest donwloads a Pharo 60 image

Re: [Pharo-dev] Discussing the roadmap

with the form of the rest of the roadmap. > > Inconsistent form makes the document look unprofessional. We need to make it > consistent, we can't let it like that. > > On Sat, Jul 8, 2017 at 8:22 AM, Stephane Ducasse <stepharo.s...@gmail.com> > wrote: >> >> > Actually

Re: [Pharo-dev] Beacon moved to github

We should write the convention somewhere too :) On Sat, Jul 8, 2017 at 12:17 PM, Esteban Lorenzano wrote: > >> On 8 Jul 2017, at 09:29, Tim Mackinnon wrote: >> >> Hi Peter - I just hit this yesterday with your kind help deciphering >> SmalltalkCI, and I

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

Hi mariano what kind of help do you want? Stef On Wed, Jul 12, 2017 at 9:53 PM, Mariano Martinez Peck wrote: > Hi all, > > A while back our team presented Quuve [1], a customizable investment > management ecosystem for professional investors. We also discussed the >

Re: [Pharo-dev] Epicea applying multiple changes

Hi andrei this is strange because I recovered multiple time recently due to some hidden bugs and I did not face the one you report. Stef On Tue, Jul 18, 2017 at 10:48 AM, Andrei Chis wrote: > Hi, > > Is there some known bug in Epicea when applying multiple changes

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

Lionel when the system does find a source, it decompiles the method and this is why you get the code changed. Stef On Tue, Jul 18, 2017 at 7:22 AM, Max Leske wrote: > As Gabriel notes, it looks like your missing the .sources file. I don't know > what pharocloud supports,

Re: [Pharo-dev] PharoSpur32Vm

+ 1 I'm curious to know the libraries that are making more trouble. (I'm thinking about FreeType) because we should throw away. Stef On Fri, Mar 17, 2017 at 12:54 AM, Ben Coman wrote: > Great to hear this news. > Thanks for your efforts Nicolas. > cheers -ben > > On Fri,

Re: [Pharo-dev] [Vm-dev] FileSystem file attributes and #isSymlink patch

Hi Alistair Yes it should become part of the core of Pharo :). Stef On Tue, Jul 25, 2017 at 5:21 PM, Alistair Grant wrote: > Hi David, > > Thanks very much for your follow-up. > > On Mon, Jul 24, 2017 at 07:28:07PM -0400, David T. Lewis wrote: >> >> Hi Alistair, >> >> I

Re: [Pharo-dev] FileSystem file attributes and #isSymlink patch

HI alistair this is supercool that you push this! I mean it for real. Because this simplnk stuff was always getting on our way for scripts. This is really great to see this happening. Stef On Mon, Jul 24, 2017 at 10:43 AM, Max Leske wrote: > Nice work Alistair! > > > > On 24

Re: [Pharo-dev] New Launcher not working (Windows)

tx christophe. Launcher is cool and this is nice to see some effort on that front. Stef On Mon, Jul 24, 2017 at 10:41 AM, Christophe Demarey wrote: > Hi Jan, > > I’m currently updating the Pharo Launcher so that it can determine the right > VM to use to launch an

Re: [Pharo-dev] Improving formatting [was: Big claps for Epicea (small request!)]

> Hi Denis, > you're right, for literal numbers it's been solved in Pharo at least since > 3.0, or maybe even 2.0 (by usage of RB AST I guess). > That's a major improvment over Squeak which is is certainly where I last > encountered the problem. > > Still, formatting does mess line

Re: [Pharo-dev] WorkingSession log

This is really interesting. I would be interested to see why ClassSessionHandler(FreeTypeSettings) takes 2/3 of the computation. Without it we would be 100 ms. Stef On Thu, Jul 27, 2017 at 2:49 PM, Sven Van Caekenberghe wrote: > Hi, > > I instrumented WorkingSession with a log

Re: [Pharo-dev] iceberg / libgit behind proxy

Nicolai here are my setup (done with pavel) for pharo 70 active dev. There are two phases: - once done for all (cloning the repo) - once for each image I download I hope it helps (bt not for the proxy) Stef On Fri, Jul 28, 2017 at 8:02 AM, Stephane Ducasse <stepharo.s...@gmail.com>

Re: [Pharo-dev] WorkingSession log

seems a good reason to not do that, and eliminate the FreeType > stuff for server-side deployment. > > cheers -ben > > On Fri, Jul 28, 2017 at 3:14 AM, Stephane Ducasse <stepharo.s...@gmail.com> > wrote: >> >> This is really interesting. >> I would be inte

Re: [Pharo-dev] iceberg / libgit behind proxy

I did not try behind a proxy. On Thu, Jul 27, 2017 at 10:28 PM, Nicolai Hess wrote: > Anyone got it working to use iceberg /libgit behind a proxy? > > I can access monticello repositories with the right proxy settings. > But using iceberg shows an error about > can not

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

I imagine that hot-fixes means when we found a serious bug in the alpha version and see that it is also in the previous version. Now Hilaire if you want a change to be integrated in Pharo and Pharo 60 for example. - we should have a bug entry on fogbugz (you see when I read the emails I do not

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

Athens is what is in Pharo. I have no idea of the rest. Stef On Wed, Jul 26, 2017 at 4:42 PM, Nicolai Hess <nicolaih...@gmail.com> wrote: > > > 2017-07-26 16:25 GMT+02:00 Stephane Ducasse <stepharo.s...@gmail.com>: >> >> I imagine that hot-fixes means when we fo

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

Thanks Norbert. The consortium paid nicolas to deliver iceberg and esteban to push further for git because the world is moving and git and github support will give us a lot of exposure and a really powerful distributing versionning source control system (even if I really enjoyed MC - it is showing

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Hi pavel Since I want to reuse my clone. I tried the following. But I have no idea about the name of my fork so I put the one of my fork = pharo and it seems that this is what should be done. Now when I execute this script I get 'You already have an Iceberg repository So hat should I do?

Re: [Pharo-dev] Pharo 7 provisional HOWTO

be working. On Fri, Jun 30, 2017 at 10:46 AM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > Ok I try to understand. > I already cloned the github repo and I do not want to be forced to > download all these small files all the time. > I want one place with all the forked cod

Re: [Pharo-dev] Pharo 7 provisional HOWTO

What is the github plugin? an Iceberg Pharo code or a C plugin? On Wed, Jun 28, 2017 at 6:25 PM, Esteban Lorenzano wrote: > > On 28 Jun 2017, at 18:21, Nicolai Hess wrote: > > And if I only want to contribute by reviewing a fix. Do I have to go the >

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

Hi alistair I'm not expert of file system. Now I like your idea to have explicit messages such as canonalize or expand. Stef On Tue, Jun 27, 2017 at 8:56 PM, Alistair Grant wrote: > Hi Sven, > > On Tue, Jun 27, 2017 at 01:31:42PM +0200, Sven Van Caekenberghe wrote: >> Hi

Re: [Pharo-dev] Pharo 7 provisional HOWTO

oject/pharo.git)" ;( On Fri, Jun 30, 2017 at 9:56 AM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > No I did it from a freshly donwloaded image. Pharo7.0-32bit-70f3b57.zip > > On Fri, Jun 30, 2017 at 9:47 AM, Pavel Krivanek > <pavel.kriva...@gmail.com> wrote: &

Re: [Pharo-dev] Pharo 7 provisional HOWTO

rom: repository origin. repository push. repository checkoutBranch: (SystemVersion current commitHash). So I will wait that the system arrives to a state I can work with. Stef On Fri, Jun 30, 2017 at 10:48 AM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > I do not get why &g

Re: [Pharo-dev] about expressions

r scope ? > > On 30 June 2017 at 11:32, Stephane Ducasse <stepharo.s...@gmail.com> wrote: >> >> I do not get why (Yes I know it is because it is not in the syntax >> but it is conceptually not nice). >> >> | d | >> d := Dictionary new. >>

[Pharo-dev] Reflecting on data (literal) object syntax

Hi recently I started to read a book on machine learning and they manipulate dictionary of dictionary. (So I started my own implementation and I will switch to DataFrame). Now it occurred to me that when we program complex objects we do not need a compact literal syntax for our objects. But when

Re: [Pharo-dev] Pharo 7 provisional HOWTO

trying it on an image that already has > the repository set? Even if I tried to use the name 'pharo' instead of > 'myFork', the scripts work. > > Cheers, > -- Pavel > > > 2017-06-30 9:34 GMT+02:00 Stephane Ducasse <stepharo.s...@gmail.com>: >> >> Hi pavel &g

Re: [Pharo-dev] Pharo 7 provisional HOWTO

DoIt ^ repository remotes detect: [ :remote | self halt. remote remoteName = 'pharo' ] remote remoteName returns 'origin' and not the name of the fork so what is upstream? Pharo on github origin? the one local? Stef On Fri, Jun 30, 2017 at 10:04 AM, Stephane Ducasse <stepharo.s...@gmail.

Re: [Pharo-dev] Pharo 7 provisional HOWTO

t; second script that only registers this repository into Iceberg and sets > proper pull and push targets on it. > > Cheers, > -- Pavel > > 2017-06-30 10:04 GMT+02:00 Stephane Ducasse <stepharo.s...@gmail.com>: >> >> So I do not understand >> >> Now if I do >

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

Hi alistair I do not know if this is me that wrote a wrong path class comment. You should consider that theere were nearly no comment at all and I started to try to give more love to this great library. Stef On Tue, Jun 27, 2017 at 8:56 PM, Alistair Grant wrote: > Hi

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

nt0...@gmail.com> wrote: > Hi Stef, > > On Fri, Jun 30, 2017 at 09:46:44AM +0200, Stephane Ducasse wrote: >> Hi alistair >> >> I do not know if this is me that wrote a wrong path class comment. >> You should consider that theere were nearly no comment at all an

[Pharo-dev] about expressions

I do not get why (Yes I know it is because it is not in the syntax but it is conceptually not nice). | d | d := Dictionary new. d at: #top at: #below1 put: 1. d at: #top at: #below1 put: 2. d at: #top at: #below1. is not an expression in Pharo. It means that I can manipulate 1 + 3, x + 3

Re: [Pharo-dev] Reflecting on data (literal) object syntax

for fun I implemented asObjectOf: MCSmalltalkhubRepository owner: 'StephaneDucasse' project: 'asObjectOf' user: '' password: '' On Fri, Jun 30, 2017 at 12:03 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > Hi > > recently I started to read a book on m

[Pharo-dev] About Fogbugz 20165 Support-segment-path-printing

Hi alistair I'm starting to review code that is in the PR pipeline. https://github.com/pharo-project/pharo/pull/126 I noticed that you wrote in the slice Changes since last slice: - Change Path>>fullName to just print the path - Fix absolute path strings - Bug fix Path class>>from:delimiter: -

Re: [Pharo-dev] About Fogbugz 20165 Support-segment-path-printing

ment after I've sent this email in case it causes the >> > response to be blocked. >> > >> > Do you or Pavel have a preference on how to get the PR fixed? I'm >> > happy to generate a new PR if you or Pavel can close the existing one >> > (#126). >&g

Re: [Pharo-dev] Reflecting on data (literal) object syntax

> But what is DataFrame? the new collection done by alesnedr from Lviv. It is really nice but does not solve the problem of the compact syntax. >> >> STON fromString: 'Point[10,20]' >> > Same goes for JSON. > >> We were brainstorming with marcus and we could have a first nice extension: >> >> {

Re: [Pharo-dev] [FT improvements] [GSoC] [guidance needed] move some of the data source responsibilities to the cells

Esteban is moving this week-end from another part of France to Lille so I think that he will get back to live wednesday. On Fri, Jun 30, 2017 at 12:14 PM, Elhamer wrote: > Since there are no response, I am guessing that this design is okay and i > will go for it :D. > >

[Pharo-dev] Baseline question

Hi I 'm trying to define a baseline for our project and I defined it as baseline: spec spec for: #common do: [ spec baseline: 'SmaCC' with: [ spec repository: 'github://ThierryGoubier/SmaCC'; loads: 'SmaCC-GLR-Runtime' ]; package: 'SmaCC-Solidity' "we

Re: [Pharo-dev] Epicea feedback

Thanks martin for your excellent support. What would be nice is to have some menus on the sessions items because often I try to click on them so see what I can do with them. Stef On Tue, Jun 27, 2017 at 4:17 PM, Martin Dias wrote: > Hello Jan, thanks for your feedback. I

Re: [Pharo-dev] Reflecting on data (literal) object syntax

, Norbert Hartl <norb...@hartl.name> wrote: >> >> >>>> Am 30.06.2017 um 21:14 schrieb Stephane Ducasse <stepharo.s...@gmail.com>: >>>> >>>> But what is DataFrame? >>> >>> the new collection done by alesnedr from Lvi

Re: [Pharo-dev] Reflecting on data (literal) object syntax

Back from paris ... Eliot I will implement your proposal I like it. Stef On Sun, Jul 2, 2017 at 3:33 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > Thanks all for the suggestions. > I did another version on the version of igor and I will do another > pass on the a

Re: [Pharo-dev] [ANN] Iceberg 0.5 released

Yes there will be a nice 6.1 because we care of people. Stef On Mon, Jul 3, 2017 at 4:39 PM, Norbert Hartl wrote: > > Am 03.07.2017 um 14:45 schrieb Esteban Lorenzano : > > > On 3 Jul 2017, at 13:32, Norbert Hartl wrote: > > So it is

Re: [Pharo-dev] P6 crashed image

Hi hilaire We should throw away this plugin it is a bug nest. Sorry because it does not solve your problem and this is super annoying for us. Stef On Tue, Jul 4, 2017 at 3:07 AM, David T. Lewis wrote: > Hi Hilaire, > > I do not know if it will help in this case, but

Re: [Pharo-dev] [ANN] for P7, default VM for linux moved to threaded

What are the implications? Stef On Mon, Jul 3, 2017 at 2:39 PM, Esteban Lorenzano wrote: > Hi, > > I made default vm for linux (for P7) the default VM. > > I also updated zeroconf to add a new type of download for linux: the explicit > iTimer heartbeat download. > > > So,

Re: [Pharo-dev] Pharo Launcher

yes latency problem. We should improve on that front :( On Mon, Jul 3, 2017 at 12:35 PM, Serge Stinckwich <serge.stinckw...@gmail.com> wrote: > > > On Thu, Jun 29, 2017 at 2:32 PM, Stephane Ducasse <stepharo.s...@gmail.com> > wrote: >> >> Hi >&

Re: [Pharo-dev] Reflecting on data (literal) object syntax

; > Von: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Im Auftrag von > Norbert Hartl > Gesendet: Montag, 3. Juli 2017 10:28 > An: Pharo Dev <pharo-dev@lists.pharo.org> > Betreff: Re: [Pharo-dev] Reflecting on data (literal) object syntax > > Eliot, > > > Am 01

[Pharo-dev] Simply Happy

Hi pharoing people Just a little word to tell you that I'm super happy about the future of Pharo. The consortium is growing and will probably be able to pay esteban and clement. The roadmap for Pharo 70 is really exciting. The bootstrap, git and the new project in the pipe will boost us. So I

[Pharo-dev] Discussing the roadmap

We would like to share this list with you and get your feedback and inputs. It will be presented and discussed again at ESUG. Stef on the behalf of the engineering team of the Pharo consortium. # Pharo 7 (and 8) potential roadmap This document contains a list of actions that should be done

Re: [Pharo-dev] [ANN] P3, a modern, lean and mean PostgreSQL client for Pharo

Thanks for all your positive energy. Your return of experience on the new tools is great too. I experienced some glitches but this is getting really better and open a lot of possibilities. On Wed, Jun 28, 2017 at 4:49 PM, Sven Van Caekenberghe wrote: > >> On 27 Jun 2017, at 14:56,

[Pharo-dev] Pharo Launcher

Hi where can I find the pharo launcher for the latest version of Pharo? Stef

Re: [Pharo-dev] Early Pull Request Validation Process

Tx guille for looking at this. On Thu, Jun 29, 2017 at 10:39 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi all, > > As some/a lot of you have been asking how to contribute, I'm here to > answer some questions :). > > First of all, integrating fixes in Pharo has been "slowed

Re: [Pharo-dev] Discussing the roadmap

- I’ll take it back, as I went back again just now > and everything I could think of was there (a lot in the news section which I > hadn’t noticed). I do think the download page is a bit confusing but I know > there is work being done on that. > > Tim > > >> On 6 Jul 2017, at 19:1

Re: [Pharo-dev] spec ui as morph

I really hope that we will be able to remove the adapter with brick On Wed, Apr 26, 2017 at 12:38 PM, Peter Uhnak wrote: > #buildWithSpec returns the SpecModel's Morph, which is what you want. > > `model spec instance`, which is the same as calling `model widget` returns >

Re: [Pharo-dev] Pharo Site showing Error 502 - Bad gateway

Esteban is on it. On Mon, Apr 24, 2017 at 1:48 PM, p...@highoctane.be wrote: > Free certs do not always work with older browsers... > > Just sayin' > Phil > > On Mon, Apr 24, 2017 at 1:04 PM, Tim Mackinnon wrote: > >> Hi guys - just noticed the Pharo site

[Pharo-dev] Call for practical tutorials

Hi I love the tutorial of sven on getting a reddit app in 10 classes. https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 Sven I will turn it into a mini booklet. :) And I think that it is really important to have some more. (I'm finishing a new book and the

Re: [Pharo-dev] Pharo 6 screenshot

super cool idea! On Mon, Apr 24, 2017 at 8:58 AM, Pavel Krivanek wrote: > Hi, > > I tried to prepare some "geeky" screenshot for Pharo 6 announcements and > advertisements. > > https://goo.gl/photos/NF5EC6dCinXRWosA9 > > -- Pavel >

[Pharo-dev] Pharodays early rate deadline

Hi the deadline to register to pharodays is approaching. After 29 of April you will pay more and we will not secure room for the diner. Please register Stef

Re: [Pharo-dev] Meanwhile in FogBugz: issue 20000

Tx torsten for these kind words. You got quoted :) https://pharoweekly.wordpress.com/2017/04/28/2-issues-mark-in-fogbugz/ On Thu, Apr 27, 2017 at 5:49 PM, Torsten Bergmann wrote: > Hi, > > our community today hit the 2 issues mark in FogBugz. > >

Re: [Pharo-dev] IMPORTANT: iceberg home changed

esteban do we have a naming convention on github? pharo-xxx? Stef On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano wrote: > As part of our work for release, I changed the home of Iceberg into his > own place: https://github.com/pharo-vcs/iceberg > > So, now to install

Re: [Pharo-dev] Smalltalk Internet Browser

What you can try is to resurrect the old web browser plugin. Now if you want to help why don;t you join the community and help? Stef On Sat, Apr 29, 2017 at 7:00 PM, askoh wrote: > Let me clarify that this browser is to enhance software development and not > for mainstream use

[Pharo-dev] GarageGlorp

Hi for a tutorial I wanted to load Glorp in Pharo 60 as described in the Glorp doc. Metacello new smalltalkhubUser: 'DBXTalk' project: 'Garage'; configuration: 'GarageGlorp'; version: #stable; load. I get an error stating that The symbolic version stable is not defined in the configuration for

[Pharo-dev] Spec menu extensibility (epicea)

Hi guys I would like to know if there is a pattern to build extensible menu in Spec. For example, I extending Epicea to support pillar fileout so that I can turn a coding section into a pillar steps of action. I wanted to extend the epicea browser to get my menu in: But the code is like that:

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names

Hi torsten Yes it sounds good to have MAJOR.MINOR.PATCH/BUILDNUMBER scheme On Fri, Aug 4, 2017 at 9:22 AM, Torsten Bergmann wrote: > Hi Ben, > > reason is that for Pharo 7 currently an sha git hash is used in the file > name > instead of a (more clear) build number. > > See

Re: [Pharo-dev] About cr and lf

:) Me too. Stef On Sat, Aug 5, 2017 at 6:32 PM, Cyril Ferlicot <cyril.ferli...@gmail.com> wrote: > On Sat, Aug 5, 2017 at 6:14 PM, Stephane Ducasse > <stepharo.s...@gmail.com> wrote: >> So one step at a time: >> >> - #cr and #lf just put this charac

Re: [Pharo-dev] About cr and lf

So one step at a time: - #cr and #lf just put this character in the stream. - #newLine put the underlying OS line ending. ( and sorry for the nostalgic but nl sucks and to me this is netherlands and not newline :). Then we should revisit all the cr inside the system and use newline. Then we

Re: [Pharo-dev] About cr and lf

;>>> wrote: >> > >>>>> >> > >>>>> I agree with Pablo, #cr and #lf should not be clever and just be >> > >>>>> names for the carriage return and linefeed characters/codepoints. >> > >>>> >> > &

Re: [Pharo-dev] Having green builds

Yes this is great. Now I will be rerunning the pending fix and integrate the green ones. On Sun, Aug 6, 2017 at 11:00 AM, Guillermo Polito wrote: > Hi all, > > As you all know, we are now building from github. Integrations are made > through pull requests. And pull

[Pharo-dev] FileSystem fix integration

Hi alistair I will go over all the FS changes and push them in Pharo 70. I'm learning the process to integrate fixes and I attract bugs :) Stef

Re: [Pharo-dev] Catalog down

Tx christophe. On Tue, Aug 1, 2017 at 11:23 AM, Torsten Bergmann wrote: > > Thanks! > > > Gesendet: Dienstag, 01. August 2017 um 10:48 Uhr > Von: "Christophe Demarey" > An: "Pharo Development List" > Betreff: Re:

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

> > What is in the super small image? > Is Hermes going to be a generic binary content loader? > > Phil > > On Aug 1, 2017 12:36, "Stephane Ducasse" <stepharo.s...@gmail.com> wrote: >> >> Hi Pavel >> >> This is super excellent! IMPRESSIVE. An

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

t is able to be > bootstrapped under 2 minutes. The minimal system based on the current > code-base that is able to be bootstrapped has about 260kB. > > -- Pavel > > >> >> Is Hermes going to be a generic binary content loader? >> >> Phil >> >> On

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

coupled with Pharo (it can be changed, for example >>>>>>> implementing another loader / installer) and uses only really core >>>>>>> classes. >>>>>>> >>>>>>> Of course it can be extended and used in another Smalltalk d

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

>> - Deprecated FileStream & childs (Moved to Deprecated70) > > *Counts direct references to FileStream & subclasses in a 6.1 Moose image* > Brave souls! It means that Moose will have to update. These classes are not gone just deprecated. > I hope the migration guide will be up to snuff, or I

Re: [Pharo-dev] FileSystem fix integration

gt-and-path-canonicalisation-td4952575.html, > so I might separate that out and make it a separate patch. > > > Cheers, > Alistair > > On 8 August 2017 at 10:27, Stephane Ducasse <stepharo.s...@gmail.com> wrote: >> Hi alistair >> >> I will go over all

Re: [Pharo-dev] FileSystem fix integration

you suggest to drop it and close it? TX On Tue, Aug 8, 2017 at 6:44 PM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > For the moment I'm trying to understand the process and this is not that > simple > because in flux. > > stef > > On Tue, Aug 8, 2017 at 3:24 P

[Pharo-dev] [Pharo 70] build 18 / PR 66

20063-isDeprecated-should-consider-protocol-names Stef

[Pharo-dev] [Pharo 70] build 21 / PR 187

in PR 21 https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/21/ https://pharo.fogbugz.com/f/cases/20295/ Stef

Re: [Pharo-dev] Spec menu extensibility (epicea)

then I've found out that PragmaMenuBuilder is > compatible with Spec. > > Something like... > > builder := PragmaMenuBuilder pragmaKeyword: 'myPragma' model: self. > menu := MenuModel new. > menu fromSpec: builder menuSpec. > > Peter > > > On Sat, Aug 05, 2017

Re: [Pharo-dev] FileSystem fix integration

https://github.com/pharo-project/pharo/pull/133 - https://pharo.fogbugz.com/f/cases/19609/FileReference-base-should-be-before-last-separator https://github.com/pharo-project/pharo/pull/137 Did I miss some others? Stef On Tue, Aug 8, 2017 at 10:27 AM, Stephane Ducasse

[Pharo-dev] [Pharo 70] build 19 / PR-168

https://pharo.fogbugz.com/f/cases/20238/Run-out-of-memory-the-image-hangs-without-out-of-memory-warning https://github.com/pharo-project/pharo/pull/168 Now I get message that I do not understand test failure error from jenkins :(

Re: [Pharo-dev] About cr and lf

Fri, 2017-08-04 at 12:03 +0200, Stephane Ducasse wrote: >> Hi guys >> >> While writing pillar code, I ended up using "stream cr" and it >> worries >> me to still expand usage >> of a pattern I would like to remove. >> >> Let us imagine tha

Re: [Pharo-dev] About cr and lf

, "Esteban Lorenzano" <esteba...@gmail.com> wrote: >> >> >> > On 4 Aug 2017, at 14:06, Stephane Ducasse <stepharo.s...@gmail.com> >> > wrote: >> > >> > Well. This is not implemented like that in Pharo. >> > >> &g

Re: [Pharo-dev] About cr and lf

Hi Guille I agree with you :). Stef On Sun, Aug 6, 2017 at 11:05 AM, Guillermo Polito <guillermopol...@gmail.com > wrote: > > > On Sun, Aug 6, 2017 at 10:54 AM, Stephane Ducasse <stepharo.s...@gmail.com > > wrote: > >> Agreed :) >> >> But so far w

[Pharo-dev] [ Pharo 70 ] Build 43 PR 208 Open-a-package-extending-a-class-via-the-extension-protocol

https://pharo.fogbugz.com/f/cases/20062/Open-a-package-extending-a-class-via-the-extension-protocol https://github.com/pharo-project/pharo/pull/208

<    1   2   3   4   5   6   7   8   9   10   >