You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(29) |
Aug
(75) |
Sep
(32) |
Oct
(147) |
Nov
(31) |
Dec
(49) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(46) |
Feb
(35) |
Mar
(148) |
Apr
(33) |
May
(53) |
Jun
(46) |
Jul
(60) |
Aug
(44) |
Sep
(135) |
Oct
(23) |
Nov
(68) |
Dec
(42) |
2011 |
Jan
(94) |
Feb
(55) |
Mar
(114) |
Apr
(78) |
May
(64) |
Jun
(10) |
Jul
(31) |
Aug
(2) |
Sep
(25) |
Oct
(13) |
Nov
(8) |
Dec
(24) |
2012 |
Jan
(5) |
Feb
(33) |
Mar
(31) |
Apr
(19) |
May
(24) |
Jun
(23) |
Jul
(14) |
Aug
(15) |
Sep
(12) |
Oct
(3) |
Nov
(4) |
Dec
(19) |
2013 |
Jan
(8) |
Feb
(20) |
Mar
(4) |
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(1) |
Nov
(4) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
(6) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Sam R. <sam...@gm...> - 2012-03-17 20:16:27
|
Swing Support in Java -> iOS I've seen in earlier threads that J2SE support for Java -> iOS is nearly complete (for C backend), but lacking support for Swing (and AWT). What would it take to add support for Swing for Java -> iOS? In order of importance, I'd say the features in order of most to least important for my project would be: *most important Java2D (including Graphics2D and java.awt.Shape classes) Containers (like JComponent and JPanel) Layouts UI components like JButton/JCheckBox Composite UI components like JSpinner Specific classes like JTable *least important I just wanted to see if anyone else has taken steps in this direction, or has thought about what it would take to get there. Is there some small set of native methods that we would need to implement, or would it be necessary to provide a complete implementation of native AWT peers (as I understand it is done for desktop Swing applications). Thanks! Sam |
From: Arno P. <ar...@pu...> - 2012-03-06 19:07:06
|
Google is your friend for those kinds of questions: http://www.cs.arizona.edu/projects/mbel/ On 3/6/12 10:15 AM, vi...@gm... wrote: > I understand, but what the abbreviation MBEL means? > > -----Ursprüngliche Nachricht----- > Von: Arno Puder [mailto:ar...@pu...] > Gesendet: Dienstag, 6. März 2012 17:46 > An: xml...@li... > Betreff: Re: [xmlvm-users] MBEL, BCEL, DX > > > > As a research project, XMLVM has been around for a decade. The various > acronyms you mentioned are different byte code instruction sets that we > worked on in the past (e.g., MBEL is used for parsing .NET byte code, YARV > is the Ruby byte code). Please note that the only front/backend combination > that is currently worked on is from DEX (Dalvik Byte Code) to C. Since > Objective-C is a super-set of C, it can also be used for iOS development > (which is the C backend's main use). All other backend are demonstrators and > by no means complete. > > Arno > > > On 3/5/12 11:23 AM, vi...@gm... wrote: >> Hello, >> >> what do the abbreviations MBEL, BCEL and DX in the XMLVM toolchain >> diagram >> > (http://research.microsoft.com/en-us/um/redmond/events/ss2011/slides/friday/ > arno_puder.pdf)? >> What is happening with Objective-C programming language? Why this is >> no longer listed? >> >> Furthermore, I would like to know what is meant exactly with Ruby YARV? >> Does this mean a .rbc bytecode file? >> >> best regards >> >> Vitali >> >> >> >> >> -- >> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen >> Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de >> >> >> ---------------------------------------------------------------------- >> -------- Try before you buy = See our experts in action! >> The most comprehensive online learning library for Microsoft >> developers is just $99.99! Visual Studio, SharePoint, SQL - plus >> HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you > subscribe now! >> http://p.sf.net/sfu/learndevnow-dev2 >> >> >> >> _______________________________________________ >> xmlvm-users mailing list >> xml...@li... >> https://lists.sourceforge.net/lists/listinfo/xmlvm-users > > ---------------------------------------------------------------------------- > -- > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers is > just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro > Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: <vi...@gm...> - 2012-03-06 18:15:35
|
I understand, but what the abbreviation MBEL means? -----Ursprüngliche Nachricht----- Von: Arno Puder [mailto:ar...@pu...] Gesendet: Dienstag, 6. März 2012 17:46 An: xml...@li... Betreff: Re: [xmlvm-users] MBEL, BCEL, DX As a research project, XMLVM has been around for a decade. The various acronyms you mentioned are different byte code instruction sets that we worked on in the past (e.g., MBEL is used for parsing .NET byte code, YARV is the Ruby byte code). Please note that the only front/backend combination that is currently worked on is from DEX (Dalvik Byte Code) to C. Since Objective-C is a super-set of C, it can also be used for iOS development (which is the C backend's main use). All other backend are demonstrators and by no means complete. Arno On 3/5/12 11:23 AM, vi...@gm... wrote: > Hello, > > what do the abbreviations MBEL, BCEL and DX in the XMLVM toolchain > diagram > (http://research.microsoft.com/en-us/um/redmond/events/ss2011/slides/friday/ arno_puder.pdf)? > What is happening with Objective-C programming language? Why this is > no longer listed? > > Furthermore, I would like to know what is meant exactly with Ruby YARV? > Does this mean a .rbc bytecode file? > > best regards > > Vitali > > > > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen > Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > > ---------------------------------------------------------------------- > -------- Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft > developers is just $99.99! Visual Studio, SharePoint, SQL - plus > HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > > > > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users ---------------------------------------------------------------------------- -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ xmlvm-users mailing list xml...@li... https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: visi80 <vi...@gm...> - 2012-03-06 18:04:46
|
The Android application that I want to cross-compile is just a prototype with less user interface. How do I integrate external libraries to cross-compile? -----Ursprüngliche Nachricht----- Von: Arno Puder [mailto:ar...@pu...] Gesendet: Dienstag, 6. März 2012 17:53 An: xml...@li... Betreff: Re: [xmlvm-users] external libraries an Android project add in a xmlvm project before you try to use XMLVM to cross-compile your app, I would suggest you first see if XMLVM supports all the necessary Android API (see instructions in the slides xmlvm/doc/slides). Lately we are focusing on providing a full-featured Java API for iOS and we de-emphasize the Android to iOS part of XMLVM. Cross-platform is only feasible for a very small subset of applications (e.g., games). Arno On 2/29/12 8:10 AM, vi...@gm... wrote: > Hello, > > I have an Android project, with 4 external libraries. This project I've > been using "xmlvm --skeleton:migrate --out = <location-android-project>" > migrated to XMLVM. Then I have compiles the project with "xmlvm --in > <input-project> --out = <output-directory> --target = iphone" to an > Xcode project. The external libraries (.jar files) from the Android > project, does not compiles, ie Xcode gives me error messages from time > compilation. What am I doing wrong? At what point do I need to specify > paths for external libraries?For a short answer I would be very grateful! > > best regards > > Vitali > > P.S. Seems, the Android library is not cross-compiles with. > > > > ---------------------------------------------------------------------------- -- > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users ---------------------------------------------------------------------------- -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ xmlvm-users mailing list xml...@li... https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: Arno P. <ar...@pu...> - 2012-03-06 17:46:34
|
As a research project, XMLVM has been around for a decade. The various acronyms you mentioned are different byte code instruction sets that we worked on in the past (e.g., MBEL is used for parsing .NET byte code, YARV is the Ruby byte code). Please note that the only front/backend combination that is currently worked on is from DEX (Dalvik Byte Code) to C. Since Objective-C is a super-set of C, it can also be used for iOS development (which is the C backend's main use). All other backend are demonstrators and by no means complete. Arno On 3/5/12 11:23 AM, vi...@gm... wrote: > Hello, > > what do the abbreviations MBEL, BCEL and DX in the XMLVM toolchain > diagram > (http://research.microsoft.com/en-us/um/redmond/events/ss2011/slides/friday/arno_puder.pdf)? > What is happening with Objective-C programming language? Why this is no > longer listed? > > Furthermore, I would like to know what is meant exactly with Ruby YARV? > Does this mean a .rbc bytecode file? > > best regards > > Vitali > > > > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > > > > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: Arno P. <ar...@pu...> - 2012-03-06 16:58:19
|
before you try to use XMLVM to cross-compile your app, I would suggest you first see if XMLVM supports all the necessary Android API (see instructions in the slides xmlvm/doc/slides). Lately we are focusing on providing a full-featured Java API for iOS and we de-emphasize the Android to iOS part of XMLVM. Cross-platform is only feasible for a very small subset of applications (e.g., games). Arno On 2/29/12 8:10 AM, vi...@gm... wrote: > Hello, > > I have an Android project, with 4 external libraries. This project I've > been using "xmlvm --skeleton:migrate --out = <location-android-project>" > migrated to XMLVM. Then I have compiles the project with "xmlvm --in > <input-project> --out = <output-directory> --target = iphone" to an > Xcode project. The external libraries (.jar files) from the Android > project, does not compiles, ie Xcode gives me error messages from time > compilation. What am I doing wrong? At what point do I need to specify > paths for external libraries?For a short answer I would be very grateful! > > best regards > > Vitali > > P.S. Seems, the Android library is not cross-compiles with. > > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: <vi...@gm...> - 2012-03-05 19:23:35
|
Hello, what do the abbreviations MBEL, BCEL and DX in the XMLVM toolchain diagram (http://research.microsoft.com/en-us/um/redmond/events/ss2011/slides/friday/arno_puder.pdf)? What is happening with Objective-C programming language? Why this is no longer listed? Furthermore, I would like to know what is meant exactly with Ruby YARV? Does this mean a .rbc bytecode file? best regards Vitali -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de |
From: Panayotis K. <pan...@pa...> - 2012-03-03 12:13:54
|
Hello! Every time I compile an application with iOS as target, I get a bunch of warning messages, like these: org/xmlvm/iphone/UIViewController.class(org/xmlvm/iphone:UIViewController.class): warning: Cannot find annotation method 'references()' in type 'org.xmlvm.XMLVMSkeletonOnly': class file for org.xmlvm.XMLVMSkeletonOnly not found org/xmlvm/iphone/UIResponder.class(org/xmlvm/iphone:UIResponder.class): warning: Cannot find annotation method 'references()' in type 'org.xmlvm.XMLVMSkeletonOnly' org/xmlvm/iphone/NSObject.class(org/xmlvm/iphone:NSObject.class): warning: Cannot find annotation method 'references()' in type 'org.xmlvm.XMLVMSkeletonOnly' org/xmlvm/iphone/CGRect.class(org/xmlvm/iphone:CGRect.class): warning: Cannot find annotation method 'references()' in type 'org.xmlvm.XMLVMSkeletonOnly' org/xmlvm/iphone/UIImage.class(org/xmlvm/iphone:UIImage.class): warning: Cannot find annotation method 'references()' in type 'org.xmlvm.XMLVMSkeletonOnly' Why is this warning? How can be fixed? |
From: Velthoven, d. W.P.G. v. (Wim) <W.P...@uu...> - 2012-03-02 12:58:53
|
Hallo all, In a project I wish to port a java application to the iphone. This project started on java MIDP en javaSE. It also runs on Android and in the GWT environment. The application runs already in de Java Emulator with the Cocoa API. For the iphone I can choose between de c and the objc backend. I found that in the objc backend I miss many classes and methods, so that I need much work to add all the missing stuff. The c backed compiled and linked correctly. All classes and methods are there. However, in the IOS simulator only two of the five UIButtons worked on my main screen. The others caused a SIGABRT in XMLVM dispatching event code. I have no idea yet what caused that. My question is: Should I stay with the objc backend and work on the missing pieces. Or is that backend obsolete and should I put effort in correcting the SIGABRT Regards, Wim van Velthoven |
From: <vi...@gm...> - 2012-02-29 16:10:57
|
Hello, I have an Android project, with 4 external libraries. This project I've been using "xmlvm --skeleton:migrate --out = <location-android-project>" migrated to XMLVM. Then I have compiles the project with "xmlvm --in <input-project> --out = <output-directory> --target = iphone" to an Xcode project. The external libraries (.jar files) from the Android project, does not compiles, ie Xcode gives me error messages from time compilation. What am I doing wrong? At what point do I need to specify paths for external libraries?For a short answer I would be very grateful! best regards Vitali P.S. Seems, the Android library is not cross-compiles with. |
From: Panayotis K. <pan...@pa...> - 2012-02-24 18:08:50
|
On 24 Φεβ 2012, at 6:51 μ.μ., Arno Puder wrote: > if you made those references strong, you > would end up with a memory leak. Since a garbage collector can deal with > those situation, this is not a problem with the C backend. Thank you for the clarification. This explains the observed "weak" behavior in the ObjC backend and makes me confident that the issue is (will be) resolved in the C backend. |
From: Arno P. <ar...@pu...> - 2012-02-24 16:58:43
|
the Java compiler sometimes will introduce so-called synthetic variables to keep a reference to the surrounding context. This happens for some type of inner classes as well as anonymous classes. These synthetic references usually lead to cycles in the dependency graph. The Objective-C backend uses reference counting as a means for memory management and a cycle results in a memory leak. That is why we have decided in the old days to make synthetic references weak (to break the cycle). So, to your questions: if you made those references strong, you would end up with a memory leak. Since a garbage collector can deal with those situation, this is not a problem with the C backend. Arno On 2/24/12 5:58 AM, Panayotis Katsaloulis wrote: > > On 23 Φεβ 2012, at 10:49 μ.μ., Paul Poley wrote: > >> Take note that one method name in UIViewAnimationDelegate had changed from "animationWillStart" to "animationDidStart", and both methods gained "Object context". The name changed to match the actual Obj-C delegate methods, not to be confused with the method that sets the selector ("setAnimationWillStartSelector:"). > > > I am not sure about it. > If you read the docs, it clearly states that one must specifically set the actual selector. The name could be anything, like > animationDidStart___java_lang_String_java_lang_Object:: > or > animationDidStop___java_lang_String_boolean_java_lang_Object::: > which is something I already did (with success) in svn -r 2155 > > Of course, it's only a name (of lesser importance), but from my understanding "animationWillStart" is more appropriate, because this is a name that appears in the API, not in the comments. > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: Paul P. <bay...@gm...> - 2012-02-24 16:41:42
|
In Java, a *static* inner class is just a fancy way to make another class, but a non-static inner class maintains an implied strong reference to the containing instance. In code, it is also available via "ContainingClass.this". For example, assume class A contains inner class B which contains inner class C. If B & C are static classes, they will not have access to the containing class' non-static variables. If B & C are NOT static, B maintains a strong reference to A, and C maintains a strong reference to B. In your scenario, A now has references to C, but has removed all references to B. As long as there is a non-collectible reference to A and as long as A references C, B will not be collected, since C references B. So to answer your questions directly: 1) Yes 2) The non-static inner class has a strong reference to the containing class Thanks, Paul On Fri, Feb 24, 2012 at 7:31 AM, Panayotis Katsaloulis < pan...@pa...> wrote: > Is it possible to give me some hints, how the GC is working with inner > classes? > > I have this scenario: > > A class (level 0) has an anonymous inner class (level 1) , which in turn > has inside another anonymous inner class (level 2). > > The lifetime is like this: > > i) Class of level 0, creates a level 1 class > ii) Level 1 class creates level 2 class and gives its reference back to > level 0 class > iii Level 0 class removes all usage & references of level 1 class (the > item should be released) > iv) Level 2 class starts executing, while requiring some variables of > level 0 class. > > If I am correct, currently XMLVM is able to access information of level 0 > class to the level 2 class through the level 1 class. > If this is so, a segmentation fault would appear. > > > 1) Is this situation handled correctly by the C backend? > > 2) In ObjC backend, I can see that the inner classes hold a weak reference > to the parent class. What if we establish a strong reference between the > parent and the inner class ? > > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > |
From: Panayotis K. <pan...@pa...> - 2012-02-24 13:58:50
|
On 23 Φεβ 2012, at 10:49 μ.μ., Paul Poley wrote: > Take note that one method name in UIViewAnimationDelegate had changed from "animationWillStart" to "animationDidStart", and both methods gained "Object context". The name changed to match the actual Obj-C delegate methods, not to be confused with the method that sets the selector ("setAnimationWillStartSelector:"). I am not sure about it. If you read the docs, it clearly states that one must specifically set the actual selector. The name could be anything, like animationDidStart___java_lang_String_java_lang_Object:: or animationDidStop___java_lang_String_boolean_java_lang_Object::: which is something I already did (with success) in svn -r 2155 Of course, it's only a name (of lesser importance), but from my understanding "animationWillStart" is more appropriate, because this is a name that appears in the API, not in the comments. |
From: Panayotis K. <pan...@pa...> - 2012-02-24 13:32:13
|
Is it possible to give me some hints, how the GC is working with inner classes? I have this scenario: A class (level 0) has an anonymous inner class (level 1) , which in turn has inside another anonymous inner class (level 2). The lifetime is like this: i) Class of level 0, creates a level 1 class ii) Level 1 class creates level 2 class and gives its reference back to level 0 class iii Level 0 class removes all usage & references of level 1 class (the item should be released) iv) Level 2 class starts executing, while requiring some variables of level 0 class. If I am correct, currently XMLVM is able to access information of level 0 class to the level 2 class through the level 1 class. If this is so, a segmentation fault would appear. 1) Is this situation handled correctly by the C backend? 2) In ObjC backend, I can see that the inner classes hold a weak reference to the parent class. What if we establish a strong reference between the parent and the inner class ? |
From: Panayotis K. <pan...@pa...> - 2012-02-24 09:19:03
|
On 23 Φεβ 2012, at 9:37 μ.μ., Arno Puder wrote: > > Ideally it would be best to maintain the Objective-C backend while > pushing the new C backend. I agree that it is not optimal that there are > problems with the Objective-C backend before we can finally move over to > the C backend. However, it is also a sad reality that we have extremely > limited resources and simply don't have any spare cycles to invest into > something that will soon be retired. Since you don't use the C backend > you might want to stay with revision 2080. > > Arno Unfortunately, I can't. For example, UIPopoverController was committed in revision 2103 by me, and I need it. Of course I know how to fix this in ObjC. My point of view thought is, not to break something that works, to replace it with something that doesn't fully work yet. Like in Debian: if something breaks we should keep both parts. |
From: Paul P. <bay...@gm...> - 2012-02-23 20:49:56
|
Agreed - limited resources & retirement considerations. If you are interested in remedying the Obj-C issue, I don't mind giving some pointers. Take note that one method name in UIViewAnimationDelegate had changed from "animationWillStart" to "animationDidStart", and both methods gained "Object context". The name changed to match the actual Obj-C delegate methods, not to be confused with the method that sets the selector ("setAnimationWillStartSelector:"). An FYI - UIViewAnimationDelegate hasn't yet been updated to use more generated code via @XMLVMDelegateMethod like NSNetServiceBrowserDelegate, but that shouldn't affect the Obj-C version anyways. Thanks, Paul On Thu, Feb 23, 2012 at 1:37 PM, Arno Puder <ar...@pu...> wrote: > > Ideally it would be best to maintain the Objective-C backend while > pushing the new C backend. I agree that it is not optimal that there are > problems with the Objective-C backend before we can finally move over to > the C backend. However, it is also a sad reality that we have extremely > limited resources and simply don't have any spare cycles to invest into > something that will soon be retired. Since you don't use the C backend > you might want to stay with revision 2080. > > Arno > |
From: Arno P. <ar...@pu...> - 2012-02-23 19:37:23
|
On 02/23/2012 11:21 AM, Panayotis Katsaloulis wrote: > > On 23 Φεβ 2012, at 6:23 μ.μ., Paul Poley wrote: > >> Yes, that's correct. We had a discussion regarding protocols at the time, and it was decided to use interfaces, which I believe is the right decision. There were a few topics, but the main one was the difficultly of implementation. In the end, using Java interfaces with Obj-C protocols involved using wrapper instances to invoke the correct Java methods. >> >> Architecturally, I do not believe we should change back to abstract classes. Additionally, I have found that the C version of XMLVM has exceeded the Obj-C version. While it is unfortunate that forward progress has broken that part of the Obj-C version of XMLVM, I am not sure it is worth it to spend time on the Obj-C version, which I view as legacy. To me that means that some prior projects may use the Obj-C version, but continued support isn't necessary. Released projects should be dependent on fixed source code, so the evolution of XMLVM shouldn't affect them. I certainly wouldn't object if someone wanted to provide an update though, and I would be happy to give some pointers. >> >> I understand that you are still invested in the Obj-C version, so I'm sure we'll have a difference of opinion& I'd like to hear your point of view as well. >> >> Thanks, >> Paul > > > First of all, I don't mind whether it's better to use interfaces or abstract classes. > Everything is fine with me. > > I agree that C is the future, but unfortunately it's not the present (yet). It is far form complete and, although ObjC is far from being optimized, I believe it's not time yet to drop support for it. > This time will come, only when the C backend is at least as feature-full as the ObjC backend. > > I don't care if the backend will be C, or ObjC or any other exotic implementation. I do care though, if a project is able to run under revision 2079 (even with legacy ObjC), and doesn't run with 2080, with either backends. > > Thanks, too > :) Ideally it would be best to maintain the Objective-C backend while pushing the new C backend. I agree that it is not optimal that there are problems with the Objective-C backend before we can finally move over to the C backend. However, it is also a sad reality that we have extremely limited resources and simply don't have any spare cycles to invest into something that will soon be retired. Since you don't use the C backend you might want to stay with revision 2080. Arno |
From: Panayotis K. <pan...@pa...> - 2012-02-23 19:21:32
|
On 23 Φεβ 2012, at 6:23 μ.μ., Paul Poley wrote: > Yes, that's correct. We had a discussion regarding protocols at the time, and it was decided to use interfaces, which I believe is the right decision. There were a few topics, but the main one was the difficultly of implementation. In the end, using Java interfaces with Obj-C protocols involved using wrapper instances to invoke the correct Java methods. > > Architecturally, I do not believe we should change back to abstract classes. Additionally, I have found that the C version of XMLVM has exceeded the Obj-C version. While it is unfortunate that forward progress has broken that part of the Obj-C version of XMLVM, I am not sure it is worth it to spend time on the Obj-C version, which I view as legacy. To me that means that some prior projects may use the Obj-C version, but continued support isn't necessary. Released projects should be dependent on fixed source code, so the evolution of XMLVM shouldn't affect them. I certainly wouldn't object if someone wanted to provide an update though, and I would be happy to give some pointers. > > I understand that you are still invested in the Obj-C version, so I'm sure we'll have a difference of opinion & I'd like to hear your point of view as well. > > Thanks, > Paul First of all, I don't mind whether it's better to use interfaces or abstract classes. Everything is fine with me. I agree that C is the future, but unfortunately it's not the present (yet). It is far form complete and, although ObjC is far from being optimized, I believe it's not time yet to drop support for it. This time will come, only when the C backend is at least as feature-full as the ObjC backend. I don't care if the backend will be C, or ObjC or any other exotic implementation. I do care though, if a project is able to run under revision 2079 (even with legacy ObjC), and doesn't run with 2080, with either backends. Thanks, too :) |
From: Paul P. <bay...@gm...> - 2012-02-23 16:23:36
|
Yes, that's correct. We had a discussion regarding protocols at the time, and it was decided to use interfaces, which I believe is the right decision. There were a few topics, but the main one was the difficultly of implementation. In the end, using Java interfaces with Obj-C protocols involved using wrapper instances to invoke the correct Java methods. Architecturally, I do not believe we should change back to abstract classes. Additionally, I have found that the C version of XMLVM has exceeded the Obj-C version. While it is unfortunate that forward progress has broken that part of the Obj-C version of XMLVM, I am not sure it is worth it to spend time on the Obj-C version, which I view as legacy. To me that means that some prior projects may use the Obj-C version, but continued support isn't necessary. Released projects should be dependent on fixed source code, so the evolution of XMLVM shouldn't affect them. I certainly wouldn't object if someone wanted to provide an update though, and I would be happy to give some pointers. I understand that you are still invested in the Obj-C version, so I'm sure we'll have a difference of opinion & I'd like to hear your point of view as well. Thanks, Paul On Thu, Feb 23, 2012 at 9:14 AM, Panayotis Katsaloulis < pan...@pa...> wrote: > Hello all! > > After revision 2080 (committed by ppoley), the UIViewAnimationDelegate is > broken in the ObjC version. > Although in Java it is defined as an interface, in ObjC is defined as an > abstract class. > > This would bring once more the question, interfaces or abstract classes, > but at any case, for the time being, the ObjC part in terms of some UIView > parts is broken. > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > |
From: Panayotis K. <pan...@pa...> - 2012-02-23 15:15:02
|
Hello all! After revision 2080 (committed by ppoley), the UIViewAnimationDelegate is broken in the ObjC version. Although in Java it is defined as an interface, in ObjC is defined as an abstract class. This would bring once more the question, interfaces or abstract classes, but at any case, for the time being, the ObjC part in terms of some UIView parts is broken. |
From: Arno P. <ar...@pu...> - 2012-02-15 17:36:52
|
I agree that the Posix target shouldn't have a dependency to iOS. Well, you can use #ifdef __OBJC__ to insert code that will only be compiled under iOS. Perhaps you can submit a patch to fix this? Arno On 2/15/12 5:32 AM, Ralf Tossenberger wrote: > Hello, > > I got compile errors inside the generated C target from my Java classes. > “native_java_util_zip_CRC32.c” got some errors. > > The #include "org_xmlvm_iphone_NSObject.h" can not work for a posix project. > In the following lines of code, some fields are used which are never > declared. > > This prevents currently the use of any zip classes. > > Maybe this could be fixed by someone. > > Thanks > RT > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: Arno P. <ar...@pu...> - 2012-02-15 17:33:58
|
"red class" is an XMLVM specific thing. It just means that it is a class we don't think you'll ever need. :) If your application uses a class mentioned in xmlvm/lib/redlist.txt, XMLVM will insert a so-called "red class exception" (which is basically a runtime exception informing you that you used a red class). If you need a class, simply remove it from redlist.txt. If you do that, you should also run "ant gen-c-native-skeletons" in case the class you have taken off the red list has native methods. Arno On 2/15/12 5:19 AM, Ralf Tossenberger wrote: > Hello, > > I have heard in the past from things like “red disctricts” but never > from “red classes” - and Google couldn’t help. Who can? > > Running a Java to Posix converted program gives the following information: > XMLVM Error: Unsatisfied red class dependency: > (java_util_TimeZone___INIT___):../src/java_util_TimeZone.c:980 > > Snapshoot of the generated C code: > > voidjava_util_TimeZone___INIT___(JAVA_OBJECT me) > { > //XMLVM_BEGIN_WRAPPER[java_util_TimeZone___INIT___] > ... > > > // Red class access removed: > java.util.TimeZone,com.ibm.icu.util.TimeZone::icuTimeZone > XMLVM_RED_CLASS_DEPENDENCY(); > XMLVM_SOURCE_POSITION("TimeZone.java", 129) > XMLVM_EXIT_METHOD() > return; > //XMLVM_END_WRAPPER > } > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: Ralf T. <ral...@co...> - 2012-02-15 13:33:02
|
Hello, I got compile errors inside the generated C target from my Java classes. ³native_java_util_zip_CRC32.c² got some errors. The #include "org_xmlvm_iphone_NSObject.h" can not work for a posix project. In the following lines of code, some fields are used which are never declared. This prevents currently the use of any zip classes. Maybe this could be fixed by someone. Thanks RT |
From: Ralf T. <ral...@co...> - 2012-02-15 13:32:33
|
Hello, I have heard in the past from things like ³red disctricts² but never from ³red classes² - and Google couldn¹t help. Who can? Running a Java to Posix converted program gives the following information: XMLVM Error: Unsatisfied red class dependency: (java_util_TimeZone___INIT___):../src/java_util_TimeZone.c:980 Snapshoot of the generated C code: void java_util_TimeZone___INIT___(JAVA_OBJECT me) { //XMLVM_BEGIN_WRAPPER[java_util_TimeZone___INIT___] ... // Red class access removed: java.util.TimeZone,com.ibm.icu.util.TimeZone::icuTimeZone XMLVM_RED_CLASS_DEPENDENCY(); XMLVM_SOURCE_POSITION("TimeZone.java", 129) XMLVM_EXIT_METHOD() return; //XMLVM_END_WRAPPER } |