From a HTML perspective this is really bad practise. ntext-chevron.ĭynamic class on the card.icn-contextĭrawbacks of remapping glyphicons? Currently the only way to get a glyphicon into mendix (that is not in a default widget) is by creating a link, removing the text and selecting an icon. Specific-context only affects itself, for instance, a container with the class. Top-level context affects itself and all the underlying elements, such as a card with the class. Usually, when done manually there will be a class called “context-X”, this way all developers know that certain elements will be changed due to the context that is given.Ĭontext can also be given on different “levels”. This section is split into 2 parts: - Context mapping - Glyphicon remapping Context MappingĬontext mapping is a methodology that can communicate context to the design system, and to the user.īasic context states are already supported by the HTML, like hover/focus states, other states are default in Mendix (like the selected state in a list-view), and other forms of context are often too specific or abstract and must be set manually.ĭynamic classes are a great way to set context based on when specific conditions are met. What is Icon mapping? In short, icon mapping is telling the browser that if it sees a certain class, it needs to show a certain icon. SVG’s can contain malicious scripts if downloaded from untrustworthy sources. Renders nicely in different sizes.Ĭons Cant have hover states.
This is the worst way to implement an SVG because it makes it difficult to manipulate, recolor, or replace the icon. Inline SVG's can be loaded in through the HTML widget, and are sometimes hardcoded into widgets. There are some security issues here, because SVG's may contain malicious scripts, so be warned.
The great thing about this is that you are able to see the icon in MXSP9 and this helps developers get an idea of what icons are in their Mendix pages. In MXSP9 The second way to load them in is through MXSP9 as you would an image. This also allows you to easily change an icon in one location and it changes everywhere in your project.
They can easily be mapped to the “brand-logo” class when named correctly. This is great when you have things like company logos. SASS/CSS The first and most common way for front-enders to implement is to load in icons through the SASS. The tricky thing about SVG’s is that they can be loaded into a Mendix app in 3 different ways (SASS/CSS, in MXSP9 & inline). The main reason to use SVG’s is to display images that contain multiple colors such as illustrations, company logos, emojis, or stickers.
0 kommentar(er)
