Archive for the 'Progress' Category


“Save for web” on Tiger (10.4) requires X11 :-( 8

Oops, I just realized (merci françois) that ImageMagick, which is required for the save for web feature actually requires X11 to be installed. It is installed by default on Leopard but not on Tiger.

So if you are running Tiger and ChocoFlop always answers “This doesn’t seem to be a valid ImageMagick folder :-(” you just need to install X11. It’s on your Tiger install DVD. Apple didn’t find it useful to post it on the web.

In the next release I’ll make the error message clearer.

Adding some cute icons 0

I had some money on the paypal account (thanks to your support!) so I decided than rather than spending hours trying to design half-baked icons for ChocoFlop I was going to buy some from IconDrawer.com. I bought the classic pack and the add-on.

One day when this projects becomes more viable I’ll certainly contact them to get personalized icons. For now, I’ll just have a nice looking icon set to use for various things in the app.

Next version is going to feel quite faster 0

After reading some reports about the difference of performance between ChocoFlop and CoreImage Funhouse (Apple’s original showoff example app for CoreImage filters) I decided to rethink and rewrite the rendering stack of the app.

The biggest error in design is due to the fact that ChocoFlop was originally developped on a G4 mac mini which didn’t support any CoreImage acceleration through the CPU. As a result I had written a lot of small caches everywhere to make it feel decent on this machine. Over time however I stopped testing it on such machine. So in the end I had both disavantages.

CoreImage is designed around a simple idea: That you only need to render what you need to display. And ChocoFlop so far was working the opposite way. For example when applying a hue filter on a 10 mb pixel image the filter would get applied to the whole image. Also when painting the paint buffer would be applie on the whole image. This basically made using ChocoFlop on a 6 megapixel image a real pain, even on a modern machine (such as my first-gen ATIx1600@128mb macbook pro). To fix this problem the app tried to scale down the whole document an rescale it back for display while filtering. This was both quite slow and ugly-looking (big blurry pixels and filter handles that you just couldn’t grab without blocking the whole UI).

After working on it for a while I am glad to announce that the upcoming release (0.71) will feel – and actually be – much faster than the previous series. When it gets released I invite you to open an 10 megapixels image and add a filter (say torus lens) on it and drag it around. It will change from unuseable to smooth, really. Same goes for paiting: the current release is not useable on a 10 mbpixel image, you’ll paint big straight lines and it’s pretty unresponsive. In the upcoming version you can actually paint what you want to paint (on my machine at least).

I still have to tackle so issues and I am bit tired to finish them today but hopefully tomorrow will be a more productive day (a.k.a. the kind without a sister crashing in at your place with beers when you were just about to get rid of a nasty bug). So stay tuned and expect great changes!

Oops, Time to wake up! 1

Today I decided to start some work on ChocoFlop again (yeah I know, it was like August the last time). Specifically I wanted to integrate a new painting method based on code gently sent by Steve Israelson (thanks Steve!). It turns out the whole way I do painting/rendering in ChocoFlop is flawed and it might take some time to rewrite the necessary parts. Not to mention that the new Leopard brought my attention to some completely buggy locking in the app too and I feel like I should fix these before releasing.

Anyway, I just realized the current version is set to expire.. in 10 days! Oops. Better get this release ready before next week-end or I fear I’ll get some angry comments…

(If you read this in ten days, and it’s the latest post, please slap me).

I am using ChocoFlop 5

I have started doing something I hadn’t done in quite a long time. Trying to actually do something useful in ChocoFlop rather than just playing around with it. I am trying, mostly as an exercise to come up with a new design for the website. And I am decided to only use ChocoFlop to do it. That’s quite an adventure. I am coming up with so many annoying things per minute, it’s hard to keep up the motivation. But the positive thing is I’ll be fixing these soon since it’s the only way I can work on my design.

Top annoyance so far: pressing the arrows when you have a selection should move the selection.. but no, it cuts from your selected layer and moves it by one pixel :-( And I don’t mention all the crashes when playing on a document with many layers. The Hue filter seems to be pretty crashy.. maybe because it’s a fast one and changes happen rapidly. I really need to revise my threading strategy.. I mean if you could call that a strategy.

I hereby promise no to update the website design until I have been able to entirely design it using CF.

Panels moving to wrong place? Disable animation 0

Since I won’t be releasing today a quick note to users who see the panels moving to weird places at start. Go to preferences / appearance and uncheck “ANimate tool window at start”. It seems the animation and the new KBPanels don’t live well together.

Sorry about that, I always disable this option but it’s the default for new users… Anyway, I am getting rid of this initial animation at start in the next release. Probably tomorrow.

New UI screenshot 3

And finally, for those too lazy to download.. here’s a screenshot showing the new user interface.

photoshop cs3

Good night. And this time I mean it. Really. I do have a life. I guess.

Note to self: test BEFORE releasing :-) 0

Hum, it seems version 0.59 that I just released makes it impossible to use tools such as selection (lasso, circle or else) or text on any live filter. It kinda messes up the filter actually. I’ll fix this right now…

Problem on MacBook with GPU rendering 0

Hm… someone just reported that ChocoFlop outputs garbage when painting on the MacBook (intel GMA GPU). The MacBook pro however is fine. The only solution seems to use software rendering but that’s not helping much :-(

Thanks Andrea for reporting this.

That’s what it looks like:


(click for bigger image)

OOps for older machines 0

I just had the opportunity to test the previous (and the coming-soon) release on a G4 mac mini which has an unsupported graphics cards… and it seems the OpenGL mode is completely f..ed up :-(

I understand the reports I had seen about this previously. Of course this doesn’t happen using CoreImage mode. So in the meantime, use the prefrences to use full coreimage mode if your machine is unsupported. I’ll try to get that fixed in the next release ..

Next Page »