|
|
Posted by Richard on 08/14/07 15:53
On Aug 14, 11:18 am, "Beauregard T. Shagnasty"
<a.nony.m...@example.invalid> wrote:
> Richard wrote:
> > No matter. That's been overtaken by events, i.e. please see my
> > response to Jonathan and take a peek at my latest version at
> >http://home.comcast.net/~CaptQueeg/_Mian.html.
>
Hi Beauregard,
> Ok, that'll work. <g>
Yeah, thankfully. I love that technique. Presently I save my notes
as .doc files in a hierarchy of subject directories. There's lots
wrong with that, but I wasn't willing to spend time/energy/money on
coming up with a better way ... until now, when I'm starting to "feel
my oats" with HTML-CSS-JavaScript in my new software-developer
incarnation.
BTW, my history is Visual C++/MFC/COM on Windows; C on VAX/VMS; DG
and Eclipse with Basic; micros with CP/M and C; IBM Mainframes with
PL/1, Cobol, Fortran, ASM; IBM 1620 with Fortran, Assembler.
There's still going to be annoying bookkeeping to synchronize the
links and the content, but I'm already planning two things:
1. a Ruby script to take a newly modified "Notes.html", backup the
modified file, strip its "menu" of links, regenerate the links based
on text in <h2> tags, paste the new links in the new file.
2. Through in some Ruby on Rails and Ajax so that only top-level links
are shown and subordinate links to <h3> links are shown for for the
current link and the <h3> links are closed when a new <h2> link is
selected.
I don't know how it'll all work out, if ever, but I'll have fun.
> You wouldn't want to use that "dummy section" on a production page,
> though. There isn't any good way to do what you want, other than to make
> sure you have enough content to keep the anchor/id at the top of the
> viewport. And testing it at various browser widths, too, including very
> wide ones.
Presently, I'm only concerned out my own "Notebook". Nevertheless,
I don't think my hack will be a problem if I publish such a thing. If
I do publish and find a problem, I'll resort to scripting,
> I've never noticed user problems if the anchor spot wasn't right at the
> top. They seem to find it...
I was the counter-example. I clicked on my link (after the code was
corrected, but without my hack) and saw nothing change. I leaped to
the conclusion that there was something wrong with my code. Of course
I eventually realized that browsers don't operate the way they should
IMHO.
Again, my thanks, Beauregard, for "tuning in". I very much
appreciate your insights.
Best wishes,
Richard
Navigation:
[Reply to this message]
|