Taskboard 0.1

After some frustrating false starts and blind alleys, I can finally announce Taskboard 0.1 is complete. It’s really just a prototype, but it has the basic functionality. Now that Iteration 1 is done (sortof), I can move on to Iteration 0.

Here’s the swf:


and here the repository at revision 38:


I still have some cleanup work to do, both with the code and the repository, then I need to go through acceptance (and maybe some testing), but as far as I’m concerned, we’re feature complete.

Here are screenshots of our celebratory feast:

Next I’ll go back and do iteration 0, and get my automated build, deployment, and testing; document requirements and defects; and build a backlog for future iterations.

Then comes the hard part.  After the prep work, I won’t be adding new visible features, but I’ll be refactoring into an MVC framework (Mate & FlexMVCS are candidates), setting up sensible test fixtures, and plugging in the server-side functionality, first with simple HTTP or AMF Service, then with BlazeDS and multiple users.

Flex, PHP, and WebORB business model

I was looking at WebORB, which is a Flex remoting framework, but I noticed there were no docs, not even for installation. I believe you can get documentation (or at least “support”) if you purchase a subscription.  Their “knowledgebase” consists of a FAQ which is really just a bunch bogus questions that basically say “should I buy a license?”, “why should I buy a license?”, etc.

It’d be better, frankly to not even hint at documentation, or give free downloads.

If I heard that there was a commercial product that did what I wanted, I’d want to see a feature list.  If I was interested, I’d pay for it.  Giving away the product and then hoping users get frustrated and pay for a license (excuse me, I mean subscription — see the FAQ for why it’s a subscription and not a license — though I suspect the real, unstated reason is that may actually be open source code that they don’t have a right to license) isn’t a good model.  It leads to frustrated potential users tweeting and abandoning the product.

This may sound like the JBoss model, but at least JBoss clearly stated that docs cost $10 (maybe at first they didn’t.)

Anyway, the error I was getting looks like there’s something breaking that eAccelerator is choking on:

[4040] EACCELERATOR: PHP crashed on opline 10 of onWriteText() at C:\dev\weborb\php\3.5\Services\Weborb\Management\Codegen\Codegenerator.php:176