Html + css are very nice way of building ui. Despite this why librocket or rmlui are not used widely? Are there any drawbacks of using html + css (librocket or rmlui) that people still go with wxwidgets etc.
Related
I'm using react, with bootstrap, and less. I was just wondering whether it was a better practice to use <center className="text-center"> when centering text for accessibility, or if I was better off just sticking with <div className="text-center>. Or does it even make a difference?
It makes no difference for accessibility, but it's a bad idea for many other reasons, and depending on the doctype you use, might even violate WCAG SC 4.1.1.
Don't use deprecated presentational HTML tags if you can avoid it. And you can, with CSS and style attributes. <center> is completely obsolete in the 21st century.
Should I use the <center> tag?
Yes, but only if you're specifically targeting Netscape Navigator (before version 2.0).
Latest HTML3.2 references said that:
CENTER was introduced by Netscape before they added support for the HTML 3.0 DIV element. It is retained in HTML 3.2 on account of its widespread deployment.
Otherwise, no ... as it will be deprecated in 1997.
$scope.barChartData.labels.push(moment(currentDate).format("YYYY-MM-DD") + "
$filter('translate')('To')" + moment(currentDate).add(4, 'days').format("YYYY-MM-DD"));
trying to translate "To" word
Reviewing this 2 lines, i found that you are using lib chart.js
for generating chart in angularjs app. And it create a svg based on data provided. So you need to again reload that svg in html with the same process of creating svg so that it is use translation based on language selection at that time.
Let me know if this solves the issue.
I would need to add an autocomplete chips component in our Angular 1.6 application. We are using Typescript, Webpack 2. As we are already using angular-ui-bootstrap, we do not want to introduce also angular-material in order to avoid style conflicts. However the wished result is exactly what material chips provide.
Is there a directive or component that i can use in my case? I found this library but it runs endless exceptions when I import it.
unfortunately I could find only partial solutions with bootstrap typehead, but then I would need to implement all the "chips" part, making me think of re-inventing the wheel.
Stack Newb here. I have an identical problem as yours. Here's how I resolved this:
1. Resolve the ReferenceError: error is not defined within the angular-chips library
The library you used (angular-chips) wasn't designed with typescript in mind. So, you'll first need to resolve the following error ReferenceError: error is not defined by defining it for them in the line above with var error;. This should prepare angular-chips for your webpack useage.
The second issue you'll find is how to add your typeahead-template-url with webpack in the mix. Rather than referring to a separate html file, use an inline template as referenced here: Bootstrap-UI Typeahead display more than one property in results list?.
If you're lazy like me and don't want to follow that hyperlink, use this as example:
2. Template to be added before the <chips> tag:
<script type="text/ng-template" id="yourTemplate.html">
<a tabindex="-1">
<i ng-class="'icon-'+match.model.type"></i>
<span ng-bind-html-unsafe="match.model.title | typeaheadHighlight:query"></span>
</a>
</scrip>
3. Include template in your directive:
typeahead-template-url:"yourTemplate.html"
Worked like a charm for me.
I can see that this was an AngularUI discussion at one point...
I'm wondering if anyone else has implemented Angular directives that would allow me to replace traditional Bootstrap laden markup like this
<div class="container-fluid">
<div class="row-fluid">
<div class="span4 offset2">
</div>
</div>
</div>
with easier-to-read, element focused, markup similar to this
<container-fluid>
<row>
<column span4 offset2>
</column>
</row>
</container-fluid>
Seems like it would be easy enough to implement, which makes me think that someone else has done this already (or that it's not worth it for some reason (maybe there's a performance hit?))
Has anyone done this already already?
If not, are there reasons I shouldn't implement it myself?
There are several Angular+Bootstrap projects, the prominent ones are AngularStrap and UI Bootstrap, I'm quite sure you're already aware of them. Sure, they provide custom directives, but only for the things that require this (i.e. Bootstrap JS components).
Seems like it would be easy enough to implement, which makes me think
that someone else has done this already (or that it's not worth it for
some reason (maybe there's a performance hit?))
Besides unnecessary performance overhead it would considerably diminish the value of Bootstrap as frontend framework - something that has learning curve that you already passed.
There are some developments in that direction - e.g. angular-deckgrid, yet I'm not aware of any ambitious and comprehensive (web-oriented) framework like Bootstrap or Angular Material.
There would be more sense in tailoring custom syntax for yourself. You can take a look at ui-alias (a part of ui-tools). It is rigid in its current state, but it a good example of smart approach to directives. And could be easily extended to make the mapping of classes to attributes and elements a breeze.
I am starting with angular and I often see two different approaches of using a module:
<input autocomplete options="..."/>
And:
<autocomplete options="..."/>
I think the first one is a better options since it uses the native HTML tags.
Is there a reason, or advantage of using the second approach?
In my opinion the HTML code becomes quite strange ...