Archive for February 16th, 2008

February 16, 2008

Komodo 4.3 – First look

I decided to give Komodo 4.3 alpha1 a spin and I’ve been running it for a better part of a week now I reckon (since 9th feb) and I must say I like it, a good improvement over 4.2 by far but still has some kinks, mostly in the newly added features I guess.

1st run – Code Intelligence tried to run and do some weird stuff but it hangs, so I had to kill Komodo, startup after that is snappy, faster than 4.2 IMHO

Search in all files = Slow as heck, installing grep and running it is faster (including the installation step), wonder if it’s like a first time cache it’s building up (debunked that theory, strike through isn’t working on this theme so meh.)

The slowness persists and is in Phase 1, gathering list of files and seems to also look in my PEAR dir for some reason; look in current project suddenly became current projects + include_path I think, could be the slow down, grep (like I use it) only searches in the dir I’m in (usually the root of the project) and down. So what I’d want is a new option “search only in current project” on top of the already existing feature :)

Would be better if it displayed results as it found them, seems to hold of for too long

The Asynchronous SCC part is going beautifully, I like it, was getting a wee bit tired of the UI hangups that 4.2 had

Haven’t given the new Unit Test runner a go since none of the projects I’m actively working on at this moment use PHPUnit but I did try to make a Test Plan and it’s not showing up anywhere and a closing Komodo and opening again doesn’t find it in the Project Unit Test Result tab but picking Project -> Select Test Plan does find it and picking the test plan updates the tab I mentioned earlier.

For the fun of it I tried to pick PHP as the language I wanted to run in and in the test command line I did pear run-tests -r just so see if I could cheat past the PHPUnit part but apparently it does not work, but gives me no error or any output what so ever, quite confusing, would have expected “Can’t run” or “No ouput”, “nothing ran” or whatever, but a alpha release is a alpha release.

Now if I just could find out how I edit or delete test plans, that would be swell.

When I have a folder open in the project view which has say, tests I’m running and they fail (phpt) they generate these .diff, .out .exp and whatever, seems to hang up the UI to update the view, same goes if I have one of those files open when I’m running the tests and the contents of the file I have open changes, then Komodo becomes a bit sluggish for a while, sometimes it’s just a second but sometimes longer, I guess it depends on how many tests I’m touching and how many of them are failing or succeeding after having failed (thus cleaning up all the extra files that were added)


Sorry about the hectic sounding post, I wrote this on the fly when I first tried out Komodo 4.3 :-P I’m going to hold of reporting bugs until alpha2 or beta1 is out and if these issues still persist then I’ll try to allocate time to report any of these bugs / feature requests and hopefully other people will enjoy the fixes that will come out of it ;-)

Advertisement
Tags: , ,