seaside-dev

seaside-dev@lists.squeakfoundation.org

3398 discussions

How to convert scriptaculous UI stuff (ie lightbox dialogs) to jQuery equivalent . Or something else?
by Tim Rowledge 06 Dec '23

06 Dec '23

Should one even do that? Is Scriptaculous sufficiently outdated that we should replace usage of it? Is jQuery ui stuff outdated? If so, what ought we use? I'm certainly not up to date enough on web frameworks etc to have a serious opinion so all advice welcomed. My specific example here is the HPI tutorial, where scriptaculous code is used to make the to-do task editor pop up as a floating dialog. Whilst puzzling through some problems (ie the tutorial seems to omit adding the pt & su libraries, so lots didn't work) I noticed the jQuery related lightbox methods. So far as I can make out there is quite a difference in how to use the two approaches, with the jQuery apparently needing to be rendered into the containing page up front. tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim "#define QUESTION ((bb) || !(bb)) - Shakespeare."

1 0

PiHole blocks ajax.googleapis.com by default for some reason
by Tim Rowledge 02 Dec '23

02 Dec '23

I've been trying to follow (and update) the HPI seaside tutorial, during which I noticed some odd things happening in the jQuery UI functional test suite. The ajax.googleapis.com theme stuff wasn't loading. At first I thought it might be a bad URL because of a newer version but soon discovered that I couldn't get to the site at all in any browser or command. Some googling suggested it might be getting blocked by my PiHole DNS ad-blocker (no idea why that would get blocklisted) and adding it to the whitelist made it all start working. Now I have to work out how to convert the old scriptaculous stuff in the tutorial to jquery. tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Useful random insult:- Trying out for the javelin retrieval team.

1 0

NoVNC within seaside sites
by Tim Rowledge 14 Nov '23

14 Nov '23

One nice thing for debugging is using the Squeak RFB/VNC package and some port forwarding trickery to fix a problem live. A problem with that is sorting out the port to use and the forwarding - it's all very well if you have a single site but with a bunch of dynamically created ones it can get a bit fraught. NoVNC claims to provide an in-browser VNC connection back to your site. I've done a tiny bit of playing with it and I think it ought to be useful. So far though, no luck in making it talk to RFB/VNC. Has anyone else tried this and had success? Spotted problems that might be beatable? Concluded it is a fools errand? Found a better solution? tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Fractured Idiom:- VENI, VIDI, VISA - I came, I saw, I bought

2 2

GRSqueakPlatform not selected when installing
by Tim Rowledge 11 Nov '23

11 Nov '23

Maybe this is the wrong list, but whatever. After installing the current seaside/grease in Squeak 6.1 trunk I was surprised to notice that the selected GRPlatform subclass was GRPharoPlatform - and obviously it caused a problem as soon as I tried an example that wanted to be debugged. 'fixing' it with GRSqueakPlatform select is simple enough but I couldn't spot where the selection gets made in the code. Clearly *something* was choosing the pharo version. What did I miss? tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim I am still waiting for the advent of the computer science groupie.

2 2

Issue with ManifestJavascriptCore when attempting Seaside load into Squeak 6.1
by Tim Rowledge 28 Oct '23

28 Oct '23

I just attempted to load seaside into a trunk Squeak 6.1 image - mostly simply to see if it would. It didn't. :-( To be more precise, it *mostly* did but a warning popped up twice for what I'm pretty sure is the same reason. "This package depends on the following classes: PackageManifest You must resolve these dependencies before you will be able to load these definitions: ManifestJavascriptCore ManifestJavascriptCore class>>ruleTempsReadBeforeWrittenRuleV1FalsePositive" The package/version in the debugger at this point was Javascript-Core-cypress.1 Suggestions welcomed. I'm guessing that PackageManifest might be a Pharo class not in Squeak? tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Strange OpCodes: BNE: Buy Non-IBM Equipment

2 1

updating a progress bar whilst looping through many longish operations
by tim Rowledge 31 Oct '22

31 Oct '22

I'd like to have a progress bar updating while I loop through several thousand read-file-do-stuff-send-to-database-operations. The job is started as a result of clicking an on-screen button. So far I'm not seeing anything but the very last update have any effect, which really rather spoils the entire point of a progress bar :-( The Seaside jquery pages only mention how to create the bar. I'm clearly missing some important clue here. Can anyone offer me one? tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Fractured Idiom:- APRES MOE LE DELUGE - Larry and Curly get wet

3 7

#substrings:
by Philippe Marschall 06 Sep '22

06 Sep '22

Hello While looking at some of our Squeak 6 test failures I noticed that GRStringTest >> #testSubStrings is testing String >> #substrings:. This is a bit surprising / confusing because: - String >> #subStrings: is ANSI but String >> #substrings: is not. - The method name and comments in #testSubStrings suggest what we actually want to test is #subStrings:, not #substrings:. - The only sender we have of String >> #substrings: is GRStringTest >> #testSubStrings I see the following options: - leave as is - remove the tests and extension methods from GemStone and Squeak - switch to #subStrings: and add it as extension method to Pharo - introduce #greaseSubStrings: Do you have any opinions? Cheers Philippe

7 9

Re: [Seaside-dev] empty collection test failures
by Adriaan van Os 02 Sep '22

02 Sep '22

Hmmm.... VAST does what Pharo/Squeak did before: #(1 2 3) endsWithSubCollection: #(3). true "<- VAST (11)" #(1 2 3) endsWithSubCollection: #(). false "<- VAST (11)" #(1 2 3) beginsWithSubCollection: #(1). true "<- VAST (11)" #(1 2 3) beginsWithSubCollection: #(). false "<- VAST (11)" But what about the following? #() beginsWithSubCollection: #(). false "<- VAST (11)" #() endsWithSubCollection: #(). false "<- VAST (11)" In VAST both #beginsWithSubCollection: and #endsWithSubCollection: use #indexOfSubCollection:startingAt:, which is in an ANSI protocol. The comment in #indexOfSubCollection:startingAt: reads: "[..] Answer 0 if no such subsequence is found in the receiver, or if @targetSequence is empty. [..] Answer 0 if the receiver is empty" Answering 0 by #indexOfSubCollection:startingAt: results in #beginsWithSubCollection: and #endsWithSubCollection: to return false subsequently. What behaviour do we want/need in Seaside? Looks like Seaside has no senders with an empty argument. So maybe not bother and drop the test? Cheers, Adriaan.

2 1

Re: [Seaside-dev] #substrings:
by Adriaan van Os 02 Sep '22

02 Sep '22

FWIW, VAST has EsString>>#subStrings: and UnicodeString>>#subStrings:. I would say: settle for #subStrings: and add it as extension method to Pharo. Cheers, Adriaan.

3 2

empty collection test failures
by Philippe Marschall 01 Sep '22

01 Sep '22

Hello I had a look at our Grease test failures in Pharo 11 and Squeak 6. It seems like on both platforms #endsWith: and #beginsWith now answer true for empty arguments. The comment even says as much. "Some platforms implement #endsWith: to answer true for an empty argument." To me this behavior makes more sense than what we have right now. To give you an illustrative example: #(1 2 3) endsWithSubCollection: #(3). "true" #(1 2 3) endsWithSubCollection: #(). "false in Pharo 10 and Squeak 5, true in Pharo 11 and Squeak 6 " #(1 2 3) beginsWithSubCollection: #(1). "true" #(1 2 3) beginsWithSubCollection: #(). "false in Pharo 10 and Squeak 5, true in Pharo 11 and Squeak 6 " How should we proceed here? - Remove the test for empty collections and leave the behavior unspecified. - Keep the tests as is but change the implementations of #beginsWithSubCollection: and #endsWithSubCollection: to return false on empty collections. - Change the tests as is but change the implementations of #beginsWithSubCollection: and #endsWithSubCollection: to return true on empty collections. Cheers Philippe

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev