BSL talk:Tutorial/airport1 level logic.bsl

Okay, here's my thoughts, seeing as my last test worked (see the first few lines of the bsl file, and note how the link takes you to the func it shows the name of). If we're going to seed the .bsl file's text with markup to use in making a TOC, we should use the <span> tag, so the changes to the text are invisible and we can use the monospaced "code" font universally without interruption. Then we can build a TOC manually using links to the span ids we set up. We could probably automate this to a degree with templates like Template:Anchor, which isn't working right yet (or I'm not using it right). If anything, this method should be less work than what you had to do to the bsl file to get a TOC to work. How does this sound? --Iritscen 17:41, 21 March 2008 (CET)

I am currently researching the idea of using templates to largely automate this method. Hopefully I can make this a lot less work than breaking up the page into sections was for you. --Iritscen 19:11, 21 March 2008 (CET)