Pathway

As a software user, I never really understood why small-scale developers (you know the kind: free, convenient software) took so much time advancing their creation.

But I’ve come to experience it from the other side now; and maintaining and improving useable builds of even small applications takes up tons of time. Even though I’m still investing a lot of hours into Pathway, it’ll surely seem slow from a user perspective.

Also, I’m having finals in a few weeks. That means work on Pathway will be paused until the first weeks of February.
However, I’m glad there are a lot of people who’d like to see further development of the app. So check back in a few weeks

Oh, and I get why so many apps deliberatly choose to remain monolingual. I’ve received a lot of translation offers and I’m very thankful for these, but integrating and maintaining those translations for every small fix you make (that means on two sides: the code side and the people side) proved to be a real time-consuming task. Now English is not my mother tongue, and I know how nice it is to be able to use software in your own language, so Pathway will support more languages (they’re coming…). But I’m looking for an efficient means to be able to release updates/smaller features more often. That means not having to e-mail every translator for every string (and possibly waiting a week).
A possible solution is to translate only the bigger updates, and asking people to use the English version if they want to use the smaller updates. What do you think, is this doable?

As always, suggestions and remarks are welcome in the comments or by e-mail.
I should be able to release updates more easily thanks to the autoupdating feature (Sparkle) that is now integrated in Pathway.

The translation process proved to be rather time-consuming, so I decided to put 0.6 up with some languages missing. Italian, German and Chinese are underway, and an update will be up when they’re ready.

Hi all. Thought I’d let you know where I’m working on. Below is a screenshot which I’ve made to let you give your opinion:

Clicky

As you can see, I’ve added a contents drawer. Clicking an item scrolls the page to the corresponding paragraph. But should you be using all that screen real estate just to show the contents of a page? A second option is to embed a button in the horizontal divider between the page web and the page browser. You would then click it to bring up a pop-up menu with a hi�rarchical contents structure. Upside: It’s non-obtrusive. Downside: you’ve got to click twice (and scroll in some cases) to achieve the same.

Please help me out and drop a line in the comments

There were many people who volunteered to translate. Thanks!

I’ll send the translators a text file with all the translation strings when I’m done with the next build.


Currently, the following languages are backed up by a kind soul:

(English, Dutch), French, German, Spanish, Traditional Chinese, Italian.

I’ve received much response to v0.5.
You’ve all sent in wonderful ideas and I’ll work on all of them. There are also some obvious bugs and misbehaviours that will be fixed.
Some of the most popular requests:

• Other Wikipedia languages, and other wikis support
• Localization in different languages

Please note: I’ll try to spend as much time as possible working on it, but that’ll have to be spare time as I have to combine it with college. I hope you’ll understand that I have to make priorities. There’s just no time to do it all. But I’ve put all suggestions on a list.

I’ll probably make a RSS feed out of this page, too