Tamaño máximo de una URL

  • Autor: administrador
  • Archivado bajo: Otros
  • Fecha: May 29,2008

Del lado del cliente:

  • Internet Explorer: 2.083
  • Firefox: 65.536
  • Safari: 80.000
  • Opera: 190.000

Del lado del servidor:

  • Apache: 4.000
  • Microsoft Internet Information Server (IIS): 16.384
  • Perl HTTP::Daemon: 8.000

Baila el Chiki Chiki.. perrea perrea!! Cancion del verano!

  • Autor: administrador
  • Archivado bajo: Otros
  • Fecha: May 29,2008

JAVASCRIPT:

  1. ¡¡¡Teclea, teclea!!!

  2.  

  3. El javascripy mola mogollón,

  4. funciona en explorer y también en firefox.

  5.  

  6. Ponle javascripy a esa paginita,

  7. que el javascripy la deja muy bonita.

  8.  

  9. Abre ventanas,

  10. muestra mensajes,

  11. valida formularios,

  12. mi amol ya tu sabes!

  13.  

  14. Programan los seniors,

  15. Programan los juniors,

  16. Programa mi jefe con acentos en el function!

  17.  

  18. Y el javascripy se programa asi:

  19.  

  20. 1 - el tag <script>

  21. 2 - el function vars

  22. 3 - el alert-confirm

  23. 4 - el return trú

  24.  

  25. Programa el javascripy,

  26. Programa el javascripy,

  27. programan los heavys, también los frikis

  28. Programan en la offis, programan en la uni,

  29. Programan los fruittis y también los lunnis.

  30.  

  31. Programa Maradona esnifando una raya,

  32. y Juan Carlos le dice: ¿Porque no usas ajax?

  33.  

  34. En el formulario de un triste portal,

  35. pusieron javascripy y ya pudo validar

  36.  

  37. ¡¡¡Validar!! ¡¡Validar, validarr, validarrr!!!

  38.  

  39. Y el javascripy se programa asi:

  40.  

  41. 1 - el tag </script><script>

  42. 2 - el function vars

  43. 3 - el alert-confirm

  44. 4 - el return trú


Recursos para desarrolladores

  • Autor: administrador
  • Archivado bajo: Enlaces
  • Fecha: May 27,2008

http://www.devlisting.com/


Mini tutorial para crear un layout CSS

  • Autor: administrador
  • Archivado bajo: Css
  • Fecha: May 27,2008

One of the major benefits of CSS is the ability to control page layout without needing to use presentational markup. However, CSS layout has gained a rather undeserved reputation of being difficult, particularly among those new to the language. This is partly due to browser inconsistencies, but mostly due to a proliferation of different layout techniques available on the Web. It seems that every CSS author has their own technique for creating multicolumn layouts, and new CSS developers will often use a technique without really understanding how it works. This “black box” approach to CSS layout may get quick results, but ultimately stunts the developer’s understanding of the language.

All these CSS layout techniques rely on three basic concepts: positioning, floating, and margin manipulation. The different techniques really aren’t that different, and if you understand the core concepts, it is relatively easy to create your own layouts with little or no hassle.

In this chapter you will learn about

  • Horizontally centering a design on a page
  • Creating two- and three-column float-based layouts
  • Creating fixed-width, liquid, and elastic layouts
  • Making columns stretch to the full height of the available space

Centering a design

Long lines of text can be difficult and unpleasant to read. As modern monitors continue to grow in size, the issue of screen readability is becoming increasingly important. One way designers have attempted to tackle this problem is by centering their designs. Rather than spanning the full width of the screen, centered designs span only a portion of the screen, creating shorter and easier-to-read line lengths.

Centered designs are very fashionable at the moment, so learning how to center a design in CSS is one of the first things most developers want to learn. There are two basic methods for centering a design: one uses auto margins and the other uses positioning and negative margins.

Centering a design using auto margins

Say you have a typical layout where you wish to center a wrapper div horizontally on the screen:

 
1 <body> 
2 <div id=“wrapper”
3 </div> 
4 </body> 

To do this you simply define the width of your wrapper div and then set the horizontal margins to auto:

 
1 #wrapper { 
2 width: 720px;
3 margin: 0 auto;
4 }

In this example I have decided to fix the width of my wrapper div in pixels, so that it fits nicely on an 800600 resolution screen. However, you could just as easily set the width as a percentage of the body or relative to the size of the text using ems.

This works on all modern browsers. However, IE 5.x and IE 6 in quirks mode doesn’t honor auto margins. Luckily, IE misunderstands text-align: center, centering everything instead of just the text. You can use this to your advantage by centering everything in the body tag, including the wrapper div, and then realigning the contents of the wrapper back to the left:

 
1 body { 
2 <strong>text-align: center;</strong> 
3 }
4
5 #wrapper {
6 width: 720px;
7 margin: 0 auto;
8 <strong>text-align: left;</strong> 
9 }

Using the text-align property in this way is a hack—but a fairly innocuous hack that has no adverse effect on your code. The wrapper now appears centered in IE as well as more standards-compliant browsers (see Figure 7-1).

Figure 7-1. Centering a design using auto margins
Figure 7-1. Centering a design using auto margins

There is one final thing that needs to be done in order for this method to work smoothly in all browsers. In Netscape 6, when the width of the browser window is reduced below the width of the wrapper, the left side of the wrapper spills off the side of the page and cannot be accessed. To keep this from happening, you need to give the body element a minimum width equal to or slightly wider than the width of the wrapper element:

 
1 body { 
2 text-align: center;
3 <strong>min-width: 760px;</strong> 
4 }
5
6 #wrapper {
7 width: 720px;
8 margin: 0 auto;
9 text-align: left;
10 }

Now if you try to reduce the width of the window below the width of the wrapper div, scroll bars will appear, allowing you to access all of the content.


Lista de Usabilidad para Diseño Web

  • Autor: administrador
  • Archivado bajo: Recursos, Diseño
  • Fecha: May 27,2008

Enough talking, let’s start!

    Technical

  1. Did you validate your (X)HTML using W3C Markup Validation Service?
  2. Did you validate your CSS using W3C CSS Validation Service?
  3. Did you check your website in at least IE, FF, Opera and Safari?
  4. Images

  5. Did you add the ALT and TITLE attributes to all your important images?
  6. Did you add the LONGDESC attributes to all your image that need a description?
  7. Did you write effective ALT text?
  8. Did you make the size of your pages less then 50KB?
  9. Did you choose the appropriate filetype for your images?
  10. Did you add a description to images that support your content?
  11. Did you use plain text instead of images for important content?
  12. Content

  13. Did you use a sans-serif typeface with a decent font size for your body text?
  14. Did you adjusted the leading and tracking, if necessary, to increase readability?
  15. Did you align your body text to the left? (depends on language)
  16. Did you use EM or percentages instead of PX?
  17. Did you make sure that there are no whole sentences in uppercase?
  18. Did you use less then 78 characters, including spaces, per line?
  19. Did you make brief and precise paragraphs with explanatory titles?
  20. Did you use lists to sum things up?
  21. Did you write your conclusion first and then your explanation?
  22. Did you create enough contrast between the text and the background?
  23. Did you make your website also accessible for text-only browsers?
  24. Did you make sure that there are no ‘under construction’ pages?
  25. Did you include a print function on pages with a large amount of text?
  26. Did you include a print stylesheet?
  27. Did you replace all special characters with the ISO Latin-1 codes?
  28. Did you spell check your content and did you proofread for grammar errors??
  29. Navigation

  30. Did you make sure that all your links work? W3C Link checker does the job.
  31. Did you include a link to all your main pages on your homepage?
  32. Did you include your main navigation on every page?
  33. Did you use no more then 8 items in your main navigation?
  34. Did you distinguish the active and nonactive page in the menu?
  35. Did you use self explanatory link text instead of ‘click here’?
  36. Did you use self explanatory link text instead of business terms?
  37. Did you make a distinction between visited and non-visited links?
  38. Did you make a distinction between links and plain text?
  39. Did you add the TITLE attribute to all your links?
  40. Did you use breadcrumbs if you have a large amount of pages?
  41. Did you include a search option if you have a large amount of pages?
  42. Did you make your logo link to your homepage?
  43. Did you make a skip to content link at the top of your pages?
  44. Did you make a skip to menu link at the top of your pages?
  45. Did you make it possible to browse your website using SHIFT-TAB and RETURN?
  46. Did you make sure you didn’t use any javascript links?
  47. Structure

  48. Did you make a consistent page structure?
  49. Did you place your logo at the top left?
  50. Did you place an explanatory tag line next to your logo?
  51. Did you place your search box at the top right?
  52. Did you place important content above the fold/scroll?
  53. Did you make your design on a grid system?
  54. Did you make your design fluid using percentages?
  55. Did you make your website also viewable on low resolutions?
  56. Did you make custom titles (as in TITLE tag) for all your pages?
  57. Forms

  58. Did you make sure that users don’t return to an altered form after an error?
  59. Did you make a friendly and informative error page?
  60. Did you make a friendly ‘thank you’ page with a confirmation email?
  61. Did you add only a ’submit’ button and no ‘reset’ button?
  62. Did you tell the user what to expect after clicking the submit button?
  63. Did you split long forms up into multiply pages?
  64. Did you gave the user room to type?
  65. Did you place an asterisk when a field is compulsatory?
  66. Did you keep the standard look of input fields that is generated by the browser?
  67. Did you create a logical order of asking information?
  68. Did you use double input fields for passwords only?
  69. Did you let the computer, not the user, handle information formatting?
  70. Did you make sure that users can fill in the entire form using the TAB key?
  71. Did you explain to the user why you ask certain information?
  72. Did you explain to the user what you are going to do with that information?
  73. Did you use realtime validation using AJAX?
  74. Did you use the LABEL tag?
  75. Did you place the LABEL above the input field, instead of next to it?
  76. Did you choose the correct input type for different data?
  77. Did you make the top input field automatically active using setfocus?
  78. Did you destinguish the active field from non-active fields using input:focus?
  79. Did you use the FIELDSET and LEGEND entities when appropriate?
  80. Did you check if your forms also work with Javascript turned off?
  81. Multimedia

  82. Did you make sure that essential information/navigation is not made in Flash?
  83. Did you make sure that music and videoclips don’t start playing automatically?
  84. Did you make sure that music and videoclips can be turned off at any time?
  85. Did you inform the user about the size and length of your music and videoclips?
  86. Extra features

  87. Did you make a custom 404 page?
  88. Did you make a site map?
  89. Did you make a rss feed? (if you add content regularly)
  90. Did you make a high contrast version of your website?
  91. Did you make good looking URL’s (like this one)?
  92. Did you make sure that there are no frames on your website?
  93. Did you make sure that there are no pop ups on your website?
  94. Did you make a contact form instead of just an email link?

Mandamientos del Webmaster

  • Autor: administrador
  • Archivado bajo: Blogroll
  • Fecha: May 27,2008
  • 1. Amarás a <div> sobre todas las demás etiquetas
  • 2. No usarás <br /> en vano
  • 3. Validarás siempre tu código con w3c
  • 4. Honrarás al XHTML y CSS
  • 5. No usarás tablas en la maquetación principal
  • 6. No utilizarás la etiqueta <font> dentro del código
  • 7. No harás Copy&Paste de otras páginas
  • 8. No programarás sólo para Internet Explorer
  • 9. No descargarás por el emule plantillas de templatemonster
  • 10. No codiciarás la Web 2.0