Forums Ignite UI for React
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Tihomir Teofilov
30
IGR vs IGC
posted

Hi,

I am new one to IgniteUI React and wondering what is the difference between IGR and IGC components.

Does IGR means - Ignite UI for React and it is library for React components ?

And IGC - Ignite UI for JavaScript ? Which can be used for Angular but also supports React applications ?

For example in the samples for the Dock Manager (React Dock Manager | Layout Controls | Infragistics) there is link to IgrDockManager (IgrDockManager | Ignite UI for React (infragistics.com) but all of the examples refer to different IgcDockManager components.

Maybe there is a documentation which is describing it and I will be thankful to share it.

Regards,

Tihomir

  • 2680
    Verified Answer
    Offline posted

    Hi Tihomir,

    Thank you for posting to Infragistics Community!

    The “igc-“ prefix is used for components from our Igntite UI for Web Components library. These components are essentially custom elements that can be used in native HTML & JavaScript apps and more.

    Our “igc-“ components are related to the other framework-specific libraries like Ignite UI for React/Angular/Blazor as some of the components in them are built as wrappers around the web component, so that they can be easily integrated in the corresponding framework.

    Taking the IgcDockManager as an example, your observation is valid for the Angular Dock Manager - it is the same component and can be used in Angular. For instance, the Blazor Dock Manager, has its own class and tag names (IgbDockManager, indicating Ignite UI for Blazor), still it is the same web component.

    This is valid for the greater part of the components from the React and Blazor suites. Ignite UI for Angular, on the other hand is the most mature among the web libraries, and most of the components are framework-specific.

    These libraries are under active development and new components are being added. One of the main goals is that the components across them share common behavior and looks, while addressing different platforms.

    If you have any other questions on the matter, do not hesitate to reach out to us.

    Best regards,
    Bozhidara Pachilova
    Software Developer