done
and thanks!!!
On 03 Jan 2014, at 00:22, Hilaire Fernandes hilaire.fernan...@gmail.com wrote:
Hello,
I want to commit a slice.
username: HilaireFernandes
Thanks
--
Dr. Geo http://drgeo.eu
Hi,
I've run into one of my favorite problems in Smalltalk and decided to
try the list. Please don't shoot me on this one; perhaps you've run
into it yourself. If there are discussions that I should read, please
send me some info.
My first assumption is that the difference between printString
Hi Marcus (and others)
On 20 Dec 2013, at 23:10, vfclists . vfcli...@gmail.com
mailto:vfcli...@gmail.com wrote:
Anyone noticed or tried Gravel?
https://github.com/gravel-st/gravel
Gravel aims to be fullyANSI Smalltalk
http://wiki.squeak.org/squeak/172 compatible.”
— the author has no
On 03 Jan 2014, at 10:15, Jan Vrany jan.vr...@fit.cvut.cz wrote:
Hi Marcus (and others)
On 20 Dec 2013, at 23:10, vfclists . vfcli...@gmail.com
mailto:vfcli...@gmail.com wrote:
Anyone noticed or tried Gravel?
https://github.com/gravel-st/gravel
Gravel aims to be fullyANSI
On 03 Jan 2014, at 00:04, Hilaire Fernandes hilaire.fernan...@gmail.com wrote:
Le 02/01/2014 20:37, Marcus Denker a écrit :
I always use “merge”. “Changes” will e.g. show all the changes towards
everything changed
in between, too.
For me this is weird, I can't understand the logic.
Hi Sebastian,
I feel your pain :)
we are aiming to focus Pharo 4 in “modularisation and tools”, to enhance what
we have currently.
Now… one of the biggest problems we have is that people is so used to the old
tools that they don’t even realise that we can do a lot better. And most
possible
On 03 Jan 2014, at 10:32, Marcus Denker marcus.den...@inria.fr wrote:
On 03 Jan 2014, at 01:01, Sebastian Sastre sebast...@flowingconcept.com
wrote:
Changes reads
Merge writes
In order to make safe a potentially dangerous operation, the write is done
in two steps so the user can
Thanks for explanation. Jan
On 03/01/14 10:19, Marcus Denker wrote:
On 03 Jan 2014, at 10:15, Jan Vrany jan.vr...@fit.cvut.cz wrote:
Hi Marcus (and others)
On 20 Dec 2013, at 23:10, vfclists . vfcli...@gmail.com
mailto:vfcli...@gmail.com wrote:
Anyone noticed or tried Gravel?
Thanks for bringing this up.
Yes, we should care about usability.
And I agree that usability is attainable as long as you approach it with
consistent discipline. It's similar to designing code: you start asking
questions, figure out what the right questions are, and then stick to it.
I like
I’ve asked the author of Gravel to show it to us at Fosdem2014.
He wants to, but might not be able to make it due to expected
family expansion.
Stephan
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 441a2ef1edbf4a433d65aeb7a26e24ea9a21c3a0
https://github.com/pharo-project/pharo-core/commit/441a2ef1edbf4a433d65aeb7a26e24ea9a21c3a0
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/30669
Home: https://github.com/pharo-project/pharo-core
Le 03/01/2014 10:31, Marcus Denker a écrit :
From then the change was made *other* changes have been done.
“Change” will show *all* differences, both the ones other integrations
did to the package as well as the changes of the slice.
In addition, there is still some bug that when e.g
Hi
The summary version of my view below:
#printString and #printOn: protocol should be used for printing and #asString
for conversion. This implies that #asString should not depend on #print
protocol.
On 03 Jan 2014, at 10:33 AM, Otto Behrens o...@finworks.biz wrote:
My first assumption is
#printString and #printOn: protocol should be used for printing and #asString
for conversion. This implies that #asString should not depend on #print
protocol.
Ah, I used it the other way around: printOn depends on asString. I saw
'conversion' as the lower level.
Why do you distinguish here
On 3 January 2014 11:24, Otto Behrens o...@finworks.biz wrote:
#printString and #printOn: protocol should be used for printing and
#asString for conversion. This implies that #asString should not depend on
#print protocol.
Ah, I used it the other way around: printOn depends on asString. I
OK. Here's some code to demonstrate the bug:
wrap := AthensWrapMorph new
extent: 100 @ 100;
yourself.
black := Morph new
extent: 100 @ 100;
color: Color black;
yourself.
red := Morph new
extent: 100 @ 50;
color: Color red;
yourself.
transparent := Morph new
2014/1/3 Hilaire Fernandes hilaire.fernan...@gmail.com
Le 03/01/2014 10:31, Marcus Denker a écrit :
From then the change was made *other* changes have been done.
“Change” will show *all* differences, both the ones other integrations
did to the package as well as the changes of the slice.
'Conversion' implies using the resulting String in some further
computation. 'Printing' usually implies displaying something to the
user (and nothing more), or serialising to a file/network.
What kinds of computation are you thinking of regarding a string? I
think I understand what you're
Our engineering bias make us think too literally some times.
Let's stay scientific but use the designer hat instead of the mathematician hat.
I know is for the web, but don't you have the feeling that you can design an
experiment in a way that will converge to the same usability principles?
As somebody coming from the HCI side, rather than the software engineering
/ programming language side, I too value usability. But, it seems to me
that you first do the major changes and then slowly hone to get usability
right. I find lots of small little usability bugs in Pharo 3.0 but I assume
On 3 January 2014 11:44, Otto Behrens o...@finworks.biz wrote:
'Conversion' implies using the resulting String in some further
computation. 'Printing' usually implies displaying something to the
user (and nothing more), or serialising to a file/network.
What kinds of computation are you
Hi Sebastian,
I think you read my mail too literally :).
We do not disagree. My comment about Don't make me think is that what
applies for the web is not quite the same as for a programming environment.
For example, on the web, it is more profitable to assume that everyone is a
newcomer, while
On 03 Jan 2014, at 12:56, J.F. Rick s...@je77.com wrote:
As somebody coming from the HCI side, rather than the software engineering /
programming language side, I too value usability. But, it seems to me that
you first do the major changes and then slowly hone to get usability right. I
Sebastian wrote
Cheap idea for us:
Good idea for a bit later, and for the new parts.
We already have a number of well-known problems for new users.
If we don’t eliminate them first, we’re not going to find much new
issues. They will be hidden behind:
- no discoverable way of creating classes
I felt we didn't disagree but wanted open that line of conversation because it
sounds heathy :D
I agree the tests for our tool aren't going to be the same as for many web
sites/apps. One thing is to try to create a great experience for woman buying
shoes in the web and another is computer
If anyone wants the solution for
https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
before Jan 26, please remember Camillo is working on his PhD till then. (needs
reviewing)
Stephan
In my experience with Pharo and other Smalltalks as well:
#printString is used for debugging, that's why the default
implementation shows the class name. It's implemented using #printOn:
#displayString (deprecated in Pharo*) is used to display the object in
the UI. It is implemented by means of
If that's the case the UI curators should decide what are those 3 priority
issues
We can jump to these:
7. Don't panic by overwhelming issues. Discuss with colleagues or publish in a
private wiki for the team or something
8. Decide what are the 3 most blocking entry barriers and show that to
To me #asString is meant to be used when you need an object with the String
protocol.
As mentioned it looks like the seaside #asString and #greaseString are meant
for displaying which causes the confusion but I’m not sure why #displayString
was removed apart from the obvious reasons of trying
I do not get that. As far as I can tell, the fix is already integrated :).
Doru
On Fri, Jan 3, 2014 at 1:29 PM, Stephan Eggermont step...@stack.nl wrote:
If anyone wants the solution for
https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
On 02.01.2014, at 14:07, Marcus Denker marcus.den...@inria.fr wrote:
On 02 Jan 2014, at 11:49, Volkert Barr volk...@nivoba.de wrote:
On 01.01.2014, at 19:26, Stéphane Ducasse stephane.duca...@inria.fr wrote:
I understand that community support is needed, and yes i am willing to
Hi!Apparently, the width (in pixels) of a stroke in athens seems to vary with the size of the path. Am I right?For example, I have the following rendering:There is just one code to draw a box, which is: athensCanvas pathTransform restoreAfter: [ athensCanvas pathTransform translateBy: rectangle
Doru wrote:
I do not get that. As far as I can tell, the fix is already integrated :).
No, it needs to be resolved to Fix to be included.
Stephan
Hmm, strange. It was available in 30666, but it is not available anymore in
30669.
Was it reverted because it was not good, or was it because of another issue?
Doru
On Fri, Jan 3, 2014 at 2:14 PM, Stephan Eggermont step...@stack.nl wrote:
Doru wrote:
I do not get that. As far as I can tell,
I liked this distinction between printString and displayString.
It was removed probably because it was a mess :)
Stef
In my experience with Pharo and other Smalltalks as well:
#printString is used for debugging, that's why the default
implementation shows the class name. It's implemented
Hi Natalia,
On Fri, Dec 27, 2013 at 11:20 PM, Natalia Tymchuk
natalia.tymc...@unikernel.net wrote:
I write a chapter to Pharo for the Enterprise. And I want to compile it,
but when I executing ./compile.sh DSL/DSL.pier, like it is writen here:
Doru wrote:
Hmm, strange. It was available in 30666, but it is not available anymore in
30669.
Was it reverted because it was not good, or was it because of another issue?
It was never there. Did you by change load the slice in your 30666?
Stephan
Hi all,
Currently I build my QCMagritte only for Pharo 2.0, loading version 3.0.9 of
Seaside. I should probably extend this to build both for Seaside 3.1 and Pharo
3.0, but here I run into trouble. The version with Seaside 3.0.9 won't work on
Pharo 3. So if I make this matrix, I will get one
On 03 Jan 2014, at 1:58 , Alexandre Bergel alexandre.ber...@me.com wrote:
Hi!
Apparently, the width (in pixels) of a stroke in athens seems to vary with
the size of the path. Am I right?
For example, I have the following rendering:
Screen Shot 2014-01-03 at 9.54.29 AM.png
There
Hi,
I tried to recover lost changes but I failed.
I used the item in tools menu and I followed the expected actions, but I was
not able to find the lost changes in my image; where do they go?
Is there any place where I can find details about the expected results and
understand what I missed?
Oops :)
Doru
On Fri, Jan 3, 2014 at 3:04 PM, Stephan Eggermont step...@stack.nl wrote:
Doru wrote:
Hmm, strange. It was available in 30666, but it is not available anymore
in 30669.
Was it reverted because it was not good, or was it because of another
issue?
It was never there. Did
I think we can do better :P (with still a workaround)
Let me digest my jet lag (just arrived at Santiago) and I will give you a real
answer :P
Ben
On 02 Jan 2014, at 20:16, Sean P. DeNigris s...@clipperadams.com wrote:
Benjamin Van Ryseghem-2 wrote
A dirty patch in the meantime would be to
+1. In all tools I wrote, I felt the need for some sort of #displayString,
and sooner or later I introduced it in some form.
Doru
On Fri, Jan 3, 2014 at 1:39 PM, Carlo snoob...@gmail.com wrote:
To me #asString is meant to be used when you need an object with the
String protocol.
As
Hi,
in Nautilus there is a menu Analyze - Class refs... to see where a class
is used.
When I select a trait it is not displayed in the menu, but CMD+N is also
working when I select
a Traits name in the code pane. Is it by intention to not browse refs for
traits or a bug in the menu?
How
On 03 Jan 2014, at 16:48, Torsten Bergmann asta...@gmx.de wrote:
Hi,
in Nautilus there is a menu Analyze - Class refs... to see where a
class is used.
When I select a trait it is not displayed in the menu, but CMD+N is also
working when I select
a Traits name in the code pane. Is
On 3 January 2014 12:38, J.F. Rick s...@je77.com wrote:
OK. Here's some code to demonstrate the bug:
wrap := AthensWrapMorph new
extent: 100 @ 100;
yourself.
black := Morph new
extent: 100 @ 100;
color: Color black;
yourself.
red := Morph new
extent: 100 @ 50;
On 03 Jan 2014, at 12:04, Hilaire Fernandes hilaire.fernan...@gmail.com wrote:
Le 03/01/2014 10:31, Marcus Denker a écrit :
From then the change was made *other* changes have been done.
“Change” will show *all* differences, both the ones other integrations
did to the package as well as the
Right: scaling scales everything not just geometry.
this is intentionally done so, that you have a uniform way to scale up/down
whole scenery i.e.
if you want to render same scene but 2 times bigger , just put 'scaleBy: 2'
before and you done,
and it will be exactly 2 times bigger (as if you
hi guys
my doc stopped me because I’m exhausted so see you in two weeks.
Stef
Take care Stéphane.
Hope to see soon here in good health.
On Fri, Jan 3, 2014 at 5:10 PM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
hi guys
my doc stopped me because I’m exhausted so see you in two weeks.
Stef
--
Serge Stinckwich
UCBN UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends
Look after yourself
Olivier :-)
Le 3 janv. 2014 17:10, Stéphane Ducasse stephane.duca...@inria.fr a
écrit :
hi guys
my doc stopped me because I’m exhausted so see you in two weeks.
Stef
Hi Otto,
2014/1/3 Otto Behrens o...@finworks.biz:
#printString is used for debugging, that's why the default
implementation shows the class name. It's implemented using #printOn:
Makes sense. So unless there's a nice symbol that one can add to show
what it is (eg #foo printString = '#foo'),
Hi,
I've just made an executable file for installing Pharo on Windows (in
program files, with a shortcut in the Start menu...). Please try
it and report problems:
https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Win-Package/lastSuccessfulBuild/artifact/pharo-ci/pharo_installer.exe
Best,
to make stroke width unaffected by scale, you obviously will need to scale
it down by same factor as you scaled geometry i.e.:
canvas pathTransform scaleBy: factor.
strokePaint width: myWidth/factor.
On 3 January 2014 17:08, Igor Stasenko siguc...@gmail.com wrote:
Right: scaling scales
2014/1/3 Marcus Denker marcus.den...@inria.fr
On 03 Jan 2014, at 16:48, Torsten Bergmann asta...@gmx.de wrote:
Hi,
in Nautilus there is a menu Analyze - Class refs... to see where a
class is used.
When I select a trait it is not displayed in the menu, but CMD+N is also
working
So, Kevin, I separeted the x-axs labels as you requested, you can try it, just
do:
| diagram | diagram := GETDiagramBuilder new. diagram
verticalBarDiagram models: (-10 to: 10); color: [ :each
| (each 0) ifTrue: [ Color blue ] ifFalse: [ Color red ] ];
Stef wrote:
my doc stopped me because I’m exhausted so see you in two weeks.
Please take care of yourself.
Stephan
Le 03/01/2014 17:10, Stéphane Ducasse a écrit :
my doc stopped me because I’m exhausted so see you in two weeks.
Hope you will not transform these two weeks in two days ;-)
Take care
Hilaire
--
Dr. Geo http://drgeo.eu
to make stroke width unaffected by scale, you obviously will need to scale it
down by same factor as you scaled geometry i.e.:
canvas pathTransform scaleBy: factor.
strokePaint width: myWidth/factor.
Thanks Igor! This works like a charm.
I have been intensively working with Athens for a
So we don't have this in Pharo anymore. Looks like it is mostly
asString now. But then, really,
Object asString
^ self printString
does not make sense?
why not as a default?
I never fully understood the intention of #asString other than to
convert the object to the String
How are we going to tell that our DateAndTime does not understand #date nor
#time? (and keep our face straight)
Sorry for the drama but hey... the raison d'être, its meaning, the purpose in
the life of a DateAndTime is to make you able to send messages about date and
time :D
How come that the
Good doctor. Smart patient :)
Take care!
Doru
On Fri, Jan 3, 2014 at 5:10 PM, Stéphane Ducasse
stephane.duca...@inria.frwrote:
hi guys
my doc stopped me because I’m exhausted so see you in two weeks.
Stef
--
www.tudorgirba.com
Every thing has its own flow
On 03 Jan 2014, at 18:50, Sebastian Sastre sebast...@flowingconcept.com wrote:
How are we going to tell that our DateAndTime does not understand #date nor
#time? (and keep our face straight)
Sorry for the drama but hey... the raison d'être, its meaning, the purpose in
the life of a
BTW
DateAndTime today class = DateAndTime. true
DateAndTime today asTimeStamp class = TimeStamp. true
DateAndTime today asTimeStamp asDateAndTime = DateAndTime. false (stays as
TimeStamp)
o.O
On Jan 3, 2014, at 3:50 PM, Sebastian Sastre sebast...@flowingconcept.com
wrote:
How are
On 03 Jan 2014, at 18:57, Sebastian Sastre sebast...@flowingconcept.com wrote:
BTW
DateAndTime today class = DateAndTime. true
DateAndTime today asTimeStamp class = TimeStamp. true
DateAndTime today asTimeStamp asDateAndTime = DateAndTime. false (stays as
TimeStamp)
o.O
And
yeah is what I'm using now but the 'as' means conversion while the #date and
#time suggest delegating access to the other guy
returning to the question.. is that omission intentional then?
I mean..
There are counter intuitive things that are cool.
This isn't one of those.
This one sounds a
On Jan 3, 2014, at 4:01 PM, Sven Van Caekenberghe s...@stfx.eu wrote:
TimeStamp is on the way out since it hardly differs from DateAndTime and
confuses the hell out of everyone. This discussion is independent of which
name is best.
I'm cool about keeping only one.
Omitting the basics,
I can’t defend the API choice.
But consider this: contrary to the name, a DateAndTime is much more that just a
Date + a Time, it has a timezone offset and fractional seconds. That could be
reason why there are #asDate and #asTime as conversion methods instead of #date
and #time as accessors.
Yeah Sven, I know timezones can be hell.
Actually for me this isn't an issue as already ported my code with asDate and
asTime.
What worries me is the thinking behind that omission
Why?
Because you don't know where it will bite you next.
But it will
And it wont be intuitive
On Jan 3,
On 01/03/2014 12:33 AM, Otto Behrens wrote:
Hi,
I've run into one of my favorite problems in Smalltalk and decided to
try the list. Please don't shoot me on this one; perhaps you've run
into it yourself. If there are discussions that I should read, please
send me some info.
Hi Otto,
Well,
Hi guys,
anyone here using SIXX?
I'm having a consistent problem in opening a SixxReadStream on a file that has
~10MB of serialized objects.
Smaller than that is all good
Bigger, raises SixxXmlParseError
ideas?
Maybe I'm using the wrong version of XMLDOMParser?
patches? workarounds?
It's probable unrelated to size as expected.
For the record:
I've changed the XMLParser and the new one complained about a problem on a
specific line that has this content
sixx.object sixx.id=1106 sixx.name=key sixx.type=String
name/sixx.object
Thanks, Martin.
I second your summary.
Doru
On Fri, Jan 3, 2014 at 8:55 PM, Martin McClure mar...@hand2mouse.comwrote:
On 01/03/2014 12:33 AM, Otto Behrens wrote:
Hi,
I've run into one of my favorite problems in Smalltalk and decided to
try the list. Please don't shoot me on this
Sebastian
You should consider that often there were no decision: just old code designed
sometimes
even before Design Patterns and any of the book on oo design we know today.
No more. Then the system grew organically, then we arrived and started to
revisit but
sometimes we did not see the
On 03 Jan 2014, at 21:07, Sebastian Sastre sebast...@flowingconcept.com wrote:
It's probable unrelated to size as expected.
For the record:
I've changed the XMLParser
how?
I do not know if SIxx fixes the version of the XML parser it uses.
and the new one complained about a problem
I agree and especially on the fact that conversion methods should be between
“polymorphic” objects
else we end up having everything converted/able.
this is why asOrderedCollection asBag… are all between collections.
So a good proposal would be to understand if we can remove asString from
On 3 January 2014 20:07, Sebastian Sastre sebast...@flowingconcept.com wrote:
It's probable unrelated to size as expected.
For the record:
I've changed the XMLParser and the new one complained about a problem on a
specific line that has this content
sixx.object sixx.id=1106 sixx.name=key
Can someone change PharoVM build configs
regarding issue 12493 https://pharo.fogbugz.com/default.asp?12493
Sound does not work for Windows and Linux VMs because
windows) PharoVMBuilder does not include soundplugin in the windows config
linux) vm-sound-alsa has unresolved externals - can not be
On Jan 3, 2014, at 7:43 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote:
I've changed the XMLParser
how?
With this guy:
ConfigurationOfXMLParser load.
from MetaRepoForPharo30
I've discovered that its part of a JsonObject that holds the facebook profile
associated with the user.
SIXX is cool but I'm with the feeling that it's time to give fuel a chance
On Jan 3, 2014, at 8:01 PM, Frank Shearar frank.shea...@gmail.com wrote:
On 3 January 2014 20:07, Sebastian
Makes sense.
Thanks Stef I will
On Jan 3, 2014, at 7:41 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote:
Sebastian
You should consider that often there were no decision: just old code designed
sometimes
even before Design Patterns and any of the book on oo design we know today.
I love the item count - thanks. I saw the double jump too, but the cause wasn't
obvious. And I see what you mean about the arrows; I'll look into it.
I'm really enjoying the collaboration :)
-
Cheers,
Sean
--
View this message in context:
Benjamin Van Ryseghem-2 wrote
I think we can do better :P (with still a workaround)
I was being a bit dramatic ;) I ended up with a slightly less depressing:
open
| windowModel labelMorphs |
windowModel := self new openWithSpec.
labelMorphs := windowModel window
84 matches
Mail list logo
