Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 20994276f5ebaf7a16734f20b4ba1e35a3a2702d
https://github.com/pharo-project/pharo-core/commit/20994276f5ebaf7a16734f20b4ba1e35a3a2702d
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/40269
Home: https://github.com/pharo-project/pharo-core
Branch: refs/tags/40270
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 678c4835011a768c138613df2cfb6c55d5d2ec8c
https://github.com/pharo-project/pharo-core/commit/678c4835011a768c138613df2cfb6c55d5d2ec8c
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Martin
you can add a paragraph saying that it is like that on old VM and that
now it is like described by eliot.
Stef
On 28/9/14 23:09, Martin McClure wrote:
On 09/28/2014 12:20 PM, Eliot Miranda wrote:
Hi Martin,
On Sep 28, 2014, at 1:18 AM, Martin McClure mar...@hand2mouse.com
wrote:
I just did a quick implementation with your idea in mind. The implementation is
very easy and looks like this:
OrderedCollection classnew
^ self new: 0
OrderedCollectiongrowSize
^ array size max: 10
I changed #growSize so that the first grow will end up having the same size the
A similar implementation is possible for HashedCollection:
HashedCollection classnew
^ self basicNew
initialize: 1 “— initialize to 1 instead of 5
HashedCollectiongrow
Grow the elements array and reinsert the old elements
| oldElements |
Hi,
now when you download a new Pharo4 image there are 3 tests failing/erroring:
Failures:
RBRenameInstanceVariableTest#testRenameInstVarAccessorsReferences
Errors:
RBRemoveClassTest#testRemoveClass
RBExtractMethodTest#testExtractMethodThatMovesTemporaryVariable
Is there an issue about that?
Branch: refs/tags/40271
Home: https://github.com/pharo-project/pharo-core
… that :)
Which means that now we have a long way to polish them until Pharo4 release.
Please test and provide feedback :)
Esteban
Oh yeah!!
On 30.09.2014, at 14:51, Esteban Lorenzano esteba...@gmail.com wrote:
… that :)
Which means that now we have a long way to polish them until Pharo4 release.
Please test and provide feedback :)
Esteban
Lovely :)
Doru
On Tue, Sep 30, 2014 at 3:00 PM, Andrei Chis chisvasileand...@gmail.com
wrote:
Cool.
Now I found the first bug :)
Seems that there is a problem with declaring variables in a playground.
Fixing it now
On Tue, Sep 30, 2014 at 2:53 PM, Max Leske maxle...@gmail.com wrote:
Oh
remember you will have to give me a 1.0.1 config version :P
On 30 Sep 2014, at 15:00, Andrei Chis chisvasileand...@gmail.com wrote:
Cool.
Now I found the first bug :)
Seems that there is a problem with declaring variables in a playground.
Fixing it now
On Tue, Sep 30, 2014 at 2:53 PM,
Could I also just provide you with a slice?
Right now Moose is still on Pharo 3 and baselines (not versions) are used
to load more or less everything.
So as soon as I'll commit something incompatible with Pharo 3 it will break
Moose.
I can also provide a version but then I'll have to commit the
Branch: refs/tags/40272
Home: https://github.com/pharo-project/pharo-core
Hi Andrei,
We are a couple of weeks away from releasing Moose.
Doru
On Tue, Sep 30, 2014 at 3:14 PM, Andrei Chis chisvasileand...@gmail.com
wrote:
Could I also just provide you with a slice?
Right now Moose is still on Pharo 3 and baselines (not versions) are used
to load more or less
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: de33c2fe729d6c4bbd7b9c3a1b3ca88514a2af44
https://github.com/pharo-project/pharo-core/commit/de33c2fe729d6c4bbd7b9c3a1b3ca88514a2af44
Author: Jenkins Build Server bo...@pharo-project.org
Date:
ok. I just need access to PharoExtras :)
Andrei
On Tue, Sep 30, 2014 at 4:02 PM, Tudor Girba tu...@tudorgirba.com wrote:
Better put it in PharoExtras. The projects under the Moose team are all
project repositories.
Doru
On Tue, Sep 30, 2014 at 3:39 PM, Andrei Chis
On 27 Sep 2014, at 09:25, Marcus Denker marcus.den...@inria.fr wrote:
On 26 Sep 2014, at 20:44, Eliot Miranda eliot.mira...@gmail.com wrote:
Hi Marcus,
On Thu, Sep 25, 2014 at 11:29 PM, Marcus Denker marcus.den...@inria.fr
wrote:
On 25 Sep 2014, at 23:02, p...@highoctane.be wrote:
username: AndreiChis
Simple enough :)
I'll create then a project Pharo4Integration in the Moose team and commit
everything there.
On Tue, Sep 30, 2014 at 3:34 PM, Tudor Girba tu...@tudorgirba.com wrote:
Sure. You just specify a repository.
Doru
On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis
done
On 30 Sep 2014, at 16:06, Andrei Chis chisvasileand...@gmail.com wrote:
ok. I just need access to PharoExtras :)
Andrei
On Tue, Sep 30, 2014 at 4:02 PM, Tudor Girba tu...@tudorgirba.com wrote:
Better put it in PharoExtras. The projects under the Moose team are all
project
thanks :)
On Tue, Sep 30, 2014 at 4:56 PM, Esteban Lorenzano esteba...@gmail.com
wrote:
done
On 30 Sep 2014, at 16:06, Andrei Chis chisvasileand...@gmail.com wrote:
ok. I just need access to PharoExtras :)
Andrei
On Tue, Sep 30, 2014 at 4:02 PM, Tudor Girba tu...@tudorgirba.com wrote:
2014-09-30 14:51 GMT+02:00 Esteban Lorenzano esteba...@gmail.com:
… that :)
Which means that now we have a long way to polish them until Pharo4
release.
Please test and provide feedback :)
Esteban
Great!
How about a new Project category in fogbugz for GTools
or should we use just Tools?
Better put it in PharoExtras. The projects under the Moose team are all
project repositories.
Doru
On Tue, Sep 30, 2014 at 3:39 PM, Andrei Chis chisvasileand...@gmail.com
wrote:
Simple enough :)
I'll create then a project Pharo4Integration in the Moose team and commit
everything there.
On
we are moving to configurations… conceptually, you *could* give us an SLICE,
but a config would be a lot better.
Esteban
On 30 Sep 2014, at 15:14, Andrei Chis chisvasileand...@gmail.com wrote:
Could I also just provide you with a slice?
Right now Moose is still on Pharo 3 and baselines
I guess a new category would make sense.
It would at least make it easy to find and keep track of those bugs related
to the GTools
On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess nicolaih...@web.de wrote:
2014-09-30 14:51 GMT+02:00 Esteban Lorenzano esteba...@gmail.com:
… that :)
Which means
new project GTools created in fogbugz :)
Esteban
On 30 Sep 2014, at 17:22, Andrei Chis chisvasileand...@gmail.com wrote:
I guess a new category would make sense.
It would at least make it easy to find and keep track of those bugs related
to the GTools
On Tue, Sep 30, 2014 at 5:00 PM,
Hi,
when fixing with configuration, this is the procedure:
1) you have to copy the configuration into the Inbox (so we keep history).
2) You complete the fields: “ConfigurationOf” and “ConfigurationVersion”. In
your case, is:
ConfigurationOf = GTPlayground
ConfigurationVersion = 1.0.1
3)
On 09/29/2014 11:36 PM, stepharo wrote:
Martin
you can add a paragraph saying that it is like that on old VM and that
now it is like described by eliot.
Right.
Regards,
-Martin
I also like configurations much more but now I need to find a way to keep
Moose running on both Pharo 3 and 4 :)
Can I say in a version that I want a particular package to be loaded form a
certain repository?
On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano esteba...@gmail.com
wrote:
we are
Sure. You just specify a repository.
Doru
On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis chisvasileand...@gmail.com
wrote:
I also like configurations much more but now I need to find a way to keep
Moose running on both Pharo 3 and 4 :)
Can I say in a version that I want a particular package
Ok. I'll do that.
Cheers,
Andrei
On Tue, Sep 30, 2014 at 5:46 PM, Esteban Lorenzano esteba...@gmail.com
wrote:
Hi,
when fixing with configuration, this is the procedure:
1) you have to copy the configuration into the Inbox (so we keep history).
2) You complete the fields:
So what did you decide to do with shortcuts?
On 30 Sep 2014, at 18:38, Andrei Chis chisvasileand...@gmail.com wrote:
Ok. I'll do that.
Cheers,
Andrei
On Tue, Sep 30, 2014 at 5:46 PM, Esteban Lorenzano esteba...@gmail.com
mailto:esteba...@gmail.com wrote:
Hi,
when fixing with
still nothing.
So now cmd+o does not work, because it collides with cmd+o+[others].
I hope now we are going to take this and move forward :)
Esteban
On Tue, Sep 30, 2014 at 6:40 PM, Yuriy Tymchuk yuriy.tymc...@me.com wrote:
So what did you decide to do with shortcuts?
On 30 Sep 2014, at
This is annoying that the backgroundColor is ovverriden by
Glamour-Morphic-Theme.
Because now backgroundColor has been removed from the system and the
Polymorph-Widgets is dirty.
and I lost 40 min because I thought that this was my new changes that
were producing this.
Now if I reintroduce
I added backgroundColor a while back to make Glamour compatible with the
dark theme.
We should remove it. Sorry, I forgot about it.
I can make a new version of glamour and submit a bugfix if you didn't do
it already.
On Tue, Sep 30, 2014 at 8:16 PM, stepharo steph...@free.fr wrote:
This is
edit: aText label: labelString accept: anAction
Open an editor on the given string/text
^(Smalltalk tools workspace openLabel: labelString)
acceptContents: aText;
acceptAction: anAction;
yourself.
- DNU
UIManager default
edit: 'jlklkjk'
label:
With the previous tools I can select a piece of text by clicking after
its last element and now I cannot
or I can but sometimes.
So what is the fix?
Stef
Hi,
I explained before but it went unnoticed. The selection happens on double
click like in any other editor.
The regular PluggableTextMorph also tries to do it on a kind of a double
click, only it is implemented as click-pause-click. So, if you click once,
wait 5 minutes, and click again, it
Hi,
sorry if this is a known thing, but I’ve just notices this and it made my day.
So in GTInspector you can browse filesystem, but when you select a fuel file,
you can press a plus” button in top right corner, and it materialises the
object. Amazing.
Uko
:)
Doru
On Tue, Sep 30, 2014 at 10:11 PM, Yuriy Tymchuk yuriy.tymc...@me.com
wrote:
Hi,
sorry if this is a known thing, but I’ve just notices this and it made my
day.
So in GTInspector you can browse filesystem, but when you select a fuel
file, you can press a plus” button in top right
On 30.09.2014, at 22:12, Tudor Girba tu...@tudorgirba.com wrote:
:)
Doru
On Tue, Sep 30, 2014 at 10:11 PM, Yuriy Tymchuk yuriy.tymc...@me.com wrote:
Hi,
sorry if this is a known thing, but I’ve just notices this and it made my day.
So in GTInspector you can browse filesystem, but
Hi,
I think that there may be sense to create a trait or at least some doc that
will say which functionality should current tools implement. Because I believe
that it is hard to find out what is used by everyone. And as we have another
tools now and some unimplemented things it makes sense to
I find click pause click useful.
No stress nor necessary adjustment of double-click delay.
What could be the intention of a user clicking repeatedly on the same area?
Did you think of it?
If copying what everyone else does is the sole value, then let's not do
Pharo.
2014-09-30 21:34 GMT+02:00
That's very nice!!!
And that ... together with the ability to define
#addPostMaterializationAction: is a super awesome combination :)
On Tue, Sep 30, 2014 at 5:17 PM, Max Leske maxle...@gmail.com wrote:
On 30.09.2014, at 22:12, Tudor Girba tu...@tudorgirba.com wrote:
:)
Doru
On Tue,
Hi,
I can see how people get use with this behavior, but I am quite certain
that the solution from PluggableTextMorph was a workaround solution due to
a missing double click event. Now we have that event and we can use it
where it is appropriate.
It's not that we copy things for the sake of
Looking at all those red exclamation marks, it looks like
there is still much to do.
Not documenting dozens of Announcement subclasses, ok, but
RubTextComposer has many many instvars.
RubParagraph has nearly 100 methods
RubTextEditor has over 200 methods.
(These are only some examples of classes
On 30 Sep 2014, at 23:50, Nicolai Hess nicolaih...@web.de wrote:
Looking at all those red exclamation marks, it looks like
there is still much to do.
Not documenting dozens of Announcement subclasses, ok, but
RubTextComposer has many many instvars.
RubParagraph has nearly 100 methods
You're right, a modal UI that would involve a triple, quadruple click or
cycle between even more states would be annoying.
But just switching a selection, how so? Personnally I don't mind. Is it a
matter of taste?
Anyway, the whole text editor is modal, mind you, did you see this thing
named
Hi,
On Wed, Oct 1, 2014 at 12:47 AM, Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com wrote:
You're right, a modal UI that would involve a triple, quadruple click or
cycle between even more states would be annoying.
But just switching a selection, how so? Personnally I don't mind. Is it a
Hi,
On Tue, Sep 30, 2014 at 11:50 PM, Nicolai Hess nicolaih...@web.de wrote:
Looking at all those red exclamation marks, it looks like
there is still much to do.
Not documenting dozens of Announcement subclasses, ok, but
RubTextComposer has many many instvars.
RubParagraph has nearly 100
On Tue, Sep 30, 2014 at 11:54 PM, Sven Van Caekenberghe s...@stfx.eu
wrote:
On 30 Sep 2014, at 23:50, Nicolai Hess nicolaih...@web.de wrote:
Indeed, the same is true for some GT classes (I was looking at
Glamour-Morphic-Pager-Morphic): no (a few) class comments, let alone method
comments.
Hi,
I think that acceptAction: should not be the responsibility of the
playground and that we should implement this behavior with a different
widget.
Cheers,
Doru
On Tue, Sep 30, 2014 at 10:20 PM, Yuriy Tymchuk yuriy.tymc...@me.com
wrote:
Hi,
I think that there may be sense to create a
Hi Mariano,
I am not sure I understand the implication of using
addPostMaterializationAction:
in combination with the inspector materialization extension. Where do you
see the opportunity?
Cheers,
Doru
On Tue, Sep 30, 2014 at 10:52 PM, Mariano Martinez Peck
marianop...@gmail.com wrote:
On 01 Oct 2014, at 06:45, Tudor Girba tu...@tudorgirba.com wrote:
On Tue, Sep 30, 2014 at 11:54 PM, Sven Van Caekenberghe s...@stfx.eu wrote:
On 30 Sep 2014, at 23:50, Nicolai Hess nicolaih...@web.de wrote:
Indeed, the same is true for some GT classes (I was looking at
is Kommiter working for you in 40 latest?
Because I get an error tellling to me that it cannot find Applications /
Pharo?
On 01.10.2014, at 07:37, stepharo steph...@free.fr wrote:
is Kommiter working for you in 40 latest?
Because I get an error tellling to me that it cannot find Applications /
Pharo?
It works, but it’s a pain to use for slices (dependencies not included if they
are not dirty, weird problems
I find click pause click useful.
Me too.
No stress nor necessary adjustment of double-click delay.
What could be the intention of a user clicking repeatedly on the same
area?
Did you think of it?
If copying what everyone else does is the sole value, then let's not
do Pharo.
2014-09-30
I do not get your point. I do not see why this is mode.
If the cursor is already on something or at the end or beginning of
something clicking on the same place, select it.
This is just different but it works. and it is not incompatible with
also supporting double clicking. So why now we
cannot
On 1/10/14 00:47, Nicolas Cellier wrote:
You're right, a modal UI that would involve a triple, quadruple click
or cycle between even more states would be annoying.
But just switching a selection, how so? Personnally I don't mind. Is
it a matter of taste?
Anyway, the whole text editor is modal,
61 matches
Mail list logo
