I am designing a suite of polymer components for finance but would like to take advantage of Angular 2.0 when it comes out, if it offers significant advantages on-top of Polymer. Can someone advise weather it is likely to be a simple process, using polymer components with Angular 2.0. Will Polymer components wrote in ES5 work well with angular 2.0 ones written in ES6?
The plans are to make Angular 2.0 compatible with Polymer.
As far as I know Angulars ES6 will be converted to ES5 anyway so I wouldn't expect any problems.
Related
I try to run my Avalonia app on .net framework. However, when I downgrade targetframework to netstandard2.0, AppBuilder becomes unavailable and I just couldn't figure out, how to fix that problem.
I couldn't find any template, that targets .net framework or netstandard. Documentation contains nothing regarding this issue. The only thing I could find is this Github issue. As I understood, AppBuilder is not supposed to be used in netstandard. Then, what is proper replacement for following code?
public static AppBuilder BuildAvaloniaApp()
=> AppBuilder.Configure<App>()
.UsePlatformDetect()
.LogToTrace()
.UseReactiveUI();
Edit:
As it was pointed out, netstandard can't be used as a target for Avalonia apps, but we can specify multiple targets. So I replaced
<TargetFramework>net7.0</TargetFramework>
with
<TargetFrameworks>net7.0;net48</TargetFrameworks>
And it worked on .NET core and .NET Framework
netstandard2.0 isn't an actual .NET framework version: it's a specification of the common API beteen .NET framework 4.6.1 and .NET core 2.0 (among others). As such netstandard2.0 only makes sense as the target framework for libraries, not applications.
If you want your app to target .NET framework then you need to use a .NET framework version as the target framework, for example net48 for .NET Framework 4.8.
I am trying to setup an application using asp.net-core 2.1 with Razor using webpack and Vue.js in the front-end.
The project is a multi-page non-spa enterprise application (you can think of AirBNB style), and it is important to use server-side routing for SEO and code maintainability.
I came across some questions about how to setup a project like this
Visual Studio 2017 Asp.Net Core 2.1 TypeScript Vue Setup - Not SPA
and template projects like this
https://github.com/mrityunjaya-kumar/AspNetCore-Vue-Starter
My question is what are the pros & cons on this type of setup and if there is a better setup for this type of application. Note that the only thing not replaceable is .net core, I have a lot of experience in the dotnet world and I don't want to learn a new language for this project.
We have a lot of components that are written in 1.6.x and we plan to upgrade them all the way to Polymer 3. I have read the upgrades guides from Polymer, but I can only see guides for 1.x to 2 and 2.x to 3, but not from 1.x to 3.
https://www.polymer-project.org/2.0/docs/upgrade
https://www.polymer-project.org/3.0/docs/upgrade
What is the best strategy to upgrade Polymer 1.6.x components to version 3?
So far from reading in each guide, I should either upgrade the components to 2.x legacy or 2.x class based components. Not hybrid, since I'm not planning to support 1.x anymore. What are the advantages and disadvantages of each type? I'm looking for the quickest way to update the components since we have a limited team and timeframe. Does Polymer 3 support each type, assuming after we run the components through the Polymer modulizer tool? Thanks in advance!
What's the difference between Polymer Starter Kit and Polymer App Toolbox?
Both are collections of web components, build & testing tools, and Material Design templates for building Progressive Web Apps with Polymer.
Which one should I base my new project on?
Here are some details regarding both of them:
Toolbox
Pros:
Was built after Polymer team started focusing on app side of Polymer
rather than elements
Gets more updates than PSK
Has all the other required tools (server, linter, bower, tester)
built-in
In case of building an element (like to publish) it uses flat import
structure, where even though bower downloads are kept in
bower_components folder and element to be made is kept outside the
bower_components folder imports are still made as though both are
present in bower_components
Is made specifically to help developers in building their
application/element
Is more in line with Progressive Web app vision of the team.
Cons:
Still in beta phase just like all the app-elements it uses internally
PSK
PSK was built with the purpose of providing a starting point for the developers who are new to Polymer and are more in learning phase. It has some pre-built elements with hard-coded data. If you look inside index.html you will find <template is="dom-bind"> being used which Polymer team recommends not to use in production environment. It was built when Polymer team was still focusing more on the elements side of Polymer as a result it does not use any of the Polymer's app-elements using which Polymer team has built the shop demo. A newer version has not been released since March as team is currently working on version 2 of PSK.
The official Polymer blog post Should I Use Polymer Starter Kit or Polymer CLI states that if you’re starting a new project, use Polymer CLI (which is a part of Polymer App Toolbox). In fact, the Polymer Starter Toolkit 2 is just another template that you can use with Polymer CLI:
I'm evaluating Knockout to use with JayData to create a standalone web application.
Following this tutorial (http://jaydata.org/tutorials/creating-a-stand-alone-web-application) it seems that I will be able to store my data on iPhone, Android and in HTML5 browsers...
I'm not sure how can I use JavaScript Query Language with Knockout. I've seen they will have some support it, but I probably you have an idea how can I do it myself.
I'm not sure if Knockout is the appropriate UI library for hybrid applications, hopefully you can share some know-how.
Thank you!
UPDATE:
From version 1.1.0 JayData has knockoutjs integration module. Include "jaydatamodules/knockout.js" in your html page, and have JayData provide Knockout observables with entity.asKoObservable(). With this module queryable.toArray() accepts ko.ObservableArrays as targets populating it with kendo observable entities.
Custom Bindings is just the way for the integration you are after. You have to connect the knockoutjs way of interacting with the JavaScript objects with the JayData entity metadata functions and its propertyChanged / propertyChanging events.
It shouldn't be difficult a task to do, as JayData supports simple property notation (object.property) and async property accessor pattern (get_property(cb), set_property(cb)) as well.
You can integrate Knockout with jQuery by way of Custom Bindings. That answers your question about integration. Custom bindings allow you to integrate with any JavaScript UI library, not just jQuery.
In regards to your second question... Knockout really isn't a UI library. It's more of a framework to facilitate data-binding between DOM objects and JavaScript objects. It is used to design web applications following the MVVM design paradigm.
Here is an example It is integrated in recent release probably