Squeak-dev September 2021

squeak-dev@lists.squeakfoundation.org

23 participants
205 discussions

XMLDomParser (monty) comments not preserved
by gettimothy 28 Sep '21

28 Sep '21

Just an FYI to whom it may concern... I am adding some complexity to the document from this source: (((XMLDOMParser onURL: 'https://w1.weather.gov/xml/current_obs/index.xml' upToLimit:nil) preservesCDataNodes: true; preservesCommentNodes: true) parseDocument) explore. CData and processing-instructions are being preserved, but comments are not. example slice of the data I add is where you can see the  stuff: <s:station subs="yes"> <?s:station-processing-instruction type = "XYZ"?>  <![CDATA[ station XYZ CDATA ]]> <s:station_id>XYZ</s:station_id> <s:state>NZ</s:state> <s:station_name>XYZ_ONE</s:station_name> <s:latitude>51.76667</s:latitude> <s:longitude>-114.68333</s:longitude> <s:html_url>http://w1.weather.gov/data/obhistory/CWAV.html</s:html_url> <s:rss_url>http://weather.gov/xml/current_obs/CWAV.rss</s:rss_url> <s:xml_url>http://weather.gov/xml/current_obs/CWAV.xml</s:xml_url> <s:substations> <s:substation location="north">  <s:station_id>XYZ1</s:station_id> <s:state>NZ</s:state> <s:station_name>XYZ_SUB_ONE</s:station_name> </s:substation> <s:substation location="northeast"> <s:station_id>XYZ2</s:station_id> <s:state>NZ</s:state> <s:station_name>XYZ_SUB_TWO</s:station_name>  </s:substation> <s:substation location="east"> <s:station_id>XYZ3</s:station_id> <s:state>NZ</s:state> <s:station_name>XYZ_SUB_THREE</s:station_name>  </s:substation> <s:substation location="south"> <s:station_id>XYZ4</s:station_id> <s:state>NZ</s:state> <s:station_name>XYZ_SUB_FOUR</s:station_name>  </s:substation> <s:substation location="west"> <s:station_id>XYZ5</s:station_id> <s:state>NZ</s:state> <s:station_name>XYZ_SUB_FIVE</s:station_name>  </s:substation> </s:substations> </s:station> The intent is to provide practice and examples on more complex axis:node-test[parameter]* paths in the Help/Documentation I am writing. Of these three XPath...only the comment does not work: self xpath:'/child::node()/child::s:wx_station_index/child::s:station[position()=1]/child::processing-instruction()'. a XPathNodeSet(<?s:station-processing-instruction type = "ABC"?>) self xpath:'/child::node()/child::s:wx_station_index/child::s:station[position()=1]/child::comment()'. a XPathNodeSet() self xpath:'/child::node()/child::s:wx_station_index/child::s:station[position()=1]/child::text()'. a XPathNodeSet( station ABC CDATA ) again, just an FYI. thanks for your time.

1 0

The Trunk: Tools-eem.1065.mcz
by commits＠source.squeak.org 27 Sep '21

27 Sep '21

Eliot Miranda uploaded a new version of Tools to project The Trunk: http://source.squeak.org/trunk/Tools-eem.1065.mcz ==================== Summary ==================== Name: Tools-eem.1065 Author: eem Time: 26 September 2021, 5:09:26.74426 pm UUID: a9290dc8-36cb-4526-a2f0-ed9e286ef3f7 Ancestors: Tools-eem.1064 Eliminate a shadowed variable warning. =============== Diff against Tools-eem.1064 =============== Item was changed: ----- Method: Browser>>defineMessageFrom:notifying: (in category 'message functions') ----- defineMessageFrom: aString notifying: aController "Compile the expressions in aString. Notify aController if a syntax error occurs. Install the compiled method in the selected class classified under the currently selected message category name. Answer the selector obtained if compilation succeeds, nil otherwise." + | currentSelector selector category oldMessageList selectedClassOrMetaClass | + currentSelector := self selectedMessageName. - | selectedMessageName selector category oldMessageList selectedClassOrMetaClass | - selectedMessageName := self selectedMessageName. oldMessageList := self messageList. selectedClassOrMetaClass := self selectedClassOrMetaClass. contents := nil. selector := (selectedClassOrMetaClass newParser parseSelector: aString). (self metaClassIndicated and: [(selectedClassOrMetaClass includesSelector: selector) not and: [Metaclass isScarySelector: selector]]) + ifTrue: ["A first-time definition overlaps the protocol of Metaclasses" - ifTrue: ["A frist-time definition overlaps the protocol of Metaclasses" (self confirm: ((selector , ' is used in the existing class system. Overriding it could cause serious problems. Is this really what you want to do?') asText makeBoldFrom: 1 to: selector size)) ifFalse: [^nil]]. + category := currentSelector - category := selectedMessageName ifNil: [ self selectedMessageCategoryName ] ifNotNil: [ (selectedClassOrMetaClass >> selectedMessageName) methodReference ifNotNil: [ : ref | ref category ]]. selector := selectedClassOrMetaClass compile: aString classified: category notifying: aController. + selector ifNil: [^ nil]. - selector == nil ifTrue: [^ nil]. contents := aString copy. + - self changed: #messageCategoryList. "Because the 'as yet unclassified' might just appear." self changed: #messageList. "Because we have code-dependent list formatting by now such as #isDeprecated." + selector ~~ currentSelector - selector ~~ selectedMessageName ifTrue: [category = ClassOrganizer nullCategory ifTrue: [self changed: #classSelectionChanged. self changed: #classList. self messageCategoryListIndex: 1]. self setClassOrganizer. "In case organization not cached" (oldMessageList includes: selector) ifFalse: [self changed: #messageList]. self messageListIndex: (self messageList indexOf: selector)]. ^ selector!

1 0

Squeak party now online at 8x8
by tim Rowledge 24 Sep '21

24 Sep '21

https://8x8.vc/3plus4/cast is now working. Join the party! tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Klingon Laundry Warrior:- "Today is a good day to dry!"

1 0

This weekend... Squeak turns: 25. We celebrate!
by Craig Latta 24 Sep '21

24 Sep '21

Hi all-- This weekend... Squeak turns 25 on Friday, 24 September 2021. Let’s celebrate! We'll begin with an informal online gathering, at [1]. It will start at 11am pacific time (18.00 UTC), and last all weekend, so that folks from all timezones may attend. To increase the chance of crossing paths, let’s aim for peaks at each noon and midnight UTC. We’re also using [2,3] as text backchannels, right now. There's a shareable announcement at [4]. Proceed for Truth! -C [1] https://8×8.vc/3plus4/cast [2] https://squeak.slack.com (created 2014) [3] https://discord.gg/xNm46K8T (created 2017) [4] https://tinyurl.com/squeak-turns-25 (thiscontext.com) -- Craig Latta :: research computer scientist Black Page Digital :: Berkeley, California 663137D7940BF5C0AFC :: 1349FB2ADA32C4D5314CE -- -- Craig Latta :: research computer scientist Black Page Digital :: Berkeley, California 663137D7940BF5C0AFC :: 1349FB2ADA32C4D5314CE

2 1

[ANN] Modern OpenGL & GLFW for Squeak
by gettimothy 24 Sep '21

24 Sep '21

Hey all, I've been working on hardware-accelerated graphics in Squeak for a bit now and wanted to share some of the projects I've been using to get current OpenGL versions running in Squeak trunk. https://github.com/hpi-swa-lab/squeak-graphics-opengl/tree/main/OpenGL https://github.com/hpi-swa-lab/squeak-graphics-opengl/tree/main/GLFW I'd consider these two projects mostly complete and hopefully stable, so feel free to try them out. You can find most of the interesting details in the READMEs (and class comments), so I'll hold myself back from repeating them here. If you have any questions, remarks or ideas pop me a message, create an issue or just answer this thread :) Cheers Stephan Thank you. I look forward to trying this in the hopes we can get Croquet running on later version of Squeak ! cheers.

1 0

Re: [squeak-dev] Interesting retrieval error with XMLDOMParser (solution found, needs guru attention)
by gettimothy 23 Sep '21

23 Sep '21

Update. I ran all the XML-Tests-Foo and no failures or errors. so that patch is non-intrusive towards them.

1 0

Re: [squeak-dev] Interesting retrieval error with XMLDOMParser (solution found, needs guru attention)
by gettimothy 23 Sep '21

23 Sep '21

I think I found a fix. for (WebClient httpGet: 'https://w1.weather.gov/xml/current_obs/index.xml') httpGet: calls httpGet: do: where we see the WebClient setting paramaters for the WebRequest thing in bold below. httpGet: urlString do: aBlock "GET the response from the given url" "(WebClient httpGet: 'http://www.squeak.org') content" | request | self initializeFromUrl: urlString. request := self requestWithUrl: urlString. request method: 'GET'. userAgent ifNotNil:[:ua | request headerAt: 'User-Agent' put: ua]. self contentDecoders ifNotNil: [:decoders | request headerAt: 'Accept-Encoding' put: decoders]. aBlock value: request. ^self sendRequest: request If I take some of that stuff and put the userAgent part into XMLHTTPWebWebClientRequest>>basicSend basicSend self webClientClient userAgent ifNotNil:[:ua | webClientRequest headerAt: 'User-Agent' put: ua]. " self webClientClient contentDecoders ifNotNil: [:decoders | webClientRequest headerAt: 'Accept-Encoding' put: decoders]." <-- note commented out ^ self responseClass request: self webClientResponse: (self webClientClient "#sendRequest: unfortunately requires #initializeFromUrl: to be sent first" initializeFromUrl: self url; sendRequest: self webClientRequest) The following calls work: (XMLDOMParser parseURL: 'https://www.w3schools.com/xml/simple.xml') explore. (XMLDOMParser onURL: 'https://w1.weather.gov/xml/current_obs/index.xml' upToLimit:nil) parseDocument; explore. (XMLDOMParser onURL: 'https://w1.weather.gov/xml/current_obs/index.xml') parseDocument; explore. (XMLDOMParser parseURL: 'https://w1.weather.gov/xml/current_obs/index.xml') explore. To summarize. for (WebClient httpGet: 'https://w1.weather.gov/xml/current_obs/index.xml') content. The WebClient correctly sets the headers for the WebRequest. For the XMLHTTPWebClientRequest which wraps both WebClient and WebRequest as instance variables, the WebRequest headers are not properly set. While I do not know enough about these systems to say definitively, it seems to me that the place to set them correctly is when the instance variable for WebRequest is created. cheers.

1 0

Re: [squeak-dev] Interesting retrieval error with XMLDOMParser
by gettimothy 23 Sep '21

23 Sep '21

XMLHTTPZincRequest basicNew initialize XMLHTTPWebClientRequest basicNew initialize This occurs in XMLAbstractFactory implementationNew on the former the wrapped ZnRequest has the User-Agent header. on the latter the webClientRequest is not even set yet. so... either XMLHTTPWebClientRequest should initialize its webClientRequest with correct headers or... I need to find where it is created and fix the headers. . I will try the latter first. at least now we know why

1 0

Re: [squeak-dev] Interesting retrieval error with XMLDOMParser
by gettimothy 23 Sep '21

23 Sep '21

Ok.... I believe this is the problem. Set a breakpoint In WebClient sendRequest: request contentBlock: contentBlock for the simple (WebClient httpGet: 'https://w1.weather.gov/xml/current_obs/index.xml') the WebRequest object looks like this: WebRequest(GET /xml/current_obs/index.xml HTTP/1.1 User-Agent: WebClient/1.5 (WebClient-Core-dtl.127; Squeak6.0alpha-20633; unix) Accept-Encoding: gzip Host: w1.weather.gov ) For the (XMLDOMParser onURL: 'https://w1.weather.gov/xml/current_obs/index.xml' upToLimit:nil) the WebRequest looks like this: WebRequest(GET /xml/current_obs/index.xml HTTP/1.1 Host: w1.weather.gov ) looking a little deeper, the headers are different... So...will try to figure out where that is set in one and not the other ---- On Thu, 23 Sep 2021 08:59:58 -0400 Marcel Taeumel <marcel.taeumel(a)hpi.de> wrote ---- Hi -- Not sure, which error your mean. Well, I had this little "contentStream" typo. This is the right call: (WebClient httpGet: 'https://w1.weather.gov/xml/current_obs/index.xml') content. Yet, I understand your "interop" concerns. Best, Marcel Am 23.09.2021 14:29:42 schrieb gettimothy <mailto:gettimothy@zoho.com>: Hi Marcel. It throws a Mal Formed Error on Squeak and on Pharo, the dependency on WebClient is not respected. Thank you for trying, I appreciate the effort. I am going to look deeper into the original error and see if I can fix it there. The reason interop is important, is because it makes the Help portable and I want to turn my work into a Pillar booklet as a first effort towards a full book on using the XML package on Squeak or Pharo. Thanks again. t ---- On Thu, 23 Sep 2021 04:59:19 -0400 Marcel Taeumel <mailto:marcel.taeumel@hpi.de> wrote ---- Hi -- It would be nice to have a streamlined support for loading XML documents from URLs. I think that WebClient would be the way to go for HTTP downloads: (WebClient httpGet: 'https://w1.weather.gov/xml/current_obs/index.xml') contentStream "XML-Parser" currently depends on "Files" because of SAXHandler class >> #parserOnFileNamed:. A dependency on "WebClient" might not hurt ... maybe through the "Tools" package? Hmmm... Well, I don't like the class-side interface of SAXHandler and XMLDOMParser. Instead, I prefer the reader/writer notion like this: XMLDOMParser onFileNamed: '...' XMLDOMParser onURL: '...' Considering the actual result, I like the interface of Form (for PNGs, JPEGs, etc.): XMLDocument fromFileNamed: '...' XMLDocument fromURL: '...' Please find attached a change set that makes the proposed interface work in Squeak Trunk. Best, Marcel Am 22.09.2021 22:30:08 schrieb gettimothy via Squeak-dev <mailto:squeak-dev@lists.squeakfoundation.org>: Hi Folks, No biggie, just interesting... |tree url | url := 'https://w1.weather.gov/xml/current_obs/index.xml'. tree := (XMLDOMParser on: (HTTPLoader default retrieveContentsFor: url) contents ) parseDocument. tree explore. (XMLDOMParser onURL: 'https://w1.weather.gov/xml/current_obs/index.xml') parseDocument; explore. "throws an error" The first form works on squeak. The latter form works on pharo. The latter does NOT Squeak because the XMLHTTPException: Forbidden (403) error gets thrown. It is interesting that a platform difference would cause that error. No biggie, but I would like to include a common retrieval method for both platforms in the XPathHelp (May turn it into a book down the road,too) cheers.

1 0

Re: [squeak-dev] Interesting retrieval error with XMLDOMParser
by gettimothy 23 Sep '21

23 Sep '21

Hi Marcel Thank you for your time. Bear with me, I am a bit slow on the uptake... I found where the Squeak and Pharo differ as I am debugging side-by-side. (btw, 'self break' does not appear to work in Pharo, but it does throw an error, so it is at least an inadvertant break point!) In DTDExternalEntityResolver >>resolveNonLocalExternalEntityURI: https://w1.weather.gov/xml/current_obs/index.xml upToLimit:nil the anXMLURIOrURIString asXMLHTTPRequest return two diffent things. The squeak returns a XMLHTTPWebClientRequest while the pharo returns a XMLHTTPZincRequest This means the problem lays somewhere in the XMLHTTPWebClientRequest. So..... I am going to reread your changeset and then see if I can fix the XMLHTTPWebClientRequest. ok...here is what I see as a problem with your changeset proposal bypasses the progression towards the DTDExternalEntityResolver where the correct branch to the ZincRequest is made for pharo . so that changeset on pharo would break pharo. imho, it merits to poke around in XMLHTTPWebClientRequest and see if I can fix that. cheers. ... ---- On Thu, 23 Sep 2021 08:59:58 -0400 Marcel Taeumel <marcel.taeumel(a)hpi.de> wrote ---- Hi -- Not sure, which error your mean. Well, I had this little "contentStream" typo. This is the right call: (WebClient httpGet: 'https://w1.weather.gov/xml/current_obs/index.xml') content. Yet, I understand your "interop" concerns. Best, Marcel Am 23.09.2021 14:29:42 schrieb gettimothy <mailto:gettimothy@zoho.com>: Hi Marcel. It throws a Mal Formed Error on Squeak and on Pharo, the dependency on WebClient is not respected. Thank you for trying, I appreciate the effort. I am going to look deeper into the original error and see if I can fix it there. The reason interop is important, is because it makes the Help portable and I want to turn my work into a Pillar booklet as a first effort towards a full book on using the XML package on Squeak or Pharo. Thanks again. t ---- On Thu, 23 Sep 2021 04:59:19 -0400 Marcel Taeumel <mailto:marcel.taeumel@hpi.de> wrote ---- Hi -- It would be nice to have a streamlined support for loading XML documents from URLs. I think that WebClient would be the way to go for HTTP downloads: (WebClient httpGet: 'https://w1.weather.gov/xml/current_obs/index.xml') contentStream "XML-Parser" currently depends on "Files" because of SAXHandler class >> #parserOnFileNamed:. A dependency on "WebClient" might not hurt ... maybe through the "Tools" package? Hmmm... Well, I don't like the class-side interface of SAXHandler and XMLDOMParser. Instead, I prefer the reader/writer notion like this: XMLDOMParser onFileNamed: '...' XMLDOMParser onURL: '...' Considering the actual result, I like the interface of Form (for PNGs, JPEGs, etc.): XMLDocument fromFileNamed: '...' XMLDocument fromURL: '...' Please find attached a change set that makes the proposed interface work in Squeak Trunk. Best, Marcel Am 22.09.2021 22:30:08 schrieb gettimothy via Squeak-dev <mailto:squeak-dev@lists.squeakfoundation.org>: Hi Folks, No biggie, just interesting... |tree url | url := 'https://w1.weather.gov/xml/current_obs/index.xml'. tree := (XMLDOMParser on: (HTTPLoader default retrieveContentsFor: url) contents ) parseDocument. tree explore. (XMLDOMParser onURL: 'https://w1.weather.gov/xml/current_obs/index.xml') parseDocument; explore. "throws an error" The first form works on squeak. The latter form works on pharo. The latter does NOT Squeak because the XMLHTTPException: Forbidden (403) error gets thrown. It is interesting that a platform difference would cause that error. No biggie, but I would like to include a common retrieval method for both platforms in the XPathHelp (May turn it into a book down the road,too) cheers.

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
21
Older →

Jump to page: