We have some exciting news this week: Kristina Schneider joined the doingText-team. She’ll take care of design and usability and already has some fine ideas. We’re thrilled and you can be, too. Expect some great changes!
Now for the new features of this week.

Add lines a new way

At the bottom of the discussion field there is now an “Add Line”-button. It adds a new line at the end of the text. We have added this button for usability reasons. People starting their first discussion ever, happened to be startled by the display of text within the lines and thereby not knowing that clicking the line and hitting enter creates a new line.

Growing text area for comments
Just like the line fields of your text grow with the content, now the the text field of the comments grow, too. This way the commenting person always has the whole comment in sight.

Confirming notifications
Inspired by the Growl app für Mac OS X, all confirming notifications now come along in that style. There’s a little rectangle showing up in the upper right corner of the site for a few seconds. It tells you what has been successfully done. It appears after events like changing that status of a discussion, adding collaborators to your discussion, sending an doingText-invite to someone or logging out of your account.

Negative CAPTCHAs
The dark side of being on top of the google search when it comes to “text collaboration” is that we’re becoming interesting for spammers. We have now implemented a negative CAPTCHA to cope with spambots at least for the near future. It’s called negative, because the CAPTCHA works exactly the other way round and you as a user won’t see anything of it. There is no extra field the user has to fill in, but an invisible field for the bots called Honeypot. If something is filled in that hidden field it must be a spambot. Those requests will then be ignored.
More information on negative CAPTCHAs can be found on Ned Batchelder’s site.

No long opening speech today. Let’s get right into this week’s news.

Login notifications

Entering a site and not getting nowhere, ’cause the failwhale’s little brother won’t let you? Now what is wrong? From now on, you’ll get a specific answer to that question. Logging in to doingText, 3 possible mistakes can occurr. Either the account is not yet activated, the login (user name)/ email address is unknown or the password is wrong. So you exactly know what’s going on and what to do in the next step.

RSS feed
Subscribing to the RSS feed is now as easy as easy can be. In the header of a discussion you find the RSS symbol. Put the link to your feed reader and get informed on all the comments and edits to a discussion.

Auto-resize of images
So far, inserting large images led to the phenomenon that the images exceeded the discussion frames. And yes, that looked kinda awkward. Now images are automatically adjusted to fit the size of the discussion.

Textile
At this point on or another might need a little recollection of what Textile is about. The basics are to find in our guides. If you’re already used to wikis, Textile will be very familiar to you. If not, the don’t worry. Textile is really simple.
A few words ahead: Textile is a markup language used here in doingText to structure text passages on a minor level - just insofar as it is needed to talk about a text comfortably. We have already introduced it in our blog some weeks ago and here’s the link to our Guides.
There’s 2 steps: First, add .textile to the discussion title up in the header. For example “Films of the Week.textile”.
Second, use the Textile tags. Here are a few examples:
For bold phrases write *bold phrase*.

For bulleted lists write
• * Point a
• * Point whatever

Images, to come back to this, can be inserted by adding exclamation marks around the URL of the images: !imageurl!.

If you happen to find any tags not working, please don’t give up. Just write me an email to katrin [at] doingtext.com or use the Feedback button on the right to let us know.

Deleting comments


There have been requests for being able to delete single comments. This is now possible for comments you created yourself. Furtheron, the discussion owner can delete all comments. That way you can keep your comments balloon as cleaerly arranged informative as you wish to.

iPhone screenshot
We just love it! So yeah, here’s a picture of the read-only iPhone and iPod touch interface. And, by the way, there’s no extra URL or so needed. The interface loads automatically when entering doingtext.com via iPhone or iPod touch.

(thanks to iPhoney)

Publish your discussions
Yes, non-protected discussions were actually accessible already. And nothing has changed in this matter: Spreading the URL of a discussion lets other cowriters work on the text without having to log in.
The news here is that you can explicitly publish your texts and in this way make them accessible to the site-wide-search.
The published discussions appear on the users profile. So if you’re a cowriter and know the user’s name but can’t remember the title not to mention the URL, you can also go that way.

Search
Imagine a friend told you he published the discussion on doingText for that event. But damn! What’s the link? And where was that email again? Or could it be he twittered it the other day? Hum, nothing found. Maybe, he skyped it…?
To get you out of those time-stealing situations there is now a site-wide search for published discussions. It searches the discussion titles so all you have to do is entering a keyword of the title.

The nice thing about it: You don’t have to be logged in to use the search. The search form appears already on the starting page. This is also good for you registered users. You only want to look up something you don’t quite remember. You hurrily have to download that text for the next meeting. You just want to show a discussion passage to someone while talking about the project and don’t want to bother with logging in first. For all those situations the search will be your helping hand.

However, there is a little constraint here: The search only catches explicitly published texts. With that there still is the control of the “owner” of a discussion to distinguish between making a text available for certain cowriters and make it available for whomever is interested in the topic.

New design of the sharing settings

Along with publish- and the search-option, the sharing settings got a new design. The table gives you more than quick the information on who can read, write, comment and search for your text.

There are also some news for the discussions themselves.

UTF-8
Do you care to write, for example, cyrillic or chinese signs? No problem. DoingText now supports UTF-8 encoding.

Relation of comment balloon and line and opening the comments section
This one falls into the category “little change, great effect”. There is now a little arrow going from the comment balloon to the related line. It makes the comment function easier to relate to the recent version of a line which makes working in doingText easier for you.

Opening the comments section is now combined with the edit mode. That means, whenever you directly enter a line you get the comments section with all the changes automatically shown. Vice versa, opening the comments will open the edit mode.
Here we have a question. When you switch to other lines to see the changes/comments there, the edit mode of the previous chosen line stays open. Does that bother you in some way? Please leave your word down in the comments or in the Feedback Forum on uservoice.

Notes on bug fixes
The deletion of discussions was broken and the News Feed showed a wrong date. That is now solved.
The list of discussions in the header is now case insensitive.