Comments on: Playing with Ecto http://www.darcynorman.net/2006/01/30/playing-with-ecto/ just a lowly edtech geek, mumble mumble university of calgary Sun, 21 Mar 2010 17:18:11 -0600 http://wordpress.org/?v=2.9.2 hourly 1 By: Alan http://www.darcynorman.net/2006/01/30/playing-with-ecto/#comment-81158 Alan Wed, 31 Dec 1969 17:00:00 +0000 1242263871#comment-81158 I'm pro edto, but cannot really counter yopur remarks-- I've pretty much gotten accustomed to the interface and found some things that get around these issues. I never use the bottom HTML menu, and pretty much go by the customized shortcuts, plus a few I've added on my own. I love the drag and rop interface for popping images in, and again have made my own image display templates for centered display, or right alinged thumbnails with links to full size. There is some bug with ecto, image uploading, and WP 2.0.... still digging through this one. Yeah the preview is not the full preview of what you get, and I use it more just as a quick check to see I've not mangled a tag or an embedded image. I usually mod the preview template to access the style sheet from the server. There is a time saving of any desktop composer in not having to got through several screens in the web editor, and I often compose some drafts offline. I also like having a central writing place to publish to my corral of WordPress, MovableType, and Blogger sites. But hey, there are always better things out there, so thanks for fleashing out and reporting! I’m pro edto, but cannot really counter yopur remarks– I’ve pretty much gotten accustomed to the interface and found some things that get around these issues. I never use the bottom HTML menu, and pretty much go by the customized shortcuts, plus a few I’ve added on my own. I love the drag and rop interface for popping images in, and again have made my own image display templates for centered display, or right alinged thumbnails with links to full size.

There is some bug with ecto, image uploading, and WP 2.0…. still digging through this one.

Yeah the preview is not the full preview of what you get, and I use it more just as a quick check to see I’ve not mangled a tag or an embedded image. I usually mod the preview template to access the style sheet from the server.

There is a time saving of any desktop composer in not having to got through several screens in the web editor, and I often compose some drafts offline. I also like having a central writing place to publish to my corral of WordPress, MovableType, and Blogger sites.

But hey, there are always better things out there, so thanks for fleashing out and reporting!

]]> By: Adriaan http://www.darcynorman.net/2006/01/30/playing-with-ecto/#comment-81159 Adriaan Wed, 31 Dec 1969 17:00:00 +0000 1242263871#comment-81159 First of all, don't use the <!--more--> blocks, just set ecto to use the MovableType API for your WordPress blog. Then you just type the "more" stuff in the bottom pane of the edit window. It would have helped if you wrote what error was popped up by error after publishing. It's always an error from the server and may indicate there's something wrong with your install. As for WP2.0, it has bugs. See: http://ecto.kung-foo.tv/archives/001602.php and http://bb.infinite-sushi.com/viewtopic.php?t=1308 First of all, don’t use the <!–more–> blocks, just set ecto to use the MovableType API for your WordPress blog. Then you just type the “more” stuff in the bottom pane of the edit window.

It would have helped if you wrote what error was popped up by error after publishing. It’s always an error from the server and may indicate there’s something wrong with your install.

As for WP2.0, it has bugs. See:
http://ecto.kung-foo.tv/archives/001602.php
and
http://bb.infinite-sushi.com/viewtopic.php?t=1308

]]> By: D'Arcy http://www.darcynorman.net/2006/01/30/playing-with-ecto/#comment-81160 D'Arcy Wed, 31 Dec 1969 17:00:00 +0000 1242263871#comment-81160 First off all, I didn't manually add the < ! -- more -- > block - Ecto did that automagically, and I guessed wrong about which text area would go where. I guessed that the first text block would be excerpt, and the second the body. But the first text area appears to be inserted before a more block, the second after it. I didn't think to write down the error, but it was something like "communication error while connecting to server" or something. I'll try again and see what it says. I wasn't knocking Ecto - it's a cool app - but it just doesn't jive with how I interact with my blog. First off all, I didn’t manually add the < ! -- more -- > block – Ecto did that automagically, and I guessed wrong about which text area would go where. I guessed that the first text block would be excerpt, and the second the body. But the first text area appears to be inserted before a more block, the second after it.

I didn’t think to write down the error, but it was something like “communication error while connecting to server” or something. I’ll try again and see what it says.

I wasn’t knocking Ecto – it’s a cool app – but it just doesn’t jive with how I interact with my blog.

]]>