Saturday, June 23, 2007

Indications along the way.

The following tells me Acropolis ( ) is adhering to a common limitation placed on "evaluation" software (i.e. a limited use package to allow the user to try the software capabilities without being able to build full blown applications). This kind of limitation is usually applied to closed beta where 'partners' are given full use and the general public gets the limited use:
Issues with Acropolis...
I have been poking around inside Acropolis for a little while now and have been attempting to make it work for some sample apps
By: Kevin Hoffman
Jun. 22, 2007 07:15 PM

Here's the rub: I can't create windows outside the Shell that contain parts. That's right. There's no such thing as File -> New -> Acropolis Window. A forum poster suggested that one workaround might be to create a standard WPF window, drop a partpane into it, and then programmatically, at runtime, use the pipeline manager to obtain an instance of a Part and stuff it into the part pane in the new window. Sorry - I don't buy it. If I have to hack in order to pop open a simple dialog box with a couple parts in it, then the framework is broken. Note to Microsoft: Beta 1 or CTP2 of Acropolis needs to have a Visual Studio "Orcas" template for creating a new Window that is a top-level part pane container. Period. This is a showstopper. While it might be nice to assume that in a perfect world all interaction with a user takes place in a single framed window, that's not how reality works. I can't think of any desktop apps that I've written in recent history that performed all their work in a single window.
Ok, I'm done ranting. Time to go back and spend some more time coding.


So isn't that strange?

I don't know what you're thinking but I'm thinking this is like Apple's half-baked ZFS or like Sun's kinda-sorta JavaFX license. Looks to me like somebody is holding the leash up short and not letting the users get too far with the goods before buying.

So if this is a "free download" from Microsoft, it comes in the guise of 'crapware' - that stuff you get to try for 90 days then you have to buy it.

But, this is worse. If you don't get the "full" Acropolis, you can only build single window gadgets widgets and wowies.

So, who is putting the evaluation limit on Acropolis here as it's being sent out to their echelon of independent developers?

Probably the same who kept Sun from being able to issue a license for JavaFX.

Probably the same who told Apple they were only going to be able to use a read-only version of ZFS.

Now, the skeptics around us will say we're crazy. They'll say the companies hold up development issues based on many licensing issues and they may not want to put out . Darn tooting because no self-respecting developer or architect or project team would put out something half-baked.

The only people that do that are desperate market guys or clever lawyers.

But marketers wouldn't do this. They would have awhole bunch of flowery language about their licensing strategy and blah blah blah survey for feedback and duh dit duh dit duh dah community adoption and yada yada yada 'not enough time in the day' or SOMEthing beyond a shove it to the developer and listen to him yodel for the sheep.

Nope. This looks like Microsoft got bit with the same licensing snake Apple finds itself with ZFS and Sun finds itself with javaFX. Almost but not quite. Snakebit.

Yeah. Licensing. Lawyers are holding them back. Lawyers are holding Microsoft clients from exercising the full power of 'Acropolis' the VCSY technology clone.

So the skeptics are right. Bless their little hearts. I just wonder how long it will take before they themselves realize they are right.

No comments: