On 06 Nov 2013, at 08:53, Max Leske wrote:
>
> On 06.11.2013, at 08:05, Marcus Denker wrote:
>
>>
>> On 05 Nov 2013, at 20:37, Mariano Martinez Peck
>> wrote:
>>
>>> Hi. From what I understand you removed the old Compiler but yet Opal does
>>> not support compiling. Also, #sourceCode was
Thanks Marcus. I’ll open a bug report.
On 06.11.2013, at 08:14, Marcus Denker wrote:
>
> On 05 Nov 2013, at 19:48, Max Leske wrote:
>
>> I discovered that AdditionalMethodState now (sometimes) stores Associations,
>> not only Pragmas and Messages. That seems to work fine so fare but leads to
On 06.11.2013, at 08:05, Marcus Denker wrote:
>
> On 05 Nov 2013, at 20:37, Mariano Martinez Peck wrote:
>
>> Hi. From what I understand you removed the old Compiler but yet Opal does
>> not support compiling. Also, #sourceCode was changed etc...
>> That means that there is no way to see the
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 1c0119dc95105dd331ce47309c7422ebaff20562
https://github.com/pharo-project/pharo-core/commit/1c0119dc95105dd331ce47309c7422ebaff20562
Author: Jenkins Build Server
Date: 2013-11-05 (Tue, 05 Nov 2013
Branch: refs/tags/30548
Home: https://github.com/pharo-project/pharo-core
On 05 Nov 2013, at 19:48, Max Leske wrote:
> I discovered that AdditionalMethodState now (sometimes) stores Associations,
> not only Pragmas and Messages. That seems to work fine so fare but leads to
> an exception if #analogousCodeTo: is sent to a state which stores an
> Association.
>
I th
On 05 Nov 2013, at 20:37, Mariano Martinez Peck wrote:
> Hi. From what I understand you removed the old Compiler but yet Opal does not
> support compiling. Also, #sourceCode was changed etc...
> That means that there is no way to see the decompiled string of a method?
Yes.
> Which means I ca
Hi,
PPExpressionParser is not meant to be subclassed. Read the class comment to
see how to use it.
PPCompositeParser is meant to be subclassed and it offers a neat mapping
between methods and variables to support caching of parsers. Take a look at
the subclasses in the Moose image:
http://www.moo
On 04/11/2013 9:42 AM, p...@highoctane.be wrote:
- make use of SandstoneDb + Fuel storage
Interesting. Can you share your reasons for choosing these technologies?
Why not GemStone? MongoDB? Or, are you still experimenting?
Yes, no compiling during holidays! We don't want you burning out. In fact the
no work of any kind... unless it's releasing Mars ;) but still better after
holiday...
Will you let me know after you've successfully compiled with latest Xcode so I
can upgrade. Thanks.
-
Cheers,
Sean
--
View
For whomever wonders what "what have the romans ever done for us" is about
watch:
http://www.youtube.com/watch?v=9foi342LXQE
you can stop around 2:10
--
View this message in context:
http://forum.world.st/Feature-request-poll-tp4718993p4719475.html
Sent from the Pharo Smalltalk Developers ma
On Tue, Nov 5, 2013 at 10:01 AM, GOUBIER Thierry wrote:
> I find this debate interesting... but a bit strange
>
> For me, Smalltalk-80 is what is inside the 80's book, and no
> implementation of Smalltalk was really Smalltalk-80 but something else
> (some principles plus a huge amount of code)...
,Ohhh
I guess I'll restart work on that old 1.3-based project of mine :-)
Well, well,this opens a lot of doors! (including doc comments with links
inside them for clickable cross refs, like we had in squeak)
Now, it is going to be used with Tx stuff ?
Phil
After reading the PetitParser chapter, I'm not clear when one would subclass
PPCompositeParser vs. using PPExpressionParser. What are the tradeoffs / use
cases? Also, can the book be improved or is that the final version? Thanks.
-
Cheers,
Sean
--
View this message in context:
http://forum.
philippeback wrote
> doing:
>
> ((Text withAll: 'foo') , (Text string: 'some link' attribute: (TextURL new
> url:'http://philippeback.eu')) , (Text withAll: 'bar')) asMorph
> openInWorld.
>
> gives me a nice purple 'some link' bit but clicking on it fails with
>
> MessageNotUnderstood: TextURL>>
I’ve temporarily disabled the Fuel builds. Martin and I discovered VM crashes
related to (maybe) garbage collection during our test runs. So right now a lot
of builds are crashing. We’ll keep investigating so as to reenable the builds.
Max
Hi. From what I understand you removed the old Compiler but yet Opal does
not support compiling. Also, #sourceCode was changed etc...
That means that there is no way to see the decompiled string of a method?
Which means I cannot deploy and image without sources and then
browse/debug/inspect/write p
Goubier Thierry wrote
> for me, Pharo will stay Pharo Smalltalk
That's valid, and just what I was speaking to. For us Smalltalkers, the tiny
sliver of people who understand the subtleties, Pharo (in its current form,
who knows in a year!) is quite reasonably described as Smalltalk - an
evolution o
I discovered that AdditionalMethodState now (sometimes) stores Associations,
not only Pragmas and Messages. That seems to work fine so fare but leads to an
exception if #analogousCodeTo: is sent to a state which stores an Association.
Can someone please confirm that this is a bug?
Cheers,
Max
I find this debate interesting... but a bit strange
For me, Smalltalk-80 is what is inside the 80's book, and no implementation of
Smalltalk was really Smalltalk-80 but something else (some principles plus a
huge amount of code)... Pharo is no more different from Smalltalk-80 than all
the other
Tudor Girba-2 wrote
> Pharo is Pharo. And we should promote it like that.
It is inherently confusing because originally "Smalltalk" meant "a
language/environment that's continually reinvented every 4 years based on
the knowledge gained by the last iteration". Then, Smalltalk-80 was frozen
and rele
Ok, thanks guy!
Alexandre
On Nov 5, 2013, at 11:21 AM, Yuriy Tymchuk wrote:
> REVEAL team is experiencing this too.
>
> On 05 Nov 2013, at 15:13, Alexandre Bergel wrote:
>
>> Hi!
>>
>> Apparently I cannot add any new team member in the team of ObjectProfile.
>> Am I the only one to experi
REVEAL team is experiencing this too.
On 05 Nov 2013, at 15:13, Alexandre Bergel wrote:
> Hi!
>
> Apparently I cannot add any new team member in the team of ObjectProfile.
> Am I the only one to experience this? When I click on add, the member is not
> added. I've tried refreshing...
>
> Che
nope, that's a know bug which will be take care of.
as for now, you can only add new contributors to repositories.
On 2013-11-05, at 15:13, Alexandre Bergel wrote:
> Hi!
>
> Apparently I cannot add any new team member in the team of ObjectProfile.
> Am I the only one to experience this? When I
Hi!Apparently I cannot add any new team member in the team of ObjectProfile. Am I the only one to experience this? When I click on add, the member is not added. I've tried refreshing...Cheers,Alexandre-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:Alexandre Bergel http://www.bergel.eu^~:;._,.
On Tue, Nov 5, 2013 at 2:36 PM, Camillo Bruni wrote:
> I added you to the PharoInbox, could you commit again?
>
Thanx and done.
>
> On 2013-11-05, at 11:54, Usman Bhatti wrote:
>
> > Here is a slice the corrects the bug.
> > I cannot commit to pharo inbox.
> >
> > Usman
> >
> >
> > On Tue, Nov
I added you to the PharoInbox, could you commit again?
On 2013-11-05, at 11:54, Usman Bhatti wrote:
> Here is a slice the corrects the bug.
> I cannot commit to pharo inbox.
>
> Usman
>
>
> On Tue, Nov 5, 2013 at 11:49 AM, Usman Bhatti wrote:
> https://pharo.fogbugz.com/f/cases/12073/Writing
On 05 Nov 2013, at 14:13, Camillo Bruni wrote:
>
> On 2013-11-05, at 14:09, Benjamin
> wrote:
>
>> On 05 Nov 2013, at 13:51, Esteban Lorenzano wrote:
>>
>>> it shouldn't be an MC issue.
>>> the integrator is configured in "merge accepting upcoming changes".
>>> So if you integrate and acc
On 2013-11-05, at 14:09, Benjamin wrote:
> On 05 Nov 2013, at 13:51, Esteban Lorenzano wrote:
>
>> it shouldn't be an MC issue.
>> the integrator is configured in "merge accepting upcoming changes".
>> So if you integrate and accept without you picking the right version, when
>> the automat
On 05 Nov 2013, at 13:51, Esteban Lorenzano wrote:
> it shouldn't be an MC issue.
> the integrator is configured in "merge accepting upcoming changes".
> So if you integrate and accept without you picking the right version, when
> the automatic process run it blindly overrides the previous cha
and btw... the whole RPackage + Announcements stuff should not prevent an
MC code to be installed, just to be properly categorized, so I wouldn't
check in that direction either, in case of an error.
On Tue, Nov 5, 2013 at 9:51 AM, Esteban Lorenzano wrote:
> it shouldn't be an MC issue.
> the in
it shouldn't be an MC issue.
the integrator is configured in "merge accepting upcoming changes".
So if you integrate and accept without you picking the right version, when
the automatic process run it blindly overrides the previous change.
So I would call it "a human mistake", before an MC one.
u
I still didn't tried with the latest xcode, but I tried the immediate
previous and there is no problem at all.
I don't see why it shouldn't work with mavericks :)
I will do it as soon as I'm back from holidays (because if I do it now,
they wouldn't be holidays ;)
Esteban
On Tue, Nov 5, 2013 at
That was my impression too.
But the interaction with RPackage Annoucement etc.. makes it hard to
isolate.
I suspect these layers, because I use MC everyday in Squeak where it's much
more robust.
That means that tests are not currently sufficient and we should focus on
this (MC used to have a fairly
Damien Cassou
wrote:
> Hi,
>
> I've just made a .dmg file for installing Pharo on MacOSX. Please try it
> and report problems:
>
> https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/16/ar
> tifact/pharo-build/Pharo%203.0.0.dmg
>
> Best,
On Mavericks on a 2013 Mac Mini. I cop
Wow! That is really great and it works like with an other application.
Awesome!
Norbert
Am 05.11.2013 um 11:18 schrieb Damien Cassou :
> Hi,
>
> I've just made a .dmg file for installing Pharo on MacOSX. Please try
> it and report problems:
>
> https://ci.inria.fr/pharo-contribution/job/Pharo
https://pharo.fogbugz.com/f/cases/12073/Writing-jpeg-files-to-disk
On Tue, Nov 5, 2013 at 11:34 AM, Usman Bhatti wrote:
> Hello,
>
> Due to the changes in Pharo 3.0, I cannot write jpeg files on the disk.
> This happens because when writing a jpeg file, we delete any precedent
> version of the f
Hello,
Due to the changes in Pharo 3.0, I cannot write jpeg files on the disk.
This happens because when writing a jpeg file, we delete any precedent
version of the file to be exported. However, now DiskStore>>delete: throws
an exception when the file to be deleted is not present
delete: path
| p
Neither, I am using the existing Help Browser which I extend with my own
class called Prometheas. Currently it fixes only the refresh button problem
but in the future I will completely redesign it cause it is part of my
larger project Ephestos that will bring a new GUI API (using Athens) and I
will
Hi,
I've just made a .dmg file for installing Pharo on MacOSX. Please try
it and report problems:
https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/16/artifact/pharo-build/Pharo%203.0.0.dmg
Best,
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability
So there must be some serious MC issue.
On 2013-11-05, at 11:15, Benjamin wrote:
> Indeed, it seems to not be in the system.
>
> Most probably because afterward another spec related issue has been
> integrated,
> and that the diff were not properly detected.
> (Already happened)
>
> Ben
>
>
Indeed, it seems to not be in the system.
Most probably because afterward another spec related issue has been integrated,
and that the diff were not properly detected.
(Already happened)
Ben
On 04 Nov 2013, at 23:06, Benjamin wrote:
> I will tomorrow :)
>
> Ben
>
> On 04 Nov 2013, at 13:22,
How do you want to bring it ? With class comments, method with comment only
?
I guess it is not a problem as long as it does not take too much memory (I
mean as long as it is not a Mb).
2013/11/5 kilon alios
> Is this a problem ? I want to bring external documentation inside the
> Pharo image,
No permission at all. You just have to give credit to the authors, nothing more
nothing less
Cheers,
Alexandre
> On 5 Nov 2013, at 06:16, kilon alios wrote:
>
> Is this a problem ? I want to bring external documentation inside the Pharo
> image, and I was wondering if I need permission and s
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 4d50f3e44e78355b74d43f8c80b7286222ca7b74
https://github.com/pharo-project/pharo-core/commit/4d50f3e44e78355b74d43f8c80b7286222ca7b74
Author: Jenkins Build Server
Date: 2013-11-05 (Tue, 05 Nov 2013
Branch: refs/tags/30547
Home: https://github.com/pharo-project/pharo-core
Is this a problem ? I want to bring external documentation inside the Pharo
image, and I was wondering if I need permission and such. I will be editing
also some documentation to make it easier to read and more current. I am
already working on Nativeboost documentation.
On 05 Nov 2013, at 06:04, Tudor Girba wrote:
> Hi,
>
> I am glad you are considering other types of fonts :). Still, I think that
> Open Sans does not work well with Source Code. First, there is not enough
> distinction between them, and second, their rhythms do not match (both in
> terms of
48 matches
Mail list logo
