Re: Status and whats the staus?

["Steve Hall" <digitect mindspring com>]

From: "Jeff Waugh" <jdub perkypants org>
> <quote who="Steve Hall">
>
> > The delivery won't depend on the templates. We can serve three different
> > scrap HTML pages to prove we can determine the browser
>
> Why are you so hung up on browser detection? It's not even a minor part of
> putting all of this together.

Because it's so critical to the templates I've already created! (I'll not
reiterate; you're welcome.) Why else do you think I've been screaming about
this? I do NOT want to start over. (But I will if the list agrees that it's
the Right Way.)


> > C. An authoring method which translates a submitted document
> > (HTML/text/XML/whatever) to our storage format (XML).
> > D. Code to auto-create the navigational HTML based on page location
> > within the structure. (NOT dynamically, but when authored in #C above.)
>
> That's what I've been working on for the last few months!

Well that's good to hear. I know we've talked about it a few times, but I
didn't know your progress. Is that something we'll be able to take a look at
soon? Is it in CVS? Where?


> > I think we're contending #3/#B here. Rather than say we *can* do it, I'd
> > rather us agree to whether we *are* or *are not* and proceed. Can we
> > please make this decision and move forward? There's still a lot to do.
>
> I still don't see what the rest of the system has to do with fixing up the
> design issues.

Again, I need to know if I'm fixing what I've got or if I'm starting over.
The way I see it, either we do server side detection, deliver the correct
CSS and use the current templates (which I have to keep tweaking), or /me
starts all over with HTML 3.2 table-type template, do a major re-design in
the process and forget the whole detection/browser-specific delivery thing.
Simple.


Steve Hall  [ digitect mindspring com ]