I have these packages importing:
angular/common
angular/compiler
angular/core
angular/http
angular/platform-browser
angular/platform-browser-dynamic
Beta 17 was working with IE shim:
node_modules/angular2/es6/prod/src/testing/shims_for_IE.js
node_modules/angular2/bundles/angular2-polyfills.min.js
node_modules/es6-shim/es6-shim.min.js
What is the equivalent of this for RC?
The order matters, it should be in this order
node_modules/zone.js/dist/zone.min.js
node_modules/reflect-metadata/Reflect.js
node_modules/es6-shim/es6-shim.min.js
Related
Describe the bug
in p-steps completed and incompleted steps should have different styles just to differentiate between them. .It was possbile with primeng9 version with ui-steps-incomplete and ui-steps-complete classes. but after migrating to 11 these classes have been removed. is there any alternate way we could do this?
Environment
Windows 10
Angular version: Angular 11
PrimeNG version: 11.4.5
node: 16.10
Reproducer
No response
Angular version
11
PrimeNG version
11.4.5
Build / Runtime
Angular CLI App
Language
ALL
Node version (for AoT issues node --version)
16.10
Browser(s)
No response
Steps to reproduce the behavior
currentbehaviour
go to p-steps and try to click next in steps . so that it shifts from step1 to step2, step2 to step3 etc
Expected behavior
if the user completes step1 and goes to steps2
step1(that is already completed should have some colors ie color1, background1 )
active one should have color2, background2
step3 ie next steps (incomplete one's) should have color3, background3
expected
When attempting to use Expo (SDK 43) in managed mode on an iPad Air 4th Gen (OS 15.0.2) with expo-three, expo-gl and a <GLView> with a model containing a SkinnedMesh and transparent textures, I receive the following warning:
Warning: THREE.WebGLRenderer: EXT_color_buffer_float extension not supported.
This is further confirmed with requesting the list of available extensions:
const ext = glContext.getExtension("EXT_color_buffer_float");
const availableExtensions = glContext.getSupportedExtensions();
...
Supported render extensions: APPLE_clip_distance,APPLE_color_buffer_packed_float,APPLE_copy_texture_levels,
APPLE_rgb_422,APPLE_texture_format_BGRA8888,EXT_color_buffer_half_float,EXT_debug_label,EXT_debug_marker,
EXT_pvrtc_sRGB,EXT_read_format_bgra,EXT_separate_shader_objects,EXT_shader_framebuffer_fetch,
EXT_shader_texture_lod,EXT_shadow_samplers,EXT_texture_filter_anisotropic,IMG_read_format,
IMG_texture_compression_pvrtc,KHR_texture_compression_astc_ldr,OES_standard_derivatives,
OES_texture_float_linear,OES_texture_half_float_linear,WEBGL_compressed_texture_astc,
WEBGL_compressed_texture_etc,WEBGL_compressed_texture_pvrtc
Required extension EXT_color_buffer_float: NOT AVAILABLE!
...
But what is confusing is that the render capabilities indicate the WebGL2 is available:
console.log(`Render Capabilities: ${JSON.stringify(renderer.capabilities)}`);
...
Render Capabilities: {"isWebGL2":true,"drawBuffers":true,"precision":"highp","logarithmicDepthBuffer":false,
"maxTextures":16,"maxVertexTextures":16,"maxTextureSize":16384,"maxCubemapSize":16384,
"maxAttributes":16,"maxVertexUniforms":512,"maxVaryings":15,"maxFragmentUniforms":224,
"vertexTextures":true,"floatFragmentTextures":true,"floatVertexTextures":true,"maxSamples":4}
and webglreport.com in Safari indicates that WebGL2 is supported and that the EXT_color_buffer_float is available. In fact, the extension list differs from the webglreport.
Versions
expo sdk: 43
expo-gl: 11.0.3
expo-gl-cpp: 11.0.1
expo-three: 6.0.1
react: 17.0.1
react-native: 0.64.2
three: 0.133.1
Question
How can I enable actual/complete WebGL2 support with the complete extension set as reported by webglreport with react-native on ios15?
I encounter an error when trying to send my app to the server for building (android). Netbeans outputs the following message (actual username removed):
Prompting for password
Building for username: <actualUsernameHere>
/home/user/NetBeansProjects/OPKP/build.xml:338: The attribute can't be empty
BUILD FAILED (total time: 6 seconds)
Build.xml (around line 338):
<target name="build-for-android-device" depends="clean,copy-android-override,copy-libs,jar,clean-override">
<codeNameOne
jarFile="${dist.jar}"
displayName="${codename1.displayName}"
packageName = "${codename1.packageName}"
mainClassName = "${codename1.mainName}"
version="${codename1.version}"
icon="${codename1.icon}"
vendor="${codename1.vendor}"
subtitle="${codename1.secondaryTitle}"
targetType="android"
keystoreAlias="${codename1.android.keystoreAlias}"
keystore="${codename1.android.keystore}"
certPassword="${codename1.android.keystorePassword}"
automated="${automated}"
/> //line 338
</target>
Also Codename One settings won't show up...
It stared when I received this error:
Cannot use a cn1lib with java version greater then the project java version
At the same time Netbeans had a problem with JavaFX. So I downloaded the latest jdk and add a hint in codename one: java.version -> 8. This fixed both issues, but now I can't build my app.
EDIT:
Codename_settings.properties file (some info are hidden, but are present in the file):
#
#Tue Jul 11 14:27:58 CEST 2017
codename1.ios.appid=
codename1.ios.release.provision=
codename1.arg.java.version=8
codename1.arg.rim.obfuscation=false
codename1.arg.ios.project_type=ios
foobarfoo=This is a description of what we are going to do
codename1.arg.ios.interface_orientation=UIInterfaceOrientationPortrait\:UIInterfaceOrientationPortraitUpsideDown\:UIInterfaceOrientationLandscapeLeft\:UIInterfaceOrientationLandscapeRight
codename1.displayName=
codename1.android.keystoreAlias=
codename1.ios.release.certificate=
codename1.arg.ios.background_modes=,bluetooth-central,bluetooth-peripheral
codename1.android.keystorePassword=<actualPassHidden>
codename1.ios.provision=
codename1.arg.ios.add_libs=;CoreBluetooth.framework
codename1.arg.ios.dsym=false
codename1.arg.android.release=true
roid.keystoreAlias=<actualAliasHidden>
codename1.arg.ios.statusbar_hidden=false
codename1.languageLevel=5
codename1.android.keystore=<actualPathHidden>
codename1.arg.ios.pods=,Cordova
codename1.vendor=CodenameOne
codename1.arg.win.ver=8
codename1.ios.certificatePassword=
codename1.ios.debug.certificatePassword=
codename1.mainName=Main
codename1.ios.release.certificatePassword=
codename1.arg.ios.prerendered_icon=false
codename1.ios.debug.certificate=
libVersion=169
codename1.arg.android.xpermissions=<uses-permission android\:name\="android.permission.BLUETOOTH"/><uses-permission android\:name\="android.permission.BLUETOOTH_ADMIN"/><uses-permission android\:name\="android.permission.ACCESS_COARSE_LOCATION"/>
codename1.arg.ios.application_exits=false
codename1.secondaryTitle=CodenameOne_Template
codename1.description=
codename1.ios.debug.provision=
codename1.arg.build.incSources=1
codename1.arg.j2me.nativeThemeConst=0
codename1.rim.certificatePassword=
codename1.version=2.0
codename1.ios.certificate=
codename1.icon=icon.png
codename1.rim.signtoolCsk=
codename1.arg.ios.plistInject=<key>NSBluetoothPeripheralUsageDescription</key><string>${foobarfoo}</string>
codename1.arg.android.debug=false
codename1.rim.signtoolDb=
codename1.arg.ios.includePush=false
codename1.arg.ios.testFlight=false
codename1.packageName=com.ijs.opkp
Does anyone know what can be the problem?
Looking thru the entries in the properties vs. the XML it seems the displayName property is blank. I didn't check everything but that seems to be an issue.
None of what used to work in RC.x helps anymore.
I have tried these:
PlatformServices.Default.Application.ApplicationVersion;
typeof(Controller).GetTypeInfo().Assembly.GetCustomAttribute<AssemblyFileVersionAttribute>().Version;
Assembly.GetEntryAssembly().GetName().Version.ToString();
They all return 1.0.0.0 instead of 1.0.0-9 which should be after execution of the dotnet publish --version-suffix 9 having this in project.json: "version": "1.0.0-*"
Basically they give me "File version" from the attached picture instead of "Product version" which dotnet publish actually seems to change.
For version 1.x:
Assembly.GetEntryAssembly().GetCustomAttribute<AssemblyInformationalVersionAttribute>().InformationalVersion;
For version 2.0.0 this attribute contains something ugly:
2.0.0 built by: dlab-DDVSOWINAGE041 so use this one:
typeof(RuntimeEnvironment).GetTypeInfo().Assembly.GetCustomAttribute<AssemblyFileVersionAttribute>().Version;
I would do it like this on ASP.NET Core 2.0+
var assemblyVersion = typeof(Startup).Assembly.GetName().Version.ToString();
In .Net Core 3.1 I show the version directly in my View using:
#GetType().Assembly.GetName().Version.ToString()
This shows the Assembly Version you have in your csproj file:
<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<AssemblyVersion>4.0.0.0</AssemblyVersion>
<FileVersion>2.2.2.2</FileVersion>
<Version>4.0.0-NetCoreRC</Version>
</PropertyGroup>
If you want to display the "other" FileVersion or "Informational" Version properties in the View add using System.Reflection:
using System.Reflection;
.... bunch of html and stuff
<footer class="main-footer">
<div class="float-right hidden-xs">
<b>Assembly Version</b> #(Assembly.GetEntryAssembly().GetName().Version)
<b>File Version</b> #(Assembly.GetEntryAssembly().GetCustomAttribute<AssemblyFileVersionAttribute>().Version)
<b>Info Version</b> #(Assembly.GetEntryAssembly().GetCustomAttribute<AssemblyInformationalVersionAttribute>().InformationalVersion)
</div>
</footer>
Note that after adding the System.Reflection the original #GetType().Assembly.GetName().Version.ToString() line returns 0.0.0.0 and you need to use the #Assembly.GetEntryAssembly().GetName().Version
There's a blog post here
Edit: Make sure to follow proper naming conventions for the Version strings. In general, they need to lead with a number. If you don't, your app will build but when you try to use NuGet to add or restore packages you'll get an error like 'anythingGoesVersion' is not a valid version string. Or a more cryptic error: Missing required property 'Name'. Input files: C:\Users....csproj.'
more here:
This work for me too:
#Microsoft.Extensions.PlatformAbstractions.PlatformServices.Default.Application.ApplicationVersion
It works with csproj file - either <Version>1.2.3.4, or <VersionPrefix>1.2.3</VersionPrefix>. However the <VersionSuffix> isn't recoganized as this doc says.
The answer by Michael G should have been the accepted one since it works as expected. Just citing the answer by Michael G above.
var version = GetType().Assembly.GetName().Version.ToString();
works fine. It gets the Package version set in the Package tab of project properties.
As an addition, if we need to get the Description we set in the same tab, this code would work. (core 3.1)
string desc = GetType().Assembly.GetCustomAttribute<AssemblyDescriptionAttribute>().Description;
Just in case someone needs this.
Happy coding !!!
I've got a strange problem on my Windows Phone 10 App.
Setup:
Cordova 6.2
Windows Platform 4.4.2
Angular 1.5.5
Angular Material v1.1.0-rc.5
Angular-Translate v.2.7.2
Inside my app I got a select-control:
<select style="width:100%;height:40px;margin-top:10px;margin-bottom:10px;" ng-model="isoCodeList.region">
<option ng-repeat="entry in ::isoCodeList.list track by $index" value="{{::entry}}">
{{::"ISO_" + entry | translate}}
</option>
</select>
The isoCodeList looks like:
$scope.isoCodeList.list = ['AD', 'AE', 'AF', 'AG',...]
The translation labels looks like:
"ISO_AE": "United Arab. Emirates"
When I open the select-control 1 second later the app crashes.
The problem doesn't exists while I debug the app via Visual-Studio, it just occures when the App is deployed and downloaded from the Windows-Store.
Also this issues doesn't occure on a Windows-Phone 8.1 device, just on Windows-Phone 10, but both get the same .appx-file.
Anyone experienced the same problem?
PS: I can't use the standard angular-material md-select because it needs more then 20 to 30 seconds to open the whole control.
Thanks in advance
Graphefruit