From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Re: Getting checkboxes in HTML output?
Date: Fri, 29 Nov 2013 13:59:30 -0500 [thread overview]
Message-ID: <5298E412.1040009@pfdstudio.com> (raw)
In-Reply-To: <16f7d77c0769177de44354bcf25abb37@mail.rickster.com>
On 11/29/13, 11:11 AM, Rick Frankel wrote:
> On 2013-11-28 16:58, Matt Price wrote:
>> On Thu, Nov 28, 2013 at 4:26 PM, Sebastien Vauban
>> <sva-news@mygooglest.com> wrote:
>> Achim Gratz wrote:
>> Rick Frankel writes:
>> For xhtml compatibility, it would need to be 'checked="checked"'. I've
>> done a quick look at the html dtd, and i does look like input elements
>> are allowed outside of forms, but i would need to double
>> check... Also, the fallback to "[-]" for the partially checked state
>> is a bit inconsistent, perhaps changing background color or other
>> attributre of the checkbox would be better.
>>
>> I'd much prefer if you'd be using character entities for that since you
>> can't do any input on the HTML anyway (WHITE MEDIUM SQUARE, SQUARE WITH
>> LOWER RIGHT DIAGONAL BLACK and BLACK MEDIUM SQUARE look like good
>> candidates). That probably makes it UTF-8 only since I don't think
>> these symbols are defined for plain (X)HTML, so for other encodings
>> things should probably stay as they are.
>>
>> FWIW, here's what I do for the HTML export:
>>
>> In JS:
>>
>> #+begin_src js
>> $(function () {
>> $('li > code:contains("[X]")')
>> .parent()
>> .addClass('checked')
>> .end()
>> .remove();
>> $('li > code:contains("[-]")')
>> .parent()
>> .addClass('halfchecked')
>> .end()
>> .remove();
>> $('li > code:contains("[ ]")')
>> .parent()
>> .addClass('unchecked')
>> .end()
>> .remove();
>> });
>> #+end_src
>>
>> In CSS:
>>
>> #+begin_src css
>> li.checked {
>> list-style-image: url('../images/checked.png');
>> }
>>
>> li.halfchecked {
>> list-style-image: url('../images/halfchecked.png');
>> }
>>
>> li.unchecked {
>> list-style-image: url('../images/unchecked.png');
>> }
>> #+end_src
>>
>> with 3 nice pictures of green V, red X, and blue || (line "pause" on
>> recorders).
>>
>>
>>
>> so, I don't know if I'm the only one here who feels this way, but I
>> would like to be able to export to an HTML file with ACTUAL HECKBOXES
>> that I cna check off, say on a phone, when I put the milk in the
>> shopping art, or pack the swim goggles in the vacation bag, or
>> whatever. Maybe though I should be thinking in terms of some other
>> export application, remember the milk or something. Am I describing a
>> different use case than other users here, perhaps?
>
> My 3 cents:
>
> I don't see that active checkboxes would help since i don't see a use
> case where you can save the html back with the modified input. The
> github usecase mentioned in anothre thread requires a bunch of
> javascript to work (and write-out the modified file).
>
> While Sebastien's solution is visually appealing, i don't think
> requiring image assets is viable for the core exporter (note that it
> could be done w/o javascript, another dependency i would like to
> avoid).
>
> I've attached an html file which shows the various possible options. My
> comments:
>
> 1. As mentioned above, I don't see active checkboxes as useful
> since the modified state is transient.
> 2. I don't really like the disabled checkboxes visually.
> 3. Either of the other two approaches (the list item style, which
> parallels Sebastien's approach w/o using images) works for me.
> Visually I like the list item style solution, but doesn't really
> make the intent clear.
>
> So, my vote is to change the exporter to use the BALLOT BOX and BALLOT
> BOX WITH CHECK instead of the ascii character currently used and
> indicate partially checked boxes ([-]) with greyed text.
>
> Opinions?
>
> rick
>
Thanks for the handy comparison page, Rick. Visually, I'm happy with
either actual HTML <input ...> checkbox elements or the Unicode BALLOT
BOX and BALLOT BOX WITH CHECK characters. Semantically, I suppose it's
better to avoid having active input elements, since, as you point out,
they're completely transient, and so potentially misleading.
Unfortunately, I don't think any of the "partial" options is very clear.
They graying out is not particularly clear. But I could live with it if
no better alternatives are found.
-pd
--
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com
next prev parent reply other threads:[~2013-11-29 18:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 15:45 Getting checkboxes in HTML output? Peter Davis
2013-11-27 16:03 ` Nick Dokos
2013-11-27 18:20 ` Peter Davis
2013-11-28 13:33 ` Rick Frankel
2013-11-28 13:55 ` Peter Davis
2013-11-28 16:08 ` Bastien
2013-11-28 17:03 ` Matt Price
2013-11-28 20:51 ` Achim Gratz
2013-11-28 21:26 ` Sebastien Vauban
[not found] ` <CAN_Dec9a5v2rqQSvAKpvgLWKsTY8YLoMSvKbtkgak77Bb=nbAg@mail.gmail.com>
2013-11-28 21:58 ` Matt Price
2013-11-29 16:11 ` Rick Frankel
2013-11-29 18:59 ` Peter Davis [this message]
2013-11-30 6:54 ` Carsten Dominik
2013-11-30 14:07 ` Rick Frankel
2013-12-01 6:46 ` Carsten Dominik
2013-12-02 8:44 ` Sebastien Vauban
2013-12-02 16:38 ` Peter Davis
2013-12-03 1:11 ` Nick Dokos
2013-12-03 12:29 ` Peter Davis
2013-12-03 15:03 ` Rick Frankel
2013-12-03 15:24 ` Sebastien Vauban
2013-12-03 16:56 ` Peter Davis
2013-12-03 15:14 ` Rick Frankel
2013-11-29 1:47 ` Eric Abrahamsen
2013-11-28 14:30 ` Waldemar Quevedo
2013-11-28 14:41 ` Waldemar Quevedo
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=5298E412.1040009@pfdstudio.com \
--to=pfd@pfdstudio.com \
--cc=emacs-orgmode@gnu.org \
/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).