> Fixed online.
Thanks, confirmed here.
Hugh
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the
Hugh Gibson schrieb:
Does anyone else get this problem, or is it only me? I ran the page
through the w3c validator at http://validator.w3.org/ and it
complained about tags appearing without an enclosing tag. But
that didn't cure the page for IE6.
This was doctype related. I've fixed this in
Hugh Gibson schrieb:
Does anyone else get this problem, or is it only me? I ran the page
through the w3c validator at http://validator.w3.org/ and it
complained about tags appearing without an enclosing tag. But
that didn't cure the page for IE6.
This was doctype related. I've fixed this in
> >
> > Does anyone else get this problem, or is it only me? I ran the page
> > through the w3c validator at http://validator.w3.org/ and it
> > complained about tags appearing without an enclosing tag. But
> > > > that didn't cure the page for IE6.
>
> This was doctype related. I've fixed t
> Just a small typo:
>
> tools/generate/makedocs.sh => tools/generate/make-docs.sh
Fixed. Thanks.
Hugh
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine
Hugh Gibson schrieb:
Yes, please rename /public to /build. Also you could explain there,
that /build is the built result of /source. I had remove this from the
FAQ as this was just not true anymore and I had no time to fix it.
Probably you could also add it to the FAQ, but I think it's the wron
> Yes, please rename /public to /build. Also you could explain there,
> that /build is the built result of /source. I had remove this from the
> FAQ as this was just not true anymore and I had no time to fix it.
> Probably you could also add it to the FAQ, but I think it's the wrong
> place the
Hugh Gibson schrieb:
Reminder...
Note that in addition that I use IE6 to view the docs files from
either the release or from CVS generated docs, I see a blank page.
It works under FF1.5. This is under Windows 2K.
Don't miss this issue, Sebastian.
I also see no content in IE6 following this
Reminder...
> > > Note that in addition that I use IE6 to view the docs files from
> > > either the release or from CVS generated docs, I see a blank page.
> > > It works under FF1.5. This is under Windows 2K.
> >
> > Don't miss this issue, Sebastian.
I also see no content in IE6 following thi
> I think the documentation should be up-to-date and all links should
> work. For the blog entries I think we don't need to update them,
> because old news are no news ;)
OK, so pages which are linked to from the
http://qooxdoo.oss.schlund.de/section/documentation page (for example)
should be
> Yes, please rename /public to /build. Also you could explain there, that
> /build is the built result of /source. I had remove this from the FAQ as
> this was just not true anymore and I had no time to fix it.
> Probably you could also add it to the FAQ, but I think it's the wrong
place there,
Hugh Gibson schrieb:
However, there is a deeper problem here
Now that you have made the new release, I also suggest a full review of
other pages. For example,
http://qooxdoo.oss.schlund.de/2005/12/15/new-qxtree-and-qxlistview is
redundant now as well as giving 404s on all the links.
Again,
Hugh Gibson schrieb:
Note that in addition that I use IE6 to view the docs files from either
the release or from CVS generated docs, I see a blank page. It works
under FF1.5. This is under Windows 2K.
Don't miss this issue, Sebastian.
Mea culpa regarding rsync. I'll change the cygwin instruct
> However, there is a deeper problem here
Now that you have made the new release, I also suggest a full review of
other pages. For example,
http://qooxdoo.oss.schlund.de/2005/12/15/new-qxtree-and-qxlistview is
redundant now as well as giving 404s on all the links.
Again, if I know your policy
t; [mailto:[EMAIL PROTECTED] Im Auftrag
> von Hugh Gibson
> Gesendet: Montag, 20. Februar 2006 18:48
> An: qooxdoo-devel@lists.sourceforge.net
> Betreff: Re: [qooxdoo-devel] also missing css in documentation
>
> > Note that in addition that I use IE6 to view the docs files
>
f sie behalten"
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag
> von Sebastian Werner
> Gesendet: Montag, 20. Februar 2006 17:54
> An: qooxdoo-devel@lists.sourceforge.net; Oliver Vogel
> Betreff: Re: AW: [qooxdoo-devel] al
> Note that in addition that I use IE6 to view the docs files from either
> the release or from CVS generated docs, I see a blank page. It works
> under FF1.5. This is under Windows 2K.
Don't miss this issue, Sebastian.
Mea culpa regarding rsync. I'll change the cygwin instructions as you gave
Hugh Gibson schrieb:
Do you have installed rsync?
Ah, that's probably the issue. This is from the output of running the docs
build script here:
Syncing files...
tools/generate/internal/syncfiles.sh: line 7: rsync: command not found
tools/generate/internal/syncfiles.sh: line 10: rsync: comm
Hugh Gibson schrieb:
Do you have installed rsync?
Ah, that's probably the issue. This is from the output of running the docs
build script here:
Syncing files...
tools/generate/internal/syncfiles.sh: line 7: rsync: command not found
tools/generate/internal/syncfiles.sh: line 10: rsync: comm
Hugh Gibson schrieb:
Do you have installed rsync?
Ah, that's probably the issue. This is from the output of running the docs
build script here:
Syncing files...
tools/generate/internal/syncfiles.sh: line 7: rsync: command not found
tools/generate/internal/syncfiles.sh: line 10: rsync: comm
> Do you have installed rsync?
Ah, that's probably the issue. This is from the output of running the docs
build script here:
>>> Syncing files...
tools/generate/internal/syncfiles.sh: line 7: rsync: command not found
tools/generate/internal/syncfiles.sh: line 10: rsync: command not found
>>> Don
> > I just got a fresh CVS head and I see the same problems as Olli with
> > the demo. Sure takes a long time to update CVS...
>
> Have you completely removed the previous check-out or just done a cvs
> update? I have no problems here. Interesting.
Completely removed. Deleted it and checked out
]
[mailto:[EMAIL PROTECTED] Im Auftrag
von Sebastian Werner
Gesendet: Montag, 20. Februar 2006 16:14
An: qooxdoo-devel@lists.sourceforge.net
Betreff: Re: [qooxdoo-devel] also missing css in documentation
Hugh Gibson schrieb:
it's strange.
The generated docs will also not work.
Only after
16:14
> An: qooxdoo-devel@lists.sourceforge.net
> Betreff: Re: [qooxdoo-devel] also missing css in documentation
>
> Hugh Gibson schrieb:
> >>> it's strange.
> >>> The generated docs will also not work.
> >>>
> >>> Only after co
Hugh Gibson schrieb:
it's strange.
The generated docs will also not work.
Only after copying main.js, print.css, screen.css and common.css by
my own to /build/docs the documentation works well.
it seems like there is a problem in copying the css - files generally
As already explained it works
> > it's strange.
> > The generated docs will also not work.
> >
> > Only after copying main.js, print.css, screen.css and common.css by
> > my own to /build/docs the documentation works well.
> > it seems like there is a problem in copying the css - files generally
>
> As already explained it w
Oliver Vogel schrieb:
it's strange.
The generated docs will also not work.
Only after copying main.js, print.css, screen.css and common.css by my
own to /build/docs the documentation works well.
it seems like there is a problem in copying the css - files generally
As already explained it wor
it's strange.
The generated docs will also not work.
Only after copying main.js, print.css, screen.css and common.css by my
own to /build/docs the documentation works well.
it seems like there is a problem in copying the css - files generally
Olli
---
28 matches
Mail list logo
