xmlvm-users — For current and interested XMLVM users, for public discussions and anouncements.

Re: [xmlvm-users] Problem getting touches

[Panayotis K. <pan...@pa...>]

On 01 Ιουλ 2010, at 5:02 μ.μ., Damian wrote:

> Sorry to bother you but, any news about this?. I've been trying to look at it and i've seen that the OpenGL screen doesn't let the touches get to the emulator, but I didn't knew how to fix it by myself.

Actually, I am not sure if this works in the emulator :(
In my system (mac) the emulator does not work correctly with OpenGL.

The patch is mainly for the actual Xcode project, and it is easy to apply it yourself.
See here:
http://xmlvm-reviews.appspot.com/64001/patch/1/31
http://xmlvm-reviews.appspot.com/64001/patch/1/32

Re: [xmlvm-users] Problem getting touches

[Damian <dam...@gm...>]

Sorry to bother you but, any news about this?. I've been trying to look at
it and i've seen that the OpenGL screen doesn't let the touches get to the
emulator, but I didn't knew how to fix it by myself.

On Thu, Jun 24, 2010 at 1:56 PM, Damian <dam...@gm...> wrote:

> Ok, I'll wait for the fix. Please, tell me when it´s ready.
> Thanks!
>
> On Thu, Jun 24, 2010 at 10:48 AM, Panayotis Katsaloulis <
> pan...@pa...> wrote:
>
>>
>> On 24 Ιουν 2010, at 12:27 ΠΜ, Damian wrote:
>>
>> I just updated to the latest svn version but the problem persists.
>> As I said, i'm adding
>>
>>     @Override
>>     public void touchesBegan(java.util.Set<org.xmlvm.iphone.UITouch>
>> touches, org.xmlvm.iphone.UIEvent event) {
>>         System.out.println("touch");
>>     }
>>
>> to class GLView (extends UIViewGL), but the function is never called.
>> I'm using eclipse and trying it in the xmlvm java iphone emulator.
>> Am I missing something? Is the click/touch working in the xmlvm emulator?
>>
>> Thanks!
>>
>>
>>
>> Problem found!
>>
>> A patch is ready, but since right now there is a long discussion with some
>> Android optimizations, you have to wait a bit :)
>>
>>
>>
>> ------------------------------------------------------------------------------
>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>> lucky parental unit.  See the prize list and enter to win:
>> http://p.sf.net/sfu/thinkgeek-promo
>> _______________________________________________
>> xmlvm-users mailing list
>> xml...@li...
>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>
>>
>

[xmlvm-users] Help! I am sure I am missing something here.

[Shekar M. <sh...@fa...>]

Hi,

As noted in my previous email to this group, I am trying to convert a 
Blackberry Java application (without any references to any packages 
other than java.*) into Objective-C for the iPhone using xmlvm. I am 
able to generate the Obj-C code but references to the following Java 
classes are not getting resolved properly:

java.util.Hashtable
java.util.TimeZone
java.util.Date
java.util.Calendar

In other words, I am unable to compile the generated Obj-C code because 
the XCode cannot find java_util_Hashtable.h, java_util_TimeZone.h, etc.

I wonder if some one can help with the resolution of the above problem. 
I have references in my Java code to other classes in the java.** 
hierarchy which are getting resolved. I am willing to implement these 
classes in Obj-C but I need some pointers on how to modify my xmlvm 
installation to incorporate these modules.

Thanks,
Shekar

[xmlvm-users] Question about java.util.Hashtable.

[Shekar M. <sh...@fa...>]

Hi,

I am trying to convert a Blackberry application into Objective-C (for 
the iPhone). I see that xmlvm converts many of the core java class files 
(e.g., java.util.Vector, etc.). But, I did not see a conversion of 
java.util.Hashtable -- I see that many of the Java 2 collection 
framework classes are supported. I implemented an Objective-C version of 
java.util.Hashtable and java.util.Enumeration -- how can I include this 
in the xmlvm framework so it will be generated automatically every time 
I run xmlvm?

Thanks for your reply.

Regards,
Shekar

Re: [xmlvm-users] iOS 4 & Xcode

[Panayotis K. <pan...@pa...>]

The patch is ready!
And more importantly, I managed to work on the current Xcode file  
(with some modifications), without the need to create a separate Xcode  
project!

With the new patch, the user will be able to select if he wants to  
create a project for iphone, ipad, or both (or use a legacy iphone 3.1  
project).

:D

The problem with the API remains, but I have just implemented the  
class UIDevice, which actually provide information with the running  
ios version!

Re: [xmlvm-users] Problem getting touches

[Damian <dam...@gm...>]

Ok, I'll wait for the fix. Please, tell me when it´s ready.
Thanks!

On Thu, Jun 24, 2010 at 10:48 AM, Panayotis Katsaloulis <
pan...@pa...> wrote:

>
> On 24 Ιουν 2010, at 12:27 ΠΜ, Damian wrote:
>
> I just updated to the latest svn version but the problem persists.
> As I said, i'm adding
>
>     @Override
>     public void touchesBegan(java.util.Set<org.xmlvm.iphone.UITouch>
> touches, org.xmlvm.iphone.UIEvent event) {
>         System.out.println("touch");
>     }
>
> to class GLView (extends UIViewGL), but the function is never called.
> I'm using eclipse and trying it in the xmlvm java iphone emulator.
> Am I missing something? Is the click/touch working in the xmlvm emulator?
>
> Thanks!
>
>
>
> Problem found!
>
> A patch is ready, but since right now there is a long discussion with some
> Android optimizations, you have to wait a bit :)
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>

[xmlvm-users] GLView classes

[Panayotis K. <pan...@pa...>]

Hello!

In the compatibility library there is the org_xmlvm_iphone_gl_GLView  
convenient class:

src/xmlvm2objc/compat-lib/objc/org_xmlvm_iphone_gl_GLView.h
src/xmlvm2objc/compat-lib/objc/org_xmlvm_iphone_gl_GLView.m

This class actually provides some methods to make GL programming for  
OpenGL easier, but it is not referenced by Java or needed (since the  
GL demo is written in Java :P )
I believe these files should be removed.
What do you think?

Re: [xmlvm-users] Problem getting touches

[Panayotis K. <pan...@pa...>]

On 24 Ιουν 2010, at 12:27 ΠΜ, Damian wrote:

> I just updated to the latest svn version but the problem persists.
> As I said, i'm adding
>>     @Override
>>     public void  
>> touchesBegan(java.util.Set<org.xmlvm.iphone.UITouch> touches,  
>> org.xmlvm.iphone.UIEvent event) {
>>         System.out.println("touch");
>>     }
> to class GLView (extends UIViewGL), but the function is never called.
> I'm using eclipse and trying it in the xmlvm java iphone emulator.
> Am I missing something? Is the click/touch working in the xmlvm  
> emulator?
>
> Thanks!


Problem found!

A patch is ready, but since right now there is a long discussion with  
some Android optimizations, you have to wait a bit :)

Re: [xmlvm-users] iOS 4 & Xcode

[Sascha H. <sa...@gm...>]

Sounds great. :-)

On Jun 24, 2010 9:57 AM, "Panayotis Katsaloulis" <pan...@pa...>
wrote:


On 23 Ιουν 2010, at 5:09 μ.μ., Sascha Haeberling wrote:

> As iOS 4 is definitely the way forward I...
So, to conclude, that is what I think I should try to do.
I should create a new template, called "ios" or something like that, which
will be a universal xcode project and have support for ios 4 for iphone and
ipad.
Also leave the old templates as is, and probably renamed it from "iphone" to
"iphone3"
And work with the new templates from now on.

Hopefully I will find a clever way not to re-implement the wheel when
creating the xcode projects :)



------------------------------------------------------------------------------
ThinkGeek and WIRED...

Re: [xmlvm-users] iOS 4 & Xcode

[Panayotis K. <pan...@pa...>]

On 23 Ιουν 2010, at 5:09 μ.μ., Sascha Haeberling wrote:

> As iOS 4 is definitely the way forward I think it's fair to introduce a legacy-flag that will just use the current iOS 3 templates and have the default be iOS4. The old templates would not get that much attention anymore and I would call them unmaintained, unless somebody has a good reason and fixes it himself.
> 
> Otherwise just continue working from the iOS4 templates.
> 
> This seems like the most reasonable solution. 


So, to conclude, that is what I think I should try to do.
I should create a new template, called "ios" or something like that, which will be a universal xcode project and have support for ios 4 for iphone and ipad.
Also leave the old templates as is, and probably renamed it from "iphone" to "iphone3" 
And work with the new templates from now on.

Hopefully I will find a clever way not to re-implement the wheel when creating the xcode projects :)

Re: [xmlvm-users] Problem getting touches

[Damian <dam...@gm...>]

I just updated to the latest svn version but the problem persists.
As I said, i'm adding

    @Override
    public void touchesBegan(java.util.Set<org.xmlvm.iphone.UITouch>
touches, org.xmlvm.iphone.UIEvent event) {
        System.out.println("touch");
    }

to class GLView (extends UIViewGL), but the function is never called.
I'm using eclipse and trying it in the xmlvm java iphone emulator.
Am I missing something? Is the click/touch working in the xmlvm emulator?

Thanks!

On Wed, Jun 23, 2010 at 3:08 AM, Panayotis Katsaloulis <
pan...@pa...> wrote:

>
> On Jun 23, 2010, at 1:49 AM, Damian wrote:
>
> I'm using the iphone emulator and trying to capture touches and it seems
> that there's something I'm doing wrong because It's just not working.
>
> I'm building the Opengl demo and everything works fine, but when I add the
> following lines
>
>     @Override
>     public void touchesBegan(java.util.Set<org.xmlvm.iphone.UITouch>
> touches, org.xmlvm.iphone.UIEvent event) {
>         System.out.println("touch");
>     }
>
> to class GLView (extends UIViewGL) the function is never executed.
> Any idea?
>
>
> Since there was a recent update to this method, did you try the latest SVN
> version of XMLVM?
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>

Re: [xmlvm-users] iOS 4 and new API

[Sascha H. <sa...@xm...>]

On Wed, Jun 23, 2010 at 12:11 PM, Panayotis Katsaloulis <
pan...@pa...> wrote:
>
>
> So, your opinion is XMLVM to be updated to the latest API, in any
> case, and let the programmer deal with multiple versions.
> That's the quickest (and easiest?) solution :)
> I am thinking though if there is a safer way to do it.
> I am completely ignorant at this point, but is there any java compiler
> option to check if the code is older than a specified version?
> How this problem is dealt with java libraries?


What you describe is exactly what is happening in Android. You might want to
use a new feature that is unavailable for older devices, but you might be
able to run the program with an older API or without the feature.

In these case it's recommended use reflection. So you check at runtime, if a
certain class or method is present. You then provide a reasonable fallback
for devices running an older version.

// Sascha

Re: [xmlvm-users] iOS 4 & Xcode

[Sascha H. <sa...@xm...>]

>
>
> I am afraid to produce 2 more XCode templates!
> RIght now we have already 2 templates. If we add support for iOS4 then
> these templates will be 4!
>
> Except if I leave iOS3 project templates as is, create proper
> templates for iOS4, and work with these templates from now on.
> But if an issue appears with the legacy templates, I found it a lot of
> work to maintain the same thing four-times :)


As iOS 4 is definitely the way forward I think it's fair to introduce a
legacy-flag that will just use the current iOS 3 templates and have the
default be iOS4. The old templates would not get that much attention anymore
and I would call them unmaintained, unless somebody has a good reason and
fixes it himself.

Otherwise just continue working from the iOS4 templates.

This seems like the most reasonable solution.

Re: [xmlvm-users] iOS 4 & Xcode

[Panayotis K. <pan...@pa...>]

On 23 Ιουν 2010, at 12:30 ΜΜ, Arno Puder wrote:

>
> correct me if I'm wrong, but it sounds like we can do a command line
> option for now and deal with this difference. Those developers who  
> still
> want to target 3.* (and therefore should not update to the iOS4 SDK)  
> can
> still use XMLVM.

I am afraid to produce 2 more XCode templates!
RIght now we have already 2 templates. If we add support for iOS4 then  
these templates will be 4!

Except if I leave iOS3 project templates as is, create proper  
templates for iOS4, and work with these templates from now on.
But if an issue appears with the legacy templates, I found it a lot of  
work to maintain the same thing four-times :)

Re: [xmlvm-users] iOS 4 and new API

[Panayotis K. <pan...@pa...>]

On 23 Ιουν 2010, at 12:42 ΜΜ, Arno Puder wrote:

>
> Apple advocates universal binaries that can be deployed on all their
> devices and recommends to use runtime checks to see if certain
> capabilities are present on the current device:
> http://developer.apple.com/iphone/library/documentation/General/Conceptual/iPadProgrammingGuide/StartingYourProject/StartingYourProject.html
>
> Check section called "Adding Runtime Checks for Newer Symbols".
>
> Well, we can mimic just the same in the Java API.
> Class.forName("UISplitViewController") will return null if not  
> executed
> on an iPad.

So, your opinion is XMLVM to be updated to the latest API, in any  
case, and let the programmer deal with multiple versions.
That's the quickest (and easiest?) solution :)
I am thinking though if there is a safer way to do it.
I am completely ignorant at this point, but is there any java compiler  
option to check if the code is older than a specified version?
How this problem is dealt with java libraries?


> Anyways, another issue I wanted to raise: there is more and more API
> being added and it incurs a lot of work to include Java versions for
> XMLVM because the wrappers are manually written. I think we should  
> take
> a more serious look at projects such as
> http://code.google.com/p/jnaerator/ and consider to generate the
> wrappers automatically.

For general wrappers, it is not bad.
Still there are a lot of methods that need to be tweaked by hand :)

Re: [xmlvm-users] iOS 4 & Xcode

[Sascha H. <sa...@xm...>]

Actually Arno just answered my question on another thread, so never mind! :)

On Wed, Jun 23, 2010 at 11:45 AM, Sascha Haeberling <sa...@xm...>wrote:

> I don't know how it works for the iPhone, but at least for Android you can
> develop an app that makes use of features of newer APIs while still
> supporting old phones. So at least this is not an issue, unless your app
> heavily depends on some new feature.
>
> // Sascha
>
>
> On Wed, Jun 23, 2010 at 11:27 AM, Dr. Alexander K. Seewald <
> al...@se...> wrote:
>
>> Concerning which devices are in the market... I don't know this for
>> iPhone, but Android has a nice current overview at
>> http://developer.android.com/resources/dashboard/platform-versions.html
>>
>> It used to be 1:1:1 for 1.5, 1.6 and 2.1 a few months ago, but now
>> it is 1:1:2. So taking away support for 1.5 would correspond to a
>> reduction in market share of about 25%. That said, the first
>> version of devices did not always have useful update paths (e.g.
>> the Samsung i7500 cannot be updated...) and are significantly
>> different in hardware capabilities (e.g. far less control in camera
>> interface), so there would be some rationale in removing them.
>>
>> Does anyone has any numbers? Which proportion of the iPhones
>> currently out there are not updateable to iOS 4?
>>
>> Best,
>>  Alex
>> --
>> Dr. Alexander K. Seewald
>>
>> Seewald Solutions
>> www.seewald.at
>> Tel. +43(664)1106886
>> Fax. +43(1)2533033/2764
>>
>>
>> ------------------------------------------------------------------------------
>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>> lucky parental unit.  See the prize list and enter to win:
>> http://p.sf.net/sfu/thinkgeek-promo
>> _______________________________________________
>> xmlvm-users mailing list
>> xml...@li...
>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>
>
>

Re: [xmlvm-users] iOS 4 & Xcode

[Sascha H. <sa...@xm...>]

I don't know how it works for the iPhone, but at least for Android you can
develop an app that makes use of features of newer APIs while still
supporting old phones. So at least this is not an issue, unless your app
heavily depends on some new feature.

// Sascha

On Wed, Jun 23, 2010 at 11:27 AM, Dr. Alexander K. Seewald
<al...@se...>wrote:

> Concerning which devices are in the market... I don't know this for
> iPhone, but Android has a nice current overview at
> http://developer.android.com/resources/dashboard/platform-versions.html
>
> It used to be 1:1:1 for 1.5, 1.6 and 2.1 a few months ago, but now
> it is 1:1:2. So taking away support for 1.5 would correspond to a
> reduction in market share of about 25%. That said, the first
> version of devices did not always have useful update paths (e.g.
> the Samsung i7500 cannot be updated...) and are significantly
> different in hardware capabilities (e.g. far less control in camera
> interface), so there would be some rationale in removing them.
>
> Does anyone has any numbers? Which proportion of the iPhones
> currently out there are not updateable to iOS 4?
>
> Best,
>  Alex
> --
> Dr. Alexander K. Seewald
>
> Seewald Solutions
> www.seewald.at
> Tel. +43(664)1106886
> Fax. +43(1)2533033/2764
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] iOS 4 and new API

[Arno P. <ar...@pu...>]

Apple advocates universal binaries that can be deployed on all their 
devices and recommends to use runtime checks to see if certain 
capabilities are present on the current device:
http://developer.apple.com/iphone/library/documentation/General/Conceptual/iPadProgrammingGuide/StartingYourProject/StartingYourProject.html

Check section called "Adding Runtime Checks for Newer Symbols".

Well, we can mimic just the same in the Java API. 
Class.forName("UISplitViewController") will return null if not executed 
on an iPad.

Anyways, another issue I wanted to raise: there is more and more API 
being added and it incurs a lot of work to include Java versions for 
XMLVM because the wrappers are manually written. I think we should take 
a more serious look at projects such as 
http://code.google.com/p/jnaerator/ and consider to generate the 
wrappers automatically.

Comments?

Arno


On 6/23/10 11:22 AM, Panayotis Katsaloulis wrote:
> I create a new email, since this is a completely different problem.
>
> What do you think should do with new API's in iOS4?
> How to make safe that someone compiling with 3.1, won't use this new API's, so break the obj-c code?
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] iOS 4 & Xcode

[Sascha H. <sa...@xm...>]

I agree. Seems like this shouldn't be a big deal, if the API hasn't changed
much. Of course there is a lot of new API, but the old one is probably
mostly untouched, right?

On Wed, Jun 23, 2010 at 11:30 AM, Arno Puder <ar...@pu...> wrote:

>
> correct me if I'm wrong, but it sounds like we can do a command line
> option for now and deal with this difference. Those developers who still
> want to target 3.* (and therefore should not update to the iOS4 SDK) can
> still use XMLVM.
>
> Arno
>
>
> On 6/23/10 11:21 AM, Panayotis Katsaloulis wrote:
> >
> > On Jun 23, 2010, at 11:15 AM, Arno Puder wrote:
> >
> >> does this mean you have to change the way Xcode projects are generated
> >> by XMLVM for iOS4 and that change would not be backward compatible with
> >> iOS 3.1 and 3.2?
> >
> > Yes, unfortunately.
> >
> >
> > On Jun 23, 2010, at 11:16 AM, Sascha Haeberling wrote:
> >
> >> what are the things that need to change right now to write apps with
> XMLVM for iOS? Did the existing APIs change dramatically? I guess the XCode
> project creator need to be adapted? If it's just the latter, I would propose
> to introduce a legacy argument that uses the current XCode code creation and
> have the current one create new XCode projects.
> >
> > The API has changed, but not so drastically.
> > What is actually happened is that the current version of the SDK has
> support ONLY for the 4.0 version of iOS, while the old (and vanished)
> versions of the SDK have of course support ONLY for version prior of 4.0 :)
> > Clever, eh?
> >
> > The Xproject creator of course needs to be updated.
> >
> > If a project is created for iOS4, then the project (not the java code)
> could not be compatible with the older versions.
> > With older SDK's of course it is not able to be loaded.
> >
> > If a project is created for version 3.1 (the latest fully supported
> version), then this project is not compatible with current iOS SDK (but it
> *is* binary compatible with older versions).
> > With the current SDK,  the user should make a couple of not obvious
> changes to the project in order to able to compile&  publish it.
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > ThinkGeek and WIRED's GeekDad team up for the Ultimate
> > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> > lucky parental unit.  See the prize list and enter to win:
> > http://p.sf.net/sfu/thinkgeek-promo
> > _______________________________________________
> > xmlvm-users mailing list
> > xml...@li...
> > https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] iOS 4 & Xcode

[Arno P. <ar...@pu...>]

correct me if I'm wrong, but it sounds like we can do a command line 
option for now and deal with this difference. Those developers who still 
want to target 3.* (and therefore should not update to the iOS4 SDK) can 
still use XMLVM.

Arno


On 6/23/10 11:21 AM, Panayotis Katsaloulis wrote:
>
> On Jun 23, 2010, at 11:15 AM, Arno Puder wrote:
>
>> does this mean you have to change the way Xcode projects are generated
>> by XMLVM for iOS4 and that change would not be backward compatible with
>> iOS 3.1 and 3.2?
>
> Yes, unfortunately.
>
>
> On Jun 23, 2010, at 11:16 AM, Sascha Haeberling wrote:
>
>> what are the things that need to change right now to write apps with XMLVM for iOS? Did the existing APIs change dramatically? I guess the XCode project creator need to be adapted? If it's just the latter, I would propose to introduce a legacy argument that uses the current XCode code creation and have the current one create new XCode projects.
>
> The API has changed, but not so drastically.
> What is actually happened is that the current version of the SDK has support ONLY for the 4.0 version of iOS, while the old (and vanished) versions of the SDK have of course support ONLY for version prior of 4.0 :)
> Clever, eh?
>
> The Xproject creator of course needs to be updated.
>
> If a project is created for iOS4, then the project (not the java code) could not be compatible with the older versions.
> With older SDK's of course it is not able to be loaded.
>
> If a project is created for version 3.1 (the latest fully supported version), then this project is not compatible with current iOS SDK (but it *is* binary compatible with older versions).
> With the current SDK,  the user should make a couple of not obvious changes to the project in order to able to compile&  publish it.
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

[xmlvm-users] iOS 4 & Xcode

[Dr. A. K. S. <al...@se...>]

Concerning which devices are in the market... I don't know this for
iPhone, but Android has a nice current overview at
http://developer.android.com/resources/dashboard/platform-versions.html

It used to be 1:1:1 for 1.5, 1.6 and 2.1 a few months ago, but now
it is 1:1:2. So taking away support for 1.5 would correspond to a
reduction in market share of about 25%. That said, the first
version of devices did not always have useful update paths (e.g.
the Samsung i7500 cannot be updated...) and are significantly
different in hardware capabilities (e.g. far less control in camera
interface), so there would be some rationale in removing them.

Does anyone has any numbers? Which proportion of the iPhones
currently out there are not updateable to iOS 4?

Best,
  Alex
-- 
Dr. Alexander K. Seewald

Seewald Solutions
www.seewald.at
Tel. +43(664)1106886
Fax. +43(1)2533033/2764

[xmlvm-users] iOS 4 and new API

[Panayotis K. <pan...@pa...>]

I create a new email, since this is a completely different problem.

What do you think should do with new API's in iOS4?
How to make safe that someone compiling with 3.1, won't use this new API's, so break the obj-c code?

Re: [xmlvm-users] iOS 4 & Xcode

[Panayotis K. <pan...@pa...>]

On Jun 23, 2010, at 11:15 AM, Arno Puder wrote:

> does this mean you have to change the way Xcode projects are generated 
> by XMLVM for iOS4 and that change would not be backward compatible with 
> iOS 3.1 and 3.2?

Yes, unfortunately.


On Jun 23, 2010, at 11:16 AM, Sascha Haeberling wrote:

> what are the things that need to change right now to write apps with XMLVM for iOS? Did the existing APIs change dramatically? I guess the XCode project creator need to be adapted? If it's just the latter, I would propose to introduce a legacy argument that uses the current XCode code creation and have the current one create new XCode projects.

The API has changed, but not so drastically.
What is actually happened is that the current version of the SDK has support ONLY for the 4.0 version of iOS, while the old (and vanished) versions of the SDK have of course support ONLY for version prior of 4.0 :)
Clever, eh?

The Xproject creator of course needs to be updated.

If a project is created for iOS4, then the project (not the java code) could not be compatible with the older versions.
With older SDK's of course it is not able to be loaded.

If a project is created for version 3.1 (the latest fully supported version), then this project is not compatible with current iOS SDK (but it *is* binary compatible with older versions).
With the current SDK,  the user should make a couple of not obvious changes to the project in order to able to compile & publish it.

Re: [xmlvm-users] iOS 4 & Xcode

[Arno P. <ar...@pu...>]

if the only difference is a new Xcode project file format, I also opt 
for a command line switch.

Arno


On 6/23/10 10:16 AM, Sascha Haeberling wrote:
> Great ...
>
> what are the things that need to change right now to write apps with
> XMLVM for iOS? Did the existing APIs change dramatically? I guess the
> XCode project creator need to be adapted? If it's just the latter, I
> would propose to introduce a legacy argument that uses the current XCode
> code creation and have the current one create new XCode projects.
>
> // Sascha
>
> On Wed, Jun 23, 2010 at 9:43 AM, Panayotis Katsaloulis
> <pan...@pa... <mailto:pan...@pa...>> wrote:
>
>     Hello all!
>
>     I have just downloaded the latest stable version of Xcode and with
>     surprise I found out that all versions of iOS prior of 3.2
>     (including 3.1) are cut off!
>
>     Which means that officially there is NO way to write applications of
>     iOS 3 any more.
>     It also means that the current produced Xcode project is no longer
>     valid.
>
>     What should we do?
>     Go on with the flow and cut compatibility with 3.*?
>
>     Right now it is not possible any more to write applications with
>     xmlvm, create a project and compile/send this project for the iphone.
>     ------------------------------------------------------------------------------
>     ThinkGeek and WIRED's GeekDad team up for the Ultimate
>     GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>     lucky parental unit.  See the prize list and enter to win:
>     http://p.sf.net/sfu/thinkgeek-promo
>     _______________________________________________
>     xmlvm-users mailing list
>     xml...@li...
>     <mailto:xml...@li...>
>     https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] iOS 4 & Xcode

[Arno P. <ar...@pu...>]

well, I don't like the fact that Apple has a tendency to remove 
developer's choice. Its as if like Google removed support for Android 
1.5 in their SDK. There are still more devices out there than you might 
think (also 1st gen iPods) and perhaps a developer does not need all the 
new fancy API of iOS 4 for the application he/she has in mind.

But lets not start a big discussion. Apple creates facts and all we can 
do is react to it.

Arno


On 6/23/10 10:20 AM, Sascha Haeberling wrote:
> What timing! :)
>
> On Wed, Jun 23, 2010 at 10:15 AM, Arno Puder <ar...@pu...
> <mailto:ar...@pu...>> wrote:
>
>
>     does this mean you have to change the way Xcode projects are generated
>     by XMLVM for iOS4 and that change would not be backward compatible with
>     iOS 3.1 and 3.2?
>
>     Also interesting to note that Apple effectively renders all 'old'
>     iPhone/iPod Touches more or less useless because you cannot update them
>     to iOS4. Well, I would expect nothing less from Apple.
>
>
> Well, I don't like Apple either, but that I find is unfair bashing. I
> think it's fine to make older platforms obsolete when limits are
> reached. The hardware is slower than today's, and if new features
> require more power then I think this is a fair step to take. Correct me,
> if I am wrong, but I think this is just affecting 1st gen devices,
> right? They are around for quite a while now.
>
>
>     Arno
>
>
>     On 6/23/10 9:43 AM, Panayotis Katsaloulis wrote:
>      > Hello all!
>      >
>      > I have just downloaded the latest stable version of Xcode and
>     with surprise I found out that all versions of iOS prior of 3.2
>     (including 3.1) are cut off!
>      >
>      > Which means that officially there is NO way to write applications
>     of iOS 3 any more.
>      > It also means that the current produced Xcode project is no
>     longer valid.
>      >
>      > What should we do?
>      > Go on with the flow and cut compatibility with 3.*?
>      >
>      > Right now it is not possible any more to write applications with
>     xmlvm, create a project and compile/send this project for the iphone.
>      >
>     ------------------------------------------------------------------------------
>      > ThinkGeek and WIRED's GeekDad team up for the Ultimate
>      > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>      > lucky parental unit.  See the prize list and enter to win:
>      > http://p.sf.net/sfu/thinkgeek-promo
>      > _______________________________________________
>      > xmlvm-users mailing list
>      > xml...@li...
>     <mailto:xml...@li...>
>      > https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>     ------------------------------------------------------------------------------
>     ThinkGeek and WIRED's GeekDad team up for the Ultimate
>     GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>     lucky parental unit.  See the prize list and enter to win:
>     http://p.sf.net/sfu/thinkgeek-promo
>     _______________________________________________
>     xmlvm-users mailing list
>     xml...@li...
>     <mailto:xml...@li...>
>     https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>