Sergio
there is a emacs guys in me too.
This is why I would love that somebody
- look at the key binding
- look at the key binding implementation
- look at the old package supporting per editor key binding and puths
that to us
Any taker?
Stef
On Mar 24, 2010, at 6:02 AM
11293
-
Polymorph Enhancements
- Further remembered keyboard focus fixes.
PluggableButtonMorph refactorings.
Added MultistateLabelMorph that can adapt to interaction sates from buttons.
- Fixes for invalid (mis-spelled) sizing options (hResizing/vResizing).
Layout tweaks for theme built widg
Gary can you check because the button look ugly now
<>
Stef
On Mar 24, 2010, at 12:20 PM, Stéphane Ducasse wrote:
>
> 11293
> -
>
> Polymorph Enhancements
>
> - Further remembered keyboard focus fixes.
> PluggableButtonMorph refactorings.
> Added MultistateLabelMorph that can adapt to int
argh I cannot use buttons anymore like pressing on open in MC. So I will
rollback the changes!
Houston we have a problem
Stef
On Mar 24, 2010, at 12:20 PM, Stéphane Ducasse wrote:
>
> 11293
> -
>
> Polymorph Enhancements
>
> - Further remembered keyboard focus fixes.
> PluggableBu
Seems that with Alain's refactoring the base window colours have been
changed (Browser was lightGreen and is now paleGreen, for instance). See
implementors of #patchworkUIThemeColor. So browsers are paler across the
board.
As for the menu selection colour, the attached should help (included t
thanks gary.
On Mar 24, 2010, at 12:30 PM, Gary Chambers wrote:
> Seems that with Alain's refactoring the base window colours have been changed
> (Browser was lightGreen and is now paleGreen, for instance). See implementors
> of #patchworkUIThemeColor. So browsers are paler across the board.
>
11293
-
- Issue 2202: Little Squeak fixes
- Issue 1838: ChangeSorter vs. ChangeOrganizer as entry point
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
A slightly trickier merge this time...
Best to keep current for the FuzzyLabelMorph change (somehow that has
reverted) to fix the ugly buttons.
And, perhaps, the trivial differences with respect to @- fixes.
The rest should be ok. Merges alright here.
Regards, Gary
- Original Message ---
On Mar 24, 2010, at 12:54 14PM, Gary Chambers wrote:
> A slightly trickier merge this time...
>
> Best to keep current for the FuzzyLabelMorph change (somehow that has
> reverted) to fix the ugly buttons.
Or if you liked it better, you can revert to the original version of
FuzzyLabelMorph>>dr
Indeed, though the current Pharo version has a performance benefit for
disabled buttons...
Regards, Gary
- Original Message -
From: "Henrik Johansen"
To:
Sent: Wednesday, March 24, 2010 12:07 PM
Subject: Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
On Mar 24, 2
Thanks guys
I will give it a try now.
\I'm sick so my brain works slowly
On Mar 24, 2010, at 1:07 PM, Henrik Johansen wrote:
>
> On Mar 24, 2010, at 12:54 14PM, Gary Chambers wrote:
>
>> A slightly trickier merge this time...
>>
>> Best to keep current for the FuzzyLabelMorph change (some
Join the club!
Regards, Gary
- Original Message -
From: "Stéphane Ducasse"
To:
Sent: Wednesday, March 24, 2010 12:22 PM
Subject: Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
Thanks guys
I will give it a try now.
\I'm sick so my brain works slowly
On Mar 24,
On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard wrote:
> Hi Mariano,
>
> I wonder why you mentioned O2 issues below because O2 is not in Pharo
> anymore, isn't it?
>
>
Sorry Adrian. I forgot about this email. I answer to the mail as it has an
excellent question and my bad :)
I put the O2 issue
Hi Mariano,
No problem. I was just a bit confused because I was not sure whether you
intended to add O2 back into Pharo 1.0 ;)
Cheers,
Adrian
On Mar 24, 2010, at 13:49 , Mariano Martinez Peck wrote:
> On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard wrote:
>
>> Hi Mariano,
>>
>> I wonder w
On Wed, Mar 24, 2010 at 1:53 PM, Adrian Lienhard wrote:
> Hi Mariano,
>
> No problem. I was just a bit confused because I was not sure whether you
> intended to add O2 back into Pharo 1.0 ;)
>
Yes, I know. But I asked what do you think because I don't want to get more
users confused ahahhaha
On Mar 24, 2010, at 13:56 , Mariano Martinez Peck wrote:
> On Wed, Mar 24, 2010 at 1:53 PM, Adrian Lienhard wrote:
>
>> Hi Mariano,
>>
>> No problem. I was just a bit confused because I was not sure whether you
>> intended to add O2 back into Pharo 1.0 ;)
>>
>
>
> Yes, I know. But I asked w
I do not have a definite answer. I personally prefer O2 instead of OB.
OB is more stable though, which is a big advantage.
Maybe a pool will help the community to say its word on it? Whether it
wants to see O2 included or not in Pharo 1.0. Like this, you will not
have to make an arbitrary dec
Sorry. Want I wanted to ask is...for next Pharo releases, I do the same but
making clear O2 is not by default ? or I just don't say anything about O2
in the release ?
On Wed, Mar 24, 2010 at 3:03 PM, Alexandre Bergel wrote:
> I do not have a definite answer. I personally prefer O2 instead of OB.
For Pharo 1.0 it is clear that it does not include O2.
For Pharo 1.1 we can consider adding it again if it is stable and people
express their interest in it.
So, Mariano, until we add O2 back into the main release, you don't need to
mention it anymore as part of the release log. Of course, if t
On 24 mars 2010, at 15:03, Alexandre Bergel wrote:
> I do not have a definite answer. I personally prefer O2 instead of OB. OB is
> more stable though, which is a big advantage.
> Maybe a pool will help the community to say its word on it? Whether it wants
> to see O2 included or not in Pharo 1
Dear Students,
Now it is your turn! You will have to register in our website, put there
some information, show interest for the projects and contact the project
mentors. After the registration step you will get all the mentors
information in order to contact them. By pressing the button on the
pro
Learning Montacello configuration.
Instead of writing a package dependency as
spec
package: 'CoolToolSet--Core' with: [spec requires: 'CoolBrowser ALL']
Can't we write more clearly as;
spec package: 'CoolToolSet--Core' requires: 'CoolBrowser ALL'
I find the first one far too cryptic.
Hila
Hello,
I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent).
I took the opportunity to write a ConfigurationOfDrGeo using Metacello
package management facility.
The Configuration is for now in the DrGeo repository:
http://squeaksource.com/DrGeoII/
in case someone want to t
Hi Hilaire,
I've downloaded DrGeo using this script (maybe you could advertise it the
squeaksource page),
Gofer new
url: 'http://www.squeaksource.com/DrGeoII' ;
package: 'ConfigurationOfDrGeo';
load.
((Smalltalk at: #ConfigurationOfDrGeo ) perform:#load.
But how do
I managed to open it,
DrGeo new.
but got a DNU.
FlapTab>>showFlap
PasteUpMorph>>adapToWorld:
EventHandler->does not understand #adaptToWorld
On Mar 24, 2010, at 3:55 PM, Fernando olivero wrote:
> Hi Hilaire,
>
> I've downloaded DrGeo using this script (maybe you could advertise it the
>
Right, I should document and fix that:
DrGeo sample openInWorld
Hilaire
Fernando olivero a écrit :
Hi Hilaire,
I've downloaded DrGeo using this script (maybe you could advertise it
the squeaksource page),
Gofer new
url: 'http://www.squeaksource.com/DrGeoII' ;
package: 'ConfigurationOfD
Hello,
Working great for me on rc3.
On Wed, Mar 24, 2010 at 4:22 PM, Hilaire Fernandes
wrote:
> Right, I should document and fix that:
>
> DrGeo sample openInWorld
>
> Hilaire
>
> Fernando olivero a écrit :
>>
>> Hi Hilaire,
>>
>> I've downloaded DrGeo using this script (maybe you could advert
Hi,
I'm looking at the Network-Kernel category, and found two classes that
seem unused:
-ConnectionQueue
-InternetConfiguration
I checked in the latest PharoCore, and Pharo-Dev. Also, I checked in
Pier 1.2.
No reference/subclass.
If you agree to remove them, how should I provide/package t
Yes and open an bug entry.
Stef
On Mar 24, 2010, at 4:45 PM, Bouraqadi Noury wrote:
> Hi,
>
> I'm looking at the Network-Kernel category, and found two classes that seem
> unused:
> -ConnectionQueue
> -InternetConfiguration
>
> I checked in the latest PharoCore, and Pharo-Dev. Also, I checked
this is cool hilaire!
Stef
On Mar 24, 2010, at 3:29 PM, Hilaire Fernandes wrote:
> Hello,
>
> I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent).
> I took the opportunity to write a ConfigurationOfDrGeo using Metacello
> package management facility.
>
> The Configuration i
On Mar 24, 2010, at 4:45 PM, Bouraqadi Noury wrote:
> InternetConfiguration
this one is in the startup list, on Macos.
The idea is that it sets to proxy automatically considering that this is
needed as SCG,
just imagine how much good this class did for Squeak and Smalltalk (and
Research!
keep it :)
On Mar 24, 2010, at 4:51 PM, Marcus Denker wrote:
>
> On Mar 24, 2010, at 4:45 PM, Bouraqadi Noury wrote:
>
>> InternetConfiguration
>
>
> this one is in the startup list, on Macos.
>
> The idea is that it sets to proxy automatically considering that this is
> needed
this is strange before lunch I could select Polymorph-Widgets and merge at will
and now
I cannot anymore because I got a message could not find versions for example 107
Now this is really strange because this is the first version that was merged so
normally it should be found.
It is either in th
11294
-
- Further remembered keyboard focus fixes.
PluggableButtonMorph refactorings.
Added MultistateLabelMorph that can adapt to interaction sates from buttons.
- Fixes for invalid (mis-spelled) sizing options (hResizing/vResizing).
Layout tweaks for theme built widgets due to TableLayout fi
DrGeo is a really cool system. It is great to see it in action in Pharo.
Are there any plan to integrate it into a window with menu and/or
toolbar? First I had some troubles to find out how it works :-)
Lukas
On 24 March 2010 16:49, Stéphane Ducasse wrote:
> this is cool hilaire!
>
> Stef
>
> O
during the integration I was thinking that we kept the complete ancestry.
I thought that since we merge all the times, the ancestry is kept.
My idea is that after just taking Pharo would be enough to merge.
Now this is not the case: if I look at Polymorph-Widgets for example I have
holes and thi
> this is strange before lunch I could select Polymorph-Widgets and merge at
> will and now
> I cannot anymore because I got a message could not find versions for example
> 107
This problem is to be expected when you move or delete versions.
You see this message when the closest ancestor of the
> during the integration I was thinking that we kept the complete ancestry.
> I thought that since we merge all the times, the ancestry is kept.
> My idea is that after just taking Pharo would be enough to merge.
Can you elaborate? I don't understand the last sentence.
> Now this is not the case:
Absolutely, if nothing else is in my path, it is the next thing I want
to do: using polymorph to provide a feature complete UI for DrGeo, I
have been waiting for that since a long time.
Hilaire
Lukas Renggli a écrit :
DrGeo is a really cool system. It is great to see it in action in Pharo.
A
what is strange is that when I merge the latest loaded version I got the normal
"no changes"
and I could merge without having to add a new repository.
I think that in squeak they cut the problem (if you do not have the history
what do you do).
You should still be able to merge.
Setf
On Mar 24,
> what is strange is that when I merge the latest loaded version I got the
> normal "no changes"
> and I could merge without having to add a new repository.
Sure, because in this situation the common ancestor is the version you
load (so it can always be found). And the delta between the working
c
>> during the integration I was thinking that we kept the complete ancestry.
>> I thought that since we merge all the times, the ancestry is kept.
>> My idea is that after just taking Pharo would be enough to merge.
>
> Can you elaborate? I don't understand the last sentence.
I was thinking that
On Mar 24, 2010, at 6:46 PM, Lukas Renggli wrote:
>> what is strange is that when I merge the latest loaded version I got the
>> normal "no changes"
>> and I could merge without having to add a new repository.
>
> Sure, because in this situation the common ancestor is the version you
> load (so
>> In either case there is never a hole. Each version stores the complete
>> ancestry tree it knows, that is the filename and uuid of each version.
>> The problem you run into is that you delete and move version files. If
>> Monticello cannot find the files that it refers to in its ancestry you
>>
>>> what is strange is that when I merge the latest loaded version I got the
>>> normal "no changes"
>>> and I could merge without having to add a new repository.
>>
>> Sure, because in this situation the common ancestor is the version you
>> load (so it can always be found). And the delta between
Stef and Lukas,
The other situation that I have seen these types of errors is when the package
that I am merging into(?) does not have the repository where the common
ancestor mcz file is located.
For example if I have Seaside.gemstone-dkh.500 with
http://seaside.gemstone.com/ss/seaside in it'
On Mar 24, 2010, at 7:11 PM, Lukas Renggli wrote:
>>> In either case there is never a hole. Each version stores the complete
>>> ancestry tree it knows, that is the filename and uuid of each version.
>>> The problem you run into is that you delete and move version files. If
>>> Monticello cannot
Hilaire,
Thanks for the feedback.
I've opened http://code.google.com/p/metacello/issues/detail?id=69 to track
this issue.
This might be a shortcut worth adding, since it _is_ used very frequently.
You'd still need to revert to the #package:with: form if you wanted to set
multiple attributes
>>>
> The ancestry cannot be lost. The .mcz files are the one thing that can
> disappear.
Yes I know but the result is the same.
>>
> The working copy is just one of the variable things in the merge.
> There is also the other version you load (and that might be different
> in your scenarios),
This is normal because ancestry cross over repository.
I think that there is something really strange. EIther you get a truly
distributed system or you get a local.
With MC you get a distributed which can be brittle (even if I understand well
the problem ancestry is solving).
I think that a pessi
Thanks!
http://code.google.com/p/pharo/issues/detail?id=2206
Fixed. In Inbox
Name: Graphics-MarianoMartinezPeck.225
Author: MarianoMartinezPeck
Time: 24 March 2010, 9:16:53 pm
UUID: f951fbb9-7db0-4b75-b383-ec616065476d
Ancestors: Graphics-StephaneDucasse.224
Fix to issue http://code.google.co
>> The ancestry is not broken! The problem is that you miss *ancestor
>> versions*, because they were deleted or moved.
>
> I know now since we systematically merge during our process I wonder how we
> break it.
> May be this is when you publish the smalltalk rewrite. Could check if you have
>
http://code.google.com/p/pharo/issues/detail?id=2205
In PharoInbox: Morphic-LaurentLaffont.558
As all SimpleHierarchicalListMorph & PluggableTreeMorph users put
autoDeselect to false (or
bug if not), it's now the default.
Laurent Laffont
___
Pharo-proj
Hi,
I took the RC3 dev image and I tried "ConfigurationOfMetacello
loadLatestVersion", but it fails.
I did not have time to look into this, but this is problematic :).
Cheers,
Doru
--
www.tudorgirba.com
"It's not how it is, it is how we see it."
_
On Wed, Mar 24, 2010 at 9:28 PM, Tudor Girba wrote:
> Hi,
>
> I took the RC3 dev image and I tried "ConfigurationOfMetacello
> loadLatestVersion", but it fails.
>
>
Hi Tudor. I have just tasted downloading
ConfigurationOfMetacello-DaleHenrichs.266
and it worked ok for me, no problem.
> I did no
Hi,
Sorry, I am a bit sick and did not express myself correctly. I just
wanted to point out the fact that loadLatestVersion crashes, which is
a bit strange. And for that, I just described the simple scenario to
reproduce it.
I did not want to say that it is impossible to load the latest
On Wed, Mar 24, 2010 at 9:48 PM, Tudor Girba wrote:
> Hi,
>
> Sorry, I am a bit sick and did not express myself correctly. I just wanted
> to point out the fact that loadLatestVersion crashes, which is a bit
> strange. And for that, I just described the simple scenario to reproduce it.
>
>
Ufff s
> I know now let me repeat the bug I see
>
> This is not a bug of Monticello.
It is or may be of the network because
tell me the difference between scenario 1 and scenario 2?
I think that you do not read what I'm writing. There is no difference except
that in the first scenario it barks and the
Hi folks.
In my university were I was graduated, used to teach with Dolphin few
years ago, then squeak and this semester they will probably start to teach
with Pharo. The good thing is that they have like 6 courses, with 50
students each courseso, it is good :) I hope several of them join t
On Tue, 2010-03-23 at 19:30 +0100, Hilaire Fernandes wrote:
> Bryce Kampjes a écrit :
> > On Thu, 2010-03-11 at 16:31 -0600, Chris Muller wrote:
> >> Well, I certainly care.. Stef wasn't remarking about license rights,
> >> he said didn't understand the smiley face. Frankly, I don't either.
> >>
Hi folks. Today I were talking with Noury and from our point of view, there
is a bug in the Class references.
Forget about refactoring browser. Right now, if you look for the references
of a class, it ONLY searches literal matches in the source code of methods.
It doesn't take into account for exa
> So this is probably a glitch somewhere
I doubt so.
> Lukas: I ***KNOW*** how MC branching/merging works. I KNOW IT. Now I'm trying
> to understand how the moved package
> could be moved in treated while it should have been to pharo.
I imagine that when you browsed the different repositories y
> Forget about refactoring browser. Right now, if you look for the references
> of a class, it ONLY searches literal matches in the source code of methods.
> It doesn't take into account for example if you have subclasses. In the
> abstract speaking, if there are subclasses, isn't that considered a
2010/3/24 Mariano Martinez Peck :
> Hi folks.
>
> In my university were I was graduated, used to teach with Dolphin few
> years ago, then squeak and this semester they will probably start to teach
> with Pharo. The good thing is that they have like 6 courses, with 50
> students each courseso,
Doru,
I was just a little bit worried when RC3 was shipped with a #development
blessing for 1.0-beta.25, now I have a concrete reason to be worried.
Since 1.0-beta.25 is in #development, the latestVersion of Metacello is
1.0-beta.24.1 and thats the version that gets loaded by #loadLatestVersion
Hi all
Updating a Pharo image to the latest version doesn't use the
downloaded update files as a cache for future updates. Is this done on
purpose?
Cheers,
Hernán
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.i
Hi, I've noticed every time I update a Pharo image I should rename
manually the image and changes file names to match the new updated
version number. I.e.:
If you have
PharoCore-1.1-11291-UNSTABLE.changes
PharoCore-1.1-11291-UNSTABLE.image
then update to #11295 and save and quit, you should modif
On Mar 24, 2010, at 10:35 PM, Mariano Martinez Peck wrote:
> Hi folks. Today I were talking with Noury and from our point of view, there
> is a bug in the Class references.
>
> Forget about refactoring browser. Right now, if you look for the references
> of a class, it ONLY searches literal m
68 matches
Mail list logo
