StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>What about using <a href="https://developers.google.com/google-apps/documents-list/#creating_or_uploading_text_documents" rel="nofollow">Google Docs API</a>? You could use either their word-like doc or a form to get the data you need, and then present that internally. </p> <p>Not sure if this meets all of your requirements, or is an available option.</p> <p>For our company, we have a few tools that utilize Google Docs. We upload data dynamically to them for specific needs.</p> <p>Based on your requirements, maybe it's best to just write your own. I haven't created a Rich Text Editor. But it looks like there are quite a few tutorials online. Here is a <a href="http://www.dreamincode.net/forums/topic/246337-a-simple-text-editor-in-html-javascript-and-a-tiny-bit-of-css/" rel="nofollow">basic tutorial for a rich text editor</a>. It's using javascript, HTML, & CSS. If you prefer to not use js, then you may need to look for other tutorials.</p> <p>This isn't the most glamorous solution, as it looks like the users view would be HTML. I'd think you could have it updating dynamically off to the side with an actual rich text view (similar to how Stack Overflow has theirs below an answer or question being written). </p> <p><strong>Update</strong> Over the weekend I was exploring HTML5's <code>contenteditable</code> attribute, I came across an editor that builds off of that called <strong><a href="http://www.aloha-editor.org/" rel="nofollow">Aloha Editor</a></strong>. It's a WYSIWYG type editor. But if that's something that you desire for your clients, than this would probably be a pretty simple integration. I have yet to use it, but it seems like it would be a great fit - if you decide to go the route of building your own editor.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload