"Angular powered bootstrap" is "ngx-bootstrap"? - ng-bootstrap

I am making a project using "Angular powered Bootstrap", but after 4 weeks of development I found out that there is also something like "ngx-bootstrap".
Are they the same thing? - If not, then which one of them is
ng-bootstrap ?
Is ngx-bootstrap dead ?

Those are completely 2 separate projects run by 2 different teams. ng-bootstrap is here:
demo: https://ng-bootstrap.github.io/
GitHub: https://github.com/ng-bootstrap/ng-bootstrap
npm: https://www.npmjs.com/package/#ng-bootstrap/ng-bootstrap
You should do your own investigations and decide which projects fits your needs better. As for any project being "dead" - you can get sense of projects state by evaluating frequency of commits, number of open issues and PRs, no of downloads on npm etc. Ultimately it is your own responsibility to choose libraries that you are planning to use.

ngx-bootstrap is definitely not dead, at the moment we are working on v2 of it
demo: https://valor-software.com/ngx-bootstrap/
github: https://github.com/valor-software/ngx-bootstrap
npm: https://www.npmjs.com/package/ngx-bootstrap
may one of the main differences of ngx vs ng, that ng supports bootstrap 4 only, while ngx-bootstrap supports bs3 and bs4

Related

Getting Started with VMWare-Clarity Design System

I would like advice on how best to move my company toward using VMWare's Clarity system, or something very much like it. Should we use it as a template? Fork it? Integrate parts of it over time?
By Q4 of 2018 we would like to:
have a decent Design System
develop in Angular 2
use Bootstrap 4
Currently we are here:
No Design System
Bootstrap 3.3.7
AngularJS
Any suggestions will be helpful!
The Clarity Design System is composed of several parts.
There are Design resources - sketch templates for the light and dark themed components as well as documentation and guidelines for using them. In addition, we publish three packages
#clr/icons - an icons library that can be used standalone. The icons are web-components and can be used like any other element in a project after you integrate it into the app
#clr/ui - standalone html/css for clarity themed components. For obvious reasons more advanced components like the datagrid or wizard are not part of this
#clr/angular - Clarity components for Angular applications.
To answer a few of your questions.
Q. Should we use it as a template?
A. No, Clarity (#clr/angular) should be integrated into your Angular application so you can use the components to build up the application with them.
Q. Fork it?
A. you are welcome to fork the code, its open source software (MIT License). If you want to stay up to date with the latest bug fixes and enhancements though I would suggest integrating it into a project and keeping up with the incremental releases. We generally try to release once a week and callout breaking changes at least two versions with deprecations.
Q. Integrate parts of it over time?
A. I (as a Clarity UI Engineer) would recommend adopting it fully from the beginning when you start your next Angular app. If not, you run the risk of competing design systems and conflicting styles and UX patterns.
We do not recommend using Clarity with Bootstrap 4. Even though our grid is based on an earlier beta version of Bootstrap 4. We would like to remove that as a dependency in the future.

angulartics2 and angular1.6 compatibility

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.

XPages: IBM OneUI vs. Bootstrap

In the near future, I have to update a bigger XPage application (development time more than three years) now running on a Domino Server 8.5.3 FP6 to Domino Server 9. In this application I am using IBM OneUIv2.1 but I am unsure if I should use it further. Unfortunately I have no experience with Bootstrap, however in one of the last Extension Library releases an essential part of the update was for Bootstrap:
This release is the sixteenth IBM Notes Domino 9.0.1 version of the
XPages Extension Library (ExtLib) to OpenNTF. This release contains a
significant Bootstrap upgrade to 3.3.6.
So for me it seems to be the XPages CSS Framework of the future?
Am I right?
Thanks in advance for sharing your experience!
I use oneUI at the day job. There are some very good things about it. However, I'm trying to get my company and all my personal work migrated to Bootstrap. OneUI is not really responsive. Even if that's not a big issue for you the biggest reason to avoid oneUI is the lack of documentation and materials for it. There actually is documentation for oneUI But nothing like Bootstrap - the most popular framework going as far as I know. Heck right here on StackOverFlow over 59,000 questions have been asked on Bootstrap. There's tons of resources like bootsnipp.com. In my opinion it's almost a no brainer that Bootstrap should be used over oneUI if at all possible.
As long as IBM won't deliver us the new "Verse" UI (which I'd refer to as OneUI Next) I'd prefer the Bootstrap UI as it is responsive. I wouldn't say that it's IBM's future UI framework as departments seem to develop indepently IMHO. The Ireland guys are proclaiming Bootstrap but the IBM Design team propagate their own styles. As always: not a straight strategy here.
But when it comes to application modernization I'd prefer Bootstrap. The next iteration will include Bootstrap 4, too (the final version).
Anyway, using Bootstrap instead of OneUI will deliver more straight and simplified CSS classes other than the "LotusUI" stuff in OneUI.
Just my 2 cents.
Yes, I agree you are right. IBM is staying in front of the curve in supporting Bootstrap for the future. I don't believe that they are investing any more resources in OneUI at this point in time. (Good news, IMO)
On the surface, your question appears opinion based, but really you need to be concerned with the level of support/investment by the IBM XPages team.
If you haven't view it already, I would recommend the TLCC webinar given this month (Feb 2016) by Brian Gleeson and Martin Donnelly on Responsive Design using Bootstrap with XPages. The team is being extremely proactive in preparing to support Bootstrap 4 which isn't even released yet.
This is the link to the webinar which is very well done: https://youtu.be/0ylbKHyiFyY
a big advantage with Bootstrap in comparison with oneUI is that there are many sites where snippets for controls / layouts / panels are being shared.
if you stick close to the oneUI defintion you are limited in your presentation options.
also Bootstrap is targetted against multiple clients (mobil / desktop / large) which oneUI is not. so if that is a requirement I definitely recommend bootstrap above oneUI.
there is a learning curve with Bootstrap but manageable.
with Bootstrap I hardly use dojo anymore and disable it in xpages whenever possible.
there are also limitations with bootstrap, e.g. motion awareness but you can overcome them with plugins. you would probably experience the same limitations with oneUI.
once you go bootstrap, you can't get back (to oneUI).
I have little experience with other front-end frameworks so I can not advice on that.

Difference between ngGrid and uiGrid?

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.

Custom CSS for Mobile development using Phonegap/Cordova

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..

Resources