- Pharo-users - lists.pharo.org

PIllar >> #visitAnnotatedParagraph:

by Ben Coman

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

June 1, 2014

Re: [Pharo-users] Mac keyboard bindings

by darrinm

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.

June 1, 2014

Re: [Pharo-users] Mac keyboard bindings

by darrinm

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.

June 1, 2014

Re: [Pharo-users] STON on ScaledDecimal?

by Sven Van Caekenberghe

Hi JosÃ©, On 31 May 2014, at 01:32, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> 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

May 31, 2014

Bug in Nautilus... (Pharo 3)

by JosÃ© ComesaÃ±a

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Ã©

May 31, 2014

Re: [Pharo-users] STON on ScaledDecimal?

by JosÃ© ComesaÃ±a

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 <jtuchel(a)objektfabrik.de>: > Hi, > > Sounds good. But I think the Scale should be streamed as well: 12345.678s3 > > Joachim > > JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> 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 >

May 31, 2014

Re: [Pharo-users] [smallwiki] Pillar annotations for Latex

by Ben Coman

Damien Cassou wrote: > You can just commit to the http://www.smalltalkhub.com/#!/~Pier/Pillar > <http://www.smalltalkhub.com/#%21/%7EPier/Pillar> repository. > duh! of course. I was looking for my name in the contributors list, but then didn't notice it was a public repository. Its uploaded now.

May 31, 2014

Re: [Pharo-users] STON on ScaledDecimal?

by Joachim Tuchel

Hi, Sounds good. But I think the Scale should be streamed as well: 12345.678s3 Joachim JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> 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

May 31, 2014

STON on ScaledDecimal?

by JosÃ© ComesaÃ±a

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

May 30, 2014

Re: [Pharo-users] ical on pharo 2

by Paul DeBruicker

Hi Jesus Mari, Thanks for spotting and fixing those bugs. The missing methods are because I overrode them in a package Iâm using and forgot about that when I saved some changes to iCal. I did not notice the problem with the timeZone because Iâm in the habit of only using UTC dates and times in the image and converting them to timeZone specific formats for display. Good find. Re: #isValidForDate: Iâm not sure about your solution. I think it depends on whether December 31st 2014 is the important part or whether the overlapping timespan of one date between two timezones is important. And to know that Iâd have to read the ical spec. Which is here: http://tools.ietf.org/html/rfc5545 and I donât have time to go through in any detail. Do you want/have write access to upload your repairs? Thanks again Paul On May 30, 2014, at 4:03 AM, Jesus Mari Aguirre <jmariaguirre(a)gmail.com> wrote: > I have tried to run the Test package in Pharo 2.0 and I have found some problems. > * You use String #subString method that is deprecated. > * There are several methods missed in your new packages, I'm not sure why... > ICConversion class #dateAndTimeClass, #dateClass, #timeSpanClass #timeClass. I have added to the ICal-SqueakPharo-Core package copied from the first version in the repository. > * methods ICEvent isValidForDate: aDate and ICTodo isValidForDate: aDate do not take care about the timeZone, then several tests fail. These tests are successful if you set the date offset to 0 hour, but maybe what you try to do with the method is returning all the events and todos currently actives. > > Could be this method the right solution? > > ICEvent isValidForDate: aDate > > ^self start asDate start<= aDate end and: [self end asDate end>= aDate start]. > > ICTodo isValidForDate: aDate > > ^self due asDate start<= aDate end and: [self due asDate end >= aDate start]. > > I hope this information will be useful for you. > keep contact > JesÃºs MarÃ > >

May 30, 2014