Bill Moseley wrote:
Ok, back at http://hank.org:5000

I think I like the search box at the top.  That's a common place on many
sites.  Then the side-bar search can go away, which I think makes Stas happy.

love it!

+1

- Need a better "go" button, and a little less tall.  Who's handy in The
Gimp/Photoshop?

First let's decide do we want Search => Go, or just Search as a submit button?


- I moved the navigation to the far left.  The search far left was ugly.
Could argue that then the navigation top doesn't line up with the
navigation at the bottom.  Or, on the other hand, one could argue that it
follows the flow of the text with the prev the first thing on the left side
of the page, and the next at the bottom right.  I just think it looks
better with the with the search on the right.

+1

BTW -- does anyone else think that the Prev|Next images are a bit big or
over powering?  What about http://hank.org:5000/test1/docs/index.html?

-0, I think it's good for them to stand out, I believe the thin margin is good. May be what makes certain buttons overpowering is the strong bg. What if use a lighter bg similar to the bg of the left box with menus? For buttons and the title?


I want to keep the margin for 'Top' for sure, otherwise it gets lost withing text.

- Let's move the [SRC][PDF] to the bottom of the page.  The vast majority
of people will view in html, after all, so why clutter up the header with
that.

we have an empty space anyway, and it's a useful feel. What if I prefer to read the PDFs and not HTML, that way I'll have to scroll down all the time... think of long pages. We can definitely have them in both places.


- There's really too many choices in the search drop down box.  I think we
could get by with just the top level dirs, and maybe docs/1.0 docs/2.0.
Although I could see limiting searches to the guide, I suppose.  In other
words, it's too many choices for most, but for a few it will be helpful.
It's not a big issues, so I'm +0.

There is another problem: When you go deeper than the subgroup listed in options, you cannot search only it. i.e. the concept of 'This section' is gone. So may be we keep the Whole site/ This section only options?


Though I do like what you've done with all the options on it. May be we can find some middle ground and have:

Whole site
This section
and main sections

notice that the guide, will be a thing of the past soon, as /docs/2.0 will take over it.

- I don't really think we need the tree display, Stas.  Just use a
drop-down box on the "advanced" form would work.  I just can't see someone
selecting more than one check box.  But it is a cool feature...

I don't know. Since we have it already, I'm fine to keep it. We can change it later, it's always easier to remove than add.


- I'm using px settings for the input and select styles.  Might need to fix
that.

yes, should use 'em's

- Stas, the navbar_local_top calls [%- INCLUDE search_field -%], the
search_field does a [% PROCESS search_options %], which is an array and
hash for labels.  What I need is a way to then copy "search_options" to the
dst_html/search directory so the cgi script can PROCESS it.

Probably the simplest is to put the source template in src/search/ and have the templates seach this src/search/, just add the new search path to src/config.cfg


- I tested on NS4.0, IE6, mozilla in Win98, and Galeon, mozilla, Konqueror
under Linux.

Konqueror doesn't right justify the search stuff, nor the camel.  Camel is
follows after the bread-crumb.

Yes, we know that. We gave up on trying to fix that. But it's sort of a cool bug :)


- Can I remove the side-bar search? Can I cvs ci?

let's see what others think first.

Other misc while I'm here:

- .htaccess is not working, but I can't find the problem.  I even looked at
the cvs diffs and still missed the problem.  Apache is not very helpful:

[Wed Apr 17 17:57:23 2002] [alert] [client 192.168.0.98]
/data/_g/lii/modperl-docs/dst_html/.htaccess: Redirect takes two or three
arguments, an optional status, then document to be redirected and
destination URL

You mean some of the redirects are broken?

I'd rather see "Error on line 12"!

using the elimination technique?

- Jobs javascript lookup doesn't render well in NS4. Attached image.

Yup, I can see here. I'll try to fix it. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to