On Monday, Jan 13, 2003, at 13:14 Europe/London, Hussein Shafie wrote:

> Jeremy Quinn wrote:
>>
>> An issue for us is the layout of 'main' and 'side' regions, side by
>> side.
>>
>> The XML:
>>
>> <doc>
>>         <section region="header">
>>                 <!-- header content -->
>>         </section>
>>         <section region="main">
>>                 <!-- main content -->
>>         </section>
>>         <section region="side">
>>                 <!-- sidebar content -->
>>         </section>
>>         <section region="footer">
>>                 <!-- footer content -->
>>         </section>
>> </doc>
>>
>> Gets transformed to <div/>s and laid out like this:
>>
>>         +---------------+
>>         |   head        |
>>         +---------------+
>>         +--------+ +----+
>>         |        | | s  |
>>         |  main  | | i  |
>>         |        | | d  |
>>         |        | | e  |
>>         +--------+ +----+
>>         +---------------+
>>         |   foot        |
>>         +---------------+
>>
>> In the browser, we use the CSS property 'float' to handle this.
>> (We don't use any HTML Tables, we prefer not to use Absolute
>> positioning, the CSS Table model is not reliably handled by most
>> browsers, so float is all we can use).
>>
>> I am wondering how we will be able to replicate this type of layout in
>> XXE.
>>
>> Float is not supported, and I cannot get CSS Table Model to work,
>> because we do not have enough tags to apply it to and XXE does not  
>> seem
>> to cope with 'anonymous tables'.
>>
>> Have you any suggestions?
>
> You have explained the problem very well: ``I cannot get CSS Table  
> Model
> to work because we do not have enough tags to apply it'' (unless you
> want to style <doc> as a table)
>

What I tried was this:

table {display:table}
section {display:table-column-group}
and
section {display:table-cell}

both attempts resulted in XXE switching to the Tree View, so I assumed  
that XXE does not handle 'anonymous tables'.

We have <chapter/> elements in the <sections/> though we cannot turn  
these into table-cell(s) as we would then get alignment problems ....  
each <section/> is able to have an arbitrary number of <chapter/>s.

So I guess I'm stuck on this one .... oh well, we can live with it ;)

> Therefore, for your types of documents, with XXE, you'll not be able to
> be as WYSIWYG as you want.
>
>
>
>> I have not tried absolute positioning yet ..... but without support  
>> for
>> 'width:' and 'height:' I suspected it was not going to work.
>
> No need to try it: absolute positioning is not supported.
>

OK

>
>
>> Even though this works in the xhtml demo, I cannot get "display:
>> marker;" to work on my list elements. Is there a special trick?
>
> Markers are drawn in the margin of a block. Therefore you must specify  
> a
> large margin for your list items to give room to the bullets.
>
> Example:
>
> li {
>     margin-left: 2.5ex;
> }
>
> li:before {
>     display: marker;
>     content: disc;
> }
>
>

Ah! Thanks for that!

>
>> New <p></p> on press RETURN, is something that works in the demos, but
>> I cannot get it to work on mine, any suggestions of what to look for?
>
> The Enter keystroke is bound to command called insertControlCharOrSplit
> (Menu "Help|Mouse and Key Bindings" displays this kind of information).
>
> This command is described in the Power User's Guide:
> http://www.xmlmind.com/xmleditor/_distrib/docs/poweruser/ 
> ar01s05s16.html
>
> This command will work with any DTD or XML-Schema provided that you  
> type
> Enter in a ``paragraph-like'' element (and, of course, it must not be
> styled using "white-space: pre;" because in such case, a newline
> character is inserted in the element.)

Hmmm, this is still not working for <p/>.
Could this be caused by the way I have written my XSD?

>> font-style: italic; does not seem to have any effect.
>
> There is no known bug related to "font-style: italic;" (this style is
> used quite often). But I remember that, a few months ago, with some
> fonts, on some platforms, "font-style: italic;" had no effect. Try to
> change the font families used by XXE to see if there is an effect (Menu
> Options|Options, Style tab).
>
> If not, may be there is a problem with your CSS.
>

OK, I'll try changing fonts.

Thanks for your replies.

regards Jeremy


Reply via email to