August 23, 2005
On Tue, 23 Aug 2005 15:09:17 +0100, Stewart Gordon wrote:

> That reminds me Derek - you were going have a go at tidying up the pages.  How far have you got with it?

I had a go at it but it's a lot of work patching things up like that. I must of got rid of my efforts because I can't locate them now.

It needed a good revamp with CSS usage. It would be best (read: economically) done with some form of generator that holds the content and is applied over some template system.

I've just about finished the automatic indexing tool, just some tidying up to do now.

-- 
Derek Parnell
Melbourne, Australia
24/08/2005 12:54:30 AM
August 23, 2005
"Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:dee2dn$1qgc$1@digitaldaemon.com...
> "AJG" <AJG@nospam.com> wrote in message news:deduje$1mca$1@digitaldaemon.com...
>> Here's a simple example:
>>
>> http://limpid.nl/lab/css/fixed/left-sidebar
>
> That looks _very_ good.  I'd really like that.

I've been implementing this layout in my site, and it's working wonderfully! I makes for very clean-looking HTML, and it's great that all the pages are consistent.  Only problem I have with it is that I have to copy the code for the header and nav bar to each page, so if I want to change something in the nav bar, I have to go through each page and change it; but I'm sure I'm doing something wrong there.


August 23, 2005
Derek Parnell wrote:
> On Tue, 23 Aug 2005 15:09:17 +0100, Stewart Gordon wrote:
> 
>> That reminds me Derek - you were going have a go at tidying up the pages.  How far have you got with it?
> 
> I had a go at it but it's a lot of work patching things up like that. I must of got rid of my efforts because I can't locate them now.
> 
> It needed a good revamp with CSS usage. It would be best (read: economically) done with some form of generator that holds the content and is applied over some template system.

Do you mean a tool to compile HTML files from some source documentation format?  I'm not sure this is necessary.  HTML isn't that complicated. But maybe if we feel the need, something like this could be done at a later stage.

If you don't want to do it anymore, I'll give it a go.  Here's an idea: I'll take one of the pages home to work on, write a stylesheet and then post the result here.  When this is done, if it's OK with everyone then we can work on getting the others converted.

> I've just about finished the automatic indexing tool, just some tidying up to do now.

Excellent!

Stewart.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:- a->--- UB@ P+ L E@ W++@ N+++ o K- w++@ O? M V? PS- PE- Y? PGP- t- 5? X? R b DI? D G e++>++++ h-- r-- !y
------END GEEK CODE BLOCK------

My e-mail is valid but not my primary mailbox.  Please keep replies on the 'group where everyone may benefit.
August 23, 2005
Hi,

Jarrett Billingsley says...
>
>"Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:dee2dn$1qgc$1@digitaldaemon.com...
>> "AJG" <AJG@nospam.com> wrote in message news:deduje$1mca$1@digitaldaemon.com...
>>> Here's a simple example:
>>>
>>> http://limpid.nl/lab/css/fixed/left-sidebar
>>
>> That looks _very_ good.  I'd really like that.
>
>I've been implementing this layout in my site, and it's working wonderfully! I makes for very clean-looking HTML, and it's great that all the pages are consistent.  Only problem I have with it is that I have to copy the code for the header and nav bar to each page, so if I want to change something in the nav bar, I have to go through each page and change it; but I'm sure I'm doing something wrong there.

What you need, my man, is a little dynamic magic. What kind of server setup are you running?

The simplest solution to your dilemma is SSI (server-side includes). This is a very straightforward way of including content from one file into many other files.

So you would have:

~/nav.inc.html = contains navigation code.
~/index.shtml  = contains index page.
~/page1.shtml  = some other page.

Then, in index.shtml and page1.shtml (and every other page you want the nav menu to appear in), you would INCLUDE nav.inc.html.

The canonical way to do this is with the following:

<!--#include file="nav.inc.html" -->

For that to work, your server must support SSI, and the _container_ page must be named with a .shtml extension. The _included_ page can have any extension, unless it, too, has SSI in it, in which case it must also be .shtml.

----------

More elaborate solutions exist using Perl or PHP or even Apache magic, but I think the simplest, quickest one is SSI. Let me know if it works out for you.

Cheers,
--AJG.


August 23, 2005
In article <deeevd$2bgr$1@digitaldaemon.com>, Walter says...
>
>
>"AJG" <AJG@nospam.com> wrote in message news:deeb3g$27o1$2@digitaldaemon.com...
>> Walter wrote:
>> > I agree totally. I'll work on it.
>>
>> Awesome.
>> --AJG.
>
>The phobos stuff is done. It only awaits google to reindex it before the search works.

Great work! What about moving the spec itself into a /d/spec/ or a /d/lang/ directory? That would finally untie it from the archives.

Cheers,
--AJG.


>


August 23, 2005
"Derek Parnell" <derek@psych.ward> wrote in message news:qwaaf2ne46kc.1az2ivuqb6rt0$.dlg@40tude.net...
> It needed a good revamp with CSS usage. It would be best (read: economically) done with some form of generator that holds the content and is applied over some template system.

Currently, the pages *are* generated using a simple text macro preprocessor I wrote. It sure makes it a heck of a lot easier to manage hundreds of pages.


August 23, 2005
"clayasaurus" <clayasaurus@gmail.com> wrote in message news:defb5q$u4v$1@digitaldaemon.com...
> I think techtips has the same problem: http://www.digitalmars.com/techtips/index.html

True, I just haven't done that directory yet.


August 23, 2005
"AJG" <AJG_member@pathlink.com> wrote in message news:defm8j$1if5$1@digitaldaemon.com...
> Great work! What about moving the spec itself into a /d/spec/ or a
/d/lang/
> directory? That would finally untie it from the archives.

Yes, I should do that too.


August 23, 2005
Jarrett Billingsley wrote:
> "Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:dee2dn$1qgc$1@digitaldaemon.com...
> 
>>"AJG" <AJG@nospam.com> wrote in message news:deduje$1mca$1@digitaldaemon.com...
>>
>>>Here's a simple example:
>>>
>>>http://limpid.nl/lab/css/fixed/left-sidebar
>>
>>That looks _very_ good.  I'd really like that.
> 
> 
> I've been implementing this layout in my site, and it's working wonderfully! I makes for very clean-looking HTML, and it's great that all the pages are consistent.  Only problem I have with it is that I have to copy the code for the header and nav bar to each page, so if I want to change something in the nav bar, I have to go through each page and change it; but I'm sure I'm doing something wrong there. 
> 
> 

yea, you're missing something:
pull out all the "style" definitions to a .css file, then include it in your html.

I'm not sure about the details, but I think:
<head>
<!-- what ever you want to put ... -->
<link href="style.css" rel="stylesheet" type="text/css">
</head>
August 23, 2005
"Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:deffus$17g8$1@digitaldaemon.com...
> Only problem I have with it is that I have to copy the code for
> the header and nav bar to each page, so if I want to change something in
the
> nav bar, I have to go through each page and change it; but I'm sure I'm doing something wrong there.

I use a simple macro text preprocessor.