From: Rob H. <rob...@gm...> - 2011-02-07 21:03:46
|
Dear Allan: I know that you know it is in the CSS... CSS when it is used properly will define everything that a web page will look like and its formatting as well! What is the page name that you are referencing about? Please send all of the comments such as this to me... It is my job here at Gramps to be in charge of NarrativeWeb, WebCal, and my addon, Image Metadata Gramplet! Now, yes, anyone can edit and fix any file in the Gramps repository, but unless Jason Simanek can come back, it is on my shoulders... Now, I am not trying to chide you ... just for your information is all... Sincerely yours, Rob G. Healey On Mon, Feb 7, 2011 at 12:42 PM, Allan Topp <ad...@nc...> wrote: > I am using what used to be Web-Nebraska colours in the Narrative Web > Report and am finding that url links show up (well actually don't) as > white text in Google Chrome - making them well nigh impossible to see - > but as brown in Firefox. > > Anyone know where the problem is here? And, much more importantly, how > to fix it? > > TIA > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Benny M. <ben...@gm...> - 2011-02-09 12:55:54
|
I tested with trunk and chromium browser (not latest chrome !). I see no problem with links, all are brown. Note that you can set a preference for links to override css, I hope that is not the case. You can change things yourself in the file narwebdir/styles/narrative-screen.css The problem might be the following. The css file contains p a { color:#FFF; text-decoration:underline; } and a { color:#542; } a:visited { color:#542; } So, a is the element for links and #FFF is white, so this would indicate the links must be in white. However, later we set the a element to #542 which is dark brown, so this should take precedence I believe. Please change the #FFF into #542 and see if that fixes chrome white links. Rob, if above is the case, can you explain it? 2011/2/7 Rob Healey <rob...@gm...> > Dear Allan: > > I know that you know it is in the CSS... > > CSS when it is used properly will define everything that a web page will > look like and its formatting as well! > > What is the page name that you are referencing about? Please send all of > the comments such as this to me... It is my job here at Gramps to be in > charge of NarrativeWeb, WebCal, and my addon, Image Metadata Gramplet! > > Now, yes, anyone can edit and fix any file in the Gramps repository, but > unless Jason Simanek can come back, it is on my shoulders... > > Now, I am not trying to chide you ... just for your information is all... > > Sincerely yours, > Rob G. Healey > > > > On Mon, Feb 7, 2011 at 12:42 PM, Allan Topp <ad...@nc...> wrote: > >> I am using what used to be Web-Nebraska colours in the Narrative Web >> Report and am finding that url links show up (well actually don't) as >> white text in Google Chrome - making them well nigh impossible to see - >> but as brown in Firefox. >> >> Anyone know where the problem is here? And, much more importantly, how >> to fix it? >> >> TIA >> >> >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: Rob H. <rob...@gm...> - 2011-02-09 21:23:45
|
Dear Benny and Allan: Something like this: a { color: #542; text-decoration: none; } is a global element. It defines the hyper links for the entire website... To be dark brown and have no underline Something like this: p#description { color: Green; } p#description a { color: #FFF; } is a more specific global element... It handles all instances of text that is like: <p id="Description"> Today, we will sign the <a href="http://www.declaration.org">"Declaration"</a> of independence. </p> * the word Declaration would be white in this instance and the rest of the text would be Green * this example could be anyway in the web pages... Now, something like: div#navigation ul li.CurrentSection a { color: #453619; } would say that hyper links in the navigation bar of current highlighted menu option would be darkest brown,, and look something like and can be in any navigation bar in the pages <div id="navigation"> <ul> <li class="CurrentSection"> <a href="index.html">"Index"</a> </li> </ul> </div> We can use this idea for one more example: div#SourceDeatil #navigation ul li.CurrentSection a { color: #000; text-decoration: underline; } would look like this: <div id = "SourceDetail"> <div id="navigation"> <ul> <li class="CurrentSection"> <a href="index.html">"Index"</a> </li> </ul> </div> </div> * this defines that only the navigation bar in the SourceDetail page will have highlighted CurrentSection hyper links to be black colored and underlined ... I have taken this from a very general element to a very specific element... There is so much that can be done with CSS! I have only scratched the little toes of what can be done! Sincerely yours, Rob G. Healey On Wed, Feb 9, 2011 at 4:55 AM, Benny Malengier <ben...@gm...>wrote: > I tested with trunk and chromium browser (not latest chrome !). I see no > problem with links, all are brown. > > Note that you can set a preference for links to override css, I hope that > is not the case. > > You can change things yourself in the file > narwebdir/styles/narrative-screen.css > > The problem might be the following. The css file contains > > p a { > color:#FFF; > text-decoration:underline; > } > > and > > a { > color:#542; > } > a:visited { > color:#542; > } > > So, a is the element for links and #FFF is white, so this would indicate > the links must be in white. > > However, later we set the a element to #542 which is dark brown, so this > should take precedence I believe. > Please change the #FFF into #542 and see if that fixes chrome white links. > > Rob, if above is the case, can you explain it? > > 2011/2/7 Rob Healey <rob...@gm...> > >> Dear Allan: >> >> I know that you know it is in the CSS... >> >> CSS when it is used properly will define everything that a web page will >> look like and its formatting as well! >> >> What is the page name that you are referencing about? Please send all of >> the comments such as this to me... It is my job here at Gramps to be in >> charge of NarrativeWeb, WebCal, and my addon, Image Metadata Gramplet! >> >> Now, yes, anyone can edit and fix any file in the Gramps repository, but >> unless Jason Simanek can come back, it is on my shoulders... >> >> Now, I am not trying to chide you ... just for your information is all... >> >> Sincerely yours, >> Rob G. Healey >> >> >> >> On Mon, Feb 7, 2011 at 12:42 PM, Allan Topp <ad...@nc...> wrote: >> >>> I am using what used to be Web-Nebraska colours in the Narrative Web >>> Report and am finding that url links show up (well actually don't) as >>> white text in Google Chrome - making them well nigh impossible to see - >>> but as brown in Firefox. >>> >>> Anyone know where the problem is here? And, much more importantly, how >>> to fix it? >>> >>> TIA >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> http://p.sf.net/sfu/intel-dev2devfeb >>> _______________________________________________ >>> Gramps-users mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>> >> >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> > |
From: Benny M. <ben...@gm...> - 2011-02-10 08:19:04
|
2011/2/9 Rob Healey <rob...@gm...> > > I have taken this from a very general element to a very specific element... > > There is so much that can be done with CSS! I have only scratched the > little toes of what can be done! Rob, My question is if the global element with color #FFF is not a bug in the gramps css. It seems allan has white links in a certain version of chrome, so something is going wrong. I certainly see no reason to have the general element in white if 1/the general element is not used 2/white is not a good color. Benny |
From: Rob H. <rob...@gm...> - 2011-02-10 08:49:24
|
Dear Benny: I would need to see his version of the style sheet that he is using to see what and where things go to white links... I will ask him for the style sheet, so that i may look at Chrome to see what he is possibly seeing... Sincerely yours, Rob G. Healey On Thu, Feb 10, 2011 at 12:18 AM, Benny Malengier <ben...@gm... > wrote: > > > 2011/2/9 Rob Healey <rob...@gm...> > >> >> I have taken this from a very general element to a very specific >> element... >> >> There is so much that can be done with CSS! I have only scratched the >> little toes of what can be done! > > > Rob, > > My question is if the global element with color #FFF is not a bug in the > gramps css. It seems allan has white links in a certain version of chrome, > so something is going wrong. I certainly see no reason to have the general > element in white if 1/the general element is not used 2/white is not a good > color. > > Benny > > |
From: Benny M. <ben...@gm...> - 2011-02-10 08:59:30
|
2011/2/10 Rob Healey <rob...@gm...> > Dear Benny: > > I would need to see his version of the style sheet that he is using to see > what and where things go to white links... > > I will ask him for the style sheet, so that i may look at Chrome to see > what he is possibly seeing... > > Rob, if you generate a Nebraska narweb in trunk (and I assume branch32), and open the css, you see that section. My question is in itself not connected to the problem Allen has. Even if it is a bug in chrome, using #FFF in the css might be a wrong thing. Benny > Sincerely yours, > Rob G. Healey > > > On Thu, Feb 10, 2011 at 12:18 AM, Benny Malengier < > ben...@gm...> wrote: > >> >> >> 2011/2/9 Rob Healey <rob...@gm...> >> >>> >>> I have taken this from a very general element to a very specific >>> element... >>> >>> There is so much that can be done with CSS! I have only scratched the >>> little toes of what can be done! >> >> >> Rob, >> >> My question is if the global element with color #FFF is not a bug in the >> gramps css. It seems allan has white links in a certain version of chrome, >> so something is going wrong. I certainly see no reason to have the general >> element in white if 1/the general element is not used 2/white is not a good >> color. >> >> Benny >> >> > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |