![]() ![]() The pi pi-fw stuff is similar to that of bootstrap icons, this makes it easier for devs that worked with that, to get a grisp of this framework. Overall, even if you choose PrimeNG or not, I wish best of good luck for your project to succeed!Įvery framework will have its issues because they target a wide variety of use cases that may or may not be dictated by a certain set of customers/users.Ĭertain stuff is dictated by opinions (like using css classes, which I find to be fine), others by limitations to the libraries that integrate them.įor your example I would put those icon classes in their own constants, there's no need to keep it like that and you can even combine more into separate variables and set them there. You may expect significant improvements in PrimeNG on the way forward! I have some ideas, for example project is very popular the downside is the issue tracker is used for questions and support requests so we sometimes miss good feedback or defect reports, once we finish the cleanup we'll be able to realize the positive feedback easily. Tomorrow, I'll discuss this thread with my team though. ![]() Still a searchable list is available at Icons page. Today I have also provided a constants helper for PrimeIcons as well, here is the proposed API. An overview of the new PrimeNG is available on YouTube. I agree that before PrimeNG 9, things could have been better but with PrimeNG 10 we have redone almost everything, new demos, new icons, all new styling called PrimeOne, push change detection, lightweight styles to make sure it is modernized. Would you mind responding to the other people in this thread? Is there a way to reference these classes, or do i have to look them up and type them out any time i want to use them? It was about applying principles described by smacss (specifically the responsibilities of layout vs module): I did not fully understand the layout css classes part It is built based on the feedback of thousands of users since PrimeTek also develops PrimeFaces, PrimeReact and PrimeVue simultaneously.ĭo you personally use primeng in any projects? I believe if you spend more time with PrimeNG, you'll start appreciating the features and will have wow moments. Icons are font-icons, they can be used without angular as well with "pi pi-*" prefix, I'm not sure why we'd like to complicate it with an icon component or directive and force angular to do more processing. To reduce the amount of declarative markup, we use a MenuModel so that you don't need to use a lot of *ngIfs and *ngFors to render the content. Menu component you've mentioned instead renders html elements mostly nested ul, li's and anchors. Panel is a container component not a menu component, idea of that demo is to show how to use templating to customize the content, the icon belongs to the button component. I did not fully understand the layout css classes part but PrimeFlex is optional and you can use your own css utilities or a 3rd party of your choice. Hey there! PrimeNG lead here, we have been developing UI component libraries since 2005 so every decision has a background history. Could someone set me straight on what it is like to use primeng for a large project?Īlso, my S-key is going out, so i might have missed a few somewhere. The API seems not very well thought out in places. specifically, why do they insist on using css classes for icons instead of providing icon components or directives or at least constants somewhere? Those are just two explicit examples, but my immediate reaction is it seems cumbersome to use at times. Or to define nested menu items you do this: ngOnInit() To customize or add icons to a panel's header, this is the example they provide on their docs: I would just not use primeflex and handle things myselfīut then there are parts of the API that just seem a bit wonky. Specifically that they delegate layout spacing to the constituents of the container rather than from the container itself. The first thing that struck me is the usage of CSS classes for handling layouts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |