emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Mike Newman <mike@newmanfamily.me.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 5.13
Date: Wed, 24 Oct 2007 18:42:13 +0200	[thread overview]
Message-ID: <3BA1CB6B-5943-465C-A466-DA1B7BDC38F8@science.uva.nl> (raw)
In-Reply-To: <20071022223824.119eace4@newmanfamily.me.uk>

So, does everybody agree that I should remove the class from the divs  
again?

- Carsten

On Oct 22, 2007, at 11:38 PM, Mike Newman wrote:

> On Sat, 20 Oct 2007 11:30:29 +0100
> Bastien <bzg@altern.org> wrote:
>
>> Hello all,
>>
>> Carsten Dominik <dominik@science.uva.nl> writes:
>>
>>>     - The table of context is wrapped into a div with a class
>>>       "table-of-contents".
>>
>> This should be "id", not "class", since there is only one instance of
>> the table of contents - fixed in the proposed patch.
>
> I think that class is the right thing here.  We are saying that  
> this is
> a "table-of-contents" rather than this is the "table-of-contents".  I
> believe at present there is no mechanism to give more than one  
> table of
> contents, but someone, sometime might want tables of contents for
> individual sections of a document.
>
>>
>>>     - The outline structure is embedded in <div> elements with
>>>       classes "outline-1", "outline-2" etc.
>>
>> Classes are ok here.
>>
>
> This appears to be logical, but is in fact (I think) redundant.  We  
> can
> specify the style to applied at different levels without using
> class attributes.  For example:
>
>    div { background-color: lightgray}
>    div > div { background-color: peachpuff}
>    div > div > div { background-color: green}
>
> shows how different styling can be applied to level 1, level 2 and
> level 3 (and above).
>
> I think this has advantages (e.g. inheritance of unspecified
> characteristics from higher levels) and leaves the class attribute  
> free
> to represent styling that is independent of the structure.
>
> -- 
> Mike
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  parent reply	other threads:[~2007-10-24 16:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  6:25 Org-mode version 5.13 Carsten Dominik
2007-10-19 11:23 ` Adam Spiers
2007-10-19 15:11   ` Eddward DeVilla
2007-10-20 10:30 ` Bastien
2007-10-22 21:38   ` Mike Newman
2007-10-22 21:48     ` Nuutti Kotivuori
2007-10-22 22:50     ` Bastien
2007-10-24 16:42     ` Carsten Dominik [this message]
2007-10-25 11:12       ` Dmitri Minaev
2007-10-26 16:53         ` Mike Newman
2007-10-25 12:00       ` Nuutti Kotivuori
2007-10-23 19:26 ` Scott Jaderholm
2007-10-24  0:14   ` Bastien
2007-10-24  3:18     ` Carsten Dominik
2007-12-30 12:31 ` Adam Spiers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BA1CB6B-5943-465C-A466-DA1B7BDC38F8@science.uva.nl \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mike@newmanfamily.me.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).