{"id":235,"date":"2005-03-07T13:00:34","date_gmt":"2005-03-07T05:00:34","guid":{"rendered":"http:\/\/www.nargalzius.com\/blog2\/http:\/www.nargalzius.com\/blog2\/archives\/2005\/03\/2005_03_07_1300.php"},"modified":"2017-02-10T04:05:42","modified_gmt":"2017-02-10T04:05:42","slug":"ecto-schmecto","status":"publish","type":"post","link":"http:\/\/nargalzius.com\/blog\/archives\/2005\/03\/07\/ecto-schmecto","title":{"rendered":"Ecto-schmecto"},"content":{"rendered":"

I apologize to the Ecto<\/a>-supporters out there, but quite frankly, that piece of software you love, can be quite intrusive at times.<\/p>\n

Since I heard Ecto<\/a> was the best offline blog-manager out there, of course I had to see what’s up and give it a try. I’ve been using MarsEdit<\/a> for the longest time and was quite happy with it save for one problem: You could only keep an offline cache of the last 30 posts you’ve made.<\/p>\n

I thought “Hey, since Ecto<\/a> can do Markdown<\/a> too, then there’s nothing to lose.”<\/em> – or so I thought.<\/p>\n\n

Before everything else, I acknowledge that MarsEdit<\/a> probably has a differnet “type-of-user-market” from Ecto<\/a> altogether… so some points here may be contested by either side saying “but this is how we<\/strong> do this, and this is how we<\/strong> do that.”<\/em> If you’re that type of user, then this article is probably not for you.<\/p>\n

MarsEdit: How I<\/em> blog<\/h1>\n

Ok first you’d have to understand how I go about my blogging business. As you know MarsEdit<\/a> and Ecto<\/a>, basically offer the same thing: a faster way to blog. By not being at the mercy of servers processing requests here and there, these tools allow you to draft your posts offline, then simply contact the server and apply the necessary additions\/changes when you’re done.<\/strong><\/p>\n

For me, using an offline weblog manager is a no-brainer… but which one to use… aye there’s the rub!<\/em><\/p>\n

I’ve been a rabid MarkDown<\/a> supporter ever since I first heard of it, I has managed to keep my back-end code neat and clean: I can export all<\/strong> my blog entries to mere textfiles and they would still<\/em> be readable (with minimal or no HTML code clutter)<\/p>\n

If you check my blog’s pagesource, you’d see it’s still in xhtml. That’s because MarkDown<\/a> is only applied when publishing. What does this imply? The actual source<\/strong> (which is stored in the database) is still<\/em> in the simplified MarkDown<\/a> format. Why am I mentioning this? Because this is where Ecto seems to drop the ball on their MarkDown<\/a> support.<\/p>\n

Just as I prefer my code in web-development in Notepad\/BBEdit, I want my blog code untouched<\/strong> So basically, my only<\/strong> requirement is MarkDown<\/a> support – and that support is of course just for the “preview” pane alone<\/strong>.<\/p>\n

MarsEdit<\/a> does this perfectly: I still edit my code as-is, but the preview pane shows it with the MarkDown<\/a> formatting applied<\/p>\n

Enter Ecto<\/h1>\n

Ecto<\/a> has been around a long time, hence the software has matured as far as “features” are concerned. It’s really a beautiful piece of software. I’d switch to it in a heartbeat if it would just resolve the issues I’m about to discuss in this post.<\/p>\n

One of the main feature’s Ecto<\/a> has to offer is of course code-automation, meaning shortcuts that can generate your tedious xhtml tags quickly. Hence their Rich Text<\/code> formatting is a big hit to the users who want that WYSIWYG<\/em> feel. It requires less brainpower to use, hence Ecto<\/a> users can just focus on the content<\/em> of their posts.<\/p>\n

Now, Ecto<\/a> supports MarkDown<\/a>, and if<\/strong> enabled, you basically have no problems with it. But that is a resounding if.<\/strong> This is also where Ecto<\/a>‘s intrusiveness come’s in.<\/p>\n

The Story<\/h2>\n

I set Ecto<\/a> up, everything went fine. I also am very pleased to see that I can import any n<\/em> number of posts. Great! I set it to import all<\/strong> my posts. No problem! Then I check out how it “edits” published posts. Now this is where the madness begins (cue The Shining<\/em> background noise\/music)<\/p>\n

First of, to use<\/em> MarkDown<\/a>, you have to set it to xhtml\/html<\/code> mode (default is rich text<\/code>) Fair enough. But you can only<\/em> set this “editing mode” after<\/strong> it has opened the post\/draft. The editing mode is grayed out when you’re in the main window… and there’s no option to force<\/em> or disable<\/em> editing modes to circumvent the problem.<\/p>\n

What does this entail? Assuming you’ve written something with MarkDown<\/a> code before – if Ecto<\/a> happens to<\/em> open it in rich text<\/code> (I say “happens to” because as I said before, you don’t get to pick editing modes from the main window), it will parse the source as such, and when you then<\/em> switch to html<\/code> mode, your once simple syntax is now riddled with html code! In short, you lose your MarkDown<\/a> syntax totally – no way to bring it back.<\/p>\n

This is a horrible situation to be put in, especially if you like editing previously published posts. It mentions something about “setting the default formatting options,” which again is only accessible on the draft\/edit window (and only applies to such). I did that, and for some reason it sometimes<\/em> remembers the settings, and sometimes<\/em> it just goes back to rich text<\/code> mode.<\/p>\n

If you hand-code via html<\/code> syntax, it would be fine since toggling between rich text<\/code> and html<\/code> retains the inherent “source” which is html-formatted. If you’re a MarkDown<\/a> user however, you have to be extremely careful<\/strong> with the formatting buttons you press – you may just lose everything in a heartbeat.<\/p>\n

So what? It’s not like users care about the “source”<\/h2>\n

That is true as far as the readers are concerned, they still see the html output anways. But as I mentioned before, the reason I use MarkDown<\/a> is so I have a clean readable format in case I decide to simply print directly from the DB. Plus the less clutter you have, the easier it is to edit. The problem with Ecto<\/a> is that if you edit something made with MarkDown<\/a> (and assuming it successfully opens it html<\/code> mode (which retains the MarkDown<\/a> syntax) – if you switch to rich text<\/code> then re-publish, the code stored on the database itself will now be html formatted, hence if you try to edit that again… you can never<\/strong> get your MarkDown<\/a> syntax back… ever!<\/strong><\/p>\n

Categories<\/h2>\n

Another issue is the way Ecto<\/a> handles multiple categories: In my blog I have category icons – the icon accompanying a post is usually the primary<\/em> category of that post. Ergo I can have a post included in 10 categories, but the icon still will show the category of my choosing<\/strong><\/p>\n

What makes this significant? Weblog systems usually list categories in alphabetical order. If you select multiple categories, regardless which category you set as primary, it still will display it in alphabetical order.<\/p>\n

The problem in Ecto<\/a> is it assumes the latter argument for all users, when clearly it’s not the case. So if you have 2 posts, spanning 3 categories called general, technology,<\/em> and nonsense.<\/em> Suppose you wanted the first’s primary as technology, and the other’s primary as nonsense. When you publish that with Ecto<\/a>, it will display both<\/strong> as General.<\/em> Why? Because it entered the categories alphabetically – and the server probably assumed the first one entered was the primary<\/em> category.<\/p>\n

MarsEdit<\/a> on the other hand, boldens<\/strong> the first category you check and sets it as the primary (I surmise that when submitting to the server, it sends that category first, then the rest alphabetically. So in my blog, even if the categories under the title are still alphabetically arranged – you can still see that the icon correctly represents the primary<\/em> category I chose.<\/p>\n

Developers should never<\/strong> assume how end-users use services. It’s one thing to anticipate stuff to make an interface more intuitive – provide the functions that can make a task easier. It’s another thing to assume the required processes in which these tasks are done.<\/p>\n

Back to MarsEdit<\/h1>\n

So now, I’m back to MarsEdit<\/a>, I have to live with the problem of it downloading 30 posts maximum. Now I know MarsEdit<\/a> developers should also not assume that people will never need more than n<\/em> number of recent posts cached offline – but I’m sure you agree with me that that<\/em> fault is far more forgivable than Ecto<\/a>‘s formatting antics.<\/p>\n

Still I still give props to Ecto<\/a> for their feature-set. But they have to understand the reason why MarsEdit<\/a> is thriving despite its lack of features, is because it implements the “basic stuff” better than Ecto<\/a> does.<\/p>","protected":false},"excerpt":{"rendered":"

I apologize to the Ecto-supporters out there, but quite frankly, that piece of software you love, can be quite intrusive at times. Since I heard Ecto was the best offline blog-manager out there, of course I had to see what’s up and give it a try. I’ve been using MarsEdit for the longest time and …

Continue reading “Ecto-schmecto”<\/span><\/a><\/p><\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[4,5,9,6,13],"tags":[377,741,745],"class_list":["post-235","post","type-post","status-publish","format-standard","hentry","category-general","category-internet","category-nargalzius","category-reviews","category-technology","tag-ecto","tag-markdown","tag-marsedit"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[],"_links":{"self":[{"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/posts\/235","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/comments?post=235"}],"version-history":[{"count":1,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/posts\/235\/revisions"}],"predecessor-version":[{"id":1820,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/posts\/235\/revisions\/1820"}],"wp:attachment":[{"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/media?parent=235"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/categories?post=235"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/tags?post=235"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}