Comments for GQAdonis http://www.gqadonis.com Cool as the other side of the pillow... Thu, 04 Mar 2010 20:34:51 +0000 hourly 1 http://wordpress.org/?v=3.0.1 Comment on Storing Images in Database on iPhone by Rob http://www.gqadonis.com/?p=171&cpage=1#comment-752 Rob Thu, 04 Mar 2010 20:34:51 +0000 http://www.gqadonis.com/?p=171#comment-752 Another good iPhone app tutorial website that has helped me out has been www.iphoneapptuts.com Another good iPhone app tutorial website that has helped me out has been http://www.iphoneapptuts.com

]]> Comment on An Idea for iPhone and Mobile: Cross Platform XML Object Binding with JavaScript by GQAdonis http://www.gqadonis.com/?p=156&cpage=1#comment-718 GQAdonis Fri, 29 Jan 2010 17:02:10 +0000 http://www.gqadonis.com/?p=156#comment-718 <p>Thanks SO much for your feedback! First let me say that I would LOVE to work with you and your team to provide this type of functionality. I will email you to discuss how we get started right away. I want to include iPad development (with considerations for other existing and upcoming tablets as well).</p> <h4>Answers to your questions:</h4> <dl> <dt>What would the XML look like?</dt> <dd>It would look similar to XAML with extensions to support data binding and script execution (JavaScript or any other language).</dd> <dt>What would I use to generate it?</dt> <dd>I would provide plug-ins to well known designer/development tools to generate the XML/JSON that represents components of the application.</dd> <dt>Would JSON be an alternative?</dt> <dd>Considering that JavaScript would be my chosen scripting language, JSON is indeed an alternative I would consider. I chose XML, because it is easily transformed from XAML or MXML or Android's XML spec using XSLT. However, there is no reason XSLT can't generate JSON as well.</dd> </dl> <h4>The Development EULA</h4> <p>Because Apple allows "in app" purchase where functionality is "unlocked" I thought restrictions might be relaxed a bit. Also, if the application has a modular structure to begin with, it would be considered complete if part of its function is for the user to select sub-components. Modularity is part of the "complete" function. This is a thin argument, I know, but I figure there has to be a way to get this to pass in some form--especially since this restriction MUST be opened up to fully support iPad development.</p> <p>Look out for an email today from gqadonis@me.com to discuss working together.</p> Thanks SO much for your feedback! First let me say that I would LOVE to work with you and your team to provide this type of functionality. I will email you to discuss how we get started right away. I want to include iPad development (with considerations for other existing and upcoming tablets as well).

Answers to your questions:

What would the XML look like?
It would look similar to XAML with extensions to support data binding and script execution (JavaScript or any other language).
What would I use to generate it?
I would provide plug-ins to well known designer/development tools to generate the XML/JSON that represents components of the application.
Would JSON be an alternative?
Considering that JavaScript would be my chosen scripting language, JSON is indeed an alternative I would consider. I chose XML, because it is easily transformed from XAML or MXML or Android’s XML spec using XSLT. However, there is no reason XSLT can’t generate JSON as well.

The Development EULA

Because Apple allows “in app” purchase where functionality is “unlocked” I thought restrictions might be relaxed a bit. Also, if the application has a modular structure to begin with, it would be considered complete if part of its function is for the user to select sub-components. Modularity is part of the “complete” function. This is a thin argument, I know, but I figure there has to be a way to get this to pass in some form–especially since this restriction MUST be opened up to fully support iPad development.

Look out for an email today from gqadonis@me.com to discuss working together.

]]> Comment on OpenGL and 3-D Game Development Resources by Charlotte Miller http://www.gqadonis.com/?p=101&cpage=1#comment-711 Charlotte Miller Fri, 29 Jan 2010 00:18:25 +0000 http://www.gqadonis.com/?p=101#comment-711 Please don't take this the wrong way. I think your overall ideas are fine but you might want to put a little more thought into your next posts. I say this becuase it seems like your writing style has gone downhill a bit as opposed to your previous posts. - C. Please don’t take this the wrong way. I think your overall ideas are fine but you might want to put a little more thought into your next posts. I say this becuase it seems like your writing style has gone downhill a bit as opposed to your previous posts. – C.

]]> Comment on An Idea for iPhone and Mobile: Cross Platform XML Object Binding with JavaScript by Lee http://www.gqadonis.com/?p=156&cpage=1#comment-709 Lee Thu, 28 Jan 2010 18:27:45 +0000 http://www.gqadonis.com/?p=156#comment-709 Interesting ideas. There is one thing to be aware of though. If you load functionality, your example is updating by loading XML, Apple will reject any app produced using your libraries. This is the problem that PhoneGap had when they were loading the HTML, CSS, and JavaScript files from web servers. It was a violation of the 'application must be entire' clause of the development EULA. I'm also somewhat concerned that Apple may not allow you to have your own JavaScript interpretation engine due to the 'no interpreted language' clause in the development EULA. What would the XML look like? What would you use to generate it? Would JSON be an alternative? It is easy to convert from JSON to objects on all of the major platforms but harder with XML Rather than invent the wheel from scratch why don't we work together? Contact me at yenrab@cableone.net Lee QuickConnectFamily author Interesting ideas. There is one thing to be aware of though.

If you load functionality, your example is updating by loading XML, Apple will reject any app produced using your libraries. This is the problem that PhoneGap had when they were loading the HTML, CSS, and JavaScript files from web servers. It was a violation of the ‘application must be entire’ clause of the development EULA.

I’m also somewhat concerned that Apple may not allow you to have your own JavaScript interpretation engine due to the ‘no interpreted language’ clause in the development EULA.

What would the XML look like? What would you use to generate it? Would JSON be an alternative? It is easy to convert from JSON to objects on all of the major platforms but harder with XML

Rather than invent the wheel from scratch why don’t we work together? Contact me at yenrab@cableone.net

Lee

QuickConnectFamily author

]]>