From the Lab: Editing Keywords on Multiple Sheets

multi sheet multi keyword

One of the most requested features since launch has been: “Let me edit keywords for multiple sheets at once.”

And we nodded. And nodded. And said it was coming. Because it was sketched, and mocked up, and laid out since waaaaaaaay before the initial release. It didn’t make it into 1.0, and it then got buried someplace between a sheet list rework and the option to actually *show* keywords in the sheet list in the first place.

So, with 1.2, we will finally enable keyword editing for multiple sheets at once – right from the sheet list. Select some sheets. Bring up the contextual menu. Select “Keywords…”. Edit away.

Keywords that are present on all sheets, will be available in the familiar keyword editing field. Adding a keyword will apply it to all selected sheets. Keywords that are only present on some sheets, will be shown in a list below, unaffected from any editing.

If you want to apply any of the grey keywords to all selected sheets, click on it. Bam! ;)

It’s the simple things…

Change in plans: Announcing Ulysses 1.2, with a twist

Sheet table rework

As mentionened on Twitter, we hit a road block with preparing Ulysses III for its mobile counterpart. To ensure seemless compatibility, we had to refactor the sidebars to an unforseen extent, which made us loose quite a lot of time that was meant to be spent on version 1.2 for desktop.

So in order to get 1.2 out the doors, we were left with the following options: Either pause porting Ulysses III to iOS, or pause creating the Style Exchange, or pause developing the blog exporter. Or, well, simply continue and push the planned release date back a couple of weeks.

Needless to say, it was a tough decision, but we finally went for option three: Pause the blog exporter.

This is stupid insofar as we announced 1.2 “for the bloggers”, but the other options would have been far worse: Pushing back release would not bring the blog exporter anytime sooner. Halting the iOS port would mean pushing back the planned iOS release for quite some time, since we need to consider WWDC, holidays, etc.

And halting the Style Exchange would mean removing all of the new Theme & Style stuff from 1.2, essentially pushing its release back to the next version.

So, no blog exporter in 1.2, but…

On Twitter, we also said 1.2 would be a cool update still. And we believe it will. Besides making Theme editing far easier and introducing the Style Exchange, we have added tons of user requests, such as sorting the sheet table and display of creation dates. We have added the option to display keywords right within the sheet table, edit keywords for multiple sheets, and introduced an option to set the amount of preview lines being displayed – it’s 1 to 6, just so you know.

We have also added some much needed fixes to how the editor responds to sidebar selection, so Ulysses is now more in line with how behaves. And we have have added writing targets/goals to sheets among other things, but that’s another post altogether.

1.2 is slated to hit the App Store in April. Yay!

Also announcing: Ulysses Style Exchange (no, for real this time)

Export Themes

Since the question popped up on Twitter: While we’re working on Ulysses for iOS, we’re of course continuing work on Ulysses III/Mac. One of the projects that’s been lingering for some time now, is the Ulysses Style Exchange – our proposed online space to publish and download export styles.

Cool thing is, it’s already been started. We hope to move into beta by the end of March, and have a full site ready come April. We’ll see.

But since styles are only half the fun, we’ll also include a Theme Exchange. So you’ll be able to up- and download themes as well as styles. And for that, we’ll be issuing a 1.1.3 sometime soon, which will allow for simpler theme creation, management, palette changes, the good stuff.

Check the screen. It’s pre-alpha footage, but already running at 60 FPS…

This one’s for the Bloggers: Announcing Ulysses 1.2, XML-RPC Edition

Blog Prefs

UPDATE: Change in plans…

Oh, folks, here we go again. Another day, another announcement. This one marks a slight change in direction for your favorite text editor, as from now on, we will focus major releases around certain use cases.

That’s a mouthful, alright, so let me elaborate.

If 1.0 was the foundation, 1.1 was the house. And with 1.2, we’re starting to decorate the rooms. And we will do so one room at a time.

First room: The Bloggers’ room.

The next update will see us leveraging the metaWeblog XML-RPC API, to plug Ulysses III right into your favourite blogging engines.

So whether you’re running a self-hosted blog or are using an online-service such as, chances are high that 1.2 will allow you to publish your work directly from within the app. No more copy and paste, no more switching between browsers, you know the drill, you hate it as much as everybody else.

But we won’t stop there. Among other things, we will add support for sheet meta data (yay!) and additional image attributes. So, yes, we will finally let you set the width, height and… classes and IDs of images.

Classes. IDs.

There’s more to this, but I guess you already wish the update was closer than it appears. Patience, my friends, patience.

Announcing Ulysses Mobile, nothing to see, please move along

That’s a comeback, eh? BOOM, Mama said knock you out, and if you’re still standing, you didn’t get the headline.

Over the course of the coming weeks, we will slowly push news and infos about our progress on Ulysses for iOS. We have next to nothing else to announce at the moment, except for the fact that we have started porting the editor.

Right now, we’re not even 100% sure, if we can pull this off. But it’s looking good.

What does this mean for Daedalus? Nothing. Daedalus is alive and well, and yes, yes, everybody would say that, but Ulysses Mobile will be a completely different beast. Both in functionality and appearance.

You’ll see.

This is exciting, folks…

1-up: タイトル:日本語ユーザの皆様へ

Ulyssesの最新リリース、Ulysses III 1.1をご案内します。

Ulysses III 1.1は、ローカライズを専門とするWordcraftsチームによってそれぞれの言語に翻訳されました。ドイツを拠点とするThe Soulmenチームが情熱と信念を注いで作り上げたこのUlysses IIIの素晴らしさを日本語バージョンにも遺憾なく反映させることができるように、*魂を*こめました。ホントですよ。
Ulysses III 1.1は、まもなくMac App Storeに登場します!

ゆかり for Wordcrafts

1-up: Grandi novità!

Ciao a tutti!

Cosa? Un articolo in italiano in questo blog? Eppure Ulysses, putroppo, è solo in inglese… Avete ragione: lavorare con un’app non tradotta nella propria lingua, a volte, è seccante e i nostri Soulmen lo sanno bene. Ma sanno anche che le cose fatte in fretta raramente riescono, e la localizzazione di un’app è un lavoro che non si può certo improvvisare. Per questo hanno chiesto a noi di Wordcrafts di aiutarli, e l’abbiamo fatto con grande piacere! Il risultato? Reggetevi forte: in ottobre avrete la vostra versione in italiano!

Wow! Non è fantastico? Ci abbiamo messo tutto il nostro impegno e la nostra passione e siamo convinti che piacerà anche a voi.

Mi raccomando, tenete d’occhio il Mac App Store e non lasciatevi scappare Ulysses III 1.1!


Luca per Wordcrafts

1-up: Sublime Text ULSS package

ULSS in Sublime Text 2

Just a heads-up: We now have a fully functional Ulysses Style Sheets Sublime Text package ready. Supports that editor’s rather cool auto-completion and, of course, syntax highlighting.

It’s our second plugin, the first being TextMate 2, and we’re now looking into also supporting Coda and maybe even BBEdit.

No download link, since you couldn’t use it without the beta anyway. ;)

1-up: Ulysses Style Sheets vs. MS Word

ULSS Word Style Names

One of the things we didn’t mention yet, is that Ulysses Style Sheets will also be used to style Word (and Pages) export.

Naturally, this will be not as refined as our PDF output, since some things are just not possible with Word and Pages @&#%!™. However, at least in the case of Word, you will be able to fine-tune style sheets in the target application.

Our language supports a “style-title” attribute for every definition. These titles are what Word uses for its very own style sheets, so, if you managed to pay attention: Word export will now map definitions to Word styles.

Happy? :)