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

Re: [xmlvm-users] Access to "raw" resources

[Wolfgang K. <wol...@xm...>]

Alex,

One thing I noticed in your layout file: You make use of String  
resources. Unfortunately we currently do not support String resources.

-- Wolfgang

Sent from my iPhone

On 15.12.2009, at 14:03, "Dr. Alexander K. Seewald" <al...@se...>  
wrote:

> There is something very strange going on. I get a major error when
> initializing a FileInputStream with any resource path (i.e. path
> obtained by ...
>  String fileName = getFileNamePath(findResourceNameById(resourceId));
>    String filePath = NSBundle.mainBundle().pathForResource 
> (fileName,"xml");
> - I've tested with activity.xml = my layout file and one raw
>  resource)
> and then instantiating a new FileInputStream object.
>
> FileInputStream fis = new FileInputStream(filePath);
>
> If filePath does not exist, it gives a FileNotFound exception. If it
> does exist (e.g. the activity.xml is obviously read during startup),
> there is a major crash of the whole MacOS - not only the iPhone
> emulator.
>
> I've noted that my icon is not shown as well, so perhaps there is a
> problem with resources in general. However, my layout xml is pretty
> basic:
>
> <?xml version="1.0" encoding="utf-8"?>
> <LinearLayout
> xmlns:android="http://schemas.android.com/apk/res/android"
>  android:layout_width="fill_parent"
> android:layout_height="fill_parent"
>  android:orientation="vertical">
>
>  <TextView android:id="@+id/result"
>    android:layout_width="wrap_content"
> android:layout_height="wrap_content">
>  </TextView>
>
>  <Button android:id="@+id/livetest"
>    android:layout_width="wrap_content"
> android:layout_height="wrap_content"
>    android:text="@string/livetest"
>> </Button>
>
>  <Button android:id="@+id/back"
>    android:layout_width="wrap_content"
> android:layout_height="wrap_content"
>    android:text="@string/back"
>> </Button>
>
>  <Button android:id="@+id/validate"
>    android:layout_width="wrap_content"
> android:layout_height="wrap_content"
>    android:text="@string/validate"
>    android:enabled="true"
>> </Button>
> </LinearLayout>
>
> ... as well as the AndroidManifest.xml:
>
> <?xml version="1.0" encoding="utf-8"?>
> <manifest xmlns:android="http://schemas.android.com/apk/res/android"
>    package="com.SeewaldSolutions.DanceMusicRecognizer"
>    android:versionCode="1"
>    android:versionName="1.0">
>    <uses-sdk android:minSdkVersion="3" />
>    <uses-permission
> android:name="android.permission.RECORD_AUDIO"></uses-permission>
>    <uses-permission
> android:name="android.permission.INTERNET"></uses-permission>
>    <application android:label="@string/dancing_guide_app"
>      android:icon="@drawable/launcher">
>        <activity android:name="DanceMusicRecognizerActivity"
>          android:icon="@drawable/launcher"
>          android:configChanges="orientation">
>            <intent-filter>
>                <action android:name="android.intent.action.MAIN" />
>                <category
> android:name="android.intent.category.LAUNCHER" />
>            </intent-filter>
>        </activity>
>    </application>
> </manifest>
>
>
> I compile using ...
> javac
> android_src/src/com/SeewaldSolutions/DanceMusicRecognizer/*.java
> android_src/gen/com/SeewaldSolutions/DanceMusicRecognizer/R.java -d
> android_src_build -cp
> xmlvm/dist/lib/objc-compat.jar:xmlvm/dist/lib/android-compat.jar
>
> ... and use xmlvm like this ...
>
> java -jar xmlvm/dist/xmlvm.jar --in=android_src_build
> --out=DanceMusicRecognizer --target=android-on-iphone
> --iphone-app=DanceMusicRecognizer --resource=android_src/res/layout
> --resource=android_src/res/raw --resource=android_src/res/drawable
> --resource=android_src/AndroidManifest.xml
>
> activity.xml (from layout directory) and the icons are copied to the
> resource directory in target, but I still get @string/back and so on
> as button text. I always got a crash when trying to access images as
> well, and the icon does not work. Is there anything I am doing
> wrong?
>
> Best,
>  Alex
> -- 
> Dr. Alexander K. Seewald
>
> Seewald Solutions
> www.seewald.at
> Tel. +43(664)1106886
> Fax. +43(1)2533033/2764
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] Access to "raw" resources

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

Alex,

I have these kind of problems all the time (although I never managed to 
crash my whole machine). The first step in finding the problem is to 
identify the precise location where the program crashes. The best way to 
do this is by setting breakpoints and to single step with Xcode. 
Tedious, but if you don't know where the program crashes it is virtually 
impossible to find out what is going on.

Since your whole machine crashes, you might want to run and debug your 
program on the device. At least you don't have to reboot your Mac all 
the time.  :)

Arno


On 12/15/09 2:03 PM, Dr. Alexander K. Seewald wrote:
> There is something very strange going on. I get a major error when
> initializing a FileInputStream with any resource path (i.e. path
> obtained by ...
>    String fileName = getFileNamePath(findResourceNameById(resourceId));
> 	String filePath = NSBundle.mainBundle().pathForResource(fileName,"xml");
> - I've tested with activity.xml = my layout file and one raw
>    resource)
> and then instantiating a new FileInputStream object.
>
> FileInputStream fis = new FileInputStream(filePath);
>
> If filePath does not exist, it gives a FileNotFound exception. If it
> does exist (e.g. the activity.xml is obviously read during startup),
> there is a major crash of the whole MacOS - not only the iPhone
> emulator.
>
> I've noted that my icon is not shown as well, so perhaps there is a
> problem with resources in general. However, my layout xml is pretty
> basic:
>
> <?xml version="1.0" encoding="utf-8"?>
> <LinearLayout
> xmlns:android="http://schemas.android.com/apk/res/android"
>    android:layout_width="fill_parent"
> android:layout_height="fill_parent"
>    android:orientation="vertical">
>
>    <TextView android:id="@+id/result"
>      android:layout_width="wrap_content"
> android:layout_height="wrap_content">
>    </TextView>
>
>    <Button android:id="@+id/livetest"
>      android:layout_width="wrap_content"
> android:layout_height="wrap_content"
>      android:text="@string/livetest"
>    ></Button>
>
>    <Button android:id="@+id/back"
>      android:layout_width="wrap_content"
> android:layout_height="wrap_content"
>      android:text="@string/back"
>    ></Button>
>
>    <Button android:id="@+id/validate"
>      android:layout_width="wrap_content"
> android:layout_height="wrap_content"
>      android:text="@string/validate"
>      android:enabled="true"
>    ></Button>
> </LinearLayout>
>
> ... as well as the AndroidManifest.xml:
>
> <?xml version="1.0" encoding="utf-8"?>
> <manifest xmlns:android="http://schemas.android.com/apk/res/android"
>      package="com.SeewaldSolutions.DanceMusicRecognizer"
>      android:versionCode="1"
>      android:versionName="1.0">
>      <uses-sdk android:minSdkVersion="3" />
>      <uses-permission
> android:name="android.permission.RECORD_AUDIO"></uses-permission>
>      <uses-permission
> android:name="android.permission.INTERNET"></uses-permission>
>      <application android:label="@string/dancing_guide_app"
>        android:icon="@drawable/launcher">
>          <activity android:name="DanceMusicRecognizerActivity"
>            android:icon="@drawable/launcher"
>            android:configChanges="orientation">
>              <intent-filter>
>                  <action android:name="android.intent.action.MAIN" />
>                  <category
> android:name="android.intent.category.LAUNCHER" />
>              </intent-filter>
>          </activity>
>      </application>
> </manifest>
>
>
> I compile using ...
> javac
> android_src/src/com/SeewaldSolutions/DanceMusicRecognizer/*.java
> android_src/gen/com/SeewaldSolutions/DanceMusicRecognizer/R.java -d
> android_src_build -cp
> xmlvm/dist/lib/objc-compat.jar:xmlvm/dist/lib/android-compat.jar
>
> ... and use xmlvm like this ...
>
> java -jar xmlvm/dist/xmlvm.jar --in=android_src_build
> --out=DanceMusicRecognizer --target=android-on-iphone
> --iphone-app=DanceMusicRecognizer --resource=android_src/res/layout
> --resource=android_src/res/raw --resource=android_src/res/drawable
> --resource=android_src/AndroidManifest.xml
>
> activity.xml (from layout directory) and the icons are copied to the
> resource directory in target, but I still get @string/back and so on
> as button text. I always got a crash when trying to access images as
> well, and the icon does not work. Is there anything I am doing
> wrong?
>
> Best,
>    Alex

Re: [xmlvm-users] Access to "raw" resources

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

There is something very strange going on. I get a major error when
initializing a FileInputStream with any resource path (i.e. path
obtained by ...
  String fileName = getFileNamePath(findResourceNameById(resourceId));
	String filePath = NSBundle.mainBundle().pathForResource(fileName,"xml");
- I've tested with activity.xml = my layout file and one raw
  resource)
and then instantiating a new FileInputStream object.

FileInputStream fis = new FileInputStream(filePath);

If filePath does not exist, it gives a FileNotFound exception. If it
does exist (e.g. the activity.xml is obviously read during startup),
there is a major crash of the whole MacOS - not only the iPhone
emulator.

I've noted that my icon is not shown as well, so perhaps there is a
problem with resources in general. However, my layout xml is pretty
basic:

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout
xmlns:android="http://schemas.android.com/apk/res/android"
  android:layout_width="fill_parent"
android:layout_height="fill_parent"
  android:orientation="vertical">

  <TextView android:id="@+id/result"
    android:layout_width="wrap_content"
android:layout_height="wrap_content">
  </TextView>

  <Button android:id="@+id/livetest"
    android:layout_width="wrap_content"
android:layout_height="wrap_content"
    android:text="@string/livetest"
  ></Button>

  <Button android:id="@+id/back"
    android:layout_width="wrap_content"
android:layout_height="wrap_content"
    android:text="@string/back"
  ></Button>

  <Button android:id="@+id/validate"
    android:layout_width="wrap_content"
android:layout_height="wrap_content"
    android:text="@string/validate"
    android:enabled="true"
  ></Button>
</LinearLayout>

... as well as the AndroidManifest.xml:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.SeewaldSolutions.DanceMusicRecognizer"
    android:versionCode="1"
    android:versionName="1.0">
    <uses-sdk android:minSdkVersion="3" />
    <uses-permission
android:name="android.permission.RECORD_AUDIO"></uses-permission>
    <uses-permission
android:name="android.permission.INTERNET"></uses-permission>
    <application android:label="@string/dancing_guide_app"
      android:icon="@drawable/launcher">
        <activity android:name="DanceMusicRecognizerActivity"
          android:icon="@drawable/launcher"
          android:configChanges="orientation">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category
android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
    </application>
</manifest>


I compile using ...
javac
android_src/src/com/SeewaldSolutions/DanceMusicRecognizer/*.java
android_src/gen/com/SeewaldSolutions/DanceMusicRecognizer/R.java -d
android_src_build -cp
xmlvm/dist/lib/objc-compat.jar:xmlvm/dist/lib/android-compat.jar

... and use xmlvm like this ...

java -jar xmlvm/dist/xmlvm.jar --in=android_src_build
--out=DanceMusicRecognizer --target=android-on-iphone
--iphone-app=DanceMusicRecognizer --resource=android_src/res/layout
--resource=android_src/res/raw --resource=android_src/res/drawable
--resource=android_src/AndroidManifest.xml

activity.xml (from layout directory) and the icons are copied to the
resource directory in target, but I still get @string/back and so on
as button text. I always got a crash when trying to access images as
well, and the icon does not work. Is there anything I am doing
wrong?

Best,
  Alex
-- 
Dr. Alexander K. Seewald

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

Re: [xmlvm-users] converting hello world android to iphone app

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

the ant-script that comes with XMLVM will automatically build all demos. 
After you run 'ant' take a look at the 'dist/demo' directory. Please 
check the build.xml to see how the demos were built.

I need to update the documentation. Things have gotten quite a bit 
easier. I'll try to do that soon.

Arno


On 12/13/09 9:50 PM, ahmet timuçin wrote:
> Hello,
>
> I tried xmlvm on the very basic "hello world" android application to see
> if it works. But it gives this error:
>
> [12/13/09 22:44:47.172]  WARNING: Unable to create InputProcesses for
> input: /HelloAndroid
>
> Is there anyone to help?
>
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

[xmlvm-users] converting hello world android to iphone app

[ahmet t. <ahm...@gm...>]

Hello,

I tried xmlvm on the very basic "hello world" android application to see if
it works. But it gives this error:

[12/13/09 22:44:47.172]  WARNING: Unable to create InputProcesses for input:
/HelloAndroid

Is there anyone to help?

Re: [xmlvm-users] Making java_lang_String immutable

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

looks like a clever way of solving a few issues that we have in our 
current version of our libraries. I assume that the category for 
java.lang.String is added to NSString, right?

Please make sure that our own demos work with your changes (in 
particular Xokoban).

Arno


On 12/13/09 5:57 PM, Gergely Kis wrote:
> Hi,
>
> Currently in XMLVM trunk, the java_lang_String is defined as a typedef
> for NSMutableString + a category. This has the side effect, that @"Const
> string" is not recognized as java_lang_String, also you need to repack
> any NString object you get from Cocoa methods before you can pass it to
> cross compiled code.
>
> This is certainly suboptimal.
>
> In our branch, I changed the definiton of java_lang_String to be a
> typedef of NSString. Of course, the problem is that we need a mutable
> string in order to call the different java string constructors.
>
> So I used the following trick:
> 1. Added a separate alloc method for java_lang_String
> + (id) __alloc_java_lang_String
> {
>      return [NSMutableString alloc];
> }
>
> 2. Changed the XSL to use this method instead of the regular alloc, when
> it needs to instantiate a java_lang_String object.
>
> 3. In the Java constructors, like
> __init_java_lang_String_byte_ARRAYTYPE, I call the setString like this:
> [(NSMutableString*)self setString: s];
>
> I plan to also submit this back for inclusion. What do you think? Are
> there any hidden issues that I did not consider?
>
> Best Regards,
> Gergely
>
> --
> Kis Gergely
> MattaKis Consulting
> Email: ger...@ma... <mailto:ger...@ma...>
> Web: http://www.mattakis.com
> Phone: +36 70 408 1723
>
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

[xmlvm-users] Converting Android application to Iphone

[ahmet t. <ahm...@gm...>]

Hello,

I am in need of help.

I am trying to convert an Android Sudoku application to Iphone but cant
manage. I read the manual in detail. I built the xmlvm and now have an
xmlvm.jar. It says that only xmlvm.jar is enough to use the tool.

So I copied xmlvm.jar to a directory named "example". Inside example there
is my android application source codes.

../example
   xmlvm.jar
   Sudoku

Sudoku is directly copied from Eclipse workspace.
Now as far as I see, I should call this command:

>java -jar xmlvm.jar --in=/Sudoku --target=android-on-iphone
--iphone-app=Sudoku
>

It seems like a successfull run, but when I look at the directory again:

It creates an empty src/lib/anroid directory, a
Sudoku.xcodeproj/project.pbxproj
file and a Makefile.

It doesnt produce anything other than these.
What am I missing? It is a simple game like your Xokoban. I don think that
there can be any compatibility issues.

thanks.

Re: [xmlvm-users] Memory management and returned objects

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

what you propose is functionally identical to what is happening in XMLVM 
right now. We had to add the returned reference to an autorelease pool 
because we don't know if the caller consumes the reference or not. In 
Java, you can just simply ignore the result.

In XMLVM, we have the following memory management rules:

- the caller owns input arguments. If the callee needs to save
   the reference, it has to do a retain.
- the caller takes over ownership of the return argument.

When you write within the callee:

return [_op1.o autorelease];

_op1.o will be added to the autorelease pool of the caller. I guess 
because of this asymmetry I decided back then to let the caller decide 
what it wants to do. When the caller knows that it doesn't need the 
reference, the caller can also call release instead of autorelease 
(which is a much more expensive operation). But I agree that right now 
we always add the return reference to the autorelease pool, so one might 
as well do it in the callee. But in the future we might add this 
optimization, so generally I would prefer to leave it the way it is. 
Apart from the fact that it would be a lot of work to make that change: 
all the hand-written Objective-C stubs would need to be changed accordingly.

Arno


On 12/13/09 6:14 PM, Gergely Kis wrote:
> Hi,
>
> I observed, the following pattern in the generated code (in pseudocode):
>
> _op1.o = [ref methodCall];
> [op1.o autorelease];
>
> However, the Cocoa memory management guide says, that you only need to
> release a reference, if you own it. It also says that you only own an
> object, if it was created with init, new or copy, or you have called
> retain on it.
>
> This means that in general if you call a method, you do not own the
> returned object, so you should not call autorelease on it.
> Why does this XMLVM the other way around? Is it because of the separate
> autoreleasepool for each method?
> It could generate the return sequence like this, and still follow the
> general rules of Cocoa memory management:
>
> in the returning method:
> [_op1.o retain];
> [_pool release];
> return [_op1.o autorelease];
>
> in the caller do not call autorelease.
>
> Am I missing something?
>
> Best Regards,
> Gergely
>
> --
> Kis Gergely
> MattaKis Consulting
> Email: ger...@ma... <mailto:ger...@ma...>
> Web: http://www.mattakis.com
> Phone: +36 70 408 1723
>
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

[xmlvm-users] Making java_lang_String immutable

[Gergely K. <ger...@ma...>]

Hi,

Currently in XMLVM trunk, the java_lang_String is defined as a typedef for
NSMutableString + a category. This has the side effect, that @"Const string"
is not recognized as java_lang_String, also you need to repack any NString
object you get from Cocoa methods before you can pass it to cross compiled
code.

This is certainly suboptimal.

In our branch, I changed the definiton of java_lang_String to be a typedef
of NSString. Of course, the problem is that we need a mutable string in
order to call the different java string constructors.

So I used the following trick:
1. Added a separate alloc method for java_lang_String
+ (id) __alloc_java_lang_String
{
    return [NSMutableString alloc];
}

2. Changed the XSL to use this method instead of the regular alloc, when it
needs to instantiate a java_lang_String object.

3. In the Java constructors, like __init_java_lang_String_byte_ARRAYTYPE, I
call the setString like this:
[(NSMutableString*)self setString: s];

I plan to also submit this back for inclusion. What do you think? Are there
any hidden issues that I did not consider?

Best Regards,
Gergely

-- 
Kis Gergely
MattaKis Consulting
Email: ger...@ma...
Web: http://www.mattakis.com
Phone: +36 70 408 1723

[xmlvm-users] Memory management and returned objects

[Gergely K. <ger...@ma...>]

Hi,

I observed, the following pattern in the generated code (in pseudocode):

_op1.o = [ref methodCall];
[op1.o autorelease];

However, the Cocoa memory management guide says, that you only need to
release a reference, if you own it. It also says that you only own an
object, if it was created with init, new or copy, or you have called retain
on it.

This means that in general if you call a method, you do not own the returned
object, so you should not call autorelease on it.
Why does this XMLVM the other way around? Is it because of the separate
autoreleasepool for each method?
It could generate the return sequence like this, and still follow the
general rules of Cocoa memory management:

in the returning method:
[_op1.o retain];
[_pool release];
return [_op1.o autorelease];

in the caller do not call autorelease.

Am I missing something?

Best Regards,
Gergely

-- 
Kis Gergely
MattaKis Consulting
Email: ger...@ma...
Web: http://www.mattakis.com
Phone: +36 70 408 1723

Re: [xmlvm-users] Access to "raw" resources

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

the java.io.* stuff are mostly skeletons at the moment, so no wonder it 
does not work. Although I'm surprised that your machine crashes.

Be nice to Gergely; sounds like his upcoming patch might fix your 
problems.  :-)

Arno


On 12/12/09 12:04 AM, Dr. Alexander K. Seewald wrote:
> Hi all,
>
> I was just trying to make access to raw resources possible in xmlvm,
> in my case .wav files, for the android2iphone toolchain. I thought of
> implementing openRawResource() for this:
>
> public String openRawResource(int resourceId) throws Exception {
>    String fileName = getFileNamePath(findResourceNameById(resourceId));
>    String filePath = NSBundle.mainBundle().pathForResource(fileName,"wav");
>    return new FileInputStream(filePath);
> }
>
> However, this leads to severe crashes -  in one case even bringing
> down MacOS(!) when running the app on the simulator. I've checked and
> fileName / filePath give back reasonable paths (when manually
> adding the wav files to the resources in Xcode, of course -
> otherwise it crashes on program start ;-). The moment I instantiate
> FileInputStream, I get severe crashes without any debugging info
> that I can see (in Xcode when running on the emulator)
>
> I've checked the objectiveC implementation of FileInputStream and it
> seems to look ok. I've observed this behavior for SVN rev. 690.
>
> Any ideas what could cause this?
>
> Best,
>    Alex
> P.S. Very minor issue: float and double NaN constants should read NAN in
> objC - not NaN.

Re: [xmlvm-users] Implementation of synchronized in objc

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

multiple monitorexit for one monitorenter is certainly a problem and I 
think your approach is a viable solution. Make sure that your 
implementation of lock and unlock are thread safe.

Looking forward to your patch!

Arno


On 12/12/09 1:02 AM, Gergely Kis wrote:
> Hi,
>
> I observed a problem with the way synchronized (or more accurately
> monitorenter and monitorexit) were implemented.
> The use of the @synchronized statement is problematic, because javac
> likes to emit multiple monitorexit's in try / catch branches for a
> single monitorenter in many different cases.
>
> So I took the following approach:
> - added an xmlvmLock and xmlvmUnlock method to the java_lang_Object category
> - these methods simply call [XMLVMLockRegistry lock: self]; and
> [XMLVMLockRegistry unlock: self]; respectively
> - XMLVMLockRegistry is a singleton instance which uses a dictionary to
> store the lock objects for each object which uses the synchronized facility.
> - now the monitorenter and monitorexit implementations are very
> straightforward, basically like this:
>
> _op1.o = _stack[_sp --].o;
> [_op1.o xmlvmLock];
>
> _op1.o = _stack[_sp --].o;
> [_op1.o xmlvmUnlock];
>
> My implementation is currently at a proof of concept level (it leaks
> lock objects currently), but it enabled me to go from ~1100 compile
> errors in the generated code to ~30 in our application.
>
> If you like this approach, I plan to submit this for inclusion after a
> bit more testing (hello world tests were successful).
>
> I also implemented a few missing opcodes in the xsl, but our private
> xmlvm branch is still at r666 of the xmlvm trunk. We will merge from
> trunk soon and then plan to start sending back our changes. We are
> implementing fair chunks of java.io <http://java.io> and java.util (and
> java.lang along the way).
>
> Best Regards,
> Gergely
>
>
> --
> Kis Gergely
> MattaKis Consulting
> Email: ger...@ma... <mailto:ger...@ma...>
> Web: http://www.mattakis.com
> Phone: +36 70 408 1723
>
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

[xmlvm-users] Implementation of synchronized in objc

[Gergely K. <ger...@ma...>]

Hi,

I observed a problem with the way synchronized (or more accurately
monitorenter and monitorexit) were implemented.
The use of the @synchronized statement is problematic, because javac likes
to emit multiple monitorexit's in try / catch branches for a single
monitorenter in many different cases.

So I took the following approach:
- added an xmlvmLock and xmlvmUnlock method to the java_lang_Object category
- these methods simply call [XMLVMLockRegistry lock: self]; and
[XMLVMLockRegistry unlock: self]; respectively
- XMLVMLockRegistry is a singleton instance which uses a dictionary to store
the lock objects for each object which uses the synchronized facility.
- now the monitorenter and monitorexit implementations are very
straightforward, basically like this:

_op1.o = _stack[_sp --].o;
[_op1.o xmlvmLock];

_op1.o = _stack[_sp --].o;
[_op1.o xmlvmUnlock];

My implementation is currently at a proof of concept level (it leaks lock
objects currently), but it enabled me to go from ~1100 compile errors in the
generated code to ~30 in our application.

If you like this approach, I plan to submit this for inclusion after a bit
more testing (hello world tests were successful).

I also implemented a few missing opcodes in the xsl, but our private xmlvm
branch is still at r666 of the xmlvm trunk. We will merge from trunk soon
and then plan to start sending back our changes. We are implementing fair
chunks of java.io and java.util (and java.lang along the way).

Best Regards,
Gergely


-- 
Kis Gergely
MattaKis Consulting
Email: ger...@ma...
Web: http://www.mattakis.com
Phone: +36 70 408 1723

[xmlvm-users] Access to "raw" resources

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

Hi all,

I was just trying to make access to raw resources possible in xmlvm,
in my case .wav files, for the android2iphone toolchain. I thought of
implementing openRawResource() for this:

public String openRawResource(int resourceId) throws Exception {
  String fileName = getFileNamePath(findResourceNameById(resourceId));
  String filePath = NSBundle.mainBundle().pathForResource(fileName,"wav");
  return new FileInputStream(filePath);
}

However, this leads to severe crashes -  in one case even bringing
down MacOS(!) when running the app on the simulator. I've checked and
fileName / filePath give back reasonable paths (when manually
adding the wav files to the resources in Xcode, of course -
otherwise it crashes on program start ;-). The moment I instantiate
FileInputStream, I get severe crashes without any debugging info
that I can see (in Xcode when running on the emulator)

I've checked the objectiveC implementation of FileInputStream and it
seems to look ok. I've observed this behavior for SVN rev. 690.

Any ideas what could cause this?

Best,
  Alex
P.S. Very minor issue: float and double NaN constants should read NAN in
objC - not NaN.
-- 
Dr. Alexander K. Seewald

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

Re: [xmlvm-users] Having trouble bringing up projects in XCode

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

On 11 Δεκ 2009, at 1:44 π.μ., Scott Wells wrote:

> Okay, after debugging a little bit, I can see the problem.  It's happening in the following stack:
> 
> 	  at org.xmlvm.proc.out.build.PathFileFilter.accept(PathFileFilter.java:18)
> 	  at org.xmlvm.proc.out.build.BuildFile.getFileNames(BuildFile.java:60)
> 	  at org.xmlvm.proc.out.build.XCodeFile$XCodeProj.injectFiles(XCodeFile.java:123)
> 	  at org.xmlvm.proc.out.build.XCodeFile$XCodeProj.access$100(XCodeFile.java:87)
> 	  at org.xmlvm.proc.out.build.XCodeFile.composeBuildFiles(XCodeFile.java:74)
> 	  at org.xmlvm.proc.out.IPhoneOutputProcess.process(IPhoneOutputProcess.java:118)
> 	  at org.xmlvm.proc.XmlvmProcessor.process(XmlvmProcessor.java:104)
> 	  at org.xmlvm.proc.NewMain.main(NewMain.java:50)
> 
> The project source file paths look like:
> 
> .\dist\demo\iphone\ihelloworld\fullscreen\iphone\src\app\org_xmlvm_demo_ihelloworld_fullscreen_HelloWorld.h
> 
> but it's looking (via String.endsWith()) to see if the file is under the path "/src/app".  So yes, it's a path delimiter issue.  There are a couple of ways to fix this: 1) canonicalize the project files' paths to use front-slashes before comparing; 2) canonicalize the test locations for the filters (and really any constructed paths) to use the OS's native path delimiter.  I can make these changes, but I wanted to get the folks who have written this code to weigh in because I don't want to make a change that's not in sync with how you guys would like to go.  Or I'm happy deferring the change to you guys as well...  Please let me know how you'd like to proceed.
> 
> Thanks!
> Scott

hehe, I was expecting this :)

My opinion is to go with the (1) solution, since at the end of the day this code will run under Mac 

Re: [xmlvm-users] Having trouble bringing up projects in XCode

[Scott W. <sco...@gm...>]

Okay, after debugging a little bit, I can see the problem.  It's happening
in the following stack:

  at org.xmlvm.proc.out.build.PathFileFilter.accept(PathFileFilter.java:18)
  at org.xmlvm.proc.out.build.BuildFile.getFileNames(BuildFile.java:60)
  at
org.xmlvm.proc.out.build.XCodeFile$XCodeProj.injectFiles(XCodeFile.java:123)
  at
org.xmlvm.proc.out.build.XCodeFile$XCodeProj.access$100(XCodeFile.java:87)
  at org.xmlvm.proc.out.build.XCodeFile.composeBuildFiles(XCodeFile.java:74)
  at
org.xmlvm.proc.out.IPhoneOutputProcess.process(IPhoneOutputProcess.java:118)
  at org.xmlvm.proc.XmlvmProcessor.process(XmlvmProcessor.java:104)
  at org.xmlvm.proc.NewMain.main(NewMain.java:50)

The project source file paths look like:

.\dist\demo\iphone\ihelloworld\fullscreen\iphone\src\app\org_xmlvm_demo_ihelloworld_fullscreen_HelloWorld.h

but it's looking (via String.endsWith()) to see if the file is under the
path "/src/app".  So yes, it's a path delimiter issue.  There are a couple
of ways to fix this: 1) canonicalize the project files' paths to use
front-slashes before comparing; 2) canonicalize the test locations for the
filters (and really any constructed paths) to use the OS's native path
delimiter.  I can make these changes, but I wanted to get the folks who have
written this code to weigh in because I don't want to make a change that's
not in sync with how you guys would like to go.  Or I'm happy deferring the
change to you guys as well...  Please let me know how you'd like to proceed.

Thanks!
Scott

2009/12/10 Scott Wells <sco...@gm...>

> Okay, I've built XMLVM on the Mac and have compared the XCode project
> output for the ihelloworld fullscreen demo.  They're definitely different.
>  The Mac-produced version has all of the leaf source files in the project
> file while the Window-produced version does not.  I've attached the
> project.pbxproj files to this email.  I'm happy to debug into this a bit if
> no one else knows a quick fix off the top of the head.  Any pointers on
> where these files are generated would be appreciated, but I'm sure I can
> find them pretty quickly in the IDE, too.
>
> Regards,
> Scott
>
> 2009/12/10 Scott Wells <sco...@gm...>
>
> Yeah, I'm going to build on my Mac and diff the created projects, then see
>> if I can find in the XCode project generator where it's building paths.
>>  Unless I'm wrong, it should always be building paths that are valid on the
>> Mac (and under XCode), not on the host operating system.
>>
>> 2009/12/10 Panayotis Katsaloulis <pan...@pa...>
>>
>>
>>> On 11 Δεκ 2009, at 12:28 π.μ., Arno Puder wrote:
>>>
>>> >
>>> > well, I'm using this feature all the time without any troubles. I've
>>> > noticed from your earlier message today that you tried to compile XMLVM
>>> > on a Windows box (looking at the path names). On which system do you
>>> try
>>> > to generate the Xcode project? On Windows as well?
>>> >
>>> > Arno
>>> >
>>>
>>> Just an idea... problably this has to do with the \ character?
>>>
>>> ------------------------------------------------------------------------------
>>> Return on Information:
>>> Google Enterprise Search pays you back
>>> Get the facts.
>>> http://p.sf.net/sfu/google-dev2dev
>>> _______________________________________________
>>> xmlvm-users mailing list
>>> xml...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>>
>>
>>
>

Re: [xmlvm-users] Having trouble bringing up projects in XCode

[Scott W. <sco...@gm...>]

Yeah, I'm going to build on my Mac and diff the created projects, then see
if I can find in the XCode project generator where it's building paths.
 Unless I'm wrong, it should always be building paths that are valid on the
Mac (and under XCode), not on the host operating system.

2009/12/10 Panayotis Katsaloulis <pan...@pa...>

>
> On 11 Δεκ 2009, at 12:28 π.μ., Arno Puder wrote:
>
> >
> > well, I'm using this feature all the time without any troubles. I've
> > noticed from your earlier message today that you tried to compile XMLVM
> > on a Windows box (looking at the path names). On which system do you try
> > to generate the Xcode project? On Windows as well?
> >
> > Arno
> >
>
> Just an idea… problably this has to do with the \ character?
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] Having trouble bringing up projects in XCode

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

On 11 Δεκ 2009, at 12:28 π.μ., Arno Puder wrote:

> 
> well, I'm using this feature all the time without any troubles. I've 
> noticed from your earlier message today that you tried to compile XMLVM 
> on a Windows box (looking at the path names). On which system do you try 
> to generate the Xcode project? On Windows as well?
> 
> Arno
> 

Just an idea… problably this has to do with the \ character?

Re: [xmlvm-users] Having trouble bringing up projects in XCode

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

well, I'm using this feature all the time without any troubles. I've 
noticed from your earlier message today that you tried to compile XMLVM 
on a Windows box (looking at the path names). On which system do you try 
to generate the Xcode project? On Windows as well?

Arno


On 12/10/09 11:21 PM, Scott Wells wrote:
> Hmmmm...I just got back to looking at XMLVM again and this is still
> happening with the latest.  Again, the XCode project doesn't have any
> references to the source code for the project, so while it creates an
> app (e.g., Xokoban.app), it's basically empty.  If I add existing files
> to "Application", "Library/Andoid", "Library/iPhone", and "Resources",
> it builds and runs fine.  XCode even knows with each of those groups
> which subfolder contains the files I want, so it's like it's *almost*
> right.  Is this working for other folks?  Does anyone know why it's not
> working for me?
>
> Thanks!
> Scott
>
> On Sun, Nov 22, 2009 at 4:46 PM, Scott Wells <sco...@gm...
> <mailto:sco...@gm...>> wrote:
>
>     I'm sure I'm missing something pretty simple, but I've pulled the
>     latest xmlvm out from SVN and built it successfully using "ant all"
>     and "ant all-cc".  I can see that the latter created a series of
>     XCode projects, but when I open those in XCode, something definitely
>     doesn't seem quite right.  The project doesn't seem to have any
>     references to the source code at all, so "Build and Go" doesn't
>     really do much and there's nothing to install on the simulator.
>
>     I did manage to bring up a project successfully by following the
>     instructions in the xmlvm manual, though I had to remove everything
>     related to GL because that framework isn't added to a project as
>     described in those instructions.
>
>     Am I doing something wrong here, or are those projects just not
>     working yet?  I saw that they're a very recent addition.
>
>     Thanks for all the great work on this project!
>     Scott Wells
>
>
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] Having trouble bringing up projects in XCode

[Scott W. <sco...@gm...>]

Hmmmm...I just got back to looking at XMLVM again and this is still
happening with the latest.  Again, the XCode project doesn't have any
references to the source code for the project, so while it creates an app
(e.g., Xokoban.app), it's basically empty.  If I add existing files to
"Application", "Library/Andoid", "Library/iPhone", and "Resources", it
builds and runs fine.  XCode even knows with each of those groups which
subfolder contains the files I want, so it's like it's *almost* right.  Is
this working for other folks?  Does anyone know why it's not working for me?

Thanks!
Scott

On Sun, Nov 22, 2009 at 4:46 PM, Scott Wells <sco...@gm...> wrote:

> I'm sure I'm missing something pretty simple, but I've pulled the latest
> xmlvm out from SVN and built it successfully using "ant all" and "ant
> all-cc".  I can see that the latter created a series of XCode projects, but
> when I open those in XCode, something definitely doesn't seem quite right.
> The project doesn't seem to have any references to the source code at all,
> so "Build and Go" doesn't really do much and there's nothing to install on
> the simulator.
>
> I did manage to bring up a project successfully by following the
> instructions in the xmlvm manual, though I had to remove everything related
> to GL because that framework isn't added to a project as described in those
> instructions.
>
> Am I doing something wrong here, or are those projects just not working
> yet?  I saw that they're a very recent addition.
>
> Thanks for all the great work on this project!
> Scott Wells
>
>

Re: [xmlvm-users] Build failure after updating to latest

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

Can you make an update and check again. I replaced that class by a
ByteArrayOutputStream. Not sure why we were using that other class in the
first place.

// Sascha

On Thu, Dec 10, 2009 at 6:07 PM, Scott Wells <sco...@gm...> wrote:

> I updated to the latest XMLVM source this morning and got the error below
> while trying to build.  I can see the imported class in the JDK (1.6.0_17).
>  Any ideas?  Is this because it's a Sun internal class?
>
> Thanks,
> Scott
>
> ==================================================
>
> build-xmlvm:
>      [echo] Compiling XMLVM
>     [javac] Compiling 60 source files to
> c:\Users\swells\dev\projects\xmlvm\build\bin
>     [javac]
> c:\Users\swells\dev\projects\xmlvm\src\xmlvm\org\xmlvm\proc\out\CILByteCodeOutputProcess.java:40:
> package com.sun.xml.internal.messaging.saaj.util does not exist
>     [javac] import
> com.sun.xml.internal.messaging.saaj.util.ByteOutputStream;
>     [javac]                                                ^
>     [javac]
> c:\Users\swells\dev\projects\xmlvm\src\xmlvm\org\xmlvm\proc\out\CILByteCodeOutputProcess.java:204:
> cannot find symbol
>     [javac] symbol  : class ByteOutputStream
>     [javac] location: class org.xmlvm.proc.out.CILByteCodeOutputProcess
>     [javac]         ByteOutputStream outputStream = new ByteOutputStream();
>     [javac]         ^
>     [javac]
> c:\Users\swells\dev\projects\xmlvm\src\xmlvm\org\xmlvm\proc\out\CILByteCodeOutputProcess.java:204:
> cannot find symbol
>     [javac] symbol  : class ByteOutputStream
>     [javac] location: class org.xmlvm.proc.out.CILByteCodeOutputProcess
>     [javac]         ByteOutputStream outputStream = new ByteOutputStream();
>
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>

Re: [xmlvm-users] Xokoban has been accepted by Apple!

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

Exactly. They might find other arbirtrary reason for why they don't like your app, but it won't be the fact that iit's written using xmlvm ;)

Actually it would have surprised me if they would have had a problem with it, now that they allow PhoneGap apps as well.

// Sascha

"Kevin Glass" <ke...@co...> wrote:

>The security that the application being XMLVM based won't be one of the
>bizarre and random reasons Apple come up with to reject you mean :D
>
>2009/12/10 Sascha Haeberling <sa...@xm...>
>
>> Indeed, we're very excited about this. XMLVM developers should now have the
>> security of knowing that XMLVM apps will be accepted in the AppStore.
>>
>>
>> On Thu, Dec 10, 2009 at 2:11 PM, Jochen Hiller <jo....@go...>wrote:
>>
>>> Cool. This is an important step to accept XMLVM as technology for cross
>>> platform development.
>>>
>>> Congratulations, Jochen
>>>
>>>
>>> On Thu, Dec 10, 2009 at 10:58 AM, Arno Puder <ar...@pu...> wrote:
>>>
>>>>
>>>> Guys,
>>>>
>>>> we have been waiting for this news for a long time. Waiting for 5 months
>>>> in fact. Some of you may know that there is a little game part of XMLVM:
>>>> Xokoban, an Android implementation of the old Sokoban game. You can find
>>>> its source code in xmlvm/demo/android/xokoban. This application is
>>>> developed in Java only making use of Android's API. Using XMLVM we
>>>> cross-compiled Xokoban to the iPhone.
>>>>
>>>> We have been quite provocative with this application. The splash screen
>>>> of Xokoban explicitly mentions that this application is cross-compiled
>>>> from a different smartphone platform. That was probably the reason it
>>>> took Apple 5 months to review it.
>>>>
>>>> As of today, Xokoban is in the AppStore! We have also published Xokoban
>>>> on the Android Market. So, you iPhone and Android users, look for
>>>> "Xokoban" on your respective app markets.
>>>>
>>>> Xokoban is only a simple game; we are not game developers but tool
>>>> developers. The important thing is that Apple is not blocking XMLVM as a
>>>> technology. Considering Apple's behavior in the past this should be good
>>>> news to everyone who considers using XMLVM.
>>>>
>>>> We at XMLVM are quite happy about this news.
>>>>
>>>> The XMLVM team.
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Return on Information:
>>>> Google Enterprise Search pays you back
>>>> Get the facts.
>>>> http://p.sf.net/sfu/google-dev2dev
>>>> _______________________________________________
>>>> xmlvm-users mailing list
>>>> xml...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Return on Information:
>>> Google Enterprise Search pays you back
>>> Get the facts.
>>> http://p.sf.net/sfu/google-dev2dev
>>>
>>> _______________________________________________
>>> xmlvm-users mailing list
>>> xml...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Return on Information:
>> Google Enterprise Search pays you back
>> Get the facts.
>> http://p.sf.net/sfu/google-dev2dev
>>
>> _______________________________________________
>> xmlvm-users mailing list
>> xml...@li...
>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>
>>

Sent from my Android phone with K-9. Please excuse my brevity.

Re: [xmlvm-users] Xokoban has been accepted by Apple!

[Jürgen J. <jj...@pa...>]

Arno Puder schrieb:

Great news - and: congratulations. I will try to use xmlvm (around xmas
days) to convert the meinestadt app from our existing android port back
to iphone ;)

Jürgen
> Guys,
>
> we have been waiting for this news for a long time. Waiting for 5 months 
> in fact. Some of you may know that there is a little game part of XMLVM: 
> Xokoban, an Android implementation of the old Sokoban game. You can find 
> its source code in xmlvm/demo/android/xokoban. This application is 
> developed in Java only making use of Android's API. Using XMLVM we 
> cross-compiled Xokoban to the iPhone.
>
> We have been quite provocative with this application. The splash screen 
> of Xokoban explicitly mentions that this application is cross-compiled 
> from a different smartphone platform. That was probably the reason it 
> took Apple 5 months to review it.
>
> As of today, Xokoban is in the AppStore! We have also published Xokoban 
> on the Android Market. So, you iPhone and Android users, look for 
> "Xokoban" on your respective app markets.
>
> Xokoban is only a simple game; we are not game developers but tool 
> developers. The important thing is that Apple is not blocking XMLVM as a 
> technology. Considering Apple's behavior in the past this should be good 
> news to everyone who considers using XMLVM.
>
> We at XMLVM are quite happy about this news.
>
> The XMLVM team.
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>   


-- 
juergen jatzkowski
jj...@pa...

[xmlvm-users] Build failure after updating to latest

[Scott W. <sco...@gm...>]

I updated to the latest XMLVM source this morning and got the error below
while trying to build.  I can see the imported class in the JDK (1.6.0_17).
 Any ideas?  Is this because it's a Sun internal class?

Thanks,
Scott

==================================================

build-xmlvm:
     [echo] Compiling XMLVM
    [javac] Compiling 60 source files to
c:\Users\swells\dev\projects\xmlvm\build\bin
    [javac]
c:\Users\swells\dev\projects\xmlvm\src\xmlvm\org\xmlvm\proc\out\CILByteCodeOutputProcess.java:40:
package com.sun.xml.internal.messaging.saaj.util does not exist
    [javac] import
com.sun.xml.internal.messaging.saaj.util.ByteOutputStream;
    [javac]                                                ^
    [javac]
c:\Users\swells\dev\projects\xmlvm\src\xmlvm\org\xmlvm\proc\out\CILByteCodeOutputProcess.java:204:
cannot find symbol
    [javac] symbol  : class ByteOutputStream
    [javac] location: class org.xmlvm.proc.out.CILByteCodeOutputProcess
    [javac]         ByteOutputStream outputStream = new ByteOutputStream();
    [javac]         ^
    [javac]
c:\Users\swells\dev\projects\xmlvm\src\xmlvm\org\xmlvm\proc\out\CILByteCodeOutputProcess.java:204:
cannot find symbol
    [javac] symbol  : class ByteOutputStream
    [javac] location: class org.xmlvm.proc.out.CILByteCodeOutputProcess
    [javac]         ByteOutputStream outputStream = new ByteOutputStream();

Re: [xmlvm-users] Xokoban has been accepted by Apple!

[Gohar S. <con...@gm...>]

Congratulations to XML VM team.



On Thu, Dec 10, 2009 at 6:11 PM, Jochen Hiller <jo....@go...>wrote:

> Cool. This is an important step to accept XMLVM as technology for cross
> platform development.
>
> Congratulations, Jochen
>
> On Thu, Dec 10, 2009 at 10:58 AM, Arno Puder <ar...@pu...> wrote:
>
>>
>> Guys,
>>
>> we have been waiting for this news for a long time. Waiting for 5 months
>> in fact. Some of you may know that there is a little game part of XMLVM:
>> Xokoban, an Android implementation of the old Sokoban game. You can find
>> its source code in xmlvm/demo/android/xokoban. This application is
>> developed in Java only making use of Android's API. Using XMLVM we
>> cross-compiled Xokoban to the iPhone.
>>
>> We have been quite provocative with this application. The splash screen
>> of Xokoban explicitly mentions that this application is cross-compiled
>> from a different smartphone platform. That was probably the reason it
>> took Apple 5 months to review it.
>>
>> As of today, Xokoban is in the AppStore! We have also published Xokoban
>> on the Android Market. So, you iPhone and Android users, look for
>> "Xokoban" on your respective app markets.
>>
>> Xokoban is only a simple game; we are not game developers but tool
>> developers. The important thing is that Apple is not blocking XMLVM as a
>> technology. Considering Apple's behavior in the past this should be good
>> news to everyone who considers using XMLVM.
>>
>> We at XMLVM are quite happy about this news.
>>
>> The XMLVM team.
>>
>>
>> ------------------------------------------------------------------------------
>> Return on Information:
>> Google Enterprise Search pays you back
>> Get the facts.
>> http://p.sf.net/sfu/google-dev2dev
>> _______________________________________________
>> xmlvm-users mailing list
>> xml...@li...
>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>>
>
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>