Greg wrote:
Nobody has exactly what you are looking for because your request is very specific.... It's not a common way for people to interact with a Drupal site,
Yes, realizing that nobody felt the need to do this before is indeed the most unexpected part :-)
I think that the suggestions for "look at this module" or "try that extension" were meant to show you a base of code that does similar things so that you can modify
I was and still am fully prepared to do a lot of custom scripting to get this working. I am well aware that a lot of my own requirements are so unique to my situation that I have to do them myself. I have no problem with that.
I _am_ already doing them, actually, for all the other parts of the job, like automatic conversion to drupal-acceptable HTML of many files in other formats.
It's just that, in my original script flow diagram, the box titled "now upload this file in one new Drupal node" was the one that I was most confident, almost certain, that already existed and was well documented...
The rich client side XUL administrator summer of code project (I believe) gets closer to what you are looking to find.
That looks like the performancing firefox plugin. Something great when you have to post short stuff, once in a while, certainly not for "volume" production. As such, I'll surely use it when ready. Thanks for signalling it.
Drupal sites are generally used for community content where it is created by many people. In that case, it makes more sense to use an in-browser WYSIWYG editor.
I disagree here. I don't think the intended *number* of authors matters at all. What I see is that Drupal, Wordpress, and basically every blog/cms I know of is implicitly designed for author(s) who publish (very) short texts, only once in a while.
I will try to hack mailhandler now (already asked privately for suggestions to the maintainer, hope he'll answer).
Any other pointer, comment, mailhandler patch, etc... is still very welcome of course.
TIA, O.
On 7/3/06, dondi_2006 dondi_2006@libero.it wrote:
The rich client side XUL administrator summer of code project (I believe) gets closer to what you are looking to find.
That looks like the performancing firefox plugin. Something great when you have to post short stuff, once in a while, certainly not for "volume" production. As such, I'll surely use it when ready. Thanks for signalling it.
Well, you were bemoaning the lack of a "real, full, screen word processors and HTML editors, with spell checking, macros and lots of other goodies." That client (and performancing and...) gives most of what you were complaining about.
It would be handy to know more details about your situation: How often you want to post new content? How often you need to edit old content? How long the posts are and how much markup you are including?
Drupal sites are generally used for community content where it is created by many people. In that case, it makes more sense to use an in-browser WYSIWYG editor.
I disagree here. I don't think the intended *number* of authors matters at all. What I see is that Drupal, Wordpress, and basically every blog/cms I know of is implicitly designed for author(s) who publish (very) short texts, only once in a while.
Ok, I'll re-assert my point. Imagine your requirements in a multi publisher environment. Multiple people editing multiple text files on their client side and running scripts that directly import them into the system. That's what you want, right? Well, how do you control versioning? How do you control the individual preferences of each user to write their text files one way or another using one editor or another? How do you sync a local copy back with the server copy (since there are multiple editors...)? I'm not sure I've ever heard/seen anyone do what you're talking about.
You don't have to spend much time looking around before you see that people use all kinds of CMS for a wide variety of tasks including very long and highly formatted documents that get revised on a regular basis (have you seen the drupal handbooks, for instance?). And they do all that right within the browser.
Regards, Greg
On Mon, July 3, 2006 10:50 am, Greg Knaddison - GVS said:
That looks like the performancing firefox plugin. Something great when you have to post short stuff, once in a while, certainly not for "volume" production. As such, I'll surely use it when ready. Thanks for signalling it.
Well, you were bemoaning the lack of a "real, full, screen word processors and HTML editors, with spell checking, macros and lots of other goodies." That client (and performancing and...) gives most of what you were complaining about.
I disagree here. I don't think the intended *number* of authors matters at all. What I see is that Drupal, Wordpress, and basically every blog/cms I know of is implicitly designed for author(s) who publish (very) short texts, only once in a while.
Ok, I'll re-assert my point. Imagine your requirements in a multi publisher environment. Multiple people editing multiple text files on their client side and running scripts that directly import them into the system. That's what you want, right? Well, how do you control versioning? How do you control the individual preferences of each user to write their text files one way or another using one editor or another? How do you sync a local copy back with the server copy (since there are multiple editors...)? I'm not sure I've ever heard/seen anyone do what you're talking about.
You don't have to spend much time looking around before you see that people use all kinds of CMS for a wide variety of tasks including very long and highly formatted documents that get revised on a regular basis (have you seen the drupal handbooks, for instance?). And they do all that right within the browser.
Another fact to consider is that most WYSIWYG word processors (Word, OOo Writer, KWord, etc.) generally produce output that is tailored for a printer. Their web-targeted output is by and large attrocious and breaks very very easily. (Even the open source word processors are bad here, although not as bad as Word.) "Web pages" that you compose in Word are a poor web page anyway unless you do a dramatic amount of cleanup, by which point it's frequently easier to just copy and paste the text out of it. If you're doing something fancier with tables or lots of graphics, then use a web-tailored editor such as DreamWeaver or an in-page WYSIWYG editor (FCKEditor, HTMLArea, etc.), or even just learning HTML. You'll get much better results.
Word processors are all around lousy at producing web-targeted content, regardless of who's using it or how many people are using it or how much content you're talking about. They do a lot of great things, but web pages are not among them.
--Larry Garfield
-
dondi_2006 -
Greg Knaddison - GVS -
Larry Garfield