Hands up, anyone who's written a Python script that was supposed to run for a long period of time unattended on a Windows box, only to come in the next morning to see this kind of dialog box on their...
Hands up, anyone who's written a Python script that was supposed to run for a long period of time unattended on a Windows box, only to come in the next morning to see this kind of dialog box on their screen 5% of the way through?
The Vancouver PHP User Group, under the umbrella of a non-profit Vancouver PHP Association that the user group started, is going to run an Open Web focused conference in April 2008.
We are happy to announce ActivePerl 5.10.0 Build 1000 Beta, a beta release of the complete, ready-to-install Perl distribution for Windows, Mac OS X, Linux, Solaris, and AIX.
I am now running both my work iMac and shiny ( well, matte black actually ) MacBook on Leopard, and for the most part I am really impressed. One thing that has *never* impressed me however was how PHP has been done on OS X. As Wez notes in his recent post about his new PHP / ObjC bridge:
"(note: you'll need to build your own PHP on Leopard, the one Apple ships has had its exports stripped, so you can't run the extension--it'll build, but not run)"
I got a comment a while ago somewhere ( the exact circumstances escape me ) that there is nothing in the ko API to easily get and iterate over all of the open files in Komodo. And that statement is correct, sort of. There is a way right now to very easily get all open files, it just isn't documented that well outside of the Komodo sources:
That is, ActiveState is consolidating our blogs on planet.activestate.com. Update your RSS feeds and bookmarks, because planet.activestate.com aggregates the word from all the bloggers at ActiveState, so you'll get news and events, geeky stuff, social networking bits and bytes, tips...
That is, ActiveState is consolidating our blogs on planet.activestate.com.
We've been so very busy getting Open Komodo out the door, and now that is done, I can start to focus on some very important todo items. One big item is that we need another developer for Komodo.
Today the Languages team is heading off site. No, we aren't on strike - we're having a planning and brainstorming meeting to cook up some great things for 2008. Got ideas? Something you think is missing or would be cool...
Today the Languages team is heading off site. No, we aren't on strike - we're having a planning and brainstorming meeting to cook up some great things for 2008. Got ideas? Something you think is missing or would be cool to see come out of this area in the New Year? Let us know.
One of Komodo's strengths is that we use the Mozilla application framework ( the same as used for Firefox, T-bird, Joost, Songbird, et al ) to develop Komodo. This buys us relatively easy cross-platform development, but the trade-off is that Komodo may not feel as 'native' on any given platform, particularly OS X.
Spurred on from some questions in the #komodo chatroom on IRC today, Eric dug into the question of 'how do I write text to the command output tab'. This ended up being a little complicated, but it works just fine and has my vote for eventual porting into the ko namespace:
