VoteOnNestedDivMarkup


PmWiki already supports a (:div1:), (:div2:), etc. syntax for nested divs... there have been proposals to add nesting capability with variants of the >>...<< markup.

Previous discussions are available at

Use this page to cast your opinion. Ideally put your name and vote weight for each option you have an opinion on; for example, "Pm +1" means Pm likes an option, "Pm -1" means Pm dislikes an option, "Pm +2" and "Pm -2" indicate a strong like or dislike, and "Pm 0" is a neutral vote. It's okay to leave short (one sentence) comments on each proposal, but please keep them short. Longer comments can go on the VoteOnNestedDivMarkup-Talk page.

Essentially we have three proposed options. These options are not mutually exclusive -- i.e., we could potentially implement two or more of them.

Option 1: Increased numbers of >'s indicate nesting markers, as in >>>...<<<

This would extend the existing >>...<< markup to allow >>>...<<<, >>>>...<<<<, etc. to indicate other levels of divs:

    >>foo<<       # outer div
    >>>bar<<<     # 1st nesting
    >>>>baz<<<<   # 2nd nesting

Votes:

  1. GNUZoo +2
  2. HansB +2
  3. Simon -2
  4. ScottConnard +1
  5. Hagan +2
  6. Kathryn Andersen +2
  7. Dfaure +1
  8. Roman +1
  9. TonyColley +1
  10. DaveG -2
  11. JonHaupt +2
  12. Blues +2
  13. Feral +1 -- This is consistent with header methodology, etc.
  14. PKHG +1
  15. NeI -2 -- Not EASY to read.
  16. Kellerfrau +2
  17. Luigi +1 -- This should be safe when including into another page, right?

Option 2: Add nesting markers as a prefix to >>...<<

For this option, an author could prefix >>...<< with digits to indicate nesting markers, as in 1>>...<<, 2>>...<<, etc.

    >>foo<<       # outer div
    1>>bar<<      # 1st nesting
    2>>baz<<      # 2nd nesting

Votes:

  1. GNUZoo -2
  2. HansB -2
  3. Simon -1
  4. ScottConnard -2
  5. Hagan -1
  6. Kathryn Andersen -2
  7. Dfaure -2
  8. Roman -2
  9. TonyColley -1
  10. DaveG +2 Against the trend, but this makes more sense to me
  11. JonHaupt -2
  12. Blues -2
  13. Feral 0 -- I no longer use this style.
  14. PKHG -2
  15. NeI -1 Cleaner than 1, not clean enough though

Option 3: Add nesting marker inside of >>...<<

This is a variation on the above, where any nesting marker appears immediately inside the first >>, as in >>1 ...<<, >>2 ...<<, etc.

    >>foo<<       # outer div
    >>1 bar<<     # 1st nesting
    >>2 baz<<     # 2nd nesting

Votes:

  1. GNUZoo -2
  2. HansB +1
  3. Simon +2
  4. ScottConnard +1
  5. Hagan +1
  6. Kathryn Andersen +0
  7. Dfaure +2
  8. Roman +2
  9. TonyColley +2
  10. DaveG +1
  11. JonHaupt +1
  12. Blues 0
  13. Feral +2 -- Counting angel brackets is a pain so I prefer this to option 1.
  14. PKHG +2 agree to Feral's meaning
  15. NeI +2 Agree with Feral; tho I think >>foo 1<< >>bar 2<< would be still easier to read.

Combining two or more of the above

If anyone is strongly in favor or opposed to implementing more than one of the above options, register your vote/comments here.

1 and 3

Votes

  1. HansB +1
  2. Hagan +1
  3. Kathryn Andersen +1
  4. Dfaure +2
  5. Roman +1
  6. TonyColley -1
  7. JonHaupt +1
  8. Blues 0
  9. Feral 0
  10. PKHG +1 tasts are different ;-)

Implement only one option

Votes

  1. Simon +2
  2. ScottConnard +2
  3. Kathryn Andersen +2
  4. Dfaure +1
  5. TonyColley +2
  6. DaveG +2
  7. Blues +1
  8. Feral +1 -- Less confusion is probably a good idea;
  9. PKHG 0 because I am a newbie to PmWiki
  10. NeI +2 There shall be only ONE! What use are two? None!
  11. Kellerfrau +2

Side Comments

Keep side comments here short... for longer comments, use the VoteOnNestedDivMarkup-Talk page.

My personal thought is that >><< for a end to end style as we have, if we want numbers use the div directive, and if we want id less and nestable, then something like >>><<<; (PITS:00887#Proposal2). I have more thoughts on this on the Talk page.

Feral April 18, 2007, at 10:28 PM
 0: 00.00 00.00 config start
 1: 00.00 00.00 config end
 2: 00.03 00.02 MarkupToHTML begin
 3: 00.04 00.03 ReadApprovedUrls SiteAdmin.ApprovedUrls begin
 4: 00.04 00.04 ReadApprovedUrls SiteAdmin.ApprovedUrls end
 5: 00.07 00.07 MarkupToHTML end
 6: 00.08 00.07 MarkupToHTML begin
 7: 00.09 00.08 MarkupToHTML end
 8: 00.09 00.08 MarkupToHTML begin
 9: 00.09 00.09 MarkupToHTML end
10: 00.09 00.09 now
Peak memory: 3,178,864 bytes