First of all, you need to determine what kind of problem you are having.

Getting started

If you are new to Xubuntu, you will want to read the excellent Xubuntu documentation, that is also shipped with Xubuntu (in version 8.04 it is located under /usr/share/xubuntu-docs/index.html). It should be your first stop when trying to figure out how to connect to the internet, how to install applications, and similar basic tasks. All this thanks to the huge, voluntary efforts of the Xubuntu Documentation Team (you can also help out with the Xubuntu documentation yourself!).

Of course, if you want to perform slightly more advanced tasks, such as setting up periodical backups on Xubuntu, the internet is your friend. There are a lot of great resources on the internet that can help you with anything from installing Xubuntu on the Eee PC to browsing Windows network shares with Thunar. However, be sure to double-check which version of Xubuntu the guide is written for. For example, the post on browsing Windows network shares I just linked to is, at the time of writing, a little outdated and contains unnecessary steps.

It is also safest to look for articles written specifically targeting Xubuntu - tutorials aiming at Ubuntu users will often work as well, articles targeting just "Linux" are less likely to result in success.

When you can't find the answer

If you've spent time roaming the dark alleys of the internet, spit through every last bit of Xubuntu's official documentation, but still don't have an answer, there are a number of support options.

One requirement for all these options is that you specify as much information as possible. This includes, but needn't be limited to, the fact that you're running/wanting to run Xubuntu, which version of Xubuntu you're running, what you're problem is, what the expected result is, and perhaps how proficient you are with Xubuntu. This allows other people to help you in the best possible way.

The xubuntu-users mailinglist is, well, a mailinglist for Xubuntu users. All messages sent to a certain email address (xubuntu-users@lists.ubuntu.com in the case of xubuntu-users) will be delivered to everybody who has subscribed to that mailinglist. Thus, if you need help with Xubuntu, you can subscribe to that mailinglist, send an email to that address explaining your problem, and perhaps the next time you check your email, the answer is waiting for you.

You might not have the patience to wait for people to respond, however. If that is the case, fear no more, as IRC comes to the rescue! IRC is a way of being able to communicate in real time with other people - in other words, a chatbox. First you need an application to talk IRC - Xchat, DarkIRC, whatever, it shouldn't really matter. Using your IRC client, you need to connect to a network - FreeNode (on irc.freenode.net) in this case. Once you're connected to the network, you need to join the appropriate chatroom (how old-school is that?) - the Xubuntu support room (or channel in IRC lingo) is #xubuntu. You can join by typing /join #xubuntu.

Once you're in - ask away! Be sure to be polite, not to spam the channel, and realize that, if nobody answers, probably nobody knows. Don't ask the same question over and over again.

It is no secret, however, that the Xubuntu community is not quite the size of the Ubuntu community. Luckily, many people in the Ubuntu community can also help you with your Xubuntu problems if nobody in the Xubuntu community can. The place to get help from the Ubuntu community is the Ubuntu forums. With a very large amount of active members, your question is very likely to find an answer here.

Another place to get help is at Launchpad answers, which is part of Launchpad, a project management website where Ubuntu is managed. Here, you'll be more likely to find developers, who are most likely to be able to help you.

When there is no answer

Even with this vast range of support options, some problems are just errors in the software - so called bugs. These can be reported at bugs.ubuntu.com, where a developer can look at it and, if you're lucky, provide a fix for you and other users to enjoy.

Conclusion

Of course, there will still be times when no answer can be found. However, after having read this article, you'll hopefully be able to better find help yourself. And of course, if you cannot find help, feel free to ask me - I may not be able to provide an answer, but I might be able to give you some pointers.

Diary as of 7/6 - 7/8/2008

Today Emma and Pete decided to drive the youngsters out of the pigeon castle - Willy and Joey have to sleep somewhere else and not on their glasses any more. I am sad. But I assume that's the way life goes and completely natural. Despite that I am sad and I worry about the kiddos. Are they really ready to live on their own already? And are they coming back? I am feeling as if they were my own kids that have left home. Geeez - I must be crazy - it's only some damn stupid pigeons but in the meanwhile I feel about them as if they were pets :(

And the next days always the same happens:

Willy and Joey are chased away by both parents vigorously now when they try to land on the balcony. This can last up to an hour or even more with some pauses in between where the kiddos try to land and are then chased away so that the feathers are flying. I am really worried and fear that they hurt themselves.

In some way it is interesting to watch how this happens: Pete runs on the balustrade after them - mostly it is Willy whom he is chasing - he lifts one of his wings and then he slaps with it with a real loud noise. It's really like a nasty person slapping someone. And each evening this happens the same way when they try to occupy their sleeping places - without success. When the chase is on, you can hear wild flapping of wings with a lot of noise each evening on the balcony. Sometimes they get so mad at each other that they are fighting on the sideboard, their beaks jammed in each other's face and flapping wildly with the wings. Even spraying them with water does not end the fight sometimes.

Gladly up till today none of the crazy pigeons got hurt so I think it's somehow okay. But it all costs them a lot of energy. And I will have to think about an alternative how I could avoid those terrible fights. It's getting on my nerves and I am always afraid that they will hurt each other one day.

The funny thing is that both kiddos gain power through these fights. Perhaps this is a necessary process. From day to day they are less afraid of their father and sometimes I laugh loud when they trick him. They really do this: one diverts his attention and of course gets chased while the other one tries to reach their beloved sleeping places on the board. But this of course does not work for long because the mother chases them as well.

Despite all this fighting during the day sometimes too Willy and Joey sneak in from time to time and I can give them some of their beloved sunflower seeds. Together we can trick ol' Pete and his nasty wife!!!!

In the meanwhile they have learned to follow the noise I am making with a little plastic bowl that has a red cover and they have learned to trust me, while I am standing at the balustrade to pick their seeds directly from that little bowl that I am holding in my hands. So they still come to get their goodies.

Especially towards evening time Pete and Emma sit like vultures on the glasses where the kiddos used to sleep in order to protect their area. And oh boy - if they dare to appear then the wild chase is on again.

Sometimes Pete gets tired chasing the youngsters but Emma especially is a real bitch - each time she gets furious when Joey or Willy appear. I wonder what will happen when the new kiddos are grown up????

That will be very interesting.

~~~

Winnie and Jimi (the new babies) are growing fast. Today I put a piece of cartonage into the flower pot in order to hinder them from falling out of the nest when they begin to flap their wings and trying to go on adventurous tours. I think it won't take very long for that. Also that piece of cardboard keeps them much warmer - the nights are quite cold at the moment and they are huddled together often.

Btw - I also observed a different behaviour of the parents while feeding: unlike in spring both parents are feeding directly one after the other. I wonder whether this is an improved behaviour or not. I don't know...

Winnie and Jimi after 9/10 days:

Btw - that pink naked part to be seen at the beginning of the little video is Jimi's bare leg...

Source Code Testing: 

1. Source Code history
2. Use of readable indentation for source
3. Source Code optimization
4. Source Code Comment documentation
5. Source Code Backup
6. Appropriate naming conventions for source files
7. Appropriate storage location for source files
8. Appropriate use of Transactions wherever required
9. Appropriate use of Stored Procedures wherever required
10. Use of functions for code reuse
11. Use of Common library
12. CSS Code to be separated from the source code
13. AJAX code to be separated from the source code
14. Use of version control mechanism
15. Source Code encryption mechanism
16. Appropriate use of sessions / cookies
17. LDAP authentication
18. Following the standards. (for e.g. XHTML 1.0 standard for web coding).
19. Appropriate naming conventions for functions used and functions in the common library
20. Appropriate Folder structure for source code files
21. Clearance of extra comments, unnecessary code, echoes, alerts, type texts
22. No hard coding should be present 

Database Testing: 

1. Appropriate linking of tables
2. Normalization
3. Naming Conventions
4. Appropriate storage engine is used
5. Optimized field types are used
6. Backup function
7. Appropriate use of Triggers
8. Encrypted storage of confidential data
9. Compressed storage of big data
10. Appropriate prefixing for special characters before storage
11. Scalability
12. Database Document - Design schema with sample data
13. Appropriate filtering of data before storing into the database
14. Appropriate default values for table fields
15. Appropriate comments entered for table fields
16. Database Design query with sample data to be documented 

UI Testing: 

1. Consistency of screens
2. Consistency of background colours
3. Usage of pleasant colours
4. IPR violation with logos, images, colours, text
5. Consistency across multiple browsers (IE, Mozilla, Netscape)
6. All controls on the screen should be accessible through keyboard / Keyboard shortcuts
7. Various screen sizes testing
8. Various Platforms testing
9. Best Configuration message on home page
10. Appropriate tool tips for all elements on UI
11. All dropdowns heights and widths, symmetry and consistency
12. Textboxes height and width
13. Overall symmetry
14. All kinds of necessary validations for blank data inputs, illegal data inputs
15. Warning, error window sizes and placement
16. Test for SQL injection
17. Testing for over limit, under limit, different data types, null inputs
18. Testing for Reflection, no variable/class/method names should be hard coded
19. Print all the output reports and test them for alignment, proper page breaks, formatting, paper size, data readability and completeness
20. Scalability for various technologies, if yes, define configuration and process steps for migration
21. Backup
22. Backup Procedure documented
23. Auto/Manual Backup
24. All necessary documentations: commenting the code, flow chart, database design/schema, table design/scheme, user manual, source code/files naming conventions, ER diagram, help files, researched material
25. Testing for SOX compliancy
26. Overall user friendliness & aesthetics
27. Should be best viewable with 800x600 resolution
28. Maximizing, minimizing, resizing of windows to be possible
29. Positioning of cursor on the first editable field in Data entry screens
30. Every screen should have one Default button
31. Acknowledgment of error messages should take the control to where the error occurred
32. The Title bar should contain appropriate title
33. Every screen should have a title/header
34. Ease of use without any help
35. Grammatical correctness of error messages
36. Correct grammar for texts, field names, tool tips
37. Grammatical correctness of Help text
38. Text box lengths should correspond the length of data they take, wherever possible
39. Default values to be populated wherever possible
40. Consistent behaviour when screen resolution is changed
41. Consistency of margins and header and footer
42. Consistency of Colour of form
43. Consistency of Size of form
44. Consistency of fonts used for labels
45. Consistency of Size of buttons
46. Consistent use of animations/graphics
47. Consistency of labelling of controls (buttons, boxes)
48. Consistency of length of textboxes for the same field
49. Consistency of formats for date fields
50. Effective reuse of repeatable visual themes
51. When a button is clicked
52. When an error is encountered
53. When a field is being validated
54. Should support users' sequence of accomplishing a task
55. ‘Back' and ‘Home' links to be provided
56. Correct order of tabbing
57. Text to be selected when tabbing to a textbox
58. All tab controls should be accessible thru' keyboard
59. Shortcut keys (hot keys) to be unique
60. Links should be obvious and consistent
61. Functioning of the ‘Back' and ‘Forward' functions of the browser
62. Check if all links are active
63. Alignment of labels
64. Alignment of buttons
65. Anything that needs user action must be communicated
66. Feedback should be provided whenever relevant
67. Minimum usage of pop-ups and message boxes
68. User errors must be communicated
69. Availability of Help feature
70. Availability of Context-sensitive help, wherever needed
71. Buttons should be enabled/disabled depending on context
72. Non-editable text fields should be distinctly visible from others
73. Messages and labels should be accurate and appropriate for the context
74. Check if all links lead to meaningful points
75. Use of familiar and comfortable language
76. Abbreviations and code language to be used minimally
77. Help and Search links should be distinctly visible
78. Visible font for all text
79. Avoid all CAPS text
80. Help messages to be clear and concise
81. Error messages to be clear and concise
82. Should avoid horizontal scrolling
83. Should avoid vertical scrolling as much as possible
84. Logical ordering of controls
85. Position of controls should be meaningful
86. Grouping of related info. and data
87. Appropriate label for grouped data
88. Drop down/combo box menu to be ordered
89. Toggling of checkboxes
90. Checking/un checking of checkboxes through space-bar
91. Single choice for radio-buttons
92. Access keys (Keyboard shortcuts) letter should be underlined when visible on the UI
93. Frozen grid titles
94. Horizontal alignment of tables, body, div, span, data grid
95. Vertical alignment of tables, body, div, span, data gird
96. Mandatory fields should be distinctly marked in the UI 

Functional Testing: 

1. Basic Data flow is working properly
2. To be able to add data and save it correctly
3. To be able to edit data correctly
4. To be able to copy data correctly
5. To be able to delete data correctly
6. Cancel function
7. Logout function
8. Change Password feature
9. Password Complexity
10. Password History
11. Various authentication levels
12. Application should be accessible thru' URL as well as IP address
13. Time to load the application must be appropriate
14. Search Function
15. Search facility should be flexible (wildcards, mixed case, partial strings etc.)
16. Prompt to save unsaved data while trying to move to next screen
17. Password validation
18. Positioning of pop up windows
19. Field vs. form level validations
20. Destructive actions to be confirmed
21. UI shows navigation and user friendly message for null records in the database
22. Search Engine Optimization (SEO)
23. A "Contact us" page for maintenance team. The page should have mail id,  address and phone numbers
24. Application should have a visible status bar - logged in user, logged in time, date
25. A user confirmation while logging out or closing the application
26. User should not be allowed to navigation to any of the application pages without logging in
27. User session should auto expire within the following specified time period (5 minutes > Session Expiry time > 15 minutes)
28. Highlighting of searched keywords should be present for Search feature

Ok, now it has officially been "a while" since my last post. But as always, there is a relatively good reason for that. Lately I have been very busy with the launch of my very first MOSS project. This has definitely been a big learning process for me and more than ever I think I've learnt the hard way. There have been quite a few obstacles on the way and the project has lasted from late 2006, so the way has been quite a long one.

I thought shortly mentioning some of the key points and problems in bullets might be of help to others, so 'ere goes:

• Think about the architecture before asking for an ITT. Since the cost of MOSS enterprise license is high, you might end up with multiple times the cost given on the ITT if you have to scale out the architecture. Remember that MOSS is an enterprise solution - b2c companies (and probably even b2b) cannot handle their traffic with a single-server farm.
• Telerik RadControls are a nice addition to the MOSS GUI and give a good deal of configurability to the editor. I love the combination of being able to limit fonts and sizes and the excellent format stripper for stripping out horrible Word tags that evidently will sooner or later find their way on your website. However there are some problems in RadControls that can make content production a bit hard:
  • Reusable Content does not work correctly if Telerik RadControls is installed. This can be a showstopper to some. Anyway, at least it's good to know beforehand. We didn't. The real unfortunate part is that it seems like Telerik might not be able to fix this at all. This reusable content problem is discussed in Telerik forums: thread 1, thread 2 and in my blog.
  • There are also a couple of smaller bugs that can still be a bit challenging for content editors who are not very experienced. See my blog: post 1 and post 2.
• MOSS is hot right now. This means that at least in a country as small as Finland, the good consultants, developers and architects are scarce and overbooked. Be alert for multiple interest groups and partners in the project, managing them is a nightmare.
• Make sure anything of importance gets documented. This belongs to project management fundamentals, but cannot be stressed enough. It tends to be forgotten as soon as deadlines close in. Also, to be able to accurately document needs, requirements, who has requested them and if the request was accepted, will greatly help in the project.
• Specify your form needs beforehand and specify them well. InfoPath 2007 might sound tempting but using it requires licenses and deploying the forms might be really difficult depending on the form functionalities, MOSS customization and probably the star constellations. If your target is to have many many people edit and create forms, InfoPath might not be a good choice if the editors are not well-versed in web mysteries. Good suggestions for using forms with MOSS are appreciated...

It's been really gratifying to see the positive and sincere responses in the comments to my original post about this situation. With this kind of support I firmly believe that Joanne deserves a concerted turn-around when the Hospital Appeal Board hears her case.

Find more info on the situation from my additional post here, that I put out after the Comox local paper covered the case.

1. Screen size
2. Screen direction
3. Number of screens
4. Screen content
5. Position of the user
6. Distance from screen
7. Interactive zone
8. Interactive mode

At present I am applying these elements in the conceptual development of interactive displays at a German football stadium.

In addition to the elements shown in the figure above, the technology to be used must be adapted to suit the location and the purpose of the display. This list of design elements is by no means exhaustive, but should serve as a basis for analysis and concept development.

Diary as of 7/3/ - 7/5/08

Things change very quickly. While on one day you could hardly see any sign of feathers already the next day there is a huge difference.

7/05/08 Winnie is 1 week old now!!!

Both new babies have already quills sticking out now and develop much quicker than the older babies from spring (if you compare the photo from earlier you will realize that these are looking the same now after 1 week as the older ones after 11 days).

Both are already trying to stand up and exercising their leg muscles. Both babies seem to be more vivid than the first ones and are moving a little bit around already. And what's also different - parents started to leave them alone already.

One can also see that Winnie will have a little white spot on his head- not as big as his elder brother's Willy but a white spot anyway.

Both babies have definitely a different character than the older ones. They "talk" much more and are much less "defensive".

And here are some photos of the older "babies" and - as I know later on - the last ones where they can sit in peace together in their favourite basket on the board:

Here is Willy with the shower cap:

And here is Joey - the sweetie:

Diary as of 6/30 - 7/2/08

This morning at 5.20 they were fighting on the balcony again after Pete returned from his night sleep - so I took the water sprayer and put an end to it - all 3 of them flew away to another balcony where I hope that they stopped fighting.

I decided to take the sprayer each time when they start fighting again - I don't want them to injure themselves.

It seems that they are not quite angry at one another because during the day they often sit side by side or fly all 3 of them together (because one is with the babies). Must be the hormones but I may be wrong (I was wrong as it turned out later).

I also examined Winnie and Jimi (the new babies) - both are in perfect health so it seems. They seem to develop a bit differently than the early spring babies - both can open their eyes already and that after 3/2 days. And they already feep. But the feathers seem to grow slower if I compare the pictures of the spring babies with these now. Also the new babies seem to have more of these fine "hair feathers" than the former. Must be the difference in temperature.

Today I saw Pete feeding Winnie for the first time!

Well - this is the doctor's couch..........

Diary as of 6/27 - 6/30/08

Hurray!!! Happy birthday to Winnie. Baby #3 is on the world - now waiting for Jimi!!!

6/28 /08 Jimi is out as well - only one day later!

6/30/08 both babies are well.

Look at these pictures and you know what I mean. What a progress after 2 days:

Do you realize how their facial colours have already changed - the beaks turning dark already? And - akthough not visible on these photos - they have already their eyes open.

Regarding the first generation, Willy and Joey: Joey has started to fight with her mother Emma as well as Willy continues to quarrel with his mother and with his father Pete. They had a bad day all along. Nothing doing but nonsense the whole day. I assume they were bored because of the bad weather, picking all the soil out of my flowerpots, quarreling with their parents so that the feathers were flying until I finally grabbed the water sprayer that I use for the laundry and gave them a dose. It did not help for long though but I did not want them to hurt themselves.

Now there is peace again for a couple of minutes - both kiddos have conquered their "night sitting glasses" again.

Hope it will be better tomorrow.

Diary as of 6/13 - 6/26/08

Nothing special really happening - besides the whole family learned very quickly to listen to the shaking noise of the little plastic box where I have the goodies: sunflower seeds.

- each evening still is the same: Pete chasing his kiddos - kiddos trying to defend their sleeping seats on the 2 glasses on the board - Pete behaving like a little obnoxious arsehole because he is really treating the kiddos very badly in my human opinion which is nonsense of course. Later on we will see why he does that...

- each morning - very early - around 5° clock the kiddos are leaving their sleeping places and fly off to somewhere for picking up greenery I suppose. They come back several times during the day, taking some food (their goodies) or other corn, drinking from the birdie bathtub etc., looking around and flying off again as soon Pete or Emma appear.

There is something happening: Willy and Joey started to coo with one another, really behaving like a loving couple just exactly like their parents. It looks so nice but is this normal? That's incest!!! :oops: :oops: :oops:

And this is not all - look what they are doing. A little talk first and then...

End of story........till the next

This is where my trouble was. I was reading the article about how import works from the standard Python docs. So I read as much as I thought I needed and skipped over, what I thought at the time, to be unimportant. As it turns out the ability to do relative imports using '..' is a feature of only Python 2.5 *sigh*. Alright, so I could have just installed Python 2.5, but I didn't want to limit this code to running on Python 2.5 for no good reason. So I went back and changed the code to using absolute imports which took around 30 minutes because there were a decent number of files to play with.

So how did I miss this in the documentation? Well I managed to skim over the part which mentions this is only for Python 2.5 (I blame myself for this, btw). I take this as a lesson to pay closer attention when reading documentation. It may have taken me an extra 5 or 10 minutes to read all the documentation about imports and Python... but I will would have saved half an hour of my time if I had taken the extra effort :)

The Test Client itself has a lot more functionality than the Enqueue and Dequeue editors, and can put and get messages from nodes other than WMQ. See, Testing Messages Using the Test Client.

The current problems are being fixed, but the changes won't be visible until the next documentation update.

On 21 September 2001 - ten days after 9/11 - the Ad Council in the United States launched its ‘I am an American’ advertising campaign. The exhibition unsettles the Ad Council’s smooth presentation of post 9/11 American patriotism through interviews with those for whom, very recently, US citizenship has been anything but ‘safe.’ These include the son of undocumented immigrant Elvira Arellano, Greg and Glenda Avery, Hurricane Katrina evacuees who became ‘internally displaced’ refugees, and James Yee, a US army Muslim chaplain wrongly accused of being a terrorist spy. The pieces show how the fantasy of unity, wholeness and security pedalled by the designers of safe citizenship in the US remain just that, fantasies. The exhibition disarticulates and rearticulates what it means to be a US citizen in a post 9/11 context, enactments neatly summed up in Cindy Weber’s provocative reversal the US motto "E Pluribus Unum" (Out of many, One) to read, ‘out of one, Many.’
The original Ad Council release

Greg and Glenda Avery: We are americans

James Yee: I am an American

Or rather than read my clumsy, and awkwardly-phrased you can read the artist's statement in his own words:

"Using colorful media such as twisting balloons, party streamers, and artist tape, I have begun to add visual representations of sound effects to public spaces as a sort of dimensional graffiti. After embellishing the found scenes and photographing the results, I leave my additions in place to engage passers-by for as long as the materials hold up. For me, this process encourages a reexamination of surroundings and objects that are usually taken for granted, and injects a hint of the fantastical surreality that I have established in my other work.

Or, at the very least, I hope someone thinks these things are kind of funny."
- From his website.

Crackle (Speaker) (2007), site intervention with colored artist tape.
Pigment print
18" x 27"

Rrring (Payphone) (2007), site intervention with balloons.
Pigment print
18" x 27"

Hadlow's series called "To Tell a Lie" tries to examine the link between photojournalists, and how easy it is to manipulate photographs and a reader's convictions and perception of truth.

His new series Land of the Free does this to extraordinary effect. Some of my favorites:



See more of Shoefield's series here.

Vous animez la fonction Veille, Documentation et Diffusion de l'information à forte valeur ajoutée sur les grands secteurs du numérique, du niveau local à l'international. Ces secteurs se déclinent sur les thèmes micro & nano technologies, les télécoms réseaux & sécurité, l'informatique et logiciels, l'usage de TIC, les technologies du multimédia & loisirs numériques, la politique d'innovation et de recherche dans le numérique.

Plus d'infos sur l'Apec.

When you are in practice, every decision to, or not to, do something is a clinical decision based, hopefully, on reasoning, experience and evidence. When it comes to x-rays, you have to take these decisions even more seriously than you do with any other clinical decision because x-rays utilize ionizing radiation that is potentially harmful to a patient. As such, you want to have a pretty good reason for taking x-rays of a patient, of which there are many.

Just as you base your decision to take an x-ray series on good reasoning, there should be ample reason for why not to take an x-ray. While it's true that x-rays use ionizing radiation, and so you shouldn't use them willy nilly, the more potentially harmful aspect of x-rays is missing something on the film because of poor reading or poor film quality, or missing something altogether because you didn't take the x-ray in the first place. 

When I started practice in Michigan in 2000, about an hour north of me a doctor had injured a patient because he had a patient complaining of midback pain and he decided not to take an x-ray. It turns out the patient had metastatic cancer that had spread to the vertebral column, and the adjustment the doctor did badly injured the patient. That said, the doctor followed the standard of care and really didn't have much reason to take an x-ray of this patient for the complaint and signs/symptoms he presented with.

The decision not to take an x-ray is every bit as important as the one to take an x-ray, so it should be documented, and the reasoning upon which the decision not to take an x-ray is based upon should also be proven, which is why the x-ray criteria sheets are important even when you don't want to take an x-ray. In fact, honestly, in my opinion, this documentation is more important when you don't take an x-ray than when you do, from a medicolegal perspective.

Connaissez vous les RichTextBox ? probablement non si vous n'êtes pas programmeur, c'est les boites qui vous permettent d'écrire du texte formaté ( avec des couleurs, gras, italique etc...) que vous retrouvez dans WordPad ou autre...

Créé par Microsoft (lisez MyCrossoft :p ) pour simplifier la vie aux programmeurs... simplifier ? j'en doute... j'ai du galéré pour trouver la documentation et encore elle est loin d'être complète, pourtant ce n'est pas si compliquer a utiliser...

Enfin, pour remonter le moral voici la définition de Microsoft by Désencyclopedie ;)

D'abord quelques citations :

« AAAAAAAHHHHHHHHH!!!!!!!! »
~ Un utilisateur de Windows à propos du plaisir qu'il ressent à travailler dans cet environnement.

« Que... Et meeeeerdeeeeuh ! »
~ Un autre utilisateur de Windows à propos du plaisir qu'il ressent à travailler dans cet environnement.

Majestic-12 Documentation

]]>