Nicolai Hess wrote
> Sean, can you look at my latest submission
> for 12704.
It looks good. I made a few more small changes. Check my new slice… in the
future I think we make a new issue with fixes to previously integrated fixes
to keep things clear...
-
Cheers,
Sean
--
View this message in
Sean, can you look at my latest submission
for 12704.
There were some types in your slice
:= instead of =
or
each value: aBlock instead of
aBlock value:each
And an error with Announcements for FontChooser that were sent to the
PluggableListMorph too.
nicolai
Tried in Pharo3.0 update: #30651 and the following worked:
1. OCASTTranslator class>>initialise
Removed line referring to the selector and then re-initialise.
2. RBMessageNode>>isInlineIfNil
Removed the reference to the ifNil:ifNotNil: selector so not picked up as
inlined.
3. Created a
I agree that it did not belong in a feature-freeze phase. I'm sorry.
I didn't realize it would create such a problem (reminds me of substring ->
subString ha ha). There are however, valid reasons for changing the name, so
let's discuss after the release.
-
Cheers,
Sean
--
View this message
https://pharo.fogbugz.com/default.asp?12720
Screenshots and code attached.
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Issue-12720-Spec-Button-Layout-Occludes-Label-tp4739124.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On Thu, Jan 23, 2014 at 1:57 AM, Esteban Lorenzano wrote:
>
> On 23 Jan 2014, at 10:50, p...@highoctane.be wrote:
>
> I had a talk with Thierry and GitFileTree isn't supported on Windows.
>
> Due to OSProcess.
>
> Is the libgit2 going to solve that?
>
>
> yes, libgit2 will be distributed with… er…
Do whatever you want, I have no more motivation to discuss this anymore
Ben
On 24 Jan 2014, at 14:34, Pharo4Stef wrote:
> Hi guys,
>
> I think that we will rename all the asReactiveVariable that got introduced
> into their old name asValueHolder.
> And we will rename the class too to its old
https://pharo.fogbugz.com/f/cases/12718
that should fix the problem.
we’ll see :P
Esteban
On 24 Jan 2014, at 14:58, Benjamin wrote:
> Step to reproduce:
>
> Open latest Pharo30719.
> Create a new package with shortcut or menu.
> Name it ‘AST-Monkey’ (to have a RPackage not a Tag)
> Go in ano
Hi guys,
I think that we will rename all the asReactiveVariable that got introduced into
their old name asValueHolder.
And we will rename the class too to its old name.
Why?
I think that we should not change at the last moment ValueHolder into
ReactiveVariable
even if the name could be better
Thanks Max!
So you finally implemented the prunning? If true, what about opening an
issue to prune the stack in Pharo when:
1) we export from a debugger
2) the jenkins CI saves the failed test
?
Thanks!!!
On Thu, Jan 23, 2014 at 6:47 PM, Max Leske wrote:
> Hi guys
>
> So apparently somehow
Stephan Eggermont wrote
> The number of distinct authors of monticello packages is not so large.
> ...
> Can we expect issues if we replace the author string by a symbol?
> …
> I don’t think this should be a must-fix for 3.0
If it's not for 4.0, how about a real object? Something like "Authors
aut
Sean P. DeNigris wrote
> If it's not for 4.0...
Should have been "not for 3.0"… duh...
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Issue-2711-Monticello-wastes-significant-amounts-of-memory-tp4739068p4739080.html
Sent from the Pharo Smalltalk Developers mailing li
The number of distinct authors of monticello packages is not so large.
MCVersionInfo allInstances size
13984 Pharo 30716
30721 Moose 5.0 (on 30714)
(MCVersionInfo allInstances collect: [ :each | each author ]) asSet size
129 Pharo 30716
269 Moose 5.0
Can we expect issues if we replace the auth
On Jan 24, 2014, at 4:57 AM, "Nicolai Hess [via Smalltalk]"
wrote:
> Do you know this places where ifNil:ifNotNil: is called?
> If so, you coulde change them to ifWorldNil:ifWorldNotNil:
> and implement this on World, ActiveWorld, NullWorld and UndefinedObject.
If I can't do it effectively with t
On 24 Jan 2014, at 10:53, Marcus Denker wrote:
> What will it help? Who will then decide? Why does that person not help
> deciding now?
Because it requires downloading an image, loading the slices check the diff.
If in Lille this can takes few minutes (which is already long), in Chile this
is
Step to reproduce:
Open latest Pharo30719.
Create a new package with shortcut or menu.
Name it ‘AST-Monkey’ (to have a RPackage not a Tag)
Go in another package.
Select some classes.
CMD M + CMD C (and probably with the menu too) (note that the Drag n’ Drop
works)
Type the name of the package ‘AS
I wish you the best for you guys and please stay safe!
Which are the reliable channels to know whats happening and spread the word?
On Jan 22, 2014, at 15:06, Yuriy Tymchuk wrote:
> My dear Pharo friends,
>
> I have no idea if you are aware, but now a big country named Ukraine is
> facing a
On 24 Jan 2014, at 14:48, Benjamin wrote:
> On 24 Jan 2014, at 10:25, Marcus Denker wrote:
>>
>> And I can not be the only person who decides things. I think people have no
>> idea how tiring it is
>> to take a decisions like that all the time.
>>
>> The tiring thin about integrating is not
Esteban wrote:
>I would really like a reproducible case… in the form of an image, if no else.
>
>btw… moose 5.0 images are severely broken in that area, so if you are using
>one of them you *will* have problems.
I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 on mac
Op
On 24 Jan 2014, at 10:25, Marcus Denker wrote:
>
> And I can not be the only person who decides things. I think people have no
> idea how tiring it is
> to take a decisions like that all the time.
>
> The tiring thin about integrating is not the integration. It’s the fact that
> one has to *de
It is not the first time we do a release and not the last time
and in the worst case we have some updates afterwards.
So the warning is clear: no radical changes anymore. But we
should try to improve and stabilize the system (as ever).
Step by step...
Thx
T.
@Marcus: we appreciate this decisio
On 24 Jan 2014, at 14:24, Marcus Denker wrote:
>
> On 24 Jan 2014, at 14:19, Benjamin
> wrote:
>
>> On 24 Jan 2014, at 10:18, Marcus Denker wrote:
>>
>>> In beta normally we should not change things that require people to change
>>> again code...
>>
>> Then do not integrate them ...
>>
On 24 Jan 2014, at 14:19, Benjamin wrote:
> On 24 Jan 2014, at 10:18, Marcus Denker wrote:
>
>> In beta normally we should not change things that require people to change
>> again code...
>
> Then do not integrate them ...
>
The issue was “fix to include” which is defined as “do not think,
I would really like a reproducible case… in the form of an image, if no else.
btw… moose 5.0 images are severely broken in that area, so if you are using one
of them you *will* have problems.
Esteban
On 24 Jan 2014, at 13:28, Goubier Thierry wrote:
>
>
> Le 23/01/2014 18:57, Benjamin Van
On 24 Jan 2014, at 10:18, Marcus Denker wrote:
> In beta normally we should not change things that require people to change
> again code...
Then do not integrate them ...
Ben
On 24 Jan 2014, at 13:48, Benjamin wrote:
> On 24 Jan 2014, at 09:44, Marcus Denker wrote:
>> “Why do I hate it when I tried to build a new 3.0 image to improve that
>> slice, that the image building ends in :
>>
>> KeyNotFound: key #TasklistMorph not found in SystemDictionary
>>
>>
We should be restrained at the start of Pharo 4 development too because we
firstly need to improve modularization of the system. It's common that at
the start of the development cycle a huge amount of various modifications
is integrated and often with only little regards on modularization. Then to
On 24 Jan 2014, at 09:44, Marcus Denker wrote:
> “ Why do I hate it when I tried to build a new 3.0 image to improve that
> slice, that the image building ends in :
>
> KeyNotFound: key #TasklistMorph not found in SystemDictionary
>
> because of my settings?”
>
>
> WE NEED TO
On 24 Jan 2014, at 13:11, Sean P. DeNigris wrote:
> EstebanLM wrote
>> *please* stop cleaning, enhancing, and modifying the image in any way
>
> Sorry :) I got burned by Morphic in a personal project and went on a rabid
> cleaning. In all fairness, I tagged some of those "later" :-P
>
We rea
Le 23/01/2014 18:57, Benjamin Van Ryseghem a écrit :
Just that you know I faced it again :(
I created a new RPackage, move classes in the newly created RPackage.
And when I wanted to commit the code, it was empty.
Have you tried with the old Browser to see if your classes were in the
right c
I highly doubt of the usability of Nautilus even in one month and a half ...
Ben
On 24 Jan 2014, at 09:10, Sean P. DeNigris wrote:
> EstebanLM wrote
>> *please* stop cleaning, enhancing, and modifying the image in any way
>
> Sorry :) I got burned by Morphic in a personal project and went on
EstebanLM wrote
> *please* stop cleaning, enhancing, and modifying the image in any way
Sorry :) I got burned by Morphic in a personal project and went on a rabid
cleaning. In all fairness, I tagged some of those "later" :-P
-
Cheers,
Sean
--
View this message in context:
http://forum.wo
Marcus Denker-4 wrote
> 3) That definitely should be a Slot! :-)
Yes! That will be fun for 4.0 :)
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/update-3-0-30717-tp4738921p4739008.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
yes people.
*please* stop cleaning, enhancing, and modifying the image in any way but the
bugfixing need to make it run *as is*.
Of course we can discuss everything, but any change will be, if so, in Pharo 4,
not now (and Pharo 4 should start in one and a half month, so you can wait).
cheers,
I'm not sure whether to file this bug under Morphic or File System, but
when you shorten a text file and save it using the File Browser, the file
length stays the same, leaving the tail end of the previous content. For
instance, say you had a file with content
Hello World
and you shortened it to
Hi
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 8e7ba4a8cc391dd005e710a575f67791d50dbbfe
https://github.com/pharo-project/pharo-core/commit/8e7ba4a8cc391dd005e710a575f67791d50dbbfe
Author: Jenkins Build Server
Date: 2014-01-24 (Fri, 24 Jan 2014
Branch: refs/tags/30719
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 71e467f8753793c3424216b9335c8c8c4a860476
https://github.com/pharo-project/pharo-core/commit/71e467f8753793c3424216b9335c8c8c4a860476
Author: Jenkins Build Server
Date: 2014-01-24 (Fri, 24 Jan 2014
Branch: refs/tags/30718
Home: https://github.com/pharo-project/pharo-core
Branch: refs/tags/30717
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 4dee1665117ef627e5afd7f46ebe11693c079ae9
https://github.com/pharo-project/pharo-core/commit/4dee1665117ef627e5afd7f46ebe11693c079ae9
Author: Jenkins Build Server
Date: 2014-01-24 (Fri, 24 Jan 2014
Branch: refs/tags/30716
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: cf56b5f2e0f225d9482af49fbe63c15feffbf94f
https://github.com/pharo-project/pharo-core/commit/cf56b5f2e0f225d9482af49fbe63c15feffbf94f
Author: Jenkins Build Server
Date: 2014-01-24 (Fri, 24 Jan 2014
2014/1/24 Sean P. DeNigris
> Thank you everyone. Yes, the subject is a bit misleading ;) I'll give you
> my
> exact use case to make things clearly…
>
> I'm cleaning up the globals ActiveWorld and World. There are methods such
> as
> Morph>>world that sometimes return one of the above, or nil. As
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 3b685791925dae9edf5025aaae1b22f21ca34b58
https://github.com/pharo-project/pharo-core/commit/3b685791925dae9edf5025aaae1b22f21ca34b58
Author: Jenkins Build Server
Date: 2014-01-24 (Fri, 24 Jan 2014
Branch: refs/tags/30715
Home: https://github.com/pharo-project/pharo-core
Hi,
We *really* need to take care.
From what I see, people under-estimate just how much everything has
consequences…
*every*thing that we do will need multiple iterations.
Please make sure to take that into account when pushing for something to be
added to
Pharo3 instead of waiting for Pharo4.
30719
-
12703 revert DockingBarMorph>>updatePosition
https://pharo.fogbugz.com/f/cases/12703
12704 clean FontMorphChooser
https://pharo.fogbugz.com/f/cases/12704
Diff information:
http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.253.diff
http://smallta
30718
-
12519 Codepanel in ByteCode view should be read only
https://pharo.fogbugz.com/f/cases/12519
12693 TasklistMorph Navigation Cleanup
https://pharo.fogbugz.com/f/cases/12693
12705 Better implementation of a method from case 12163
https://pharo.fogbugz.com/f/case
btw… you can add a job in pharo-contribution (public and free :P ),
https://ci.inria.fr/pharo-contribution
that will run all the tests (in all platforms, if needed), so you can be sure
tests pass :)
Esteban
On 24 Jan 2014, at 09:26, Esteban Lorenzano wrote:
> Hernan,
>
> thanks for you co
Hernan,
thanks for you contribution. But it does not works in mac :(
1) Smalltalk os isMac does not exists, now is Smalltalk os isMacOSX
2) after fixing that, tests does not run either :(
Esteban
On 24 Jan 2014, at 07:25, Hernán Morales Durand
wrote:
> I have added ConfigurationOfNacl to Ph
Sean,
I find this very interesting.
Le 24/01/2014 03:11, Sean DeNigris a écrit :
> I think the tree nodes should be based on name-matching and not only
per-package
I should've appended: "as a compromise for the time being"...
In 4.0, imagine this killer combination:
- Declare high-level logic
52 matches
Mail list logo
