User talk:Ccornell

Hello,

I tried to setup the menu structure for the second chapter. But I seem to run into trouble in that I can't figure out how to get the pages within the chapter to show up in the menu. Could you check to see what I'm doing wrong?

--Kirk 00:45, 18 July 2007 (CEST)

Nevermind, I seem to have figured it out. --Kirk 00:35, 19 July 2007 (CEST)

It's a little complex to begin with, but once you see the pattern of how the TOC works, it starts to make sense :-) I made a small change to the template - changed max-width to just width. Internet Explorer is a broken browser, and does not respect CSS standards very well. It doesn't know max-width, so the easy solution is just to use a fixed width for the TOC. --Ccornell 08:41, 19 July 2007 (CEST)

New Template problem

I'm having a bit of difficulty getting the revised template to show the next page in a document. Could you have a look at Template:Documentation/ImpressFormattingTOC? Everything else seems to be working okay, I just can't seem see what I'm missing on that part. --Kirk 03:24, 13 December 2007 (CET)

You have implemented the TOC correctly. When you look at the TOC page itself, you will see it shown as you see it on the link above (the raw TOC, not the TOC as it is shown when included in a content page). The Next and Previous page parts of the TOC will show (in the raw TOC) as [[{{{PrevPage}}}|< Previous Page]] and [[{{{NextPage}}}|Next Page >]] on the TOC page itself - this is because the variables for the Next and Previous pages have not yet been given to the template.

When the TOC is included in a content page and you pass the Next and Previous variables, the links will be created on the content page. --Ccornell 11:49, 2 January 2008 (CET)

Syntax Highlighting for the Color Blind

Hey,

I couldn't find an appropriate place to bring this up elsewhere, so I decided to contact you. I'm color blind, and I'm having a very hard time reading source code which is syntax-highlighted. I wind up having to select text, and read the selected text, or paste to another program.

The cyan (I think?) syntax color is nearly invisible for me, and entirely unreadable. See for example:

// 4-parameter template
class RNG_impl : public ::cppu::WeakImplHelper4<
        ::org::openoffice::sheet::addin::XRNG,
        ::sheet::XAddIn,
        lang::XServiceName,
        lang::XServiceInfo >

Good point! It is a horrible color for anyone to have to try and read. We need to look at the colors used for the syntax highlighting. Right now it is simply using the defaults. Changing the default colors means editing the CSS for GeSHI - so not too difficult. The old syntax highlighter had some color customizations that I can refer to as a place to start.

The best place to discuss this is on the dev@website.openoffice.org mailing list. I will post updates and information there. --Ccornell 20:44, 25 March 2008 (CET)