Re: [HELP REQUIRED]: edit reference version on the website
On Jun 25, 2012, at 2:29 AM, Jürgen Schmidt wrote: > On 6/22/12 4:45 PM, Dave Fisher wrote: >> Hi Jürgen, >> >> My memory was not correct the string to change is in >> templates/api/ssi.mdtext. >> >> I've made this change: >> >> @@ -3,5 +3,5 @@ >> footer: /footer.html >> topnav: /topnav.html >> leftnav: /api/leftnav.html >> -legacy: Content for OpenOffice.org version 3.3. >> +legacy: Content for Apache OpenOffice version 3.4. >> home:home >> > > thanks for changing the version string. But I can't see the whole string > anymore. Should be all good. Let me know if you'd like to discuss a redesign. Regards, Dave > > Juergen > > >> You may need to make a trivial change to trigger the rebuild of the api >> content. >> >> Regards, >> Dave >> >> >> On Jun 20, 2012, at 5:10 AM, Dave Fisher wrote: >> >>> Look in api/brand.mdtext >>> >>> I'm on board a flight home and will help later. We can totally discuss the >>> CSS. What don't you like? >>> >>> Regards, >>> Dave >>> >>> Sent from my iPhone >>> >>> On Jun 20, 2012, at 4:04 AM, Jürgen Schmidt >>> wrote: >>> Hi, I need some help. I have updated the generated reference documentation on api.openoffice.org. where I have not changed the related css files. Ok I have checked in the files but they are not yet published. On top of the page is a string "Content for OpenOffice.org version 3.3.". I haven't found the string and would like to know where I can find and edit it for now. I don't really like the current layout anymore and would like to rework the whole page in the future. But that is a different topic ;-) Thanks Juergen >> > >
Re: [HELP REQUIRED]: edit reference version on the website
On 6/22/12 4:45 PM, Dave Fisher wrote: > Hi Jürgen, > > My memory was not correct the string to change is in templates/api/ssi.mdtext. > > I've made this change: > > @@ -3,5 +3,5 @@ > footer: /footer.html > topnav: /topnav.html > leftnav: /api/leftnav.html > -legacy: Content for OpenOffice.org version 3.3. > +legacy: Content for Apache OpenOffice version 3.4. > home:home > thanks for changing the version string. But I can't see the whole string anymore. Juergen > You may need to make a trivial change to trigger the rebuild of the api > content. > > Regards, > Dave > > > On Jun 20, 2012, at 5:10 AM, Dave Fisher wrote: > >> Look in api/brand.mdtext >> >> I'm on board a flight home and will help later. We can totally discuss the >> CSS. What don't you like? >> >> Regards, >> Dave >> >> Sent from my iPhone >> >> On Jun 20, 2012, at 4:04 AM, Jürgen Schmidt >> wrote: >> >>> Hi, >>> >>> I need some help. I have updated the generated reference documentation >>> on api.openoffice.org. where I have not changed the related css files. >>> >>> Ok I have checked in the files but they are not yet published. >>> >>> On top of the page is a string "Content for OpenOffice.org version >>> 3.3.". I haven't found the string and would like to know where I can >>> find and edit it for now. I don't really like the current layout anymore >>> and would like to rework the whole page in the future. But that is a >>> different topic ;-) >>> >>> Thanks >>> >>> Juergen >
Re: [HELP REQUIRED]: edit reference version on the website
On Jun 23, 2012, at 3:58 AM, TJ Frazier wrote: > On 6/22/2012 17:35, Dave Fisher wrote: >> Hi Jürgen, >> >> I've moved the navigation over to the righthand side. I think that looks >> much better. >> >> Please see >> http://ooo-site.staging.apache.org/api/docs/common/ref/com/sun/star/auth/module-ix.html >> > > > Dave, > > A few thoughts on the nav column: > > * (Personal): "You are messing with the tools in my workshop. You need a very > good reason to do that ... " Forgive me. I tool the opening to suggest a change. It is easily reversible although it takes a couple of hours because the API is big. This is also staged, it is there for RTC. Revert? If so simply revert templates/api/ssi.mdtext and leave the rightnav work in content/css/ooo.css. > > * Both Mwiki and Cwiki have their nav info on the left. For those accustomed > to LTR languages, there is a certain natural hierarchy of position involved. I think that if the content is the main focus then for LTR languages having subsidiary navigation on the right makes more sense. What wikis do may be different. The main API page uses a right nav. > > * Is a nav column really the best use of screen real-estate? The Apache main > site cleverly relegates a lot of navigation to the footer. Perhaps a > "Navigation" button link thereto? Agreed. These pages already have two or three layers of horizontal buttons in a mess of styles. > > * IIRC, the SDK provides a local copy of the API. Will that look the same as > the web site? No and it would be good to consider the needs of both in the SDK generation which AFAIK is what Jürgen is providing with this update. If you'd like to I can work with you slowly to correct these issues. HTH, Dave > > /tj/ >
Re: [HELP REQUIRED]: edit reference version on the website
On 6/22/2012 17:35, Dave Fisher wrote: Hi Jürgen, I've moved the navigation over to the righthand side. I think that looks much better. Please see http://ooo-site.staging.apache.org/api/docs/common/ref/com/sun/star/auth/module-ix.html Dave, A few thoughts on the nav column: * (Personal): "You are messing with the tools in my workshop. You need a very good reason to do that ... " * Both Mwiki and Cwiki have their nav info on the left. For those accustomed to LTR languages, there is a certain natural hierarchy of position involved. * Is a nav column really the best use of screen real-estate? The Apache main site cleverly relegates a lot of navigation to the footer. Perhaps a "Navigation" button link thereto? * IIRC, the SDK provides a local copy of the API. Will that look the same as the web site? /tj/
Re: [HELP REQUIRED]: edit reference version on the website
Hi Jürgen, I've moved the navigation over to the righthand side. I think that looks much better. Please see http://ooo-site.staging.apache.org/api/docs/common/ref/com/sun/star/auth/module-ix.html I think that API to dos are now: (1) Improve the look by adjusting the CSS in these files (relative to content/api/.) ./docooo.css ./docs/common/ref/idl.css ./docs/cpp/ref/cpp.css ./docs/java/ref/stylesheet.css (2) Adjust the trademark references that you added to the bottom. I think the copyright stays but the trademark is already in the common footer. (3) Update the main page content/api/index.html. Regards, Dave On Jun 22, 2012, at 11:10 AM, Dave Fisher wrote: > These changes are now staged. I may have some cycles to help with design > Sunday. > > > On Jun 22, 2012, at 7:45 AM, Dave Fisher wrote: > >> Hi Jürgen, >> >> My memory was not correct the string to change is in >> templates/api/ssi.mdtext. >> >> I've made this change: >> >> @@ -3,5 +3,5 @@ >> footer: /footer.html >> topnav: /topnav.html >> leftnav: /api/leftnav.html >> -legacy: Content for OpenOffice.org version 3.3. >> +legacy: Content for Apache OpenOffice version 3.4. >> home:home >> >> You may need to make a trivial change to trigger the rebuild of the api >> content. >> >> Regards, >> Dave >> >> >> On Jun 20, 2012, at 5:10 AM, Dave Fisher wrote: >> >>> Look in api/brand.mdtext >>> >>> I'm on board a flight home and will help later. We can totally discuss the >>> CSS. What don't you like? >>> >>> Regards, >>> Dave >>> >>> Sent from my iPhone >>> >>> On Jun 20, 2012, at 4:04 AM, Jürgen Schmidt >>> wrote: >>> Hi, I need some help. I have updated the generated reference documentation on api.openoffice.org. where I have not changed the related css files. Ok I have checked in the files but they are not yet published. On top of the page is a string "Content for OpenOffice.org version 3.3.". I haven't found the string and would like to know where I can find and edit it for now. I don't really like the current layout anymore and would like to rework the whole page in the future. But that is a different topic ;-) Thanks Juergen >> >
Re: [HELP REQUIRED]: edit reference version on the website
These changes are now staged. I may have some cycles to help with design Sunday. On Jun 22, 2012, at 7:45 AM, Dave Fisher wrote: > Hi Jürgen, > > My memory was not correct the string to change is in templates/api/ssi.mdtext. > > I've made this change: > > @@ -3,5 +3,5 @@ > footer: /footer.html > topnav: /topnav.html > leftnav: /api/leftnav.html > -legacy: Content for OpenOffice.org version 3.3. > +legacy: Content for Apache OpenOffice version 3.4. > home: home > > You may need to make a trivial change to trigger the rebuild of the api > content. > > Regards, > Dave > > > On Jun 20, 2012, at 5:10 AM, Dave Fisher wrote: > >> Look in api/brand.mdtext >> >> I'm on board a flight home and will help later. We can totally discuss the >> CSS. What don't you like? >> >> Regards, >> Dave >> >> Sent from my iPhone >> >> On Jun 20, 2012, at 4:04 AM, Jürgen Schmidt >> wrote: >> >>> Hi, >>> >>> I need some help. I have updated the generated reference documentation >>> on api.openoffice.org. where I have not changed the related css files. >>> >>> Ok I have checked in the files but they are not yet published. >>> >>> On top of the page is a string "Content for OpenOffice.org version >>> 3.3.". I haven't found the string and would like to know where I can >>> find and edit it for now. I don't really like the current layout anymore >>> and would like to rework the whole page in the future. But that is a >>> different topic ;-) >>> >>> Thanks >>> >>> Juergen >
Re: [HELP REQUIRED]: edit reference version on the website
Hi Jürgen, My memory was not correct the string to change is in templates/api/ssi.mdtext. I've made this change: @@ -3,5 +3,5 @@ footer:/footer.html topnav:/topnav.html leftnav: /api/leftnav.html -legacy:Content for OpenOffice.org version 3.3. +legacy:Content for Apache OpenOffice version 3.4. home: home You may need to make a trivial change to trigger the rebuild of the api content. Regards, Dave On Jun 20, 2012, at 5:10 AM, Dave Fisher wrote: > Look in api/brand.mdtext > > I'm on board a flight home and will help later. We can totally discuss the > CSS. What don't you like? > > Regards, > Dave > > Sent from my iPhone > > On Jun 20, 2012, at 4:04 AM, Jürgen Schmidt > wrote: > >> Hi, >> >> I need some help. I have updated the generated reference documentation >> on api.openoffice.org. where I have not changed the related css files. >> >> Ok I have checked in the files but they are not yet published. >> >> On top of the page is a string "Content for OpenOffice.org version >> 3.3.". I haven't found the string and would like to know where I can >> find and edit it for now. I don't really like the current layout anymore >> and would like to rework the whole page in the future. But that is a >> different topic ;-) >> >> Thanks >> >> Juergen
Re: [HELP REQUIRED]: edit reference version on the website
You'll want to look at api/leftnav.mdtext. You could rename that rightnav.mdtext to move the navigation. Sent from my iPhone On Jun 20, 2012, at 7:14 AM, Jürgen Schmidt wrote: > On 6/20/12 2:10 PM, Dave Fisher wrote: >> Look in api/brand.mdtext >> >> I'm on board a flight home and will help later. We can totally discuss the >> CSS. What don't you like? > > I am thinking more about a general redesign of the page, nothing > technical so far > > Thanks for the pointer > > Juergen > >> >> Regards, >> Dave >> >> Sent from my iPhone >> >> On Jun 20, 2012, at 4:04 AM, Jürgen Schmidt >> wrote: >> >>> Hi, >>> >>> I need some help. I have updated the generated reference documentation >>> on api.openoffice.org. where I have not changed the related css files. >>> >>> Ok I have checked in the files but they are not yet published. >>> >>> On top of the page is a string "Content for OpenOffice.org version >>> 3.3.". I haven't found the string and would like to know where I can >>> find and edit it for now. I don't really like the current layout anymore >>> and would like to rework the whole page in the future. But that is a >>> different topic ;-) >>> >>> Thanks >>> >>> Juergen > >
Re: [HELP REQUIRED]: edit reference version on the website
On 6/20/12 2:10 PM, Dave Fisher wrote: > Look in api/brand.mdtext > > I'm on board a flight home and will help later. We can totally discuss the > CSS. What don't you like? I am thinking more about a general redesign of the page, nothing technical so far Thanks for the pointer Juergen > > Regards, > Dave > > Sent from my iPhone > > On Jun 20, 2012, at 4:04 AM, Jürgen Schmidt > wrote: > >> Hi, >> >> I need some help. I have updated the generated reference documentation >> on api.openoffice.org. where I have not changed the related css files. >> >> Ok I have checked in the files but they are not yet published. >> >> On top of the page is a string "Content for OpenOffice.org version >> 3.3.". I haven't found the string and would like to know where I can >> find and edit it for now. I don't really like the current layout anymore >> and would like to rework the whole page in the future. But that is a >> different topic ;-) >> >> Thanks >> >> Juergen
Re: [HELP REQUIRED]: edit reference version on the website
Look in api/brand.mdtext I'm on board a flight home and will help later. We can totally discuss the CSS. What don't you like? Regards, Dave Sent from my iPhone On Jun 20, 2012, at 4:04 AM, Jürgen Schmidt wrote: > Hi, > > I need some help. I have updated the generated reference documentation > on api.openoffice.org. where I have not changed the related css files. > > Ok I have checked in the files but they are not yet published. > > On top of the page is a string "Content for OpenOffice.org version > 3.3.". I haven't found the string and would like to know where I can > find and edit it for now. I don't really like the current layout anymore > and would like to rework the whole page in the future. But that is a > different topic ;-) > > Thanks > > Juergen
[HELP REQUIRED]: edit reference version on the website
Hi, I need some help. I have updated the generated reference documentation on api.openoffice.org. where I have not changed the related css files. Ok I have checked in the files but they are not yet published. On top of the page is a string "Content for OpenOffice.org version 3.3.". I haven't found the string and would like to know where I can find and edit it for now. I don't really like the current layout anymore and would like to rework the whole page in the future. But that is a different topic ;-) Thanks Juergen
