When creating Spec2 presenters, I noticed the automated refactorings
(create accessors) don't all work.
Do we need changes to the slots, or to the rewrite rules there?
Stephan
https://vimeo.com/329368348
Stephan
Verstuurd vanaf mijn iPhone
> Op 14 apr. 2020 om 14:36 heeft Stéphane Ducasse
> het volgende geschreven:
>
> Hello
>
> I would like to build a lecture around TDD and XtremeTDD (coding in the
> debugger).
> I’m looking around t
turned back on as needed in the future.
I use them once in a while. Useful when triangulating issues
Stephan
on" could be added but again I think this is a bit odd
> feature.
If you support select all you need at least one of invert selection and
select none. All actions are supposed to be reversible as far as possible.
Stephan
the answer was: Not so easy.
> But then again, Fortran predates the theory of languages and it was not
> defined to be easily parseable with a formal grammar.
On the other hand, you know that you can parse these kinds of languages
with 16K of ram, one 80 character line at a time.
Stephan
https://github.com/jecisc/GitBridge might be of help here
Stephan
wrote:
> Since my last post, Pharo is still crashing during installation of
> Seaside 3 in Windows 10 platforms. It happens because git uses SSL and
> there’s some bug that causes libssl to crash, killing VM.
With the latest vm?
Stephan
, so that makes the handling of projects with lots of packages easier by
eliminating the simple problem of having to write down the exact version
number of these packages. That helps
Stephan
Sven Van Caekenberghe wrote:
>
>
>> On 1 Jun 2019, at 10:41, Stephan Eggermont wrote:
>
>> Could you explain how configurations are simpler?
>>
>> Stephan
>
> Because BaselineOfs are simpler than ConfigurationOfs.
>
> Of course, they don't
ducasse wrote:
> Now migrating to iceberg is super easy and configurations are a lot
> simpler than with monticello.
Could you explain how configurations are simpler?
Stephan
amHolder can be
non-trivial.
The fallback behavior of a readWriteStream opened on a read-only file is
also not easy to get right.
Stephan
teso...@gmail.com
wrote:
> If somebody is willing to use it in Pharo 7, I can create a PR against
> Pharo7 to generate patched P7 images.
Yes, I want to
Stephan
ducasse wrote:
> Hi stephan
>
>> Unless someone is working on fixing it today, I want this PR reverted.
>> Issues 2865, 2963, 2964, 2980, 3013
>>
>> Stephan
>
> Nobody is working on Pharo this is well known.
I am feeling angry and ignored. I am trying to c
Unless someone is working on fixing it today, I want this PR reverted.
Issues 2865, 2963, 2964, 2980, 3013
Stephan
Guillermo Polito
wrote:
>>
>> BOOL GetExitCodeProcess(
>> HANDLE hProcess,
>> LPDWORD lpExitCode
>> );
>>
>
> what are your mappings for BOOL, HANDLE and LPDWORD? Those are user defined
> types :)
>
I downloaded the stable version of OSWindows from the catalog
Stephan
green in 32
bit) triggered the idea. We did a quick and dirty change to verify, and
then found out that the Squeak code had cleaner fixes.
Stephan
were unaware of.
Stephan
, with blocking, returning nil, returning null objects, or
returning errors as possible expected behaviors?
Stephan
ferent encodings, or a dropped leading
character, and code where the method contents are changed but the timestamp
didn’t and the other way around
Stephan
response. A few years ago I did some
prototypes with DeprecationFinder and MonticelloProjects, applying it to a
subsection of smalltalkhub.
This is essential infrastructure. Both for deprecations and to recover
dependencies. Should be easy to get a paper out of it.
Stephan
Sven Van Caekenberghe wrote:
.
>
> So I propose to remove [Stream|Collection]>>#write:
>
> What say thou ?
Check the selectors used in the latest packages on squeaksource, ss3,
smalltalkhub and decide.
Stephan
rofile
(221 s vs 93)
Do I need all those calls to #basicOpenForWrite?
Stephan
Guillermo Polito
wrote:
> Hi Stephan,
>
> I'm sorry for the noise.
No problem, just trying to understand where we want to go.
Stephan
encoding or can I ask the OSEnvironment
for the one I need?
Before the Pharo 7 release we need at least a #getEnv: back and a class
comment corresponding to what is expected. If we want to change to the new
API it needs to be deprecated.
Stephan
ires calling the right *Wide version of the functions from
>C, plus the correct encoding routine. This could be implemented as an FFI
>call or by modifying the VM to do it properly instead of calling the Ascii
>version
>
>
What is the conclusion from this and issue 22658? See PR 2238. #getEnv: is
public API
Stephan
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 old configuration problems
>
--- Begin Message ---
I’m not sure why, but I’ve noticed baselines being changed to refer to
patch versions for releases. Why are the old configuration problems
repeated?
Stephan
--- End Message ---
Christophe Demarey wrote:
> Why not following git flow?
Because git flow has branches that don’t add value?
Stephan
> And latestVM, still works for me on windows.
>
PharoLauncher Pharo 7 (development version) list isn’t updated anymore,
stuck at 1384. 1411 works for me too.
Thanks,
Stephan
--- End Message ---
Esteban Lorenzano
wrote:
> They work for me.
> Same combination as always (alt+shift+click)
Not on 1384-64 in Windows with the latest vm
Stephan
What happened with halos in Pharo 7? They don’t show up anymore
Stephan
Pharo. There’s a chicken and egg
problem there
Stephan
Ben Coman wrote:
> On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users <
> pharo-us...@lists.pharo.org> wrote:
>
What is the current status of this? DelaySpinScheduler is default in my
recent Pharo 7 images and makes my images unusable on Ubuntu 18.04LTS.
Stephan
versions, it sounds to me like it
might be better of in the Pharo project. Tonel is supposed to be
cross-platform so should be separate.
Is this helpful?
Stephan
ening a morphic menu on a bloc
mouseclick. Here I open a ColorChooser
https://vimeo.com/236419682
Stephan
ongly prefer ML-etiquette.
> Sent from my iPhone
That supports NewsTap, which makes it easy to not top-post. I’m not sure
why lines are not broken though.
Stephan
Norbert Hartl <norb...@hartl.name> wrote:
> How can pillar kill pier?
They can not both be loaded. Pillar should have just forked: copy and
rename the parts needed.
Stephan
high priority.
If you take up responsibility for changing core, you make sure the higher
level still works. If you don’t want that, fork
Stephan
Denis Kudriashov <dionisi...@gmail.com>
wrote:
> If two entities needs separate versioning they should be in
separate
> repositories. Do you agree with this?
They don’t, and shouldn’t.
That is the way Pillar killed Pier. No separate maintaining of core
constantly breaking users.
Stephan
d in a way that gives us more work
now makes it take longer to get those tools.
Groups are at the moment essential to minimize manual work.
Stephan
Denis Kudriashov <dionisi...@gmail.com>
wrote:
> 2018-05-25 20:03 GMT+03:00 Stephan Eggermont
<step...@stack.nl>:
>
>> Denis Kudriashov <dionisi...@gmail.com>
>> wrote:
>>>
>>> Because when you will fix or improve Beacon-SysLog you will pro
Esteban Lorenzano <esteba...@gmail.com>
wrote:
>
>
>> On 25 May 2018, at 23:48, Stephan Eggermont <step...@stack.nl> wrote:
>>
>> Esteban Lorenzano <esteba...@gmail.com>
>> wrote:
>>> that’s because 6.1 images still comes with an old
Esteban Lorenzano <esteba...@gmail.com>
wrote:
> that’s because 6.1 images still comes with an old VM.
> I think I will backport the newer, but next week (testing time has passed, I
> think).
You probably want to include the TLS fix from this week for Win7 so github
repos eork
Stephan
cy issues the duplication of volatile information
creates a lot of commit ripple
I’d would like to see a description of how that is supposed to work with
all the duplicated baselines and repos.
Stephan
y would you update the baseline for
that?
Stephan
to integrate only core part of Beacon
> which requires MemoryLogger and TranscriptLogger. And we wanted to manage
> logger backends using separate baselines. So we need separate repos to have
> separate versioning.
Why would you want separate baselines for that? And on top of that separate
repos?
Stephan
tive VM.
>
> https://pavel-krivanek.github.io/pharo/pharo.html
>
> Cheers,
> -- Pavel
>
>
Cool. It works on my phone.
Stephan
o breaks when you need to work on different branches, so a
shared repository location is at the moment not a recommended setting?
Stephan
more).
That is great! Thanks!
Stephan
rong (in most cases), especially in an international context.
How do we capture these kinds of decisions? This is crucial information for
people trying to migrate to Pharo.
Stephan
rsions, from say 1.3 to now.
>
> But, in a way, please do the way you like, and, well, a few years down
> the line, we're back at the same situation as now.
>
> Not that I wish it, but I can see when someone is solving a problem with
> yet another way of having the problem.
Indeed.
Stephan
Gabriel Cotelli <g.cote...@gmail.com> wrote:
> And please support the use of baselines. Nobody wants to also mantain a
> ConfigurationOf just for the catalog when using baselines.
That sounds like a non-problem. One file that never needs to change. Let’s
solve the problems first
Stephan
On 20-03-18 08:55, Stephan Eggermont wrote:
Cyril Ferlicot D. <cyril.ferli...@gmail.com>
wrote:
Le 19/03/2018 à 18:49, Stephan Eggermont a écrit :
Then why bother releasing?
Hi,
For people using Pharo 7 to not get the same bugs for more than 1 year,
to get the new functiona
Stephane Ducasse <stepharo.s...@gmail.com>
wrote:
> Hi All
>
> We would like to organise PharoDays the 14 and 15 June. Could you tell us
> if you see big problems from your side before we announce it.
Works better than 7/8, which I cannot make
Stephan Eggermont
Cyril Ferlicot D. <cyril.ferli...@gmail.com>
wrote:
> Le 19/03/2018 à 18:49, Stephan Eggermont a écrit :
>> Then why bother releasing?
>>
>
> Hi,
>
> For people using Pharo 7 to not get the same bugs for more than 1 year,
> to get the new functionaliti
Denis Kudriashov <dionisi...@gmail.com>
wrote:
> 2018-03-19 9:16 GMT+01:00 Stephan Eggermont
<step...@stack.nl>:
>
>> Denis Kudriashov <dionisi...@gmail.com>
>> wrote:
>>> 2018-03-17 17:01 GMT+01:00 Stephan Eggermont
>> <step...@stack
Denis Kudriashov <dionisi...@gmail.com>
wrote:
> 2018-03-17 17:01 GMT+01:00 Stephan Eggermont
<step...@stack.nl>:
>
>> Denis Kudriashov <dionisi...@gmail.com>
>> wrote:
>>>
>>> No. Each build just loads specified version. I do not need to c
aking it necessary for your dependencies to change. Will you make
a new release each time one of your dependencies needs to change?
Stephan
Denis Kudriashov <dionisi...@gmail.com>
wrote:
> 2018-03-17 13:15 GMT+01:00 Stephan Eggermont
<step...@stack.nl>:
>
>> Denis Kudriashov <dionisi...@gmail.com>
>> wrote:
>>
>>> So to get all minor fixes from all dependencies the code sh
ersions (0.5.3 tag) will be completely reproducible.
>
So your goal for released versions is to be only loadable on a specific
pharo build?
Stephan
re a deeper reason for this? If I look at “other systems”, they
> manage to have *one* download, *one* way of installing.
> For me, offering *a lot* of possible different ways means that the user
> has to choose without knowing why there is even the option to choose…
Yes. I want the live usb stick experience
Stephan
).
Easy for now, yes. And also a bad example for others to follow. And
something that doesn't scale. Where is the increased modularity going to
come from if we still manage everything as a monorepo?
Stephan
ich versions were loaded in which order, so that information
should be recorded for reproducibility.
Stephan
d-coded versions
of anything you don't control yourself. See the 5D paper
Stephan Eggermont
ersion of Pharo is
increasingly unattractive. It also requires indefinite support of all the
old pharo versions. A collection of separate rewrite rules looks to me like
the right thing to both explain changes and speed up migrations.
Stephan
ups at this low level need to be done with rewrite rules (and tests)
Stephan
eful
2 Yes, having much more control over the package cache makes sense,
especially with TelePharo. Different scenario's need different strategies.
Mixing new, own code with loaded frameworks is not very practical
Stephan
le than network, and it depends on simpler
and working infrastructure. The package cache is deliberately not cleaned,
and not shared by default.
Stephan
e,
but with a high innovation rate comes a higher risk. Denial helps noone,
keep up the good work!
Stephan
lo+iceberg+fogbugz+jenkins feels like a series of
> obstacles between me and maintaining my application.
Isn't nix supported by travis? I suppose that means that you should be able
to automatically build a variant of opensmalltalk
I have absolutely no idea how much work that would be though.
Stephan
? If we only limit ourselves to open source, just look
at Glorp and PDFTalk.
Stephan
Eliot Miranda <eliot.mira...@gmail.com>
wrote:
> Hi Stephan,
> Then why on /earth/ would one stop using Smalltalk in /the most central
> part/ of the collaborative programming process, version control?
Because of the underestimation of the work needed, vs. the advantage of
pport turns out to be much more work than we hoped and expected. Too
many library updates needed, support for different workflows and platforms,
switch to file per class. The Iceberg channel on Discord is one of the
busiest channels.
Stephan
Esteban Lorenzano <esteba...@gmail.com>
wrote:
> Hi everybody,
>
> This looks like a good moment of the year to ask all of you what would
> you want to see in Pharo next year.
I wish you all the time and good health to realize some of your Pharo
dreams
Stephan
Denis Kudriashov <dionisi...@gmail.com>
wrote:
> Hi Bernhard.
>
> The deprecation is still in progress.
Considering the amount of non-image code using this, I would be interested
to hear how this is going to be supported and documented.
Stephan
On 13-12-17 16:32, Sean P. DeNigris wrote:
Marcus Denker-4 wrote
I have updated the download instruction…
Thanks!! This seems to have been a common pain point, for new users
especially.
And then a newer 32 bit Linux VM needs to be build and promoted to
stable as next point?
Stephan
s done with WideString. That probably needs a look in
the squeak mailing list archives.
Stephan
own of a factor 20. 1 (primary) file per
class and sorting the methods helps a lot. Doing that in a
cross-platform compatible way so we can easier share source code needs
some further refinement
Stephan
On 02-12-17 11:18, Thierry Goubier wrote:
Le 02/12/2017 à 11:00, stephan a écrit :
On 01-12-17 21:21, Thierry Goubier wrote:
To avoid segfaults, I'm using one from November.
Where does that come from? Or do you compile it yourself?
It comes from the bintray opensmalltalk folder
On 01-12-17 21:21, Thierry Goubier wrote:
To avoid segfaults, I'm using one from November.
Where does that come from? Or do you compile it yourself?
Stephan
On 01-12-17 18:56, Alistair Grant wrote:
On 01-12-17 11:16, stephan wrote:
Is the latest really from august?
I have: Date: Sun Aug 27 21:55:26 2017 +0200
So what happened in the past two months?
Stephan
On 01-12-17 11:16, stephan wrote:
Is the latest really from august?
Ping
Is the latest really from august?
Stephan
like the booklets very much too.
Stephan
On 28-11-17 19:40, Torsten Bergmann wrote:
2c) Code subdirectory: enter "src" here !!!
Do we really need that? Why would I care about that?
Stephan
On 27-11-17 12:08, Tudor Girba wrote:
How do they crash? When you run something specific?
Different things. The script crashed reliably on all my machines the
last time I checked.
Stephan
tion/main'.
project read.
project saveToFile.
Stephan
)
will be needed too. I would like to avoid the problems we earlier had
with Komitter. Can we discuss the scenario's (through personas) here first?
Cheers,
Stephan
applications. The project goals are:
Interesting approach. Might be useful to use as a target for
(QC)Magritte. So much things to try out, and not enough time!
Stephan
Is all this summarized on Guille's (and Thorstens) pages?
Stephan
of an
object outside the space, I assume. Also, the creation of temporary
instances of itself raises the question of exactly what to copy. Please
elaborate a bit on the consequences of this for application and test design.
Cheers,
Stephan
it in users
Stephan
result in silent failure.
That actually needs a quality rule (or rewrite to also flatten)
Stephan
ritten for
pharo 3 or 4 and add it there. Just unplanned work to keep up with Pharo
changes. And would have been better handled as a rewrite rule, I think.
Stephan
On 07-11-17 21:11, Sven Van Caekenberghe wrote:
Nobody (trying to use|using) Seaside on Pharo 7 ??
I already did one pull request. That is not enough because of the
flattening of traits
Stephan
form exactly because different
smalltalks have different ideas of what a valid symbol is.
Stephan
there is a broken one.
Stephan
I've noticed a few VM updates I want to use with PharoLauncher.
What is the currently recommended way to update my PharoLauncher to use
a non-stable version?
Stephan
On 28-10-17 16:26, Stephane Ducasse wrote:
I was reading ...
I will see if I can load cassowary in Pharo.
I could get the squeaksource cassowary for morphic working without a
problem, just needed some extensions and fixes for changes we made in Pharo.
Stephan
/Bloc/issues/25
Just applying and adapting Thierry's code should provide us what we need
Stephan
1 - 100 of 808 matches
Mail list logo
