July 20, 2009
Hello. I’ve been progressing quite well on this particular feature during the past days and here I present to you: the brand-new Xcode project importer. You will probably not notice a single difference at first sight, except a small option in the open panel and maybe that is is way more robust and reliable than the previous one.
However, this importer is not only a importer. Basically what it does is to load the Xcode project and to construct an object tree from the complete file tree. And now the best: this object tree is mutable. Mutable as in add/remove files, groups, folders etc. I’ll use this functionality to implement a feature to export your localization to an project. Like say files translated at least 80% in a language translated at least 80% should be in the project and all others not. Done. No more hassle going through your big projects, just single click away.
You will be able to get this feature in the tomorrow’s nightly build of the Localization Manager. Let me hear what you think!
have fun, Max
June 29, 2009
So not that you think the development has stalled again, here’s a update on what I am doing right now — besides fixing several bugs from time to time (as they are brought up to me).
I am currently rewriting or upgrading the whole matching, error checking and auto-translation stuff from Localizer. This has all been transfered to a new Framework (yay, another one) calles LocTools – Localization Tools. Hosting a nice number of Unit tests, I finally rest assured it works the way I wnat it. Will make debugging a lot easier in the future.
Including the completely new Interface Preview I began during last autumn and this spring, these upgraded and now finally good-shaped pieces of code will make up the Localizer of version 3. Basically I am now doing the same to it like I did to the Localization Manager.
Next up: A working preview. After that: finally a remake of the Localization Dictionary – this is in urgent need of that.
I’d love to hear your comments!
Max
May 20, 2009
Hey,
the Loc-Suite now features a new Logging facility. This means we no longer have the regular text log that is also written to a file, but now a tree-based logging with error levels. Just like the Xcode compile log, each action log can consist of multiple inner log items. Each of these items has a level (none, warning, error) that is propagated upwards. Now here come the nice things:
- Using these levels I can express ibtools error and warning messages!
- When a warning appears, the window will automatically open!
- Even the string parsing can easily be verified by the user: Warnings and errors will pop up.
I hope you find it as useful a I do. I’d love to get some feedback!
Max
May 20, 2009
Hello,
the latest nighly build now features the Sparkle framework in both the Localizer and the Localization Manager. As soon as we see this release is stable I will also move this to the stable directory, ready for the big screen. The update cycles will then go with the stable development releases, which means version number changes.
Please send me your feedback on the current builds, I am eager to fix bugs 
Max
April 27, 2009
You can get the newest development builds (the ones which should be somehow stable) from this directory. Testers are very welcome. I will probably announce important new version here, so keeping an eye on this site will be sufficient.
Max
April 27, 2009
We finally have public nightly builds. You can get them here.
Disclaimer: while we take no warranty for all applications, we take explicitly even less warranty for nightly builds. Use them at your own risk and not in production environments, etc blah…
Have fun 
Max
April 27, 2009
Hi there,
I’m finally going public! For real now. Irreversible.
We have a new discussion board, a new public bug tracker and a public read of all SVN commits (yeah, I went to svn, too. What a experience!). Did I mention nightlies? Sure there are some. Read later about this.
Max
