[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] NKedit and Instructions
- To: "'hobbit (at) hswn.dk'" <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] NKedit and Instructions
- From: "Epp, Matthew Contractor PEO EIS AKO" <matthew.epp (at) us.army.mil>
- Date: Wed, 26 Jul 2006 18:59:43 -0400
> -----Original Message-----
> From: henrik (at) hswn.dk [mailto:henrik (at) hswn.dk]
> Sent: Friday, July 21, 2006 5:24 AM
> To: hobbit (at) hswn.dk
> Subject: Re: [hobbit] NKedit and Instructions
>
> You're welcome to look at the source code, but this particular bit of
> Hobbit is not one of the prettier in terms of how it's implemented :-)
> Eventually you will end up in lib/htmllog.c and try to tweak that.
Just completed my modification to htmllog.c and the code is working
perfectly so far. I'm not a very skilled C coder though, so there may be
some potential bugs in the code. I can post the code if anyone wants to try
it out. It isn't a very drastic change to the file, just the function and an
additional #include.
> However, I think you could do this without changing a single line of
> code in Hobbit. The ~hobbit/server/web/hostsvc_footer is already
> inserted at the bottom of all the status pages (in the default setup,
> it's just a link to bb_footer, but copy that and make your own file).
I tried that at first, and it sort of worked, however I noticed that only
Firefox even showed the object at all. Internet Explorer just acts as if the
<object> tag isn't even there. I didn't like how it was within a frame with
a scrollbar either, and wasn't sure if there was a way to easily change
that.
> One nice aspect of this is that you have completely de-coupled the
> maintenance of the instructions from Hobbit. If you have a content
> management system for uploading the instructions, you can use that to
> maintain the data. Or any other tool which is appropriate.
I don't have a content management system yet, so I guess the next step is to
look at how you control the editing of the hobbit-nkview.cfg and emulate
that for my comments.conf and other content files.