Scripts in your Word Press projects
Inserting scripts in your Word Press projects the proper way.
Sometimes you need to to enhance you WP project capabilities (plugins, themes, widgets, whatever), and to do so you need to add some scripts to your WP projects, either your own scripts or someone else’s. There are several ways to do this, and most of them are wrong.
This is a post excerpted from the Word Press Codex explaining how to do it.
Also there is a list with the default script libraries included with your Word Press installation, that you don’t need to include, just call whenever you need!
Cool ah!?
Semantic meaningful names in html elements.
“When coding a webpage layout, one tends to organize the html elements, naming them by their present location or purpose. Ignoring that, in the future, that organization can make no sense at all.”
Lets say you’re coding a three column layout with a header and a footer. You will use two columns as sidebars and the third as the central to hold the content.
Naturally you would name your columns with some semantic significant names, like “Left Column”, “Central Column”, “Right Column”, “Header” or “Footer. Probably something like that, right?
Ok, fair enough, these “location” names will definitely help you to organize your content trough the layout development. But what will happen if a couple of months later you decide to refresh your layout and move things around?
Word Press Role dependent admin-menus
Sometimes we need to give different tasks to different admin-users in our word-press blogs, in order to do so, we need to have some way to give them what we want, and just that. The safest way to do it is the WYSIWYG way, “they will only get what they see”.
This means you will only show them the menus or options they are supposed to act upon. We can achieve this by means of the Word Press roles “user level capabilities”, as was described in the previous article (“Word Press roles and capabilities“), and that will here be put to practice.
Word Press Roles and Capabilities
There are pre determined admin-roles in every word press installation.
This means every registered user can have a specific role, with specific capabilities within the blog.
This capabilities, relate to access levels, and are granted by the blog’s administrators.
This doesn’t mean that a user can’t perform someone-else’s task, it just means it will only be able to do a determined number of tasks, allowed by his user level.
“Every user with an access level can do everything his access level allows, plus all the capabilities of the user levels bellow.”
The Word Press roles and Capabilities hierarchy will be described in this article, along with the allowed admin-tasks for each level or role.
Adobe Unveils AIR on Mobile Device
*BARCELONA, Spain. — Feb. 15, 2010* *—* At Mobile World Congress™ 2010, Adobe Systems Incorporated today announced advancements to the Adobe®Flash® Platform including the unveiling of Adobe® AIR® on mobile devices, a consistent runtime for standalone applications to come out othe Open Screen Project™, an industry-wide initiative led by Adobe that has grown to close to 70 ecosystem partners. With support for the Android™ platform expected in 2010, AIR provides developers with a feature-rich environment for delivering rich applications outside the mobile browser and across multiple operating systems via mobile marketplaces and app stores. AIR leverages mobile specific features from Flash® Player 10.1, is optimized for high performance on mobile screens and designed to take advantage of native device capabilities for a richer and more immersive user experience.