Release today?

#1 Looking forward to this. :)

#2 I will know shortly. I've been asked to go to a meeting to discuss the release status. I want to release today, but it's not 100% up to me.

#3 We are having problems with the installer, documentation and the website. We are still working and probably will be until the late hours, but the release is most likely slipping. I can have a new estimate after a meeting tomorrow.

#4 Rabble rabble! Preview 2? :)

#5 I don't see it in My Products so I'm guessing you didn't make the release.

I don't mean for this to come off the wrong way but ... Your first new release since your re-imaging is late. Not the greatest sign in the world.

However, it is better than your first new release being buggy.

#6 I don't care so much if something is late, as long as we get frequent status updates on whats going on. I understand things take time to get right and when you do release you want it done properly. So woot! for positive updates that at least we are very close to getting a new stable release.

#7 @All - Thanks for the understanding. I will continue to update you on the fly. Right now things are looking very positive and I believe everyone will really like the final release and new docs. After this release we are going to reevaluate our dev cycles, release standards and update frequency. For now, we are targeting a home run for this release and I think we are moments away from achieving that goal.

#8 Awesome

#9 So what is the deal on mouseDraggable these days?










Anyone got any links?










I couldn't find anything as I trying to run a level, dragging just one large imageMap with the mouseDraggable behavior.

#10 @rennie - I told you before that mouseDraggable is disabled and will not be enabled in the future. Instead, the new docs will show you how to do simple dragging using oniPhoneTouchMove.

#11 yay ... i can't wait to see all new stuff coming ..... i'm checking this post hour after hour ... lol

#12 sweeeeet.


:::)))(((

#13 michael,
what about pinch zoom.
crucial (arguably) feature.


:???


:::)))))))))

#14 Not this release. But I did some research and testing over the weekend for a future release containing the functionality. It's not trivial.

#15 Cool.

I have looked it up,
but still looks heavy duty as in, looks like a lot of work done to the engine.. be it, there are two resources(/posts?) that describe what to do, but as I say it seems quite hefty... tho I am sure I could follow. I am bothering asking in that... if you issed it with the next release... would it be a simple behavior like script? Or would one be required to copy paste a lot of stuff/make adjustments to the engine? And... If I follow the posts made and make those adjustments, is that the best bet for the next 6 months?


Cheers!


::))(

#16 @rennie - For things after 1.4.1, well...you'll have to wait for now. I can't commit to what the end result will be. Right now I'm exploring options for implementing the true gesture system exposed by the iOS SDK, but I'm already irritated with it.

The true gesture system is directly attached to a UIView, unlike the touches functionality. iTorque 2D does not render on a UIView. It renders directly onto a Window. This is a roadblock at the very start, so we are exploring options for better multi-touch and gestures.

However, this was all outside the scope of 1.4.1. This version being released shortly is all about bug fixes and updated docs.

#17 What about the android implementation? As it's open-source. Is likely to be a good implementation.

#18 And from out of left field!

@Alistair - No plans for an Android implementation. Our focus is on T3D, iT2D and T2D. Get them stable, get rid of bugs, get better docs and demos.

#19 Open source does not guarantee anything about quality (good or bad). It just IS. Remember that GG would then have to support a far wider range of devices than for iOS, where just 3 screen resolutions and 2 generations of GPU already make consistency a bit of a hassle.

They've got their hands full with the current platforms, and despite the number of sales of Android devices the users simply aren't buying apps in droves like on iOS. The general impression app developers have is that the users are cheapskates ;)

#20

Quote:The general impression app developers have is that the users are cheapskates

You know, I always wish I could counter that argument. Then I look at the apps on my Droid I've had since shortly after launch and I realize that the only apps I have are free ones. Then I look at the iPad I don't even own and realize that I have at least one paid app on it.