You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oh, weird. I can't click on your tasks at all. they're read only. Probably because, I'm assuming, when you check one it sends an edit XHR request and adds an "X" inside the bracket.
Yeah, you're right, that's very github specific. It generates checkboxes without a form. List items with certain data attr's and classes, catering to githubs specific stylesheet. Not to mention the js which adds the dynamic behavior. I see this as being really hard to standardize. ...maybe if they were renamed to just "GFM checkboxes" instead of "todo lists", since the "todo" list part entails the dynamic behavior.
edit: Anyway, I'll leave this open if anyone else wants to comment.
I like the idea to simply render checkboxes using this markup. In app you can add event handler to manage specific behaviour. [ ] a task list item just parses to label with input. What do you think? Also we could think about wrapper around this checkboxes.
But it would require a new markdown format for checkboxes, which is non standard even in gfm mode.
I.e. [ ] for unchecked and [x] or [v] for checked
Could be nice for showing todo lists with static marks..
I think this actually is useful, even in contexts where an HTML checkbox doesn't make sense.
+1 for generating unicode characters as in here and here.
In non-HTML environments, editors could choose to draw them as a bulleted list with strikethroughs for completed items.
I've been hoping for someone to cross Taskpaper's text-based todo lists with Markdown for a little while, and this seems a little more user-friendly. Taskpaper requires you to add an @done tag to the end of each line, which makes scanning plaintext to see what is done w/o syntax highlighting somewhat difficult. The GFM syntax is arguably more readable.
Yes, Github uses this feature to power some crazy custom features for Github Issues, but it's also generally useful.
Note: in GFM, [ ] (or [x]) has to be in the very beginning of a list item. (Only a whitespace may happen between the checkbox and the preceding bullet.) Bullets are not displayed for these lists (even for their items that do not start with checkboxes).
GitHub has announced (in June 25) that task lists are supported in gists as well as in repositories.
This announcement widens (and generalizes) the area of their application, making more reasonable to support these lists in GFM-flavoured mode of marked.
I'm curious, though. If you do this, and there's no commensurate back-end to handle them, what good are they besides eye-candy? In Github, there is a running JavaScript observer waiting for you to click one of these, and backing that choice to a persistence layer somehow. Marked doesn't provide that, so who will?
Walter
On Jul 3, 2013, at 1:33 AM, Mithgol wrote:
A week ago GitHub announced that task lists are supported in gists as well as in repositories.
This announcement widens (and generalizes) the area of their application, making more reasonable to support these lists in GFM-flavoured mode of marked.
—
Reply to this email directly or view it on GitHub.
and there's no commensurate back-end to handle them
@walterdavis Marked doesn't provide any backend service at all. All it does is parse out HTML. Without a backend you can't save anything anyway. Even if it's just an H1, it doesn't persist in any way.
Right. That was my understanding as well, and I was asking to make the point that adding the GFM checkboxes only does half the job.
Walter
On Jul 3, 2013, at 12:37 PM, Oscar Godson wrote:
and there's no commensurate back-end to handle them
@walterdavis Marked doesn't provide any backend service at all. All it does is parse out HTML. Without a backend you can't save anything anyway. Even if it's just an H1, it doesn't persist in any way.
—
Reply to this email directly or view it on GitHub.
I use icons from fontawesome, but can just use html checkbox simply, of course. Don't remember to create you own marked.Renderer instance and make config right.
Activity
chjj commentedon Jan 10, 2013
Just testing so I can see the HTML.
OscarGodson commentedon Jan 10, 2013
Oh, weird. I can't click on your tasks at all. they're read only. Probably because, I'm assuming, when you check one it sends an edit XHR request and adds an "X" inside the bracket.
chjj commentedon Jan 10, 2013
Yeah, you're right, that's very github specific. It generates checkboxes without a form. List items with certain data attr's and classes, catering to githubs specific stylesheet. Not to mention the js which adds the dynamic behavior. I see this as being really hard to standardize. ...maybe if they were renamed to just "GFM checkboxes" instead of "todo lists", since the "todo" list part entails the dynamic behavior.
edit: Anyway, I'll leave this open if anyone else wants to comment.
alekseykulikov commentedon Jan 10, 2013
I like the idea to simply render checkboxes using this markup. In app you can add event handler to manage specific behaviour.
[ ] a task list itemjust parses to label with input. What do you think? Also we could think about wrapper around this checkboxes.TheCloudlessSky commentedon Jan 15, 2013
IMO - something like this would be good as an extension.
leeoniya commentedon Jan 17, 2013
another option maybe would be to render them as unicode entities since there's no implied interaction...
http://www.fileformat.info/info/unicode/char/2610/index.htm
http://www.fileformat.info/info/unicode/char/2611/index.htm
velsa commentedon Jan 17, 2013
But it would require a new markdown format for checkboxes, which is non standard even in gfm mode.
I.e.
[ ]for unchecked and[x]or[v]for checkedCould be nice for showing todo lists with static marks..
jessmartin commentedon Jan 21, 2013
I think this actually is useful, even in contexts where an HTML checkbox doesn't make sense.
+1 for generating unicode characters as in here and here.
In non-HTML environments, editors could choose to draw them as a bulleted list with strikethroughs for completed items.
I've been hoping for someone to cross Taskpaper's text-based todo lists with Markdown for a little while, and this seems a little more user-friendly. Taskpaper requires you to add an @done tag to the end of each line, which makes scanning plaintext to see what is done w/o syntax highlighting somewhat difficult. The GFM syntax is arguably more readable.
Yes, Github uses this feature to power some crazy custom features for Github Issues, but it's also generally useful.
Mithgol commentedon Feb 19, 2013
Note: in GFM,
[ ](or[x]) has to be in the very beginning of a list item. (Only a whitespace may happen between the checkbox and the preceding bullet.) Bullets are not displayed for these lists (even for their items that do not start with checkboxes).Mithgol commentedon Jul 3, 2013
GitHub has announced (in June 25) that task lists are supported in gists as well as in repositories.
This announcement widens (and generalizes) the area of their application, making more reasonable to support these lists in GFM-flavoured mode of marked.
walterdavis commentedon Jul 3, 2013
I'm curious, though. If you do this, and there's no commensurate back-end to handle them, what good are they besides eye-candy? In Github, there is a running JavaScript observer waiting for you to click one of these, and backing that choice to a persistence layer somehow. Marked doesn't provide that, so who will?
Walter
On Jul 3, 2013, at 1:33 AM, Mithgol wrote:
Mithgol commentedon Jul 3, 2013
An eye-candy would already be as good as on GitHub where you cannot click other people's task lists (unless you are an owner of the repo).
OscarGodson commentedon Jul 3, 2013
@walterdavis Marked doesn't provide any backend service at all. All it does is parse out HTML. Without a backend you can't save anything anyway. Even if it's just an H1, it doesn't persist in any way.
walterdavis commentedon Jul 3, 2013
Right. That was my understanding as well, and I was asking to make the point that adding the GFM checkboxes only does half the job.
Walter
On Jul 3, 2013, at 12:37 PM, Oscar Godson wrote:
rough implementation of task lists. see #107 #111.
12 remaining items
Github Task Lists
jhollingworth commentedon May 6, 2015
I've just opened #587 which should resolve this issue
Github Task Lists
rough implementation of task lists. see markedjs#107 markedjs#111.
use renderer for task lists. see markedjs#107 markedjs#111.
Revert "use renderer for task lists. see markedjs#107 markedjs#111."
Revert "rough implementation of task lists. see markedjs#107 markedjs…
Github Task Lists
jungor commentedon Feb 6, 2017
This works for me...
I use icons from
fontawesome, but can just use html checkbox simply, of course. Don't remember to create you ownmarked.Rendererinstance and make config right.joshbruce commentedon Dec 3, 2017
#952
joshbruce commentedon Dec 3, 2017
Closing as it appears a fix was merged, but may not be working.