401

(39 replies, posted in Development)

402

(3 replies, posted in Squashed Bugs)

During the download? Is this before or after you clicked "Install and Relaunch"? This is an odd place for it to crash. Hmm. Can you duplicate it by downgrading and doing the update again?

403

(1 replies, posted in Squashed Bugs)

This is not a bug. You can determine what application's notifications get shown in the Growl settings. Disable Cog or Last.fm notifications, and everything should be fine.

404

(28 replies, posted in Development)

Yeah, I noticed this a bit ago. The cue sheet plugin needs a way of telling cog what file(s) it's using, so the loader can ignore them.

406

(39 replies, posted in Development)

The mini mode is currently just the normal view rolled up. If I had the file drawer button in one, it would be in the other.

407

(4 replies, posted in Features)

The playlist is track-oriented, so a bitrate column wouldn't need to be updated. You would show the bitrate for the track, whether its an average for variable, or constant.

I need to rework the column code because Leopard is having conflicts (They added their own hide/show column methods), so I may add the others while I'm at it. I also think the info drawer should be redesigned to show all the columns and values for a given track, metadata and all. This way if you want a quick peek without showing/hiding columns, you can just pull out the info drawer. For info you always want to see, add a column.

408

(39 replies, posted in Development)

409

(39 replies, posted in Development)

410

(3 replies, posted in Development)

Actually, there is an example audio codec in the developer examples that does FLAC decoding and encoding.

Enter wold work also. It always plays the selected song.
I don't like the way cd players handle this, so previous wont be going to the beginning of the song, it'll go to the previous song.

412

(39 replies, posted in Development)

There is, I think. I'll look into it. This is a 0.09 feature though, so it'll be a while.

413

(39 replies, posted in Development)

414

(39 replies, posted in Development)

415

(28 replies, posted in Development)

How's this sound? I'll maintain 10.4 support up to 0.08. It'll likely be 6 months before 0.09 would be released (Assuming 3 months devtime for 0.08, and 3 months devtime for 0.09).

10.5 is going to allow quite a few changes to the plugin system, so I'd like to hold off on messing with that until I'm able to take advantage of that, otherwise I'd just be writing code knowing it's outdated and is going to be replaced, which isn't much fun. All of the current 0.08 stuff is doable without needing to touch Leopard, so I'll do that.

416

(28 replies, posted in Development)

417

(39 replies, posted in Development)

This is a quickly thrown together mockup, I'm not too concerned about pixels yet. I just wanted to make sure it'd be doable and usable. I now see that it is, and will work on getting the functionality in, then we can all worry about pixels smile

418

(1 replies, posted in General)

I've already read it, but thanks! There's actually a few places where I can take out some ugliness thanks to Leopard.

419

(4 replies, posted in General)

420

(39 replies, posted in Development)

421

(28 replies, posted in Development)

I've been debating on whether or not to make 0.08 10.5+, (0.07 is guarenteed to be 10.4 compatible, so don't worry about that!)

Keep in mind (if you don't want to switch yet because leopard is still unstable) that 0.08 is _at least_ a few months away. I'd imagine Leopard will have an update or two before then, so I don't think it will be a huge problem.

Some of the nice things that 10.5 brings are not user-facing, but do allow me to write better code quicker. A few things:
* Toolbars are a lot easier to make, so the toolbar based UI will come together a lot quicker.
* Type-ahead select. Leopard supports this natively, that means I can remove a monkeypatching hack I was using to get this working in the file drawer.
* Protocol additions. They now allow the requires, and optional keywords, which will make plugins a lot cleaner.
* Properties and fast enumeration, just a nice thing that will make writing code easier and less tedious.
* Checking the documentation to find that method is 10.5 only and I will need to go through some hoops to get it going in 10.4 has a demotivating effect.

Also, some nice things that will be useful, but likely won't be needed for 0.08:
* Garbage Collection. I have yet to decide if I want to use this in Cog. Usually I only spend a few hours each release hunting down leaks, so I don't think it's a huge problem, but who knows.
* FSEvent. Cog currently uses a third party class that uses kqueues to track file events. Leopard has a new FSEvent API that may be quicker. I haven't looked into this much yet. Tiger's built-in cocoa API for this type of thing missed a lot of events, so I need to look into this a bit further.
* Bundle unloading. This means plugins could be unloaded at runtime. This will definitely be handy once there's a plugins preference pane. Otherwise, you'd just be disabling them and they would still be using up memory.

In the end, it basically makes my life easier, but not really  yours. This is basically an outrage check, so I can see what people think and go from there.

422

(11 replies, posted in Archives)

It's likely not very time consuming, there are just other things I'm also working on that get higher priority at the moment. I will put it on the 0.08 list though, because it may be a nice feature to have, though I may hold off until 0.09.

423

(39 replies, posted in Development)

424

(20 replies, posted in Features)

425

(3 replies, posted in Development)

Using 10.5, I can't open flac with iTunes or Quicktime, so I doubt theres any support there. I've never heard of apple even wanting to add FLAC support to OS X (They do have apple lossless, after all). Perhaps you're thinking of the xiph.org QT Components?