January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] XMLParser Problem with SVG

by monty

The problem with not fetching external DTDs/parsed entities is that they can contain entity declarations that affect the way the document is parsed. So your document is valid, but because it references &someEntity; which was declared in external.dtd, it will generate an error because external.dtd wasn't retrieved. But I am still considering what the best default behavior is. At a minimum I think the caching behavior (for HTTP) will become default. Old XML and code should still work, unless it references an external DTD or contains an internal subset it doesn't conform to. As for security, I already figured out how to secure the parser completely against every type of DoS attack (billion laughs, entity blowup, and so on) and will be adding that shorlty. I'm still considering what limits to impose on input. Right now there is already a three-deep limit on entity replacement. these limits will be configurable and removable. Â ----- Original Message ----- From: Igor Stasenko Sent: 01/06/14 11:25 AM To: Pharo Development List Subject: Re: [Pharo-dev] XMLParser Problem with SVG Hmm, my only question is about default behavior.Before it was not using/resolving any DTD links,and now it is... which means old code which was worked perfectly before, now will stop to function.So, maybe its worth to change the default behavior to be backwards compatible?Also, i'm not sure if it is good idea to go over a wire for an arbitrary content you can give to XMLDOMParser, imo this should be disabled by default, and instructed by user explicitly instead. Don't take me wrong: i really like that now we can handle DTD stuff properly, i'm only doubting current default way of handling it. Â On 6 January 2014 12:58, monty <monty.os(a)engineer.com> wrote:You can use the DTDCachingEntityResolver to cache responses: resolver := DTDCachingEntityResolver new. then: (XMLDOMParser onFileNamed: 'lion.svg') Â externalEntityResolver: resolver; Â parseDocument. or you could just disable validation and external entity resolution altogether: (XMLDOMParser onFileNamed: 'lion.svg') Â isValidating: false; Â resolvesExternalEntities: false; Â parseDocument. if you're parsing a string or stream (and you can always create your own file stream and give it that), you can do everything with just one message: XMLDOMParser Â parse: xmlStringOrStream Â usingNamespaces: true; Â validation: false; Â externalEntities: false. This is all in the documentation for SAXHandler.Â Â ----- Original Message ----- From: J.F. RickSent: 01/06/14 04:37 AM To: Pharo Development ListSubject: Re: [Pharo-dev] XMLParser Problem with SVG Â Monty, thanks. You are right that the latest version of XMLParser fixes the parsing problem. I think you just need to upload an updated configuration to the MetaRepoForPharo30 to fix this. And, yes, I would like to know how to turn DTD parsing off or for it to cache the DTD as it takes several seconds to retrieve the DTD for SVG and that gets annoying. Cheers, Jeff On Mon, Jan 6, 2014 at 10:18 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: On 06 Jan 2014, at 10:06, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 5 January 2014 15:19, J.F. Rick <self(a)je77.com> wrote:> I am trying to use SVG with Athens; however, the XMLParser for Pharo 3.0 cannot read normal SVG files that it used to. So, the demo of "ASVGMorph fromFile: 'lion.svg'" fails in the XMLParser (i.e., before ASVGMorph really does anything to it). It seems to download the DTD file from the Internet and then cannot properly parse it. Here is my setup: > > Up-to-date Pharo 3.0. Added XMLParser from the Configuration Browser. > Example file can be found here: http://www.thetangentbundle.net/w/images/f/ff/lion.svg > The following brings up an error: XMLDOMParser parseFileNamed: 'lion.svg' >> Hmm, why it tries to parse DTD file? It looks like something has changed in XMLDOMParser, because it wasn't before, and there is no support in SVG parser > for that. Â Yes, the parsing of DTDâd is new, Monthy added it recently. He says there is a way to turn it off. >> Cheers, > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > > >> -- > Best regards, > Igor Stasenko. Â Â -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick -- Best regards, Igor Stasenko.

Jan. 8, 2014

Re: [Pharo-dev] Update Log Messages

by Marcus Denker

On 08 Jan 2014, at 00:37, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Is there an easy way to see the messages chronologically? i.e. for 30535, > then 30536 > ScriptLoader new logStream contents â> all of them.

Jan. 8, 2014

Re: [Pharo-dev] Spotlight Demo

by Sean P. DeNigris

Tudor Girba-2 wrote > Seriously, this is fun. And now I am curious about the ActiveTutor :). Is > the idea to provide contextual help for every morph? Ha ha, you caught me. I wasn't going to mention it until it was further along, but here's a first cut... https://vimeo.com/83655001 (the video will be available in ~45 minutes) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spotlight-Demo-tp4733076p4735073.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 8, 2014

Re: [Pharo-dev] Spotlight Demo

by Tudor Girba

No. Thank you for the great contribution :). Seriously, this is fun. And now I am curious about the ActiveTutor :). Is the idea to provide contextual help for every morph? Cheers, Doru On Tue, Jan 7, 2014 at 11:12 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Tudor Girba-2 wrote > > I added the categories now. > > Ugh, you're too fast ;) I already had made several commits to the old > package. I'll try to merge into the new oneâ¦ > > Thanks for all the help!! > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Spotlight-Demo-tp4733076p4735029.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 8, 2014

Please Review Issue 12592: Text Embedded Morphs Broken

by Sean P. DeNigris

Fix in inbox: SLICE-Issue-12592-Text-Embedded-Morphs-Broken-SeanDeNigris.1 The following causes a DNU without the fix, works after: text := (Text withAll: 'foo') , (Text string: (Character value: 1) asString attribute: (TextAnchor new anchoredMorph: Smalltalk ui icons confirmIcon)) , (Text withAll: 'bar'). text asMorph openInHand Waiting for answer from Nico Cellier on squeak dev (see http://forum.world.st/Text-Morph-Embedding-Broken-td4735055.html) as to why you can't add a TextAnchor to Text with an arbitrary string anymore, but I'll make a new issue for that if necessary ----- Cheers, Sean -- View this message in context: http://forum.world.st/Please-Review-Issue-12592-Text-Embedded-Morphs-Broken… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 8, 2014

Re: [Pharo-dev] [Glass] printString and asString

by Carlo

+1 for #basicPrintOn: (sub classes might want to re-use base implementation) -1 for #basicDisplayOn: (not necessary and by definition no base implementation could satisfy all clients) On 08 Jan 2014, at 1:05 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: I don't want to add more fire to this... but I would even add a #basicPrintOn: and a #basicDisplayOn: in Object. The default #printOn: and #displayOn: would be based on these basic implementations. :) Esteban A. Maringolo 2014/1/6 Tudor Girba <tudor(a)tudorgirba.com>: > +1 > > > On Mon, Jan 6, 2014 at 4:19 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: >> >> + 1 >> >>>>>> I need for example a string representation of objects generally to >>>>>> display in anchors in our seaside application. We have a class >>>>>> DomainObject from which most of our classes inherit, so this is >>>>>> probably the place to add a 'displayString' for something like this. >>>>> >>>>> Not necessarily domain objects only. >>>>> >>>>> Some core objects (Blocks, CompiledMethods, etc.) could benefit from >>>>> having a developer string representation (#printString) and a UI >>>>> string representation (#displayString). >>>> >>>> I don't really understand why. How would you distinguish between which >>>> (kinds of) core objects and which not? Will you not end up with a >>>> displayString on Object again? >>> >>> Yes, I want displayString on Object. >>> >>> What I don't like is #asString in Object. >>> >>> I want to be able to do: >>> Transcript show: anyObject displayString. >>> >>> Without getting a single quoted output if anyObject was a String. >>> >>> Regards. >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Jan. 8, 2014

Update Log Messages

by Sean P. DeNigris

Is there an easy way to see the messages chronologically? i.e. for 30535, then 30536 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Update-Log-Messages-tp4735044.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 7, 2014

Re: [Pharo-dev] [Glass] printString and asString

by Esteban A. Maringolo

I don't want to add more fire to this... but I would even add a #basicPrintOn: and a #basicDisplayOn: in Object. The default #printOn: and #displayOn: would be based on these basic implementations. :) Esteban A. Maringolo 2014/1/6 Tudor Girba <tudor(a)tudorgirba.com>: > +1 > > > On Mon, Jan 6, 2014 at 4:19 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: >> >> + 1 >> >> >>>> I need for example a string representation of objects generally to >> >>>> display in anchors in our seaside application. We have a class >> >>>> DomainObject from which most of our classes inherit, so this is >> >>>> probably the place to add a 'displayString' for something like this. >> >>> >> >>> Not necessarily domain objects only. >> >>> >> >>> Some core objects (Blocks, CompiledMethods, etc.) could benefit from >> >>> having a developer string representation (#printString) and a UI >> >>> string representation (#displayString). >> >> >> >> I don't really understand why. How would you distinguish between which >> >> (kinds of) core objects and which not? Will you not end up with a >> >> displayString on Object again? >> > >> > Yes, I want displayString on Object. >> > >> > What I don't like is #asString in Object. >> > >> > I want to be able to do: >> > Transcript show: anyObject displayString. >> > >> > Without getting a single quoted output if anyObject was a String. >> > >> > Regards. >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Jan. 7, 2014

Re: [Pharo-dev] Spotlight Demo

by Sean P. DeNigris

Tudor Girba-2 wrote > I added the categories now. Ugh, you're too fast ;) I already had made several commits to the old package. I'll try to merge into the new oneâ¦ Thanks for all the help!! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spotlight-Demo-tp4733076p4735029.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 7, 2014

Re: [Pharo-dev] Spotlight Demo

by Tudor Girba

I added the categories now. Doru On Tue, Jan 7, 2014 at 9:49 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Please wait before going on :). I published a Spotlight2 (renamed package > and classes) in PharoExtras together with a development configuration. > Please use this one. > > You can load it from: > > Gofer new > smalltalkhubUser: 'PharoExtras' project: 'Spotlight2'; > package: 'ConfigurationOfSpotlight2'; > load. > (Smalltalk globals at: #ConfigurationOfSpotlight2) loadDevelopment. > > I just noticed that indeed, the tags are gone. I have no idea why, but I > suspect it has to do with the refactoring I did. I will fix the categories > tomorrow. > > Cheers, > Doru > > > > On Tue, Jan 7, 2014 at 7:24 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > >> Tudor Girba-2 wrote >> > Ok. I am renaming it and will publish it in PharoExtras. >> >> Thanks. I just loaded it. There is a problem. It flattened the package, >> removing all my sub-categories/tags/whatever-we're-calling-them. >> >> Also, I don't think it is necessary to rename the package and all the >> classes as there is no name conflict with Esteban's. Although maybe I'm >> missing something. What do you think? >> >> I'm going to continue to commit to the old package until we get this >> sorted >> out. >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Spotlight-Demo-tp4733076p4734989.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 7, 2014