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.
Related
What is the difference between umbraco and vanila umbraco.
i'm currently using umbraco 6.2.1 version in my website.
Any special procedure available for upgrading this version to Vanila umbraco version.
Vanilla Umbraco means a fresh clean installation of Umbraco, without any customization.
Vanilla is a general term used for software, see also on wiki
Related to upgrading, one approach is to do a new installation of Umbraco (we can called it a vanilla installation) and then deploy your code, and migrate the content. Instead of the General Umbraco upgrade instructions.
I'd say that there is no running website with a vanilla Umbraco install. Umbraco is not a typical CMS. You are customizing it as soon as you start setting up your site in it. This is partly due to a choice on the Umbraco HQ team's decision to store their settings in the same files where you change settings by using Umbraco, requiring you to merge certain files during the upgrade.
As for upgrading, I'll warn you, there are a few ways to install Umbraco (Web PI, Nuget, Zip file), and if you upgrade in a way different than you installed, it can be hell. Step one, back up your site (front-end file-system files and db)! If you did not install Umbraco via Nuget (in Visual Studio), do not upgrade via Nuget. You will regret it.
Umbraco upgrades are a problem.
If the versions are minor running the update-package umbracocms nuget might work, but it often leaves the project mismatching version assemblies elsewhere.
Upgrading Umbraco is a bit of a minefield. Soz
Umbraco is now at version 11 and have moved their code base from the .NET framework into .NET core. Newer version is offering so much more, block-list, block-grid, inline editing, so many new and improved property editors. Editing experience and working with the CMS has changed so much since version 6.
Vanilla Umbraco would a term for a non-configured, fresh install.
You can find out everything you need to know about Umbraco on their documentation pages.
https://docs.umbraco.com/getting-started
Umbraco is a free open source project so there is no cost if you want to roll your sleeves, dig in and move over to the newest version. There are some paid offerings as well that would give support if you needed it.
Now that they have moved away from the .NET framework and moved their code base over to .NET Core there is no longer a direct path to upgrade from version 8 and earlier to the most recent version 11.
I would recommend you set up a fresh install, configure and customize as desired and then move any relevant content over to your new site.
There are many articles out there detailing how others moved over to the newer version.
Good article here on how they upgraded from version 7 to the newer version 11.
https://skrift.io/issues/how-i-upgraded-my-umbraco-v7-project-to-umbraco-v11/
Worth the read if your planning on going down that path.
Good luck.
I have been some time away from Dart. What happened to AngularDart and PolymerDart?
What is the way to go 2015?
Angular has released 1.0 but left it quite unmainained and development now focuses on Angular 2.0 which is written in AtScript and transpiled to Dart and JS. An early alpha of Angular 2.0 for Dart is available at pub.dartlang.org.
Polymer has evolved slowly the recent year. Most effort went into core- and paper-elements. Recently Polymer 0.8 (current 0.5.x) was announced and will bring some breaking changes. The architecture is changed to allow to choose between different levels of support (and with it the library size you add to your app) and some breaking changes how attributes and properties are defined and used.
A Polymer.js 0.8 release is expected during this month, availability for Dart will take a few weeks longer I guess.
I want to port a Compact Framework/Windows CE app to Xamarin to create Android and IOS (and possibly Windows Phone) "versions." I reckon I need Windows 8 for Windows Phone (8) but for now I thought I could get started with Android and IOS in moving this prehistoric app into the 21st century.
According to this article, I first need "Project linker" and can NuGet it, but searching for it via Tools > Extensions and Updates in VS 2013 returns no search results.
That article says you need VS 2012 or better; the direct link to "Project Linker," though, says it supports VS 2010.
Where do I go from here?
UPDATE
I went here, and am in the processing of downloading.
UPDATE 2
Here, it says, "Modern Integrated Development Environment (IDE) – Xamarin uses Xamarin Studio on Mac OS X, and also Xamarin Studio or Visual Studio 2010 on Windows."
Yet in VS 2013, I do have project types now for Android and IOS*, so I reckon that's just a typo (hasn't been updated)?
although I don't have a Mac, so that is not possible for me right now; also, since I'm still on Windows 7 at work, Windows 8 Phone apps are not yet a possibility, either. So at present, Xamarin within Visual Studio is simply a replacement for Eclipse/Java in the creation of Android apps.
UPDATE 3
I've been waiting for something better than PhoneGap, and I think maybe I've found it. If MS were to buy this company and bake Xamarin into Visual Studio -- voila!/yowza/wow! The cats in Cupertino will have to reach for the Pepto-Bismol!
That's a bit outdated and there's a much better approach available today.
You can use Portable Class Libraries (PCL) to share code across project spanning iOS, Android, Windows (Phones) and even OSX.
See this article (and where it leads) for more details.
I certainly agree with #poupou that PCL's are the way to go (if possible). I would recommend James Montemagno's app on github. He just created this for channel9 using VS 2013. I just created a cross-platform app based off of this and it worked out well. I would only use the file-linking for the platform specific implementations with compiler directives. This can be seen in his ServiceRegistrar class in said app.
This SO answer actually explains how to get the 2012 Project Linker to work with 2013 if you still want to go that route and gives a link to the extension.
Also, you may want to check out MvvmCross. It is open-source, has a large user-base and following, and really helps with maximum code re-use. Best part, it uses PCLs and all of it's features (plugins) are available via nuget.
I would recommend reading the article #poupou posted, watching James' channel9 videos on his github page, and (if you want to check out mvvmcross) watch #slodge's N+1 videos on mvvmcross.
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).
I am a few weeks from hopefully launching my site (Yes, I know like I may be tempting fate, even merely asking this question).
I am developing using SF 1.2.9 (using Propel ORM), but I am increasingly being tempted to upgrade to 1.4, least of all, I feel it will be less of an effort to migrate a life system from 1.4 to 2.0 later on, than from 1.2 to 1.4. Also, IIRC, active support for 1.2 is being phased out next year, whereas 1.4 is to be supported till 2012 (IIRC).
So, shall I bite the bullet and upgrade, or shall I take the (on the face of it - safer) option and stay put with 1.2.9?
If you want to use some of the new features, you should upgrade of course. As the symfony development is test driven, I assume the new versions are stable and reliable.
But: Do not upgrade to 1.4 but to version 1.3. The later has an extra compatibility layer to ensure that projects based on 1.2 still work. There are some internal changes in 1.4 that forces you to really refactor some parts of your project to keep it working. With 1.3 you can make this changes step by step.
The only differences between 1.3 and 1.4 is this compatibility layer. For specific instructions, read this upgrade guide.
As for support, 1.3 is supported until the end of next year which gives you plenty of time to upgrade to 1.4 step by step.
And in general I belief also that upgrading from 1.4 to 2.0 will be easier than from 1.2.
Edit:
You can find the changes here and the deprecated stuff here.
I don't know if 'internal changes' was the right word. There is some stuff you have to consider if you change to 1.4 but the deprecated stuff in 1.4 still works in 1.3.
I will try to upgrade one of my projects to 1.3 this weekend and I can give you feedback somehow if you want to.
Are their any compelling reasons for the upgrade? Does version 1.4 have more bug fixes, or additonal features that your appliation must have? Are their any breaking changes between 1.2.9 and 1.4? Is there any refactoring to do after you've upgraded to 1.4 from 1.2.9?
I'm looking at this from a .net framework perspective;
.net 1.1 to 2.0 - there were many changes here. many of them were breaking changes, but the benefits of the upgrade were great.
.net 2.0 to 3.0 or 3.5 - a lot of upgrades were introduced here, but not very many if any breaking changes since the last two upgrades were based on the same basic framework. You can live with the 2.0 version without upgrading to any of the other two.
So if the Symfony upgrade is similiar, I would wait for a little while. You've got your application built, tested and ready to go. See what it takes for the upgrade and then see about integrating the new features in during the next iteration of your development.
Good luck with your site, and hope this helps some.