To me, default and current suggest these are not singleton, and I
wouldn't be surprised to see a specific, previous and next instances.
Nicolas
2012/5/14 Sean P. DeNigris s...@clipperadams.com:
I've noticed we use a buffet of accessors for singletons, like #default,
#instance, #current... it'd
Thanks for the pointer :)
I'm wondering though how that can work in a multi dialects ecosystem. At
the moment, a given version can have different dependency depending on
your smalltalk dialect/version. Isn't that another dimension of the problem?
On 13/05/12 19:45, Sean P. DeNigris wrote:
Do
On May 14, 2012, at 12:49 AM, Igor Stasenko wrote:
On 14 May 2012 00:03, Lawson English lengli...@cox.net wrote:
[pharo-project list added back in]
On 5/13/12 1:34 PM, Nicolas Cellier wrote:
[10 primeSwingFactorial] timeToRun 3411 [10 factorial] timeToRun
61219 So gmp is still
20073
-
Issue 5887: Less Sensor hardcoded
http://code.google.com/p/pharo/issues/detail?id=5887
Issue 5839: TestRunner Run Coverage fails.
http://code.google.com/p/pharo/issues/detail?id=5839
Issue 5876:
On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris s...@clipperadams.comwrote:
I've noticed we use a buffet of accessors for singletons, like #default,
#instance, #current... it'd be nice to just pick one. I like #instance, but
could live with any as long as I never have to guess which one from
Hi,
the Pharo Kernel job working again. This two issues are related:
http://code.google.com/p/pharo/issues/detail?id=5890thanks=5890ts=1336981613
http://code.google.com/p/pharo/issues/detail?id=5889thanks=5889ts=1336981445
Cheers,
-- Pavel
On Mon, May 14, 2012 at 9:42 AM, Mariano Martinez Peck
marianop...@gmail.com wrote:
On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris
s...@clipperadams.comwrote:
I've noticed we use a buffet of accessors for singletons, like #default,
#instance, #current... it'd be nice to just pick one.
On 05/14/2012 04:45 AM, Sean P. DeNigris wrote:
Do you guys know about this?
Yes, Eclipse uses it, successfully, for a decade.
This seems like it could fit really well with
Metacello...
I don't think you'd be happy with the consequences. First you'd have to
define what is API which is hard
Hi,
On Mon, May 14, 2012 at 6:18 AM, Sean P. DeNigris s...@clipperadams.comwrote:
A few updates...
* StringdisplayProgressAt:from:to:during: has deprecated in the
comment,
but is not in a deprecated category. The timestamp is 9/7/11 which puts it
either 1.2 or early 1.3, but either way, it
Paul,
On 12 May 2012, at 23:59, Sven Van Caekenberghe wrote:
I'll have a look later on (I have little time this weekend).
We also need at least one simple test (another one of Marcus' quotes; if
there is no actively run test, it does not exist). We just need an extra
version of
Historically, #soleInstance can be found in st80 I think.
Nicolas
2012/5/14 Esteban Lorenzano esteba...@gmail.com:
On Mon, May 14, 2012 at 9:42 AM, Mariano Martinez Peck
marianop...@gmail.com wrote:
On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris s...@clipperadams.com
wrote:
I've
For personal/work projects, I also use #uniqueInstance. It's true that if
#current is used for singleton instances it could be ambiguous.
On Mon, May 14, 2012 at 7:12 AM, Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com wrote:
Historically, #soleInstance can be found in st80 I think.
In Nautilus there is a combo box spanning and underneath the protocol
and method panes which I shall presume to call the 'history pulldown'
where items are display like:MyObject - myMethod: (1)
The usual convention in most documentation seems to be: MyObject
myMethod: (2)
Now it
well the previous implementation was so horrible I didn't really feel
to fix too much. besides, drag and drop works pretty nicely, so I personally
don't see why using a shitty file browser in pharo when I can do the same thing
100 times faster in my OS :/
but I think we will reimplement it from
You are right.
It was because it used to be package-class-protocol-method
Fix in Nautilus-BenjaminVanRyseghem.277 in PharoInbox
Ben
On May 14, 2012, at 2:40 PM, Ben Coman wrote:
In Nautilus there is a combo box spanning and underneath the protocol and
method panes which I shall presume to
Sean P. DeNigris wrote
* StringdisplayProgressAt:from:to:during: has deprecated in the
comment, but is not in a deprecated category. The timestamp is 9/7/11
which puts it either 1.2 or early 1.3, but either way, it should be
removed for 2.0, right? There is only one sender in the image,
We will have to reimplement it using Spec so :)
Ben
On May 14, 2012, at 3:02 PM, Camillo Bruni wrote:
well the previous implementation was so horrible I didn't really feel
to fix too much. besides, drag and drop works pretty nicely, so I personally
don't see why using a shitty file browser
Sean P. DeNigris wrote
Issue 5874: [ENH]: Notify progress with Announcements instead of
Exceptions
Why do we measure progress #from: a value? Has anyone ever put a value other
than 0 here?
--
View this message in context:
Hi,
I have this issue:
Dictionary with: #one-'ONE' with: #two-'TWO' This gives me a correct
Dictionary with keys #one, #two and values 'ONE', 'TWO'
Dictionary withAll: {#one-1 with: #two-2} This gives me a Dictionary
with keys 1,1 and values #one-'ONE', #two-'TWO'
So... I think one of both is
Mariano Martinez Peck wrote
Indeed. For me it depends in the case.
Fair enough, but let's have a protocol. For example, UIManager default...
From Mac dictionary:
default: a preselected option... when no alternative is specified by the
user
Is that really what we mean? I don't think so. It
On Mon, May 14, 2012 at 3:43 PM, Sean P. DeNigris s...@clipperadams.comwrote:
Mariano Martinez Peck wrote
Indeed. For me it depends in the case.
Fair enough, but let's have a protocol. For example, UIManager default...
From Mac dictionary:
default: a preselected option... when no
On Mon, May 14, 2012 at 3:42 PM, Esteban Lorenzano esteba...@gmail.com wrote:
Dictionary withAll: {#one-1 with: #two-2}
your #with: is suspicious :-)
--
Damien Cassou
http://damiencassou.seasidehosting.st
Lambdas are relegated to relative obscurity until Java makes them
popular by not having
maybe :)
I use #with: a lot, but I agree that one of the two approaches is wrong...
it should be a coherent API.
Esteban
On Mon, May 14, 2012 at 3:54 PM, Damien Cassou damien.cas...@gmail.comwrote:
On Mon, May 14, 2012 at 3:42 PM, Esteban Lorenzano esteba...@gmail.com
wrote:
Dictionary
On 14 May 2012, at 15:54, Damien Cassou wrote:
On Mon, May 14, 2012 at 3:42 PM, Esteban Lorenzano esteba...@gmail.com
wrote:
Dictionary withAll: {#one-1 with: #two-2}
your #with: is suspicious :-)
--
Damien Cassou
http://damiencassou.seasidehosting.st
Lambdas are relegated to
maybe we should even start considering again replacing dict + set with
something more
standard that internally relies on buckets instead of associations.
I've shown in my master thesis that the bucket implementation performs slightly
better
or the at least the same in various use-cases.
On
oops... yep, my mistake. You see, we should use copypaste ;)
but Sven is right :P
On Mon, May 14, 2012 at 4:08 PM, Sven Van Caekenberghe s...@beta9.bewrote:
On 14 May 2012, at 15:54, Damien Cassou wrote:
On Mon, May 14, 2012 at 3:42 PM, Esteban Lorenzano esteba...@gmail.com
wrote:
grrr. we shouldn't :)
On Mon, May 14, 2012 at 4:11 PM, Esteban Lorenzano esteba...@gmail.comwrote:
oops... yep, my mistake. You see, we should use copypaste ;)
but Sven is right :P
On Mon, May 14, 2012 at 4:08 PM, Sven Van Caekenberghe s...@beta9.bewrote:
On 14 May 2012, at 15:54,
On 14 May 2012, at 16:10, Camillo Bruni wrote:
maybe we should even start considering again replacing dict + set with
something more
standard that internally relies on buckets instead of associations.
I've shown in my master thesis that the bucket implementation performs
slightly
On 2012-05-14, at 16:22, Sven Van Caekenberghe wrote:
On 14 May 2012, at 16:10, Camillo Bruni wrote:
maybe we should even start considering again replacing dict + set with
something more
standard that internally relies on buckets instead of associations.
I've shown in my master
Holy crap, SystemProgressMorph's instance creation method doesn't return an
instance at all but a block. I really wish I understood this design decision
before I try to cut all this out. Yikes, check out
SystemProgressMorphlabel:min:max:
label: shortDescription min: startMinValue max:
fstephany wrote
I'm wondering though how that can work in a multi dialects ecosystem
Hmm... good point. I'm thinking this is handled by Metacello already. IOW,
my project's Metacello version 1.3 means these are the packages you load
for 1.3 in all supported platforms, e.g. Pharo 1.3, Squeak
I know :D nice no? :D
Specific class please!!
It's specially nice when you want to inspect it and figure out on how to use it
:/
On 2012-05-14, at 16:56, Sean P. DeNigris wrote:
Holy crap, SystemProgressMorph's instance creation method doesn't return an
instance at all but a block. I
Philippe Marschall-2 wrote
I don't think you'd be happy with the consequences. First you'd have to
define what is API which is hard because everything is public in
Smalltalk
Right, first you'd have to specify public packages/categories or individual
classes (which would be helpful with of
So if I fix
a bug, and now Pharo 1.3 will have to load package.pharo13.3 and Squeak
package.squeak43.5, I would declare 1.3.1 in my config with the new
packages. Does that sound right?
Yep, sounds right.
What if you only need the bug fix in the Pharo version and not the
Squeak one? The
Sean P. DeNigris wrote
[:barValArg | | barVal return newBarSize |
barVal := barValArg.
return := nil.
...
new fun stuff here
barVal == #current ifTrue: [ return := barSize ].
barVal == #label
fstephany wrote
What if you only need the bug fix in the Pharo version and not the
Squeak one? The package becomes 1.3.1 in Squeak but is identical to
1.3.0. No big deal I guess...
Well, we're versioning the *project* i.e. the config, not the package, so I
don't think there's a conflict.
Francois,
Regarding the mutability of Metacello configurations ... you are right that it
is tempting, but one should never modify a version that has been marked as
#released ... it is a convention.
One of the appeals of git/github is that a git commit is immutable so all of
the artifacts in a
- Original Message -
| From: Francois Stephany tulipe.mouta...@gmail.com
| To: pharo-project@lists.gforge.inria.fr
| Sent: Monday, May 14, 2012 9:02:25 AM
| Subject: Re: [Pharo-project] Semantic Versioning
|
| A release should maybe be a complete new entity (and not editable)
| hosted
- Original Message -
| From: Sean P. DeNigris s...@clipperadams.com
| To: pharo-project@lists.gforge.inria.fr
| Sent: Monday, May 14, 2012 8:11:19 AM
| Subject: Re: [Pharo-project] Semantic Versioning
|
|
| Right, first you'd have to specify public packages/categories or
| individual
|
On 05/14/2012 05:11 PM, Sean P. DeNigris wrote:
Philippe Marschall-2 wrote
I don't think you'd be happy with the consequences. First you'd have to
define what is API which is hard because everything is public in
Smalltalk
Right, first you'd have to specify public packages/categories or
Hi Steph,
I'll let you know.
CAS seems to be kind of standard for high organization SSO. It's just sad I
didn't thought of it for Google Summer of Code. This could have been an
opportunity.
There's also ESUG. But maybe others should say of they find such an
implementation useful (and not
Bonjour Cédrick, Stépahane,
On 14 May 2012, at 19:44, Cédrick Béler wrote:
I'll let you know.
CAS seems to be kind of standard for high organization SSO. It's just sad I
didn't thought of it for Google Summer of Code. This could have been an
opportunity.
There's also ESUG. But maybe
EstebanLM wrote
our new release process...
two bug fix releases at month 4 and month 8...
During this year we'll also release bugfix versions of Pharo 1.4.
This is exciting because as soon as a version is released, everyone starts
pounding on it and inevitably finding bugs. It will be
Hi guys,
Just FYI, me and Cloudfork guys are just finishing the OpenID 2.0/OAuth
2.0 support for Iliad and Aida, based on Cloudfork SSO [1]. On Pharo and
VW. On Pharo Zync with Zodiak SSL is used. Current goal is to develop a
Google Docs API support.
Let me also thanks in this ocasion to the
That is excellent news.
I will check it out after the Pharo conference for sure.
Thanks for the pointer, Janko.
On 14 May 2012, at 21:07, Janko Mivšek wrote:
Hi guys,
Just FYI, me and Cloudfork guys are just finishing the OpenID 2.0/OAuth
2.0 support for Iliad and Aida, based on Cloudfork
Hi guys. So far, when we export/import packages with Fuel, we have our own
FLPackage that we serialize/materialize. We get that info from a
PackageInfo. Now, my question is, say I have materialized a package, how
can I do (by code) to create and register in the system a normal package
from our
In the end there is no replacement for discipline...
;)
I'm wondering when Fuel and its package loader will be ready, can we
imagine a read-only repo of packages? I'm still wrapping my head around
packaging and thinking aloud right now.
Is there a place where I can read more about how
Hi guys. When importing a package with fuel, I am sending
SystemChangeNotifier uniqueInstance classAdded: aBehavior inCategory:
category asSymbol.
for EACH class ... that is really slow.
so...as part of GSoC we will try to improve this. I would like to do bulk
events, that is, one even that
Francois,
No documentation for how Metacello works under the covers, but I would be
willing to help with your exploration --- your questions and my answers might
become the documentation ... There are several layers:
- metacello configuration specification language
- metacello
Regarding Fuel package loader ... Metacello was intended to extensible from
the very beginning, so it should be possible to incorporate Fuel and it's
package loader into the mix ... the complexity of the project will really
depend upon how versions of the packages are managed ...
Dale
-
On May 14, 2012, at 9:07 PM, Janko Mivšek wrote:
Hi guys,
Just FYI, me and Cloudfork guys are just finishing the OpenID 2.0/OAuth
2.0 support for Iliad and Aida, based on Cloudfork SSO [1]. On Pharo and
VW. On Pharo Zync with Zodiak SSL is used. Current goal is to develop a
Google Docs
On May 14, 2012, at 10:28 PM, Mariano Martinez Peck wrote:
Hi guys. So far, when we export/import packages with Fuel, we have our own
FLPackage that we serialize/materialize. We get that info from a PackageInfo.
Now, my question is, say I have materialized a package, how can I do (by
On 14/05/2012 17:51, Dale Henrichs wrote:
One of the appeals of git/github is that a git commit is immutable so all of
the artifacts in a commit are guaranteed.
Are you sure? It was my understanding that you *can* alter a git commit.
Not advisable, but possible.
I think you are referring to the the fact that there are ways to go through
commits and remove sensitive data from them, however, unless I'm mistaken, the
SHA of the commit gets changed when you modify it, so you may have modified a
commit but you have done so by copying it to a new identity.
I am trying to implement an asString method for gmp floats but I don't
quite see how.
Prototype for getting a string is:
Function: char * mpf_get_str (char *str, mp_exp_t *expptr, int base,
size_t n_digits, mpf_t op)
where mp_exp_t *expptr is just a pointer to a long, and size_t is just
Hello all,
I have recently developed a new logging library called Nagare.
http://code.google.com/p/nagare-logger/
Nagare is designed to be simple and scalable.
Contrary to other logging frameworks which provide rich set of log
output methods (file, socket, DB, etc.), Nagare just connects to
it was a time, when were able to track all activities around squeak,
pharo and vm..
today the amount of updates, news and activities is just overwhelming..
a rusty locomotive, which once staying in backyard, repaired by Stef
and Marcus and now goes faster and faster :)
--
Best regards,
Igor
Sean P. DeNigris wrote
Holy crap, SystemProgressMorph...
As a first step, I cleaned out the system progress morph classes...
Issue 5897: [ENH]: Clean SystemProgressMorph and friends
Fix in inbox:
SLICE-Issue-5897-ENH-Clean-SystemProgressMorph-and-friends-SeanDeNigris.1
* create
I have a few questions about displaying progress...
1. What's the best way to do something like the following: I may be in the
UI thread. I want to process a loop in a background thread, but block my
current execution path, while still letting the world update. This is my use
case...
On 15 May 2012, at 04:43, Igor Stasenko wrote:
it was a time, when were able to track all activities around squeak,
pharo and vm..
today the amount of updates, news and activities is just overwhelming..
a rusty locomotive, which once staying in backyard, repaired by Stef
and Marcus and
A random thought: how about a stackexchange site for smalltalk? Most of the
things disussed on the list could probably go there and the list would once
again be a quiet place for core stuff only.
We (or I) would have to propose a new site and we would need people from Pharo
AND Squeak (and
61 matches
Mail list logo
