Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I was wondering what your opinion is on choosing the right tool for implementing a grid in my react project? It should support paging, filtering, adding new data, editing the existing data (in a new view). I already know that all two options support all the things I need, but I have 0 experience in all of them. So I was wondering, which one do you think is best?
ag-Grid: Absolute winner! It is feature rich, good looking and well documented.
The below link has explained the Rendering Time, Frames Per Second (FPS), Memory Consumption, Live Updates capacity in detail.
https://www.crankuptheamps.com/blog/posts/2020/01/23/grid-comparison-2/#
You can check the popularity of different grid in the below link
https://jspreadsheets.com/
From experience I can say ag grid has the best documentation so the learning and implementation will be easy. The documentation is so good that you can learn to implement all the features in just one day.
Size-wize, ag-Grid is larger than much of the competition. This may be a deal-breaker for some people.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I need to implement a Microsoft Solution with Angular Js.
Solution have one Microsoft .Net Web Api for Crud operations, and MVC5 Project with angular js. I need an angular js grid where show data from web api json. I need i grid with paging and search. No inline editing functions.
I see ng-grid. Is it the best solution?
Thanks
ng-grid is good. Lots of functionality it has. you can also use smart table. Less functionality than ng-grid but too easy to use. the functionality you told I think all will be easily covered. Its a suggestion but ng-grid is fantastic with a lot of functionalities.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
So, I have a desktop site that has lots of features and design specific contents which are not really suitable for mobile view (loading speed etc).
So, I want to have a separate mobile site, such as m.example.com.
I am thinking of somehow detecting that it is in either mobile or tablet view.
What would be the most appropriate tutorial that is up to date?
As for a good overview of what you might want (to do further research), you might want to take a look at this question: How to make Mobile website like m.yahoo.com (Mobile Version)?
For a good tutorial, I'm not sure if you're asking for a text tutorial or a video tutorial. I find that text tutorials give you options to go at your own pace and dive deeper in the subject. Therefore, I would suggest this tutorial: http://www.html5rocks.com/en/mobile/responsivedesign/
Wish you best of luck with your developing
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I need to develop a website and the website need to be responsive. I haven't developd a site since 2011. I always developed with 960px, but now I already did some Google search now and I view some statistics that say that nowadays the resolution most used is 1366x768. So maybe its better develop for 1366x768? Whats your opinion?
You can use StatCount to give you a idea how much market are you losing (the link points to screen resolution statistics for North America in the last year period).
First you can try to support all screen resolutions you can.
Now, how much work do you need to add support for lower resolutions and how that ill affect your site? It depends a lot on what do you want and how do you develop your sites.
It's a trade off and only you can tell if you need to support that resolution or if it a waste of time and money.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
So, CakePHP is a really awesome MVC framework, but I'm looking to better understand the MVC architecture in it, especially for services and organizing logic.
I currently have a lot of logic in components related to models, but I want to do some processing with that same logic in a shell script. I'm not sure if I'm approaching it correctly. I'm particularly concerned about technical debt and scaling maintainability. I don't want to go down this road then have to turn back. Thanks in advance for any and all pointers, best practice tips, etc.
You probably want to move the component logic you mentioned into models. Generally you want more of your logic in the model layer than the controller layer (which includes components).
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I am developing a mid-size application with VB2008. To better test my application I am following a MVP/Supervising Controller approach.
My question is: What are your recommendations to separate responsibilites? So far I've come up with a winform with an instance of a controller and with an instance of my class. The controls are updated via DataBinding
The problem is that I'm just not sure where to write the responsibilites (let's say Validation, Report creation, Queries and so on) Inside my class? in a separate class?
Is there any small example of a clean Winform class design that you could point me?
I would suggest you spend time reading Jeremy Millers 'Build your own CAB' series of posts to get a feel for what you might like/need to implement as your application becomes more complex.
Martin Fowler is a good source of information on all things design patterns including MVC. Fowler discusses Passive View and separation of responsibilities is demonstrated also
http://martinfowler.com/eaaDev/ModelViewPresenter.html