[opensuse-wiki] New wiki skin - help/feedback needed
Hi, I finally managed to get the new skin working! Adrian and Darix set up a test server, so you can test it under almost real-life terms! http://en.test.opensuse.org/ The skin was completely written from scratch, so it is no longer based on MonoBook or other existing MediaWiki styles. This made the skin development a bit picky, because there is no longer a Fallback css (like MonoBook) that covers styles not in the openSUSE css. This is where I need your help - please test all Special pages on the wiki you can think of, generate and apply templates, upload files ... in short stress-test the skin and tell me what I have missed. To make it easier for you, I have already put together some pages showcasing tag formatting, structural and content elements as well as links to the most commonly used Special pages. Two pages are of special interest: Styles Not Defined Yet: This is a list of styles MediaWiki generates that I have not covered, yet, because I wasn't able to find out on which pages they are used. Maybe you can help me here. Content Elements: I am planning to add useful classes to the CSS, like the command-line style (.shell). Please add whatever you find useful to this page (with inline css) and discuss them on this list. I will add the ones we all agree upon. The "this page in other languages" stuff is currently not working - I hope to be able to fix this soon. If a page exists in other languages, you will either see a drop down box in the gray page header (where the edit, discussion links are) - requires JavaScript - or an additional box in the left nav when JavaScript is disabled. Thanks for all your feedback in advance! Don't expect to hear from me until Thursday, 31 - I will be online very rarely until then. -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Reality is always controlled by the people who are most insane" Dogbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Thursday 24 May 2007 12:07, Frank Sundermeyer wrote:
Hi,
I finally managed to get the new skin working! Adrian and Darix set up a test server, so you can test it under almost real-life terms!
The skin was completely written from scratch, so it is no longer based on MonoBook or other existing MediaWiki styles. This made the skin development a bit picky, because there is no longer a Fallback css (like MonoBook) that covers styles not in the openSUSE css.
This is where I need your help - please test all Special pages on the wiki you can think of, generate and apply templates, upload files ... in short stress-test the skin and tell me what I have missed.
To make it easier for you, I have already put together some pages showcasing tag formatting, structural and content elements as well as links to the most commonly used Special pages.
Two pages are of special interest:
Styles Not Defined Yet: This is a list of styles MediaWiki generates that I have not covered, yet, because I wasn't able to find out on which pages they are used. Maybe you can help me here.
Content Elements: I am planning to add useful classes to the CSS, like the command-line style (.shell). Please add whatever you find useful to this page (with inline css) and discuss them on this list. I will add the ones we all agree upon.
The "this page in other languages" stuff is currently not working - I hope to be able to fix this soon. If a page exists in other languages, you will either see a drop down box in the gray page header (where the edit, discussion links are) - requires JavaScript - or an additional box in the left nav when JavaScript is disabled.
Thanks for all your feedback in advance! Don't expect to hear from me until Thursday, 31 - I will be online very rarely until then. I just went to the test wiki site and for some reason the green text and art turn shades of green and yellow as I move up and down. It was so visually erating that I had to stop and tell you. sorry for the negative first comment. I'm on an IBM r51 with 15.4 lcd \ openSUSE 10.2 KDE -- James Tremblay Director of Technology Newmarket School District Novell CNE 3\4\5 CLE \ NCE in training. http://en.opensuse.org/education
To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Thursday 24 May 2007 18:37, James Tremblay wrote: Hi,
I just went to the test wiki site and for some reason the green text and art turn shades of green and yellow as I move up and down. It was so visually erating that I had to stop and tell you. sorry for the negative first comment. I'm on an IBM r51 with 15.4 lcd \ openSUSE 10.2 KDE
sorry, but I was not able to verify that on any computer/monitor/operating system I tested the skin. Does this only happen with the new skin? Does it happen in a particular browser only or on different browsers? -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Reality is always controlled by the people who are most insane (Dogbert) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Friday 25 May 2007 08:12, Frank Sundermeyer wrote:
On Thursday 24 May 2007 18:37, James Tremblay wrote:
Hi,
I just went to the test wiki site and for some reason the green text and art turn shades of green and yellow as I move up and down. It was so visually erating that I had to stop and tell you. sorry for the negative first comment. I'm on an IBM r51 with 15.4 lcd \ openSUSE 10.2 KDE
sorry, but I was not able to verify that on any computer/monitor/operating system I tested the skin. Does this only happen with the new skin? Does it happen in a particular browser only or on different browsers?
I haven't tested it with anything other than firefox and it only happens on the test site. Is the shade of green you are using some custom color because the green looks different on the main page than on yours. is it possible my color pallette could be effecting it? -- James Tremblay Director of Technology Newmarket School District Novell CNE 3\4\5 CLE \ NCE in training. http://en.opensuse.org/education --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Thursday 24 May 2007 18:37, James Tremblay wrote:
Hi,
I just went to the test wiki site and for some reason the green text and art turn shades of green and yellow as I move up and down. It was so visually erating that I had to stop and tell you. sorry for the negative first comment. I'm on an IBM r51 with 15.4 lcd \ openSUSE 10.2 KDE
sorry, but I was not able to verify that on any computer/monitor/operating system I tested the skin. Does this only happen with the new skin? Does it happen in a particular browser only or on different browsers?
On Friday 25 May 2007 08:12, Frank Sundermeyer wrote: p.s. the geeko on the top does not do it. -- James Tremblay Director of Technology Newmarket School District Novell CNE 3\4\5 CLE \ NCE in training. http://en.opensuse.org/education --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Frank Sundermeyer wrote:
Hi,
I finally managed to get the new skin working! Adrian and Darix set up a test server, so you can test it under almost real-life terms!
the first look is very good I tested the === === subtitles on the discussion main page (feel free to erase) * may be the difference is a little too small between them. We could have a little more difference in size, say for the first three and then use plain standard black color I notice the login is no more the Novell one, I suppose this is only for the test? I don't really understand the difference between relative and recent change. I know there was a thread on this subject, but a one line explain should be nice :-) the "home" box seems misnamed, better could be "services", for example with "wiki" replaced by "Community wiki" I work also with pmwiki, and standard edit boxes of this wiki have a small (5/6 lines) of edit tags remainder below the edit window, we could do the same (example http://www.pmwiki.org/wiki/PmWiki/PmWiki?action=edit) jdd -- http://www.dodin.net http://gourmandises.orangeblog.fr/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
jdd wrote:
Frank Sundermeyer wrote:
Hi,
I finally managed to get the new skin working! Adrian and Darix set up a test server, so you can test it under almost real-life terms!
I just found on the net a page (http://www.lea-linux.org/cached/index/Admin-admin_env-sudo.html) where a code window can have a fixed heigth (search for "Voilà mon /etc/sudoers :" on the page, the box is there) this is very handy and it's a mediawiki... jdd -- http://www.dodin.net http://gourmandises.orangeblog.fr/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Hello, on Donnerstag, 24. Mai 2007, jdd wrote:
jdd wrote:
Frank Sundermeyer wrote:
Hi,
I finally managed to get the new skin working! Adrian and Darix set up a test server, so you can test it under almost real-life terms!
I just found on the net a page (http://www.lea-linux.org/cached/index/Admin-admin_env-sudo.html) where a code window can have a fixed heigth (search for "Voilà mon /etc/sudoers :" on the page, the box is there)
this is very handy and it's a mediawiki...
Without having looked to the CSS, I guess it's styled with max-height: 15em; overflow:auto; However I'm not sure if this is a good idea - just imagine someone puts a meeting transcript in such a box :-/ OK, that's what I would use as standard. Now let's try to make it more flexible. What would be useful? IMHO: Having overflow:auto as optional style like <pre class='scrollable'> would be an option. It would also be nice to have a class for horicontal scrolling also (overflow-x:auto;) which could be used on long code lines. (But not for code blocks with many lines - the whole block must fit on the screen in this case. And another class with "normal" (sans-serif, not monospaced) font would be very useful for meeting transcripts, because it reduces the need to manually insert linebreaks ;-) Regards, Christian Boltz -- | Yes, I know. But there are even conjobs running as user games? Sometimes when cron is bored he starts playing games, didn't you know? ;-) [Aschwin Marsman and Robert Schiele opensuse] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Thursday 24 May 2007 19:57, jdd wrote: Hi,
I notice the login is no more the Novell one, I suppose this is only for the test?
yes.
I don't really understand the difference between relative and recent change. I know there was a thread on this subject,
This was the reason I added "Recent changes"
but a one line explain should be nice :-)
When you call Related Changes from a page, it only lists pages that page links to: http://en.opensuse.org/index.php?title=Special:Recentchangeslinked&target=Contact&hideminor=0&days=30&limit=50 http://en.opensuse.org/Contact links to "How to Participate" and "Template:IW", so it will only list changes on these two pages (provided changes exist) Recent changes will list all site-wide changes.
the "home" box seems misnamed, better could be "services", for example with "wiki" replaced by "Community wiki"
Perhaps we should name the "Home" box "openSUSE" and rename the existing openSUSE box... -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Reality is always controlled by the people who are most insane (Dogbert) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On 5/24/07, Frank Sundermeyer <fs@suse.de> wrote:
Hi,
I finally managed to get the new skin working! Adrian and Darix set up a test server, so you can test it under almost real-life terms!
The skin was completely written from scratch, so it is no longer based on MonoBook or other existing MediaWiki styles.
Wow, that must've been quite some work =). A few ideas/thoughts: * For the top navigation/login, I really don't think it should be enclosed by bars; bars should only be used to separate options. i.e. | My contributions | Log out | ...should be: My contributions | Log out * The non-exiting page link colour reads awkwardly on the green background; too contrasting. i.e. such as | Apokryphos | My talk | * Could there really not be perhaps a lighter hint of anchor tags for a:hover? Some interaction is nice. * Not sure if this is relevant to mention here (if not just ignore), but could we do something about the navigation options on the left? There's way too many entries I think, so it just gets confusing. How about removing (from the "openSUSE" section) Home (I think Geeko linking to home is intuitive; all other sites handle it similarly) and Download+Build Service (link already above), and removing the whole "Participation" section and instead just linking to a single wiki page which has all the information on how to participate? * Could the content-table have some type of Geeko-image styling? Fedora one springs to mind, which is quite nice: http://fedoraproject.org/wiki/Docs * Is the footer perhaps too large? Would combining two of the lines of text be a possibility? * I'm also wondering if the grey boxes are just a little too light in contrast to the quite strong green? Could also partly be an issue if we think the box-outline isn't strong enough. * A few people I've spoken to just commented on the search box and buttons appearing a little out-of-place. Perhaps the rounded arc is a little too round? Indeed, there isn't anything else on the page that round, only slightly curved. * Perhaps something could also be done with the buttons displayed when editing an entry? They still have the taste of monobook (that style also appears elsewhere I see). All the special pages I looked at looked pretty good to me; really looking forward to this theme going live :) Kind thoughts, -- Francis Giannaros http://francis.giannaros.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On 2007-05-25 13:41:09 +0100, Francis Giannaros wrote:
A few ideas/thoughts: * For the top navigation/login, I really don't think it should be enclosed by bars; bars should only be used to separate options. i.e. | My contributions | Log out | ...should be: My contributions | Log out
that is the same code that puts the stuff there, depending whether you are logged in or not. you cant change that easily. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Thursday 24 May 2007 11:07, Frank Sundermeyer wrote:
Hi,
I finally managed to get the new skin working! Adrian and Darix set up a test server, so you can test it under almost real-life terms!
The skin was completely written from scratch, so it is no longer based on MonoBook or other existing MediaWiki styles. This made the skin development a bit picky, because there is no longer a Fallback css (like MonoBook) that covers styles not in the openSUSE css. ...
I like this. Additional structural and content elements will give a lot of formatting options. Though it will take time to learn to use them. Now the other: 1) The bar of buttons over the edit box is still the old mediawiki style. The Save, Show preview, Show changes below edit box looks much better. 2) Visited links don't change color on recent changes. 3) In http://en.test.opensuse.org/index.php?title=Midnight_commander block of code can't be highlighted using <code> and <div class="shell">, both are broken. To me it seems that both tags expect text to start from the first position in the line, if not than text is formatted as usual with a space in the first position ie. as <pre> tag. Please look in history of the article for examples. How long it will be online for testing? -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Saturday 26 May 2007 17:10, Rajko M. wrote: Hi,
3) In http://en.test.opensuse.org/index.php?title=Midnight_commander block of code can't be highlighted using <code> and <div class="shell">, both are broken.
works for me.
To me it seems that both tags expect text to start from the first position in the line, if not than text is formatted as usual with a space in the first position ie. as <pre> tag.
Yes, this is a feature - in wiki markup a space at the beginning of the line makes this line a <pre> text. http://www.mediawiki.org/wiki/Help:Formatting
How long it will be online for testing?
As long as we need it ;-) -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Reality is always controlled by the people who are most insane" Dogbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Hello, on Donnerstag, 24. Mai 2007, Frank Sundermeyer wrote:
http://en.test.opensuse.org/ [...] Styles Not Defined Yet: This is a list of styles MediaWiki generates that I have not covered, yet, because I wasn't able to find out on which pages they are used. Maybe you can help me here.
You can help yourself. Just define these styles with border: 5px solid red; background: red; and wait for bugreports ;-))
Content Elements: I am planning to add useful classes to the CSS, like the command-line style (.shell). Please add whatever you find useful to this page (with inline css) and discuss them on this list. I will add the ones we all agree upon.
I already mentioned some options for <pre> blocks in my last mail and just included them on the Content Elements Page (section "Proposals for <pre>")
The "this page in other languages" stuff is currently not working - I hope to be able to fix this soon.
If a page exists in other languages, you will either see a drop down box in the gray page header (where the edit, discussion links are) - requires JavaScript -
Can you add something like "--- other languages ---" as very first option? It should be selected by default instead of the first available language. This would make the meaning of the dropdown clear.
or an additional box in the left nav when JavaScript is disabled.
Nice usecase for <noscript> ;-)
Thanks for all your feedback in advance!
I was a bit late in checking and Francis and Rajko already found nearly all bugs I noticed ;-) and I can only highlight the most important things: - the contents box needs a better look, a background image like in the Fedora wiki would be a nice idea - grey boxes are too light-grey (nearly displayed as white on my laptop) A minor bug I just found is in the Content_Elements page, section ".center": The code looks like this: <span class="center">...Content...</div> -> Is <span> or <div> correct? Please fix the example ;-) A word about highlighting of links: - you can remove the underline (text-decoration:none) _as long as the link color differs from text color_ [1] or just allow the browser default in this case (no text-decoration statement) - a:hover should always be underlined - I don't really like the current style (underline non-visited links only by default) - please use different colors for visited links instead. Please read also my rants in the footnotes ;-) Regards, Christian Boltz [1] but you should _not_ define black font color for links and skip the text-decoration:underline. If you do this and someone (like me) has changed the browser defaults to display the underline only on :hover, searching for links is like searching for easter eggs. Unfortunately, this can be tested on *.novell.com :-( [2] [2] Yes, I have reported this, both via the feedback link (I got a "thanks for your hint", but nothing more) and via bugzilla https://bugzilla.novell.com/show_bug.cgi?id=141494 Basically I was told to change my browser settings there :-/ which isn't an option because usability of a website should never depend on the browser settings. [3] AFAIK there's a bugzilla component for the Novell website, but I don't have access to it. Can someone @SUSE please reopen the bug and reassign it to the Novell webmaster, please? [3] I also like to change the default colors to yellow background with violet font color - a good method to find undefined colors ;-) (BTW: The new openSUSE page passed this test :-) -- Ein gutes Logo ist wie ein Butler: Es ist immer da, wird aber nicht bemerkt. [Ratti] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Thursday 24 May 2007 11:07, Frank Sundermeyer wrote:
This is where I need your help - please test all Special pages on the wiki you can think of, generate and apply templates, upload files ... in short stress-test the skin and tell me what I have missed.
Sorry for hanging on this message, but for time being I don't receive emails from opensuse.org domain and if I want to follow the thread the simplest way is to use last message received. Related to previous post: Discovered what is difference between visited and not visited link. It is underscore, and it is not very intuitive. The intuition is based on previous experience and links usually change color. Just noticed on: http://en.test.opensuse.org/index.php?title=Special:Listusers http://en.test.opensuse.org/index.php?title=Midnight_commander that visiting link to page that opens for edit will change link color to some dark orange from dark red for not visited. http://en.test.opensuse.org/index.php?title=Special:Disambiguations Link to Template:Disambig is blue although template does not exist. It seems to be because template is not automatically opened for edit as it is on regular page http://en.test.opensuse.org/index.php?title=Midnight_commander http://en.test.opensuse.org/index.php?title=Special:Watchlist Not logged in gives this: "(for user "::ffff:<IP address here>") You have no items on your watchlist." It would do better message like: "You should be logged in to see your watch list." or not to show Special:Watchlist to users that are not logged in. http://en.test.opensuse.org/index.php?title=Special:Lonelypages Deserves some explanation what that means, like: "Orphaned pages are those that no other pages are linking to them. Under normal circumstances they should not exist." There is more special pages that need some explanation. Some examples: http://en.test.opensuse.org/index.php?title=Special:Uncategorizedcategories http://en.test.opensuse.org/index.php?title=Special:Booksources http://en.test.opensuse.org/index.php?title=Special:Deadendpages http://en.test.opensuse.org/index.php?title=Special:Statistics Gives: "Excluding those, there are ' pages that are probably legitimate content pages. There have been a total of ' page views, and ' page edits since the wiki was setup." Missing numbers. With or without being logged. http://en.test.opensuse.org/index.php?title=Special:Allpages It is a mess. Titles stick togheather. This seems to be css problem. It would be probably better to have simple list with one item per line where even long titles would fit in single line with more lines per page. I guess for that is responsible some function in Mediawiki. http://en.test.opensuse.org/index.php?title=Special:Protectedpages Nothing listed. With or without being logged. Freedom to play without messing the web site structure gives me idea that having a test server even when layout job is done would help to explore abilities of openSUSE on exact copy, without crowding main site. Last example would be test how to improve readability of subpage titles. See http://en.test.opensuse.org/index.php?title=Midnight_commander_/_t1 -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Hello, on Sonntag, 27. Mai 2007, Rajko M. wrote: [...] ACK on your mail, no need to quote most of it ;-) Just some notes:
Freedom to play without messing the web site structure gives me idea that having a test server even when layout job is done would help to explore abilities of openSUSE on exact copy, without crowding main site.
Yes, a place to do some tests is always useful. I'd also like to propose a wiki for new translations (that don't have an own wiki yet) to keep them out of the english wiki.
Last example would be test how to improve readability of subpage titles. See http://en.test.opensuse.org/index.php?title=Midnight_commander_/_t1
Yes, the additional space is a good thing in the page headline. But: The additional "_" make the URL looking odd and also make it harder to enter URLs manually. Conclusion: If we want the additional space around "/", it should be inserted on the server side (in the displayed headline), but *not* in the page title (URL). Regards, Christian Boltz -- mv ~/Hirn ~/Sieb [David Haller in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Sunday 27 May 2007 18:28, Rajko M. wrote: Hi,
Just noticed on: http://en.test.opensuse.org/index.php?title=Special:Listusers http://en.test.opensuse.org/index.php?title=Midnight_commander that visiting link to page that opens for edit will change link color to some dark orange from dark red for not visited.
yup, this is intended.
http://en.test.opensuse.org/index.php?title=Special:Disambiguations Link to Template:Disambig is blue although template does not exist.
Yes - MediaWiki does not generate a class="new" - don't know whether this is intentional or a bug.
http://en.test.opensuse.org/index.php?title=Special:Watchlist Not logged in gives this: "(for user "::ffff:<IP address here>") You have no items on your watchlist." It would do better message like: "You should be logged in to see your watch list." or not to show Special:Watchlist to users that are not logged in.
This page is auto-generated and I haven't found a way to change the text MediaWiki:Nowatchlist also applies to users that are logged in but do not watch pages.
http://en.test.opensuse.org/index.php?title=Special:Lonelypages Deserves some explanation what that means, like: "Orphaned pages are those that no other pages are linking to them. Under normal circumstances they should not exist."
MediaWiki:Lonelypages is a headline - there is no way to add normal text.
There is more special pages that need some explanation. Some examples: http://en.test.opensuse.org/index.php?title=Special:Uncategorizedcate gories http://en.test.opensuse.org/index.php?title=Special:Booksources http://en.test.opensuse.org/index.php?title=Special:Deadendpages
The same that was said on MediaWiki:Lonelypages goes for these pages as well.
http://en.test.opensuse.org/index.php?title=Special:Statistics Gives: "Excluding those, there are ' pages that are probably legitimate content pages. There have been a total of ' page views, and ' page edits since the wiki was setup." Missing numbers. With or without being logged.
Probably a setup error on the test wiki - nothing to worry about.
http://en.test.opensuse.org/index.php?title=Special:Allpages It is a mess. Titles stick togheather. This seems to be css problem.
and I haven't got a solution - please see my previous mail. Help is welcome.
http://en.test.opensuse.org/index.php?title=Special:Protectedpages Nothing listed. With or without being logged.
Because there are no protected pages on this wiki.
Freedom to play without messing the web site structure gives me idea that having a test server even when layout job is done would help to explore abilities of openSUSE on exact copy, without crowding main site. Last example would be test how to improve readability of subpage titles. See http://en.test.opensuse.org/index.php?title=Midnight_commander_/_t1
I go with Christian - this needs to be fixed in MediaWiki. Please feel free to file an enhancement request in the MediaWiki bugzilla http://en.wikipedia.org/wiki/Wikipedia:Bugzilla -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Reality is always controlled by the people who are most insane" Dogbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Thursday 24 May 2007 18:07, Frank Sundermeyer wrote: Hi,
I finally managed to get the new skin working! Adrian and Darix set up a test server, so you can test it under almost real-life terms!
thanks a lot for all your feedback. Here is a the list of changes you requested - if your change request is not listed here, please have a look at my forthcoming individual replies. Headlines: http://en.test.opensuse.org/index.php?title=Tag_Formatting#.3Ch1.3E....3Ch6.... Left Navigation: * first box renamed to "openSUSE" * former "openSUSE"-box renamed to "Discover it" (better suggestions welcome) * former "Participate" box removed Top Navigation/Login: * Removed enclosing "|" Non-existing Page Link Colour in Top Navigation: * Yes, it looks a bit awkward on green, but on the other hand I do not want to introduce a new "non-existing page" colour just for the top navigation - this would be confusing Link colors * a, a:hover, a:active: now dark blue * a:visited now light blue * a:hover now has got a dotted border (Colours will likely change again, these are just a draft) Footer: * I don't think we can remove text, nor does it make sense to combine two lines in one. Search Box: * I would prefer to leave the round corners (they are the same as the ones used for the boxes) Editing Page Buttons: * top (Editor functions): These cannot be changed - they are hardcoded * bottom (Save page etc.) looking forward for ideas to making them look less monoBook style - using an image as input type is not possible, because the HTML code is generated Content Table Background: * according to Novell brand guidelines the Geeko tail as well as the Geeko head should no longer be used, so I run out of background graphics matching the theme (and on the other hand I do not like copying Fedora ;) ). I have now changed the background to light green, but I am not sure whether this is better... Language selector (JavaScript): * Now with Headline msg('otherlanguages') Content Elements: I have added Christians <pre> proposals. http://en.test.opensuse.org/index.php?title=Special:Allpages * I have absolutely no idea why the tables do not use the whole page width - this is why the list of all pages is messed up. Unfortunately no special style is created on this page, so there is no workaround. Please help! -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Reality is always controlled by the people who are most insane" Dogbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On 5/31/07, Frank Sundermeyer <fs@suse.de> wrote:
* a:hover now has got a dotted border
I think it's good that there's a hover effect, but dotten lines should seriously be avoided. Bad nostalgia of the early 90s ;). Just a lighter blue would probably do the trick. Re: contents-table, I definitely think something still a little lighter for the contents-table is needed. With regard to branding, I thought the Geeko button head could still be used (reading opensuse.org/Artwork:Brand). Perhaps something like http://francis.giannaros.org/temp/content-table.png ? Site's going to be great; looking forward to the launch =) Kind thoughts, -- Francis Giannaros http://francis.giannaros.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Hello, on Donnerstag, 31. Mai 2007, Frank Sundermeyer wrote:
On Thursday 24 May 2007 18:07, Frank Sundermeyer wrote:
Headlines: http://en.test.opensuse.org/index.php?title=Tag_Formatting#.3Ch1.3E.. ..3Ch6.3E
<h6> looks smaller than normal text - I'm not sure if this is a good idea. (Not really a problem - is there really someone who needs <h6>?)
Non-existing Page Link Colour in Top Navigation: * Yes, it looks a bit awkward on green, but on the other hand I do not want to introduce a new "non-existing page" colour just for the top navigation - this would be confusing
Unfortunately the current status looks terrible :-( so please re-think your position on that.
Link colors * a, a:hover, a:active: now dark blue * a:visited now light blue * a:hover now has got a dotted border
(Colours will likely change again, these are just a draft)
Please, please unify the underlining. Non-visited links are underlined, visited links are not. This will cause lots of confusion... I don't really care if all links are underlined or not - as long as the same policy applies to *all* links.
Footer: * I don't think we can remove text, nor does it make sense to combine two lines in one.
Can you add some max-width then? Especially the first line would benefit from it. (The goal should be to have the "The content on ..." line as two lines with nearly equal length, which should be possible independent of the font size when using the "em" unit for max-width.) BTW, the bar after "About openSUSE" is superfluous... Another idea: This page was last modified 16:01, 24 May 2007. | This page has been accessed 221 times. could be combined to This page was last modified 16:01, 24 May 2007 and has been accessed 221 times. Doesn't save a line, but looks more readable IMHO.
Search Box: * I would prefer to leave the round corners (they are the same as the ones used for the boxes)
round corners are OK, but they look to rounded at the search box... Apropos search box: It seems it has a hardcoded height: which is unfortune for people who have a very large font size. Oh, and the layout has some problems on very large fonts in the header (tested with 300% in Konqueror - one of my favorite stress tests for websites ;-) The same problems appear with smaller font size when the window isn't wide enough to display the top menu (home page, My talk, Preferences etc.) in one line. Oh, and the Article/Discussion/Edit/... menu bar can hide the language selector on big fonts and/or too small window size. Additionally, the left column width should be specified in em also. Otherwise the menu can overlap the content on high font sizes. You can find two screenshots on www.cboltz.de/tmp/: - www.cboltz.de/tmp/fonts200.png - showing the cut-off language selector - www.cboltz.de/tmp/fonts300.png - showing the effects when the top menu bar needs more than one line 1. search field to small for entered text, search buttons outside the green box 2. and 3. overlapping text because of hardcoded width of left column 4. "Discover it" outside the green box
Content Table Background: * according to Novell brand guidelines the Geeko tail as well as the Geeko head should no longer be used, so I run out of background graphics matching the theme (and on the other hand I do not like copying Fedora ;) ). I have now changed the background to light green, but I am not sure whether this is better...
The main problem I see are the thick top and bottom border lines. Can you make them less visible? (for example thinner)
Language selector (JavaScript): * Now with Headline msg('otherlanguages')
Thanks!
Content Elements: I have added Christians <pre> proposals.
Thanks, but please remove the overflow-x:auto from div.meetings. Reason: Users will need to scroll down until they can reach the scrollbar. This is not funny for meeting transscripts which usually contain text to fit several pages. Without overflow-x:auto the horicontal scrollbar at the bottom of the browser scrollbar can be used which is always available. Also a note should be added to div.pre_hscroll saying that this should not be used for code that does not fit on the screen without scrolling. (Or make div.pre_hscroll a copy of div.pre_scroll with larger height to auto-enforce this rule.) Another thing I just noticed: please add some whitespace after <div> - the next headline is too close to it. Screenshot: www.cboltz.de/tmp/div.png
http://en.test.opensuse.org/index.php?title=Special:Allpages * I have absolutely no idea why the tables do not use the whole page width - this is why the list of all pages is messed up. Unfortunately no special style is created on this page, so there is no workaround. Please help!
Hmm, what about adding some padding (left and right) to <td> and <th> in general? This would also make normal tables in the content area looking better (see the table on Tag_Formatting which looks quite squeezed). Regards, Christian Boltz --
ich wollte wohl eigentlich sagen / demonstrieren, dass Updateritis heilbar sein kann... Das mag sein, aber der Entwöhnungsprozess kann dauern... [> David Haller und Michael Höhne in suse-linux]
To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Sunday 03 June 2007 21:12, Christian Boltz wrote: Hi, once again, thank you VERY much for your feedback. Seems we are reaching our goal very fast!
on Donnerstag, 31. Mai 2007, Frank Sundermeyer wrote:
On Thursday 24 May 2007 18:07, Frank Sundermeyer wrote:
Headlines: http://en.test.opensuse.org/index.php?title=Tag_Formatting#.3Ch1.3E .. ..3Ch6.3E
<h6> looks smaller than normal text - I'm not sure if this is a good idea. (Not really a problem - is there really someone who needs <h6>?)
I have never used it so far ;-). OK, <h6> now looks the same as <h5>.
Non-existing Page Link Colour in Top Navigation: * Yes, it looks a bit awkward on green, but on the other hand I do not want to introduce a new "non-existing page" colour just for the top navigation - this would be confusing
Unfortunately the current status looks terrible :-( so please re-think your position on that.
Modified the colour and made visited/new non-existing links the same colour (after all, non-existing is non-existing ;-) ). Hope it's at least slightly better now.
Link colors Please, please unify the underlining. Non-visited links are underlined, visited links are not. This will cause lots of confusion... I don't really care if all links are underlined or not - as long as the same policy applies to *all* links.
All links are underlined now. I have also removed the dotted border for the :hover effect and replaced it with a slight change in colour.
Footer: * I don't think we can remove text, nor does it make sense to combine two lines in one.
Can you add some max-width then? Especially the first line would benefit from it. (The goal should be to have the "The content on ..." line as two lines with nearly equal length, which should be possible independent of the font size when using the "em" unit for max-width.)
This does not work (or at least I am not able to make it work). Have added a linebreak, this also does the trick (at least for reasonable font sizes/screen resolutions).
BTW, the bar after "About openSUSE" is superfluous...
Fixed Template and edited MediaWiki:Disclaimers.
Another idea: This page was last modified 16:01, 24 May 2007. | This page has been accessed 221 times. could be combined to This page was last modified 16:01, 24 May 2007 and has been accessed 221 times.
Doesn't save a line, but looks more readable IMHO.
Modified MediWiki:lastmod and MediWiki:viewcount accordingly.
Search Box: * I would prefer to leave the round corners (they are the same as the ones used for the boxes)
round corners are OK, but they look to rounded at the search box...
Apropos search box: It seems it has a hardcoded height: which is unfortune for people who have a very large font size.
Without the fixed height, I do not see a way to make the round corners work in IE (at least not in IE 5.x)... .
Oh, and the layout has some problems on very large fonts in the header (tested with 300% in Konqueror - one of my favorite stress tests for websites ;-)
The same problems appear with smaller font size when the window isn't wide enough to display the top menu (home page, My talk, Preferences etc.) in one line.
Oh, and the Article/Discussion/Edit/... menu bar can hide the language selector on big fonts and/or too small window size.
OK, "white-space: nowrap" fixed that problem.
Additionally, the left column width should be specified in em also. Otherwise the menu can overlap the content on high font sizes.
Yup, fixed that, too.
Content Table Background: * according to Novell brand guidelines the Geeko tail as well as the Geeko head should no longer be used, so I run out of background graphics matching the theme (and on the other hand I do not like copying Fedora ;) ). I have now changed the background to light green, but I am not sure whether this is better...
The main problem I see are the thick top and bottom border lines. Can you make them less visible? (for example thinner)
Made the lines thinner and added a tail graphic - seems I was wrong regarding head and tail - they are still present on www.novell.com Francis, I thought a graphic would be more visible in the top right corner, rather than bottom right and the tail seemed to fit better than the head - hope you agree.
Thanks, but please remove the overflow-x:auto from div.meetings. Reason: Users will need to scroll down until they can reach the scrollbar.
Good point. Removed the overflow-x rule.
Also a note should be added to div.pre_hscroll saying that this should not be used for code that does not fit on the screen without scrolling. (Or make div.pre_hscroll a copy of div.pre_scroll with larger height to auto-enforce this rule.)
Another good point - I set the max. height to 25em and added a warning to the description.
Another thing I just noticed: please add some whitespace after <div> - the next headline is too close to it. Screenshot: www.cboltz.de/tmp/div.png
This has to be defined within the individual, additional classes for div, otherwise the whole layout will break. Since there should be no need to use a regular div within the content area (use p instead), this should be OK.
http://en.test.opensuse.org/index.php?title=Special:Allpages * I have absolutely no idea why the tables do not use the whole page width - this is why the list of all pages is messed up. Unfortunately no special style is created on this page, so there is no workaround. Please help!
Hmm, what about adding some padding (left and right) to <td> and <th> in general?
This would also make normal tables in the content area looking better (see the table on Tag_Formatting which looks quite squeezed).
Yes, seems to be the only solution -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Reality is always controlled by the people who are most insane (Dogbert) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Hallo, Am Montag, 4. Juni 2007 schrieb Frank Sundermeyer:
On Sunday 03 June 2007 21:12, Christian Boltz wrote:
once again, thank you VERY much for your feedback. Seems we are reaching our goal very fast!
Yes, but your changes discovered some new bugs ;-)
on Donnerstag, 31. Mai 2007, Frank Sundermeyer wrote:
On Thursday 24 May 2007 18:07, Frank Sundermeyer wrote:
Non-existing Page Link Colour in Top Navigation:
Modified the colour and made visited/new non-existing links the same colour (after all, non-existing is non-existing ;-) ). Hope it's at least slightly better now.
Yes, thanks.
Footer: * I don't think we can remove text, nor does it make sense to combine two lines in one.
Can you add some max-width then? Especially the first line would benefit from it. (The goal should be to have the "The content on ..." line as two lines with nearly equal length, which should be possible independent of the font size when using the "em" unit for max-width.)
This does not work (or at least I am not able to make it work).
Without having looked at the code: What exactly is the problem? (And: don't expect IE to understand max-width [don't know about IE7])
Have added a linebreak, this also does the trick (at least for reasonable font sizes/screen resolutions).
OK, acceptable workaround. (But max-width would still be better.)
Search Box: * I would prefer to leave the round corners (they are the same as the ones used for the boxes)
round corners are OK, but they look to rounded at the search box...
Apropos search box: It seems it has a hardcoded height: which is unfortune for people who have a very large font size.
Without the fixed height, I do not see a way to make the round corners work in IE (at least not in IE 5.x)... .
Then define the fixed height for IE only please ;-)
Oh, and the layout has some problems on very large fonts in the header (tested with 300% in Konqueror - one of my favorite stress tests for websites ;-)
The same problems appear with smaller font size when the window isn't wide enough to display the top menu (home page, My talk, Preferences etc.) in one line.
Oh, and the Article/Discussion/Edit/... menu bar can hide the language selector on big fonts and/or too small window size.
OK, "white-space: nowrap" fixed that problem.
Yes.
Additionally, the left column width should be specified in em also. Otherwise the menu can overlap the content on high font sizes.
Yup, fixed that, too.
Too good, 1em less would be enough ;-) Now to the problems this change discovered in combination with large font size - see screenshot on www.cboltz.de/tmp/opensuse-disco.png ;-) - on small screens there will be an openSUSE Disco ;-)) because "Discover it" is cut off" - the search box and the "Go" button are also cut off - OTOH, there's enough whitespace (to be exact: greenspace ;-) unused around these elements - so there's no real need to cut them off - The Article / Discussion / ... bar only uses the half width, causing too much unneeded linebreaks All unused white- or greenspace is marked with red color in my screenshot.
Content Table Background: * according to Novell brand guidelines the Geeko tail as well as the Geeko head should no longer be used, so I run out of background graphics matching the theme (and on the other hand I do not like copying Fedora ;) ). I have now changed the background to light green, but I am not sure whether this is better...
The main problem I see are the thick top and bottom border lines. Can you make them less visible? (for example thinner)
Made the lines thinner and added a tail graphic - seems I was wrong regarding head and tail - they are still present on www.novell.com
Much better :-)
Also a note should be added to div.pre_hscroll saying that this should not be used for code that does not fit on the screen without scrolling. (Or make div.pre_hscroll a copy of div.pre_scroll with larger height to auto-enforce this rule.)
Another good point - I set the max. height to 25em and added a warning to the description.
Hmm, is the warning really correct? <pre> with a horizontal scrollbar. Maximum height is 25em. Please _do not_ use the regular <pre> if your text does not fit the box. I would say Please _do_ use the regular <pre> (remove the "not")
Another thing I just noticed: please add some whitespace after <div> - the next headline is too close to it. Screenshot: www.cboltz.de/tmp/div.png
This has to be defined within the individual, additional classes for div, otherwise the whole layout will break. Since there should be no need to use a regular div within the content area (use p instead), this should be OK.
OK, so <div> is reserved as freestyle element ;-) in the hope that nearly nobody uses it...
http://en.test.opensuse.org/index.php?title=Special:Allpages * I have absolutely no idea why the tables do not use the whole page width - this is why the list of all pages is messed up. Unfortunately no special style is created on this page, so there is no workaround. Please help!
Hmm, what about adding some padding (left and right) to <td> and <th> in general?
This would also make normal tables in the content area looking better (see the table on Tag_Formatting which looks quite squeezed).
Yes, seems to be the only solution
It seems you added some padding-right to <td> now. Please have a look at the table on http://en.test.opensuse.org/index.php?title=Tagformatting and then add some padding-left also. Oh, and please apply the same padding to <th> ;-) Hmm, just curious: Special:Allpages has no borders at the table, Tagformatting has borders. So there *must* be a difference somewhere... Another thing that was mentioned some time ago, but obviously got lost: The grey boxes should use a slightly darker grey. The current one is nearly invisible on white (especially on laptop displays). Oh, and is there a special reason why the footer in the green double box http://en.test.opensuse.org/index.php?title=Structural_Elements#Double_Boxes doesn't have white text color? I doubt ;-) Regards, Christian Boltz -- An NT server can be run by an idiot, and usually is. [Tom Holub,a.h.b-o-u] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Tuesday 05 June 2007 14:27, Christian Boltz wrote: Hi,
Am Montag, 4. Juni 2007 schrieb Frank Sundermeyer:
On Sunday 03 June 2007 21:12, Christian Boltz wrote:
Yes, but your changes discovered some new bugs ;-)
I feared that - thanks a lot for digging it it again!
Footer: * I don't think we can remove text, nor does it make sense to combine two lines in one.
Can you add some max-width then? Especially the first line would benefit from it. (The goal should be to have the "The content on ..." line as two lines with nearly equal length, which should be possible independent of the font size when using the "em" unit for max-width.)
This does not work (or at least I am not able to make it work).
Without having looked at the code: What exactly is the problem? (And: don't expect IE to understand max-width [don't know about IE7])
The page consists of two floating columns, the bigger one has got a left margin that corresponds with the width of the left column. When specifying a max width for the footer, the text is centered within the area specified by max-width and not within the parent div.
Search Box: * I would prefer to leave the round corners (they are the same as the ones used for the boxes)
round corners are OK, but they look to rounded at the search box...
Apropos search box: It seems it has a hardcoded height: which is unfortune for people who have a very large font size.
Without the fixed height, I do not see a way to make the round corners work in IE (at least not in IE 5.x)... .
Then define the fixed height for IE only please ;-)
Sigh, this will be a lot of work - the search box code needs to be rewritten completely. I will see what I can do.
Additionally, the left column width should be specified in em also. Otherwise the menu can overlap the content on high font sizes.
Yup, fixed that, too.
Too good, 1em less would be enough ;-)
Yes.
Now to the problems this change discovered in combination with large font size - see screenshot on www.cboltz.de/tmp/opensuse-disco.png ;-)
Oh, come on ;-) - with a font-size that big the page is unusable anyway.
- on small screens there will be an openSUSE Disco ;-)) because "Discover it" is cut off" - the search box and the "Go" button are also cut off
Sure - they just don't fit in the parent element box anymore ;-). OK, defining the left/right margins in px and the height in em helped a lot. Nevertheless, when enlarging the font to a certain extend you will reach a point where the search box and/or the slogan won't fix anymore.
- OTOH, there's enough whitespace (to be exact: greenspace ;-) unused around these elements - so there's no real need to cut them off
- The Article / Discussion / ... bar only uses the half width, causing too much unneeded linebreaks
Should be fixed by now.
Hmm, is the warning really correct?
<pre> with a horizontal scrollbar. Maximum height is 25em. Please _do not_ use the regular <pre> if your text does not fit the box.
I would say Please _do_ use the regular <pre> (remove the "not")
Of course.
Another thing I just noticed: please add some whitespace after <div> - the next headline is too close to it. Screenshot: www.cboltz.de/tmp/div.png
This has to be defined within the individual, additional classes for div, otherwise the whole layout will break. Since there should be no need to use a regular div within the content area (use p instead), this should be OK.
OK, so <div> is reserved as freestyle element ;-) in the hope that nearly nobody uses it...
Nobody should in a wiki - why? And I wouldn't call it freestyle - it is just the bare element with no styles attached to it.
http://en.test.opensuse.org/index.php?title=Special:Allpages * I have absolutely no idea why the tables do not use the whole page width - this is why the list of all pages is messed up. Unfortunately no special style is created on this page, so there is no workaround. Please help!
Hmm, what about adding some padding (left and right) to <td> and <th> in general?
This would also make normal tables in the content area looking better (see the table on Tag_Formatting which looks quite squeezed).
Yes, seems to be the only solution
It seems you added some padding-right to <td> now.
Oh, seems I made a copy&paste error on that section ... .
Hmm, just curious: Special:Allpages has no borders at the table, Tagformatting has borders. So there *must* be a difference somewhere...
==<table><caption><tr><td><th>== {| border="1" width="50%" ;-)
Another thing that was mentioned some time ago, but obviously got lost: The grey boxes should use a slightly darker grey. The current one is nearly invisible on white (especially on laptop displays).
Not forgotten, but postponed. Anyway, it's a bit darker now ( s/F0F0F0/E0E0E0/ )
Oh, and is there a special reason why the footer in the green double box http://en.test.opensuse.org/index.php?title=Structural_Elements#Doubl e_Boxes doesn't have white text color? I doubt ;-)
Fixed. -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Reality is always controlled by the people who are most insane" Dogbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Tuesday 05 June 2007 18:16, Frank Sundermeyer wrote: Hi,
On Tuesday 05 June 2007 14:27, Christian Boltz wrote:
[search box]
Then define the fixed height for IE only please ;-)
Sigh, this will be a lot of work - the search box code needs to be rewritten completely. I will see what I can do.
turns out that rewriting that bit of html/css was worth while ;-) The new code works much better than the former hack. Now the input field is scalable. -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Reality is always controlled by the people who are most insane" Dogbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Wednesday 06 June 2007 06:48, Frank Sundermeyer wrote:
On Tuesday 05 June 2007 18:16, Frank Sundermeyer wrote:
Hi,
On Tuesday 05 June 2007 14:27, Christian Boltz wrote:
[search box]
Then define the fixed height for IE only please ;-)
Sigh, this will be a lot of work - the search box code needs to be rewritten completely. I will see what I can do.
turns out that rewriting that bit of html/css was worth while ;-) The new code works much better than the former hack. Now the input field is scalable.
Yet another problem. In Firefox I went from normal font size to the maximal and back to minimal. The logo is covered by "Discover it". The width of left pane including logo is dictated with font size used in menu items. The same in Konqueror, but not so explicit as font sizes don't go to very small or very large as in Firefox. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Friday 08 June 2007 03:40, Rajko M. wrote: Hi,
Yet another problem.
In Firefox I went from normal font size to the maximal and back to minimal. The logo is covered by "Discover it". The width of left pane including logo is dictated with font size used in menu items.
yes, that's intentional. The downside is that the logo does not fit when using very small font-sizes. I have tried a percentage width for the logo (width: 92%) which does the trick, but then the browser renders the image, resulting in poor quality. A minimum width for the left column is not an option, too, because this would require a variable left margin for the content area and that is not possible with CSS at the moment. Specifying the left column width in percent or with a fixed value is also no option, because this will result in text becoming wider than the column when using large fonts. Any other/better ideas? -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Reality is always controlled by the people who are most insane" Dogbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Hello, on Dienstag, 5. Juni 2007, Frank Sundermeyer wrote:
On Tuesday 05 June 2007 14:27, Christian Boltz wrote:
Am Montag, 4. Juni 2007 schrieb Frank Sundermeyer:
On Sunday 03 June 2007 21:12, Christian Boltz wrote:
Footer: [...] which should be possible independent of the font size when using the "em" unit for max-width.)
This does not work (or at least I am not able to make it work).
Without having looked at the code: What exactly is the problem? (And: don't expect IE to understand max-width [don't know about IE7])
The page consists of two floating columns, the bigger one has got a left margin that corresponds with the width of the left column. When specifying a max width for the footer, the text is centered within the area specified by max-width and not within the parent div.
Sounds like you want to use a nested <div>. Not nice, but should work ;-) (and IE will simply ignore it, which isn't a real problem)
Search Box: Apropos search box: It seems it has a hardcoded height: which is unfortune for people who have a very large font size.
Without the fixed height, I do not see a way to make the round corners work in IE (at least not in IE 5.x)... .
Then define the fixed height for IE only please ;-)
Sigh, this will be a lot of work - the search box code needs to be rewritten completely. I will see what I can do.
It's perfect now - thanks!
Now to the problems this change discovered in combination with large font size - see screenshot on www.cboltz.de/tmp/opensuse-disco.png ;-)
Oh, come on ;-) - with a font-size that big the page is unusable anyway.
*g* I know, but usually testing with extremes makes things better for the normal usecases - and speeds up finding bugs a lot ;-)
- on small screens there will be an openSUSE Disco ;-)) because "Discover it" is cut off" - the search box and the "Go" button are also cut off
Sure - they just don't fit in the parent element box anymore ;-).
OK, defining the left/right margins in px
Much better, thanks!
and the height in em helped a lot.
I'm not sure if defining the height in em was a good idea. Now the green box is too heigh on large font sizes. Or fix it the other way round and allow line wraps in the top menu again. Then the height will be OK and the top menu is usable with all font sizes ;-) Choose whatever you want...
Nevertheless, when enlarging the font to a certain extend you will reach a point where the search box and/or the slogan won't fix anymore.
I know ;-)
- OTOH, there's enough whitespace (to be exact: greenspace ;-) unused around these elements - so there's no real need to cut them off
- The Article / Discussion / ... bar only uses the half width, causing too much unneeded linebreaks
Should be fixed by now.
Not really - now the language dropdown is cut off at the left even at small font sizes :-( Screenshot: http://www.cboltz.de/tmp/opensuse-menu.png Proposal: make the dropdown float:right instead of assigning a column width of xx % .
OK, so <div> is reserved as freestyle element ;-) in the hope that nearly nobody uses it...
Nobody should in a wiki - why? And I wouldn't call it freestyle - it is just the bare element with no styles attached to it.
... and the possibility to add style=... ;-) However, I agree that it shouldn't be used.
Hmm, just curious: Special:Allpages has no borders at the table, Tagformatting has borders. So there *must* be a difference somewhere...
==<table><caption><tr><td><th>== {| border="1" width="50%"
;-)
What about {| class="nopadding" and .nopadding td { ... } ? ;-)
Another thing that was mentioned some time ago, but obviously got lost: The grey boxes should use a slightly darker grey. The current one is nearly invisible on white (especially on laptop displays).
Not forgotten, but postponed. Anyway, it's a bit darker now ( s/F0F0F0/E0E0E0/ )
My laptop display likes it ;-) Regards, Christian Boltz -- [vordefinierte Perlvariablen $_, $>, $[ usw.]
Steht eigentlich in $§ die Lizenz? ;-))) $ perl -we 'print $§' Use of uninitialized value in print at -e line 1. [> Christian Boltz und David Haller in fontlinge-devel]
To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
participants (7)
-
Christian Boltz -
Francis Giannaros -
Frank Sundermeyer -
James Tremblay -
jdd -
Marcus Rueckert -
Rajko M.