When I recently updated an Adobe AIR app I’d written for AIR Beta 1, I found that I had to go to enormous lengths to continue being able to use ExtJs as a selection & effects library for it. This is due to “eval()” being prohibited in the base Javascript on any AIR app.
Blueprint CSS Grid Tool for Adobe Air
October 26, 2007 By 12 Comments
I’m a big fan of the Blueprint CSS framework. In the process of using it to develop the base template for Banjo, the blog app I'm writing, I realized I need a tool to help me keep page elements lined up on the grid, both vertically and horizontally.
Blueprint comes with a background grid image to use for this, but it only works as a background, and it is not that useful when you are working with colors and final tweaks. So, I made a little (tiny) AIR app which will show a floating grid, sized at 18px and with Blueprint-sized columns.
Related posts
Updated Weewarify AIR app to Beta 2
October 25, 2007 By Leave a Comment
After more work than I expected, I’ve updated my Weewar status notifier to work with the Adobe Air Beta 2 SDK.
There were two tricky parts to the update. The first, separating the AJAX/UI logic out into a separate sandbox. The second challenge was getting rid of the pesky scrollbars AIR seemed to insist upon putting on my window.
Importing WordPress to Banjo
October 22, 2007 By 5 Comments
Thanks to Andy C I’ve finished the WordPress import script for Banjo.
That article gives instructions for direct SQL loading of a somewhat different blog database. I couldn’t use it directly for Banjo, partially because I’m through with using MySQL. I just can’t take all the UTF problems any more. I’ve gone all PostgreSQL all the time.
So my solution needed to speak MySQL and then directly create objects in Django. That way it could be used for any target database.
Banjo Blog nearing 0.1 release
October 19, 2007 By 13 Comments
I’m nearing release 0.1 for Banjo, a blog app written in Python on the Django framework. If you look at the mailing list, you’ll see plenty of people asking about a blog app, and the standard reply is that it is just so easy, almost trivial, to write your own that there is not much call for such a package.
I disagree
I really don’t agree with that logic although I do understand it. Blogs look simple, and stripped of everything else, they really are simple. Basically they are just reverse chronological posting of text on a page. No biggie, at least at first or second glance.
But the trick is in the phrase “stripped of everything else.” Once you start considering the features commonly available in blog apps, it gets quite a bit more complex:
Related posts
Oohgabooga launched
October 2, 2007 By 1 Comment
My premiere e-commerce client, Oohgabooga Island Traders launched yesterday. After doing a little dance of happiness, I sat down to think through all that went into it.
I used the Satchmo e-commerce framework for Django to build it. Of course I did, because I am a core developer on Satchmo, and a peripheral contributor to Django. They’re my absolute favorite frameworks for actually getting web apps done without going crazy.
To get Oohgabooga done, I had to add tons to Satchmo. I added an entire settings management system, a modular payment system, newsletter management, and a custom-order workflow/product-type. The great thing about doing all that was that the framework let me. It didn’t force me to do it “their way” or no way at all like some systems (CubeCart). And it didn’t make me hate having to work with ugly ugly hacks (ZenCart). Best of all, it isn’t PHP.
At the moment I’ve got three more Satchmo clients. It is rapidly becoming the core of my consultancy, which is no surprise for me. The world needed a strong framework for people who need a beautiful, fast, customizable, extensible cart.
[tags]satchmo,django,e-commerce[/tags]
Recent Comments