 | | [LDraw FAQ] Who wrote LDraw? —Jacob Sparre Andersen
|
| | | Subject: Who wrote LDraw? Content-Language: en Topic-Level: 0 Revision: Jacob Sparre Andersen, 1999-05-14 Location: /cad/ Comment: Unedited cut from the LDraw FAQ. Comment: Insert link to the Memorial. <P> James Jessiman. James passed away July (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | |
| | | | | Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | (...) Whoops. This won't work in the current FAQ format, but we need its capability. Suggestions? Cheers, - jsproat (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | |
| | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jacob Sparre Andersen
|
| | | | | Jeremy: (...) Good you caught it. There is more of the same. Can we assume that when we have a raw FAQ entry file named "some_entry.en.faq" with the location header Location: /category/group/,/other/group2/ the FAQ web site will contain files named (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | |
| | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | | | | (...) Ah...no. We need to be able to solve this without using duplicate files. Plus, this action would break if the FAQ were slurped into one big file. Urg. Cheers, - jsproat (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | |
| | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jacob Sparre Andersen
|
| | | | | | | | | Jeremy: (...) If an answer is located in two places, we will also need two copies in the _processed_ version of the FAQ, not in the raw data (of cause). (...) Yes. Do you have a better solution (preferably not one that involves too much work). Play (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | | |
| | | | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | | | | | | | (...) Do we really need duplicates in the output, though? Physical location in the subdirectory structure can be worked around. Also, at this point, I'm inclined to scrap the Location header (1), since I can't see any real use for it. Cheers, - (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | | | |
| | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | | | | | (...) Okay, I got it. From my end, I can guarantee that all FAQ items (1) have unique file names. This is the key thing, to be able to find a specific file by its name, in any subdirectory. So, to make a HREF to "#whatsitz" in file "flarn.en.html" (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jacob Sparre Andersen
|
| | | | | | | | | Jeremy: (...) [...] (...) OK. Will you take care of keeping a list of used entry names? (...) Skip the ".en.html#whatsitz". * Fixed language codes (".en") will give us unneccessary problems when translating the FAQ. * Todd will generate the (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | | |
| | | | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | | | | | | | (...) Already done. Actually, this is already being done, albeit indirectly. I've been giving the FAQ items longish and semi-informative filenames; e.g. "number_bricks_sf_to...c.en.faq". This significantly reduces the odds of getting a duplicate (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jacob Sparre Andersen
|
| | | | | | | | | | Jeremy: (...) Fine. I would like to reserve these names for entries from the LDraw FAQ: who_wrote_ldraw bmp_to_dat_conversion changing_hinge_betwe..._dat-steps changing_ldraw_output_location clear_ldraw_parts ldraw_colours comments_in_dat-files (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | | | | | | | (...) Okey-dokely. I'll put empty entries for the ones I don't have yet. They'll be unanswered for the time being, but this will ensure that the filenames are held. Heh, and I was working so hard to get the number of unanswered items *down*! ;-) (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | | | |
| | | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Todd Lehman
|
| | | | | | | | (...) If you make the filenames themselves unique, you'll end up in the long run encoding bastardized forms of the directory names into the filenames in order to keep the namespaces clean. No way to avoid that. :-( --Todd (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | | | | | (...) An alternative is to refer to the directory and the file specifically, leaving the slurper script to figure out if it should resolve the address or not (1). The drawback to this is, is that the author who wishes to link to another items has (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | | | Namespace of FAQ-entry filenames —Todd Lehman
|
| | | | | | | | (...) By "resolve the address" do you mean munging the HREF? Can you give an example? (...) Doing that is surely gonna be easier than firstly doing that and secondly looking up the associated global ID string. (...) In a very large system of ID (...) (25 years ago, 15-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | | | Re: Namespace of FAQ-entry filenames —Jeremy H. Sproat
|
| | | | | | | | (...) Sure. Example 1: File "twitch.faq" contains the HREF ".../twitch#kneecap". The HREF is pointing to a name within the same file. The script would convert the HREF to "#kneecap". Example 2: File "scarface.faq" contains the HREF ".../boondoggle". (...) (25 years ago, 15-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Todd Lehman
|
| | | | | | (...) No, because it's unlikely that the website will contain any files with the .html extension -- they'll definitely all be generated on-the-fly (dunno what the URLs will look like yet) with transparent caching of generated content. (...) Yup, (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jacob Sparre Andersen
|
| | | | | | | Todd: (...) OK. On www.ldraw.org it will definitely be files (I need the processor to run X and other things). Play well, Jacob ---...--- -- E-mail: sparre@cats.nbi.dk -- -- Web...: <URL:(URL) -- ---...--- (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | |
| | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Todd Lehman
|
| | | | | | | | (...) It would be super-cool if we had a cross-platform way to give some sort of "see-also" link from one FAQ question to another -- so that the links could be handled in a way most appropriate to their target platform... In an LDraw-oriented FAQ (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jacob Sparre Andersen
|
| | | | | | | | Todd: (...) Yes. I think Jeremy's suggestion (".../entry_file_name") is a reasonable solution for this. (...) Each question will appear as a separate file on ldraw.org (the LDraw FAQ is more than 40 kb _text_ at the moment). (...) Five in the 32 (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | | | (...) I'm just curious, FMI (1): Why generate them on-the-fly when you only really need to generate them once after a change? What advantage does on-the-fly generation give us? Or when you say transparent caching, that means that the FAQ items are (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Todd Lehman
|
| | | | | | (...) Although the number of possible views into the FAQ is finite, it may very well be an extremely large number when all is said and done -- that is, when viewing options are taken into consideration. For example, the sitemap.cgi pages, based at (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Todd Lehman
|
| | | | (...) Jeremy, what are the antecedent of the words "this" and "its" in your sentence above? The general idea of referring via "see ..." to another question, or the "#xxx" anchors? I hope there never ever* is a need for any "#xxx" anchors in this (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | |
| | | | | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?) —Jeremy H. Sproat
|
| | | | (...) "this" refers to using URLS to point to other FAQ items. "its" as in "its capability" refers to the essential capability to use URLs to point to other FAQ items. (...) I'm not sure about never ever (1) but it'd still be nice to point to other (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | |
| | | | | | Why I hate # anchors —Todd Lehman
|
| | | | (...) I think #-anchors are totally evil and I wish they'd never been invented in HTML (or at least implemented as poorly as they have been by the browser manufacturers). Here's why I think they totally suck and I hate them even more than I hate the (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | |
