David,

     Great work on the new manual.  I like this version.  I was in the
middle of typing
up a response to the original email, when I got the email about the update
you've done.

      Using margin-right and margin-left in the body { } in style.css might
be a good idea
along with percentage values.  This will allow it to be more readable on a
mobile device
as well.  It could stay centred but slightly wider margins so more of the
real-estate is
taken up by the body rather than blank space.

      Other than that, I like this second version better.


cheers,

     mehul




On Thu, Sep 11, 2014 at 11:06 AM, David Bjergaard <dbjerga...@gmail.com>
wrote:

> I've fixed some of the things outlined below, you've always got the
> option to "View > Page Style > No Page Style" in firefox.  I'm not sure
> what the chrome invocation is.
>
> More feedback is definitely welcome! Its really nice to hear that people
> are benefiting from my work (even if I don't get it right the first
> time).
>
>     Dave
>
>
> David Bjergaard <dbjerga...@gmail.com> writes:
>
> > Scott Jaderholm <jaderh...@gmail.com> writes:
> >
> >> But I liked the garish look :(
> >>
> >> I thought I'd share a few of my reasons why just so you can be aware.
> >> I realize these are very subjective and people will disagree about
> >> them. I'm not trying to argue that I'm right and anyone else should
> >> agree with me. I'm totally fine with it looking the way you like since
> >> you've been putting in the work. I can always use my own stylesheet.
> >> These are just FYIs.
> >>
> >> - I like the way links look in the old version. It's obvious what is a
> >> link and what isn't a link without hovering over the text. Blue and
> >> purple texts are links. I also like how much clearer it is what links
> >> you've already visited--they're purple. In your version the contrast
> >> between visited and not-visited is very slight.
> > I take your point, and will update the colors. (Though probably not back
> > to the default colors).
> >
> >> - I don't like the all caps. I find it harder to read. I find it
> >> particularly annoying on the table of contents where you want to be
> >> able to scan the sections quickly and identify which might relate to
> >> your issue.
> > Again, I take your point, I was experimenting.
> >> - I don't like how it's centered and narrow. I often read at 300% zoom
> >> (when far away from my screen, admittedly not the typical use case)
> >> and I like how the old one filled the window correctly at varying zoom
> >> levels. I realize that at 100% zoom with a wide window the old version
> >> would create very long lines. This didn't bother me, but I can
> >> understand that it would bother other people.
> > Unfortunately (unless many others complain) I won't change this one.
> >> - If there's a way to make Contents be in the same font as TOP and
> >> INDEX that would be nice :)
> > The old manual is still up (though outdated and won't be updated). Also,
> > you can always read the manual from emacs with the info page created.
> >
> > I don't want to sound pessimistic, I'm very glad for your feedback.
> >
> >     Dave
>
> _______________________________________________
> Stumpwm-devel mailing list
> Stumpwm-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
>



-- 
Mehul N. Sanghvi
email: mehul.sang...@gmail.com
_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/stumpwm-devel

Reply via email to