Feng Forum
Other Topics => Ideas => : neuron November 08, 2009, 07:30:29 AM
-
http://closure-library.googlecode.com/svn/trunk/closure/goog/docs/index.html
Now I haven't looked into the specifics, but from the screenshot and text it looks like the normal google docs editor.
It even has "table" and "insert" as menu items.
-
The Closure Library is a JavaScript library. It may include an editor component but it would be just a front-end. It would lack server-side functionality like concurrent edition, exporting/importing to/from other formats, etc. Without all that I don't think there would be much difference with the editor we are using today, so it wouldn't be worth to add a whole new library. What do you think?
I haven't looked into the specifics either, so I could be wrong.
-
Yeah it's more than likely missing import/export, but in my experience the editor your using now is very html based, it doesn't have the text document "feel" to it. Enter does what a linefeed would in html, not what it would do in a text document, etc.
Now of course it depends entirely on how much of the editor is actually there, and I seriously doubt it's much more than a basic rtf editor. It'd be very cool if it had tables support though.
-
Yeah it's more than likely missing import/export, but in my experience the editor your using now is very html based, it doesn't have the text document "feel" to it. Enter does what a linefeed would in html, not what it would do in a text document, etc.
We are on the web, aren't we? It must be HTML based.
I think the key to enhance it is the export functionality, not the editor itself.
Of course you can have XML instead of HTML, but HTML is easier when we are working on the web.
-
Yeah it's more than likely missing import/export, but in my experience the editor your using now is very html based, it doesn't have the text document "feel" to it. Enter does what a linefeed would in html, not what it would do in a text document, etc.
We are on the web, aren't we? It must be HTML based.
I think the key to enhance it is the export functionality, not the editor itself.
Of course you can have XML instead of HTML, but HTML is easier when we are working on the web.
We are on the web, but that doesn't mean it must feel like a web document/web editor. For example in a document enter would mean linefeed, in the web based editor shift+enter is a linefeed. It's not much, but it's small things like that that make it seem like your editing a web page and not a document.
-
Our editor can be configured to treat ENTER as a regular line feed instead of a new paragraph. In fact, when composing an email ENTER behaves like that. Do you think it should also behave that way for documents?
-
Our editor can be configured to treat ENTER as a regular line feed instead of a new paragraph. In fact, when composing an email ENTER behaves like that. Do you think it should also behave that way for documents?
Yes, I defenatly do. If your editing a document, it's the behavior you'd expect.
This is going slightly off topic, looking over the page it looks to be considerably more basic than I was led to believe. Got the link from an article talking about their document editor along with a link to the now open source library.
-
What user expects is not what best accomplish the solution. If you change the behaviour of the editor, you are creating bad semantic HTML code, and that would get bad export options.
WYSIWYG editors overlook the neccesity of a good structure in the document, and that's not a good solution for anyone. Semantic markup is a must on every editor, no mind what desktop solutions do, specially if they are getting worse document structures
-
We could remove (or reduce) the top and bottom padding in paragraphs, so that a new paragraph looks like a line break, although this would mean that in order to get an empty space between paragraphs you would have to type ENTER twice, creating an empty paragraph between paragraphs.
-
buying cialis online forum (https://bestcialis20mg.com) Edwin, USA 2022 06 19 07 52 28
-
If you wear the trays for too long, the peroxide in the gel can irritate your teeth and or gums so be sure to follow your dentist s instructions amazon priligy (https://priligy.me) Avoid use of NSAIDs, including NAPRELAN, in pregnant women at about 30 weeks gestation and later
-
buy priligy in uae (http://priligy.bond) Dosage, and days Also add if you are doing IUI, trigger, etc 2