On Fri, Jan 30, 2009 at 9:00 AM, Andreas Raab andreas.r...@gmx.de wrote:
Since you're compiling the VM yourself, you might want to add a guard that
catches the condition and prints out the environmental values (oldLimit,
delta, newSize, newDelta). I would suspect that this is a signed/unsigned
Not for newbies.
People really look at the package before its contents.
We should give them a chance.
Stef
On Jan 29, 2009, at 6:59 PM, Gary Chambers wrote:
Indeed... though that does make you focus on the underlying stuff
and give
an opportunity for changing the image to improve your lot!
Lukas
so do I understand correctly that your point is to replace
asByteArray by #[]
Stef
On Jan 30, 2009, at 8:47 AM, Lukas Renggli wrote:
I committed a patch that adds literal byte arrays to Pharo, with the
same syntax as most other Smalltalk do (VW, VASt, GST).
so do I understand correctly that your point is to replace
asByteArray by #[]
Yes, instead of writing
#( 1 2 3 ) asByteArray
you write
#[ 1 2 3 ]
Which is much faster and saves memory, as no conversion and no copying
happens at runtime. All Smalltalk dialects (with the
Running ScriptLoader loadOB fails at some point because it tries to load
http://source.wiresong.ca/ob/OB-Enhancements-dr.291
instead of http://source.wiresong.ca/ob/OB-Enhancements-dr.291.mcz
Fixed, thank you.
Thanks!
David
___
Pharo-project
Hi all,
while working on the unicode cleanup I ran into the current
implementation of
CharacterstoreBinaryOn: aStream
Store the receiver on a binary (file) stream
value 256
ifTrue:[aStream basicNextPut: self]
ifFalse:[Stream nextInt32Put: value].
Buttons - after loading you should reselect your theme to initialize the forms
used for square button corners.
menu selection - not sure what you mean. Is it a menu or a popup choice (in
which case spacebar should be used to choose option since enter is likely to
activate the default button in
Provoost, P (Paul) wrote:
I have the same problem when compiling the vm on OpenSolaris 2008-11
using the SUN compilers. So please do some more testing with the
4.3.2. version, after all we cannot stick to old compilers, can we?
Some VM maintainers can ;-)
Windows is still officially compiled
Michael Rueger wrote:
Provoost, P (Paul) wrote:
I have the same problem when compiling the vm on OpenSolaris 2008-11
using the SUN compilers. So please do some more testing with the
4.3.2. version, after all we cannot stick to old compilers, can we?
Some VM maintainers can ;-)
Windows is
On Fri, Jan 30, 2009 at 09:14:33AM +0100, Damien Cassou wrote:
On Fri, Jan 30, 2009 at 9:00 AM, Andreas Raab andreas.r...@gmx.de wrote:
Since you're compiling the VM yourself, you might want to add a guard that
catches the condition and prints out the environmental values (oldLimit,
Hi Gary,
On Jan 30, 2009, at 13:10 , GARY CHAMBERS wrote:
Buttons - after loading you should reselect your theme to initialize
the forms used for square button corners.
ok, works.
menu selection - not sure what you mean. Is it a menu or a popup
choice (in which case spacebar should be
Hi all,
are there any other tests available for the Multilingual stuff other
than MultilingualTests-TextConversion?
Would like to avoid re-inventing the wheel...
Michael
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
br...@kampjes.demon.co.uk wrote:
But Monticello packages are just a naming scheme.
yes and no. A package is defined using the name and string matching, but
a package is a package.
Your statement: That would also allow to simply load all plugins into
a VMMaker image by using a package
On Fri, Jan 30, 2009 at 9:00 AM, Andreas Raab andreas.r...@gmx.de wrote:
Since you're compiling the VM yourself, you might want to add a guard that
catches the condition and prints out the environmental values (oldLimit,
delta, newSize, newDelta). I would suspect that this is a signed/unsigned
Lukas,
I had pretty much resigned to going without this - not sure why given
how much I grip about other stuff :) There are indeed efficiency
considerations, but it's also a big step in compatibility.
THANKS!!!
Bill
Wilhelm K. Schwab, Ph.D.
University of Florida
Department of
OB buttons - David and I will get there eventually!
yep.
I integrated your patch, but it needs some fine-tuning.
There are still places where OB directly sets button colors. This is easy to
fix.
The bigger problem is that with your patch we get problems in all other systems
not
using
Not to add any pressure or be annoying, but what is the current estimate of
when 1.0 will
be released? I am just curious.
-- Original message --
From: Stéphane Ducasse stephane.duca...@inria.fr
Use pharo (better UI).
Once we will have pharo 1.0 we will work on pharo
Maybe this is something the compiler could do without extending the
syntax since, I far as I understood,
#(...) asByteArray is always equivalent to#[...]
Statically, the compiler could make the conversion. No?
Alexandre
On 30 Jan 2009, at 10:55, Lukas Renggli wrote:
so do I understand
Before esug I hope.
Alexandre
On 30 Jan 2009, at 15:20, michael_atkis...@comcast.net wrote:
Not to add any pressure or be annoying, but what is the current
estimate of when 1.0 will
be released? I am just curious.
-- Original message --
From: Stéphane Ducasse
On Jan 30, 2009, a
The same convention could also be applied to test packages btw to
avoid
all this very creative naming, patching the test somewhere into
the
category name.
YES
so what are the organizations we can use?
Ideally I would like to have the test associated with their
ideally we planed for march now what is left to do:
- trait fixes
- etoy removal
- licensing.
Stef
On Jan 30, 2009, at 3:20 PM, michael_atkis...@comcast.net wrote:
Not to add any pressure or be annoying, but what is the current
estimate of when 1.0 will
be released?
Stéphane Ducasse wrote:
so what are the organizations we can use?
Ideally I would like to have the test associated with their packages.
XXX
XXXTests
The problem with that naming scheme is that then the tests would always
be loaded together with their tests because of the simple string
Statically, the compiler could make the conversion. No?
Sure, that would be a possibility, but it is not standard.
Almost all modern Smalltalk implementations support the #[ ] syntax.
The parsers of the NewCompiler and the RefactoringBrowser already
support the syntax for literal byte arrays
so what are the organizations we can use?
Ideally I would like to have the test associated with their packages.
XXX
XXXTests
but may be people found a better way
That doesn't work, because you end up with overlapping package names.
This is how we name packages in Seaside 2.9:
On 30.01.2009, at 15:32, Stéphane Ducasse wrote:
ideally we planed for march now what is left to do:
- trait fixes
- etoy removal
- licensing.
Yes, this is what is left from the list of things for 1.0 (and: use
TT fonts by default).
I hope to be able to work again on
Yes, I can't recall it was what 50% of the performance of a 3.x
compile out of the box, and after *much*
tweaking of compiler flags it was mmm just 20% slower.. Well
certainly the performance impact was measured in 10 of percent.
On 30-Jan-09, at 4:33 AM, Michael Rueger wrote:
John
On Jan 30, 2009, at 15:32 , Stéphane Ducasse wrote:
ideally we planed for march now what is left to do:
- trait fixes
- etoy removal
- licensing.
...there is some more stuff. This is also documented at
http://code.google.com/p/pharo/wiki/Milestones
- default in-image
Hi Adrian,
Furthermore, In the OB Browser there are two types of blue buttons. It
would be nice to have a consistent style for buttons.
What exactly do you mean with two styles of blue buttons? One style for
instance / ?
/ class buttons and different one for browse, hierarchy, variables,
Thanks, Gary, for this new patch. Indeed this works better. :)
I adapted some parts and committed it for the moment. From the Polymorph point
of
view: Is this what you need?
Because I need to adapt it again as OB does not work properly in Squeak now, so
I
would like to know whether it does
Good news Stef.. we will use Pharo in our course Software Atèlier IV
- Software Engineering for Web Development.
cheers
Marco
On Jan 29, 2009, at 6:23 PM, Stéphane Ducasse wrote:
Btw if you use pharo please let us know because this is important for
us that we list such use
and also the
Hi David,
I meant the two different styles of blue buttons that you see on the
screenshot below.
Is this the latest version I am looking at?
Cheers,
Adrian
inline: Picture 4.png
On Jan 30, 2009, at 16:01 , David Röthlisberger wrote:
Hi Adrian,
Furthermore, In the OB Browser there are
I meant the two different styles of blue buttons that you see on the
screenshot below.
Is this the latest version I am looking at?
no, can you execute 'ScriptLoader loadOBAlpha' to get the latest version?
David
On Jan 30, 2009, at 16:01 , David Röthlisberger wrote:
Hi Adrian,
Hi,
There are a couple of issues I stumbled across in Pharo and I thought
of reporting them:
- When loading Pier and Seaside there were some Warnings related to
some instance variables that blocked the loading. This is a rather
strange behavior, especially given that they are warnings. I
I notice the back/forward buttons are created with a morph as the label. Might
be better to refactor OBDraggableButton to be under PluggableButtonMorphPlus
(or implement enablement protocol) and use just a string or text, using
enablement rather than on/off state - that should help avoid use
On Jan 30, 2009, at 17:19 , David Röthlisberger wrote:
I meant the two different styles of blue buttons that you see on the
screenshot below.
Is this the latest version I am looking at?
no, can you execute 'ScriptLoader loadOBAlpha' to get the latest
version?
yep, that looks nice.
mmm, let me clarify. I currently use Apple's GCC 4.0.1 i686-apple-
darwin9-gcc-4.0.1
that works fine for macintel, 3.3 is required for decent performance
on powerpc.
The version that I worked with Michael on was the LLVM GCC 4.2 and or
GCC 4.2. Michael I believe tried GCC 4.3
Michael
On Jan 29, 2009, at 19:15 , Gary Chambers wrote:
Well, a contemporary look will always drive the computer harder...
Don't really find it a problem here though. Main PC is a
2.8MHzQuadCore, lappie is a 1.7MHz Centrino.
Guess you might benefit from faster hardware.
The SoftSqueak theme
I start using Pharo for my OO course (instead of Squeak used for
previous years).
I decided to switch to Pharo because it's cleaner (UI, code, ...).
Noury
On 29 janv. 09, at 18:23, Stéphane Ducasse wrote:
Btw if you use pharo please let us know because this is important for
us that we list
On 1/29/09 11:56 AM, Gary Chambers wrote:
Anything that anyone thinks could be improved?
Not sure if this is the type of feedback you're looking for but I'd like
to see some UI behavior changed/modernized:
1) Multiple selection support.
2) Generally, the context of where the mouse pointer is
On Fri, Jan 30, 2009 at 7:53 PM, Phil pbpubl...@gmail.com wrote:
On 1/29/09 11:56 AM, Gary Chambers wrote:
Anything that anyone thinks could be improved?
Not sure if this is the type of feedback you're looking for but I'd like
to see some UI behavior changed/modernized:
1) Multiple
1) Multiple selection support.
I would love to have this when generating accessor automatically. VERY often
I would like to only create accessors for some fields, not all. And
sometimes I want create just the setter or the getter, not both of them. So,
yes. I think this would be nice.
If
On Fri, Jan 30, 2009 at 8:16 PM, Lukas Renggli reng...@gmail.com wrote:
1) Multiple selection support.
I would love to have this when generating accessor automatically. VERY
often
I would like to only create accessors for some fields, not all. And
sometimes I want create just the
Hi Gary,
Thanks for Polymorph, it does a very good job when showing Squeak/Pharo
to Smalltalk-advert people...
A thing that i find clumsy with watery is the taskbar. There is no way
to distinguish Browsers/workspace/other windows. The original Squeak
uses different colors for that. Maybe
On Fri, Jan 30, 2009 at 9:26 PM, Adrian Lienhard a...@netstyle.ch wrote:
On my machine I get:
Squeak 3.9: 3800ms
Pharo #084: 2950ms
Pharo #213: 5200ms
#084 is before Polymorph was added and #213 is the most recent version.
BTW, with OB: 8590ms.
ouch...
any obvious hotspots?
Michael
2009/1/31 Michael Rueger m.rue...@acm.org:
On Fri, Jan 30, 2009 at 9:26 PM, Adrian Lienhard a...@netstyle.ch wrote:
On my machine I get:
Squeak 3.9: 3800ms
Pharo #084: 2950ms
Pharo #213: 5200ms
#084 is before Polymorph was added and #213 is the most recent version.
BTW, with OB:
45 matches
Mail list logo
