Bakerstreet, with all due respect, 'neat' isn't missing the point. Surely if i want to have a mail checker, a clock, and a net meter, having a small exe is more efficient than having the whole of DX running? While I couldn't state tht as fact, I would like to think so. So take a step back, there's more to it then the end result you visibly see on your desktop.

As a CG Artist, memory is precious, and while I love Stardocks apps, too many runnign at once does see the old memory hit go quite high.

Cheers

PlayTime: if their computers are too slow to run DesktopX, they'll be too slow to run the standalone exe. The standalone exe is DesktopX AND the object all in one. That's all it is. I don't know where people got the idea that they would be any less resource intensive.

It is slightly less resourse intensive in that the executable itself is smaller, there are no GUI dialoge, no wallpaper, desktop, workarea, systray code etc at runtime. That said, usually graphics take most of the overall object size in RAM.

Just one more guy's opinion here. I'm a Developer for an international franchisor. I write the software that we sell to many of the franchisees who use it to run their day-to-day operations. It would be easy for me to justify spending $499 of the company's money for the ability to say, use DX Pro to create an interactive tutorial for the software we sell. Using DX Pro, I could create the tutorial and have it interact with my program and my users because of DXScript. And the ability to include it all in an EXE for our users to run is simple and smart. Sure, I could do this with tons of other DEMO APP and TUTORIAL creators, but with DX Pro I get so much more (like alphablending and vb scripting).

At home, I'm a Object Desktop subscriber and a DX fan for my home machine. I also enjoy creating unique objects to share with other users on wincustomize. Would I personally pay $499 for DX Pro - no, for I don't need it for commercial development. Is it worth $129 for me (again, personally)? No, not when I think about my OD subscription. I think the idea of $55 to $75 for non-commercial OD subscribers is fair. A lot of us hard-working people don't have that much cash to through around for software when it comes to home use. My OD subscription is already a luxury for me, as it is for most home users I'm sure. I'd have to spread a-hell-of-a-lot of joy creating .EXE's at home to make DX Pro worth anything more than $75 more for me, a home user and OD subscriber.

I hope this reads as well as it does in my mind. Thanks for listeni-- err, reading.

"Surely if i want to have a mail checker, a clock, and a net meter, having a small exe is more efficient than having the whole of DX running?"

CAClark: Actually, I would have to disagree, because it isn't one exe, there are 3 executables in your example. With such 'themes' each would be handled independently by the OS.

DesktopX objects aren't natively standalone, so you have to assume each executable is going to have a hunk of DesktoX in it to enable it to run. This is no big deal in a theme, because all the objects rely on the same 'mother' program. In the case of your example above, though, each item would have included it's own hunk of DesktopX. Instead of several objects relying on one background app, you have several objects each running with their own, redundant support code.

Frogboy will correct me on this if I am wrong, but I can't see how else it could be done, at least until the next version that relies upon DesktopX already being installed. That is why I said, if people are going to use more than a couple of these standalones, they would be much better off just using DesktopX, and have the added functionality to boot.

**

FYI: the conversation moved to the messageboard about a 4th of the way through. It might catch everyone up if they shifted there. Frogboy knows what he is doing, and while I think his original plan was best, his plan-of-action seems like a good one nonetheless.

I love my toys, but I couldn't justify spending $500 on an app unless I was making my living with it. But I also spend $100 on games or toys when I want. I just spent $100 on PSP8 because my goal is to become a skinner, and the expense was worth it. I don't have money to throw around, but if I buy a program I really like, I quit worrying about how much I'm using it, it's enough that it's there when I do want it. So, I might not have a whole lot of people that would use my widgets a lot, but I have only one person that would even consider using DesktopX. That being the case, the $100 upgrade from ObjectDesktop is something I would definitely do, as soon as I had the bucks. I've only been into this community since April, but I couldn't even begin to think about using an "ordinary" pc anymore, they look wierd when I work on someone elses.

I don't know. I've been doing some thinking about this.I can't see paying 499 for a corporate use, and neither can I see paying 129 for home use.  Let me explain. 
 
With the Pro version, you can only make EXE objects, not themes.  One could not go after companies and sell them corporate branded desktops, you'd need the Enterprise version for that, and that well is just way too much up there in the price list.  To hope getting your money back from the 499$ expense, you'd have to basically sell a whole lot of 3 to 4$ clocks and desktop calendars... The price of DX Pro has been compared to the price of Flash. I'm sorry, but it just doesn't compare. I can justify the expense of Flash in a heartbeat. I pay it back in just one single cotract, which I could only hope to do with DX Pro if I could see a whole desktop suite to a company, which I can't.  No, to me, I can't see the 499$ corporate version being worth the risk for a huge loss.
 
As for a 129$ home version, again, I think it's a lot of money for just being able to make EXE's and send widgets to friends and families. Personnaly, I don't spend 100$ per month in games. I don't even spend that per year.  I think Object Desktop is well worth it for 50$, no doubt about that. But if I balance that with 129$ for just turning an object into an EXE? No, can't see it either. But I'm sure there are companies ready to buy the 499$ version, I just can't think of any I know. As there probably will be a few people ready to buy the 129$ home version. BUt how many?
 
I guess time will tell.

Hmm a idea i had posted in msgboard...

A 129 version could make exes, but all those exes from 129$ version could warn that it was made from non-commerical version of desktopx pro ONCE. (Once per exe that is)

That will easily block commerical sellers from selling those exes from 129$ version and dodging the extra 350 or so price. Clicking 'OK' once is not inconvient for regular customers.

i admit its a great idea making stand-alone exe's, but is it worth the extra money for one feature?

To everybody that thinks $499 is expensive for a corporate level product, you need to think about the -real- capabilities of what DesktopX can do, when you can export files as .exe's. It goes beyond little clocks, and calenders and such.

Suddenly, Stardock & Desktop X finds itself in a whole new ballpark. With the capablities of Desktop X and .exe's the doors are opened for things (possibly, from what I've gathered from DX's current, and upcoming capabilities,) as autorun programs for CDs, product demo apps, product training apps, etc - as well as rapid application development (to an extent?)

Compare the prices of some of the industry leaders in these areas already:

Demoshield 7.5: $699
Flash MX Pro 2004: $699

I don't know if DX is capable of more 'complicated' apps/designs yet (Lack of experience with it for me...) but when I think of the .exe export, these are the first things I start thinking of for professional use. Companies /always/ want an eye-catching autorun solution, for instance - and DX is great with the eye candy.

(Of course, I could totally be off base and over-estimating DX's capabilities as well... by now I'm sure I've mentioned enough that I haven't kept up with it. 1.9b was my last version. )

I think that FChestnut has something.

The purpose of the Comersial version is to protect the code/intelectual property and make money. Where as the personal version is to get something to friends and family without care of sharing the code. That should be the insentive to upgrade.

A few questions though?
What is the averge size of the executables? (Depending on graphics of course)
Is the memory shared with other stardock programs?
What is the memory usage on small objects?
What about Upgrades?
How will it work whatn version 3.0 is released?

I like the new Pricing Ideas though.
$499,$129,$99

My .02
Cmeisman

I just exported just the default blue object as exe: 300Kb file size and around 1Meg in RAM. That's the stand alone Exe footprint, so very very low. The only "overhead" is the very core code and graphic renderer, plus plugins (differently from DX, there are no hooks, wallpaper, workarea, systray management components and such). The extra RAM and size is for graphics and other plugins.
Exes are totally independent by the current DX version. If you compile them with version x.y, that'll be the code they'll use at runtime, that is statically linked, so there will never be issues with installing runtimes in system32 and such. Also, this means the objects will always run as they are meant to.
You can have a widget made with version x.y run with another widget made with version z.w.
It makes to reason to try and mess with memory or libraries sharing, it already very light like this and instance isolation makes EXEs very solid and easily distributable (i.e. no installation needed, no need to touch system32 and registry).

kthxbye:  
 
Suddenly, Stardock & Desktop X finds itself in a whole new ballpark. With
the capablities of Desktop X and .exe's the doors are opened for things
(possibly, from what I've gathered from DX's current, and upcoming
capabilities,) as autorun programs for CDs, product demo apps, product training
apps, etc - as well as rapid application development (to an extent?)  
 
 I may be way off here. Either that or you are. Anyway, I can't
imagine using DX for the applications you described above.  Some other
products make those jobs much easier.  AFAIK, Desktop X is a desktop
enhancement software, not a training tool, not a slideshow tool, or anything the
likes. It's made to create objects, and have those objects interact with each
other in odre to accomplish nice desktop finctions. IE: shortcuts, menus,
clocks, calendars, system meters, etc.I'm not saying it would be impossible to
make a tutorial or a product demo using Destop X objects, but man, it would be
hell of a lot of work compared to other existing tools.

you keep comparing prices but those software do alot more than exporting to exe. it is a great idea, but $470 for exporting to exe? thats like buying photoshop because it has a better zoom function than paint shop pro.

Paxx: I probably am, yeah, but with support for such things as com objects, VBSCript, JScript and (Eventually, according to SD,) C# and XAML - /EVEN THOUGH/ it is meant as desktop ehancement software, it could be used ideally, for much, much more.

Frogboy (I do believe it was him,) already said they made a slideshow .exe with it - so even if it wasn't /meant/ was that originally, it's shown it's quite capable at it. As soon as you put robust scripting support into something, it becomes harder and harder to say "Oh, it's just for 'x'." Especially if it can make .exe's.

Karb0n: Actually, that /is/ pretty much all that demoshield does. You give it the content you want/need using scripts/widgets/etc. and it makes an .exe for you.

A lot of companies who buy Macromedia Flash also sometimes buy it for specific reasons only. It wasn't the best example, perhaps - but there -are- people who buy Flash with doing say, a tutorial, or demo, in mind, who never even touch its other capabilities. It balances out - Desktop X has that whole 'desktop enhancement' capability too.

(I could argue your last point too - because if Photoshop's zoom feature had feature 'x' and I /needed/ that feature, than the cost of Photoshop would be easily justified, if PSP didn't support it. Hell, I /did/ buy Photoshop, as a home user mind you, over PSP simply because it's the one I'm most comfortable with.)

. Sorry but it's just amazing how myopic some people are.

Paxx: I do agree, some of the things people have mentioend DesktopX could do are better served by other programs. What DesktopX allows developers to do is create highly customized looking applets very very quickly. Its best use is probably in the creation of custom interfaces.

Any software developer will tell you that trying to create something that looks slick on screen is a long and tedious process using conventional softwrare tools. With DesktopX it's easy. And bear in mind, you can mix and match flash and DesktopX objects together.

Let me give you one example:

With DesktopX Pro, I could export an auto run installer menu program that in is incredibly slick looking that was created in less than an hour. 

Working for a game company, we have tried other mechanisms over the year to try to have a slick autorun screen and nothing remotely compares to DesktopX.  And that's just one example.

Any sort of GUI front end for launching a set of tools would make sense with DesktopX Pro. Any sort of on-line marketing would make sense. $499 is dirt cheap for this kind of thing.

karb, your comparison is meaningless because there is nothing that competes with DesktopX Pro realistically. If you're a commercial developer who wants to quickly be able to create stand alone "Skinned" widgets, this is the fastest way by far.

As I said elsewhere, commercial companies and developers pay real money for real software.  A DirectSkin license is $9,500. I have no doubt that people around here would make the same myopic comments about that pricing. But $9,500 is how much it costs and we have, at any given time, a half dozen to a deals pending.  DirectSkin makes more revenue for Stardock than almost any other product.

here is my opinion

firstly the LX price should be 129$ retail, 79.99$ for current Object Desktop users.

the retail price of 129 should include a standard one year subscription to Object Desktop, and the 79% upgrade for current OD users should add a full year to thier current subscription starting AFTER thier curent one expires.

secondly the standalone objects should be allowed to be traded just the same as all other stardock skins are now, however the non commercially licensed standalone objects should have contained in them somewhere that they were created by a DesktopX pro LX non commercial version and that they are NOT to be SOLD but can be freely traded.

the way i see it just because these are standalone objects doesnt mean that they necessarily need to be purchased, just like the windowblinds skins out now, ive seen and have downlaoded skins that are FAR FAR better and more funtionall than some of the skins that people including stardock and wincustomize are selling yet they are being traded for free.

if certain things continue to slowly be sold instead of free then this type of community will diminish to people consisting solely of skins that are paid for, wich in my opinion would destroy not only this great group of people i have come to love here at WC but it woulkd destroy sales of Object desktop wich the sales were driven mostly because the skins themselves were free.


so to this i say take a stand againt what is becoming the norm and try to keep this as free as possible.