|
|
Just wanted to let you know, that our time-tracking app Chronograph is available for $12.95 from MacZOT today. That’s 50% of our usual price. Please note, that it is a time-limited offer: you can buy Chronograph at this price only on June 30, 2009. Additionally, MacZOT will be giving several free licenses to their subscribers — take your chance.
By the way, we recently released Chronograph 1.3 which has one of the most requested features: iCal integration. Just click one button in preferences and watch how all your tracked time-data appears in iCal-calendar. Add a simple AppleScript and you can integrate Chronograph data into your workflow. With each release Chronograph becomes more mature, but, still, is an extremely easy to use piece of software.
If you were waiting for some special occasion to buy Chronograph license — this is exactly such occasion. Don’t miss it. It is HERE.
relevant links:
Some seriously good news here. It took several years of waiting, but, it finally happened. PHP-FPM project is officially BSD-licensed now, which means, that it has good chances to become a part of official PHP distribution.
PHP-FPM is “deciphered” as “PHP FastCGI Process Manager” and is a patch for php to greatly improve FastCGI SAPI usage in production. It adds a bunch of additional features to php’s fastcgi such as: easy php-process daemonization (with ability to specify uid/gid/chroot/log-file), safe php-processes restart (without losing requests), custom error-handling and accelerated file-upload support (requires additional support from web-server).
There’s not much documentation in english, currently, but, again, there is a good chance that it will be added really soon.
It’s been a while since I posted anything here. Life was keeping me busy 
Today, I am glad to announce the release of my new product: Chronograph. Chronograph is one of those tools, that I wrote for myself, because everything else out there felt like nonsense. Either too complicated, or too ugly. Anyway, Chronograph — is a time tracking application. Basically, there are Projects, which consist of Tasks. You can select task and start the timer. Then you do the job, stop the timer and move on to the next task. Chronograph keeps stats on the time spent and you can create reports (basic, for now) based on them.
I am trying to make application, which would feel “right”, and looks like the direction is correct.
If you have any comments, ideas regarding Chronograph let me know in comments, or using email: info@milkfarmsoft.com
Thanks
The concept of headers in C was necessary at its time, but these days it just makes compilation of complex program in complex environment several times more complex. Whenever you have several package-roots (I have /usr, /usr/local, /sw, /opt/local, /opt/some_pkg1, /opt/some_pkg2 at the same time), which have different versions of the same libraries, you need to separately check resolution order of libraries and header-files.
Sometimes it feels completely counter-intuitive and you just end up manually hiding some files.
Common end-user solution is just sticking to the package-root provided by distribution (usually “/usr”), but that is not an option for developer, who needs to test different combinations of bleeding-edge apps.
How do you manage this stuff?
Example. I need to build php6 (installation prefix /opt/php6) with:
- iconv from /sw (whle there is other iconv in /usr)
- libxml from /usr (while there is other libxml in /sw)
- icu from /sw/local (while there are pieces of other icu’s in /sw and /usr)
In reality, there are more libs involved, and complexity arises, when these different libs are needed by the same components of php. I start thinking, that I should create some special package-root and just symlink every needed library in it. And just give it as the only package-root to php. Seems like a complex task, while considering all dependencies.
In my ideal world, there would be no name-resolution at all, compiler would just require exact position of library (which would be represented by the single file)
Two news:
- LLVM 2.3 is supposed to be released today (what’s new?)
- WWDC 2008 is starting today
I wonder, if that is coincidence
Playing with Spread Toolkit. Absolutely love their constant-names 
- UNRELIABLE_MESS
- RELIABLE_MESS
- FIFO_MESS
- CAUSAL_MESS
- AGREED_MESS
- SAFE_MESS
- REGULAR_MESS
p.s. freshly released php binding is here
Google announced the list of students, they will be sponsoring this summer to work on open-source projects. My congratulations to everyone, who succeeded.
May the force be with you!
[official announcement]
Some things still wonder me, after 10+ years of web-development. Todays wonder is here:
RFC2821 (SMTP) tells: The maximum total length of a text line including the <CRLF> is 1000 characters . In real world, most MTAs default to 990 characters per-line, which means, that if you will try to dump longer line on them, they would split it by putting “!\n” after 990-th byte. This is mostly harmless for plain-text, but can easily break html.
Actually, there is even a PHP-bug reported, regarding this, but PHP obviously can’t do anything to help the situation
The solution is really simple: if there is a chance, that lines of your emails would be longer than 990 bytes encode body using base-64. The easiest way to do it for emails without attachments, in php is to use mb_send_mail() function instead of mail(), as it will apply encoding automatically.
The shortcut to switch tabs is…
| TextMate: |
Command + Option + Left/Right |
| Skype: |
Command + Shift + Left/Right |
| Adium, Firefox: |
Command + Left/Right |
| Colloquy, Firefox: |
Command + Up/Down |
| Opera, Safari, Terminal: |
Command + Shift + [/] |
Dear Santa, please, bring me Mk 41 next christmas, so I can fix this world.
I’ve just released syck for php 0.9.2 (a parser and emitter of YAML documents. If you don’t know anything about YAML and why it is good: check my previous posts on the subject). A lot of new and tasty features
First, and most important: a lot of stability and consistency fixes (previous release wasn’t properly dealing with some kinds of number-like strings and with mixed-keys arrays). This release is HIGHLY recommended to anyone who uses syck-php in production. I was using this version for several weeks as a server-to-server exchange format under heavy load and coudn’t be satisfied more.
I started to dive into object-serialization and unserialization topics. Any object which implements Serializable interface can be dumped into yaml-document now. It will be stored using !php/object::ClassName signature. And, of course, you would be able load the object afterwards. Important: at the moment of loading yaml-file, all of the classes mentioned in it have to be either declared, or be available to php’s autoload mechanism.
I also implemented loading of objects with !php/array::ClassName and !php/hash::ClassName signatures. These have to implement ArrayAccess interface. Unfortunately, I didn’t implement dumping of such objects yet. That is planned for the next releae.
As always, I am open to hear any of your comments and bug-reports.
|
|
