Re: [Pharo-dev] [ANN] Migrated Artefact to GitHub

> On 2 Oct 2018, at 10:39, Guillermo Polito wrote: > > Also, everybody seems to assume that it is "really easy to do" in emails. > But nobody is taking the time to do it, so why should I? > > Now apparently you also missed a point in my email: what I did is not > incompatible with migrating

[Pharo-dev] Reach of Iceberg/git/tonel ?

Hi, So the future for Pharo is Iceberg/git/tonel and that is fine. My question however is: if I convert my external libraries to this new format, what is the reach of this new technology ? Can people still load code in older versions of Pharo ? I think 6.x is no problem, but what about earlier

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

I think that would be monty, email addresses (CC-ed) mon...@programmer.net montykam...@gmail.com I should note that he has been very good at maintaining the XML packages (the specs of which are super complex), and as far as I know, the code works under Pharo 7 ... What does not work for you

Re: [Pharo-dev] Esteban's ChangeLog week of 17 September 2018

> On 24 Sep 2018, at 10:01, Esteban Lorenzano wrote: > > > >> On 24 Sep 2018, at 09:11, Sven Van Caekenberghe wrote: >> >> Esteban, >> >>> On 24 Sep 2018, at 08:00, esteba...@gmail.com wrote: >>> >>> *I migrated all [

[Pharo-dev] Top MenuBar does not auto follow font changes

Hi, The Top MenuBar does not seem to auto follow font changes, although it picks them uppitiest when you hide/show the menu bar from the Settings. Sven

Re: [Pharo-dev] [Pharo-users] [ANN] Success story Mobility Map

> On 25 Sep 2018, at 14:39, Norbert Hartl wrote: > > > >> Am 25.09.2018 um 12:52 schrieb Sven Van Caekenberghe : >> >> Wow. Very nice, well done. >> >> Any chance on some more technical details, as in what 'connected by a >> message queu

Re: [Pharo-dev] Fraction and ScaledDecimal should be not be serialized as Float in STON format

> On 18 Sep 2018, at 16:45, Sven Van Caekenberghe wrote: > > Of course, we could also extend the basic number parser and allow the native > (stored) notation > > 1/3 > 3/2s2 > > Note how that last one should use the more exact #storeOn: notation, not the

Re: [Pharo-dev] [ANN] Success story Mobility Map

Wow. Very nice, well done. Any chance on some more technical details, as in what 'connected by a message queue for the communication' exactly means ? How did you approach micro services exactly ? > On 25 Sep 2018, at 12:20, Norbert Hartl wrote: > > As presented on ESUG here is the brief

Re: [Pharo-dev] Files-Core and Zinc-Character-Encoding-Core package load sequence

> On 24 Sep 2018, at 21:55, Alistair Grant wrote: > > Hi Guille, Sven, Esteban and Everyone, > > Can someone (dis)confirm that the Zinc-Character-Encoding-Core package is > considered part of the pharo "core" image? Yes, for me anyway, it is (or should be) part of core. > The reason I ask

Re: [Pharo-dev] Esteban's ChangeLog week of 17 September 2018

Esteban, > On 24 Sep 2018, at 08:00, esteba...@gmail.com wrote: > > *I migrated all [pharo-ide](https://github.com/pharo-ide) projects to > tonel format. > >Harder than it seems, it took me a good bunch of hours. But now is > working. > >This will enhance work/fixes on Calypso.

Re: [Pharo-dev] Fraction and ScaledDecimal should be not be serialized as Float in STON format

Hi Julien, Good and interesting point. Your summary is correct: STON, inheriting from JSON so to speak, only knowns about integer and float numbers. All other Smalltalk numbers get converted, which results in a loss of type and precision. That might not be a perfect situation, but nobody

[Pharo-dev] Confused about FileReference read/write streams

Hi, Since ever (or as far as I can remember), FileReference made a distinction between read and write streams, see #readStream[Do:] and #writeStream[Do:] - these return a ZnCharacterReadStream and ZnCharacterWriteStream in Pharo 7. Along the same lines, #binaryReadStream and #binaryWriteStream

Re: [Pharo-dev] Status fo Stream changes in Pharo 7

> On 6 Sep 2018, at 21:42, Torsten Bergmann wrote: > > Hi, > > In Pharo 7 there were changes applied to rework the streams. I understand > that we might have > reasons to change it - but to me this looks incomplete and not finished. > > For instance "FileStream" is a deprecated class - but

Re: [Pharo-dev] Streams and FileDialog in Pharo 6 and 7

> On 6 Sep 2018, at 21:37, Torsten Bergmann wrote: > > Hi, > > A question to those who worked on the new streams for Pharo 7: > > > In PHARO 6 I used the following expression to open a file dialog and let the > user choose > a binary file: > >s := UITheme builder fileOpen: 'Choose

Re: [Pharo-dev] ZnCharacterEncoder default instances

Hi Alistair, Thanks for the feedback, but consider: count := 1. str := 'test-äöü'. [ count timesRepeat: [ ZnCharacterEncoder utf8 encodeString: str ] ] timeToRunWithoutGC. => 8 #newForEncoding: is indeed slow as it has to look through all known encoders, which also involves a

Re: [Pharo-dev] [Pharo-users] fixing font aliasing/sizing for a specific font

> On 24 Jul 2018, at 11:30, Aliaksei Syrel wrote: > > Hi Peter, > > Thanks for the question and motivation to do a text rendering quality > comparison. > > I think you forgot that Pharo does not support "retina" or "hi-dpi" displays. > Imagine you have a laptop screen with the resolution

Re: [Pharo-dev] Problem with zinc 2.9.2

1 images for building the > deployment artefact. Great! > > thanks, > > Norberr > >> Am 22.07.2018 um 12:59 schrieb Sven Van Caekenberghe : >> >> Done: >> >> === >> Name: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.117 >> Author:

Re: [Pharo-dev] Problem with zinc 2.9.2

t; us a note when you are done! > > thanks again, > > Norbert > >> Am 22.07.2018 um 11:06 schrieb Sven Van Caekenberghe : >> >> Ah, that makes total sense. Great catch. Thank you. >> >> === >> Name: Zinc-FileSystem-SvenVanCaekenberghe.17 >>

Re: [Pharo-dev] Problem with zinc 2.9.2

nt > after loading Zinc-HTTP-SvenVanCaekenberghe.472, which is being loaded by > version 2.9.1 of ConfigurationOfZincHTTPComponents. > > Cheers, > Max > > On 21 Jul 2018, at 17:21, Max Leske wrote: > > Just to be safe, I'll redo my experiment and get back to you. >

Re: [Pharo-dev] Problem with zinc 2.9.2

I tried running Max's snippet (Pharo 6.1 on Ubuntu 16.04 LTS), ZnClient new url: 'https://github.com/zweidenker/Parasol/archive/master.zip'; downloadTo: '/tmp/foobar.zip'. bytes := '/tmp/foobar.zip' asFileReference binaryReadStreamDo: [ :s | s contents ]. Transcript open; show: bytes

Re: [Pharo-dev] ZnUnicodeComposingReadStream?

Alistair, are you aware of the following (article/codebase) ? https://medium.com/concerning-pharo/an-implementation-of-unicode-normalization-7c6719068f43 Due to the size of the full DB it is doubtful it would become a standard part of Pharo though. Sven > On 13 Jul 2018, at 19:46, Alistair

Re: [Pharo-dev] Problem with zinc 2.9.2

> On 12 Jul 2018, at 23:15, Max Leske wrote: > > Hi Norbert, > > I was able to reproduce the problem and then identify the culprit, although > what I don't yet understand is how this is related to the changes in Zinc. > > Anyway, the problem is that the file stream isn't properly flushed

Re: [Pharo-dev] Problem with zinc 2.9.2

s in Pharo 7 and not related to the loading of Zinc. The bug might be a binary/text stream mixup or the usage of deprecated code. > Norbert > >> Am 11.07.2018 um 16:46 schrieb Sven Van Caekenberghe : >> >> FWIW, I created a new #stable version 2.9.3 that includes a newer >> Zinc

Re: [Pharo-dev] Problem with zinc 2.9.2

FWIW, I created a new #stable version 2.9.3 that includes a newer Zinc-FileSystem-SvenVanCaekenberghe.16 - maybe this helps. === Name: Zinc-FileSystem-SvenVanCaekenberghe.16 Author: SvenVanCaekenberghe Time: 11 July 2018, 4:30:36.923152 pm UUID: 830fbcd3-1b2d-0d00-bd45-164704867404 Ancestors:

Re: [Pharo-dev] [Pharo-users] Which command-line handlers do you use most?

> On 9 Jul 2018, at 17:38, Damien Pollet wrote: > > Hi all, > > I'm starting to port / reimplement existing command line handlers using Clap. > There's a dozen, but I wonder which ones are the most relied upon, because > it's a good opportunity for refactoring the command line API as a

Re: [Pharo-dev] Problem with zinc 2.9.2

;> >> $> unzip baseline-of-zincproblem.zip >> $> curl get.pharo.org/64/61 | bash >> $> /Applications/Pharo64.app/Contents/MacOS/Pharo ./Pharo.image eval >> „Metacello new repository: 'filetree://src'; baseline: 'ZincProblem'; load" >> >> Look at ZnCli

Re: [Pharo-dev] Problem with zinc 2.9.2

Norbert, I did (on macOS): $ mkdir pharo61 $ cd pharo61/ $ curl get.pharo.org/61+vm | bash % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 3036 100 30360 0 24386 0

Re: [Pharo-dev] Problem with zinc 2.9.2

How exactly did you load ? On macOS Pharo-7.0+alpha.build.1099.sha.bcfa81fa7b35214eede30962d35d1d547c199989 (64 Bit) I went to the Catalog and loaded the default stable version. Fetched -> ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.115 ---

Re: [Pharo-dev] [Moose-dev] Re: [Pharo-users] [ann] gt documenter

> On 17 Jun 2018, at 15:09, Denis Kudriashov wrote: > > Hi Tudor. > > This is super impressive. +10 > What's next? Do you plan to implement IDE for writing documents, navigation, > refactorings? (senders, renames should find all places in documents) > > 2018-06-13 21:57 GMT+01:00 Tudor

Re: [Pharo-dev] [CI] Cause of the random failures in the CI

Well done. Great work. > On 19 Jun 2018, at 16:55, Cyril Ferlicot D. wrote: > > Hi, > > Since months now there are a lot of random failure on the CI making it > hard to work. > > There is different kind of failures: > - Network problems > - Failing tests > - Incomprehensible problems > > Now

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher v1.2 release

> On 19 Jun 2018, at 16:01, Tudor Girba wrote: > > Great work! Indeed. Thank you. > Doru > > >> On Jun 19, 2018, at 3:55 PM, Christophe Demarey >> wrote: >> >> Hi all, >> >> I just released PharoLauncher 1.2. It includes a new windows installer that >> you can use without

Re: [Pharo-dev] SessionManager Questions

Did you read the very nice class comment ? > On 17 Jun 2018, at 20:20, Sean P. DeNigris wrote: > > What is the SessionManager equivalent to `Smalltalk addToStartupList: self > after: AnotherClass`? > To do it manually, I don't see an easy way to query the priority/category of >

Re: [Pharo-dev] ZnUrl and mailto

I didn't even know that multiple addresses were possible. As you know, URL's can basically be anything, it does not seem possible to handle them all. ZnUrl covers the most common cases, that is already something. Indeed, as you can see from #testMailTo there is basic support for the mailto:

Re: [Pharo-dev] Pharo 7 and Traits ?

> On 14 Jun 2018, at 14:56, Marcus Denker wrote: > > > >> On 14 Jun 2018, at 12:56, Sven Van Caekenberghe wrote: >> >> Bump. >> >>> On 5 Nov 2017, at 23:19, Sven Van Caekenberghe wrote: >>> >>> Hi, >>> &g

Re: [Pharo-dev] Pharo 7 and Traits ?

Bump. > On 5 Nov 2017, at 23:19, Sven Van Caekenberghe wrote: > > Hi, > > So what is the story with Pharo 7 and Traits ? > > I may be wrong, but were they not removed but flattened ? > > How are external libraries that want to support multiple Pharo versio

Re: [Pharo-dev] Weird Warnings at startup

leted system-settings.ston in {preferences}/pharo/7.0 - Hurray for GT Inspectors ;-) Thank you. > On Fri, Jun 8, 2018 at 4:49 PM, Sven Van Caekenberghe wrote: > Hi, > > For a couple of days I am seeing a number of weird warnings at startup (via > Growl/inform). Here is a scre

Re: [Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

But if we can have - the old situation (world menu is click on background) + new task/open window widget - the new task/open window widget + optional 1st special 'start' button (and keep world menu is click on background) - the new task/open window widget + the new menu bar widget that would

Re: [Pharo-dev] Updated syntax postcard

Cool & beautiful ! The $p are good for me. I agree with the other remarks. I would love a big A4 landscape version. > On 1 Jun 2018, at 13:20, Peter Uhnák wrote: > > This is a really nice overview! > > Two "p" characters are rendered weirdly for me (Chrome 66), but the remaining > "p"s are

Re: [Pharo-dev] curious behaviour - disappearing variable scope

There is also #repeat for 'infinite' loops > On 1 Jun 2018, at 10:18, Ben Coman wrote: > > > > On 1 June 2018 at 15:23, Ben Coman wrote: > > > On 1 June 2018 at 14:59, Ben Coman wrote: > I'm curious about the following behaviour... > > "In Playground, first evaluate..." > s := Semaphore

Re: [Pharo-dev] server slow

> On 1 Jun 2018, at 03:55, Ben Coman wrote: > > Server access is very slow for me right now. It took 20 seconds to bring up > the directory index for... > https://files.pharo.org/image > > Is it just me? > cheers -ben Right, but it *is* a directory with 3000 files ...

Re: [Pharo-dev] Image format not recognized

https://pharo.manuscript.com/f/cases/22035/Delete-PNGReadWriter-class-createAFormFrom > On 31 May 2018, at 19:43, Sven Van Caekenberghe wrote: > > Great, so you agree that #createAFormFrom: is a candidate for removal ? > >> On 31 May 2018, at 19:01, Hilaire wrote: >>

Re: [Pharo-dev] Image format not recognized

> On 1 Jun 2018, at 04:58, Ben Coman wrote: > > > > On 1 June 2018 at 03:27, Sven Van Caekenberghe wrote: > > Did you see https://github.com/DraagrenKirneh/PngSuiteExplorer ? We score > 100% on the http://www.schaik.com/pngsuite2011 test suite. > > So woul

Re: [Pharo-dev] Image format not recognized

> On 31 May 2018, at 13:23, Hilaire wrote: > > Oh, but wait PNG reader seems to break now on another part... See screenshot. Did you see https://github.com/DraagrenKirneh/PngSuiteExplorer ? We score 100% on the http://www.schaik.com/pngsuite2011 test suite.

Re: [Pharo-dev] Image format not recognized

Great, so you agree that #createAFormFrom: is a candidate for removal ? > On 31 May 2018, at 19:01, Hilaire wrote: > > This is what I did, But I hope this problem will not hit somewhere else. > > > Le 31/05/2018 à 18:06, Sven Van Caekenberghe a écrit : >> That is

Re: [Pharo-dev] Image format not recognized

rm, right. It is not the responsibility of a system class to do UI for you, I think. > Hilaire > > > Le 31/05/2018 à 16:23, Sven Van Caekenberghe a écrit : >> Hi Hilaire, >> >> On Pharo 7 build 993 it works on both 32 and 64 bits (macOS): >> &

Re: [Pharo-dev] Image format not recognized

Hmm, works for me: Pharo 7.0 Build information: Pharo-7.0+alpha.build.981.sha.5c76a586939f4336b1d3f4f3d47dfecdde90058e (64 Bit) > On 31 May 2018, at 11:23, Hilaire wrote: > > Hi, > > Anyone knows why the former code snippet fail but the later deprecated one > succeed? > > PNGReadWriter

[Pharo-dev] Pharo 10th Anniversary

Hi, This short post by Stéphane Ducasse is worth sharing: https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/ Congratulation ! Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Re: [Pharo-dev] [Pharo-users] pharo location include korean charactor then look is not good.

(i.e. should be further UTF-8 decoded): SmalltalkImage>>#[prim]ImagePath and #vmFileName basically probably every call VirtualMachine>>#getSystemAttribute: what a mess ... > On 25 May 2018, at 10:49, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > We looked at

Re: [Pharo-dev] [Pharo-users] [Ann] Some new iceberg videos

Thanks! > On 24 May 2018, at 10:34, Guillermo Polito wrote: > > AAAnd, I've uploaded some of this things to Iceberg's documentation. > > How to contribute to Iceberg: > https://github.com/pharo-vcs/iceberg/wiki/Contributing-to-Iceberg > Metacello support:

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

kes more sense. > > > > > > Similar duplication exists for FileAlreadyExistsException and > > > FileExists. > > > > > > Thoughts? > > > > > > > Hi Alistar, > > > > See the conversation here: > > > > https:/

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

I vote for the simple names without Exception in them. > On 21 May 2018, at 15:01, Cyril Ferlicot D. wrote: > > Le 21/05/2018 à 14:58, Alistair Grant a écrit : >> Hi Everyone, >> >> Does anyone know the history behind FileDoesNotExist and >> FileDoesNotExistException?

Re: [Pharo-dev] Pharo 7 on SqueakJS (demo)

> On 21 May 2018, at 12:01, Pavel Krivanek wrote: > > Hi, > > with some tweaks mostly related to FFI and fonts, we are able to run Pharo 7 > on SqueakJS VM. > > Do not expect blazing performance. Currently, it is about two orders of > magnitude slower than the

Re: [Pharo-dev] [ANN] Alternative Pharo-contributor tool now explained with videos

> On 18 May 2018, at 12:41, Torsten Bergmann wrote: > > https://github.com/astares/pharo-contributor > > now provides two videos demonstrating how this tool can be used as an > alternative to easily contribute to latest Pharo 7 > > > VIDEO 1 >

Re: [Pharo-dev] [Pharo 7.0-dev] Build #869: 21863-Integrate-Calypso-v0113

> On 11 May 2018, at 09:50, ci-pharo-ci-jenki...@inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #869 was: FAILURE. > > The Pull Request #1327 was integrated: "21863-Integrate-Calypso-v0113" > Pull request url:

Re: [Pharo-dev] Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"

Yeah, I saw that for a while too, but my 64bit P7 VMs from the last couple of days don't do this anymore. I don't know why. > On 10 May 2018, at 23:53, Tim Mackinnon wrote: > > I noticed that recent Pharo 6.1 zero conf downloads show lots of these errors > when you run the

[Pharo-dev] Fix Base64 madness for good

Hi, I propose the following: https://pharo.manuscript.com/f/cases/21870/Fix-Base64-madness-for-good https://github.com/pharo-project/pharo/pull/1331 This is a much needed cleanup, IMHO. It is a breaking change however, since it changes the signature (return type) of an existing method.

Re: [Pharo-dev] [ Umbrella Issue ] Cleanup remaining DeprecatedFileSystem users

> On 9 May 2018, at 16:06, Alistair Grant <akgrant0...@gmail.com> wrote: > > > > On Wed., 9 May 2018, 13:49 Sven Van Caekenberghe, <s...@stfx.eu> wrote: > > > > On 9 May 2018, at 13:41, Thierry Goubier <thierry.goub...@gmail.com> wrote:

Re: [Pharo-dev] [ Umbrella Issue ] Cleanup remaining DeprecatedFileSystem users

> On 9 May 2018, at 13:41, Thierry Goubier <thierry.goub...@gmail.com> wrote: > > 2018-05-09 13:14 GMT+02:00 Sven Van Caekenberghe <s...@stfx.eu>: >> You mean you made a subclass of StandardFilestream yourself ? > > There are a few subclasses o

Re: [Pharo-dev] [ Umbrella Issue ] Cleanup remaining DeprecatedFileSystem users

classes? > > Regards, > > Thierry > > 2018-05-09 11:51 GMT+02:00 Sven Van Caekenberghe <s...@stfx.eu>: >> Hi, >> >> I created the following: >> >> >> https://pharo.manuscript.com/f/cases/21858/Cleanup-remaining-DeprecatedFileSystem-users &

[Pharo-dev] Is #openFileStream:writable: used ?

Hi, Both FileSystem and FileSystemStore (and its subclasses DiskStore and MemoryStore) implement #openFileStream:writable: However, there are no users and putting a breakpoint there does not trigger when reading/writing files. Candidate for removal or not ? Sven

[Pharo-dev] [ Umbrella Issue ] Cleanup remaining DeprecatedFileSystem users

Hi, I created the following: https://pharo.manuscript.com/f/cases/21858/Cleanup-remaining-DeprecatedFileSystem-users This is an umbrella issue, please create sub issues for each set of changes. It is better to work step by step. The package DeprecatedFileSystem contains classes that should

Re: [Pharo-dev] who redefined the #balloonBackgroundColor for dark theme?

Tested manually. OK from this Dark Theme user, Thx ! > On 9 May 2018, at 08:59, Torsten Bergmann wrote: > > Peter wrote: >> Finally, consider the following test: In a dark room, only monitor with >> pharo and dark theme is producing light. Now a large popup with yellow >>

[Pharo-dev] GT Playground Print It Popup unreadeable

In the very latest Pharo 7 using the Dark Theme (with the recent changed Tooltip), the intermediate Popup shown when doing Print It in a GT Playground is unreadable: It seems like it is white on yellow ... Sven

Re: [Pharo-dev] who redefined the #balloonBackgroundColor for dark theme?

> On 8 May 2018, at 15:53, Cyril Ferlicot <cyril.ferli...@gmail.com> wrote: > > > On mar. 8 mai 2018 at 15:37, Sven Van Caekenberghe <s...@stfx.eu> wrote: > Yes, it was changed. > > But for me (latest 7) it is black text on yellow background which is OK. >

Re: [Pharo-dev] who redefined the #balloonBackgroundColor for dark theme?

Yes, it was changed. But for me (latest 7) it is black text on yellow background which is OK. However, Print It in Playground is unreadable now ... > On 8 May 2018, at 15:32, Esteban Lorenzano wrote: > > first time I use the “blame” to actually blame someone ;) > >

Re: [Pharo-dev] fun with announcers

It brings down the number considerably, for me, but not to 30 or so, it is still about 80. I also terminated the update process. > On 8 May 2018, at 11:30, Denis Kudriashov wrote: > > Hi. > > Can you try with clean Calypso cache to check if it is the bad guy? > Close

Re: [Pharo-dev] Failing tests

> On 3 May 2018, at 17:12, Guillermo Polito wrote: > > Hi all, > > There are a couple of Zn tests that are failing not even in the CI but > locally in my machine. > This happens because the tests are trying to do a request to > > encrypted.google.com > > and

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg 0.7.3

Hi Guillermo (et al), I finally found the time to test this new setup and I found it much easier and quite straightforward to make a PR. The new approach, with the simpler UI and lots more dialogs/explanations (and the glossary) is really well done. It felt much better, much higher quality. I

Re: [Pharo-dev] self-backporting from P7 to P6.1

> On 30 Apr 2018, at 11:41, Guillermo Polito wrote: > > Esteban did some work on making a forward compatibility package for spec. > > github://pharo-contributions/Spec70Compatibility:v1.0.0/src > > The idea is that people should do the opposite: code for Pharo7,

Re: [Pharo-dev] Fwd: ByteArray>>at:put:

> On 26 Apr 2018, at 20:19, Stephan Eggermont <step...@stack.nl> wrote: > > Sven Van Caekenberghe <s...@stfx.eu> wrote: >> >> >>> On 26 Apr 2018, at 15:21, Sean P. DeNigris >>> <s...@clipperadams.com> wrote: >>> >>&

Re: [Pharo-dev] Is Beacon still planned to be added to P7?

> On 26 Apr 2018, at 16:50, Denis Kudriashov wrote: > > 2018-04-26 16:27 GMT+02:00 Guillermo Polito : > > > On Mon, Apr 23, 2018 at 1:13 PM, Tudor Girba wrote: > I hope so. Beacon is ready to be integrated, but I do not

Re: [Pharo-dev] Fwd: ByteArray>>at:put:

> On 26 Apr 2018, at 15:21, Sean P. DeNigris wrote: > > Relevant to Pharo? > > From http://forum.world.st/ByteArray-at-put-tp4955848.html : We don't (want to) mix binary and character collections or streams. Going from one to the other is called encoding and decoding,

Re: [Pharo-dev] (no subject)

That's great, Tristan. Welcome ! Have fun. Sven > On 24 Apr 2018, at 17:14, Tristan Debrousse > wrote: > > Hello, I am a student at Université de Bretagne Occidentale (Brest, France) > and I just began an internship project of 6 weeks with Alain Plantec and >

Re: [Pharo-dev] Do we kill the catalog?

> On 24 Apr 2018, at 00:49, monty wrote: > > +1. > > Replacing is sometimes necessary (Sven's stream work is an obvious example), > but I don't see why Nautilus had to be junked rather than gradually evolved > into Calypso. And I don't see why the catalog can't be

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

> On 23 Apr 2018, at 12:03, Esteban Lorenzano <esteba...@gmail.com> wrote: > > > >> On 23 Apr 2018, at 11:46, Marcus Denker <marcus.den...@inria.fr> wrote: >> >> >> >>> On 23 Apr 2018, at 11:38, Sven Van Caekenberghe <s...@stfx.eu

[Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

Hi, I got the new Iceberg working on the latest Pharo 7 (used it to commit something to P3) - authentication should be OK then I guess. It feels much better. I would like to try contributing to Pharo again. Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo been

[Pharo-dev] Using P3 to connect to CockroachDB

Hi, Just a quick note: it is possible to use P3 (the lean and mean PostgreSQL client for Pharo using frontend/backend protocol 3.0, https://github.com/svenvc/P3) to connect to CockroachDB (an SQL database for global cloud services, an open source clone of Google Spannner,

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

ell it should not be, not even in older Pharo versions, as long as you use everything correctly. But the latest changes are a bold step forward. > Thanks a lot! > > Cheers, > Doru > > >> On Apr 20, 2018, at 5:24 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: &g

Re: [Pharo-dev] Spotter search in Catalog ?

ault because people with slow internet connection had issues with it. >> >> Cheers, >> Doru >> >> >>> On Apr 21, 2018, at 9:10 AM, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>> >>> Hi, >>> >>> Do we have a Spotter extension/plu

[Pharo-dev] Spotter search in Catalog ?

Hi, Do we have a Spotter extension/plugin that searches in the Catalog (meta data, descriptions) ? I though that would be really cool and help in discovering packages/frameworks. Sven

[Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

Hi, After the File and Stream changes in Pharo 7, a binary read, resp. write stream from/to a file is actually a ZnBuffered(Read|Write)Stream on a BinaryFileStream. You access these using #binary(Read|Write)Stream[Do:] sent to a FileReference. As minimal streams the API of

Re: [Pharo-dev] Small lint cleanups for Zodiac

Hi Torsten, Sorry for the late reply. Changes accepted upstream. Thank you, Sven > On 4 Apr 2018, at 08:14, Torsten Bergmann wrote: > > Hi Sven, > > attached some small lint cleanups for Zodiac as I was not able to commit to > Zodiac on SThub. > Changes mentioned below.

Re: [Pharo-dev] Do we kill the catalog?

I also think that the catalog is important. If anything is wrong with it we should fix it. The problem is that the catalog is never working well with the current unstable version of Pharo (today 7). Not all package developers take the trouble of checking/porting all the time, that is perfectly

Re: [Pharo-dev] Environment variables encoding ?

's no official > > encoding whatsoever (i.e. they're just bytes with a 0 at the end…) > > > > On 17 April 2018 at 09:36, Sven Van Caekenberghe > > > sven@ > > > wrote: > > > >> Hi, > >> > >> The dictionary > >> > &

Re: [Pharo-dev] Fun with AST evaluation

> On 18 Apr 2018, at 08:34, Marcus Denker wrote: > > > >> On 18 Apr 2018, at 08:11, Marcus Denker wrote: >> >> >> >>> On 18 Apr 2018, at 07:41, Stephane Ducasse wrote: >>> >>> So this means that we could also have

Re: [Pharo-dev] Environment variables encoding ?

Yes, I also saw the *W variants, my initial reaction was that those would make more sense, but it is hard to see all consequences. > On 17 Apr 2018, at 10:49, Henrik Sperre Johansen > wrote: > > primitiveGetenv returns values in the current locale's code page on

Re: [Pharo-dev] Environment variables encoding ?

> On 17 Apr 2018, at 10:40, Nicolai Hess <nicolaih...@gmail.com> wrote: > > > > 2018-04-17 10:05 GMT+02:00 Sven Van Caekenberghe <s...@stfx.eu>: > > > > On 17 Apr 2018, at 09:57, Damien Pollet <damien.pol...@gmail.com> wrote: > > &

Re: [Pharo-dev] Environment variables encoding ?

ow what encoding is being used. Hence my question. > On 17 April 2018 at 09:36, Sven Van Caekenberghe <s...@stfx.eu> wrote: > Hi, > > The dictionary > > OSPlatform current environment > > contains a copy of the OS's environment variables (more correctly of the VM

[Pharo-dev] Environment variables encoding ?

Hi, The dictionary OSPlatform current environment contains a copy of the OS's environment variables (more correctly of the VM process), as key/value pairs. These are obtained via the following system calls: on macOS & *nix LIBC environ on Windows KERNEL32 GetEnvironmentStrings It

Re: [Pharo-dev] pharo-contribution CI machines out of disk space

> On 17 Apr 2018, at 06:02, monty wrote: > > https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console Yes, I know, the whole CI infrastructure is down I guess ...

Re: [Pharo-dev] File path encoding

ues are wrongly decoded - and this is on macOS as well. > On 16 Apr 2018, at 15:10, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > >> On 16 Apr 2018, at 14:51, Alistair Grant <akgrant0...@gmail.com> wrote: >> >> Hi Sven, >> >> On 16 Ap

Re: [Pharo-dev] File path encoding

> On 16 Apr 2018, at 14:51, Alistair Grant <akgrant0...@gmail.com> wrote: > > Hi Sven, > > On 16 April 2018 at 13:57, Sven Van Caekenberghe <s...@stfx.eu> wrote: >> >> Technically, at the File (FilePlugin) level we seem to be able to handle >> p

Re: [Pharo-dev] File path encoding

018, at 13:05, Ben Coman <b...@openinworld.com> wrote: > > On 16 April 2018 at 18:52, Ben Coman <b...@openinworld.com> wrote: >> On 16 April 2018 at 17:51, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>> Hi, >>> >>> Some people ra

[Pharo-dev] File path encoding

Hi, Some people raise issues with file path encoding with non-ASCII characters. The following works fine for me (macOS, Pharo 7, using new File class): "works" (FileLocator temp / 'foo' , 'txt') writeStreamDo: [ :out | out << 'Les élèves Français' ; crlf ]. (FileLocator temp / 'foo' , 'txt')

Re: [Pharo-dev] [Pharo70 alpha] Store settings raise a DNU primFlush

ean P. DeNigris <s...@clipperadams.com>: > Sven Van Caekenberghe-2 wrote > > If we add #closed to ZnBufferedReadStream… > > Would #isClosed be more consistent with the rest of the system? > > > > - > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Re: [Pharo-dev] [Pharo70 alpha] Store settings raise a DNU primFlush

> On 13 Apr 2018, at 22:26, Alistair Grant wrote: > > Hi Stef & Sven, > > On 13 April 2018 at 20:38, Stephane Ducasse wrote: >> Hi >> >> I do not know if this is related to the OldStreamCleaningEffort but >> when I press store settings in the

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

> On 12 Apr 2018, at 03:15, Eliot Miranda <eliot.mira...@gmail.com> wrote: > > Hi Sven, > > On Wed, Apr 11, 2018 at 1:25 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > > On 11 Apr 2018, at 21:44, Stephane Ducasse <stepharo.s...@gmai

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

> On 12 Apr 2018, at 04:07, Ben Coman <b...@openinworld.com> wrote: > > > > On 12 April 2018 at 04:25, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > > On 11 Apr 2018, at 21:44, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > > >

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

> On 12 Apr 2018, at 08:33, Alistair Grant <akgrant0...@gmail.com> wrote: > > Hi Sven, > > On 11 April 2018 at 20:47, Sven Van Caekenberghe <s...@stfx.eu> wrote: >> Alistair, >> >>> On 11 Apr 2018, at 19:42, Sven Van Caekenberghe <s...@stfx.

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

use it to be able to hook/look into running headless server images. For this it is super handy. > Stef > > On Wed, Apr 11, 2018 at 8:47 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: >> Alistair, >> >>> On 11 Apr 2018, at 19:42, Sven Van Caekenberghe <s...

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