 | | Why I hate # anchors
|
|
(...) 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 (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) 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*! ;-) (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
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 (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
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 (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) 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 (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
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 (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Suggestion for LDraw FAQ
|
|
(...) [snip] (...) This is definitely something you need to do. I think that if you change the rather dull description "Ongoing maintenance and development" into "Release of new parts, programs and add on's" that item on voting procedures will catch (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) 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 (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) 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 (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
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) -- ---...--- (26 years ago, 14-May-99, to lugnet.faq)
|
