Also see Etherpad, ShareJS and Hackpad
Show HN: Real-time Wiki
31–40 of 54 posts
Re: Show HN: Real-time Wiki
#32This would be very popular indeed if a WYSIWYG editor was used instead of a markup language. There has been study after study showing how the wiki markup syntax is a hurdle to participation on wikipedia, to the point where wikipedia is now finally, after 12 years, working on a wysiwyg editor: http://techcrunch.com/2012/06/21/jimmy-wales-on-new-editing-... There are so many free and open source wysiwyg editors that ca…
We really need to get people out of the habit of using WYSIWYG editors.
Just stick them on reddit and they will learn markdown in a few weeks!
Re: Show HN: Real-time Wiki
#33Is there some Open Source solution in the similar spirit as document.ly? Would love this, but has to be running inside the company only.
Re: Show HN: Real-time Wiki
#34When I signed out of the application it didn't forward me to a logged-out verification page or give me a model that tells me I've signed out. It kind of just hung there without letting me edit anymore. When I sign out I like a very robust verification that tells me I've signed out. It looks great regardless.
Re: Show HN: Real-time Wiki
#35This would be very popular indeed if a WYSIWYG editor was used instead of a markup language. There has been study after study showing how the wiki markup syntax is a hurdle to participation on wikipedia, to the point where wikipedia is now finally, after 12 years, working on a wysiwyg editor: http://techcrunch.com/2012/06/21/jimmy-wales-on-new-editing-... There are so many free and open source wysiwyg editors that ca…
We really need to get people out of the habit of using WYSIWYG editors.
This is a very naive view of reality. WYSIWYG editors are superior in almost every way for almost all users. I used to force markdown on people too, but WYSIWYG is really a killer feature for most users. It requires far less learning, the features are more discoverable, it's quicker to edit even after they manage to become proficient with markdown, and there is no mental translation from what they're editing to what it's going to look like. But also other features that you might not immediately think of are very important, such as the ability to copy-paste from their existing word processor documents and preserve markup. Editing rich text with a plain text editor rather than a rich text editor is to most people like editing your photos with a hex editor instead of Photoshop is to you: not the right tool for the job, unpleasant, slow, requires learning, requires mental translation, and can't easily copy paste from existing material.
Re: Show HN: Real-time Wiki
#36This would be very popular indeed if a WYSIWYG editor was used instead of a markup language. There has been study after study showing how the wiki markup syntax is a hurdle to participation on wikipedia, to the point where wikipedia is now finally, after 12 years, working on a wysiwyg editor: http://techcrunch.com/2012/06/21/jimmy-wales-on-new-editing-... There are so many free and open source wysiwyg editors that ca…
We really need to get people out of the habit of using WYSIWYG editors.
Why? Garish formatting?
A really simple editor that only had the formatting options allowed by markdown would be functionally equivalent, and the great unwashed would find it much easier to use.
Re: Show HN: Real-time Wiki
#37The export feature would be really awesome if it could handle larger documents!
Also, sharing a document with someone else seems to throw an exception when they try to sign in...
Re: Show HN: Real-time Wiki
#38Earlier quoted context omitted.
We really need to get people out of the habit of using WYSIWYG editors.
This is a very naive view of reality. WYSIWYG editors are superior in almost every way for almost all users. I used to force markdown on people too, but WYSIWYG is really a killer feature for most users. It requires far less learning, the features are more discoverable, it's quicker to edit even after they manage to become proficient with markdown, and there is no mental translation from what they're editing to what…
It is comparable to the difference between digital cameras and film cameras. I see results sooner.
Sure, I can take good film pictures if I know the lighting conditions, shutter settings, business about f-stops but being able to see how you failed sooner is a big plus.
Re: Show HN: Real-time Wiki
#39Got past over-quota issue and gave google permissions, but Chrome OSX shows nothing when you login. JS console shows: Uncaught ReferenceError: goog is not defined socket.js:43 Uncaught Error: Load timeout for modules: text!templates/context_menu.html require.js:26 http://requirejs.org/docs/errors.html#timeout
Try refreshing... It's a non-optimized version so it doesn't always load right.
Same issue (3 hours later) but now I can't even load the page to logout :/
Re: Show HN: Real-time Wiki
#40Is this going to be freeium? I really recommend putting a pricing page up even if you don't know what the pricing will be, just to make it clear... hard to even try something (and I want to b/c it looks very useful) without knowing that important detail.