Is angulartics2 compatible with angular1.6
OR
Is angulartics compatible with angular2
Because I'm currently working with angular 1.6 and I plan to migrate to angular2 in the future, and I'm searching for a solution that is compatible with both
There's two "versions" available:
angulartics
and
angulartics2
As you can see, the first one is for Angular 1.x, where as the second one is for Angular 2/4/5.
I have not worked with either version, but my guess is that migrating your entire app from Angular 1.6 to Angular 2/4/5 will take a good amount of work anyways, so exchanging these plugins with one another shouldn't be that much of a problem.
So, in a way, no. This plugin isn't exactly the solution you need considering it is supposed to work in both versions. I highly doubt there's a solution available that will just work out of the box for both versions to be all honest.
Related
I am starting to work on my grid implementation using AngularJS ngGrid...But I see the next version as UI grid...which is unstable? Have any one ever used any of them and what is the main difference of both?
The github repo says that all development will happen on ui-grid
(ng-grid 3). That means ng-grid has become a legacy grid. ui-grid is
stable enough to use in my opinion and the only reason to use ng-grid
is if you already started with it. New projects would probably be
better off using ui-grid. They also claim that the performance of
ui-grid is better than that of ng-grid though I haven't tested that.
It's the same project. ng-grid is older (version 2.x), UI Grid is
newer (version 3.x) but not officially relased yet (currently in
release candidate status). They're very similar, compare the
tutorials for v2 (ng-grid) and v3 (UI Grid).
Edit (Nov 12 2014): One major feature from v2 that is still missing in
v3 is grouping (github issue). If that's something you can't do
without stick with v2 for now.
I started using the ui-grid in my project. It is pretty stable if you choose the stable version download but if you wanted to keep upto date with the new features, you can start using the unstable version (with possible bugs).
The performance has been pretty good so far with ui-grid. I load a lot of data based on the user action, including adding/removing columns on demand. The performance is good so far.
Also the code structure is way better in the ui-grid where main features are separated as modules with directives which helps a lot. For example if you want to use pagination you can include ui-grid-pagination directive and ui.grid.pagination module.
I´m planing to use Cordova v3 to develop a generic application to target mobile devices using HTML/CSS. Which is the best solution in order to reuse most of the html but having the visual style for each mobile platform? Which will be the best css/framework to use in this case (preferably free)?
Thanks in advance.
As you said "but having the visual style for each mobile platform?" I understand you are searching for a native look in the apps. the other answers are good frameworks however unless you want to spend time tweaking css they will not look similar to a native UI (visually).
I have worked with Twitter bootstrap and jQM. So far so good but for a native UI look I will go for the following options which I think are the best.
These are my top choices after spending a considerable time looking for a jQM alternative as I am not really happy with it in specific aspects.
EDIT: I am adding two new options based on my experience and what I have found so far (ionic and onsen ui).
Ionic Framework
http://ionicframework.com/
Intended to develop hybrid app using Angular JS is a really gem.
I have been working with it and it has really helped me to develop faster than when using jQuery.
It also was UI elements that you can use out of the box and they are styled properly for iOS and Android although I think its style is more iOS-lish.
Pros
Angular JS based framework
Speed up the development process because of angular JS powers
Very well documented and a lot of examples and tutorials and recipes.
You could use the CSS without using angular if it is required
Free and open source
theming is done via CSS or SASS
Enough components out of the box to start building and app.
Cons
Maybe reading the ionic documentation and the Angular ties if you want to enjoy all of its powers, but it worth it.
Onsen UI
http://s.onsen.io/
I have not work yet with it but it looks like a really complete UI option for hybrid apps.
Pros
Work with Angular and jQuery was well
Free and Open SourceFree and Open Source
It has a theming tool which make easier to customize the look in case you are afraid of CSS or SASS.
Kendo UI mobile
http://www.kendoui.com/mobile.aspx
Pros
It help you create a native look with already native UI looking elements for Android, iOS, Windows Phone, BB.
Incorporates an MVC framework
Theming machine like jQM theme roller
Looks solid (I am looking forward to use it soon)
jQuery based so you can leverage the power of all jquery and JS libraries out there to solve specific problems very easily.
Cons
It is not free for commercial use.
PhoneJS
http://phonejs.devexpress.com
Pros
jQuery based so you can leverage the power of all jquery and JS libraries out there to solve specific problems very easily.
Optionally support Knockout.js for MVVM user interface development
Cons
Seems like its community is far less reduced in comparison with kendo, so I am not sure how much people are out there using it and that could help later.
It is not free for commercial use.
Chocolate chip UI
http://chocolatechip-ui.com
Pros
iOS 7, Android Jelly Bean and Windows Phone 8 UI looking
Open Source and the project looks active
jQuery compatible
ChocolateChip-UI uses its own JavaScript library, ChocolateChip, for DOM manipulation, Ajax requests, etc. It is very similar to jQuery. (they claim have better performance than jQuery and Zepto)
Cons
Doesn´t seems that have a wide community out there
Steroids
http://www.appgyver.com/steroids
If you feel like a adventure explorer take a took at steroids, which is cordova compatible and they claim you UI will perform as well as native.
It is quite new, I haven´t give it a try but I seems promising, however as still is not widely used I did not decided to use it as having a lot of people using it is helpful when you face problems.
NOTE: If other have interesting alternatives to experiences with this or other UI frameworks for cordova/phonegap please share!
My suggestion would be jQuery Mobile which supports almost all mobile devices in the market.
For the list of supported devices: http://jquerymobile.com/gbs/
1) It provides a native feel for each device platform.
2) Supports all platform
3) Easy support and 3rd party plugins
It's been said by some that jQuery mobile might be slow.. but you can tweak its settings to make it good.
You could use Onsen UI. It claims to be faster than jQuery and has its own theme roller and is built to be compatible with PhoneGap/Cordova.
try you using twitter bootstrap, http://getbootstrap.com..
might be a solution for you, because twitter bootstrap is framework for html and responsive code for all device,, check resolution web in http://quirktools.com/screenfly.. and you can convert web with phonegap..
I'm enjoying the Bootstrap tutorials here, but after the first two, I realize that it's working off a V1 version of Bootstrap, where the layout worked as a 16-column grid and things like the span-one-third class were still active.
I know I could download and use an old version of Bootstrap, but (a) I'm not that smart, and (b) I'm trying to adopt best practices early on by using a github fork.
I'm not sure what else this tutorial will differ on. I can kind of figure out the differences between a 16- and a 12-column grid, but is there anything in Bootstrap between 1.4 and 2.0 that will completely screw me up while I follow these tutorials?
Super crucial. There were a significant amount of changes from 1.4 to 2.0, as summarized here: http://twitter.github.com/bootstrap/upgrading.html
I would highlight being almost fully responsive as the most important change, but just about any other component has changed, providing better support for mobile devices and keeping up to date with new standards and changes in the industry.
By not upgrading to 2.0 you are limiting yourself from future updates to your framework, as most of the changes will break your current progress. Some of the tutorials are good to follow as a "get the idea and implement yourself" tutorial.
Don't stay behind technology just because you are comfortable. You won't be when you have no support for the issues you run into, which are probably fixed in 2.0 or some later version. Save your time now!
I am trying to use plone 4 with deco, using this buildout: http://svn.plone.org/svn/plone/plone.app.deco/buildouts/dev/
It seems to work, but when I add the new page element nothing special happens. (No deco.gs)
Anyone knows what is happening? or know a way of making it work with plone 4?
Deco is still experimental as of this writing, and shouldn't be used in production just yet.
Steps to get it working (what's currently working, that is) can be found in the install docs:
http://svn.plone.org/svn/plone/plone.app.deco/trunk/docs/INSTALL.txt
As far as i am aware, there has recently been a refactoring leaving the Deco UI editor not in a workable state. It shouldn't be a lot of work to repair, but it would be best if one of the core developers would do it.
Your best bet is probably asking on the plone.dev list to make someone do a small development push.
I want to migrate from Flex 3.1 to Flex 3.5, but I can't find any useful release notes on the differences between the two. I found the official Adobe website but it is more focused on the difference between 2 and 3, and not different versions of 3. Can someone help me out?
Thanks
In theory there isn't a lot of difference. Have you tried to just change the SDK on your project(s) and then see what works or doesn't?
Msot of the issues you'll run into, I expect, will relate to your custom component development that extend the existing components. The Flextras AutoCompleteComboBox, for example, had issues because the way the drop down is handled in the Flex ComboBox changed from 3.4 to 3.5. Since our component is a highly customized ComboBox; we inherited this change which "Broke".
However, my experience is probably a fringe case as in the course of normal development you wouldn't be customizing things so heavily.
Try it and see.