Could someone please explain something for me.
I am confused. Currently Polymer and Web UI seems to be two separate projects with a lot of similarities.
Is Polymer to succeed Web UI - meaning Web UI will be discontinued in favour of Polymer?
Yes, Polymer is the successor to Web UI. At some point in the future, once Polymer is more stable, Web UI will be abandoned.
For now though, it still may make sense to use Web UI if you need it for a production app.
As mentioned already, yes Polymer is the next version of web_ui. It is being developed in conjunction with the JavaScript version of Polymer. web_ui is currently in extended support mode, in which bug fixes are applied to keep the library functional (particularly as new SDK releases are made), however there will be no new functionality added to web_ui.
As of yesterday, the integrated build reached 0.8.1, and with Polymer 0.8.1, Polymer has virtually reached parity with web_ui and in some areas already surpassed with additional functionality.
Google has committed to maintaining web_ui for existing projects, however I would highly recommend that any new projects be started with Polymer. It is also the time to look at porting any old web_ui projects over to the new libraries (something I'm in the process of doing myself).
Related
I'm new to Angular and I'm a bit confused whether the implementation of the angular components reflects the recent (2018) material design system changes or they are just updating the old version of the system?
the Angular components version is been updated:
https://trimox.github.io/angular-mdc-web/#/angular-mdc-web/home
But it seems to me that the Angular Dart components version is still using the old system:
https://dart-lang.github.io/angular_components/
Am I missing something or the Angular components will not get the latest material design updates?
(I think the Angular team is using foundations and adapters to adapt the vanilla web version of the updated material design system, is the Angular Dart team doing the same?)
The specs and M2 components are still being worked on. We have some ready, but I don't see us releasing them until after internal teams have shaken out most of the bugs. They are still going through big API changes to make sure they work well in our products.
There is one that is released which is the material_card.
I am little confused which one is best for build hybrid mobile application.
IONIC Framework, Onsen Framework, IBM Worklight, Sencha or other. I am familiar with javascript, css, and angular.js
There is no "better" framework. They all have their own strength and weakness.
The only things that matter for me when I want to start a new project with a new technology are:
Is it mature enough to be used in production?
Is it still in developpment?
Is it well documented?
Is the community active?
Is it hard to use?
I'm using Onsen UI And Ionic and for what I can tell, both are doing the job, are easy to learn once you know how to use Angular.
Ionic:
Big community and support
Lots of tool to make your developpment easier
Plugins and themes available
Growing project
Onsen UI
Can be used with multiple framework
Good Documentation
Easy Router implementation
Small community
I have a CRM plugin which I can deploy to Salesforce and it works fine.
My plugin is SPA which is written on javascript with durandal framework and it uses such libraries as knockout.js, require.js, q.amd.js, jquery.js, underscore.js, i18next.js and a few other javascript libraries. Is it possible to deploy such kind of app to Zendesk environment?
Unfortunately, up to the moment no. There is an "ongoing" discussion on Zendesk Support Forums about the matter, but it looks like it's not going to happen anytime soon. Product managers interacted in the thread expressing some will to do it, but I wouldn't rely on that happening in a near future:
At the moment we have no plans to support external libraries. We may open this up to a select few in the future.
I am using spring framework for my java enterprise application .
I felt javascript / jquery is hard to maintain for larger enterprise application.
Classes and Objects makes code maintenance easier.
how can i use dart with spring framework / JSP?.
The HTML code can be generate with JSP. However, we cannot debug with Dart Editor anymore.
It would be nice and more encourage people to start to use Dart by just by support debugging a HTML with dart from non-standard dart editor debug server.
For example: The HTML part is served by a Jetty server which contains links to dart
and we should be able to debug in Dart Editor.
Personally, This is the most needed feature otherwise, it's difficult to ask people to migrate old sytem with JSP, PHP to start to use Dart
We are listening to Dartian reponse.
I found one issue in Dart issue list: https://code.google.com/p/dart/issues/detail?id=3748
The best way to use dart with springframework and JSP is to create rich client app (RCP) in dart and use springframework and JSP for implementing a service layer that should be used by the RCP.
There are various disadvantages if you chose to mix the application state between the client (browser) and the server. Much more scalable model is to build on service oriented architecture (SOA) and keep the UI logic solely on the client side.
Hope it helps ;-)
Upgrading MVC apps done with VS 2010 has been the biggest issue for me. I have an application that I use to run various websites and I maintain and develop this application separetely then upgrade the sites based on it. A lot of things might change during development of a new version - new Views, new Controllers, stuff added into JS files, updated stylesheets etc.
I've searched around the web but nothing useful came up besides this Haack's article but no source code is available.
I also tried making a Nuget package for the entire MVC app and while this works, it doesn't package up the resource files (an issue within Nuget itself) and my apps rely on those so until this is fixed I cannot use this method.
I checked how others do it and this pretty much summarizes Umbraco's way and it's the same painful way of a dozen of steps like I do it now.
Do you have any good advice on it?
You don't specify the target OS, but I create native packages, i.e. .deb for Ubuntu servers.
However this still means you need to specify all files, manage configuration, upgrade database schemes. But if you test this on a CI server it becomes more reliable, and you can do it iteratively. This is all part of good deployment practice. I can recommend the Continuous Delivery book.