yeah the dumps are really strange..
seems like most of the times crashing at this point:
0xffc05bd8 M ZnChunkedReadStream>next -613198972: a(n) ZnChunkedReadStream
0xffc05bfc M ZnUTF8Encoder>nextFromStream: -613185216: a(n) ZnUTF8Encoder
0xffc05c30 M [] in ZnStringEntity>readUpToEndFrom: -61318640
20390
-
Issue 6912: #fancyText:font:color: has no senders, and is in strange place
(AlignmentMorph)
http://code.google.com/p/pharo/issues/detail?id=6912
Issue 6883: Type Class refactoring
http://code.google.com/p/pharo/issues/detail?id=6883
Issue 6947
>
>> Hi,
>>
>> I completely agree that the PIer syntax is rather niche these days, but we
>> should not confuse the PIer syntax with the Pier model. I think that it
>> would be beneficial to capitalize on this model (and all the infrastructure
>> built on top of it) and simply create a Markdow
On Mon, Nov 12, 2012 at 9:51 PM, Sebastian Nozzi wrote:
> Now, having said this, let me tell you that *I* (me) am not always
> happy with the "recover lost changes" way of recovering my changes.
People are working on how to improve this situation, you are not alone :-).
> As I said, I think I sh
2012/11/12 Fernando Olivero :
> Sebastian, thanks for sharing your code and thoughts.
Hey, you're welcome.
> Maybe what Mariano was implying is that you already have the data for the
> backup in the changes, and having yet another mechanism for that adds
> complexity to the system.
As I said, I
On Nov 12, 2012, at 9:51 PM, Sebastian Nozzi wrote:
> Now, having said this, let me tell you that *I* (me) am not always
> happy with the "recover lost changes" way of recovering my changes.
Me too.
Stef
On Nov 12, 2012, at 9:32 PM, Sebastian Sastre wrote:
> sure Stef.
>
>> Did you try with the VM with the new semaphores?
> not sure. The method below answers this question?
>
>> and without the new semaphores handling?
> again, now sure.
>
>> In the two cases the primitives used looks differen
yeah but future does not means "right in the corner", just a bit more time :)
On Nov 12, 2012, at 9:57 PM, Sebastian Nozzi wrote:
> UI builder? Cool, this is getting better and better... :-)
>
> 2012/11/12 Stéphane Ducasse :
>> Yes.
>> So for now you simply used plain polymorph.
>> In the futur
Since you mention it, yes. I think (but not 100% sure) that I had the
case that I chose all the relevant changes to recover, but still I got
the error message about a class not existing. The class creation event
was not there (in the changes). It might have been an obscure case,
maybe I deleted the
+1
On Nov 12, 2012, at 9:57 PM, Tudor Girba wrote:
> Hi,
>
> I completely agree that the PIer syntax is rather niche these days, but we
> should not confuse the PIer syntax with the Pier model. I think that it would
> be beneficial to capitalize on this model (and all the infrastructure built
UI builder? Cool, this is getting better and better... :-)
2012/11/12 Stéphane Ducasse :
> Yes.
> So for now you simply used plain polymorph.
> In the future we will have a UI builder.
>
>
> Stef
Hi,
I completely agree that the PIer syntax is rather niche these days, but we
should not confuse the PIer syntax with the Pier model. I think that it would
be beneficial to capitalize on this model (and all the infrastructure built on
top of it) and simply create a Markdown support.
Cheers,
D
2012/11/12 Damien Cassou :
> it's a backup! You probably never need any backup... until you do :-).
Exactly! ;-)
> In a perfect world Pharo would be perfect, never crash and never loose
> any data.
To be fair, I have not had a VM crash in quite some time. What I do
manage to archieve is to make
On Mon, Nov 12, 2012 at 8:53 PM, Damien Cassou wrote:
> On Mon, Nov 12, 2012 at 8:42 PM, Mariano Martinez Peck
> wrote:
> > So...my question is, what is the actual problem/limitations with those
> which
> > are "solved" with this new tool?? or in other words, why do we need this
> new
> > tool? s
sure Stef.
> Did you try with the VM with the new semaphores?
not sure. The method below answers this question?
> and without the new semaphores handling?
again, now sure.
> In the two cases the primitives used looks different.
What should I look?
> Could you also provide a size of the image?
On Nov 12, 2012, at 9:19 PM, Sebastian Nozzi wrote:
> It seems that I *was* using Spec after all :-) Only I didn't know it...
> At least I think so, since I defined the UI programmatically...
>
> I used information from here:
>
> http://book.pharo-project.org/book/LanguageAndLibraries/GUI/Polym
thanks
Now do you have a case where the categories get lost (because they should be
saved in the change file)
And we may broke something.
Which version are you using?
Stef
On Nov 12, 2012, at 8:06 PM, Sebastian Nozzi wrote:
> Dear Pharo Community,
>
> I would like to share with you the work o
thanks a lot for sharing that with us.
Did you try with the VM with the new semaphores? and without the new semaphores
handling?
In the two cases the primitives used looks different.
Could you also provide a size of the image?
If the crash reproducible?
Stef
On Nov 12, 2012, at 8:12 PM, Sebastian
It seems that I *was* using Spec after all :-) Only I didn't know it...
At least I think so, since I defined the UI programmatically...
I used information from here:
http://book.pharo-project.org/book/LanguageAndLibraries/GUI/PolymorphTutorial/Layout/
and here:
http://www.pharocasts.com/2011/02
I thought it should work :(
> I was playing with the following:
>
> http://en.wikipedia.org/wiki/Chess_symbols_in_Unicode
>
> '/tmp/chess.txt' asFileReference writeStreamDo: [ :stream |
> (16r2654 to: 16r265F)
> do: [ :each |
> stream nextPut: each as
Sebastian, thanks for sharing your code and thoughts.
Maybe what Mariano was implying is that you already have the data for the
backup in the changes, and having yet another mechanism for that adds
complexity to the system.
I think is a good idea, but too focused on the categories you choose up
f
hey sounds nice :)
does it save version after version right? (like not overwriting the same files)?
sebastian
o/
On Nov 12, 2012, at 5:15 PM, Sebastian Nozzi wrote:
> Sorry, forgot the screenshots...
>
>
> 2012/11/12 Sebastian Nozzi :
>> Dear Pharo Community,
>>
>> I would like to share
Sorry, forgot the screenshots...
2012/11/12 Sebastian Nozzi :
> Dear Pharo Community,
>
> I would like to share with you the work of my past weekend, and
> announce "CategorySaver".
>
> It is a simple utility to periodically save (file-out) a list of
> categories given (wildcards accepted).
>
> Y
Thanks Igor. I will have to explore this option when I get time. It
seems a lot to learn.
I have downloaded the videos and slides. I also downloaded Bruce
Eckel's "Thinking in C++" books.
And also thanks Stéphane for the reference the Greenberg pdf.
Jimmie
On 11/10/2012 5:35 PM, Igor Sta
On 12 Nov 2012, at 14:54, Emilia wrote:
> Hello! I'm porting code from Cincom Smalltalk to Pharo. It's a web
> application so I've got several WAComponent instances and one component which
> inherits from WAFileLibrary that renders images.
> In the original code ( the one that runned in VW) i
On 12.11.2012 14:54, Emilia wrote:
Hello! I'm porting code from Cincom Smalltalk to Pharo. It's a web
application so I've got several WAComponent instances and one
component which inherits from WAFileLibrary that renders images.
In the original code ( the one that runned in VW) i had the followi
>It's a web application so I've got several WAComponent instances
The #asPackagedString: is VW specific and not available
in Pharo. In Seaside on Pharo the resources like pictures
are stored in methods returning a ByteArray
with the bytes only.
There is an easy way: just save the original re
I was playing with the following:
http://en.wikipedia.org/wiki/Chess_symbols_in_Unicode
'/tmp/chess.txt' asFileReference writeStreamDo: [ :stream |
(16r2654 to: 16r265F)
do: [ :each |
stream nextPut: each asCharacter ]
separatedBy:
On 2012-11-12, at 15:56, Stéphane Ducasse wrote:
> You won I put a filter markdown to thrash on my mail sadly.
?? I do not parse
> On Nov 12, 2012, at 3:11 PM, Camillo Bruni wrote:
>
It depends at which level.
Can you tag on word in markdown to have bold, italic, index?
>>
>> stef,
You won I put a filter markdown to thrash on my mail sadly.
On Nov 12, 2012, at 3:11 PM, Camillo Bruni wrote:
>>> It depends at which level.
>>> Can you tag on word in markdown to have bold, italic, index?
>
> stef, I already explained you that at least 4 times! Plus I gave you the
> solutions
>> It depends at which level.
>> Can you tag on word in markdown to have bold, italic, index?
stef, I already explained you that at least 4 times! Plus I gave you the
solutions,
the only thing I don't have is the time to complete the Markdown parser!
>> If I would not have written 350 pages of s
On 11 Nov 2012, at 17:26, Stéphane Ducasse wrote:
> On Nov 10, 2012, at 9:41 PM, Sven Van Caekenberghe wrote:
>
>> On 10 Nov 2012, at 21:33, Stéphane Ducasse wrote:
>>
3. Lets discuss how we want to describe the content "in-image"
for "serving on the web". Maybe with a "Markup to HT
On Nov 12, 2012, at 9:45 AM, Pavel Krivanek wrote:
> Hi,
>
> in the condenseChanges method the message moveChangesTo: is heavily
> called. And this method exports changes for all selectors of the
> behavior. But I suppose that we want to process only local selectors
> here. Can some traits guy
Sven Van Caekenberghe-2 wrote
>> I want to use the pier syntax because I know that I can generate the
>> correct latex
>> with it for the books, and of course any kind of html and other formats.
>
> I vote for Markdown, it is more like a defacto standard.
> And you can convert Markdown into anyth
Just as a side note, there is no "password recovery" feature for those with
bad memory like me. :D
Thank you!
--
View this message in context:
http://forum.world.st/New-MongoTalk-Repo-tp4654808p4654828.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Hi,
in the condenseChanges method the message moveChangesTo: is heavily
called. And this method exports changes for all selectors of the
behavior. But I suppose that we want to process only local selectors
here. Can some traits guy confirm that we should replace call of the
message #selectors with
Francois Stephany writes:
> I've moved the MongoTalk project to SmalltalkHub:
>
> http://www.smalltalkhub.com/#!/~francois/MongoTalk/
>
>
> The original repo is still available but please use the new one.
>
> I don't know how to put a repo in global read/write on Smalltalkhub (is
> it possible?
I've measured a few variations, with and without preallocation:
(using new:streamContents:)
your version: 207 ms 584 ms
using a WordArray as destination: 1160 ms 2524 ms
using a WordArray as both source and destination: 157 ms 522ms
Stephan
38 matches
Mail list logo