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.
Related
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.
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.
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.
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 planning to use community sever for one of our projects, i used it in the past but we had a lot of problems customizing it and understanding how things work, im affraid to get into that again, and i would like to add some things to it but i dont know how flexible it is.
Based on the fact we've been working with CS ever since version 1.0 (and even before as ASP.Net Forums) I can tell you this - CS 2007 and 2008 introduces a great out-of-the-box community solution along with a very extensive platform you can develop on top of and extend.
If you're aiming at Microsoft technologies this is the place to be.
IMPORTANT - Don't rush into their SDK and start changing the moving parts, focus on learning their theming engine (Chameleon) and using it's large variety of controls that get you farther than you could imagine. Use the SDK only when you need a better understanding of the inner working of things and when you've reached the point of extending CS.
IMPORTANT #2 - When extending, remember that Telligent releases two major versions every year, usually including features you'd want for your project, remember to review your changes and develop outside of the product core for easier upgrade to future versions.
Good luck!