fbreuer / qute-html5 Goto Github PK

for example ctrl+up and ctrl+down

this is probably caused by the behaviour of copy in Firefox. \n is ignored, and
is translated as newline.

the workaround is to handle ctrl-c manually. but that can wait.

I was wondering if there could be some global css options.

For example, the blockquote styling is too soft for me (I like having a slightly different background color).

I know I should probably just hack the themes, but I'd love to have your expertise on this. Do you think some global overrides for css-options could make sense (eg. ul, blockquote, headings)?

It is desirable to extend Qute's Markdown capabilities beyond what Showdown is currently offering, perhaps by including some Pandoc extensions.

Qute 0.5 will allow users to switch between different compilers/translators: Users may choose which "plugin" they use to transform the markup content of a paragraph into a fully-rendered "preview". This makes it easy to experiment with different Markdown processors.

Currently I see three possible approaches towards extending the Markdown syntax supported by Qute:

Extend the Showdown library currently in use, by hacking showdown.js directly.

This is possible, now that Showdown and MathJax coexits peacefully!

PRO:

• Incremental style of development.
• Should yield results relatively quickly.

CON:

• showdown.js is a collection of regular expressions!
• Hard to understand.
• Hard to maintain.

Use Pandoc as processor.

PRO:

• Guarantees consistency with what Pandoc does.
• Somebody else does (or already did) the work for us!

CON:

• Should we bundle Pandoc with Qute? (Not necessary, this plugin could be optional.)
• Performance? Running pandoc as a separate process for every transformation of a paragraph seems excessive.

Write Markdown processor from scratch, using OMeta.

PRO:

• OMeta will be integrated in Qute 0.5 anyway -> consistent solution.
• Provides the user with a uniform mechanism for extending/customizing the syntax. (Creating custom Markdown flavors! This is TeX macros done right!)

CON:

• Reimplementing a Markdown processor with OMeta will be a lot of work with a steep learning curve. (Would be a great exercise though.)
• Places an additional maintenance burden on us.

Thanks to the planned plugin architechture it is perfectly feasible to try all three of these options simultaneously: The current Showdown-based compiler would be the default. Pandoc could be a (easy to write) plugin for users who need syntax extensions and do not care about performance. And the OMeta plugin would be a highly experimental testing ground for people who want to learn how to define their own syntax and write their own compilers.

add an option to create a backup of the document before saving.

should work (almost) out of the box (with the appropriate css stylesheets).

however, chromeless has trouble showing dialog windows?

this appears to be caused by xulrunner's performance when rendering text shadows. (is it just me or did xulrunner become even slower in this regard since version 6?)

as a workaround you may try to use the plain black and white themes.

One of the big conflicts I continuously see between markdown and mathjax are backslashes. LaTeX needs them, markdown considers them escape characters. So when I write something like ${ x : x< 0 }$, it will be rendered like $x: x<0$ would be.

Usually, I use backticks to force markdown to ignore TeX code. But for some reason this stopped working in Qute (although I don't know for sure if it worked with earlier versions). So now enclosing math in backticks prevents mathjax rendering.

What can we do about it? Is it just that mathjax adheres to skipping <code>? (I know you used to do that in your site's mathjax, but I can't see it in Qute's files)

Can we teach markdown to consider $ to be an escape character? (won't solve anything, I think)

E.g. "<" is exported as "<" which MathJax does not process properly.

This is caused by running first MathJax and then Showdown on the document.

I do not think I will fix this before the 0.4 release.

Undo/redo functionality is unreliable. Most times, it's lost as soon as a new pagraph is formed, sometimes it isn't. Should be cross paragraph, imho.

Ok, not really an issue, more a choice of font remark.

• The | is not unusual in design, but I dislike it in my texts.
• The apostrophe is very odd looking/placed, especially in mathjax.

The Garamond/Junicode combo has a good apostrophe except in mathjax; everything else is strange..

add Scrivener-style outlining in a sidebar

• ctrl+T should also re-enter editing mode
• There should be more ways to enter editing mode if accidentally dropped out of it.
• clicking on the margin does not get into editing mode, one needs to click on the text.
• double click on end of line to leave/enter editing mode should be documented.

Currently, Qute relies on Chromeless' builtin handling of undo/redo in contentEditable paragraphs.

Naturally, this produces unexpected results as soon as paragraphs have been switched. In particular, changes made by the undo operation to the source code of paragraphs that are currently in display mode are invisible until the paragraph is switched again. Is there a way to hook into Chromeless' undo mechanism and trigger transformations of the source whener changes are made?

I'm currently working on a document that needs a lot of moving-text-around. This is essentially impossible with qute right now since I cannot copy or cut multiple paragraphs.

From what I understand, this is hard for the default view because of your design decision (unless you find a fancy way to have copy/cut actually grab the source, not the rendered material).

But it could be helped in split-view if you abandoned the paragraph separation there, i.e., have a "normal" text window.

What do you think?

Undo/redo functionality is unreliable. Most times, it's lost as soon as a new pagraph is formed, sometimes it isn't. Should be cross paragraph, imho.

compiling instructions are lacking.

compiling scripts should be extended to also handle copying of license, etc. ideally also dowloading of chromeless and mathjax.

compiling script should be ported to other platforms.

If I hit enter fast twice, qute drops out of editing mode and I have to click back into a line to edit again.

Needless to say that sucks ;)

standard keybindings be bound to cmd on mac and ctrl on other systems.

Paragraphs can't be deleted, can't be split into two parts and cannot be joined.

for completeness.

I mostly miss cmd+q for quitting -- having to quite with the mouse is cumbersome since one first has to leave fullscreen mode and then click the red dot.

I'm sure there's a set of regular commands users would expect (but then again, I don't use macos as my primary system).

I noticed that the desk-theme has white hyperlinks -- white on white that is...

Also, in split view the entire background is white. I don't know if there's a solution for that -- I guess the theme tries to imitate paper on wooden desk but in split view it's two paper next to each other and no room to see the desk.

Peter requested an optional two column view. maybe this is possible without too much trouble?

When I paste text , the next time I hit del or backspace, the cursor will do del/backspace at at the end of the line, not where it's actually at.

Sometimes, writing some more stuff helps, but not always. I thought it had something to do with the preview, but even switching paragraphs does not prevent this -- the next time I get back to the paragraph I pasted into, the first del/backspace will happen to the end of the line.

That is really annoying :(

Could there be keyboard navigation in the menu? Or keyboard commands to access the different menu commands.

I just noticed the following: if I do a markdown code block with 4 white spaces, the preview breaks: the text in the code block is displayed without any line break.

I can reproduce this reliably in two-pane mode, but in single window mode it is more erratic -- sometimes having a consecutive line in the paragraph prevents the code block and thereby the breaking...

notify("one"); notify("two"); notify("three"); will display "three" three times.

pandoc integration would be desirable for various reasons. especially because printing does not really work, due to bugs in gecko (disappearing math characters).

the plan: add a "compile with pandoc" publishing option that only works if the user has pandoc installed.

if the implementation is as quick and easy as I think, this should be done for 0.4. otherwise after 0.5.

if the document has not been saved, Qute should ask if the user wants to save his text before allowing the operating system to close the window.

I'm finding that when I paste some Markdown into Qute, it isn't parsed properly.

The presence of newlines in the paste buffer appears to confuse the Markdown processor - if I paste a line that doesn't contain newlines it works fine, but if I paste a longer chunk, the text appears but when I double-click it disappears.

Platform: MacOS 10.6, version July 1, 2011

using linux binaries on ubuntu 11.04

Apologies for the vagueness -- I haven't found a way to reproduce this effectively.

This is all in single column mode

• Sometimes, when I edit a paragraph and switch to a different paragraph with the mouse, the first one does not switch back to preview. Switching back and forth with the keyboard corrects this.
• Sometimes, qute leaves editing mode after a few seconds of inactivity. That's actually nice (if intended), but typing does not get you back into editing mode. ctrl+up/down does get you into the surrounding paragraphs -- but that's not very optimal when editing a longer paragraph...
• Sometimes, changes do not show up in preview. Switching to two column view and back seems to correct this.