[Pharo-dev] Re: [Esug-list] [ANN] Pharo 12 released !

Congratulation once again for this new release. Can‘t wait to put my hands onto it.NorbertAm 26.04.2024 um 12:19 schrieb Esteban Lorenzano : Dear Pharo users and dynamic language lovers: We have released Pharo version 12! What is Pharo? Pharo is a pure

[Pharo-dev] Re: [ANN] Soil release v1

from different DB’s ?I have trouble understanding what you mean. Can you elaborate on that?You mean multiple open databases on the same data on different images? As long as you don‘t use indexes it should work. But I think this is only a good option in very rare cases.Norbert   From: Norbert Hartl

[Pharo-dev] [ANN] Soil release v1

...we said at last ESUG that there will be a release soonish but as usual it doesn't go that fast. But now we are very happy to announce that Soil has a first public release v1. So what is soil? Soil is an object oriented database in pharo . It is transaction based having

[Pharo-dev] Re: [ANN] success story: ApptiveGrid

ally nice project, the front end as well. > > It reminds me a bit of FileMaker, but for the web. > > I am hoping you have commercial success with ApptiveGrid ! > >> On 12 Dec 2023, at 13:02, Norbert Hartl wrote: >> >> I wanted to write this for a very long time now

[Pharo-dev] Re: [Pharo-users] [ANN] Pharo 11 Released !

Hurray! Congats to all of you for the hard work once more to bring it to life. And I like the picture that does not lie about us not having HiDPI  Now I need to upgrade all of my stuff again !! norbert > Am 11.05.2023 um 13:39 schrieb Esteban Lorenzano : > > Dear Pharo users and dynamic

[Pharo-dev] Re: [Pharo-users] This week (13/2023) on the Pharo Issue Tracker

It is just incredible what happens in one week in the pharo community. This is really great! Thank you all for your efforts! Norbert > Am 31.03.2023 um 12:18 schrieb Marcus Denker : > > We again merged ~60 PRs. > > Pharo11 got some bugfixes and last improvements. > > In Pharo12, we

[Pharo-dev] Re: Pharo VM Release - v10.0.0

This is yet again an impressive list of good things. Always appreciated are "Remov*" features :) I'm especially interested in ephemerons and how it improves the weak structures in the image. Hope the image support that makes use of the vm features follows soon. A wish would be to know a bit

[Pharo-dev] Re: [Pharo-users] Pharo VM Release - v9.0.21

Thanks Pablo for the new vm but as well for the update notification. This is super valuable. Norbert > Am 12.12.2022 um 14:30 schrieb teso...@gmail.com: > > Hello, > I have released a new version of the Pharo VM for Pharo 9, Pharo 10 and > Pharo 11. This VM is accessible right now from

[Pharo-dev] Re: [Pharo-users] Omnibase/Monibase repository removal

aked ideas of course. I’ll follow the project, and hope to > contribute. Thanks. I don't how far this project will get. But I have a need and ideas. Just need time :) Let's see where the journey gets. Norbert > > Yanni > > On Wed, Aug 10, 2022 at 7:08 AM Norbert Hartl

[Pharo-dev] Re: [Pharo-users] Omnibase/Monibase repository removal

tiques and laughs are appreciated, Norbert > Am 08.08.2022 um 15:18 schrieb Norbert Hartl : > > To all Omnibase and Monibase users. > > It turned out that neither of those are open source. The author of the > database contacted me clarifying the situation that he has th

[Pharo-dev] Re: Omnibase/Monibase repository removal

> <https://github.com/GemTalk/RemoteServiceReplication> > On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl <mailto:norb...@hartl.name>> wrote: > To all Omnibase and Monibase users. > > It turned out that neither of those are open source. The author of the > database contacted me

[Pharo-dev] Omnibase/Monibase repository removal

To all Omnibase and Monibase users. It turned out that neither of those are open source. The author of the database contacted me clarifying the situation that he has the copyright and never released something open source. This means that I will remove the Omnibase repositories in few weeks

[Pharo-dev] Re: [Pharo-users] Pharo-vm mailing-list

Good move. There should be more interest in vm topics. thanks, Norbert > Am 01.07.2022 um 22:47 schrieb stephane ducasse : > > Hi > > Since a couple of years the Pharo crew has been working on the Pharo-vm and > most of the communication was using internal channels. > > Now that the

[Pharo-dev] Re: About Image Size Pharo9->Pharo11

This is gold. This is the work nobody usually likes to do but is THE apsect for sustainability of a system. Like it!!! thanks, Norbert > Am 11.05.2022 um 09:00 schrieb Marcus Denker : > > Pharo9: 65,8 MB > Pharo10: 57,4 MB > Pharo11: 56,5 MB > > The space saving come from three things: >

[Pharo-dev] Re: [Pharo-users] [ANN] Pharo 10 released!

Hinsen, Kurt > Kilpela, Luz Paz, Marco Rimoldi, Marcus Denker, Martín Dias, Massimo > Nocentini, Max Leske, Maximilian-ignacio Willembrinck Santander, Miguel > Campero, Milton Mamani Torres, Nahuel Palumbo, Norbert Hartl, Norm Green, > Nour Djihan, Noury Bouraqadi, Oleksandr Z

[Pharo-dev] Re: [Pharo-users] [ANN] Pharo 9 released!

ancis > Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni > Corriga, Guille Polito, Himanshu jld, Johan Brichau, Jonathan van Alteren, > Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper Østerbye, Kurt Kilpela, > Laurine Dargaud, Marco Rimoldi, Marcus Denke

[Pharo-dev] Re: [ANN] Freezing Pharo 9 development right now :)

Very good! Does it mean the release will be around august? Norbert > Am 30.04.2021 um 23:04 schrieb Esteban Lorenzano : > > Hi, > > So, today I was checking how much it is missing for release and what is our > status, and I realized if we do not freeze now, we will never release in a >

[Pharo-dev] Re: [Pharo-users] Pharo - GSOC 2021

Great! This is to be accepted as organization? Projects still have to be accepted IIRC. Right? Norbert > Am 11.03.2021 um 07:33 schrieb Serge Stinckwich : > > Dear all, > > great news I want to share with you: Pharo has been selected to be part of > GSOC 2021 > >

Re: [Pharo-dev] Robust Functionality vs. Minimalism (was "Microdown ?")

Sean, > Am 01.08.2020 um 20:23 schrieb Sean P. DeNigris : > > I wonder whether/how-best to apply our principle of minimalism when it > applies to areas of the system that, while critical, seem inherently > non-minimalist e.g. test harnesses, documentation, etc. > > I thought a lot about this

Re: [Pharo-dev] Microdown ?

Microdown is a subset of markdown that can parse to a pillar model. So the discussions about pillar markup have finally settled and we have a syntax format that reads well in ascii which can be used in class comments even if it is a basic image. To integrate pillar core in pharo is not new just

[Pharo-dev] [ANN] PharoPro

Dear community, we are very proud to announce the availability of PharoPro, a company that offers professional support for the pharo platform. Our mission is to enable people and companies to secure their business when building products with pharo. We have been tinkering with the idea creating

Re: [Pharo-dev] OpenSSL binding Re: About strange email related to smalltalkhub read-only on squeak-dev

> Am 04.06.2020 um 02:44 schrieb Pierce Ng : > > On Tue, Jun 02, 2020 at 11:17:30AM +0200, Norbert Hartl wrote: >> PierceNg has an implementation that implements a subset of openssl. >> This implementation is modeled after the library so lots of class >> methods. I

Re: [Pharo-dev] [Pharo-users] About strange email related to smalltalkhub read-only on squeak-dev

Stef, that is a second problem. The main problem to me is solving the crypto stuff once and for all. And then I would like to know why people like Ron say things like this. But yes, shouldn't go without explanation/reaction! Norbert > Am 03.06.2020 um 00:13 schrieb Stéphane Ducasse : > >

Re: [Pharo-dev] About strange email related to smalltalkhub read-only on squeak-dev

Hi Paul, thanks for the info but I won't read it. I try to focus on things that matter. There are too many things that try to distract everyone from producing something helpful. Law suits are IMHO not of that kind. I would rather put some money on the table for someone building proper FFI to

Re: [Pharo-dev] About strange email related to smalltalkhub read-only on squeak-dev

Yes, let us coordinate what to respond. To me this doesn't even sound like Ron. Usually he is a rather quite and reasonable guy. Seems to be a lot of misunderstandings here (again). As I was the one copying the Cryptography package to github it concerns me a bit. I've been remembered now about

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo 8.0 Released!

veira, Andreina Cota, >> Theo Rogliano, Clément Dutriez, Quentin Ducasse, Cyril Ferlicot, Cameron >> Bierwagen, Marek Niepieklo, Clotilde Toullec, Esteban Lorenzano, Vincent >> Blondeau, Danil Osipchuk, Eiichiro Ito, Noury Bouraqadi, Oleksandr Zaytsev, >> Jason Riggs, Alain Pl

Re: [Pharo-dev] New Latest VM - Please Test

ash > > Cheers, > Pablo > > On Sat, Jan 18, 2020 at 7:53 AM Norbert Hartl wrote: >> >> Just a short remark. If you announce something it is good to say how to get >> it. What seems obvious to you is not necessarily obvious for others. >> >> Norbert >>

Re: [Pharo-dev] New Latest VM - Please Test

Just a short remark. If you announce something it is good to say how to get it. What seems obvious to you is not necessarily obvious for others. Norbert > Am 17.01.2020 um 10:49 schrieb "teso...@gmail.com" : > > Hello, > I have just uploaded a new version of the VM as the latest. This >

Re: [Pharo-dev] about signal

> Am 10.01.2020 um 22:32 schrieb ducasse : > >  >> ducasse wrote >>> It was so simple that I preferred to do it myself so like that I will look >>> like a great Pharo contributor. >> >> :) > :) > > Sometimes I do not know if my humour is strange or not :) It is! And you are the only one

Re: [Pharo-dev] Happy new year!

> Am 31.12.2019 um 11:56 schrieb Sven Van Caekenberghe : > >  > >> On 31 Dec 2019, at 11:44, Esteban Lorenzano wrote: >> >> Hi, >> >> Just that, happy new year to everybody! :) >> For 2020, let’s make a great Pharo 8 release and an even better Pharo 9. > > +100 > > And I would also

Re: [Pharo-dev] [Pharo-users] TaskIt

Hi, > Am 16.12.2019 um 11:41 schrieb Santiago Bragagnolo > : > >  > Hi everybody! >We are starting to discuss with norbert about letting taskit to leave my > incubator (my github account to go elsewhere). I have being thinking about it > since long time, since i would like it to allow

Re: [Pharo-dev] Building Pharo VM on Alpine Linux within Docker

This is great! Do you consider to register that on dockerhub? This way a new docker image is built on commit/release. And everyone can use a static url to refer to it. I tried to create a pharo organization on dockerhub but did not find the time to do all of the necessary steps. If both were

Re: [Pharo-dev] Git URL issues

> Am 01.11.2019 um 17:44 schrieb Sven Van Caekenberghe : > > > >> On 31 Oct 2019, at 12:18, Norbert Hartl wrote: >> >> >> >>> Am 31.10.2019 um 12:12 schrieb Sven Van Caekenberghe : >>> >>> >>> >>>>

Re: [Pharo-dev] Git URL issues

> Am 31.10.2019 um 12:12 schrieb Sven Van Caekenberghe : > > > >> On 25 Oct 2019, at 14:49, Sven Van Caekenberghe wrote: >> >> How do you build/deploy non-public production code using the command line ? > > I just learned about the following technique: > > Using SSH agent forwarding > >

Re: [Pharo-dev] Git URL issues

> Am 29.10.2019 um 17:16 schrieb Sven Van Caekenberghe : > > Hi Esteban, > > I tried your snippets, see comments below. > >> On 29 Oct 2019, at 11:07, Esteban Lorenzano wrote: >> >> Hi Sven, >> >> You are facing two different problems at the same time :) >> 1) a problem with Metacello

[Pharo-dev] ESUG Videos

It has been a while since ESUG took place in cologne. We are sorry for the delay in providing the videos of the talks but the end of summer was a busy time for the guy doing the videos and there is quite some material to post-process. Talk videos are prepared now and we start soon to upload

Re: [Pharo-dev] looking for the baselineoffuel

https://github.com/theseion/Fuel/tree/master/repository/BaselineOfFuel.package Notbert > Am 05.10.2019 um 10:05 schrieb ducasse : > > Hi > > I would like to depend on fuel for a project and I cannot find the baselinein > the image. > Is there one somewhere and where can I find it. > > Tx >

Re: [Pharo-dev] About tweets

So now I should complain why my twitter account is not in this list? ;) All pharoers are equal …. Norbert > Am 05.09.2019 um 12:25 schrieb ducasse : > > We are in sync. So I updated the web site to list the main pharo project > and I put a list of other accounts with a disclaimer. > > I can

Re: [Pharo-dev] About tweets

Ok, there seems to be some agreeable sense. Dealing with accounts of people tends to collect opinions and things not related to pharo. We are not interested in these. There are hashtags and mentions for things related to a topic. But a few (!) want to have more control. So using the

Re: [Pharo-dev] [Pharo-users] Information on Spec development

> Am 13.08.2019 um 12:28 schrieb Guillermo Polito : > > Thanks for pushing this Cyril! > This will let us move forward with Iceberg too :) Ah yes, I just wrote on discord. I did a tool in spec2 which I cannot use in the newest pharo. The #asSpecAdapter uses still MorphicGenericAdapter instead

Re: [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

This way cooler than expected. Lot of stuff already done. Great! Norbert > Am 08.08.2019 um 09:53 schrieb "teso...@gmail.com" : > > TL;DR; > == > > For the anxious, you can get real headless vm and image from zero-conf. > > $ wget get.pharo.org/64/80+vmHeadlessLatest | bash > > Zero

Re: [Pharo-dev] Some new bindings for native emulation stuff

There is much sense in this mail, I like it. The unicorn GPL shouldn‘t be an issue in this usage scenario. Well done, Norbert > Am 05.08.2019 um 11:48 schrieb Guillermo Polito : > > >> El 3 ago 2019, a las 13:59, Norbert Hartl escribió: >> >> That

Re: [Pharo-dev] Some new bindings for native emulation stuff

That is pretty awesome. Couldn‘t be an constraint umbrella for VMMaker. This way it would be possible to write tests that check for resulting code. Or writing tests for the JIT (does sista has something like this). Could be one step closer to a deterministic code generation, no? Norbert > Am

Re: [Pharo-dev] P8 + aTalent - aKind

Just if you wonder where this #includesTalent: method is. You can get it from here https://github.com/noha/pharo-talents/tree/api-enhancements <https://github.com/noha/pharo-talents/tree/api-enhancements> Norbert > Am 23.07.2019 um 11:24 schrieb Norbert Hartl : > > I’

Re: [Pharo-dev] Changes proposal on Pre debugger

That‘s definetely worth a try Norbert > Am 10.07.2019 um 20:21 schrieb Cyril Ferlicot D. : > > Hi, > > After talking with Steven (in copy) we agreed on possible improvements > around the pre debugger. I would like to share our vision and check if > the community agrees. > > Context: > > The

[Pharo-dev] Pharo source code formatting guide

Sometimes I wonder when I change a piece of code in pharo if there is an official formatting guide line. Is the formatter in calypso the incarnation of it or how code is supposed to be formatted in the offical image? I just see tons of occurrences where caret immediately follows a token and

Re: [Pharo-dev] [Pharo-users] [ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 bindings)

Great! Can you explain what is there, what somebody can load and what to expect. And even more important: what not to expect? I don’t get any of the essential details from this mail. Norbert > Am 18.04.2019 um 12:08 schrieb Esteban Lorenzano : > > People that assisted to Pharo Days 2019 (or

Re: [Pharo-dev] Roassal Animations

Great! Will this be part of the minimal roassal? That could improve documentation quite a bit. Norbert > Am 18.04.2019 um 01:05 schrieb Alexandre Bergel : > > Hi! > > Just as a follow up, we have a UML diagram builder for Roassal3. > > You can load Roassal3 using: > Metacello new >

Re: [Pharo-dev] [ANN] Pharo 7.0.3

> Am 14.04.2019 um 07:49 schrieb Esteban Lorenzano : > > Hi Tim, > > Is not about subprojects, is about hot fixes :) > Pharo 7 will continue having some updates on critical bugs but it should not > include regular changes (like an update on Calypso). > In that sense, fix #2781 sneaked in

Re: [Pharo-dev] [Pharo-users] [OT] (slightly) What makes other dialects "enjoyable" for you? (WAS: difference between double dispatch...)

> Am 11.04.2019 um 21:35 schrieb Mariano Martinez Peck : > > > >> On Thu, Apr 11, 2019 at 10:54 AM Norbert Hartl wrote: >> >> >>> Am 11.04.2019 um 15:29 schrieb Mariano Martinez Peck >>> : >>> >>> Hi Esteban, &g

Re: [Pharo-dev] [Pharo-users] [OT] (slightly) What makes other dialects "enjoyable" for you? (WAS: difference between double dispatch...)

> Am 11.04.2019 um 15:29 schrieb Mariano Martinez Peck : > > Hi Esteban, > > We talk this privately a couple of weeks ago, but I thought it was worth > writing again here. As for other IDE's being enjoyable, I can only talk about > VASmalltalk. If there is ONE thing I enjoy from it, is the

Re: [Pharo-dev] how implement isAbstract?

> Am 30.03.2019 um 21:05 schrieb Denis Kudriashov : > > We can also look into it from the other side. All these methods are > definitely a kind of code duplication. > I think what we need here is an explicit property for classes. It could be > even part of class definition. I use it myself

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

Yes, please. Do you know https://github.com/peteruhnak/git-migration ? That is a good way to preserve commit history in git. If you have trouble contact me please. Norbert > Am 07.03.2019 um 11:19 schrieb monty : > > I will move it to github, if

Re: [Pharo-dev] [ANN] Pharo 7.0.2 released!

yeah, bright future we come! Norbert > Am 06.03.2019 um 13:01 schrieb Esteban Lorenzano : > > > >> On 6 Mar 2019, at 12:38, Norbert Hartl > <mailto:norb...@hartl.name>> wrote: >> >> How wonderful is that? How much effort it was compared to t

Re: [Pharo-dev] [ANN] Pharo 7.0.2 released!

How wonderful is that? How much effort it was compared to the old process? Norbert > Am 06.03.2019 um 11:32 schrieb Esteban Lorenzano : > > Hi, > > I just made a bugfix release of Pharo: > > v7.0.2 > <513630.jpeg>

Re: [Pharo-dev] managing modification of class initialization methods

> Am 04.03.2019 um 03:46 schrieb Ben Coman : > > In relation to developing sample solutions for an Exercism exercise, the > following observation was made about class initialization... > > > class is initialized on load - and not when you modify it - so this can be > > very confusing for

Re: [Pharo-dev] Proposal to remove [Stream|Collection]>>#write:

> Am 22.02.2019 um 19:45 schrieb Sven Van Caekenberghe : > > > >> On 22 Feb 2019, at 19:39, Stephan Eggermont wrote: >> >> Sven Van Caekenberghe wrote: >> . >>> >>> So I propose to remove [Stream|Collection]>>#write: >>> >>> What say thou ? >> >> Check the selectors used in the latest

Re: [Pharo-dev] [Ann] TelePharo and PharoThings adopted for Pharo 7

> Am 17.02.2019 um 21:03 schrieb Denis Kudriashov : > > Hi. > > I released new versions of TelePharo (v0.3.0) and PharoThings (v0.2.3) > adopted for Pharo 7 changes. > > PharoThings also includes new features from Alex Oliveira: > - Raspberry model B3 > - water alarm example > And few

Re: [Pharo-dev] Esteban's ChangeLog week of 4 February 2019

> Am 11.02.2019 um 10:32 schrieb Guillermo Polito : > > > > On Mon, Feb 11, 2019 at 9:54 AM Norbert Hartl <mailto:norb...@hartl.name>> wrote: > > >> Am 11.02.2019 um 09:22 schrieb Esteban Lorenzano > <mailto:esteba...@gmail.com>>: >>

Re: [Pharo-dev] Esteban's ChangeLog week of 4 February 2019

> Am 11.02.2019 um 09:22 schrieb Esteban Lorenzano : > > > >> On 11 Feb 2019, at 09:20, Nicolas Cellier >> > <mailto:nicolas.cellier.aka.n...@gmail.com>> wrote: >> >> >> >> Le lun. 11 févr. 2019 à 08:45, Norbert Hartl > <m

Re: [Pharo-dev] Esteban's ChangeLog week of 4 February 2019

> Am 11.02.2019 um 08:00 schrieb esteba...@gmail.com: > > Hello! > > This is my weekly ChangeLog, from 4 February 2019 to 10 February 2019. > You can see it in a better format by going here: > http://log.smallworks.eu/web/search?from=4/2/2019=10/2/2019 > > ChangeLog > = > > 9

Re: [Pharo-dev] Roadmap for Pharo 8.0

> Am 08.02.2019 um 16:47 schrieb Serge Stinckwich : > > > > On Fri, Feb 8, 2019 at 4:41 PM Alexandre Bergel via Pharo-dev > mailto:pharo-dev@lists.pharo.org>> wrote: > Dear All, > > At the consortium meeting we discussed the possibility to have a mini-Roassal > included in Pharo8. Many

Re: [Pharo-dev] Roadmap for Pharo 8.0

> Am 08.02.2019 um 14:04 schrieb Alexandre Bergel via Pharo-dev > : > > > Von: Alexandre Bergel > Betreff: Aw: [Pharo-dev] Roadmap for Pharo 8.0 > Datum: 8. Februar 2019 um 14:04:24 MEZ > An: Pharo Development List > > > Dear All, > > At the consortium meeting we discussed the

Re: [Pharo-dev] [ANN] Pharo open documentation

Very good initiative! Did you talk about the catalog, too? This list somehow mirrors the catalog. And as it is done in markdown it does not easily work as a parsable document, does it? Norbert > Am 30.01.2019 um 15:00 schrieb Cyril Ferlicot : > > Hi everyone! > > With some other members of

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

> Am 30.01.2019 um 20:23 schrieb ducasse : > > it means this is a call for fork :) > No! A fork from something not github to github is contraproductive. Norbert >>> On 30 Jan 2019, at 16:58, Norbert Hartl wrote: >>> >>> >>> >>

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

> Am 30.01.2019 um 16:13 schrieb Sven Van Caekenberghe : > > > >> On 3 Oct 2018, at 07:43, monty wrote: >> >> I am the principal maintainer of those projects, but any PharoExtras dev can >> contribute. And the blog below (which I plan on updating) provides >> additional information on

Re: [Pharo-dev] [ANN] SmalltalkCI now supports Pharo 8

> Am 23.01.2019 um 08:20 schrieb Sven Van Caekenberghe : > > > >> On 23 Jan 2019, at 01:13, Ben Coman wrote: >> >> Only in the past week I became aware of that SmalltalkCI was integrated with >> Travis... >> https://docs.travis-ci.com/user/languages/smalltalk >> > > Shame on you ;-) >

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

> Am 23.01.2019 um 04:13 schrieb Sean P. DeNigris : > > EstebanLM wrote >> https://news.ycombinator.com/item?id=18968116 > > Wow! 13 hours without any hardcore flame wars. We are improving ;-) > > > EstebanLM wrote >> https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

m Mackinnon, Max Leske, Andrew P. Black, > Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas > Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury > Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, > Alain Plan

Re: [Pharo-dev] Bad baseline practices

> Am 16.01.2019 um 09:42 schrieb Stephan Eggermont : > > Cyril Ferlicot > wrote: >> On Tue, Jan 15, 2019 at 6:03 PM Stephan Eggermont via Pharo-dev >> wrote: >>> >>> >>> >>> I’m not sure why, but I’ve noticed baselines being changed to refer to >>> patch versions for releases. Why are the

Re: [Pharo-dev] external#senders (was Re: DebugSession>>activePC:)

> Am 11.01.2019 um 11:33 schrieb Sven Van Caekenberghe : > > > >> On 11 Jan 2019, at 08:45, Esteban Lorenzano wrote: >> >> You know? since we are sharing frustrations, I have to say: we already had >> that process (which was the old pharo-vm project). In that project, for each >> version

Re: [Pharo-dev] [Pharo-users] [Ann] TaskIt v1.0

u have already something I wouldn't mind to integrate it) > I don’t have it now but I think when we change to TaskIt we will make them and we could provide it then. Norbert > > > Thanks. > Santiago > > > El jue., 29 de nov. de 2018 17:36, Norbert Hartl via P

Re: [Pharo-dev] [Ann] TaskIt v1.0

Great, thanks! Does TaskIt include implementations for combining futures such as the ALL and the ANY futures which resolve either when all or one future resolves? From the documentation it looks that rather not. Norbert > Am 29.11.2018 um 15:29 schrieb Santiago Bragagnolo > : > > Hi

Re: [Pharo-dev] Version control of Playground scripts

> Am 29.11.2018 um 11:15 schrieb Christopher Fuhrman > : > > > > On Wed, 28 Nov 2018 at 10:23, Norbert Hartl <mailto:norb...@hartl.name>> wrote: >> Am 28.11.2018 um 09:38 schrieb Christopher Fuhrman >> mailto:christopher.fuhr...@inria.fr>&g

Re: [Pharo-dev] Excel export with Tabular

Is there any progress on this? Can you tell the S3 url you are using? Do you need help to put it on github? Norbert > Am 12.11.2018 um 22:41 schrieb Hans-Martin Mosner : > > I put it on ss3 because I'm not yet familiar with the way Pharo uses github. > Will look into it later. > > I'm

Re: [Pharo-dev] Version control of Playground scripts

> Am 28.11.2018 um 09:38 schrieb Christopher Fuhrman > : > > Hello, > > In Pharo 6.1 I have got Iceberg working and love the interface to GitHub. > Thanks to the Rmod folks for all the patient answers to my newbie questions. > > However, most of my development remains in playground

Re: [Pharo-dev] Zinc HTTP Components version 3.0.1

Great That removes a decent disruption we had. Thank you very much! Norbert > Am 22.11.2018 um 21:55 schrieb Sven Van Caekenberghe : > > I finally merged and synced all Zinc HTTP Components repos and did a full > release on Pharo versions 3 to 7. > >

Re: [Pharo-dev] WELL512 PRNG

I was about to say let‘s add this to the Cryptography package  > Am 09.11.2018 um 15:34 schrieb Serge Stinckwich : > > Can you contribute your code to PolyMath: > https://github.com/PolyMathOrg/PolyMath > We have other RNGs available. > > Thank you. > >> On Fri, Nov 9, 2018 at 3:23 PM Sven

Re: [Pharo-dev] Cannot use Zinc in Pharo7 anymore

> Am 06.11.2018 um 19:54 schrieb Stephane Ducasse : > > Calypso is integral part of Pharo as Iceberg. > We started to discuss the problem in the team. Right now this project > spread kills us. > It is not an easy decision. Either you bind everything closely to you and ease your workflow but

Re: [Pharo-dev] Cannot use Zinc in Pharo7 anymore

> Am 02.11.2018 um 12:23 schrieb Sven Van Caekenberghe : > > > >> On 2 Nov 2018, at 12:01, Norbert Hartl wrote: >> >> Hi >> >>> Am 02.11.2018 um 11:15 schrieb Stephane Ducasse : >>> >>> Hi >>> &

Re: [Pharo-dev] Cannot use Zinc in Pharo7 anymore

(!!!). I have the same situation in my company. I’m the one that is reluctant to go to monorepo because I don’t like my code jailed in a project. But the effort we have to take in order to organize a stable and development version with a lot of external projects is killing us. So can we please

Re: [Pharo-dev] Cannot use Zinc in Pharo7 anymore

> Am 02.11.2018 um 00:13 schrieb Sven Van Caekenberghe : > > > >> On 1 Nov 2018, at 19:50, Sven Van Caekenberghe wrote: >> >> Norbert, >> >>> On 1 Nov 2018, at 18:12, Sven Van Caekenberghe wrote: >>> >>> I was planning on getting all changes to Zn/Zdc from pharo 7 back upstream >>>

Re: [Pharo-dev] Cannot use Zinc in Pharo7 anymore

Hi, > Am 02.11.2018 um 00:13 schrieb Sven Van Caekenberghe : > > > >> On 1 Nov 2018, at 19:50, Sven Van Caekenberghe wrote: >> >> Norbert, >> >>> On 1 Nov 2018, at 18:12, Sven Van Caekenberghe wrote: >>> >>> I was planning on getting all changes to Zn/Zdc from pharo 7 back upstream >>>

[Pharo-dev] Cannot use Zinc in Pharo7 anymore

I asked this before because I don’t get it. External packages like Zinc seem to be modified when integrated into pharo. Looking at the changes between to newest Zinc from Sven’s repository and the one in pharo there are a few differences. As an example there is ZnCharacterReadWriteStream>>#tab

Re: [Pharo-dev] GitHub Topics

> Am 13.10.2018 um 11:09 schrieb Cyril Ferlicot : > > > >> On sam. 13 oct. 2018 at 10:42, Norbert Hartl wrote: >> I don‘t want to kick off another war but shouldn‘t we add pharo as a >> language to github. Now it is a topic but the configurations fo

Re: [Pharo-dev] GitHub Topics

I don‘t want to kick off another war but shouldn‘t we add pharo as a language to github. Now it is a topic but the configurations for linguist are still tying it to smalltalk. Norbert > Am 11.10.2018 um 16:28 schrieb Sean P. DeNigris : > > Stephane Ducasse-3 wrote >> super c00l > > +1.

Re: [Pharo-dev] GitHub Topics

Mine are tagged, too. And most of them have the gitattributed so is surely discovered as smalltalk > Am 11.10.2018 um 03:48 schrieb Pierce Ng : > >> On Wed, Oct 10, 2018 at 08:42:13AM -0300, Esteban Maringolo wrote: >> PR approved! We're listed at https://github.com/topics/pharo > > Great!

Re: [Pharo-dev] Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

> Am 10.10.2018 um 15:58 schrieb Sven Van Caekenberghe : > > > >> On 10 Oct 2018, at 11:15, Norbert Hartl wrote: >> >> Very cool. Thank you very much, >> >> Can you make releases for your repos? In my repos I did a release of a >> version s

Re: [Pharo-dev] Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

Very cool. Thank you very much, Can you make releases for your repos? In my repos I did a release of a version saying it is the same as the last on smalltalkhub. So people can pinpoint to a specific release. I think this is a good way of doing it. Norbert > Am 05.10.2018 um 14:05 schrieb

Re: [Pharo-dev] Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

Great! And yet another reminder that all projects should consider moving to git. Norbert > Am 05.10.2018 um 14:05 schrieb Sven Van Caekenberghe : > > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > >

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

> Am 03.10.2018 um 14:02 schrieb Sven Van Caekenberghe : > > So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. > > I got a fresh 6.0 and I installed Tonel into it using > > Metacello new > repository: 'github://pharo-vcs/tonel'; > baseline: 'Tonel'; > load. > > Which

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

> Am 30.09.2018 um 13:01 schrieb Pierce Ng : > > On Wed, Sep 26, 2018 at 07:49:10PM +0200, Norbert Hartl wrote: >>>> And a lot more. This is a coarse grained overview over the >>>> architecture. I’m happy to answer further questions about this. >>

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

cceed but a requirement Hope this is the information you were asking for. Norbert > > Le mar. 25 sept. 2018 à 17:45, Sven Van Caekenberghe <mailto:s...@stfx.eu>> a écrit : > > > > On 25 Sep 2018, at 14:39, Norbert Hartl > <mailto:norb...@hartl.name>> wro

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

Super! Thanks Norbert > Am 27.09.2018 um 11:26 schrieb Guillermo Polito : > > Hi all, > > I've moved the Artefact library to GitHub > (https://github.com/pharo-contributions/Artefact). > > I've also made some changes to it in the way and made a 1.7.0 version with: > - support for Pharo7

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

> Am 25.09.2018 um 17:44 schrieb Sven Van Caekenberghe : > > > >> 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.

[Pharo-dev] IoT hackathon @zweidenker

Hi, we (ZWEIDENKER) and RModD organized an IoT Hackathon in cologne at 19th of october 2018. The plan will be: - Allex Oliviera will present the tutorial he made on PharoThings [1]. The audience will try it in a hands-on-session and give feedback to improve it. Zweidenker is sponsoring the

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

er the architecture. I’m happy to answer further questions about this. Norbert >> On 25 Sep 2018, at 12:20, Norbert Hartl wrote: >> >> As presented on ESUG here is the brief description of one of our current >> projects. >> >> Mobility Map >> —

Re: [Pharo-dev] Extension methods in p7

> > In Calypso there are no protocols for extensions. You should simply call > command Move methods to package either from menu or drag and drop to package > (where you see it). > > I don't know what the reason for commit and removal. I will check. > > вт, 21 авг. 20

[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

  1   2   3   4   5   6   7   8   >