Interesting... but I don't see it... using firebug to un-hide the textarea I don't actually see any of the changes taking effect... If I change something in the text area and than save it is treated as though nothing happens...
<https://lh6.googleusercontent.com/-bpmpbJBc4zs/UbDoKrE72UI/AAAAAAAAAJU/sJKzIduODcw/s1600/2013-06-06_125030.png> When I change the document type on the other hand it updates the textarea, which dose tell me that it's storing somewhere else than syncing so it dose seem like there should be a way to simply make a "switch" that moves to and from the two which would than allow both the use of code mirror and the use of the quickeditbar. As an FYI I'm pretty adapted to wiki syntax so I don't use the QEB for things like basic formatting I instead use it as an easy access database for many snippets of code, ready-made layout pieces, and full on templates. Which I personally think is the real power of the QEB. So when I think about switching been the normal text area and the codemirror system I'm thinking the ability to be able to switch between "building" mode and visual mode. I suppose the easiest way to do this would be simply to start with the normal edit mode than back out and re-enter the codemirror edit mode, but I can't help but think there could be a very fairly simple way to simply the process and avoid having to break up workflow so much. Really making a simple javasript toggle to hide/show the normal text area and codemirror div is easy enough I just don't know how to force it to sync well doing it. On Thursday, June 6, 2013 11:52:31 AM UTC-7, PMario wrote: > > On Thursday, June 6, 2013 8:25:22 PM UTC+2, Arc Acorn wrote: >> >> It looks like the normal textarea is still around just hidden in >> codemirror mode, so would it be possible to reverse this and make a system >> where you could switch between the two and it would copy/replace the >> content from one to the other on switch? >> > :)))) > What you discribe here is exactly, what codemirror does. The hidden > textarea is still in use. When you open a tiddler it creates the cm-editor > by copying the "visible" stuff from the textarea to the highlighter. cm > only keeps about 100 lines of the text in the "editor". Imagine you need to > highlight 1000 lines and just see 30 of them. .... so the hidden text area > is the "cached text content" everything is synced back and forth. > > effectively adding a button to the normal view mode: [Switch to code view.] >> >> It seems like logically the way this would work is to not use the CmEdit >> or CmSave and instead simply have it as a layer on top () that could >> be switched from hidden to displayed (Which looks like you can already do, >> the content just doesn't interact with each other.) >> > There is super heavy interaction going on. As I said that's how codemirror > works :) > It would be less work to create cm aware EditButtons because cm has api > functions for this. > > >> and have the content of the textarea copied over, and when save is hit if >> the codemirror div is displayed have it's contents copied back over to the >> normal textarea and than save as normal. >> > Thats how cmEdit and cmSave works :) > > There is no problem, if you have cmEdit and editTiddler in the > ToolbarCommands tiddler. The whole stuff, just wasn't designed for this. It > may be confusing and atm imo it won't work. > > -m > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
