gramps

Note:  when I view the example site using FF v2.0.0.12 on 64-bit
Ubuntu 7.10, it does not come up with Nebraska as the default
stylesheet.  Each page I view, I have to click on View->Page
Style->Nebraska.

Just mentioning it for those of you wanting a quick view of what Jason has done.

(By default it looks like it comes up in Modern/GRAMPS style.)

Stéphane


On Feb 17, 2008 2:03 PM, Jason Simanek <jsimanek@...> wrote:
> Hello,
>
> I have finally prepared a working example of my updated NarrativeWeb.py
> script output as well as my Nebraska CSS stylesheet, an updated
> rendition of the Modern CSS stylesheet and a default Print CSS
> stylesheet.
>
> http://bohemianalps.com/GRAMPS/index.html
>
> I was going to build a test database, but that would take too long.
> Maybe in the future. For now, this is my complete database, so please be
> kind to my personal information.
>
> I took advantage of the 'alternate stylesheet' option in XHTML so that
> you can review these three stylesheets without going to different sites.
> I exported it with the Modern stylesheet as default, but you can pick
> and choose between the others. All of the existing stylesheets are there
> too, but I have only worked with the three specified above. Here's how
> to switch stylesheets:
>
> Firefox
> Main Menu/View/Page Style
>
> Konqueror
> Main Menu/View/Use Stylesheet
>
> Opera
> Main Menu/View/Style (and go all the way to the bottom)
> Toolbar/Author mode (and go all the way to the bottom)
>
> Safari and Internet Explorer
> (From what I know, you can't do this with these browsers. Maybe in
> IE7...)
>
> If you aren't familiar with media-specific stylesheets:
> http://www.w3.org/TR/REC-CSS2/media.html
>
> Basically, the Print stylesheet would only be used if you try to print a
> page from the site. However, for this example, I have also set the Print
> stylesheet as an alternate so that you can view it on-screen.
>
> If you have it, Konqueror is pretty slick since it keeps the stylesheet
> you choose active until you change it again. The other browsers keep
> flipping back to the default style sheet every time you go to a new
> page.
>
> I hope you find my version of the Modern Style a refreshing update.
> Also, the print stylesheet is focused on a classy and efficient printed
> presentation. The Nebraska style feels a little inflated, but it is easy
> on the eyes and I think will be good for older viewers as well.
>
> Let me know what you think,
>
> Jason Simanek
>
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Gramps-devel mailing list
> Gramps-devel@...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

On Sun, 2008-02-17 at 14:25 -0800, Stéphane Charette wrote:
> Note:  when I view the example site using FF v2.0.0.12 on 64-bit
> Ubuntu 7.10, it does not come up with Nebraska as the default
> stylesheet.  Each page I view, I have to click on View->Page
> Style->Nebraska.

Stephane, sorry about that. My email got a bit long and might be
confusing. There was just so much to say!

I didn't want to take for granted that everyone here knows how to choose
alternate stylesheets. As I said, Konqueror seems to work as expected in
that when you choose a different stylesheet it retains that change from
page to page.

Also, please keep in mind that some of the big changes have to do with
the markup more than the styling. Here are some key points of interest:

1
Navigation: Now the navigation item that represents the current section
you are viewing has the id="CurrentSection", allowing for the navigation
to provide more feedback to the user.

2
Gallery detail page: the Previous/Next links can easily be styled to
resemble buttons.

3
Depending on the situation, ordered lists are used in place of tables,
specifically with reference lists and the pedigree list on an
individual's page.

4
Ancestor Tree on Individual's page: With CSS the tree now has some hover
features with Nebraska and my interpretation of the Modern styles. IE of
course doesn't handle it well.

> (By default it looks like it comes up in Modern/GRAMPS style.)

That's correct. Please review that also, since it is actually a
completely new stylesheet that I wrote in attempt to retain the primary
character of the existing Modern style while improving the design and
adapting it for the new features of the updated markup.

-Jason

Looks great.
I'd say, attach it to the bug ticket and send reminder to Brian, so he can
go over it and commit it.
Looks like a great addition, so it should be added now so as to get optimal
testing before release of 3.0

Benny

2008/2/18, Jason Simanek <jsimanek@...>:
>
>
> On Sun, 2008-02-17 at 14:25 -0800, Stéphane Charette wrote:
> > Note:  when I view the example site using FF v2.0.0.12 on 64-bit
> > Ubuntu 7.10, it does not come up with Nebraska as the default
> > stylesheet.  Each page I view, I have to click on View->Page
> > Style->Nebraska.
>
> Stephane, sorry about that. My email got a bit long and might be
> confusing. There was just so much to say!
>
> I didn't want to take for granted that everyone here knows how to choose
> alternate stylesheets. As I said, Konqueror seems to work as expected in
> that when you choose a different stylesheet it retains that change from
> page to page.
>
> Also, please keep in mind that some of the big changes have to do with
> the markup more than the styling. Here are some key points of interest:
>
> 1
> Navigation: Now the navigation item that represents the current section
> you are viewing has the id="CurrentSection", allowing for the navigation
> to provide more feedback to the user.
>
> 2
> Gallery detail page: the Previous/Next links can easily be styled to
> resemble buttons.
>
> 3
> Depending on the situation, ordered lists are used in place of tables,
> specifically with reference lists and the pedigree list on an
> individual's page.
>
> 4
> Ancestor Tree on Individual's page: With CSS the tree now has some hover
> features with Nebraska and my interpretation of the Modern styles. IE of
> course doesn't handle it well.
>
> > (By default it looks like it comes up in Modern/GRAMPS style.)
>
> That's correct. Please review that also, since it is actually a
> completely new stylesheet that I wrote in attempt to retain the primary
> character of the existing Modern style while improving the design and
> adapting it for the new features of the updated markup.
>
> -Jason
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Gramps-devel mailing list
> Gramps-devel@...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

>
> > (By default it looks like it comes up in Modern/GRAMPS style.)
>
> That's correct. Please review that also, since it is actually a
> completely new stylesheet that I wrote in attempt to retain the primary
> character of the existing Modern style while improving the design and
> adapting it for the new features of the updated markup.
>
> -Jason
>

Jason, on the Ancestor chart, see
http://bohemianalps.com/GRAMPS/ppl/t/s/TSA7AEGCA91GYQNGVV.html mouse
over doesn't have good results for the GRAMPS style. It works fine
when using Nebraska stylesheet. I think GRAMPS css has no background
color and therefore the lines interfere with the text.

Raphael

On Mon, 2008-02-18 at 10:04 +0100, Raphael Ackermann wrote:
> Jason, on the Ancestor chart, see
> http://bohemianalps.com/GRAMPS/ppl/t/s/TSA7AEGCA91GYQNGVV.html mouse
> over doesn't have good results for the GRAMPS style. It works fine
> when using Nebraska stylesheet. I think GRAMPS css has no background
> color and therefore the lines interfere with the text.

Thanks Raphael. I corrected that issue and updated the example site
also.

-Jason

On Mon, 2008-02-18 at 09:38 +0100, Benny Malengier wrote:
> Looks great.
> I'd say, attach it to the bug ticket and send reminder to Brian, so he
> can go over it and commit it.
> Looks like a great addition, so it should be added now so as to get
> optimal testing before release of 3.0

Okay Benny, just a few things:

1
Should I finish updating the rest of the stylesheets before I do this?

2
What exactly does 'attach it to the bug ticket' mean? :D Remember, I'm
not a programmer by trade. Subversion and bug trackers are new to me.
Should I submit my changes via Subversion and then add the version
number to the bug tracker?

Thanks. I'm finally 'getting' Subversion as far as checking out versions
and updating to the most recent versions. It really takes first hand
experience to truly understand how version control works.

-Jason

2008/2/19, Jason Simanek <jsimanek@...>:
>
>
> On Mon, 2008-02-18 at 09:38 +0100, Benny Malengier wrote:
> > Looks great.
> > I'd say, attach it to the bug ticket and send reminder to Brian, so he
> > can go over it and commit it.
> > Looks like a great addition, so it should be added now so as to get
> > optimal testing before release of 3.0
>
> Okay Benny, just a few things:
>
> 1
> Should I finish updating the rest of the stylesheets before I do this?


Well, you should only add stuff centrally if nothing is broken anymore. So
yes, the patch should be complete.

2
> What exactly does 'attach it to the bug ticket' mean? :D Remember, I'm
> not a programmer by trade. Subversion and bug trackers are new to me.
> Should I submit my changes via Subversion and then add the version
> number to the bug tracker?


Is there no bug ticket about improving the narrative web css? If not, create
one.
To create a patch, do in the top dir of your checked out repo:

svn diff > narrativewebchanges.patch

This will create a patch file that the developer doing the commit can apply
with

patch -p0 <narrativewebchanges.patch

Thanks. I'm finally 'getting' Subversion as far as checking out versions
> and updating to the most recent versions. It really takes first hand
> experience to truly understand how version control works.
>
> -Jason
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Gramps-devel mailing list
> Gramps-devel@...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

On Mon, 2008-02-18 at 20:30 -0600, Jason Simanek wrote:
> On Mon, 2008-02-18 at 09:38 +0100, Benny Malengier wrote:
> > Looks great.
> > I'd say, attach it to the bug ticket and send reminder to Brian, so he
> > can go over it and commit it.
> > Looks like a great addition, so it should be added now so as to get
> > optimal testing before release of 3.0
Another reason to have this committed is that then others can help with
small adjustments to the markup and start seeing what they can do with
other style sheets. I'll certainly start playing with it.

I have one small suggestion: what about the URL of the originating
website in the print view? It can just be hidden in the other
stylesheets.

Duncan

On Thu, Feb 21, 2008 at 1:24 PM, Duncan Lithgow <dlithgow@...> wrote:

> Another reason to have this committed is that then others can help with
> small adjustments to the markup and start seeing what they can do with
> other style sheets. I'll certainly start playing with it.
>

Right. That sounds great. I'll try to submit my changes and note it on the
bug tracker listing that I made this morning.

I have one small suggestion: what about the URL of the originating
> website in the print view? It can just be hidden in the other
> stylesheets.


I'm not sure I understand. Are you  asking  to have the URL of the
originating website displayed in the Print Style? One of the things I did do
with the Print Style was to display the URL after all hyperlinks (I hid them
in some of the tables because it got way too busy). If that's what you want,
I'll have to think about how the originating URL will be known. I guess it
could be entered in the Narrative Web dialog, if it isn't already.

Let me know if that's what you meant.

-Jason

On Thu, 2008-02-21 at 13:48 -0600, Jason Simanek wrote:
>         
> 
> I'm not sure I understand. Are you  asking  to have the URL of the originating website displayed in the Print Style? One of the things I did do with the Print Style was to display the URL after all hyperlinks (I hid them in some of the tables because it got way too busy). If that's what you want, I'll have to think about how the originating URL will be known. I guess it could be entered in the Narrative Web dialog, if it isn't already.
I can see how that might be a problem...

I'm thinking that a piece of paper with useful information on can lose
it's context if it doesn't record where it came from. In this case the
address of the website. It's useless information while I look at the
website, but very useful if I post something I've printed to a friend.

Does that make more sense?

But I can now see this is not so easy, isn't there some way to do it
with an HTTP meta tag? I think I might have seen that once - don't know
where...

Duncan

>  I'm thinking that a piece of paper with useful information on can lose
>  it's context if it doesn't record where it came from. In this case the
>  address of the website. It's useless information while I look at the
>  website, but very useful if I post something I've printed to a friend.


I don't understand this.  The URL is printed or not depending on the
browser page settings, not CSS.  For example, in Firefox, I click on:

    File -> Page Setup -> Margins & Header/Footer

...then at the bottom of that notebook tab I click to select where I
want the URL, date/time, page # to be printed.

Is this what you're looking for?

Stéphane

On Thu, Feb 21, 2008 at 4:28 PM, Stéphane Charette <
stephanecharette@...> wrote:

> I don't understand this.  The URL is printed or not depending on the
> browser page settings, not CSS.  For example, in Firefox, I click on:


>    File -> Page Setup -> Margins & Header/Footer


> ...then at the bottom of that notebook tab I click to select where I
> want the URL, date/time, page # to be printed.
>


Yes, there are definitely ways the user can help themselves in this matter.
I don't know how much responsibility we want to take for this. In terms of a
point of reference, the site creator's information (such as that info listed
on the Contact page) could be included inside the site footer that is on
every page along with the copyright line.

I guess we should look at the site as being a published document and the
footer could contain a bibliographic reference to the author/publisher. This
way the extent of information provided would be up to the author/publisher.

Any thoughts?

On 21/02/2008, Jason Simanek <jsimanek@...> wrote:>
> Yes, there are definitely ways the user can help themselves in this matter.
> I don't know how much responsibility we want to take for this. In terms of a
> point of reference, the site creator's information (such as that info listed
> on the Contact page) could be included inside the site footer that is on
> every page along with the copyright line.
>
> I guess we should look at the site as being a published document and the
> footer could contain a bibliographic reference to the author/publisher. This
> way the extent of information provided would be up to the author/publisher.
That seems perfectly reasonable for all of us on this list. But I'm
still wondering if this is the best thing to do when a number of
GRAMPS users are not that computer literate.

What about a pre selected option to automatically populating the
footer with user info from the database owner information? That way
anyone who's not too concerned with such technical details will get a
sensible reference note at the bottom.

Duncan

On Fri, Feb 22, 2008 at 5:34 AM, Duncan Lithgow <dlithgow@...> wrote:

> What about a pre selected option to automatically populating the
> footer with user info from the database owner information? That way
> anyone who's not too concerned with such technical details will get a
> sensible reference note at the bottom.


I think that's what I had in mind. Isn't that how the current 'Contact' page
works? I'm not at my home computer right now to check, but whatever data
gets thrown in the Contact  page might as well be in fine print on the
footer also.

-Jason

On Fri, 2008-02-22 at 14:49 -0600, Jason Simanek wrote:


> I think that's what I had in mind. Isn't that how the current 'Contact' page works? I'm not at my home computer right now to check, but whatever data gets thrown in the Contact  page might as well be in fine print on the footer also.
something like that seems like a good idea.

duncan