tom wrote:

Flex is a framework which sits on top of Flash so it won't work on iDevices.

Now for the second question that's out of my league...is there a way to fake or bounce this stuff so that it will work on iDevices?  I ask because I'm now on a team that is web based and uses all Flex, in which they have a way of the web page working iDevices without a complete/second re-write.

Yertle wrote:

tom wrote:

Flex is a framework which sits on top of Flash so it won't work on iDevices.

Now for the second question that's out of my league...is there a way to fake or bounce this stuff so that it will work on iDevices?  I ask because I'm now on a team that is web based and uses all Flex, in which they have a way of the web page working iDevices without a complete/second re-write.

I'm slightly curious about this...although I should probably just ask the guys at work...and since I should probably know it :P

tom wrote:

You may have noticed a slowdown in the frequency of updates recently - this is because I've started work on a pure JavaScript version of the player. This will allow WarGear to be played on practically any device with a web browser (esp. those which don't support Flash like iDevices).

Will one of these players be the 'primary' player?  Are they going to be identical?  When new features are added to the player will they get added to both the flash & javascript versions?

Raptor wrote:

I can test Android 2.3.4, IE (7,8,9), Mozilla, Chrome and Wii with my devices.  Count me in.

I can test almost all the same list as Raptor, with the exception of Chrome, and with the addition of IPad.
If you need volunteers, feel free to add me the list as well.

I now have an ipad and am willing to join in.

Ozyman wrote:

tom wrote:

You may have noticed a slowdown in the frequency of updates recently - this is because I've started work on a pure JavaScript version of the player. This will allow WarGear to be played on practically any device with a web browser (esp. those which don't support Flash like iDevices).

Will one of these players be the 'primary' player?  Are they going to be identical?  When new features are added to the player will they get added to both the flash & javascript versions?

Initially it will just be for mobile devices. However assuming the functionality of the JS player can match that of the Flash player at some point the Flash player will be dropped as it doesn't make sense to maintain 2 separate code bases.

Will the look and feel of the player be noticeably different?  I don't know much about the coding bases but I recall that on ToS there was an option to use the standard or HTML.  The HTML option reloaded the image after each move and wasn't too fun.

^ "...wasn't too fun" that should be changed to "ridiculously horrible" :)

No it won't be like that - I've worked out how to make the JS player act like the Flash version in terms of no page reloads required during moves. In fact it should be quicker and less resource intensive than the flash player, particularly noticeable is the quick load times.

Rest assured it won't replace the Flash version until all the functionality is there and it is superior to the Flash version.

See this tom? http://www.wargear.net/forum/showthread/1801/iSWiFTER

Yep interesting going to try it out - I've suspended work on the JS player to fix a few outstanding issues - currently working on the tournament tie-breaking update.