I'm planning to create a cross platform (Windows, Linux, macOS, Android, iOS, Wasm) audio player using latest AvaloniaUI along with LibVLCSharp. Unfortunately only support for Windows, Linux and macOS is listed for Avalonia.
I think that this might be a lack of documentation only, since Avalonia pretty recently introduced Android and iOS support officially.
So how is the state of this? Would it be possible to create a REAL cross platform player for all the listed platforms with LibVLCSharp? And if not, is there an alternative, that could be used with AvaloniaUI?
I found these libs for C#, that are (partially) capable of playing audio:
LibVLCSharp (unmanaged/wrapper, cross platform including Android + iOS)
SharpAudio (mostly managed, cross platform, but poor codec support atm)
cscore (unmanaged/wrapper, well designed, development stalled)
libsoundio-sharp (unmanaged, pretty raw)
ManagedBass (unmanaged/wrapper for BASS, awesome but only free for open source)
NAudio (awesome managed library, but windows only atm, although efforts to evolve to cross platform)
Related
I’m working on an app which is required to run on multiple different platforms. The original code is written in J2ME (Java ME).
The documentation online regarding using J2ME Polish for targeting multiple platforms is scarce and difficult to follow.
Can anyone here offer advice on targeting these 3 platforms using one code base? I’m currently using NetBeans 7.3 + the J2ME Polish plugin.
I’d ideally like to support:
Android 2.1+
BlackBerry OS 5.0+
J2ME/Java ME devices
Are there WebRTC libraries ported to BlackBerry? If not, is it possible to port Android NDK code to BB10 project?
Thanks in advance!
WebRTC is completely free for both paid and unpaid apps.
Currently, BlackBerry is interested in delivering support for WebRTC and are researching/investigating on the technology. However, no dates or release schedules have been announced at the moment.
Depending on the APIs being used in the Android app. it may or may not be possible to port Android NDK code to BlackBerry10.
Though the Android Runtime would not support WebRTC projects, BlackBerry10 OS is built on QNX, which is a fully compliant POSIX system.
The QNX compiler, QCC, has a GCC-compliant mode to easily port over existing code.
I am starting a project that is heavily graphics related (think, paint app with layers).
Anyway, I have a long history in C#, Java, JavaScript and Ruby. This application will be open source.
But what I'm looking for is a "build once, use everywhere" framework. Most of the platforms I've looked into either seem to be far too outdated, too complicated, or just not a right fit.
I've looked into Swing, WindowBuilder, wxRuby, etc. So many choices and none seem modern enough, have good documentation, etc.
I was a C# desktop developer for years so if I were targeting Windows only, I would go that route easily. But I want my app to run on Macs too. But, I would like the Mac version to look like it was designed for a Mac and the Windows version designed for Windows, etc. I'm looking at the Mono Project currently. But the idea of my Mac users installing Mono doesn't appeal to me.
Anything Ruby based would be cool but not required.
Anyway, what are some recommendations? I use NetBeans, Eclipse and Visual Studio. So I'm not concerned with learning new IDE's if I had to. I even thought about doing it all in JavaScript and using the canvas but since I need to work with large, local binary files, I didn't know if that would be a good option.
Thanks for any suggestions.
Real Studio can create cross-platform desktop apps for OS X, Windows and Linux. It can also create Cocoa apps and you can use it to interface with Cocoa directly when needed.
However, Real Studio creates Win32 apps, not .NET apps so you cannot directly interface with .NET libraries.
I was just wondering if Tizen and LiMo are same things.
Both are supported by samsung, but tizen is new version of meego and LiMo has been there since 2006.
Is samsung merging these platforms and if yes, how does that work?
The development for Limo is targeted at using C/C++ SDK. But Tizen is targeted at using HTML5 for creating apps.
See also LiMo & Tizen FAQs:
What makes Tizen different from other mobile platforms?
Tizen is a new open-source web-centric platform which supports advanced web applications, such as HTML5 and WAC. Tizen meets the mobile industry's desire for a unified mobile Linux platform built on moarket-tested technologies that is openly governed and adheres to open source principles. As Tizen will establish a third and truly independent mobile ecosystem we believe that it will attract more operators, service providers, vendors and developers.
How does Tizen relate to MeeGo and LiMo?
Tizen builds upon best practices and technologies from MeeGo and LiMo to deliver a complete cross-device open source software platform and will result in broader, stronger ecosystem support from leading service providers and OEMs. Intel will be working with partners to help them transistion from MeeGo to Tizen. In order to enable successful transition, sustainng engineering support will continue for MeeGo v1.1 and v1.2 releases into 2012. Intel will fold its ongoing MeeGo development efforts into the new Tizen project.
What are the key differences between MeeGo, LiMo and Tizen?
The key differences are Tizen's comprehensive, standards-based HTML5 application solution, broader industry support and a hardened mobile device stack.
I am a newbie to J2me. I am programming a Java program to recognise QRs.
The specifications of the projects include the compatibility with most of cellphones. For example, Nokia with Symbian, iPhone or HTC with windows mobile.
I have started downloading, JDK, WTK, eclipse and MTJ.
Any other advice would be of help.
To do this, I will need to provide a different distro for every commercial mark? or OS?
You can't run J2ME applications on iPhone or Android.
iPhone apps are written in Objective-C, and Android apps are written in regular Java (almost). Don't know about the Symbian case (but that probably runs J2ME just fine).
If you want a high degree of code-reuse, I strongly advice you to try to do the application web-based, preferably executed in the browser, or with a minimal OS-specific implementation of a front-end.