(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-8) was last changed on 23-Sep-2008 00:22 by JohnMcClure  

This page was created on 15-Sep-2008 03:40 by StephenDay

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 changed 4 lines
==Some ideas for global attributes (id and class).
Here is an example usage with link markup:
== [[http://textism.com/tools/textile| Approach #1]]
Here is an example usage with link markup and could be applied to any inline creole (links, bold, italics, etc.):
At line 6 changed 5 lines
[[{.someclass}http://google.com|This is a link with a class attribute "someclass"]]
[[{#someid}http://google.com|This is a link with an id]]
[[{#someid.someclass}http://google.com|This is a link with a class and id!]]
1. [[{.someclass}url|label]]
2. [[{#someid}url|label]]
3. [[{#someid.someclass}url|label]]
At line 12 changed 3 lines
The above could be applied to any inline creole (links, bold, italics, etc.). Block markup becomes more complicated:
Block markup becomes more complicated:
At line 16 changed 7 lines
|{.someclass} Does this class apply to the table, row, or cell | There doesn't seem to be an easy way |
Paragraphs, on the other hand, are pretty straight forward:
{.indent}Here is my paragraph with class="indent"!
Tables:
|{.someclass}cell content|
Paragraphs:
{.someclass}graf content
At line 15 added 5 lines
* Does the class in the table example apply to the table, row, or cell?
\\-- [[StephenDay]], 2008-Sept-15
----
Hi Stephen (hope my editing is ok with you!)\\The general Creole design seems to be 2+ delimiters for most things so as to distinguish markup from (unusual) text content, so I disagree with {...} at the start of a paragraph (graf). I also don't like having just one-or-none css classes, so I disagree with {#id.class}. Maybe that could be accommodated by {#id.class1.class2...} but then it starts looking strange to my eye. I think I'd prefer //explicitly// identifying classes as the value of a named argument, e.g., +class=, so as to have by default, an open-ended ability to add attributes.
\\--[[JohnMcClure]]
At line 25 removed one line
These ideas come from http://textism.com/tools/textile (although not verbatim)
At line 27 changed 4 lines
-- [[StephenDay]], 2008-Sept-15
----
For links, I have proposed at [Talk.Link Extensibility Proposal] to reserve the first positional for specification of an xml:id.
== [[Talk.Link Extensibility Proposal| Approach #2]]
For links, reserve the first positional for specification of an xml:id.
At line 29 added one line
\\-- [[JohnMcClure]]
At line 37 changed 4 lines
-- [[JohnMcClure]]
JohnMcClure said "... Personally I favor the solution that blank_line=paragraph_begin_OR_end... and I favor a distinct paragraph_start character pattern that allows the specification of an id for the generated <p> plus any other XHTML attribute(s)"
== More discussion ==
Personally I favor the solution that blank_line=paragraph_begin_OR_end... and I favor a distinct paragraph_start character pattern that allows the specification of an id for the generated <p> plus any other XHTML attribute(s)"
\\-- [[JohnMcClure]]
----
At line 38 added 3 lines
\\-- [[StephenDay]] 2008-Sept-19
----
I agree with your view that consistency is key. And I don't like the [[Creole Additions|indented paragraph suggestion]] either (for several reasons). I think the single */# for lists is not a 'regular case' because the number of such chars relates to the level of the listitem, not to whether it is a block or not.
At line 45 changed 2 lines
-- [[StephenDay]] 2008-Sept-19
IMO I'd like to see //inline-//lists be distinct from //block-//lists by virtue of the latter being preceded by an empty line, just as for paragraphs -- users would readily understand that I think. Thus, the "empty line" is my choice for a general, minimalistic indication of a subsequent text block, although that approach is probably contradicted in Creole 1.0 syntax, e.g. table and hx, and by certain suggestions (like block quote) that do not have such requirement. Maybe those can conform to this approach, in 2.0.
That said, I think a graf tag (to which XHTML id/attrs are attached) should simply be the NL tag(!) -- easily detected by the presence of __a required__ xml:id &/or attrs specification (else it is translated to a <br/> element). Thus, the para tag with id/attrs would be
{{{
\\.id1: +attr1=val-1 val-2 +attr2=val-n... (comment)
Here is the content of a graf.
\\.id2: +attr1=val-1 ... (comment)
Here is the content of the next graf.
}}}
Simple enough?
\\--[[JohnMcClure]]
Version Date Modified Size Author Changes ... Change note
8 23-Sep-2008 00:22 4.204 kB JohnMcClure to previous
7 22-Sep-2008 22:33 4.204 kB JohnMcClure to previous | to last
6 22-Sep-2008 22:10 3.918 kB JohnMcClure to previous | to last
5 22-Sep-2008 22:08 3.925 kB JohnMcClure to previous | to last Response to Stephen Day
4 20-Sep-2008 01:34 2.533 kB 96.20.127.193 to previous | to last note about explicit paragraph markup
3 15-Sep-2008 18:59 1.645 kB JohnMcClure to previous | to last
2 15-Sep-2008 03:42 0.82 kB StephenDay to previous | to last some ideas for id and class attributes
1 15-Sep-2008 03:40 0.815 kB StephenDay to last Suggestion for class and id attributes
« This page (revision-8) was last changed on 23-Sep-2008 00:22 by JohnMcClure