The requested info ie:
I have no idea how but could these 'headers' be "protected" or 'tabbed' maybe so they cannot be overwritten to keep readability ?
Michael answered this on CMS-list: "I think it would be possible if we split them into separate fields then the save action compiles it into the single description field that it has to go into on GitHub"
Right, it would be separate text areas and/or editors (can the markItUp editor handle multiple instances on one page?).
According to the documentation here
http://markitup.jaysalvat.com/documentation/
I think markitup can handle multiple instances on one page ;)
Cheers,
Allen
在 2014年3月9日,上午12:23,Michael Babker notifications@github.com 写道:
Right, it would be separate text areas and/or editors (can the markItUp editor handle multiple instances on one page?).
—
Reply to this email directly or view it on GitHub.
Sounds interesting. Do we want them to be tabbed?
I think for accessibility reasons, tabs aren't very friendly. But, that does help keep the screen cleaner.
Agree that not so friendly, but otherwise we will have huge screen with multi editors...
And when there will be a screen with several editors (whenever tabs or not) how then an upload form should work? Currently it is tied to one of the textareas to make a markdown code for the uploaded images. If there will be more textareas it won't be possible to tie it to all of them...
I think I've mentioned that earlier, and you can see about that on the page, the markdown editor we are using now is capable of multiple text areas
Cheers | 顺颂时祺
Allen Zhao | 赵泽涵
在 2014-3-12,15:21,Dmitry Rekun notifications@github.com 写道:
And when there will be a screen with several editors (whenever tabs or not) how then an upload form should work? Currently it is tied to one of the textareas to make a markdown code for the uploaded images. If there will be more textareas it won't be possible to tie it to all of them...
—
Reply to this email directly or view it on GitHub.
I think you did not understand me. I am talking about upload form which is not a part of the editor.
Oh, sorry. But I think one form can still handle that, by adding all the contents together before submitting to the server. Does that make sense?
Cheers | 顺颂时祺
Allen Zhao | 赵泽涵
在 2014-3-12,18:50,Dmitry Rekun notifications@github.com 写道:
I think you did not understand me. I am talking about upload form which is not a part of the editor.
—
Reply to this email directly or view it on GitHub.
Does make sense, but again I am talking about the different thing. Imagine that you have several textareas and want to upload an image. When you upload it the script generates a markdown code and inserts it inside the textarea. But how this script can decide to which textarea it should insert that code? We should pass some ID of the textarea to the script, but it is not possible to do. If you will find the way then no problem :)
The document of Markitup says we can get the textarea object using a callback function, but now the upload function is outside the editor, so can we move the function into the editor, make it a button or so then it can get the current textarea the user is editing
But that sounds a little bit hard to implement ;(
| Labels |
Added:
enhancement
|
||
| Labels |
Added:
UI
|
||
Seems that this feature is not so interesting for community. Closing for now.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-10-22 08:07:55 |
I think Michael's idea is good. And by split them into sparate fields does this mean different text areas?