allan wrote:
hi stas etc.

Stas Bekman wrote:

[CC'ing the list, since I need to raise a few issue to be decided ]

to get pdfs you need to add -d flag, have you considered build -h ;)


[OT] yes, i know this option (-d), but i get Can't exec "ps2pdf": No such file or directory at /ajutest/a/modperl-docs/bin/../lib/DocSet/Doc/Common.pm line 26. - what am i missing?

You are missing the ps2pdf utility coming with ghostscript package.

You mean DocSet didn't clearly stated that you need this to create pdfs? Can you please debug why? Look at sub can_create_ps DocSet/RunTime.pm this is called from
lib/DocSet/DocSet/PSPDF.pm: my $html2ps_exec = DocSet::RunTime::can_create_ps();
and
lib/DocSet/Doc/Common.pm: my $html2ps_exec = DocSet::RunTime::can_create_ps();


Thanks a lot!

* because the input field in opera is quite big and seems
non-adjustable i think we should increase the height of all
the widgets to 22px including the download_link, but that we
can of course do later if we decide.

well, from my testing on other linux browsers it's going to be a big
pain. the height is different in konqueror. You cannot use absolute px
in font size, you know that. I've attached a snapshot. I'm not talking
about NS4, which is a mess as usual.


- how is it a mess, mine looks perfect?

what's the definition of mine ;)

- why can't i use absolute font-size (not that i have the desire)?

you know why. Because on certain systems the text will be unreadable.

in any case we move to images, so it's not an issue. Will commit the change soonish.

- btw, looking at the screenshot, i noticed the logo wasn't
centered. are you running latest code?

yup, may be I've missed bits of your changes. It's hard to do it right when applying manually. Can you diff your rep with cvs?


I suggest to mix images with text, so we have a really fixed text of the
same width as prev|next.

But, how about putting the download sizes into the ALT tag? This way we
solve the problem immediately and simply use the pure images.


actually i tried that here, but i didn't really like it as it seemed unclear what pdf|src actually was doing there.

Don't worry, people will figure out after awhile. Our site is not for one time use.


i like the idea of putting the sizes in the alt tag.
but i suggest that we stick to text and then text _exactly_
like this:
| Pdf 5.5K | Src 516B |

please note (i forgot to mention) that the code i sent used
a fixed width 70px of the two cells. if we can trim the
size-code so it says:
5.5K (or 5.5Kib) and not: 5.5 Kib
we can skip the width all together so it should scale.

Well, from what others and I've tried we better off with images + ALT tags. it simply doesn't worth the effort, which is not clear if it's going to lead anywhere.


So we have images of the same style for the search button, src/pdf and
prev/next navigation.


i say go with (em'ed) text (apart from the search button)


maybe i missed something: do we want the button to look like a system button or our own design? do we want the button to look like a button at all or could it be looking just like plain clickable text?

Allan, give me a few minutes. Let me try to commit some stuff and then we will discuss whether it's good or not, OK?


Also I'm considering to put the real 'next' and 'prev' and 'up' titles
into the ALT tags, as in ALT="prev: developers guide", etc.


+1




--


_____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/


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



Reply via email to