It’s not my ball, it’s everyone else’s ball. I do not suffer the problem of
a 6-month release cycle, or how painful Ruby on Rails is to deploy. I
realize I don’t see your pain, so perhaps if you could actually write up a
way we could make this easier for you? Because clearly I don’t get it, and
won’t get it. So instead of venting your frustration the way you are,
please educate us.
Let’s see…
Chet said “Doesn’t work w/ MarsEdit or TextMate client-side publishing
tools” and Frederic responded saying “You’re right, it doesn’t in the
release but is in the trunk and wait for the next release.”
Chet said “Documentation is sub-optimal” and Frederic responded saying
“You’re right, it is sub-optimal because I haven’t put too much effort
into it. I’ll work on that.”
Chet said “Updating the blog is failing” and Frederic responded saying
“You’re right, that is a defect that has been fixed in the trunk. It
will be in the next release.”
Chet said “Installation and upgrades are somewhat awkward especially
compared to more mature solutions implemented in other languages.” and
Frederic and most everyone else said “You’re right, they are awkward
due to the options and evolving Ruby platform and we choose to put up
with that because we like Ruby and Typo but we understand your pain.”
So now I’m confused - If one of the maintainers is agreeing that
Chet’s posted issues are both understandable and valid then why would
you continue arguing?
You have issues with
surprised, after that, to get Scott’s fanboy eruptions. I believe I
you could not do this or that, and Truthfully all I could find were
posts related to “MarsEdit”. Which those bugs have been fixed in
trunk, if you want you can try updating to “Trunk” and see if that
fixes your problems?
I’ve fixed MetaWeblog API tags issues as well in trunk today. However,
it seems marsedit doesn’t support that feature (or didn’t found how to
do so). Other issue for me is that the Metaweblog API provides a
getCategories method, but no way to getKeywords, which means 2 things :
– Using the metaweblog API won’t let you see which tags already exist
on your blog (our wb based admin interface now have tags autocompletion)
– Editing a post will make you delete every tags used so far from this
post, unless you remember them and add them by hand.
Regarding the documentation, I’ve been talking with a friend today
about what we should provide. Cool things came up, and amongst them
the fact we should officially support one installation way of self
hosting Typo, which means the easiest one (obvious heh ?). Having to
choose between 3 webservers, and 3 ways to serve pages (mod_rails,
(Fast)CGI and application server) is just too confusing for people. If
they want to deploy their webserver an exotic way (that’s to say
without Apache + MySQL which are the most widespread things you’ve
ever found on the Internet), it’s not our problem. However, we’ll keep
the existing docs about exotic configs for information purpose. redmine.typosphere.org is a wiki, if someone want to complete… it’s
up to him / her.
Was my 2 cents, now I must leave you, I’ve a release t finish before
sunday and I’d love to add some more fancy things if I can (like
autosave). If anyone want to help instead of just trolling
