I am trying to compile Spark IDE for chrome apps from https://github.com/dart-lang/spark/tree/master/ide. Steps
Opened chrome://flags and enabled experimental api
Opened chrome://extensions and "Load unpacked extension" pointed to the local folder for the above code.
The app loads. On loading it is stuck with a loading animation forever
For running in Dartium you need to point to the app directory not the package directory.
You also need to run grind setup to copy the application to the app directory as the readme here says https://github.com/dart-lang/spark/tree/master/ide
I'm not sure this experimental settings are still necessary (probably not if you use a Dart development build which already includes Dartium 36)
For building to JavaScript you run pub build in the package directory and load the extension from build/web/app (normally it is done this way, not sure if this really works with Spark, haven't tried it myself yet)
Related
I'm trying to build the "latest" version of Appium Desktop from source (on a Mac), but I'm clearly not doing something that I need to be doing, because no binary is generated after I run all the build commands.
So, I've downloaded and unpacked the .zip archive https://github.com/appium/appium-desktop/archive/v1.16.0.zip, opened up a terminal session inside the root of the source directory, and followed the online instructions for building from source--but I think this is for the server build https://appium.io/docs/en/contributing-to-appium/appium-from-source/#running-appium-from-source
npm install
npm run build
node .
And it all appears to work successfully! I get a "build completed" message and life looks fab, but nothing launches as far as an app is concerned, and I can find no .app file anywhere in the source directory. And, oddly, there are no build instructions to be found anywhere in the source directory. There's a "ReadMe.md" file but it provides no instructions on how to build from source.
Can someone please tell me what I need to do to build and launch Appium Desktop (not the server) from source? (Oh, I also ran appium-doctor and it gave me a clean bill of health.)
Any feedback would be most appreciated!
Thanks,
Wulf
You've already run npm install so it should be as simple as running npm run dev if you want it in dev mode or npm start if you want non-dev.
See the Contributing to Appium Desktop readme for more.
I have a Unity project that uses a native ios framework from C# scripts. When I compile it for iOS app (.ipa), everything works fine.
I want to compile it for macOS, too, that means Standalone build.
To enable that, I check Standalone in import settings:
Then build the app for Standalone platform:
It builds an app, but it is unable to access native framework, and I don't see it inside package contents:
What am I missing?
unable to access native framework, and I don't see it inside package
contents:
The structure is:
Project-Name/Assets/SDK-Name/Plugins/iOS/SDK.framework
There are two issues:
1.The directory you put the plugin.
You put the iOS plugin the Plugins/iOS folder which works fine.
For Mac OSX, you put it in the Assets/Plugins folder. This is also where you put plugins for Windows and Linux.
2.You must convert or build the plugin or framework into a bundle. This bundle is what you should place in the Assets/Plugins folder.
After successfully creating, building, and emulating Cordova's Hello World project, I unzipped the project folder that I am taking over from another developer on a different machine and saved it locally. While I can run the iOS app from XCode with the built project from the previous developer, I can't run the $ cordova build ios command successfully to rebuild it on my machine.
It give the following output:
The following build commands failed:
Check dependencies
Write auxiliary files
When I run it in debug mode, I notice that both of these commands are trying to make a directory for the old dev's computer (/Users/hisName/whereHePutIt/CordovaProject/stuffItIsTryingToBuild) rather than one relative to my project folder (/Users/myName/whereIPutMine/CordovaProject/stuffItIsTryingToBuild).
There is a lot of text to comb through, but it looks as though it is always failing while attempting to make a directory in /Project/platforms/ios/CordovaLib/build/CordovaLib.build
I am really stumped by this because I can't find any sort of setting or file in the project that tries to write anywhere but a path relative to my project file, and Android builds and emulates fine.
I had a similar issue on Android actually. My home for sdk tools moved but the project still wanted to use the old sdk tools.
The solution I took was to remove the platform and then re-add it. I am sure there is a way of going through the existing files and patching this, but everything you should need is in the plugin/ and www/ and where ever you elected to keep your assets.
If you do try this, make sure to create a backup before removing the platform -- it would be awful to lose changes that someone might have jammed down in the platform/ios folder.
I just ran across this issue under similar circumstances - unzipped a zipped copy of a iOS Cordova app from a coworkers computer to continue developing it, and found I could not successfully run the cordova build command.
I managed to get this to work by deleting the old "Debug-iphonesimulator" folders that had been zipped up with the rest of the project from the other computer, and then re-running the build command.
There were two folders that I deleted:
"../ios/CordovaLib/build/CordovaLib.build/Debug-iphonesimulator"
and
"../ios/build/ProjectName.build/Debug-iphonesimulator"
Hope this helps someone!
I am running Cordova 2.9.1 for iOS. When I run my app in the browser, the console says I am missing cordova_plugins.js.
What is that? How do I get it?
Is that the reason none of my plugins are working at all?
Thanks!
Have you added the "browser" platform to your Cordova project?
cordova platform add browser
After which, you need to build the Cordova project:
cordova build browser
You'll notice the platforms/browser/www folder exists and contains a cordova_plugins.js file.
At this point, you need to "serve" files to your web browser from that folder (to test your app using a web browser). I use Grunt and the NodeStatic task for this purpose.
Hope this helps! Let me know if you have any questions, take care.
I have an angular dart application with a component using canvas via a shadowroot. This runs fine with Dartium, "run as javascript" and pub serve. However when I run pub build and launch the html file in build/web, the component does not appear. The code is at
https://github.com/siddhartha-gadgil/mathlets
Should I be using some special transformers, or do something different to build as against serve?
I tried your project and it appears to be working fine.
What I have done in the past is run pub build and hit the built file in dartium and that will not work. So you have to hit the build file from chrome proper. So if I load .../mathlets/build/web/mathlets.html in chrome it works fine.
The reason for this is because pub build is the release build, which does not copy any of the dart files. However the index file still has the check if dart is enabled than try to use dart files. Well in dartium dart is enabled but the build doesn't have the dart files. In chrome dart is not enabled so then that 'packages/browser/dart.js' file dynamically writes the mathletes.dart.js to index and launches the app that way.
If you want to work around this and improve performance of the release build at the same time you can use this transformer: http://pub.dartlang.org/packages/dart_to_js_script_rewriter
We are using this also. Ensure it's the last transformer run though, if it's before the angular transformer there are problems.