I hope this time it will be fine. I removed the newline characters. I will also check if I can keep the original url in the browser rather than the redirected one.
Regards, Christophe. > Le 29 août 2020 à 18:41, Dale Henrichs <dale.henri...@gemtalksystems.com> a > écrit : > > Christophe, > > Again, I appreciate your effort, but you are not quite there. > > If you look at SqueakSource or GemSource html (attached), the html uses <br > /> to create newlines on the page and in the Smalltalkhub page, you've > inserted a newline as part of the href filename, while SqueakSource and > GemSource (and the other monticello sites) do not include a newline in the > href, so for better or worse, in GemStone the method > MCReader>>canReadFileNamed: expects the filename to end with `.mcz` not a > newline and all of the filenames parsed from the SmalltalkHub page are > discarded as non-Monticello files. > > So if you eliminate the trailing newline in the href, the GemStone code > should finally be happy. > > Thanks for your effort! > > Dale > > > On 8/28/20 3:05 PM, Christophe Demarey wrote: >> I understand that he new site is unusable if tools do not get the expected >> input. Sorry for the inconvenience. I was just not aware of this as Pharo >> uses the raw format. >> I had to set up a CGI to produce an html listing from the raw file. >> It should now be ok. Could you tell me if it works in GemStone now? >> >> Christophe >> >>> Le 28 août 2020 à 19:21, Dale Henrichs <dale.henri...@gemtalksystems.com >>> <mailto:dale.henri...@gemtalksystems.com>> a écrit : >>> >>> Christophe, >>> >>> I appreciate your effort, but I assume that you aren't finished yet? >>> >>> When I use the url from your message I get a `Not Found` error (note that I >>> explicitly included a trailing slash in the url): >>> >>> <dkbjiegjmlbelgio.png> >>> >>> This is a bug (or omission) as well, since other Monticello sites produce >>> the expected HTML output with or without a trailing slash. >>> >>> Without the trailing slash I get the same (non-html) response that was >>> causing a problem before ... although something must have changed, because >>> the GemStone command is now producing an error instead of an empty list ... >>> Once you get the static site to produce the expected output, I'm confident >>> that the GemStone errors will go away (this code has been running for about >>> a decade on all Monticello html repositories). >>> >>> I suggest that you look at what is produced on SqueakSource >>> (http://www.squeaksource.com/MooseSQL/ >>> <http://www.squeaksource.com/MooseSQL/>) as an example of expected output >>> of the mcz file listing ... this html page format has been used since 2003 >>> for ALL (valid) monticello repositories. >>> >>> If it is not clear, the `?format=raw` option is a recent Pharo only option >>> and when the dynamic site was running and the `?format-raw` option was >>> OMITTED it produced output compatible with >>> (http://www.squeaksource.com/MooseSQL/ >>> <http://www.squeaksource.com/MooseSQL/>) ... >>> >>> Restoring HTML is *REQUIRED* for the static site to be a faithful >>> replacement of the dynamic site... the format that is produced today is >>> only compatible with the Pharo only `?format=raw` option. >>> >>> Bug or omission ... the static site is currently in worse shape than the >>> dynamic site before the swap ... >>> >>> Dale >>> >>> On 8/28/20 2:12 AM, Christophe Demarey wrote: >>>>> Le 28 août 2020 à 10:15, Sven Van Caekenberghe <s...@stfx.eu> >>>>> <mailto:s...@stfx.eu> a écrit : >>>>> >>>>> >>>>> >>>>>> On 28 Aug 2020, at 10:13, Christophe Demarey >>>>>> <christophe.dema...@inria.fr> <mailto:christophe.dema...@inria.fr> wrote: >>>>>> >>>>>> Smalltalkhub is now to able to distinguish between raw and not raw mcz >>>>>> listing requests. >>>>>> Ex: >>>>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw >>>>>> <http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw> >>>>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/ >>>>>> <http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/> >>>>>> >>>>>> I already use the apache directory index for another page so I will not >>>>>> be able to modify this one. I guess the current index will « not work » >>>>>> because glass expect some HTML structure. >>>>>> Could you confirm and tell me what is the expected structure? >>>>> See my earlier mail with code. >>>> Thanks Sven >>>> >>>> >> > <squeaksource.html><gemsource.html>
