My project was working with angular 11 and bootstrap v3 but since I updated angular to v13 my ruby project although building spits out runtime ActionView:Template errors such as:
actionview (6.1.4) lib/action_view/template.rb, line 314
which tells me that the (compile &) render template method in ruby is tripping an error.
FYI the compatibility table from:
https://www.npmjs.com/package/ngx-bootstrap#compatibility
goes as far as: Angular 10 with Bootstrap v3
Related
When using Xcode 11.3 and running on watchOS 6.1.1, I see the following conflicts
objc[45250]: Class AVAssetDownloadTask is implemented in both /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/watchOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/CFNetwork.framework/CFNetwork (0x4ddd0ec) and /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/watchOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/AVFoundation.framework/AVFoundation (0x16aea494). One of the two will be used. Which one is undefined.
objc[45250]: Class AVAssetDownloadURLSession is implemented in both /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/watchOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/CFNetwork.framework/CFNetwork (0x4dddd44) and /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/watchOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/AVFoundation.framework/AVFoundation (0x16aea4bc). One of the two will be used. Which one is undefined.
Then my URLSession code stops working
2020-01-13 22:50:12.430920+0100 MyAppWatch WatchKit Extension[45250:2099229] Task <3CECDE81-59B9-4EDE-A4ED-1BA173646037>.<1> finished with error [-999] Error Domain=NSURLErrorDomain Code=-999 "cancelled" UserInfo={NSErrorFailingURLKey=https://myapp.com/def.json, NSErrorFailingURLStringKey=https://myapp.com/def.json, NSLocalizedDescription=cancelled}
It works perfectly on watchOS 6.0 and before, this is probably due to URLSession classes conflicts. How to solve this?
I am using d3js for my project in Angular CLI.
I have successfully integrated d3js in the project. In order to perform what I want to create, I need the scale method. However, D3js 4.0 have been split into mini-libraries and it seems like each of them have to be integrated separately into the project. Here you can see the result of npm install d3:
node_module_tree
I tried importing d3 and d3-scale like this:
angular-cli-build.js
vendorNpmFiles: [
'systemjs/dist/system-polyfills.js',
'systemjs/dist/system.src.js',
'zone.js/dist/**/*.+(js|js.map)',
'es6-shim/es6-shim.js',
'reflect-metadata/**/*.+(ts|js|js.map)',
'rxjs/**/*.+(js|js.map)',
'#angular/**/*.+(js|js.map)',
'#angular2-material/**/*',
'bootstrap/**/*',
'ng2-bootstrap/**/*.js',
'moment/moment.js',
'd3/**/*.js',
'd3-scale/**/*.js'
]
system-config.ts
const map: any = {
'#angular2-material': 'vendor/#angular2-material',
'ng2-bootstrap': 'vendor/ng2-bootstrap',
'moment': 'vendor/moment/moment.js',
'd3': 'vendor/d3/build/d3.js',
'd3-scale': 'vendor/d3-scale/build/d3-scale.js'
};
my_component
import * as d3 from 'd3';
import * as d3Scale from 'd3-scale';
But the build fail even if my d3-scale is in the vendor folder, he cannot find it.
Is it the correct way to integrate those mini libraries?
Thanks!
I found my problem.
Definitely Typed does not provide a typings file for d3js 4.0 but for 3.0 versions.
That's why I had:
- a method d3.scale.linear() available which returned undefined (typings for d3 3.0)
- the library d3-scale for d3 4.0 which crashed during build
So I will go back to d3js 3.0 until they provide a d.ts file for the 4.0.
I'm new to ExtJs and want to integrate ExtJs 5 app created with Sencha CMD to WebAPI app!
I did the integration for BUILD mode, but not for the DEVELOPMENT mode.
Regarding to this post
the steps of integration are done as show below!
Step 1. Creating the path: C:\VCProject\SVCodeCampWeb\WebAPI
Step 2. Creating the WebAPI project named 'API_NAME' on the directory of Step 1.
Step 3. Moving ExtJS 5 framework (ext-5.0.0) to the directory of Step 1.
Step 4. Generating the extjs app with sencha cmd:
C:\VCProject\SVCodeCampWeb\WebAPI\ext-5.0.0>sencha generate app MyApp
C:\VCProject\SVCodeCampWeb\WebAPI\API_NAME\API_NAME\CMDBUG1
Step 5. Including the ext app to Web Api through the Solution Explorer.
Step 6. Building the app with sencha cmd as shown below:
C:\Users\albert\Documents\Visual Studio 2013\Projects\BMSIA\BMSIA.Web\BMSJS>sencha app build
WORKS!!!
These are the files that I included in my _Layout.chtml of the WebAPI for BUILD mode and works!
<script src="~/CMDBUG1/build/production/MyApp/app.js"></script>
<link href="~/CMDBUG1/build/production/MyApp/resources/MyApp-all.css" rel="stylesheet" />
ERROR SECTION!!!
And for DEVELOPMENT mode I'm including these files:
< link href="~/CMDBUG1/build/production/MyApp/resources/MyApp-all.css" rel="stylesheet" />
< script src="~/CMDBUG1/ext/ext-all.js"></script>
< script src="~/CMDBUG1/app.js"></script>
But it's throwing this error:
TypeError: Ext.application is not a function
If you need more details, let me know!
Any help will be appreciated!
There is no need to set .js and .css to _Layout.cshtml. When you build your application using Sencha CMD you get index.html, app.js, resources/App-all.css and some images. The goal here is that this app can work anywhere on app domain (or other domain if CORS is applied). Web Api will provide URI's your app will call. This way you decouple client app (extjs) from server (webapi) even if they are in same project.And the whole thing will work if you for instance provide different webapi for your application. One thing to bear in mind is baseUri. While you are developing it will be http://localhost:xxxx and when app is deployed it will http://www.somedomain.com. I use simple singleton class where i set my dev and production paths(s). This is necessary so your ajax calls from models/stores/ext.ajax have a valid path to your api. General goal is to decouple client and webapi. You can put your builded app to /app folder and keep your extjs code inside /source folder which you can then exclude from publishing.
Ext.define('MyApp.config.AppConfig', {
statics: {
path: 'http://localhost:8888'
//path: 'http://client1.azurewebsites.net',
//path: 'http://client2.azurewebsites.net'
}
});
and then when calling api you say: url: MyApp.config.AppConfig.path + /users/list. This can be done nicely of course.
I'm having trouble getting angularjs working on windows phone 7 with phonegap. The simple stiff works, but as soon as I try to add page include or a view (route) it doesn't do anything. In the function matchUrl(url,obj) in angular.js (1.0.3) there is a regex that fails because Windows Phone use an unusual URL format.
What happens is angular is expecting a url like 'http://localhost/www/index.html' but in windows phone it will look like: 'x-wmapp0:app/www/index.html' instead.
Has anyone run across this and is there a solution?
This issue is as of now still unresolved and tracked here
https://github.com/angular/angular.js/issues/2303
EDIT:
The mentioned issue is still open although fix was submitted.
I managed to get a basic angular app running in phonegap WP7 by
applying the mentioned fix
including jquery (2.0.3) above angular.js
changing line of code in angular from
var xhr = new XHR();
to
var xhr = new XMLHttpRequest();
manually bootstrapping angular app after cordova deviceready event fired
I reported it here
Using angularjs-1.1.5 and changing line 5612 with
var SERVER_MATCH = /^([^:]+):[\/\/]*(\w+:{0,1}\w*#)?(\{?[\w\.-]*\}?)(:([0-9]+))?(\/[^\?#]*)?(\?([^#]*))?(#(.*))?$/,
should fix the problem
I upgraded Joomla to 1.5.14. Unfortunately I am getting a 404 error (Component not found) while accessing Chrono Forms component. I had been using Chrono Forms succesfully for a long time.
The stack trace looks like:
# Function Location
1 JAdministrator->dispatch() C:\Users\sdelamo\workspace\SVNHenaresAlDia-Trunk\administrator\index.php:67
2 JComponentHelper->renderComponent() C:\Users\sdelamo\workspace\SVNHenaresAlDia-Trunk\administrator\includes\application.php:136
3 JError->raiseError() C:\Users\sdelamo\workspace\SVNHenaresAlDia-Trunk\libraries\joomla\application\component\helper.php:120
4 JError->raise() C:\Users\sdelamo\workspace\SVNHenaresAlDia-Trunk\libraries\joomla\error\error.php:171
5 JException->__construct() C:\Users\sdelamo\workspace\SVNHenaresAlDia-Trunk\libraries\joomla\error\error.php:136
I really have no idea how to solve this problem .
It seems updating Chrono Forms to ChronoForms_V3.1_RC5.5.zip solved the problem