BambooInvoice 0.87 Release : DerekAllard.com

BambooInvoice 0.87 Release

August 25^th, 2008

BambooInvoice screen This release is mostly a bug-fix release, but includes a few features that I had been meaning to get around to, and also has some architectural changes that should allow for some neat things in the future. Mostly though, some real effort went into trying to make Bamboo as intuitive as possible - the growth in popularity has meant that I’m now seeing it installed in some rather “unconventional” server setups (GoDaddy… I hate you).

This version of Bamboo also includes an automated “new version check”. I’m hoping this will reduce the number of very old installations I’m seeing - the newer versions really are superior. The new version check is just a simple file read from the BambooInvoice website, no information is transmitted, but it can be easily disabled in Settings > Advanced Settings > Automatically check for new versions.

You can get the new version from the BambooInvoice website.

If you are a Bamboo user, and discover any issues with this version, please let me know and I’ll get them fixed right up.

Here’s a small sample from the changelog:

Naming changes on “private” invoice notes.
Further adjustments to how logos get included. I think this time all the issues are resolved.
Uploading a logo now changes both the web and PDF views.
Moved logo insertion code into a centralized location.
Added “Edit” option to Ajax client contact creation, move text into language variables.
Specified that logo inserts must be jpg or gif for PDF creation.
Flushed out new version check tool in utilities. Its functional now.

Happy Bamboo’ing!

Comments

Cliff wrote on August 25^th, 2008 @ 10:33

Thanks for the update. I’ll give it a looksee

Victor wrote on August 25^th, 2008 @ 11:15

Man Derek!!

Spend your time on EE 2 !!

Hehe we want it now…:’(

Just kidding,
Love to see this update.

-Victor

Lee wrote on August 25^th, 2008 @ 16:58

I am just curious as to why you moved your validation code into your controllers? I hadn’t really thought of doing that, so I’m just wondering your reasoning behind it. In particular do you think the decision will have any affect on controller size/maintainability as they grow in future releases?

Great work, keep it up!

Derek wrote on August 25^th, 2008 @ 17:02

I am just curious as to why you moved your validation code into your controllers? I hadn’t really thought of doing that, so I’m just wondering your reasoning behind it. In particular do you think the decision will have any affect on controller size/maintainability as they grow in future releases?

They were in views. That just felt wrong, but was the most convenient place at the time. I’m moving them now in preparation for a different way of handling this, but at any rate it makes more sense to me in the controllers, even though in one instance it means a bit of code duplication.

Lee wrote on August 25^th, 2008 @ 17:16

I see, that makes a lot of sense. I think you made a good decision. Any insight you can give on what your different way of handing validation in the future might be?