gluon

I hope to make use of existing functionalities in other apps on iOS in my own app. To my knowledge it should be able to be done with URL custom schemes: https://developer.apple.com/library/content/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/Inter-AppCommunication/Inter-AppCommunication.html Right now in my TryingService gluon application that are acting as a listener, I am using RuntimeArgsService to listen for LAUNCH_URL_KEY . And to my Default-Info.plist file of this application I have added URL Identifier : com.tryingservice.TryingService , and URL Scheme : outputHello . How

Hi guys Am new to Android development using javafx . Am trying to create push notification on android using javafx (javafxports and gluon Mobile ) . My problem is that push-notification is not displaying as I did Expected. I got this idea from http://gluonhq.com/products/mobile/charm-down/ http://docs.gluonhq.com/charm/javadoc/4.2.0/com/gluonhq/charm/down/plugins/LocalNotificationsService.html#getNotifications-- here's the gradle.build file Below. buildscript { repositories { jcenter() } dependencies { classpath 'org.javafxports:jfxmobile-plugin:1.2.0' } } apply plugin: 'org.javafxports

I'm trying to implement a JavaFX ScrollPane with a nested VBox, and I'm experience a strange issue when scrolling too fast in mobile. The issue is that if I scroll in smaller yet quick upward gestures, the scrollpane stalls for a half a second first, and then continues. It gets laggy in random swipe gestures. Is there anyway I can optimize this? This doesn't happen on the desktop version, so I'm guessing it may be a limitation of my phone and JavaFX itself. This issue is more evident when I set a background image for the scroll pane viewport. Here is some sample code for a View: public class

I had created small mobile apps using Gluon Mobile and now on beta testing trough Google Play. but I realized that start-time of my mobile apps on android device is quite slow (take around more than 10 seconds). it would be great if I can add a SplashScreen before the apps is loaded so user will not waiting in total for 10 times, but they feel only half of it because they got response from apps while seeing the SplashScreen. on native android development, we just build 2 activity (one for SplashScreen and one the main apps) like blow : <activity android:name=”.SplashScreen”> <intent-filter>