PHP in the Enterprise [Infographic]


infographics4u.com

PHP is a general-purpose server-side scripting language originally designed for Web development to produce dynamic Web pages. It is one of the first developed server-side scripting languages to be embedded into an HTML source document rather than calling an external file to process data. This infographic is an attempt to readdress the balance and show how PHP is used in the enterprise.

 

Anuncios

7 plugins jQuery que te harán el trabajo más simple


 | http://bitelia.com

Sin duda alguna, jQuery cambió por completo la forma en que usamos -y aprovechamos-JavaScript, llevando a otro nivel la forma en que los usuarios interactuan con sitios y aplicaciones web. Si eres desarrollador web, seguramente ya te has aventurado a escribir código para dotar tu proyecto de alguna funcionalidad especial y te habrás dado cuenta que lograr algo realmente asombroso con jQuery no siempre es una tarea simple.

Muchas veces queremos resolver por nosotros mismos todos los problemas, y que todo el código en el proyecto sea de nuestra propia cosecha, sin embargo, hay ocasiones en las que no contamos con el tiempo suficiente y se hace necesario recurrir a código de terceros, y así, evitar reinventar la rueda.

Aunque existen miles de plugins de este tipo regados en Internet, he recogido estos 6 por su gran calidad y sus particulares características que, además de darle un toque extra de genialidad a tu proyecto, te harán el trabajo mucho más simple.

Adipoli


Adipoli permite aplicar diferentes efectos, de gran calidad, a las imágenes cuando se desplaza el puntero del ratón sobre ellas. Además de los -casi- 20 efectos y transiciones, ofrece múltiples opciones configurables cómo: opacidad, velocidad de animación, color de relleno, margenes, sombras y más.

blur.jsLeer más “7 plugins jQuery que te harán el trabajo más simple”

Useful Tools, Scripts, and Resources for Front-End Developers


By  | http://www.noupe.com

If you’re a front-end developer mostly focused on HTML, CSS, and JavaScript, then you’re probably always on the look out for ways to be more productive. In this post we’ll share sometools and other resources for front-end developers that you might find useful to include in your workflow.

Tools and Scripts and Resources, Oh My!

Font Stack Builder by Erin Lawrence

This font stack builder lets you select a font stack and will tell you, using percentages, how likely it is for the fonts to be present on users’ systems. It includes options for a number of different font category styles and summarizes how the different options size up for different operating systems (Mac, Windows, Linux). Very easy to use, and, best of all, it gives you the necessary CSS to copy and paste into your projects.

Font Stack Builder by Erin Lawrence

Browser Support by Paul D. Waite

This simple tool lets you type in the name of any CSS feature (including properties, selectors, at-rules, values, and more) and it will display a simple graphic-based chart that outlines browser support. The individual results’ pages even have links to test cases and the official specification for the selected feature.

Browser Support

CSS Hat

This looks like quite a revolutionary tool. Although it might disturb purists who prefer to code everything by hand, it certainly looks like an excellent productivity tool. In a nutshell, CSS Hat is a Photoshop plugin that converts layer styles in Photoshop to CSS3 code. The site embedsa video review and demonstration that shows the tool in action, so be sure to check that out. The plugin adds conversion support for gradients, opacity, shadows, inner/outer glow, rounded corners, and more. It’s not free, but for $19.99, if it does what they claim it does, it’s well worth it.

CSS Hat

WYSIHTML5 (…) Leer más “Useful Tools, Scripts, and Resources for Front-End Developers”

Gestores de contenido y SEO, matrimonio de conveniencia

Dentro de la importancia de los contenidos y la correcta gestión de estos a la hora de posicionar cualquier proyecto web en Internet, puede ser interesante ahondar en la relación de como los CMS o gestores de contenidos pueden establecer una excelente relación con las acciones seo encaminadas a posicionar en Internet cualquier web.

Pero vayamos por orden, en primer lugar, un buen CMS orientado a SEO deber permitir que llamemos a las urls de forma amigable. Este pues es uno de los factores iniciales. En esta línea Joomla, Drupal o Wordpress nos permite editar muy fácilmente estas y llamarlas (siempre en relación al contenido) como más nos convenga. CMS hay muchos y cada uno tiene su punto de interés, siempre va a ir en función de lo que queramos hacer con él. Ni que decir tiene que el CMS nos debe permitir siempre trabajar con CSS´s ya que el peso del sitio se reduce de forma drástica (la plantilla solo se carga una web en el equipo cliente y da más peso específico al contenido respecto del peso del código).


por Cayetano Torres

Dentro de la importancia de los contenidos y la correcta gestión de estos a la hora de posicionar cualquier proyecto web en Internet, puede ser interesante ahondar en la relación de como los CMS o gestores de contenidos pueden establecer una excelente relación con las acciones seo encaminadas a posicionar en Internet cualquier web.

Pero vayamos por orden, en primer lugar, un buen CMS orientado a SEO deber permitir que llamemos a las urls de forma amigable. Este pues es uno de los factores iniciales. En esta línea Joomla, Drupal o WordPress nos permite editar muy fácilmente estas y llamarlas (siempre en relación al contenido) como más nos convenga. CMS hay muchos y cada uno tiene su punto de interés, siempre va a ir en función de lo que queramos hacer con él. Ni que decir tiene que el CMS nos debe permitir siempre trabajar con CSS´s ya que el peso del sitio se reduce de forma drástica (la plantilla solo se carga una web en el equipo cliente y da más peso específico al contenido respecto del peso del código). Leer más “Gestores de contenido y SEO, matrimonio de conveniencia”

Commonly Confused Bits Of jQuery

* By Andy Croxall

The explosion of JavaScript libraries and frameworks such as jQuery onto the front-end development scene has opened up the power of JavaScript to a far wider audience than ever before. It was born of the need — expressed by a crescendo of screaming by front-end developers who were fast running out of hair to pull out — to improve JavaScript’s somewhat primitive API, to make up for the lack of unified implementation across browsers and to make it more compact in its syntax.

All of which means that, unless you have some odd grudge against jQuery, those days are gone — you can actually get stuff done now. A script to find all links of a certain CSS class in a document and bind an event to them now requires one line of code, not 10. To power this, jQuery brings to the party its own API, featuring a host of functions, methods and syntactical peculiarities. Some are confused or appear similar to each other but actually differ in some way. This article clears up some of these confusions.

[Offtopic: by the way, have you already visited Smashing Magazine’s Facebook fan page? Join the community for a stream of useful resources, updates and giveaways!]
1. .parent() vs. .parents() vs. .closest()

All three of these methods are concerned with navigating upwards through the DOM, above the element(s) returned by the selector, and matching certain parents or, beyond them, ancestors. But they differ from each other in ways that make them each uniquely useful.
parent(selector)

This simply matches the one immediate parent of the element(s). It can take a selector, which can be useful for matching the parent only in certain situations. For example:
view source
print?
1 $(‘span#mySpan’).parent().css(‘background’, ‘#f90’);
2 $(‘p’).parent(‘div.large’).css(‘background’, ‘#f90’);

The first line gives the parent of #mySpan. The second does the same for parents of all

tags, provided that the parent is a div and has the class large.

Tip: the ability to limit the reach of methods like the one in the second line is a common feature of jQuery. The majority of DOM manipulation methods allow you to specify a selector in this way, so it’s not unique to parent().



The explosion of JavaScript libraries and frameworks such as jQuery onto the front-end development scene has opened up the power of JavaScript to a far wider audience than ever before. It was born of the need — expressed by a crescendo of screaming by front-end developers who were fast running out of hair to pull out — to improve JavaScript’s somewhat primitive API, to make up for the lack of unified implementation across browsers and to make it more compact in its syntax.

All of which means that, unless you have some odd grudge against jQuery, those days are gone — you can actually get stuff done now. A script to find all links of a certain CSS class in a document and bind an event to them now requires one line of code, not 10. To power this, jQuery brings to the party its own API, featuring a host of functions, methods and syntactical peculiarities. Some are confused or appear similar to each other but actually differ in some way. This article clears up some of these confusions.

[Offtopic: by the way, have you already visited Smashing Magazine’s Facebook fan page? Join the community for a stream of useful resources, updates and giveaways!]

1. .parent() vs. .parents() vs. .closest()

All three of these methods are concerned with navigating upwards through the DOM, above the element(s) returned by the selector, and matching certain parents or, beyond them, ancestors. But they differ from each other in ways that make them each uniquely useful.

parent(selector)

This simply matches the one immediate parent of the element(s). It can take a selector, which can be useful for matching the parent only in certain situations. For example:

1 $('span#mySpan').parent().css('background', '#f90');
2 $('p').parent('div.large').css('background', '#f90');

The first line gives the parent of #mySpan. The second does the same for parents of all <p> tags, provided that the parent is a div and has the class large.

Tip: the ability to limit the reach of methods like the one in the second line is a common feature of jQuery. The majority of DOM manipulation methods allow you to specify a selector in this way, so it’s not unique to parent(). Leer más “Commonly Confused Bits Of jQuery”