Tx Uko.
We should improve.
On Tue, Jul 11, 2017 at 7:07 PM, Yuriy Tymchuk wrote:
> This is actually fun. For pharo contributions I just used Iceberg ui without
> scripting anything and it works absolutely fine. Iceberg has a default
> location for cloned repositories, and it puts pharo there too
Hi nicolai
we should really fix that. I know that it is painful because we got
out our confort zone.
I really hope that we will be able to do something better. Now what we
should do is incrementally
rebuild a better system.
About the git support on windows. I thought it was working what is the
pro
lovely :)
On Mon, Jul 10, 2017 at 8:34 PM, Pavel Krivanek
wrote:
> Can you try to prepare a pull requeast that will integrate it? The PR will
> need to:
> - add the packages into the repository
> - add them into the baseline (BaselineOfUI)
> - remove old FileDialogWindow (becuase when we add som
Hi mariano
what kind of help do you want?
Stef
On Wed, Jul 12, 2017 at 9:53 PM, Mariano Martinez Peck
wrote:
> Hi all,
>
> A while back our team presented Quuve [1], a customizable investment
> management ecosystem for professional investors. We also discussed the
> technologies employed to bu
Hi andrei
this is strange because I recovered multiple time recently due to some
hidden bugs and I did not face the one you report.
Stef
On Tue, Jul 18, 2017 at 10:48 AM, Andrei Chis
wrote:
> Hi,
>
> Is there some known bug in Epicea when applying multiple changes at once in
> Pharo 6?
>
> I ha
Lionel
when the system does find a source, it decompiles the method and this
is why you get the code changed.
Stef
On Tue, Jul 18, 2017 at 7:22 AM, Max Leske wrote:
> As Gabriel notes, it looks like your missing the .sources file. I don't know
> what pharocloud supports, but you could try packa
Thanks Norbert. The consortium paid nicolas to deliver iceberg and
esteban to push further for git because
the world is moving and git and github support will give us a lot of
exposure and a really powerful distributing versionning source control
system (even if I really enjoyed MC - it is showing
+ 1
I'm curious to know the libraries that are making more trouble. (I'm
thinking about FreeType)
because we should throw away.
Stef
On Fri, Mar 17, 2017 at 12:54 AM, Ben Coman wrote:
> Great to hear this news.
> Thanks for your efforts Nicolas.
> cheers -ben
>
> On Fri, Mar 17, 2017 at 4:51 AM,
tx christophe.
Launcher is cool and this is nice to see some effort on that front.
Stef
On Mon, Jul 24, 2017 at 10:41 AM, Christophe Demarey
wrote:
> Hi Jan,
>
> I’m currently updating the Pharo Launcher so that it can determine the right
> VM to use to launch an image and download it if not av
HI alistair
this is supercool that you push this!
I mean it for real. Because this simplnk stuff was always getting on
our way for scripts.
This is really great to see this happening.
Stef
On Mon, Jul 24, 2017 at 10:43 AM, Max Leske wrote:
> Nice work Alistair!
>
>
>
> On 24 July 2017 at 10:10:0
Hi Alistair
Yes it should become part of the core of Pharo :).
Stef
On Tue, Jul 25, 2017 at 5:21 PM, Alistair Grant wrote:
> Hi David,
>
> Thanks very much for your follow-up.
>
> On Mon, Jul 24, 2017 at 07:28:07PM -0400, David T. Lewis wrote:
>>
>> Hi Alistair,
>>
>> I am copying this to vm-de
I imagine that hot-fixes means when we found a serious bug in the
alpha version and see that it is also in the previous version.
Now Hilaire if you want a change to be integrated in Pharo and Pharo
60 for example.
- we should have a bug entry on fogbugz (you see when I read the
emails I do not se
Athens is what is in Pharo. I have no idea of the rest.
Stef
On Wed, Jul 26, 2017 at 4:42 PM, Nicolai Hess wrote:
>
>
> 2017-07-26 16:25 GMT+02:00 Stephane Ducasse :
>>
>> I imagine that hot-fixes means when we found a serious bug in the
>> alpha version and see that
This is really interesting.
I would be interested to see why ClassSessionHandler(FreeTypeSettings)
takes 2/3 of the computation.
Without it we would be 100 ms.
Stef
On Thu, Jul 27, 2017 at 2:49 PM, Sven Van Caekenberghe wrote:
> Hi,
>
> I instrumented WorkingSession with a log collection that ho
> Hi Denis,
> you're right, for literal numbers it's been solved in Pharo at least since
> 3.0, or maybe even 2.0 (by usage of RB AST I guess).
> That's a major improvment over Squeak which is is certainly where I last
> encountered the problem.
>
> Still, formatting does mess line breaking/indenti
o that, and eliminate the FreeType
> stuff for server-side deployment.
>
> cheers -ben
>
> On Fri, Jul 28, 2017 at 3:14 AM, Stephane Ducasse
> wrote:
>>
>> This is really interesting.
>> I would be interested to see why ClassSessionHandler(FreeTypeSettings)
>
I did not try behind a proxy.
On Thu, Jul 27, 2017 at 10:28 PM, Nicolai Hess wrote:
> Anyone got it working to use iceberg /libgit behind a proxy?
>
> I can access monticello repositories with the right proxy settings.
> But using iceberg shows an error about
> can not access github.org
>
>
Nicolai
here are my setup (done with pavel) for pharo 70 active dev.
There are two phases:
- once done for all (cloning the repo)
- once for each image I download
I hope it helps (bt not for the proxy)
Stef
On Fri, Jul 28, 2017 at 8:02 AM, Stephane Ducasse
wrote:
> I did not try behin
Hi norbert
did you update the catalog entry?
Stef
On Fri, Jul 28, 2017 at 12:40 PM, Norbert Hartl wrote:
> In the spirit of git notification…I moved mustache to github.
>
> https://github.com/noha/mustache
>
> Enjoy!
>
> Norbert
>
>
Tx denis.
I like the scoped refactoring :).
Do you have settings for all the automatic protocols?
BTW do you kept the inplace edit of protocol? Because it was cool to
double click on it to rename it.
Stef
On Fri, Jul 28, 2017 at 10:58 AM, Denis Kudriashov wrote:
> Hi.
>
> I moved Calypso to gi
Hi Pavel
This is super excellent! IMPRESSIVE. An image without the compiler and
a reloadable compiler.
Super cool.
Stef
On Tue, Aug 1, 2017 at 11:57 AM, Pavel Krivanek
wrote:
> Hello,
>
> we are checking a huge pull request #177
> (https://github.com/pharo-project/pharo/pull/177) that will cha
Tx christophe.
On Tue, Aug 1, 2017 at 11:23 AM, Torsten Bergmann wrote:
>
> Thanks!
>
>
> Gesendet: Dienstag, 01. August 2017 um 10:48 Uhr
> Von: "Christophe Demarey"
> An: "Pharo Development List"
> Betreff: Re: [Pharo-dev] Catalog down
>
> It is nows back on line!
>
> Christophe
>
>
> Le 1 a
ystem based on the current
> code-base that is able to be bootstrapped has about 260kB.
>
> -- Pavel
>
>
>>
>> Is Hermes going to be a generic binary content loader?
>>
>> Phil
>>
>> On Aug 1, 2017 12:36, "Stephane Ducasse" wrote:
>
all image?
> Is Hermes going to be a generic binary content loader?
>
> Phil
>
> On Aug 1, 2017 12:36, "Stephane Ducasse" wrote:
>>
>> Hi Pavel
>>
>> This is super excellent! IMPRESSIVE. An image without the compiler and
>> a reloadable compiler.
gt;>>> designed to only work as light way of loading code during the
>>>>>>> bootstrap. So
>>>>>>> that, it is heavily coupled with Pharo (it can be changed, for example
>>>>>>> implementing another loader / installer) and u
>> - Deprecated FileStream & childs (Moved to Deprecated70)
>
> *Counts direct references to FileStream & subclasses in a 6.1 Moose image*
> Brave souls!
It means that Moose will have to update. These classes are not gone
just deprecated.
> I hope the migration guide will be up to snuff, or I ima
Thanks because this is months that I said the same to denis.
And I will never never explain that to students and I will add a
setting to turn it the other way.
I hate this!
Stef
On Thu, Aug 3, 2017 at 2:02 PM, Mariano Martinez Peck
wrote:
> Hi Denis,
>
> I love the inherited methods feature. Rea
Mariano
how many year of pharo programming do you have? And you got confused :)
so imagine a newbie.
And imagine when you browse code that you do not know.
It violates all the inheritance mind sharing.
Stef
On Thu, Aug 3, 2017 at 4:29 PM, Mariano Martinez Peck
wrote:
>
>
> On Thu, Aug 3, 2017 a
Hi guys
While writing pillar code, I ended up using "stream cr" and it worries
me to still expand usage
of a pattern I would like to remove.
Let us imagine that we would like to prepare the migration from cr.
I was thinking that we could replace cr invocation by newLine so that
after newLine
coul
200, Stephane Ducasse wrote:
>> Hi guys
>>
>> While writing pillar code, I ended up using "stream cr" and it
>> worries
>> me to still expand usage
>> of a pattern I would like to remove.
>>
>> Let us imagine that we would like to prepare the
ot;Esteban Lorenzano" wrote:
>>
>>
>> > On 4 Aug 2017, at 14:06, Stephane Ducasse
>> > wrote:
>> >
>> > Well. This is not implemented like that in Pharo.
>> >
>> > cr is bad because it does not mean that it is independent of
So one step at a time:
- #cr and #lf just put this character in the stream.
- #newLine put the underlying OS line ending. ( and sorry for the
nostalgic but nl sucks and to me this is netherlands and not newline
:).
Then we should revisit all the cr inside the system and use newline.
Then we shoul
Hi torsten
Yes it sounds good to have MAJOR.MINOR.PATCH/BUILDNUMBER scheme
On Fri, Aug 4, 2017 at 9:22 AM, Torsten Bergmann wrote:
> Hi Ben,
>
> reason is that for Pharo 7 currently an sha git hash is used in the file
> name
> instead of a (more clear) build number.
>
> See http://files.pharo.or
Hi guys
I would like to know if there is a pattern to build extensible menu in Spec.
For example, I extending Epicea to support pillar fileout so that I
can turn a coding section into a pillar steps of action.
I wanted to extend the epicea browser to get my menu in:
But the code is like that:
EP
:)
Me too.
Stef
On Sat, Aug 5, 2017 at 6:32 PM, Cyril Ferlicot wrote:
> On Sat, Aug 5, 2017 at 6:14 PM, Stephane Ducasse
> wrote:
>> So one step at a time:
>>
>> - #cr and #lf just put this character in the stream.
>> - #newLine put the underlying OS li
gt;>>>
>> > >>>>
>> > >>>>> On 4 Aug 2017, at 15:41, Damien Pollet
>> > >>>>> wrote:
>> > >>>>>
>> > >>>>> I agree with Pablo, #cr and #lf should not be clever and
Hi Guille
I agree with you :).
Stef
On Sun, Aug 6, 2017 at 11:05 AM, Guillermo Polito wrote:
>
>
> On Sun, Aug 6, 2017 at 10:54 AM, Stephane Ducasse > wrote:
>
>> Agreed :)
>>
>> But so far what do we do?
>>
>>
>> - #cr and #lf just put this
Yes this is great.
Now I will be rerunning the pending fix and integrate the green ones.
On Sun, Aug 6, 2017 at 11:00 AM, Guillermo Polito wrote:
> Hi all,
>
> As you all know, we are now building from github. Integrations are made
> through pull requests. And pull requests are validated using
Hi alistair
I will go over all the FS changes and push them in Pharo 70.
I'm learning the process to integrate fixes and I attract bugs :)
Stef
t-gt-and-path-canonicalisation-td4952575.html,
> so I might separate that out and make it a separate patch.
>
>
> Cheers,
> Alistair
>
> On 8 August 2017 at 10:27, Stephane Ducasse wrote:
>> Hi alistair
>>
>> I will go over all the FS changes and push them in Pharo 70.
>> I'm learning the process to integrate fixes and I attract bugs :)
>>
>> Stef
>>
>
ut do you suggest to drop it and close it?
TX
On Tue, Aug 8, 2017 at 6:44 PM, Stephane Ducasse
wrote:
> For the moment I'm trying to understand the process and this is not that
> simple
> because in flux.
>
> stef
>
> On Tue, Aug 8, 2017 at 3:24 PM, Alistair Grant wrote:
Hi
We do not have yet an automated mail after each integration. So I will
do it by hand.
I'm going over the green issues
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/view/change-requests/
And integrating the ones I understand. Then I will lo
Tx guille.
So I will update the bug entry.
On Tue, Aug 8, 2017 at 7:29 PM, Guillermo Polito
wrote:
> Hi Stef,
>
> On Tue, Aug 8, 2017 at 7:00 PM, Stephane Ducasse
> wrote:
>
>> Hi Alistair
>>
>> I'm going over the green build first.
>>
>> - Ca
Tx!
So that I do not make mistake:
The fix is the second solution. Now do we have somewhere the first one?
On Wed, Aug 9, 2017 at 10:08 AM, Denis Kudriashov wrote:
> Hi
>
> 2017-08-09 8:47 GMT+02:00 Alistair Grant :
>>
>> Hi Stef,
>>
>> On Tue, Aug 08, 2017 at 0
20063-isDeprecated-should-consider-protocol-names
Stef
https://pharo.fogbugz.com/f/cases/20238/Run-out-of-memory-the-image-hangs-without-out-of-memory-warning
https://github.com/pharo-project/pharo/pull/168
Now I get message that I do not understand test failure error from jenkins :(
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20
found out that PragmaMenuBuilder is
> compatible with Spec.
>
> Something like...
>
> builder := PragmaMenuBuilder pragmaKeyword: 'myPragma' model: self.
> menu := MenuModel new.
> menu fromSpec: builder menuSpec.
>
> Peter
>
>
> On Sat, Aug 05, 2017 at 06:26:
eFile
https://github.com/pharo-project/pharo/pull/133
-
https://pharo.fogbugz.com/f/cases/19609/FileReference-base-should-be-before-last-separator
https://github.com/pharo-project/pharo/pull/137
Did I miss some others?
Stef
On Tue, Aug 8, 2017 at 10:27 AM, Stephane Ducasse
in PR 21
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/21/
https://pharo.fogbugz.com/f/cases/20295/
Stef
Build 22
https://github.com/pharo-project/pharo/pull/169
https://pharo.fogbugz.com/f/cases/20249/Add-some-colors-to-the-themes
Le mer. 9 août 2017 à 21:47, Stephane Ducasse a
> écrit :
>
>> https://pharo.fogbugz.com/f/cases/20238/Run-out-of-memory-
>> the-image-hangs-without-out-of-memory-warning
>>
>> https://github.com/pharo-project/pharo/pull/168
>>
>> Now I get message th
> for each menu, or have the menu name as an argument. The same goes for
> differentiating pragmas between different tools.
>
> e.g.
>
> vs #OP context: #OPUmlClassEditorPlugin>
>
> the latter seems like it's adding more complexity.
>
> Peter
>
>
>
Tx
On Thu, Aug 10, 2017 at 7:21 AM, Alistair Grant wrote:
> Hi Stef,
>
> On Wed, Aug 09, 2017 at 08:23:50PM +0200, Stephane Ducasse wrote:
>> Tx!
>> So that I do not make mistake:
>> The fix is the second solution. Now do we have somewhere the first one?
>
> N
Hi
https://pharo.fogbugz.com/f/cases/17848/SequenciableCollection-first-raise-an-Error-if-the-collection-if-too-small
https://github.com/pharo-project/pharo/pull/132
Stef
vigate. But if we want to extend it we wan to be able to add groups to
> it. In VW we number the groups in the base menu in tens, so again/undo is
> 10.0, cut/copy/paste is 20.0, etc. Then anyone can define a new group
> relative to the base groups by providing a group number su
Tx this is really good and I will use it to produce new clean images to
work on Pharo 70
On Thu, Aug 10, 2017 at 5:17 PM, Guillermo Polito wrote:
> Hi,
>
> I've made some write up for the pharo part (not metacello or external
> projects)
>
> https://github.com/guillep/PharoIntegrationProcess/wik
PR 69
https://github.com/pharo-project/pharo/pull/69
https://pharo.fogbugz.com/f/cases/19802/Make-sure-Symbol-concatenation-results-in-a-Symbol-not-a-String/
Nicolai
I started super simple. I clone and point my fresh dled image to the use
the clone.
Then I can do simple PR and review the issues.
I will do the installation several times to learn (but not clone).
I'm not sure that it is needed but I have
cd /Users/ducasse/Library/Preferences/pharo/7.0
Hi
Noury is still developing PharoJS. If you want to be productive you
should report
- what you did.
- what went wrong.
I will forward to Noury such information because he is not reading
Pharo mailing-list.
Stef
On Sun, Aug 13, 2017 at 4:46 PM, Frank-B wrote:
> As recommended here:
> http://fo
Hi frank
You can contact noury at bouraq...@gmail.com
Serge does not work on PharoJS. Noury and Dave are.
Stef
On Sun, Aug 13, 2017 at 4:50 PM, Frank-B wrote:
> @Serge and @those who developed PharoJS
>
> My first attempt to play with PharoJS failed.
> See here: http://forum.world.st/PharoJS-cr
Hi frank
I think that you are slowly but steadily destroying your aura in this
mailing-list, so be careful. I say that to help
you. Filter are easy to set.
We are all concerned that some of the solutions are not at the level
where they should be.
I'm sure that Noury like us all would love to have
Hi henry
Here is the email of sven Van Caekenberghe
He is probably on vacation else he would have replied.
This is great if you can extend neoJSON it is a nice and important
piece of software.
Stef
On Sat, Aug 12, 2017 at 10:04 PM, henry wrote:
> Is Sven still working on NeoJSON? I want to he
We have some instability with the VM. Now can you tell us more how it "blew up"?
I browsed the code and nothing special jump to my eyes.
Stef
On Sun, Aug 13, 2017 at 2:08 PM, henry wrote:
> Hi all. I was testing with this eventual_test package and it blows up the
> pharo 6.1 vm. I'd welcome poin
Tx eliot.
On Fri, Aug 11, 2017 at 12:55 AM, Eliot Miranda wrote:
> Hi Andrei,
>
> On Thu, Aug 10, 2017 at 3:02 AM, Andrei Chis
> wrote:
>>
>>
>> Hi,
>>
>> I was executing this code '(2009/2000) ** (3958333/10)' with the
>> Pharo6.1 distribution and the vm crashed with she stack attached be
Tx guille!
On Sun, Aug 13, 2017 at 3:05 PM, Guillermo Polito wrote:
> Hi all,
>
> we just configured fogbugz and github integration as follows:
>
> http://help.fogcreek.com/8048/integration-with-git
>
> Quoting the instructions:
>
>
>1. Now you can refer to your FogBugz cases in your GitHub
n my learning todo list was to try and replace that JS
> generator with something from Smalltalk - so I think we can possibly come up
> with something that ticks all the right boxes (I’d like to try anyway).
>
> I’ll keep working away on it and compare notes with you. I think with
> Pil
Hi guille
thanks for raising this point. I will wait a bit that other people comment
on it since it is a crucial point.
Stef
On Mon, Aug 14, 2017 at 4:47 PM, Tim Mackinnon wrote:
> I’m definitely in favour of doing something (as I found it confusing, and
> in a way also found it has the potent
Hi Henry
I do not think that Fuel is managed from SqueakSource.
Fuel is central to Pharo so it should be under Pharo..
Have a look at the repo associated with the fuel package in Pharo 60
for example.
Sent from a phone that is not trendy
On Mon, Aug 14, 2017 at 7:02 PM, henry wrote:
> I loaded
I checked and in Pharo 60
MCSmalltalkhubRepository
owner: 'Pharo'
project: 'Fuel'
user: ''
password: ''
Now Fuel is by default loaded into Pharo so may be you have another scenario.
Stef
On Mon, Aug 14, 2017 at 7:02 PM, henry wrote:
> I loaded the latest Fuel from squeak source and
>
> Oh, I'm plenty comfortable discussing it on the Pharo lists. :) I
> was referring to different context in which someone asked me a question
> here, and I got attacked for responding to it.
I surprised about it.
Because we are welcoming discussions. Now discussions around Pharo are better
Thanks guille
This is great to have all these ressources on git integration.
Once you are done :) we can really easily create a booklet around git and
pharo.
Stef
On Mon, Aug 14, 2017 at 7:40 PM, Guillermo Polito wrote:
> This little article explains how you should keep your branches in sync
>
On Sun, Aug 13, 2017 at 9:19 PM, Frank-B wrote:
> Stephane,
>
> thank you for your open words.
>
> 1) No I am NOT Frank Lesser and I will communicate this even clearer in a
> personal email to you.
Ok ;)
>
> 2) I had tried to make very clear that I see the Pharo project very positive
> and my cr
impression that this is going to be a slightly rockier year as there
>> have been some pretty revolutionary changes made to get us here.
>>
>> As its a vm change does this mean we get 6.2 queued up somehow?
>>
>> Tim
>>
>> > On 13 Aug 2017, at 20:12, Stephane D
[Pharo 70 ] build 35 - PR 172 Implement-WeakIdentityValueDictionary
https://github.com/pharo-project/pharo/pull/
https://pharo.fogbugz.com/f/cases/20105/Implement-WeakIdentityValueDictionary
Thanks for this discussion!
It will improve Guille proposal and Pharo :)
I'm happy!
And learning things. (ok I should prepare my lectures instead of reading.
I guess that I will have to use pomodoro techniques to force me to work :)
Stef
On Mon, Aug 14, 2017 at 9:48 PM, Eliot Miranda wrote:
>
>
.com/pharo-project/pharo/pull/75
>
>
> Thanks!
> Alistair
>
>
>
> On Thu, Aug 10, 2017 at 08:23:49PM +, Alistair Grant wrote:
>> Hi Stef,
>>
>> On Wed, Aug 09, 2017 at 10:12:17PM +0200, Stephane Ducasse wrote:
>> > Hi alistair
>> >
>>
Tx for the information. I will focus on 20307 then
On Tue, Aug 15, 2017 at 11:07 AM, Alistair Grant wrote:
> Hi Stef,
>
> On Tue, Aug 15, 2017 at 10:04:31AM +0200, Stephane Ducasse wrote:
>> tx a lot for the summary, this is super useful :)
>> I will over them later (beca
Thanks I will try it on my mac Sierra and report.
Stef
On Tue, Aug 15, 2017 at 2:59 AM, henry wrote:
> Yes, here it is, in Pharo6.1, as mentioned previously. Just run the
> eventual_test tests and it will exit on Ubuntu 32-bit.
>
> https://ufile.io/pa9ym
>
> Thank you,
> - HH
>
>
> Orig
https://pharo.fogbugz.com/f/cases/20091/Improve-comment-of-SmallDictionary
https://github.com/pharo-project/pharo/pull/204
I'm integrating 20307 and I would like to really thank you for
- the bug entry description
- all the comments
- and tests in the PR.
Tx!!!
On Tue, Aug 15, 2017 at 5:11 PM, Stephane Ducasse
wrote:
> Tx for the information. I will focus on 20307 then
>
>
> On Tue, Aug 15,
https://pharo.fogbugz.com/f/cases/20307/File-names-should-not-be-canonicalised-by-default
https://github.com/pharo-project/pharo/pull/206
https://pharo.fogbugz.com/f/cases/20269/FileReference-size-needs-a-comment
https://github.com/pharo-project/pharo/pull/199
I often use long selectors for tests :)
On Wed, Aug 16, 2017 at 9:49 AM, Guillermo Polito wrote:
> (ByteSymbol allInstances select: [ :e | e size > 50 ]) size
> "638"
> (ByteSymbol allInstances select: [ :e | e size > 50 and: [ e beginsWith:
> 'test' ] ]) size
> "200"
>
> Still 438 non test sel
https://pharo.fogbugz.com/f/cases/20165/Support-segment-path-printing
https://github.com/pharo-project/pharo/pull/210
one more :)
2PM +0200, Stephane Ducasse wrote:
>> I'm integrating 20307 and I would like to really thank you for
>> - the bug entry description
>> - all the comments
>> - and tests in the PR.
>>
>> Tx!!!
>
> Thanks for your kind words.
>
> And for integrating
Hi martin
https://pharo.fogbugz.com/f/cases/18084/FileReference-EnsureCreateFile
https://github.com/pharo-project/pharo/pull/133
rs are internal to the library. In my latest image
> there are no Epicea users of it.
>
> On Wed, Aug 16, 2017 at 8:59 PM, Stephane Ducasse > wrote:
>
>> Hi martin
>>
>>
>> https://pharo.fogbugz.com/f/cases/18084/FileReference-EnsureCreateFi
I do not know but I imagine that I added basenameWithoutExtension because
I found the name much much clearer. I would have never guessed that
base is the basename without the extension.
Stef
On Wed, Aug 16, 2017 at 9:46 PM, Alistair Grant wrote:
> Hi All,
>
> I've just taken a look at issue 1960
Hi guys
my son coded in Pharo 60
testGuessUrlPart
|dg8|
dg8 := GameItem new;
name: 'Dragon Quest VIII : Journey Of The Cursed King';
console: 'PS2'.
self assert: dg8 guessUrlPart equals:
'dragonquestviiijourneyofthecursedking'
and guess wha
l share for 7.0?
>>
>> Sort out the expert tools (like git etc), but equally enable that
>> simplicity you expect for a child/newbie/expert...
>>
>> I'm in!
>>
>> Tim
>>
>> Sent from my iPhone
>>
>> > On 17 A
Hi denis
The extra protocols are super confusing for newbies.
Is there a setting to remove the critiques (because it flickers) from
the protocols.
Can we remove the overrides and inherited?
I do not care to know that I overrides initialize from Object for example.
When you learn a system you do n
Hi
I really like (when I save little data files) to have a simple versioning.
For example for my game collection I have
Games.1.ston
Games.2.ston
...
and I like that this is managed for me by the system.
I harvested this functionality from squeak long time ago.
I rewrote it fast and dirty in Phar
MethodGroup
>
>
> But according to your logic method icons (up/down arrows) should be disabled
> too. Right now they are still managed by Nautilus method actions. To disable
> them use:
>
>
> ClyNautilusBrowserPlugin disable
>
>
> 2017-08-18 21:07 GMT+02:00 Stephane Ducass
We should add this in a class comment and probably a menu somewhere.
On Fri, Aug 18, 2017 at 10:05 PM, Stephane Ducasse
wrote:
> Tx denis.
>
> Stef
>
> On Fri, Aug 18, 2017 at 9:40 PM, Denis Kudriashov
> wrote:
>> Hi Stef.
>>
>> Yes, you need disable plugin
case we cannot access the
old method definition).
Stef
On Fri, Aug 18, 2017 at 10:05 PM, Stephane Ducasse
wrote:
> We should add this in a class comment and probably a menu somewhere.
>
> On Fri, Aug 18, 2017 at 10:05 PM, Stephane Ducasse
> wrote:
>> Tx denis.
>>
>
https://pharo.fogbugz.com/f/cases/20062/Open-a-package-extending-a-class-via-the-extension-protocol
https://github.com/pharo-project/pharo/pull/208
Hi torsten
On Thu, Aug 17, 2017 at 10:44 AM, Torsten Bergmann wrote:
> Hi,
>
> even when contributing to Pharo 7.0 is still very very cumbersome I was able
> to sort out most of the problems and contribute already a few smaller things.
Excellent. Because with my first contribution I broke filet
Now this is not easy because the browser does not know what to display
because the edited method (with the new selector is still not
compiled) but we could automatically add an entry after the first
carriage return
because this is the moment where we know that there is potentially a
new selector.
https://pharo.fogbugz.com/f/cases/20321/Add-build-number-to-SystemVersion
https://github.com/pharo-project/pharo/pull/212
No I will have a look :)
But I also need latestVersion because you need the two: to always load
the latest and save latest + 1
Stef
On Fri, Aug 18, 2017 at 11:38 PM, Denis Kudriashov wrote:
> Do you know that there is #nextVersion method in FileReference?
>
> 2017-08-18 22:04 GMT+02:00
101 - 200 of 1357 matches
Mail list logo
