Pixelframe: One dot One

Pixelframe 1.1 is out. Written in 1/2 an hour of flow.

Get it at the Pixelframe Hompage

Pixelframe feedback and what next

Some folks at YoungCoders gave me some feedback about Pixelframe. One big criticism was that the client doesn't work without javascript. So for One dot One Pixelframe will have the following changes over One dot Oh:

• Client will work even with Javascript disabled, using static links
• Different loading images for admin and client, to suit the theme
• Default theme has the thumbnail bar moved to the left. This is better for usability. Also the theme is a bit darker.

The IE6 max-width problem still remains, and I will not waste time fixing it, if anybody has a patch please send it to me.

So now Pixelframe is done. What next? Well I have already started planning an Tetris clone called TetraBlocks. It will be written in C++ and SDL. Here, have a tetramino.

Pixelframe: It is DONE!

Pixelframe is ready. You can grab it from http://22bits.exofire.net/browse/code/pixelframe . Please report bugs at the Issues page .

Pixelframe: Almost there

So after 3 weeks of development on getting it to work in Internet Explorer, Pixelframe is ready. Testing is almost complete and after wrapping up a few loose ends it will be released. Some of the things remaining are converting PNGs to GIFs since IE has a problem with displaying PNGs, handling an unforeseen theme error, and a few look-n-feel changes. You can check out the almost working version ( uploaded at the time of writing this post ) at http://22bits.exofire.net/demos/pixelframe/

To IE or not to IE

Before I begin
-------------------------------------------------
Statuatory Warning: The below scenes may be disturbing
-------------------------------------------------

Pixelframe was once upon a time chugging along just fine and I was ready for a release about the 15th of April. Then along came the world's Favourite Browser and my life ( atleast the Pixelframe dedicated process ) has become worth dropping to /dev/null. I am so^googol sick of Internet Explorer. It took me one week to get the client working. The client has only 4 user generated actions.Now it seems like it will be two weeks to get Settings to work. Maybe I should just release Pixelframe and fix the IE bugs in a maintenance release. After all no webmaster worth his salt uses IE.

Here's the problem:
EVERY action triggers some error, if I am lucky only one, normally a dozen, due to some unsupported or badly implemented property. But it would have been fine in any decent browser. In IE it means doing the following

1. Click on the Yes button for 'Do you want to debug?...'.
2. Say which debugger you want even when their is only one.
3. Kill the Microsoft Frontpage installer.
4. In the debugger again select a debugger, when the only option is script debugger.
5. See what the problem is and click break.
6. Quit and again say Yes to are you sure you want to quit.
7. Rinse and Repeat for every error.

As you can see this will slowly push any web developer of the edge. Which means I spend barely half an hour on making it to work on Internet Explorer. More than that and you will find me in the cuckoo pot. These things make me wonder if its worth writing a web application if the world's most used browser won't even support it properly.

I need a good dose of antidepressant with a dash of music...

Back in Business

I forgot to post, my computer's back for 2 days now and Pixelframe development is back on track. I have given up on the max-width property in IE, because no matter what expression() I use, it doesn't work.
As for the settings page, the style isn't getting applied, but most of the Javascript errors are ironed out. ~2 days left for it to be ready. Need to start writing the themeing docs.

Scrap the Schedule

Pixelframe will not release on Sunday, nor will I be doing anything for 2-3 days. My motherboard decided to conk out today morning, so I all development has screeched to a halt till atleast Monday.

Sorry.

Pixelframe: Getting Closer

Pixelframe is getting closer and closer to finishing, in fact if Internet Explorer stops hiccoughing every now and then it will release on Sunday. Right now I have uploaded version 0.9 since the feature set is complete, only two problems are left. Both unfortunately and logically are due to Internet Explorer

1. IE refuses to show the settings page.
2. There are problems in IE with respect to maximum width.

As soon as these are solved Pixelframe will be released. If you know a solution to the second problem please comment. Meanwhile I will be trawling Google.

For 0.9 Demos check the following albums ( I recommend any browser other than IE for now ):

• Demo
• Inkscape

I welcome your views and suggestions.

Pixelframe Preview

As Pixelframe is nearing completion I have uploaded a pre-alpha not as a download but as a demo. Most of the features are complete. The few remaining are sorting out bugs and writing some documentation. To see the demo with two galleries try these links

• http://22bits.exofire.net/demos/pixelframe/client/?album=Wallpapers
• http://22bits.exofire.net/demos/pixelframe/client/?album=Inkscape

If you have comments about improvements, please post them below.

Introducing Pixelframe

In Trac(k)ing I mentioned the "secret project" I was working on. Well I have decided its time to let the world know what it is, even though its not finished yet.

Its called Pixelframe.

Pixelframe is meant to be a lightweight image gallery. It uses PHP for the backend and my custom javascript toolkit ( called Juice ) for frontend effects and ajax requests. Juice will also be released seperately once it is done. Pixelframe is easy to setup and use and doesn't have ( and won't have ) a lot of features. It is purposely made to be featureless. For description and development status check the Pixelframe page on Google code .

For now those interested can check out the latest bug free build which has the backend almost implemented. --> Demo