[Pharo-dev] Extension methods in p7

I’m about preparing magritte to be loadable in pharo 7. I encountered a bit strange behaviour where I had to take cumbersome measures. Magritte has method extensions that are called e.g. *Magritte-model-builder These methods get loaded but when I commit something all of these methods are to

Re: [Pharo-dev] Mustache bug?

Steph, > Am 13.08.2018 um 18:45 schrieb Stéphane Ducasse : > > Hi > > In pillar we needed variable lookup with Mustache so we used a > https://github.com/Ducasse/Containers-PropertyEnvironment > instead of a simple dictionary. > thanks. Do I understand it correctly that the user has to

Re: [Pharo-dev] [Pharo-users] New Iceberg Version 1.2.1

inal rather than in a Pharo image) >> Should I just remove the /src part, now that my repo has the project >> metadata? >> Also, are more features planned for the .project file? E.g. what about >> storing a default selection for Calypso and the Test Runner in there? >

Re: [Pharo-dev] CI Down

gt; On 8 Aug 2018, at 11:15, Norbert Hartl > <mailto:norb...@hartl.name>> wrote: >> >> The one thing is not be able to run the CI. The bigger problem is that pharo >> is not buildable at all. Can we please move mission critical repos like >> epicea to github? >>

Re: [Pharo-dev] CI Down

The one thing is not be able to run the CI. The bigger problem is that pharo is not buildable at all. Can we please move mission critical repos like epicea to github? Norbert > Am 08.08.2018 um 09:55 schrieb Guillermo Polito : > > Hi all, > > Since yesterday evening, CI is down because of

Re: [Pharo-dev] New Iceberg Version 1.2.1

> Am 07.08.2018 um 16:00 schrieb Guillermo Polito : > > Hi, > > I'll write down some of the reasons of the project's design, like that I can > afterwards copy paste it in the wiki :). > > First, this design did not came up from an egg. We worked on it for about two > months. And it is

Re: [Pharo-dev] New Iceberg Version 1.2.1

Forgot one thing. I find the new project feature quite intrusive. It will add those file to all repos unasked. So I have a lot of dirty projects I have no write access to. How is this supposed to work. Isn’t it better to assume defaults and add an option to add project files? Norbert > Am

Re: [Pharo-dev] New Iceberg Version 1.2.1

Great, thanks! I used 1.2.0 a few days ago and I had some problems: - some repos like voyage had a .properties file in the repo with content „{}“. This made the repo unusable. The only thing noticed is that in the repo view in iceberg the packages were named Voyage-Core.package instead of

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1160: Integrating Iceberg v1.2.1

Is it the case that as soon as a mail like this (let’s assume it would have been a success) arrives at the mailing list there is a new pharo image on get.pharo.org that has it? Norbert > Am 07.08.2018 um 12:07 schrieb ci-pharo-ci-jenki...@inria.fr: > > There is a new

Re: [Pharo-dev] Minheadless trial

What keeps you from doing a pull request to opensmalltalk-vm ? > Am 07.08.2018 um 07:47 schrieb Esteban Lorenzano : > > Hi Ben, > > Sorry for coming here so late, I didn’t see this thread before. > I already have a working minheadless branch that was adapted to Eliot’s > process. > It was

Re: [Pharo-dev] About the infinite debugger

bump > Am 04.07.2018 um 02:28 schrieb Martin McClure : > >> On 07/03/2018 05:02 PM, Martin McClure wrote: >>> On 06/29/2018 07:48 AM, Guillermo Polito wrote: >>> I know that the exception handling/debugging has been modified several >>> times in the latest years (some refactorings, hiding

Re: [Pharo-dev] Problem with zinc 2.9.2

onents-SvenVanCaekenberghe.116 > > stable v 2.9.4 > === > > Please tell us if this works for you > >> On 22 Jul 2018, at 12:10, Norbert Hartl wrote: >> >> Thank you guys! It is really great to see that there are people like Max >> jumping onto problem

Re: [Pharo-dev] Problem with zinc 2.9.2

zip' asFileReference binaryReadStreamDo: [ :s | s >> contents ]. >> Transcript open; show: bytes size; cr. >> 5 seconds asDelay wait. >> Transcript show: ('/tmp/foobar.zip' asFileReference binaryReadStreamDo: [ :s >> | s contents ]) size. >> &g

Re: [Pharo-dev] Problem with zinc 2.9.2

ve/master.zip'; >>>downloadTo: '/tmp/foobar.zip'. >>> bytes := '/tmp/foobar.zip' asFileReference binaryReadStreamDo: [ :s | s >>> contents ]. >>> Transcript open; show: bytes size; cr. >>> 5 seconds asDelay wait. >>> Transcript show: ('/t

Re: [Pharo-dev] IndexedSlots in combination with StatefulTraits

> Am 18.07.2018 um 14:39 schrieb Damien Pollet : > > I understand what slots are, but haven't heard of frames in this context… can > you elaborate ? > +1 Norbert > On Wed, 18 Jul 2018 at 13:44, Reg Krock via Pharo-dev > mailto:pharo-dev@lists.pharo.org>> wrote: > The Slot class

Re: [Pharo-dev] Problem with zinc 2.9.2

something or did you > make a typo ? > > As for #close, it is my understanding that Pharo did a #flush before doing a > #close, but maybe that is no longer true with the new primitive streams, > we'll have to check carefully. > > Good catch. I'll think about your suggestion (

Re: [Pharo-dev] Problem with zinc 2.9.2

> Am 12.07.2018 um 08:05 schrieb Max Leske : > >> On 11 Jul 2018, at 22:44, Norbert Hartl wrote: >> >> Hi Max, >> >> I constructed a case that fails exactly like I experience it. Could you try? >> Just unpack the attachment on a linux, set PHARO

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Max,I constructed a case that fails exactly like I experience it. Could you try? Just unpack the attachment on a linux, set PHARO_VM env to your executable and execute build.shNorbert<> Am 10.07.2018 um 09:17 schrieb Max Leske <maxle...@gmail.com>:On 10 Jul 2018, at 8:48, N

Re: [Pharo-dev] Problem with zinc 2.9.2

> Am 11.07.2018 um 20:19 schrieb Sven Van Caekenberghe : > > > >> On 11 Jul 2018, at 19:50, Norbert Hartl wrote: >> >> Thank you Sven. That fixed my first problem. Sadly the other problem is more >> persitent than this. > > I would guess th

Re: [Pharo-dev] Problem with zinc 2.9.2

ent changed) > === > >> On 10 Jul 2018, at 09:17, Max Leske wrote: >> >> On 10 Jul 2018, at 8:48, Norbert Hartl wrote: >> >>> Max, >>> >>> thanks for taking the effort. >> >> No worries. >> >>> >>>> A

Re: [Pharo-dev] Problem with zinc 2.9.2

o days on that already. Norbert > Max > > > On 9 Jul 2018, at 19:43, Norbert Hartl wrote: > > > >> Am 09.07.2018 um 19:10 schrieb Max Leske : >> >> I checked the Parasol Archive and it does not appear to be in Zip64 format >> (Metacello uses ZipA

Re: [Pharo-dev] Problem with zinc 2.9.2

ing build is the upgrade to zinc 2.9.2. Norbert > I'd debug it myself but I can't run VirtualBox at the moment because I'm on > the macOS beta and it won't start... > > Max > > On 9 Jul 2018, at 18:31, Norbert Hartl wrote: > > Hi Max, > > >> Am 09.07.2018 u

Re: [Pharo-dev] Problem with zinc 2.9.2

is saved, copied to a new name and reopened to load the tests and then it fails. I did try to load the tests in the first run and then it works. I’m running out of ideas thanks, Norbert > Cheers, > Max > > > On 9 Jul 2018, at 17:14, Norbert Hartl wrote: > > With the h

Re: [Pharo-dev] Problem with zinc 2.9.2

m back on pharo6.1 for the time being :( Norbert > Am 07.07.2018 um 13:28 schrieb Norbert Hartl : > > Really? I thought the same but then I didn’t believe it works like that. > > Anyway this would be very easy to solve. We just need to ask Sven if he is > fine with doing an em

Re: [Pharo-dev] Problem with zinc 2.9.2

Really? I thought the same but then I didn’t believe it works like that. Anyway this would be very easy to solve. We just need to ask Sven if he is fine with doing an empty .16 version for Zinc-FileSystem and does an in-place version reset of 2.9.2 or a new 2.9.3. I’m not fully convinced that

Re: [Pharo-dev] Problem with zinc 2.9.2

t for everyone that has a product based on 6.1 and that want to migrate someday to pharo7. This way it is impossible to do it step by step. Norbert >> On 7 Jul 2018, at 12:29, Norbert Hartl wrote: >> >> Can anyone explain how zinc is managed? The package Zinc-FileSystem in ph

Re: [Pharo-dev] Problem with zinc 2.9.2

76f3014de7ca Ancestors: Zinc-FileSystem-SvenVanCaekenberghe.14 patch to dynamically work on older pharo versions How do this packages relate? Norbert > Am 06.07.2018 um 16:34 schrieb Norbert Hartl : > > Sven, > > I use Metacello and that seems to be different in behaviour. I prepared

Re: [Pharo-dev] Problem with zinc 2.9.2

ileSystem-SvenVanCaekenberghe.15Author: SvenVanCaekenbergheTime: 14 March 2018, 2:08:47.155993 pmUUID: 9c55f9cf-c023-0d00-9b4a-76f3014de7caAncestors: Zinc-FileSystem-SvenVanCaekenberghe.14===SvenOn 6 Jul 2018, at 12:50, Norbert Hartl wrote:Bump. I wonder nobody sees the problem. Or do I misunderstand th

Re: [Pharo-dev] Problem with zinc 2.9.2

Bump. I wonder nobody sees the problem. Or do I misunderstand there is something wrong in pharo? Norbert > Am 05.07.2018 um 09:09 schrieb Norbert Hartl : > > Ok, > > I think I’ve found something. If you look at the screenshot (that is my image > from jenkins, 6.1 w

Re: [Pharo-dev] Problem with zinc 2.9.2

HTTPComponents --- cache > Loaded -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 --- > http://mc.stfx.eu/ZincHTTPComponents --- cache > ...finished 2.9.2 > > All unit tests 411 were green. > > #newBinaryFileNamed:do: can be found on the class side of ZnFileSystemUtils

Re: [Pharo-dev] Problem with zinc 2.9.2

o be there? Norbert > Max > >> On 4 Jul 2018, at 17:30, Norbert Hartl wrote: >> >> I tried to see how hard it would be to load my current project in pharo7. >> Cyril helped me to see that I load an old version of zinc and it does not >> work that way. Upgrading

[Pharo-dev] Problem with zinc 2.9.2

I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I don’t fully understand what is

Re: [Pharo-dev] Commenting test classes?

> Am 04.07.2018 um 00:45 schrieb Cyril Ferlicot D. : > > Le 04/07/2018 à 00:39, Tim Mackinnon a écrit : >> Au contraire - when looking at a Test - seeing inline the comment of the >> class to remind me what I’m supposed to be testing is actually quite >> helpful. I fully expect this is where

Re: [Pharo-dev] Commenting test classes?

> Am 03.07.2018 um 22:40 schrieb Tim Mackinnon : > > And/Or we could display some automatic comment text (unless some is provided). > > Somethings like > > Tests for Xxx > > (Xxx comment eg I am class that provides services) > Another example of counter productivity! Norbert > > >

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

> Am 19.06.2018 um 15:22 schrieb Guillermo Polito : > > > On Tue, Jun 19, 2018 at 2:07 PM Norbert Hartl <mailto:norb...@hartl.name>> wrote: > Hi, > > let me wear the project manager hat for a moment. > > let me too, because the fact that I'm younger

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

Hi, let me wear the project manager hat for a moment. > Am 19.06.2018 um 10:59 schrieb Guillermo Polito : > > Hi, > > About why 1.1.1 and not 1.2.0. It’s not about cheap or not, but about > semantics :) for me „caring about semantics“ is just one of the top ten justifications developers use

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

Thanks again for the new things. Just a little maneuver critique. The amount of changes you did should be iceberg 1.2.0 and 1.1.1. Versions are cheap ;) and everything which is not really a hot-fix should be a new minor version. Norbert > Am 18.06.2018 um 17:47 schrieb Guillermo Polito : > >

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

> Am 06.06.2018 um 22:00 schrieb Hernán Morales Durand > : > > Hello Martin, > > 2018-06-05 15:49 GMT-03:00 Martin Dias : >> On Tue, Jun 5, 2018 at 3:30 PM Hernán Morales Durand >> wrote: >>> What are Ombu and Hiedra? >> >> Hello Hernán, this is how I described them: >> >> Ombu: >>

Re: [Pharo-dev] Pharo 10th Anniversary

Happy saphire deprecation day!!! Norbert > Am 30.05.2018 um 10:10 schrieb Sven Van Caekenberghe : > > 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

Re: [Pharo-dev] [ANN] VM for Pharo 6.1 updated

Meaning we can get it via get.pharo.org ?? Norbert > Am 30.05.2018 um 11:54 schrieb Esteban Lorenzano : > > Hello, > > I backported stable VM from Pharo 7 to Pharo 6.1. > It should fix some issues (not listed, because I really don’t know them). > > Let me know if

Re: [Pharo-dev] Beacon for Pharo 7

To be honest you sound a bit harsh. And I‘m not sure I can remember that such kind of arguments have ever been exchanged before something was integrated. You want to have a concrete definition. But you just said you don‘t want the core the rely neither on Beacon nor on Announcements. So maybe

Re: [Pharo-dev] Beacon for Pharo 7

> Am 26.05.2018 um 11:02 schrieb Stephan Eggermont : > > Esteban Lorenzano > wrote: > . >> >> Pillar did not kill Pier. >> Pier was killed by the fact that nobody is using it (then, there is few >> efforts to maintain it). >> which is sad, because Pier

Re: [Pharo-dev] Beacon for Pharo 7

> Am 26.05.2018 um 08:41 schrieb Denis Kudriashov : > > > 2018-05-26 9:30 GMT+03:00 Stephan Eggermont : >> Denis Kudriashov >> wrote: >> > 2018-05-25 20:03 GMT+03:00 Stephan Eggermont >> : >> > >> >> Denis

Re: [Pharo-dev] Beacon for Pharo 7

+1 Norbert > Am 26.05.2018 um 10:57 schrieb Tudor Girba : > > Hi, > > I do not know what you mean by Glamour. Glamour is stable since years. If you > refer to the Glamorous Toolkit, then perhaps the problem comes from the fact > that the existing tools and the new

Re: [Pharo-dev] Beacon for Pharo 7

Really?? Don‘t you think the overhead is massive compared to the gain? Norbert > Am 25.05.2018 um 21:08 schrieb Tudor Girba : > > Hi, > > Yes, we want to have the concrete loggers managed with separate baselines. I > would also put them in individual repositories. > >

Re: [Pharo-dev] feenk log

Very impressive!! Hope Bloc and Brick move along to be included in pharo soon!! Norbert > Am 25.05.2018 um 13:30 schrieb Tudor Girba : > > Hi, > > We were a bit silent the last couple of months. Quite a bit happened in the > meantime, so here is a summary (for more fine

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

Do I get it from get.pharo.org? > Am 09.05.2018 um 14:05 schrieb Pavel Krivanek : > > 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

Re: [Pharo-dev] Fix Base64 madness for good

> Am 10.05.2018 um 21:42 schrieb Sven Van Caekenberghe : > > 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

Re: [Pharo-dev] [Ann] Iceberg 0.7.5

Will it be too hard to do 6.2? I encourage the backport but it will break stuff which is also really annoying. Norbert > Am 03.05.2018 um 17:16 schrieb Guillermo Polito : > > Time for the weekly Iceberg update. > > Iceberg 0.7.5. will be in the next Pharo build. >

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

What do you mean „copy into pharo“?? We have a bootstrap process and Beacon has a baseline. What else needs to be decided? Norbert > Am 26.04.2018 um 16:50 schrieb Denis Kudriashov : > > 2018-04-26 16:27 GMT+02:00 Guillermo Polito

Re: [Pharo-dev] [Pharo 7.0-dev] Build #593: 21390-Do-not-store-any-non-literals-in-the-literal-array

> Am 25.02.2018 um 22:02 schrieb Stephane Ducasse : > > I really like this idea of read only literals :) > Tx for pushing it. +1 > >> On Thu, Feb 22, 2018 at 11:52 AM, Marcus Denker >> wrote: >> This fixes the Reflectivity compiler to not

Re: [Pharo-dev] Linux installation

> Am 23.02.2018 um 05:41 schrieb Sean P. DeNigris : > > I know we've struggled with this over the years, especially with the 32-bit > libs. But now we have a lot of infrastructure that seems to be successfully > building/running the VM on various flavors - OBS, travis,

Re: [Pharo-dev] Ficus question

What is Ficus? Norbert > Am 13.02.2018 um 18:23 schrieb Stephane Ducasse : > > Hi martin > > I would like to know what is the API Ficus uses from TClass. > Do you have an idea? > > > Stef

Re: [Pharo-dev] About method comments

One more reason to do reviews. Now that it is super easy with iceberg there is less reason to do so. Norbert > Am 09.02.2018 um 12:10 schrieb Sven Van Caekenberghe : > > > >> On 9 Feb 2018, at 12:04, Stephane Ducasse wrote: >> >> Hi guys >> >> From

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

Is there a summary what and why the model changed? I’m really interested as you know. And I can tell that there are still things very fishy in the whole process. Norbert > Am 19.01.2018 um 08:39 schrieb Esteban Lorenzano : > > hi :) > >> On 18 Jan 2018, at 18:39,

Re: [Pharo-dev] Pharo Lecture at Tunis next week

> Am 13.01.2018 um 13:36 schrieb Stephane Ducasse : > > Hi guys > > just to tell you that next week I will give a lecture at ENIS at tunis. > 3 full days of Pharo and advanced design. > > Stef +1

Re: [Pharo-dev] Protocol names convention

> Am 13.01.2018 um 13:37 schrieb Alistair Grant : > > Hi Eliot, > > On 13 January 2018 at 12:59, Eliot Miranda wrote: >> >> And it would be nice to have tool support to suggest protocol names to >> maintain consistency so that the same

Re: [Pharo-dev] Blame support P7

> Am 13.01.2018 um 12:39 schrieb Eliot Miranda : > > Hi Stephan, > > >> On Jan 13, 2018, at 2:08 AM, Stephan Eggermont wrote: >> >> Eliot Miranda >> wrote: >>> Isn't it important to preserve the ability to exchange code >>

[Pharo-dev] Protocol names convention

I’m not the biggest fan of method categories/protocols but I try to. What strikes me is the huge mess in names we have. Everytime I create e.g. an initialize method I’m asking myself which is the proper name to choose initialize initializing initialization …. Do we have a convention for this?

Re: [Pharo-dev] Blame support P7

Don‘t you think having Author and timestamps is important? > Am 12.01.2018 um 10:26 schrieb Stephane Ducasse : > > Hi torsten > > we have a super long list of *important* fixes and enhancements to do. > > Stef > >> On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann

[Pharo-dev] Mutation of symbols

What is the purpose of ByteSymbol>>#privateAt:put: ByteSymbol>>#string: WideSymbol>>#privateAt:put: WideSymbol>>#string: ? thanks, Norbert

[Pharo-dev] Calling primitiveFailed

Looking through primitive methods I can see two cases. Most methods seem to call self primitiveFailed at the end of the method. But some as Object>>#at:put: do not. Can I assume that all primitive methods should call primitiveFailed at the end? Norbert

Re: [Pharo-dev] (Morph>>#asDraggableMorph) isPrimitive

Forgot the details. I downloaded image and vm with wget -O- get.pharo.org/70+vm | bash one hour ago. Norbert > Am 06.01.2018 um 13:24 schrieb Norbert Hartl <norb...@hartl.name>: > > Can anyone explain why > > (Morph>>#asDraggableMorph) isPrimitive. > > returns true? > > Norbert

[Pharo-dev] (Morph>>#asDraggableMorph) isPrimitive

Can anyone explain why (Morph>>#asDraggableMorph) isPrimitive. returns true? Norbert

Re: [Pharo-dev] [Pharo-users] Best wishes for 2018

14:04 schrieb Bernhard Pieber <bernh...@pieber.com>: > > And all on one machine?! Wow. > > Happy New Year > Bernhard > >> Am 31.12.2017 um 14:18 schrieb Norbert Hartl <norb...@hartl.name>: >> >> I want to second that. It has been another amazing

Re: [Pharo-dev] [Pharo-users] Best wishes for 2018

I want to second that. It has been another amazing year for pharo. And I think things have changed significantly. So 2018 should be really great! I matched my personal not-to-serious goal # ps aux | grep pharo | wc -l 59 So I have 59 pharo images in production. Next step will be to exceed 100

Re: [Pharo-dev] [Pharo-users] Best wishes for 2018

> Am 29.12.2017 um 10:27 schrieb Esteban Lorenzano : > > Thanks Torsten, > I was about to write a similar mail. > > Thanks to everybody for allow me to be your “guy to hate” :) > I will continue doing my best to make Pharo a better place for everybody, one > step at a

Re: [Pharo-dev] Flexibility of ZnUrl (For Metacello evolution)

> Am 29.12.2017 um 10:35 schrieb Cyril Ferlicot D. : > > Hi, > > In order to improve the usage of Pharo and the git integration there is > some discussions around Metacello in order to be able to: > > - Load a private git project from Metacello API > - Load a project

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

I had that problem when openssl 1.1x library was present and SqueakSSL uses 1.0.2 library. The patch is done by Holger and ready to be integrated. But as always it is close to impossible to having something integrated in the vm. Norbert > Am 22.12.2017 um 16:12 schrieb Torsten Bergmann

Re: [Pharo-dev] Linux vm packages

ly remove it because this is just a pain to maintain a >>> description for system that we cannot even >>> use. >>> >>> >>> >>>> On Sun, Nov 26, 2017 at 1:52 PM, Norbert Hartl <norb...@hartl.name> wrote: >>>> Can

Re: [Pharo-dev] Linux vm packages

in a > description for system that we cannot even > use. > > > >> On Sun, Nov 26, 2017 at 1:52 PM, Norbert Hartl <norb...@hartl.name> wrote: >> Can we change linux installation instructions on the web site? I can't >> believe they aren't there, yet. Her

[Pharo-dev] Credentials for Metacello

I have a very annoying problem with projects referenced in metacello that are private. When I try to use that on jenkins … - I cannot use filetree:// to load the project because the dependent projects are loaded as zip via https and there seems to be no way to specify credentials - when using

Re: [Pharo-dev] About a shared trello board

> Am 13.12.2017 um 10:58 schrieb Stephane Ducasse : > > Hi > > I'm thinking that we are not good at communicating and coordinating effort > I would like start a (read only) and welcome contributions on demand > trello board > so that we know each others on what parts

Re: [Pharo-dev] Epicea feedback - save points

Same for me. I thought the last save point would be the last session in the list but I don‘t think that is really true. So I‘m confused by Epicea, too. Norbert > Am 13.12.2017 um 08:27 schrieb Ben Coman : > > When I'm in need Epicea, the common scenario is that I've

Re: [Pharo-dev] spurious characters in class comments

IMHO this would be the case if the sourde code is written in utf-8 but read in latin1. Norbert > Am 12.12.2017 um 23:41 schrieb Nicolas Cellier > : > > Take a look at Dictionary.class.st for example > >

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

Sorry, I’m not sure what I’ve read but it does not seem to be the mail of Pavel :) Norbert > Am 12.12.2017 um 11:05 schrieb Norbert Hartl <norb...@hartl.name>: > > For me split methods operate on separators which are not included in the > result. So name it splitXXX mig

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

For me split methods operate on separators which are not included in the result. So name it splitXXX might not be the best idea. And I think it should be more explicit. When the matching elements are included in the result it needs to indicate where the are added. So it is rather something like

Re: [Pharo-dev] Weird ZnClient benchmarking result

I like that kind of noise because these numbers are very informative. And they show that pharo can be used in heavy scenarios, too > Am 10.12.2017 um 19:14 schrieb Sven Van Caekenberghe : > > @ Henrik > > Arg, arg, arg, yes of course. > I actually did think about that, but still

Re: [Pharo-dev] How to get rid of empty XML nodes?

and: [ e isEmpty or: [ e isWhitespace ] ] ]) > > So I understand why people are going away from XML. > > Stef > >> On Fri, Dec 8, 2017 at 4:02 PM, Norbert Hartl <norb...@hartl.name> wrote: >> >> >>> Am 08.12.2017 um 14:21 schrieb Stephane Duca

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

> Am 08.12.2017 um 21:24 schrieb Tudor Girba : > > Hi Stef, > > Do you get the debugger issue even in a plain Pharo image? > I do Norbert > Doru > > >> On Dec 8, 2017, at 3:40 PM, Stephane Ducasse wrote: >> >> I would love to have Ctrl E and

Re: [Pharo-dev] How to get rid of empty XML nodes?

> Am 08.12.2017 um 14:21 schrieb Stephane Ducasse : > > Hi monty > > >> On Fri, Dec 8, 2017 at 9:03 AM, monty wrote: >> By "empty XML nodes," do you mean whitespace-only string nodes? > > Yes > >> Those are included because all in-element

Re: [Pharo-dev] I love the launcher!!!!

Maybe we should make the pharo launcher move to opensuse build service as the vm did. This way it would be under the same umbrella and available for the main linux distributions Norbert > Am 30.11.2017 um 12:27 schrieb Christophe Demarey > : > > Hi Eduardo, > >

Re: [Pharo-dev] clarifying pharo crashing issue(s)

It is even crashing headless. I have one jenkins job where the build fails everytime because the vm is crashing. 32 bit runs fine Norbert > Am 27.11.2017 um 09:34 schrieb Thierry Goubier : > > > > 2017-11-27 9:20 GMT+01:00 Tudor Girba : >> Hi,

Re: [Pharo-dev] Pharo 32bit on debian 9 stretch 64bit

Cyril, basically it should much more easy to install the vm on debian than what you described. The problem is that nobody put the updated installation instructions on the web site. Here they are http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo-vm-td4962000.html

[Pharo-dev] Linux vm packages

Can we change linux installation instructions on the web site? I can't believe they aren't there, yet. Here is the description. http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo-vm-td4962000.html

Re: [Pharo-dev] CRC checks of downloads fail really often

Yes, this drives me crazy. You cannot do much or invite people to use it because the download does not work. Sometimes it is really ridiculous. Norbert > Am 09.11.2017 um 10:28 schrieb Guillermo Polito : > > Hi, > > In the travis jobs of many projects (pillar,

Re: [Pharo-dev] about SortFunctions

> Am 07.11.2017 um 11:24 schrieb Denis Kudriashov : > > > 2017-11-07 9:23 GMT+01:00 Nicolas Cellier >: > I have other ideas yet. > > The selector undefinedFirst is good, but the

Re: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

Maybe that is the reason the status is considered a FAILURE? Norbert > Am 03.11.2017 um 13:44 schrieb Torsten Bergmann : > > This build number is red: > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/ > >

Re: [Pharo-dev] [update 6.0] #60519

That is so cool. I think everyone that uses pharo in production appreciates this very much! Norbert > Am 03.11.2017 um 09:57 schrieb Marcus Denker <marcus.den...@inria.fr>: > > > >> On 3 Nov 2017, at 09:50, Norbert Hartl <norb...@hartl.name> wrote: >&

Re: [Pharo-dev] [update 6.0] #60519

Wow! Is there an explanation for that? If this is the pharo6 maintenance I would be very lucky! Too many good things happening here, too less time to spent! Norbert > Am 03.11.2017 um 09:46 schrieb Stephane Ducasse : > > Super cool! > > > On Fri, Nov 3, 2017 at 9:43

Re: [Pharo-dev] Zinc and Zodiac - Synching/Contributing

> Am 28.10.2017 um 11:21 schrieb Sven Van Caekenberghe : > > Torsten, > >> On 26 Oct 2017, at 19:12, Torsten Bergmann wrote: >> >> Hi Sven, >> >> for Zinc there is a new issue: >> >> >> 1. Zinc is using #asBytesDescription. It should not be used as it is >>

Re: [Pharo-dev] [ANN] Iceberg 0.6.2 backported to Pharo 6.1

Super! Thanks for that! Norbert > Am 27.10.2017 um 11:36 schrieb Esteban Lorenzano : > > Hi, > > I backported lastest Iceberg version to Pharo 6.1 to allow people to benefit > for latest changes. > This version has an important amount of tweak and fixes, but most

Re: [Pharo-dev] Github API on github

> Am 26.10.2017 um 15:54 schrieb Esteban Lorenzano <esteba...@gmail.com>: > > > >> On 26 Oct 2017, at 15:51, Norbert Hartl <norb...@hartl.name> wrote: >> >> Now the interesting question >> >> *drumroll* >> >> W

Re: [Pharo-dev] Github API on github

Now the interesting question *drumroll* Will iceberg use this library??? Norbert > Am 26.10.2017 um 15:06 schrieb Tudor Girba : > > Even more awesomeness :). Thanks for doing this! > > Doru > > >> On Oct 26, 2017, at 2:02 PM, Torsten Bergmann

Re: [Pharo-dev] Pharo Process question

But don't complain for the coming weeks about things not working ;) Norbert > Am 25.10.2017 um 12:16 schrieb Stephane Ducasse : > > Thanks guys. > Let us move to tonel :) > So I have to watch out then before pushing the button ;) > Stef > > > On Wed, Oct 25, 2017 at

Re: [Pharo-dev] CI Build order and strange "latest" Pharo 7 effect

> Am 12.10.2017 um 14:23 schrieb Torsten Bergmann : > > Hi, > > today there was an interesting effect visible for the Pharo build on CI for > Pharo 7: > > Esteban merged three contributions for Pharo 7 into #development (see [1]). > All three merges on git triggered the CI. >

Re: [Pharo-dev] State of files.pharo.org

;> Le 5 oct. 2017 à 13:50, Marcus Denker <marcus.den...@inria.fr> a écrit : >> >> >> >> On 5 Oct 2017, at 13:35, Norbert Hartl <norb...@hartl.name> wrote: >> >> I'm trying to download images from files.pharo.org. Either it takes a lot of >>

[Pharo-dev] State of files.pharo.org

I'm trying to download images from files.pharo.org . Either it takes a lot of time or get something like Downloading the latest 70 Image: http://files.pharo.org/get-files/70/pharo.zip error: invalid compressed data to inflate

Re: [Pharo-dev] catalog seems down?

Esteban, this sounds as the catalog will be generated on each request. This is architectural asking for problems. The catalog is updated once per day. At that time the response content of the catalog should be written to a file. The file can be served from a frontend web server. This way it is

Re: [Pharo-dev] Bloc status

> Am 19.09.2017 um 22:50 schrieb Tudor Girba : > > Hi, > > Thanks for the question :). > > Indeed, the summary of Stef is quite good. > > Here are some additions: > - Indeed, Bloc gets stable. Recently, we learned that we can optimize the > layouts even more and Alex

<    1   2   3   4   5   6   7   8   >