Are the values in the Array numbers or strings? i.e. x = 1 vs x = "" & 1

Development on C2/the runtime would not stop completely - it would just slow down. There's a steady stream of new browser features, compatibility changes, platform tweaks, bug fixes etc. that regularly need addressing, and we would keep doing that. There may be minor new features as well, but it would be more like a maintenance mode than a steady stream of new features.

One of my favorite apps in the world is PropellerHead's Reason. It was already very good before they added an extensibility API, but after they added that everything went into Turbo mode... third party developers have made dozens of super powerful add-ons that PropellerHead simply would not have had time to build themselves... in the mean time they instead spent their time making major core additions to the product instead of making all those instruments etc.. that the third parties made.

Adding modularity / extensibility would be a game changer.

Though not having a clear and certain export path to all platforms is also a big sore point... Maybe PhoneGap will take care of that for all new devices going forwards at least. The only thing I would be more interested in and willing to pay a couple hundred dollars for is an export to Unity like I have seen for Spriter so I could know for sure my game will work right on all the mobile platforms as well as larger devices... when I finally get my game done I do not want to fight with Cocoon, Ejecta, etc... to try to get it production ready.

> I've not seen any web UI frameworks that in my estimation compare to what we use at the moment.

>

I'm not sure I understood what you mean. The web is miles ahead of the desktop in terms of styling and widgets. There's no desktop equivalent for CSS, and although there are many desktop UI widgets, they're hard to integrate if they come from different sources, and none of them are as extensible as their javascript-based counterparts.

Where I work we make extremely high end enterprise applications and the front end UIs that the customers see are super advanced HTML/JavaScript/CSS/AJAX/JQuery/etc. However in no way is the state of UI frameworks and extensibility anyway near as advanced as in the desktop world. The reasons are obvious, the desktop (Microsoft .Net) is a continuation of decades of advances.

The equivalent of CSS in the desktop world is called XAML styles... same thing except more powerful... not that C2 has any need for cascading styles within the developer environment itself.

It is possible for some of the C++ parts of the current C2 to be turned into a "user control" and hosted inside the new UI (and call code with pInvoke) so that it can get up and running much faster by transitioning instead of starting over all at once.

You are not going to get a DataVIewGrid, PropertyGrid, Dockable toolbars and windows, XML + LINQ, WebBrowser control, advanced treeviews, DataSets, on and on all in one HTML framework... You would have to build a lot of things from scratch and patchwork a bunch of libraries together to get something only "close".

Only Scirra can answer what their actual percentage of market share is between Windows and all other OSes, but if it is like the rest of the world then the market share for Apple / Linux just wouldn't justify building everything from scratch with a technology base that has zero backwards compatibility with their existing code base.

Benefits from 64bit processing generally comes from the computer CPU handling large amounts of data in a continuous stream... which is why they mention video as showing a benefit. If your work is being handled by the GPU rather than the CPU then you will not see much difference with that work... it also does not help much with processing individual smaller amounts of data like INT variables or simple strings of text.

The editor is C++ and doing new UI features in C++ is generally a big pain in the ass, to the extent that a beta update can generally contain a basic implementation of a single new UI feature which is subsequently refined over the next few releases, or several engine updates in one beta update (which are comparatively easy and quick to implement, even for relatively significant new features). So usually it weighs up in favour of the engine updates. I think we are reaching a point where the engine is largely in good shape so perhaps now is a good time to return to editor UI features, but they are slow and difficult to produce. (I'd point out that had we done it the other way round we would end up with a slightly better UI and a seriously less advanced engine, so I think we did it the right way round.)

You could probably rebuild the whole UI and get extensibility features for free by redoing it in C#. For example the PropertyGrid control you use in the current UI already exists in .Net as well as the toolbars, dockable windows, etc.

At my day job most of my time is spent building server software, but after that work is done I get a little bit of time to build admin tools for those servers and I can whip them out pretty quick (and still very advanced) with VS / C#.

For example get extensibility for free:

http://msdn.microsoft.com/en-us/library/dd460648(v=vs.110).aspx

Yip, it's not about price, its about a right fit at that price point.

More info is needed to make a decision. Or some constructive reviews. Pity store only opened yesterday...

but once store gets traction, more purchases, more reviews, and info etc, then making decisions will become easier.

Bit the bullet and purchased. Will review it for others.

Thanks for the feedback.

In addition if you run into scenarios where this tool could have saved you more time if it had feature X let me know.

Once the new version is done and in the store I will make a video showing the tool being used.

I am shooting for this weekend to have the new version out.

> As far as price... well how much is your time worth?

>

You have not correctly understood =) I'm not complaining about the price, I'm talking about the lack of information. After buying it may be useless for some users, and will be sorry for the money spent.

I think that the video will help in this matter =)

Very true.

I am trying to get the new version finished and then I will create the video with the new features as well.

Thanks to those who have purchased already!

A new version is in the works which you will get for free once it has been released.

Great job!

If you can't make a demo version, please make a youtube video with a demonstration and examples.

This tool seems to be very interesting, but $34 is a large price to just look at it.

Good suggestion on the video.

As far as price... well how much is your time worth? This tool is all about saving on time messing with the data manually.

I have been using it since January and it saved me more than $30 worth of time.

Plus Scirra gets their cut and they deserve it.

Yep. Not sure why when I choose "duplicate" or "clone" it does not actually duplicate or clone and I have to go back through and reset things.

Basically I put all my variables into a dictionary and then save the dictionary in json format into the slot.

I can loop over the slots to do things like find an empty slot or whatever.

To clear a slot I just set it to an empty string (thus overwriting the json dictionary saved there).

I use IE a lot and simulate all my touch events with clicks... I have not noticed any problems.

Maybe your collision polys are not where you think they are.