[Pharo-dev] Re: Sockets not working under heavy VM load?

Hi Sven, it seems to be fixed, thank you for your attention. Cheers, -- Pavel čt 28. 9. 2023 v 16:36 odesílatel Sven Van Caekenberghe napsal: > I know this is very old, but is this still an issue today ? > > > On 29 Dec 2021, at 12:30, Pavel Krivanek > wrote: > > > &g

[Pharo-dev] Re: Linux OBS builds updated

ense to create an even more general table that would handle the conversion of any key, including various modifiers. Let's move the conversation to the PR discussion: https://github.com/pharo-project/pharo/pull/12258 -- Pavel > > G > > El 6 ene. 2023, a las 08:53, Pavel Krivanek >

[Pharo-dev] Re: Linux OBS builds updated

ME / PG UP) and (END / PG DN) > They work in Pharo with the FN key to get HOME and END. > > I hope this helps. > > Aik-Siong Koh > > > Pavel Krivanek wrote: > > Hi, in Schmidt, we use Pharo 11 on Windows and Home and End keys work for > us. Tested in the code editor and Ca

[Pharo-dev] Re: Linux OBS builds updated

Hi, in Schmidt, we use Pharo 11 on Windows and Home and End keys work for us. Tested in the code editor and Calypso lists. Do you miss it in some special context, or does it not work for you at all? Do you use some different input methods? Or keyboard layouts are the boring European ones. --

[Pharo-dev] Sockets not working under heavy VM load?

Hi, we have some performance issues with Glorp over P3 and, after some investigation, I have a theory that could explain it. And I would like to know your opinion if it is correct. To reproduce this issue, you can try something easy. Just create a process with normal or higher priority that will

[Pharo-dev] Re: PharoJ now available for Pharo10

I have tested it, but it translated to JavaScript all code in the Pharo image except the project I wanted. What am I doing wrong? The huge GDPR overlay on every image startup is annoying :-( -- Pavel čt 1. 4. 2021 v 13:38 odesílatel Noury Bouraqadi napsal: > Hi everyone, > > We continue to

[Pharo-dev] Pharo on Emscripten (WebAssembly)

Hi, I just want to note that in 2019, I tried to build a Pharo VM to WebAssembly using Emscripten. It was not really working but I was able to, at least, build and run the VM. [image: EmPharo.png] The code is here: https://github.com/pavel-krivanek/EmPharo Maybe someone will be interested

Re: [Pharo-dev] Pharo-dev Digest, Vol 88, Issue 7

o. > > Where is this port? I haven't seen it and it would be great if we > could merge it with the canonical repository at pharo-rdbms/glorp > which has been active lately (I even have a few bugfixes to submit) > It is here: https://github.com/pavel-krivanek/glorp/tree/8.3.1-23-baselin

[Pharo-dev] Pharo key features (document)

Hi, I have created a list of the key Pharo features with some images and animations that should help to explain to public what is cool on Pharo. It is based on a list formerly created for a Wikipedia article. https://github.com/pavel-krivanek/pharoMaterials/blob/master/features

[Pharo-dev] Pharo 8 on SqueakJS

Hi, a small update of Pharo running of SqueakJS: https://pavel-krivanek.github.io/pharo8/pharo.html FileAttributes plugin and file support generally is still not in good shape but inspectors work now and the number of changes to the image was significantly reduced ( https://github.com/pavel

Re: [Pharo-dev] How top report a fix to github of Pharo????

BTW. fix of this issue is already part of this PR that did changes is the Catalog loading: https://github.com/pharo-project/pharo/pull/4943 -- Pavel ne 20. 10. 2019 v 22:07 odesílatel Brainstorms napsal: > Hi Casimiro, > > Since you have

Re: [Pharo-dev] [Pharo 8.0] Build #724: 4287-Integrate-Ring2

No, directly to Pharo (unless it is for older versions), I will add information to the original repository. -- Pavel st 11. 9. 2019 v 16:26 odesílatel Martin Dias napsal: > Nice. Is it decided where should issues and PRs be reported? pharo or > original ring2 repo? > > On Wed, Sep 11, 2019 at

Re: [Pharo-dev] Impossible to create new protocol?

yes, the tagsForAllMethods method now hides protocols without methods: allProtocols select: [ :each | each methods anySatisfy: ... út 13. 8. 2019 v 9:05 odesílatel Pavel Krivanek napsal: > introduced in build.613. This is probably the source of this issue: > https://github.com/pharo-p

Re: [Pharo-dev] Impossible to create new protocol?

introduced in build.613. This is probably the source of this issue: https://github.com/pharo-project/pharo/commit/a0706a080383be50fde8aa90d1709062919d3794 út 13. 8. 2019 v 8:53 odesílatel Pavel Krivanek napsal: > on three days old image (build.610) it worked > > út 13. 8. 2019 v 8:50 o

Re: [Pharo-dev] Impossible to create new protocol?

I'm confirming this issue po 12. 8. 2019 v 21:55 odesílatel ducasse napsal: > Hi > > In latest pharo version (we broke a bit iceberg and it will be fixed) I > cannot add a new protocol. > Nothing happen once I type a new name. > > Is it something that only happen to me? > > S > > > >

Re: [Pharo-dev] Read-only image mode

Pavel Krivanek napsal: > Hi Stef, > > út 9. 7. 2019 v 21:30 odesílatel ducasse > napsal: > >> Pavel >> >> I looked at your PR and I have some questions: >> - could the fileReference have a class/instance var pointing to the store >> instead of havin

Re: [Pharo-dev] Read-only image mode

itely the way to go. > > I hope that the class comment explains it :) > :-) I will improve it > > - Why do you have a class var for each store? and not one single metaclass > inst var in the superclass? > There are no class variables of Store classes. What do you mean, exactly? --

[Pharo-dev] Read-only image mode

Hi, the current Pharo cannot deal very well in situations when you want to run multiple instances from one image file, especially on Windows, which complicates the setup of parallel applications. It is not able to work reasonably on read-only file-systems too. That's why I did the next attempt

[Pharo-dev] DisplayableObject

Hi Stef, I think that the inclusion of DisplayableObject or something like that will not help in better system design. The only thing that should really know about how to generate forms for icons, should be the UI framework. Imagine that we will want to use something like GTK framework with

Re: [Pharo-dev] Contribute to pharo8.0 ?

It is working now again as expected. The only difference is that you need to use "Github-Create new branch for issue..." instead of "Pharo-Create new branch for issue..." for the new issues reported on GitHub. -- Pavel st 30. 1. 2019 v 9:42 odesílatel Guillermo Polito napsal: > Hi, > > there

Re: [Pharo-dev] contribution workflow

You may simply clone your fork because the synchronization between it and the upstream repository is done automatically if you are contributing using Iceberg. When you are creating a branch from your image commit, Iceberg fetches the main Pharo repository to obtain information about the required

Re: [Pharo-dev] Pharo 7 changelog proposal

n entry (that was Pharo 7, right?, maybe my memory is failing). > > Cheers, > Alistair > > On Sun, 23 Dec 2018 at 12:29, Pavel Krivanek > wrote: > > > > Hi, > > > > I'm trying to summarize the changelog for Pharo 7 (based on about 2500 > merged PRs, not co

[Pharo-dev] Pharo 7 changelog proposal

Hi, I'm trying to summarize the changelog for Pharo 7 (based on about 2500 merged PRs, not counting standalone commits to Iceberg and Calypso). If something more should be mentioned, please let me know. Revolutionary kernel changes - bootstrap - modular stateful traits - traits flattening in

[Pharo-dev] [ANN] New window tiling shortcuts

Hello, the latest Pharo 7 includes new window tiling shortcuts that should help you to manage windows position and size without the need of using a mouse. In this description, the key ⌘ has equivalent in Ctrl on Linux and Windows. I need to notice that some nicer key combinations would be chosen

[Pharo-dev] Quick menubar tweak

In the current menu bar in Pharo 7 I miss launcher icons. This is a quick ad-hoc tweak how to add them: MenubarMorph reset. World menubar submorphs second delete. World menubar addMorph: (SimpleButtonMorph new label: '|'; actionSelector: #value; color: Color transparent; borderWidth: 0;

Re: [Pharo-dev] Updated syntax postcard

Thanks to all for feedback. Updated. https://upload.wikimedia.org/wikipedia/commons/a/a7/Pharo_syntax_postcard.svg Related can be found here: https://github.com/pavel-krivanek/pharoMaterials/tree/master/postcard -- Pavel 2018-06-01 13:20 GMT+02:00 Peter Uhnák : > This is a really n

[Pharo-dev] Updated syntax postcard

Hi, for the Wikipedia article I prepared an updated version of Phar syntax postcard: https://upload.wikimedia.org/wikipedia/commons/a/a7/Pharo_syntax_postcard.svg Cheers, -- Pavel

[Pharo-dev] Horrible mess in keyboard modifiers processing

On Linux and Windows, the keyboard usage is very limited, especially in combination with the mouse. There is no way how to invoke any key corresponding to Mac command key (⌘). As result there are is no option how on these platforms select several nonadjacent methods in Calypso to display them at

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

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 native VM. https://pavel-krivanek.github.io/pharo/pharo.html Cheers, -- Pavel

Re: [Pharo-dev] ASK FOR TEST: latest vm

Tested on 32-bit and 64-bit Linux. Everything seems to work well. -- Pavel 2018-05-09 13:36 GMT+02:00 Esteban Lorenzano : > hi, > > I will try to promote new stables. > Can you people try the latest vm and report issues? (linux32 libgit2 > problem should be fixed) > >

Re: [Pharo-dev] Problems with the removal of Nautilus

://pharo.fogbugz.com/f/cases/21827/clean-NautilusRefactoring-menu-entries-for-Nautilus ). So at least from the method extensions point of view, we should be safe. Thanks -- Pavel 2018-05-04 13:30 GMT+02:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > In an old image with Nautilus I did this:

Re: [Pharo-dev] Problems with the removal of Nautilus

or:of: #notifyCritique:AutoFixedFor:)" I will check them and make the issue entries. -- Pavel 2018-05-04 13:08 GMT+02:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > > > 2018-05-04 10:19 GMT+02:00 Guillermo Polito <guillermopol...@gmail.com>: > >> Hi, >&

Re: [Pharo-dev] Problems with the removal of Nautilus

2018-05-04 10:19 GMT+02:00 Guillermo Polito : > Hi, > > I've just tried to create a new package in Calypso and I got bitten by > this: > > https://pharo.fogbugz.com/f/cases/21804/Creating-a- > Package-from-Calypso-produces-DNU > > Creating a new package was an extension

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-03-19

rst class objects in ring? > > On Mon, Mar 26, 2018 at 11:02 AM, Pavel Krivanek <pavel.kriva...@gmail.com > > wrote: > >> 2018-03-26 10:52 GMT+02:00 Stephane Ducasse <stepharo.s...@gmail.com>: >> > Pavel >> > >> > Why we do not know if this

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-03-19

simplifies your life. Because the traits are now a library and anyone can come with its own metaclass that modifies the behavior metamodel, it is reasonable to support it. And anyway, this work is already done ;-) -- Pavel > Stef > > On Mon, Mar 26, 2018 at 10:37 AM, Pavel Krivanek &

[Pharo-dev] Pavel's ChangeLog week of 2018-03-19

Hi, I did some serious Ring 2 refactorings that I wanted to have finished before the integration into Pharo. Because Pharo now starts to support the stateful traits, it needs to be supported by the metamodel too. However, we need to be able to model the images with the old traits as well and from

Re: [Pharo-dev] Error opening Zinc MC repository in latest Pharo 7

way to sync up locally (command line) ? > >> On 13 Mar 2018, at 15:53, Pavel Krivanek <pavel.kriva...@gmail.com> wrote: >> >> Hi, try firstly to register the local Pharo repository. For me it something >> like >> >> location := '/tmp/ramdisk/pharo'. >>

Re: [Pharo-dev] Error opening Zinc MC repository in latest Pharo 7

Hi, try firstly to register the local Pharo repository. For me it something like location := '/tmp/ramdisk/pharo'. (IceRepositoryCreator new location: location asFileReference; subdirectory: 'src'; createRepository) register. --- Pavel 2018-03-13 15:40 GMT+01:00 Sven Van Caekenberghe

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-02-26

2018-03-09 16:47 GMT+01:00 Alistair Grant <akgrant0...@gmail.com>: > Hi Pavel, > > On 9 March 2018 at 16:12, Pavel Krivanek <pavel.kriva...@gmail.com> wrote: >> 2018-03-09 16:02 GMT+01:00 Alistair Grant <akgrant0...@gmail.com>: >>> Hi Pavel, >>&

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-02-26

63c807 > (64 Bit) > > > Cheers, > Alistair > > > > > > > On 5 March 2018 at 10:29, Pavel Krivanek <pavel.kriva...@gmail.com> wrote: >> Hi, >> >> Guille is working on the Iceberg improvements and he wanted to be able to >> open a terminal window

Re: [Pharo-dev] Released versions in Pharo Bootstrap

as far as I understand it, you have this: Calypso v1 - Commander v1 - ClassAnnotations v1 You are working on and you fix a version in ClassAnnotations Calypso v1 - Commander v1 - ClassAnnotations v2 but you still do not want to make it as a release. When rebuilding your image, you

Re: [Pharo-dev] Released versions in Pharo Bootstrap

Hi, it is an issue of Calypso dependencies. I discussed it with Denis before Calypso integration and he would like to change it but, for now, it would make the development for him much harder because he needs a way how to load the latest bleeding edge versions of the packages and no one was able

Re: [Pharo-dev] The 6.1 Space Monkey is unhappy

ignored because of a temporal network issue but for the second time it failed for o good reason and you even didn't know. Cheers, -- Pavel > > Stef > > > On Mon, Mar 5, 2018 at 11:07 AM, Pavel Krivanek > <pavel.kriva...@gmail.com> wrote: >> 2018-03-05 10:54 GMT+01:00 Marcus Denke

Re: [Pharo-dev] The 6.1 Space Monkey is unhappy

2018-03-05 10:54 GMT+01:00 Marcus Denker : > > >> On 5 Mar 2018, at 10:27, Alistair Grant wrote: >> >> Hi Marcus, >> >> On 5 March 2018 at 09:23, Marcus Denker wrote: >>> >>> On 5 Mar 2018, at 09:16, Alistair Grant

[Pharo-dev] Pavel's ChangeLog week of 2018-02-05

Hi, among other less interesting things, I spent some time on existing PosixSharedMemory project. It is a UFFI binding for the LibC methods that provide support for the memory allocation between several separate processes. I significantly improved the performance by implementing the block access.

Re: [Pharo-dev] Iceberg - creating virgin repos

Does it work if you add the package, commit changes (without push) and then in separate step do the push? -- Pavel 2018-02-08 4:28 GMT+01:00 Ben Coman : > If in the System Browser I do and work a bit on it, > then later want to push it to a new github repo, what is the >

Re: [Pharo-dev] Reviewing Changes ?

2018-02-05 13:54 GMT+01:00 Sven Van Caekenberghe : > Hi, > > With pull requests, it is relatively easy to see what changed in GitHub. > > Eg. Marcus' latest fix: > > https://github.com/pharo-project/pharo/pull/797 > > shows 6 files/classes changed, reasonably readable diff. > > How

[Pharo-dev] Pavel's ChangeLog week of 2018-01-29

Hi, on my laptop, I have a 13.3" display with resolution 3200x1800. The value of PPI of this display is 276 and because I'm using Linux that does not provide a simple way how to scale the resolution of a window that does not provide high PPI out of the box, it makes Pharo with the default

Re: [Pharo-dev] MCGitlabRepository Missing

The PR was against a wrong branch. The fixed one is being validated. -- Pavel 2018-02-02 8:17 GMT+01:00 Marcus Denker : > Hi, > > The PR was this: > > https://github.com/pharo-project/pharo/pull/700/files > > It might be that the baseline is not used somehow? > > >> On

[Pharo-dev] Pavel's ChangeLog week of 2018-01-22

Hi, this week not much time left for some interesting work on Pharo. Some notes: With Marcus, we were looking at the resurrecting of the old possibility to place method source code directly into the method trailer so it is stored as byte array at the end of the compiled method. Because no new

[Pharo-dev] Pavel's ChangeLog week of 2018-01-15

Hi, - continuing on Ring 2 integration - work on Magma port to Pharo. It's very far from being in a usable state but some progress has been done: - make packages from the version 1.6-tests loadable, baseline - fix tests for collections (except two weak related) are green - fix indexing

[Pharo-dev] Pavel's ChangeLog week of 2018-01-08

I was continuing on work on Ring 2 integration. The image with replaced Ring versions can be bootstrapped and most of the failing tests are fixed. The most problematic part is Epicea adoption. I improved the optional resolving granularity in Ring 2 and added new cleaning mechanisms of the

Re: [Pharo-dev] Pavel's ChangeLog week of 2017-01-01

ssed in-memory sources are of course not really important. -- Pavel > Stef > > On Mon, Jan 8, 2018 at 4:50 PM, Pavel Krivanek <pavel.kriva...@gmail.com> > wrote: > > > > > > 2018-01-08 16:27 GMT+01:00 Martin Dias <tinchod...@gmail.com>: > >> >

Re: [Pharo-dev] Pavel's ChangeLog week of 2017-01-01

2018-01-08 16:27 GMT+01:00 Martin Dias <tinchod...@gmail.com>: > > > On Mon, Jan 8, 2018 at 6:30 AM, Pavel Krivanek <pavel.kriva...@gmail.com> > wrote: > >> In memory sources file >> - I slightly improved the PR for integration of the source

Re: [Pharo-dev] Pavel's ChangeLog week of 2017-01-01

2018-01-08 10:39 GMT+01:00 Sven Van Caekenberghe <s...@stfx.eu>: > > > > On 8 Jan 2018, at 10:30, Pavel Krivanek <pavel.kriva...@gmail.com> > wrote: > > > > In memory sources file > > - I slightly improved the PR for integration of the

Re: [Pharo-dev] Pavel's ChangeLog week of 2017-01-01

ehh, new year :-D so 2018-01-01 2018-01-08 10:30 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > In memory sources file > - I slightly improved the PR for integration of the sources file inside > the object memory. Now it will be possible to extract them back to the disk

[Pharo-dev] Pavel's ChangeLog week of 2017-01-01

In memory sources file - I slightly improved the PR for integration of the sources file inside the object memory. Now it will be possible to extract them back to the disk from the menu so everything can work as before. I'm not sure if it will be integrated into Pharo 7 or we will wait for Pharo 8

[Pharo-dev] FreeCell resurrection

Hi, I fixed the old FreeCell code from Squeak to be able to run on Pharo 6 and 7. Repository: https://github.com/pavel-krivanek/FreeCell How to load: Metacello new baseline: 'FreeCell'; repository: 'github://pavel-krivanek/FreeCell/src'; load. How to run: FreeCell open. Cheers

Re: [Pharo-dev] PR: Compressed sources inside the object memory

2017-12-28 22:29 GMT+01:00 Denis Kudriashov <dionisi...@gmail.com>: > > > 2017-12-28 20:02 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > >> For string searching in source codes it is 1.5s (external sources) vs >> 3.7s (in image compressed), for reco

Re: [Pharo-dev] PR: Compressed sources inside the object memory

ecute] timeToRun > > > >> >> 2017-12-28 16:21 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: >> >>> >>> >>> 2017-12-28 16:00 GMT+01:00 Denis Kudriashov <dionisi...@gmail.com>: >>> >>>> Nice. >>>> >&g

Re: [Pharo-dev] PR: Compressed sources inside the object memory

s not > complain during the image build though. Still don't know how to get the > trace of the error log. > > Build image is here[1] in case it is useful. > > Hilaire > > [1] https://www.dropbox.com/s/wc18e21p371z28f/DrGeo.app-18.01a.zip?dl=0 > > > > Le 28

Re: [Pharo-dev] PR: Compressed sources inside the object memory

2017-12-28 16:00 GMT+01:00 Denis Kudriashov <dionisi...@gmail.com>: > Nice. > > 2017-12-28 15:50 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > >> Hi, >> >> when the Pharo 7 image is being built on top of the bootstrapped image, >>

[Pharo-dev] PR: Compressed sources inside the object memory

Hi, when the Pharo 7 image is being built on top of the bootstrapped image, all loaded code is placed in the changes file so this process ends with an empty sources file, huge changes file and the image. We condense the sources file for every build so we distribute the Pharo 7 as three files -

Re: [Pharo-dev] Problem with ZipArchive (probably bug due to large file)

Pharo does not support Zip64 file format so it cannot work with big files nor files with huge amount of files. -- Pavel 2017-12-21 12:54 GMT+01:00 Mariano Martinez Peck : > Hi guys, > > I discovered a problem with ZipArchive when using Metacello to download a > zipball of

Re: [Pharo-dev] :: Separator in class names

in the code. > Which would be more confusing and useless then ... > > Bye > T. > > > Gesendet: Donnerstag, 21. Dezember 2017 um 08:25 Uhr > Von: "Pavel Krivanek" <pavel.kriva...@gmail.com> > An: "Pharo Development List" <pharo-dev@lists.phar

Re: [Pharo-dev] :: Separator in class names

Actually I think we do not need any change in the language syntax. Classes can provide information about their prefix and tools can take it into account during displaying it in the lists or code. -- Pavel 2017-12-21 0:35 GMT+01:00 Torsten Bergmann : > Remember this December

Re: [Pharo-dev] Failing tests in #development

The same for https://github.com/pharo-project/pharo/pull/514 :-( 2017-12-18 9:12 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > it was a bad idea to integrate PR 606 [1] about the world menu tooltips > before it was green. Now we have failing tests in the develo

[Pharo-dev] Failing tests in #development

it was a bad idea to integrate PR 606 [1] about the world menu tooltips before it was green. Now we have failing tests in the development branch and validations of new pull requests will fail immediately. Btw. I do not think this test should be in the ReleaseTest because these tests should be

Re: [Pharo-dev] Does pharo build not retry anymore?

The UI Manager problem was fixed by Pablo and Guille -- Pavel 2017-12-16 13:06 GMT+01:00 Stephane Ducasse <stepharo.s...@gmail.com>: > tx pavel > > On Sat, Dec 16, 2017 at 9:25 AM, Pavel Krivanek <pavel.kriva...@gmail.com> > wrote: > >> The problems were

Re: [Pharo-dev] Does pharo build not retry anymore?

The problems were related UIManager initialization and consequences of the opening of the Welcome window. -- Pavel 2017-12-16 9:12 GMT+01:00 Stephane Ducasse <stepharo.s...@gmail.com>: > Pavel what was the problem? > > Stef > > > On Tue, Dec 12, 2017 at 9:34 PM, Pav

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Works for me :-) This update will simplify things a lot because as soon as you create a branch from FogBugz issue, the Iceberg does following [1]: - fetches the pharo-project repository - checkouts to the particular commit from which the image was bootstrapped - creates a new branch That means

Re: [Pharo-dev] Does pharo build not retry anymore?

The variable value was reverted to the original value. Thanks. -- Pavel 2017-12-12 20:13 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > Yes, with Marcus we decreased the retryTimes variable two weeks ago to 1 > because in that time the validations were in really bad shape a

Re: [Pharo-dev] Does pharo build not retry anymore?

Yes, with Marcus we decreased the retryTimes variable two weeks ago to 1 because in that time the validations were in really bad shape and literally every validation failed on some random issue and the retries caused enormous build times. It was producing more troubles than profit. It probably can

Re: [Pharo-dev] Did the selection in Playground or rubric change?

gt; What you see is that we cannot rely on the AST. > Now selecting items is boring. > > Stef > > On Tue, Dec 12, 2017 at 1:47 PM, Pavel Krivanek > <pavel.kriva...@gmail.com> wrote: > > Hi, > > > > Andrew improved that so it now works on AST and provid

Re: [Pharo-dev] Did the selection in Playground or rubric change?

Hi, Andrew improved that so it now works on AST and provides better results. If you have some code where it does not work, please try to describe the particular case so we can fix it. -- Pavel 2017-12-12 13:31 GMT+01:00 Stephane Ducasse : > Hi > > usually in previous

Re: [Pharo-dev] better name for #aggregateRuns:

If short names not work, what about to use something more descriptive like #splitToGroupsThatAlternatelySafisfy: -- Pavel 2017-12-12 10:23 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > Hi, > > do you have some proposals for a better name for the message named > #aggre

Re: [Pharo-dev] better name for #aggregateRuns:

maybe something in the direction of splitOnThresholds:? 2017-12-12 10:38 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: > We already have #splitOn: with slightly different behavior: > > (#(1 2 3 4 1 2 3 5 6 ) splitOn: [ :each | each = 4]) > > So splitOnEach:

Re: [Pharo-dev] better name for #aggregateRuns:

splitWhen: [ :each | each = 4] > > > > Le 12/12/2017 à 10:23, Pavel Krivanek a écrit : > >> Hi, >> >> do you have some proposals for a better name for the message named >> #aggregateRuns? >> >> (#(1 2 3 4 1 2 3 5 6 ) aggregateRuns: [ :each | each = 4])

[Pharo-dev] better name for #aggregateRuns:

Hi, do you have some proposals for a better name for the message named #aggregateRuns? (#(1 2 3 4 1 2 3 5 6 ) aggregateRuns: [ :each | each = 4]) >>> #(#(1 2 3) #(4) #(1 2 3 5 6)). (#(1 2 3 4 1 2 3 4 5 6 ) aggregateRuns: [ :each | each = 4]) >>> #(#(1 2 3) #(4) #(1 2 3) #(4) #(5 6)).

Re: [Pharo-dev] Text Indentation in Pharo editor

2017-12-07 16:19 GMT+01:00 Torsten Bergmann : > Hi, > > in most code editors I know one can select a (multiline) block of > code/text and then hit > TAB to indent and move it from the position to the right side. > > Using SHIFT+TAB one can move it back to the left. In Pharo the

Re: [Pharo-dev] Is Pharo spying on me?

ShoreLIne is already removed from Pharo 7 -- Pavel 2017-12-06 10:43 GMT+01:00 Esteban Lorenzano : > > > > On 6 Dec 2017, at 07:12, Tudor Girba wrote: > > > > Hi, > > > > What exactly are we removing? > > shoreline and QA. > both phd are finished :) >

Re: [Pharo-dev] Is Pharo spying on me?

2017-12-05 20:30 GMT+01:00 Bernhard Pieber : > I just found a file named org.pharo.global-identifiers.ston in my > preferences folder. It contains a #secretUUID and a #computerUUID. :-( What > is this information used for? More importantly, how can I turn it off? > There is

[Pharo-dev] VoxelSpace

Hi, I tried to port and optimize the extremely simple VoxelSpace engine into Pharo. https://github.com/pavel-krivanek/VoxelSpace How to load Metacello new baseline: 'VoxelSpace'; repository: 'github://pavel-krivanek/VoxelSpace/src'; load. How to run Copy maps into the image directory

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

2017-11-19 19:05 GMT+01:00 despotadesdibujau : > Sven Van Caekenberghe-2 wrote > > Great work, Gabriel, thanks for sharing. I have yet to look at what you > > did in detail, but what is your pending issue exactly, because I don't > > understand "the staless image".

Re: [Pharo-dev] Dark Mode List

2017-11-17 16:35 GMT+01:00 Stephane Ducasse : > ahhh. > :) > I think that we should have nice white theme and a nice dark new theme > for Pharo 70. > Because we need to see the difference. Since Pharo 60 was dark by default > Pharo 70 should be white by default so that

Re: [Pharo-dev] undocumented method is quest of comment

https://github.com/pharo-project/pharo/pull/487 2017-11-16 23:32 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > It's not documented because hashing is complex... > The goal is to shuffle the receiver bits and distribute them over the > available 28bits used for hash codes. >

Re: [Pharo-dev] [Pharo-users] why is adding instance variables so slow?

Hi, with Yuriy and Miroslava we have tried to finish a pull request for conversion of rules to Renraku. But we had to face to a strange failing tests. It was not clear on the first sight but these tests were failing because of time-outs. Then we realized that the reason for this may be in big

Re: [Pharo-dev] Stuck trying to contribute

2017-11-15 22:46 GMT+01:00 Alistair Grant : > Hi Sven, > > On 15 November 2017 at 22:27, Sven Van Caekenberghe wrote: > > Alistair, > > > > Are steps 8 & 9 needed, since the latest image should be in sync with > the latest dev version, no ? > > Until the next

Re: [Pharo-dev] Stuck trying to contribute

2017-11-15 22:27 GMT+01:00 Sven Van Caekenberghe : > Alistair, > > Are steps 8 & 9 needed, since the latest image should be in sync with the > latest dev version, no ? > 8) the latest build may not be created from the latest merged commit. This step is not necessary because Iceberg

Re: [Pharo-dev] Stuck trying to contribute

I use something like this: pharoRepository := IceRepository registry detect: [ :each | each name = 'pharo' ]. pharoRepository checkoutBranch: 'development'. pharoRepository backend pullFrom: pharoRepository origin. pharoRepository push. Beware, it switches the branch and you can loose

Re: [Pharo-dev] Pharo6.1 is hangs and then crashes

Thank you for reporting https://pharo.fogbugz.com/f/cases/20691/infinite-recursion-when-evaluating-45-56-matchesRegex-s-d-2 -- Pavel 2017-11-14 10:47 GMT+01:00 Yuriy Babah : > Hi! > I don't know haw important this is, but > > when executing: > ' 45 56' matchesRegex:

[Pharo-dev] Thank you

Hi, yesterday I have seen this interesting talk: https://www.youtube.com/watch?v=VS6IpvTWwkQ=desktop ...where pictures like this were presented:

Re: [Pharo-dev] Pharo6.1 World menu order

2017-11-13 21:02 GMT+01:00 Stephane Ducasse : > I would remove also MC from this list. > Too many items. :) > > For Pharo 7: https://github.com/pharo-project/pharo/pull/478/files -- Pavel > Stef > > On Mon, Nov 13, 2017 at 8:47 PM, Peter Uhnák

Re: [Pharo-dev] Is fileout on the change sorter working in Pharo 70?

I tried it and the file-out looks to work as expected for me. I guess that your troubles can be related to a working directory location. Can you check your working directory path (FileSystem workingDirectory)? -- Pavel 2017-11-08 21:53 GMT+01:00 Stephane Ducasse : > It

Re: [Pharo-dev] How should I load Seaside/Bootstrap in Pharo 7 ?

ility. Because with > flattening you will just has duplication of code for classes and traits but > classes and traits existed in Pharo all the time. So flattened version of > STON will correctly work in older Pharo's. > > I didn't look careful enough to realise you made your own for

Re: [Pharo-dev] [Pharo 7.0-dev] Build #268: 20650-Release-cleanup-failures

This is the Heisenbug - it appears only if you do not add a code to study it. -- Pavel 2017-11-08 13:05 GMT+01:00 : > There is a new Pharo build available! > > The status of the build #268 was: SUCCESS. > > The Pull Request #448 was integrated:

Re: [Pharo-dev] How should I load Seaside/Bootstrap in Pharo 7 ?

I successfully loaded Seaside into minimal Pharo 7 image: http://forum.world.st/Seaside-on-minimal-Pharo-7-0-td4979763.html -- Pavel 2017-11-07 21:11 GMT+01:00 Sven Van Caekenberghe : > Nobody (trying to use|using) Seaside on Pharo 7 ?? > > > On 6 Nov 2017, at 09:51, Sven Van

Re: [Pharo-dev] [Pharo 7.0-dev] Build #265: 20648-Provide-Bitmap-variant-of-Source-Code-fonts

It was stuck on the release cleanup. It is not the only case. Instance of GlobalVariable did not understand #bitAnd: [32] [0mGlobalVariable(Object)>>doesNotUnderstand: #bitAnd: [32] CompiledMethod(CompiledCode)>>numLiterals [32] CompiledMethod(CompiledCode)>>literals [32] [:method | |

Re: [Pharo-dev] STOP THE WORLD FINISHED

2017-11-05 22:17 GMT+01:00 Stephane Ducasse : > Esteban > > when I save code in Tonel I get > > - #category : 'HelpSystem-Core-Builders' > + #category : #HelpSystem-Core-Builders > > and this is not a correct symbol. > > So why do we get broken code? > It is a property

Re: [Pharo-dev] [Pharo-users] [Pharo7.0a] Next batch of enhancements

Ups, my fault. -- Pavel 2017-11-05 12:58 GMT+01:00 Guillermo Polito : > Just a side note, all text preceded by >> in the mail is the original pull > request comment. So it was the PR comment that was wrong. We decided with > Stef to let the comment untouched and not

  1   2   3   4   5   >