From: Jeff D. <da...@da...> - 2000-07-19 22:19:45
|
On a related note: what about trying to phase out the page references altogether? As far as I can see (except for the case of inlined images) [1] with the appropriate entry in the page references is identical in function to [1|http://www.foo.bar/wazoo.html]. Now... In message <Pin...@bo...>,Steve Wai nstead writes: >But unnamed, bracketed image links do: > >[http://phpwiki.sourceforge.net/phpwiki/png.png] > >Does anyone see any obvious flaws to this? Nothing terrible. But it sort of breaks my intuitive feeling that [http://foo/bar.png] should be equivalent to http://foo/bar.png in the same way that [WikiWord] is equivalent to WikiWord. > Would you rather introduce a > new construct, which might be more intuitive, like: > >{http://phpwiki.sourceforge.net/phpwiki/png.png} If you're going to invent new syntax, how about something that doesn't create any more special characters. Maybe something like [ INLINE | alt text | http://foo.com/img.png ] Yeah, it's ugly. There's probably something better. A couple of things to think about: To by lynx friendly, it would be nice to be able to specify ALT text for an inlined image. One of the reasons I personally don't use the wiki inlined images very much is that there's currently no way to specify the image size. With my browser, that means I don't get to see any of the page until the image loads. I hate that. One could create syntax for specifying image size: [ INLINE 20x60 | alt text | http://foo.com/img.png ] Or to get fancy, one might be able to have PhpWiki fetch the image once (in a while) and cache the size. In other news. The CVS problem appears to be fixed. You can now check out (or otherwise use) named revisions. I've mostly finished hacking in PATH_INFO support (switchable in wiki_config.) Soon (probably tomorrow) I'll check it into a branch ("jeffs_pathinfo_hacks-branch") in the CVS so y'all can inspect it. Jeff |