Re: [Pharo-users] STON on ScaledDecimal?
Oh, sorry, I forgot to write it. And Fraction as well. I have added it for my own use. Regards José 2014-05-31 6:13 GMT+02:00 Joachim Tuchel : > Hi, > > Sounds good. But I think the Scale should be streamed as well: 12345.678s3 > > Joachim > > José Comesaña schrieb: > > > Wouldn't it be good if STON could save ScaledDecimals as 12345.678s?. That > way, we could read them back again as ScaledDecimal, instead of Float. I > have tried and it seems quite useful. > > Regards >
[Pharo-users] Bug in Nautilus... (Pharo 3)
If I try to "move to another package" a class I always get an exception. Try moving any class present in the standard Pharo 3 to AST-Core, for example... Anyway, thanks for the great work you are doing. Regards José
Re: [Pharo-users] STON on ScaledDecimal?
Hi José, On 31 May 2014, at 01:32, José Comesaña wrote: > Wouldn't it be good if STON could save ScaledDecimals as 12345.678s?. That > way, we could read them back again as ScaledDecimal, instead of Float. I have > tried and it seems quite useful. > > Regards That is an interesting idea and it is probably nice to have for those relying on ScaledDecimals. One of the ideas of STON is to be portable across dialects, so I am wondering if ScaledDecimals exists everywhere ? I am curious as to how you did it though, since STONReader basically contains its own number parser. Could you share your code ? Sven
Re: [Pharo-users] Mac keyboard bindings
Thanks Stephan. Unfortunately it looks like the problem is deeper. The Home/End (as well as Insert and others) key events don't actually make to the image from the VM. keyUp is received but not keyDown or keystroke. Still looking into why. -- View this message in context: http://forum.world.st/Mac-keyboard-bindings-tp4760656p4761128.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] Mac keyboard bindings
OK, I have fixed the problem with a patch to the Pharo VM. I cannot claim to
understand what is going on with the keyboard handling there but I see what
is missing.
Now, how should I go about submitting this patch for inclusion in the VM?
diff --git a/platforms/iOS/vm/OSX/sqSqueakOSXCGView.m
b/platforms/iOS/vm/OSX/sqSqueakOSXCGView.m
index e63794e..0a1f9fe 100644
--- a/platforms/iOS/vm/OSX/sqSqueakOSXCGView.m
+++ b/platforms/iOS/vm/OSX/sqSqueakOSXCGView.m
@@ -449,6 +449,11 @@
lastSeenKeyBoardModifierDetails,dragInProgress,dragCount,dragItems,windowLogic,s
else encode( 27, 53,cancel:)
else encode( 27, 53,complete:)
else encode( 27, 71,delete:)
+
+else encode( 1, 115, moveToBeginningOfLine:)
+else encode( 1, 115, moveToBeginningOfLineAndModifySelection:)
+else encode( 4, 119, moveToEndOfLine:)
+else encode( 4, 119, moveToEndOfLineAndModifySelection:)
else return;
@synchronized(self) {
--
View this message in context:
http://forum.world.st/Mac-keyboard-bindings-tp4760656p4761133.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
[Pharo-users] PIllar >> #visitAnnotatedParagraph:
PRMarkdownWriter >>visitAnnotatedParagraph: says "Pier seems to lack consistency here ...". Indeed, for #visitAnnotatedParagraph: we currently have: * PRPillarWriter outputs all annotations unchanged * PRMarkdownWriter * prepends the the annotationLabel to the annotationText * has special handling for @@todo by calling #visitCommentedLine: * indicates it does some kind of nesting in a custom way; but I can't work out the semantics; and it interrupts nested list numbering similar to what I reported for comments. * PRVisitor * throws away the annotationLabel by just calling #visitParagraph * knows nothing about @@todo * knows nothing about nesting * PRHTMLWriter has no definition inheriting from PRVisitor * PRLaTeXWriter has no definition inheriting from PRVisitor * PRTextWriter has no definition inheriting from PRVisitor To bring some consistency I propose to... 1. Prepend annotationLabel for all the xxWriters 2. Change PRMarkdownWriter to use the code I implemented for nested comments. Have all xxWriters use this also. 3. Drop the @@todo from PRMarkdownWriter, since if you want ToDos to be hidden like a comment, you should just use a comment, e.g." %todo ..." . However this change would alter the semantics of existing users of Pier. So what is the process for such changes? Announce here and wait some period? For consideration, there are currently no tests for annotated paragraphs, so this could be considered outside the existing API ;) - and so I'll add tests, which will be simpler without @@todo. cheers -ben
