Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs











More recommended blogs »

Here are posterous posts filed under software...

nataliav says...

Following the instructions on this article and downloading the files from this site, I installed Google OS. 

Starting

Login with a Google Account is a good concept, because you don't need one more extra password and you're already logged in Google. On the other hand. I had personal and business accounts, so I need to be able to login at different websites with different credentials, I don't think this will be possible without restarting. 

The Operating System

It's just a browser! There are 2 icons, a battery indicator and an option to turn in/off the Wi-Fi, and nothing more. There's a big icon that apparently is a menu, but nothing happens, so we're going to be patient and wait till next year to fully test the OS.  

The OS concept

Google's OS is the first OS with a concept behind, accessing Internet very fast (7 seconds). As a graphic designer, I can't give up all the desktop software, but I think it's a good idea for some people. Way too minimal maybe. 

At this stage, I've seen a more appealing Linux version for netbooks, but it's nice to have more Open Source options.

Filed under: Software

danshafer says...

It appears from this article on Ars Techica today that Apple's widely publicized and uniformly hated iPhone AppStore policies and management are beginning to catch up with the snazzy company. A couple of key developers have publicly announced that they will no longer develop apps for the Apple smartphone platform due not to the market but to the channel. This is a ridiculously untenable situation for Apple but the company has passed up numerous opportunities to do the right thing by its developers and has turned a blind eye and a deaf ear to their legitimate complaints.

Arbitrary rejections of software submissions based on ill-considered and poorly documented reasoning by an apparently largely bureaucratic neophyte group of screeners has frutstrated dozens if not hundreds of iPhone developers. While it is hard to know whether the underlying policies on which rejection is based are sound and logical or just anti-competitive, it is clear that both the process and communication with developers are deeply flawed.

Apple needs to fix this. Now. It is only a matter of time before this attitude -- on the parts of both Apple and the developer community -- causes Mac developers to begin to reconsider their commitment to Apple platforms and technologies. And without that particular flavor of loyalty, Apple oculd be in big trouble, fast.

Filed under: Software

http://www.smashingmagazine.com/

 

Buttons, whatever their purpose, are important design elements. They could be the end point of a Web form or a call to action. Designers have many reasons to style buttons, including to make them more attractive and to enhance usability. One of the most important reasons, though, is that standard buttons can easily be missed by users because they often look similar to elements in their operating system. Here, we present you several techniques and tutorials to help you learn how to style buttons using CSS. We’ll also address usability.

Links vs. buttons

Before we explain how to style buttons, let’s clear up a common misconception: buttons are not links. The main purpose of a link is to navigate between pages and views, whereas buttons allow you to perform an action (such as submit a form).

In one of his articles, Jakob Nielsen writes about command links, which are a blend of links and buttons. But he recommended that command links be limited to actions with minor consequences and to secondary commands. To learn more about primary and secondary commands (and actions), check out Primary and Secondary Actions in Web Forms by Luke Wroblewski. To learn more about the differences between links and buttons, read Creating Usable Links and Buttons at UXBooth.

Basic Styling

The simplest way to style links and buttons is to add background color, padding and borders. Below are examples of the code for the link, button and input (”Submit”) elements.

Sample button
<button class="button" id="save">Sample button</button>
<input class="button" value="Sample Button" type="submit" />
.button {
padding:5px;
background-color: #dcdcdc;
border: 1px solid #666;
color:#000;
text-decoration:none;
}

This simple code minimizes the visual differences between links and buttons. And here are the rendered examples of the code above:

Different Buttons in Designing CSS Buttons: Techniques and Resources

The important thing to note is that these three elements render differently with the same CSS. So, you should style these elements carefully to ensure consistency across your website or application.

Images

Adding images to buttons can make the buttons more obvious. Sometimes the image itself clearly communicates the purpose of a button; e.g. a loupe icon for searching or a floppy disk icon for saving. The easiest way to add an image to a button is to use a background image and then position it accordingly. Below are our examples with a checkmark icon.

.button {
padding: 5px 5px 5px 25px;
border: 1px solid #666;
color:#000;
text-decoration:none;
background: #dcdcdc url(icon.png) no-repeat scroll 5px center;
}

Different Buttons2 in Designing CSS Buttons: Techniques and Resources

Button States

In addition to their default state, buttons and links can have two other states: hover and active (i.e. pressed). It is important that buttons appear different in different states so that users are clear about what is happening. Any element in a hover state can be styled by invoking the :hover CSS pseudo-class.

a:hover {
color:#f00;
}

Though very important, the active state is rarely implemented on websites. By showing this state, you ensure that your buttons are responsive and send a visual cue to users that a button has been pressed. This is called isomorphic correspondence, and it is “the relationship between the appearance of a visual form and a comparable human behavior” (Luke Wroblewski, Site-Seeing). The article Pressed Button State With CSS elaborates on the importance of the active state.

a:active {
color:#f00;
}

There is yet one more state, one that is seen when navigating with the keyboard: the focus state. When the user navigates to a button using the Tab key, it should change appearance, preferably to have the same appearance as the hover state.

a:focus {
color:#f00;
}

The examples below shows the common way to style button states. The hover state is a bit lighter than the normal state, while the active state has an inverted gradient that simulates a pressed action. Although you need not limit yourself to this styling, it is a good place to start.

Button States in Designing CSS Buttons: Techniques and Resources

We should talk about how to handle the outline property for the :active and :focus states. Handling this property well is important for the experience of users who employ the keyboard as well as the mouse. In the article Better CSS Outline Suppression,” Patrick Lauke shows how buttons and links behave in different combinations of states and explains why the outline property should be invoked only with the :active state.

Apple in Designing CSS Buttons: Techniques and Resources

The blue “Buy now” button on Apple.com has a slightly lighter background for the hover state and an inset style for active state. Even the main navigation button on Apple’s website implements all three states.

Tearoundapp in Designing CSS Buttons: Techniques and Resources

Although it doesn’t implement the active state, this fancy button on Tea Round has a nice fading effect on hover.

Uxbooth Button in Designing CSS Buttons: Techniques and Resources

The “Read more” button on UX Booth turns green on hover and moves down one pixel in the active state, which simulates the effect of pressing a button.

Useful Reading

The article Rediscovering the Button Element shows the differences between links and buttons and explains how to style buttons easily.

Rediscover Button in Designing CSS Buttons: Techniques and Resources

Styling Form Buttons covers the basics of styling buttons, with many examples.

Tyssendesign in Designing CSS Buttons: Techniques and Resources

Beautiful CSS Buttons With Icon Set shows how to style buttons using background images. Although not scalable, these are really nice buttons.

Buttonnice in Designing CSS Buttons: Techniques and Resources

Recreating the Button is a very good article that explains how Google ended up with the buttons that it uses on majority of its websites.

Stopdesign in Designing CSS Buttons: Techniques and Resources

Scalable CSS Buttons Using PNG and Background Colors explains how to create really stunning buttons for all states. Although it uses jQuery, it degrades gracefully if JavaScript is turned off.

Monc in Designing CSS Buttons: Techniques and Resources

Sliding Doors: Flexible Buttons

One important consideration needs to be made when styling buttons: scalability. Scalability in this context means being able to stretch a button to fit text and to reuse images. Unless you want to create a different image for each button, consider the “sliding doors” technique. This technique enables you to create scalable, rich buttons.

Sliding Doors in Designing CSS Buttons: Techniques and Resources

The principle involves making two images slide over each other, allowing the button to stretch to the content. Usually, this is done by nesting a span element within a link. As shown in the image above, each element has its own background image, allowing for the sliding effect. The two code snippets below show the structure and basic styling for this effect.

Typical sliding doors button
a {
background: transparent url('button_right.png') no-repeat scroll top right;
display: block;
float: left;
/* padding, margins and other styles here */
}
a span {
background: transparent url('button_left.png') no-repeat;
display: block;
/* padding, margins and other styles here */
}

The advantages of this technique are that it:

  • Is an easy way to create visually rich buttons;
  • Ensures accessibility, flexibility and scalability;
  • Requires no JavaScript;
  • Works in all major browsers.

Useful Reading

The “Sliding Doors of CSS” article on A List Apart (part 1 and part 2) covers the basics of this technique. Although a bit old, these articles are a must-read for every Web developer.

Alistapart in Designing CSS Buttons: Techniques and Resources

Also a bit old, Creating Bulletproof Graphic Link Buttons With CSS is an excellent article that shows how to create bulletproof, resizable, shrunk-wrap buttons. Also a must-read.

456bereast in Designing CSS Buttons: Techniques and Resources

Filament Group has a variety of excellent articles and tutorials. Its second article on CSS buttons, Styling the Button Element With CSS Sliding Doors,” explains how to create buttons by combining techniques. Although it doesn’t support the active state, it can be easily extended.

Filament in Designing CSS Buttons: Techniques and Resources

How to Make Sexy Buttons With CSS is one of the best and simplest explanations of the sliding doors technique. It also contains a little fix for the active state in Internet Explorer.

Oscaralexander in Designing CSS Buttons: Techniques and Resources

If you want Wii-like buttons, the article Simple Round CSS Links (Wii Buttons) provides all the necessary resources and explanation on how to style them.

Wii in Designing CSS Buttons: Techniques and Resources

The common way to achieve the CSS sliding doors technique is to use two images. However, the article CSS Sliding Door Using Only One Image shows that it is possible to achieve the same effect with only one image.

Kailoon in Designing CSS Buttons: Techniques and Resources

CSS Oval Buttons and CSS Square Buttons from Dynamic Drive are two other articles that show the effectiveness of CSS sliding doors.

Dynamicdrive in Designing CSS Buttons: Techniques and Resources

CSS Sprites: One Image, Not Many

With CSS Sprites, one image file contains multiple graphic elements, usually laid out in a grid. By tiling the image, we show only one Sprite at a time. For buttons, we can include graphics for all three states in a single file. This technique is efficient because it requires fewer resources and the page loads faster. We all know that many requests to the server for multiple small resources can take a long time. This is why CSS Sprites are so handy. They significantly reduces round-trips to the server. They are so powerful that some developers use CSS Sprites for all their graphics. The Holy Sprites round-up on CSS Tricks offers some very creative solutions.

The example below shows the simplest use of CSS Sprites. A single image contains graphics for all three button states. By adjusting the background-position property, we define the exact position of the background image we want. The image we’re choosing to show here corresponds to a background position of top: -30px and left: 0.

Sprites in Designing CSS Buttons: Techniques and Resources

a {
background: white url(buttons.png) 0px 0px no-repeat;
}
a:hover {
background-position: -30px 0px;
}
a:active {
background-position: -60px 0px;
}

For general information and resources on CSS Sprites, check out The Mystery of CSS Sprites: Techniques, Tools and Tutorials.”

Useful Reading

In this easy-to-follow tutorial How to Build a Simple Button with CSS Image Sprites,” Chris Spooner explains how to create a CSS Sprites image in Photoshop and use it with CSS.

Line25 in Designing CSS Buttons: Techniques and Resources

Transforming the Button Element With Sliding Doors and Image Sprites shows how to enrich a button element with a combination of sliding doors and image Sprites. It implements the active state in a very interesting way, not by using different images or colors but rather by positioning.

CSS 3: Buttons Of The Future

CSS 3 allows us to create visually rich buttons with just a few lines of code. So far, this is the easiest way to create buttons. The downside of CSS 3 is that it is currently supported only by Firefox and Safari. The upside is that buttons styled with CSS 3 degrade gracefully in unsupported browsers. By using the browser-specific properties -moz-border-radius (for Firefox) or -webkit-border-radius (for Safari), you can define the radius of corners. Here are a few examples of what can be done with the border radius property.

Css3 Rounded in Designing CSS Buttons: Techniques and Resources

For better results, you can combine CSS 3 rounded corners with the background image property. The example below shows a typical button with a gradient image, the first without rounded corners, and the second with.

Rounded Corners in Designing CSS Buttons: Techniques and Resources

Compared to sliding doors, this technique is far simpler. However, if you want to maintain visual consistency across all browsers, then use sliding doors, because it works in all major browsers, including IE6. To learn more about the capabilities of CSS 3, read CSS 3 Exciting Functions and Features: 30+ Useful Tutorials.” And here are a few good tutorials on styling buttons with CSS 3 features.

Useful Reading

Super Awesome Buttons With CSS 3 and RGBA shows the power of CSS 3 with rounded corners, Mozilla box shadows and RGBA, which is a color mode that adds alpha-blending to your favorite CSS properties. This is one of the best examples of CSS 3 buttons.

Zurb in Designing CSS Buttons: Techniques and Resources

Create a CSS 3 Button That Degrades Nicely is a good example of CSS 3 buttons that degrade gracefully in browsers that don’t support CSS 3.

Stylizedweb in Designing CSS Buttons: Techniques and Resources

Creating buttons without Images Using CSS 3 explains the drawbacks of using images for buttons and shows several options for creating image-less CSS 3 buttons.

Opera in Designing CSS Buttons: Techniques and Resources

Emulating Google-Syle Buttons Using CSS 3 & dd_roundies JS is a fantastic article that shows how to create Google-like buttons. It goes even further and shows how to create the button pillbox commonly seen on Google pages.

Instant Tools: Are They Useful?

Tools exist for creating buttons, such as Easy Button and Menu Maker and My Cool Button, and for creating CSS Sprites, such as CSS Sprite Generator, but the question is, do they really help you create buttons that fit your needs. Although they are configurable and easy to use, your creativity and control over the results are limited, which makes for average-looking buttons. Using one-size-fits-all buttons is not a good idea.

The solution is to use Photoshop (or a free alternative) and the proven techniques described in this article. If you are a beginner with Photoshop, here are several excellent tutorials on creating amazing buttons.

If you don’t know where to start, iPhone-Like Button in Photoshop is the perfect choice. In only 10 to 15 minutes, you will be able to create the kind of buttons seen on the iPhone.

Iphone Button in Designing CSS Buttons: Techniques and Resources

How to Create a Slick and Clean Button in Photoshop is a very detailed tutorial that guides you through 30 simple steps and helps you learn the Photoshop basics. In addition, the article explains how to use these graphics in combination with HTML and CSS to create fully functional CSS buttons.

Sixrevisions in Designing CSS Buttons: Techniques and Resources

Photoshop Button Maker is a fantastic tutorial from PSD Tuts that shows how to create fancy oval buttons (or badges).

Psdtuts in Designing CSS Buttons: Techniques and Resources

Buttons And Usability: Instead Of Conclusion

The techniques described above can help you create stunning buttons. However, because they play a critical role in website usability, the buttons should meet some key principles:

  1. First consider the labeling. Always label buttons with the name of the action that the user is performing. And always make it a verb. A common mistake is to label buttons “Go” for various actions such as searching, sending email and saving. Labels should also be short and to the point; no need to clutter the user interface.
  2. As mentioned, include all button states (default, hover, active) to provide clear visual cues to the user as to what is happening. Button outlines should remain in the active state only.
  3. Clearly distinguish between primary and secondary actions. The most important action should be the most prominent. This is usually done by giving primary and secondary actions different colors.
  4. Pay close attention to consistency. Buttons should be consistent throughout a Web application, both visually and behavior-wise. Use CSS sliding doors for reused buttons or CSS 3 rounded corners to maintain consistency.
  5. Though obvious, we should note that the entire button area should be clickable.

The articles below provide even more usability guidelines and best practices for designing buttons.

Make Complete Button Surface Active and Enhance Usability is an in-depth article that shows mistakes in button design and that explains why the entire button surface should be clickable.

Uxpassion in Designing CSS Buttons: Techniques and Resources

Creating Usable Links and Buttons explains why users expect buttons sometimes and links other times. It also shows how to choose between the two elements.

Uxbooth in Designing CSS Buttons: Techniques and Resources

How to Design Buttons to Help Improve Usability explains some usability principles that should be considered when designing buttons. It covers the basics of icon usage, appearance, behavior, hierarchy and consistency.

(al)

Filed under: software

frangarnes says...

Llevo algo más de un mes con mi nuevo móvil, un HTC Hero, que es uno de los primeros modelos de teléfonos móviles (el tercero en comercializarse en España) que ha incluido el sistema operativo para móviles Android de Google. Pues bien, durante este tiempo he estado probando diversas aplicaciones del Android Market, que es la tienda de aplicaciones oficial del sistema Android. Hay muchas aplicaciones que valen la pena dentro del Market, pero en esta ocasión me gustaría hacer una pequeña reseña acerca de una en concreto que me parece muy interesante: chompSMS.

¿Qué es chompSMS?
Se trata de una aplicación para editar, leer y enviar mensajes cortos SMS en teléfonos móviles Android.

Ventajas respecto a la aplicación nativa
  • La principal ventaja que tiene chompSMS frente a la aplicación nativa de mensajería SMS me parece, sin duda alguna, el doble sistema de envío de mensajes que emplea. Por un lado, permite enviar mensajes de manera tradicional, por medio de tu operadora. Por otro, existe un método alternativo: mediante la propia red de chompSMS. Esta red envía los mensajes por internet (si estás conectado a una red WiFi o a la red móvil de tu operadora) a un precio de 8 céntimos por mensaje (tanto para mensajes nacionales como internacionales). Además, la persona que reciba tu mensaje enviado de esta manera, lo recibe tal y como si lo hubieras mandado mediante tu operadora (le aparecerá tu número de teléfono como emisor del mensaje). Puedes comprar créditos para mandar mensajes mediante la red chompSMS desde la propia aplicación o desde la página web de la misma. Para probar este sistema de envío, compré 50 créditos (que equivalen a 50 SMS) a un precio de 4€ (permiten además el pago mediante PayPal). Por mi experiencia hasta ahora, puedo afirmar que los mensajes llegan al instante. Ahora, siempre que tengo cobertura WiFi, mando los mensajes por este método; paso de regalarle el dinero a mi operadora.
  • Posee una mejor (y más bonita) interfaz de usuario. Por ejemplo, en la lista de mensajes que aparece al iniciar la aplicación, puedes ver la foto de la persona a la que mandas (o que te manda) el mensaje. El intercambio de mensajes con otras personas (conversaciones) se muestra con bocadillos como si de un cómic se tratara (ver cuarta imagen). Mencionar también que es posible personalizar el aspecto de la aplicación a tu gusto (ver tercera imagen).
  • Además de las funciones comentadas anteriormente, tiene tiene otras opciones, muy curiosas algunas de ellas, como leer a viva voz los mensajes que te envían (mediante las librerías Text-To-Speech); aunque eso no lo he probado aún (esperando al nuevo firmware). También tiene una lista negra, muy útil para evitar los SMS de pesados o publicidad no deseada. Otras funciones interesantes son el atajo para editar un mensaje nuevo sin abrir la aplicación (manteniendo pulsado el botón de búsqueda del teclado), o la opción de activar la respuesta rápida al recibir un mensaje.
  • Por último, comentar que para mí (que soy un anti-lenguaje SMS hasta en los propios SMS) es esencial que una aplicación de este tipo incluya algo tan sencillo como un contador que marque el número de caracteres que hayas introducido en el mensaje que estés editando. Y por increíble que parezca, al menos en la versión 1.5 de Android, la nativa no lo incluye. El editor de chompSMS (ver segunda imagen) cuenta los caracteres y, además, cuando introduces caracteres especiales también cambia automáticamente el formato de codificación de texto (el límite de caracteres pasa a ser 70 en vez de 160).
Desventajas respecto a la aplicación nativa
  • No es posible editar ni enviar mensajes MMS (aunque sí los puede leer). Es una característica que está en desarrollo.
  • No tiene widget para el escritorio. Aunque la nativa creo que tampoco, ya que el widget que tengo en mi móvil para la aplicación nativa parece ser del fabricante (HTC) y no de Android.
  • La aplicación está en inglés y no parece que por el momento la vayan a traducir a otros idiomas. Pero si sabes algo de inglés, tampoco es problema.
¿Dónde descargar la aplicación?
chompSMS es una aplicación gratuita y la puedes encontrar en el Android Market de tu teléfono, introduciendo "chompsms" en la búsqueda. Si tienes instalada en tu teléfono una aplicación capaz de leer QR codes, también puedes encontrar chompSMS leyendo el QR code que puedes ver al final (última imagen).

chompSMS en otros móviles
chompSMS es exclusivo de Android. Sin embargo, esta aplicación tiene una hermana en iPhone, llamada biteSMS. Ambas han sido creadas por los mismos desarrolladores y tienen características totalmente análogas.

Más información
Para más información, ir a la página oficial de la aplicación (en inglés): www.chompsms.com

credits: Logo of pic#1 is property of chompSMS. Screenshoots (pic#2, pic#3 and pic#4) and QR code (pic#5) taken from androlib. This review has been written by me (Fran Garnés) about version 2.14 of chompSMS to take part in chompSMS' promotion [ PROMOTION CODE: PNSXCZ ].

         

Filed under: software

Jamal says...

 

I’d pay good money for this! that’s if it existed. I had a HP palm like thing & an XDA (Still got them somewhere rotting in the back of a draw) I always liked the organiser home screen feature on them and I used it all the time, it helped be more efficient.

 

The iphone is an excellent phone, if it does get this feature in the near future, it’ll be another notch on it massive belt. So Steve if your reading this – take a note! We want this!    

 

Via: teehan+lax

Filed under: Software

mlevit says...

Introduction

Open source doesn't just mean access to the source code.
The distribution terms of open-source software must comply with the following criteria:
1. Free Redistribution
The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.
2. Source Code
The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost preferably, downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed.
3. Derived Works
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
4. Integrity of The Author's Source Code
The license may restrict source-code from being distributed in modified form only if the license allows the distribution of "patch files" with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software.
5. No Discrimination Against Persons or Groups
The license must not discriminate against any person or group of persons.
6. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
7. Distribution of License
The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.
8. License Must Not Be Specific to a Product
The rights attached to the program must not depend on the program's being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution.
9. License Must Not Restrict Other Software
The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software.
10. License Must Be Technology-Neutral
No provision of the license may be predicated on any individual technology or style of interface.

Open Source Initiative, http://opensource.org/docs/osd

Interesting read. Never actually knew the exact definition of Open Source but Wiki knows all :)

Thanks

Filed under: software

squidlord says...

You know, I love the new Blood Bowl team they've added; I'm truly torn between venturing into the online leagues with my trusty Lizardmen or the new hotness, the Dark Elves who play to my brutal, heavily running-slanted play-style. I love the Witch Elf brutality and the Dark Elf Blitzer's Block ability baked right in ... and you just know I do love running an Assassin-heavy team.

So what do I get when I roll out to skim the forums?

MySQL is full of evil.

I wonder if they had a recent injection-exploit attempt, causing it to overflow?

(Really, I needed an excuse to create another Failure image. Duh.)

Filed under: software

x0x04pat says...

From the editor's blog
http://omz-software.com/blog/finally-newsstand-22-is-available

About 2.0 version
http://x0x04pat.posterous.com/newsstand-20-my-favorite-rss-reader-for-iphon

Filed under: software

Filed under: software

Mike says...

Releasing the Chromium OS open source project

In July we announced that we were working on Google Chrome OS, an open source operating system for people who spend most of their time on the web.

Today we are open-sourcing the project as Chromium OS. We are doing this early, a year before Google Chrome OS will be ready for users, because we are eager to engage with partners, the open source community and developers. As with the Google Chrome browser, development will be done in the open from this point on. This means the code is free, accessible to anyone and open for contributions.......more

Filed under: Software