Attached is a list of issues I've had while working with xweb. Any help would be greatly appreciated.
- generic.xsl
- is it possible to have documents in the top-level without using the ../ method in some of the examples? I keep generating navigation bars with "" as the target :-(
- how does one embed a relative image tag in a header file. the reference doesn't seem to be expanded
- the xmlns attribute of the <html> entity set by HTML Tidy's XHTML output seems to confuse the generic stylesheet. Once the attribute is removed the stylesheet works as expected
- other
- the DOCTYPE directive (is this the right noun in XML-speak?) set by HTML Tidy's XHTML output causes xweb to stop processing.
- style.css
- how does one embed a relative image tag in the style sheet (i.e. background)? Do I need to pass the .css file thru xslt to set this?
- documentation
- the <homepage> entity in the makefile syntax isn't documented
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
here some comments and maybe some help on your problems:
- there should be two other ways to get documents at the toplevel: one is to use the <index> element from the multi-layout version (see http://xweb.sourceforge.net/manual/advanced/layouts.html\), another one is to use targetDir="." as directory for one of the sections. The drawback of the latter is that all files (html, images) from this section will end up there
- the header and footer files are not processed at all -- I probably could easily add this, just file a feature request. Urgent?
- the xmlns and DOCTYPE issues are known problems, sorry -- no solution yet. "DOCTYPE directive" is AFAIK proper XML-speak.
- yes, to resolve internal references in the CSS you would have to create it via XSLT. The XSLT for this would be easy, though. It might add other useful things like being able to define colors for different things in one place (e.g. a parameter).
- the <homepage> is not documented, because I want to drop it ;-) Originally it seemed a good idea but by now I think using the first <entry> is as good and does keep things simple. Do you like the idea of the explicit section <homepage>? I think the notion that a click on a section button opens the first entry is more obvious.
Hope this helps at least a bit,
Peter
PS: if you have more feedback (which is highly appreciated), it might be a good idea to switch to the mailing list. Answering emails is easier than webforms. No real need, though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
Attached is a list of issues I've had while working with xweb. Any help would be greatly appreciated.
- generic.xsl
- is it possible to have documents in the top-level without using the ../ method in some of the examples? I keep generating navigation bars with "" as the target :-(
- how does one embed a relative image tag in a header file. the reference doesn't seem to be expanded
- the xmlns attribute of the <html> entity set by HTML Tidy's XHTML output seems to confuse the generic stylesheet. Once the attribute is removed the stylesheet works as expected
- other
- the DOCTYPE directive (is this the right noun in XML-speak?) set by HTML Tidy's XHTML output causes xweb to stop processing.
- style.css
- how does one embed a relative image tag in the style sheet (i.e. background)? Do I need to pass the .css file thru xslt to set this?
- documentation
- the <homepage> entity in the makefile syntax isn't documented
Hello Mark,
here some comments and maybe some help on your problems:
- there should be two other ways to get documents at the toplevel: one is to use the <index> element from the multi-layout version (see http://xweb.sourceforge.net/manual/advanced/layouts.html\), another one is to use targetDir="." as directory for one of the sections. The drawback of the latter is that all files (html, images) from this section will end up there
- the header and footer files are not processed at all -- I probably could easily add this, just file a feature request. Urgent?
- the xmlns and DOCTYPE issues are known problems, sorry -- no solution yet. "DOCTYPE directive" is AFAIK proper XML-speak.
- yes, to resolve internal references in the CSS you would have to create it via XSLT. The XSLT for this would be easy, though. It might add other useful things like being able to define colors for different things in one place (e.g. a parameter).
- the <homepage> is not documented, because I want to drop it ;-) Originally it seemed a good idea but by now I think using the first <entry> is as good and does keep things simple. Do you like the idea of the explicit section <homepage>? I think the notion that a click on a section button opens the first entry is more obvious.
Hope this helps at least a bit,
Peter
PS: if you have more feedback (which is highly appreciated), it might be a good idea to switch to the mailing list. Answering emails is easier than webforms. No real need, though.