We Keep Coding

cordova/exec fails within meteor project

After building a Cordova plugin with plugman, installing it in meteor 2.3.2 and running meteor run android-build, I get the following error from within the plugin:
Unable to resolve some modules:
"cordova/exec" in ~/MeteorApp/MyPlugin/www/MyPlugin.js (web.browser)
The error line is from line 2 in the generate MyPlugin.js
// ~/MeteorApp/MyPlugin/www/MyPlugin.js
// I added this check for cordova myself
if (cordova && cordova.exec ) {
var exec = require('cordova/exec');
exports.coolMethod = function (arg0, success, error) {
exec(success, error, 'MyPlugin', 'coolMethod', [arg0]);
};
}
My meteor structure includes the plugin folder at the route of the app
I installed the package using meteor add cordova:my.plugin.id#file://path/to/plugin/project
Cordova version 10.0.8
I have the following plugin structure:
pluginDir/
src/
android/
MyPlugin.java
www/
MyPlugin.js
package.json
plugin.xml
I have tested the plugin inside a Cordova app and that works just fine.
I bet the issue here is how meteor exposes the internal Cordova object.

Solution
Meteor already wraps the cordova object so really instead of importing cordova/exec in the /www plugin definition I simply had to use cordova.exec('my logic goes here')
The above is scaffolded with plugman and the /www folder and files get generated automatically, as well as the above code.
The code above is valid within Cordova, but this logic fails within Meteor.
Extra comments
Only Android support was required for this plugin and the cordova.exec() logic was moved into a Meteor api method.
Because of this Android-only requirement the /www folder and references was removed.
The /www folder may be reintroduced in the future in order to define a nice fallback for web usage scenarios, but it's unlikely for our internal plugin.

File manager for TinyMCE 5.0.6

I have installed TinyMCE (TinyMCE Dev Package 5.0.6) in my personal project. Everything is installed and
configured correctly, but there is no File Manager available in this package. To resolve this flaw I have tried to install
ResponsiveFileManager (RFM), but it just doesn't work. There is an error in a console when I click an icon of the RFM:
plugin.js:84 Uncaught TypeError: editor.windowManager.openUrl is not a function
at Object.openmanager [as onAction] (plugin.js:84)
at theme.js:21482
at theme.js:9575
at theme.js:21480
at theme.js:2457
at each (theme.js:267)
at run (theme.js:2456)
at theme.js:2969
at theme.js:56
at theme.js:10825
I guess that RFM is not properly prepared for this version of TinyMCE.
So I want to ask if there are any available file manager plugins for TinyMCE.
I need a file manager which is capable of:
- preview of uploaded photos,
- create new catalogs,
- upload files to server's catalogs (with Drag and Drop functionality as well).

Are you sure you're using 5.0.6? editor.windowManager.openUrl was a new API in that release, so if you're using an earlier version it might cause that exception.

Electron application can't resolve 'greenworks-linux32' on Steamworks integration

I have html5 application built for desktop with Electron. I currently try to integrate Greenworks SDK for Steamworks SDK to support achievements in it.
I tried both electron-rebuild and node-gyp ways to integrate Greenworks resulted in the same error - application crashes on startup with a problem in module resolving - "greenworks-linux32.node cannot be found”.
I tried to download this file separately and put it in greenworks/lib. But the problem persists. I also tried to put whole greenworks folder in the same folder with script that calls Greenworks API.
I use the following build:
Greenworks: [v0.10.0 x64]
Steamworks SDK: [v1.40]
Electron: [v1.6.15]
Folder structure is as follows:
app/
steam_appid.txt
node_modules/
greenworks/
greenworks.js
lib/
greenworks-linux32.node
greenworks-linux64.node
greenworks-osx64.node
greenworks-win32.node
greenworks-win64.node
libsdkencryptedappticket.dylib
libsdkencryptedappticket.so
libsdkencryptedappticket64.so
libsteam_api.dylib
libsteam_api.so
libsteam_api64.so
sdkencryptedappticket.dll
sdkencryptedappticket.lib
sdkencryptedappticket64.dll
sdkencryptedappticket64.lib
steam_api.dll
steam_api.lib
steam_api64.dll
steam_api64.lib
public/
index.html
electron/
Please share any thoughts on what could it be. I have an idea that the problem caused. The problem appears only when I'm calling Greenworks API.
I used this guide to proceed: https://github.com/greenheartgames/greenworks/blob/master/docs/build-instructions-electron.md

On running sonar analysis on react-native project getting error related to sonar.java.binaries property

I have a react-native project written in JavaScript for which I'm trying to run the sonar-analysis.
I have a sonar server set-up for this and system where I'm trying to run the analysis has Sonar-scanner, npm and all other project dependencies installed.
However, When I run the sonar analysis on the react-native project I'm getting following error:
ERROR: Error during SonarQube Scanner execution
org.sonar.squidbridge.api.AnalysisException: Please provide compiled classes of your project with sonar.java.binaries property
at org.sonar.java.JavaClasspath.init(JavaClasspath.java:59)
at org.sonar.java.AbstractJavaClasspath.getElements(AbstractJavaClasspath.java:281)
at org.sonar.java.SonarComponents.getJavaClasspath(SonarComponents.java:141)
at org.sonar.java.JavaSquid.<init>(JavaSquid.java:83)
at org.sonar.plugins.java.JavaSquidSensor.execute(JavaSquidSensor.java:83)
at org.sonar.scanner.sensor.SensorWrapper.analyse(SensorWrapper.java:53)
at org.sonar.scanner.phases.SensorsExecutor.executeSensor(SensorsExecutor.java:88)
at org.sonar.scanner.phases.SensorsExecutor.execute(SensorsExecutor.java:82)
at org.sonar.scanner.phases.SensorsExecutor.execute(SensorsExecutor.java:68)
at org.sonar.scanner.phases.AbstractPhaseExecutor.execute(AbstractPhaseExecutor.java:88)
at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:180)
at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:135)
at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:121)
at org.sonar.scanner.scan.ProjectScanContainer.scan(ProjectScanContainer.java:288)
at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:283)
at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:261)
at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:135)
at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:121)
at org.sonar.scanner.task.ScanTask.execute(ScanTask.java:48)
at org.sonar.scanner.task.TaskContainer.doAfterStart(TaskContainer.java:84)
at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:135)
at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:121)
at org.sonar.scanner.bootstrap.GlobalContainer.executeTask(GlobalContainer.java:121)
at org.sonar.batch.bootstrapper.Batch.doExecuteTask(Batch.java:116)
at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:111)
at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:60)
at com.sun.proxy.$Proxy0.execute(Unknown Source)
at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(EmbeddedScanner.java:233)
at org.sonarsource.scanner.api.EmbeddedScanner.runAnalysis(EmbeddedScanner.java:151)
at org.sonarsource.scanner.cli.Main.runAnalysis(Main.java:123)
at org.sonarsource.scanner.cli.Main.execute(Main.java:77)
at org.sonarsource.scanner.cli.Main.main(Main.java:61)

Had the same issue, and was wondering where did java files came in to a node project. Then by doing a file search I found several java classes in the node_modules folder. Was able to move forward by excluding them in the sonar properties file.
sonar.exclusions=test/**, node_modules/**

The error message is actually pretty clear:
Please provide compiled classes of your project with sonar.java.binaries property
Your project includes Java files, which cannot be analyzed without also providing their compiled .class files. You must either first compile (and feed the class file location into analysis) or exclude the .java files from analysis.

I'm trying to use Angular JS Timer, and am getting a 'humaniseDuration is not defined' error

I'm using: https://github.com/siddii/angular-timer#requirements
I've bower installed the 'humanize duration' library & have scripted it into my index.html correctly.
I went to the angular-timer.js file and required in 'humanize duration' - it didn't make a difference.
Anyone have any ideas?