Source: A Pen by Bennett Feely on CodePen.
- Open the Bookmark Manager and export your bookmarks;
- Open the exported html file in your favorite editor and look for the bookmarklet you want a favicon applied to;
- Convert the 16x16 px (or greater) favicon you want to use into the BASE64 format (I used Base64 Image Encoder);
- Now you can add the favicon via adding the
ICON="data:image/insert-your-base64-image-code-here"
attribute in the link; - Save the file and import it in the bookmark manager.
Done! If the favicon doesn’t show up, try clicking on the bookmarklet. Afterwards the changes should stick and you can delete the imported bookmarks folder. If you have sync activated the favicons on your bookmarklets will also show up on your other PC, Mac, smartphone etc.
<!-- Add some tags here, head, title etc and your references --> | |
<p> | |
<label>Codificada:</label> | |
<span id='1'></span> | |
</p> | |
<p> | |
<label>Limpa:</label> | |
<span id='2'></span> | |
</p> |
var $element = $('div#test'); | |
// You can examine all of the events attached to an element | |
$._data($element.get(0), 'events'); | |
// Remove namespaced events added using .on() | |
$element.off('pluginNamespace'); | |
// Remove namespaced events added using .bind() | |
$element.unbind('.pluginNamespace'); |
/* | |
* HOW TO WRITE AN INFORMATION IN THE V$SESSION TABLE USING THE | |
* CURRENT USER SESSION IN ORACLE DATABASE. | |
*/ | |
-- EXAMPLE OF RECORDING INFORMATION | |
BEGIN | |
DBMS_APPLICATION_INFO.SET_MODULE('ANY_ID', 'YOUR INFO HERE'); | |
END; |
Quando usado o mapeamento por Data Annotations, as propriedades das entidades POCO (Plain Old CLR Object) são decoradas com atributos, fazendo necessário referência externa, além da “sujeira” dos metadados.
public int ClienteId {get; set;}
[MaxLength(150), Required]
public string Nome { get; set; }
No Fluent Api usamos métodos encadeados fora das entidades, as mesmas permanecem “limpas”, porém precisamos escrever mais código.
I've faced this need several times over the years:
So, we've got our dashboard, and we need to show customer/user/whatever data in a table so we can search, sort, filter, all that good stuff...
Sound familiar? Well, there are a few ways we could approach this. To start with, we could put it all together by hand. Creating the table structure and binding each individual row from a data source. But that's loads of work! What we need is some kind of helper or plugin to make our lives easier. Something that will turn our ordinary table into a powerhouse of searchable goodness.
In ASP.NET MVC, there are several ways to validate the model data prior to saving the data into the data store.
- Validate the model data explicitly
- Implement the IValidateableObject interface
- Specify Data Annotations [Recommended]
Data Annotation is recommended because there are built-in Data Annotations in .NET Framework. You don’t have to implement your own validation logic, instead specifying the Validation Data Annotation that you need. The Data Annotations specified support both server-side & client-side validation. In case the built-in cannot fulfill your requirements, you can also implement your own Data Annotation.
Built-in Data Annotations
Before we jump into the code, it is important to understand that progressive web apps have the following characteristics:
- Progressive. By definition, a progressive web app must work on any device and enhance progressively, taking advantage of any features available on the user’s device and browser.
- Discoverable. Because a progressive web app is a website, it should be discoverable in search engines. This is a major advantage over native applications, which still lag behind websites in searchability.
- Linkable. As another characteristic inherited from websites, a well-designed website should use the URI to indicate the current state of the application. This will enable the web app to retain or reload its state when the user bookmarks or shares the app’s URL.
- Responsive. A progressive web app’