Sep 21

openDaedalus : Open Development Standard

Uncategorized Add comments

I just submitted the project to SouceForge, if this works out i can start building the base structure untill i get more people interested in this project.

<meta name="GENERATOR" content="OpenOffice.org 2.0 (Linux)" /><meta name="AUTHOR" content="Allan Gray" /><meta name="CREATED" content="20060921;6331700" /><meta name="CHANGEDBY" content="Allan Gray" /><meta name="CHANGED" content="20060921;6482700" /><br /> <style> <!-- @page { size: 21cm 29.7cm; margin: 2cm } P { margin-bottom: 0.21cm } --> </style> <p style="margin-bottom: 0cm"> <p style="margin-bottom: 0cm">openDaedalus is an open source development standardization project</p> <p style="margin-bottom: 0cm"> <p style="margin-bottom: 0cm">It’s main focus it to construct a standard for all the aspects of systems development, templates, samples and tutorials to teach all who wish to learn.</p> <p style="margin-bottom: 0cm"> <p style="margin-bottom: 0cm">The main goal of the project in a nutshell is this:</p> <p style="margin-bottom: 0cm"> <p style="margin-bottom: 0cm">“Make one standard to rule them all”</p> <p style="margin-bottom: 0cm"> <p style="margin-bottom: 0cm">To Design a development standard to help guide:</p> <p style="margin-bottom: 0cm"> <p style="margin-bottom: 0cm">* All those just learning about professional development</p> <p style="margin-bottom: 0cm">* Small startups without any real development experience</p> <p style="margin-bottom: 0cm">* New development project managers</p> <p style="margin-bottom: 0cm"> <p style="margin-bottom: 0cm">The openDaedalus project structure is simple:</p> <p style="margin-bottom: 0cm"> <blockquote> <p style="margin-bottom: 0cm"><strong> Core Standard</strong></p> </blockquote> <blockquote> <p style="margin-bottom: 0cm">[ generic document structure, memory usage standard, etc ]</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote> <p style="margin-bottom: 0cm"><em><strong> Development Languages Standard</strong></em></p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">C++ Code Standard</p> </blockquote> <blockquote /> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Templates</p> <p style="margin-bottom: 0cm">Samples</p> <p style="margin-bottom: 0cm">Tutorials</p> <p style="margin-bottom: 0cm">Quality Control</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Python Code</p> </blockquote> <blockquote /> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Templates</p> <p style="margin-bottom: 0cm">Samples</p> <p style="margin-bottom: 0cm">Tutorials</p> <p style="margin-bottom: 0cm">Quality Control</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Ruby Code</p> </blockquote> <blockquote /> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Templates</p> <p style="margin-bottom: 0cm">Samples</p> <p style="margin-bottom: 0cm">Tutorials</p> <p style="margin-bottom: 0cm">Quality Control</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">PHP Code</p> </blockquote> <blockquote /> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Templates</p> <p style="margin-bottom: 0cm">Samples</p> <p style="margin-bottom: 0cm">Tutorials</p> <p style="margin-bottom: 0cm">Quality Control</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">JavaScript Code</p> </blockquote> <blockquote /> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Templates</p> <p style="margin-bottom: 0cm">Samples</p> <p style="margin-bottom: 0cm">Tutorials</p> <p style="margin-bottom: 0cm">Quality Control</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Other…</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote> <p style="margin-bottom: 0cm"><em><strong> Content Standard</strong></em></p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">XHTML Standard</p> </blockquote> <blockquote /> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Templates</p> <p style="margin-bottom: 0cm">Samples</p> <p style="margin-bottom: 0cm">Tutorials</p> <p style="margin-bottom: 0cm">Quality Control</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">XML Standard</p> </blockquote> <blockquote /> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">Templates</p> <p style="margin-bottom: 0cm">Samples</p> <p style="margin-bottom: 0cm">Tutorials</p> <p style="margin-bottom: 0cm">Quality Control</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote /> <blockquote> <p style="margin-bottom: 0cm">And so on..</p> </blockquote> <p style="margin-bottom: 0cm"> <blockquote> <p style="margin-bottom: 0cm">Anybody is welcome to contribute and better the standard ..</p> </blockquote> </div> <!-- You can start editing here. --> <!-- If comments are open, but there are no comments. --> <h3 id="respond">Leave a Reply</h3> <form action="http://blog.guillermoamaral.com/wp-comments-post.php" method="post" id="commentform"> <p><input type="text" name="author" id="author" value="" size="22" tabindex="1" /> <label for="author"><strong>Name</strong> (required)</label></p> <p><input type="text" name="email" id="email" value="" size="22" tabindex="2" /> <label for="email"><strong>Mail</strong> (will not be published) (required)</label></p> <p><input type="text" name="url" id="url" value="" size="22" tabindex="3" /> <label for="url"><strong>Website</strong></label></p> <p><textarea name="comment" id="comment" cols="100%" rows="10" tabindex="4"></textarea></p> <p><input name="submit" type="submit" id="submit" tabindex="5" value="Submit Comment" /> <input type="hidden" name="comment_post_ID" value="6" /> </p> </form> </div><!--/post --> </div><!--/content --> <div id="sidebar"> <ul> <li id="search" class="widget widget_search"><form method="get" id="searchform" action="http://blog.guillermoamaral.com/"> <div><input type="text" value="" name="s" id="s" /> <input type="submit" id="searchsubmit" value="Search" /> </div> </form> </li> <li id="text-209800141" class="widget widget_text"> <h2 class="sidebartitle">About</h2> <div class="textwidget"><center> <img alt="gamaral" src="http://dl.guillermoamaral.com/gamaral_100.jpg" /> <small> <h4>Guillermo Antonio<br />Amaral Bastidas</h4> Free/Libre/Open-Source Software Developer <a href="http://www.kde.org/">KDE</a> Tarball </small> </center> <a href="/about/">More...</a> </div> </li><li id="tag_cloud" class="widget widget_tag_cloud"><h2 class="sidebartitle">Tags</h2><a href='http://blog.guillermoamaral.com/tag/advocacy/' class='tag-link-35' title='4 topics' rel="tag" style='font-size: 9.27272727273pt;'>advocacy</a> <a href='http://blog.guillermoamaral.com/tag/agile/' class='tag-link-29' title='3 topics' rel="tag" style='font-size: 8.84848484848pt;'>agile</a> <a href='http://blog.guillermoamaral.com/tag/bash/' class='tag-link-23' title='6 topics' rel="tag" style='font-size: 10.1212121212pt;'>bash</a> <a href='http://blog.guillermoamaral.com/tag/books/' class='tag-link-53' title='1 topic' rel="tag" style='font-size: 8pt;'>books</a> <a href='http://blog.guillermoamaral.com/tag/cc/' class='tag-link-14' title='5 topics' rel="tag" style='font-size: 9.69696969697pt;'>c/c++</a> <a href='http://blog.guillermoamaral.com/tag/dell/' class='tag-link-56' title='2 topics' rel="tag" style='font-size: 8.42424242424pt;'>dell</a> <a href='http://blog.guillermoamaral.com/tag/development/' class='tag-link-8' title='8 topics' rel="tag" style='font-size: 10.9696969697pt;'>development</a> <a href='http://blog.guillermoamaral.com/tag/eee/' class='tag-link-49' title='1 topic' rel="tag" style='font-size: 8pt;'>eee</a> <a href='http://blog.guillermoamaral.com/tag/emacs/' class='tag-link-42' title='1 topic' rel="tag" style='font-size: 8pt;'>emacs</a> <a href='http://blog.guillermoamaral.com/tag/floss/' class='tag-link-36' title='6 topics' rel="tag" style='font-size: 10.1212121212pt;'>floss</a> <a href='http://blog.guillermoamaral.com/tag/gentoo/' class='tag-link-50' title='1 topic' rel="tag" style='font-size: 8pt;'>gentoo</a> <a href='http://blog.guillermoamaral.com/tag/gnulinux/' class='tag-link-25' title='34 topics' rel="tag" style='font-size: 22pt;'>gnu/linux</a> <a href='http://blog.guillermoamaral.com/tag/gpl/' class='tag-link-38' title='1 topic' rel="tag" style='font-size: 8pt;'>gpl</a> <a href='http://blog.guillermoamaral.com/tag/internet/' class='tag-link-9' title='3 topics' rel="tag" style='font-size: 8.84848484848pt;'>internet</a> <a href='http://blog.guillermoamaral.com/tag/javascript/' class='tag-link-18' title='1 topic' rel="tag" style='font-size: 8pt;'>js</a> <a href='http://blog.guillermoamaral.com/tag/kde/' class='tag-link-39' title='15 topics' rel="tag" style='font-size: 13.9393939394pt;'>kde</a> <a href='http://blog.guillermoamaral.com/tag/kphone/' class='tag-link-57' title='1 topic' rel="tag" style='font-size: 8pt;'>kphone</a> <a href='http://blog.guillermoamaral.com/tag/laptop/' class='tag-link-54' title='3 topics' rel="tag" style='font-size: 8.84848484848pt;'>laptop</a> <a href='http://blog.guillermoamaral.com/tag/licensing/' class='tag-link-37' title='1 topic' rel="tag" style='font-size: 8pt;'>licensing</a> <a href='http://blog.guillermoamaral.com/tag/management/' class='tag-link-28' title='5 topics' rel="tag" style='font-size: 9.69696969697pt;'>management</a> <a href='http://blog.guillermoamaral.com/tag/mods/' class='tag-link-58' title='1 topic' rel="tag" style='font-size: 8pt;'>mods</a> <a href='http://blog.guillermoamaral.com/tag/mta/' class='tag-link-44' title='1 topic' rel="tag" style='font-size: 8pt;'>mta</a> <a href='http://blog.guillermoamaral.com/tag/no-luck/' class='tag-link-33' title='7 topics' rel="tag" style='font-size: 10.5454545455pt;'>no-luck</a> <a href='http://blog.guillermoamaral.com/tag/os/' class='tag-link-24' title='16 topics' rel="tag" style='font-size: 14.3636363636pt;'>os</a> <a href='http://blog.guillermoamaral.com/tag/personal/' class='tag-link-2' title='23 topics' rel="tag" style='font-size: 17.3333333333pt;'>personal</a> <a href='http://blog.guillermoamaral.com/tag/professional/' class='tag-link-3' title='28 topics' rel="tag" style='font-size: 19.4545454545pt;'>professional</a> <a href='http://blog.guillermoamaral.com/tag/quotes/' class='tag-link-31' title='7 topics' rel="tag" style='font-size: 10.5454545455pt;'>quotes</a> <a href='http://blog.guillermoamaral.com/tag/reviews/' class='tag-link-34' title='2 topics' rel="tag" style='font-size: 8.42424242424pt;'>reviews</a> <a href='http://blog.guillermoamaral.com/tag/scrum/' class='tag-link-30' title='2 topics' rel="tag" style='font-size: 8.42424242424pt;'>scrum</a> <a href='http://blog.guillermoamaral.com/tag/sleep/' class='tag-link-52' title='1 topic' rel="tag" style='font-size: 8pt;'>sleep</a> <a href='http://blog.guillermoamaral.com/tag/spam/' class='tag-link-43' title='1 topic' rel="tag" style='font-size: 8pt;'>spam</a> <a href='http://blog.guillermoamaral.com/tag/tijuana/' class='tag-link-45' title='1 topic' rel="tag" style='font-size: 8pt;'>tijuana</a> <a href='http://blog.guillermoamaral.com/tag/tjlug/' class='tag-link-46' title='1 topic' rel="tag" style='font-size: 8pt;'>tjlug</a> <a href='http://blog.guillermoamaral.com/tag/trip/' class='tag-link-47' title='2 topics' rel="tag" style='font-size: 8.42424242424pt;'>trip</a> <a href='http://blog.guillermoamaral.com/tag/twitter/' class='tag-link-51' title='2 topics' rel="tag" style='font-size: 8.42424242424pt;'>twitter</a> <a href='http://blog.guillermoamaral.com/tag/usa/' class='tag-link-7' title='2 topics' rel="tag" style='font-size: 8.42424242424pt;'>usa</a> <a href='http://blog.guillermoamaral.com/tag/usenet/' class='tag-link-40' title='2 topics' rel="tag" style='font-size: 8.42424242424pt;'>usenet</a> <a href='http://blog.guillermoamaral.com/tag/web-applications/' class='tag-link-11' title='1 topic' rel="tag" style='font-size: 8pt;'>webapps</a> <a href='http://blog.guillermoamaral.com/tag/winblows/' class='tag-link-26' title='1 topic' rel="tag" style='font-size: 8pt;'>winblows</a> <a href='http://blog.guillermoamaral.com/tag/wordpress/' class='tag-link-55' title='1 topic' rel="tag" style='font-size: 8pt;'>wordpress</a> <a href='http://blog.guillermoamaral.com/tag/world/' class='tag-link-4' title='5 topics' rel="tag" style='font-size: 9.69696969697pt;'>world</a></li><li id="archives" class="widget widget_archive"><h2 class="sidebartitle">Archives</h2> <select name="archive-dropdown" onchange='document.location.href=this.options[this.selectedIndex].value;'> <option value="">Select Month</option> <option value='http://blog.guillermoamaral.com/2008/09/'> September 2008 </option> <option value='http://blog.guillermoamaral.com/2008/08/'> August 2008 </option> <option value='http://blog.guillermoamaral.com/2008/04/'> April 2008 </option> <option value='http://blog.guillermoamaral.com/2008/01/'> January 2008 </option> <option value='http://blog.guillermoamaral.com/2007/12/'> December 2007 </option> <option value='http://blog.guillermoamaral.com/2007/11/'> November 2007 </option> <option value='http://blog.guillermoamaral.com/2007/10/'> October 2007 </option> <option value='http://blog.guillermoamaral.com/2007/09/'> September 2007 </option> <option value='http://blog.guillermoamaral.com/2007/08/'> August 2007 </option> <option value='http://blog.guillermoamaral.com/2007/07/'> July 2007 </option> <option value='http://blog.guillermoamaral.com/2007/06/'> June 2007 </option> <option value='http://blog.guillermoamaral.com/2007/05/'> May 2007 </option> <option value='http://blog.guillermoamaral.com/2007/04/'> April 2007 </option> <option value='http://blog.guillermoamaral.com/2007/03/'> March 2007 </option> <option value='http://blog.guillermoamaral.com/2007/02/'> February 2007 </option> <option value='http://blog.guillermoamaral.com/2007/01/'> January 2007 </option> <option value='http://blog.guillermoamaral.com/2006/12/'> December 2006 </option> <option value='http://blog.guillermoamaral.com/2006/11/'> November 2006 </option> <option value='http://blog.guillermoamaral.com/2006/10/'> October 2006 </option> <option value='http://blog.guillermoamaral.com/2006/09/'> September 2006 </option> </select> </li><li id="linkcat-32" class="widget widget_links"><h2 class="sidebartitle">blogroll</h2> <ul class='xoxo blogroll'> <li><a href="http://www.tjlug.org/" rel="me">Grupo de Usuarios de GNU/Linux de Tijuana</a></li> <li><a href="http://planetkde.org/" title="Planet KDE is an aggregation of public weblogs written by contributors to the K Desktop Environment. The opinions expressed in these weblogs and hence this aggregation are those of the original authors.">Planet KDE</a></li> <li><a href="http://planet.tjlug.org/" rel="me">Planeta Grupo de Usuarios de GNU/Linux de Tijuana</a></li> <li><a href="http://mx.planetalinux.org" rel="colleague co-resident">Planeta Linux Mexico</a></li> </ul> </li> <li id="rss-1" class="widget widget_rss"><h2 class="sidebartitle"><a class='rsswidget' href='http://planetkde.org/rss20.xml' title='Syndicate this content'><img style='background:orange;color:white;border:none;' width='14' height='14' src='http://blog.guillermoamaral.com/wp-includes/images/rss.png' alt='RSS' /></a> <a class='rsswidget' href='http://planetKDE.org/' title='Planet KDE - http://planetKDE.org/'>Planet KDE</a></h2><ul><li><a class='rsswidget' href='http://weblog.obso1337.org/2008/pilot-usability-testing-activity/' title='A while back, there was some discussion about how Ubuntu LoCos could get more involved in usability, such as through testing. So for the past few months, I’ve been talking with some Ubuntu LoCo members on how we can Get Things Done. Usability testing is when you ask a study participant (who has similar characteristics as your target users) to complete a series of tasks using your product. The goal is to get feedback about the product so you can make it better. There are various types of testing protocols, but the one I use the most often as part of the design process is called an interrupted think aloud protocol (TAP). The participant is given a scenario and asked to complete a set of tasks. They may work quietly, but talk aloud if they like or ask questions. The moderator may or may not answer their questions in order to see how the participant attempts to solve the problem. The moderator may also interrupt the participant during the task scenario in order to discuss a particular choice or action. This isn’t performance-based testing because the participant is distracted by moderator’s presence, periodic interruptions, and thinking/talking aloud, and is more useful than a pure TAP because the participant only speaks when they need to or asked to. When participants are required to speak through every thought and action, it can be very distracting to the task and affect the participant’s problem solving skills and performance on the task. But what about actually running usability tests? You can teach a monkey to run a test, but that doesn’t mean they will be any good at it. The main problems which came to mind were moderator skill and analysis of usability issues. Two of the most difficult skills to master as a test moderator are establishing a rapport with the participant, and knowing when to help a participant or let them struggle through a task. The first moderating skill problem, rapport, can be solved in a simple recruiting strategy. In what is called a “friends and family” recruit, LoCo members could find people they know who have certain characteristics (such as a certain age, computer experience, or education) and invite them to participate. The existing relationship between the moderator and participant allows the participant to speak and act freely instead of feeling like they are under a microscope. However, this existing relationship may complicate the second moderating skill problem, knowing when to help. Because the moderator has an established relationship with the participant, they may be more inclined to help the participant at the first signs of trouble rather than allowing the participant to figure it out for themselves. Hopefully careful training will help mitigate this effect. The identification and analysis of usability issues is a tough problem to solve. LoCo members may be able to report what the user said or did, but not necessarily why. As a moderator, they will be busy with the participant and may not be able to take good notes or they might miss something important if they do. Additionally, without rich context, even reporting what the user said or did may not be enough information for a designer to diagnose a problem. This is where the “second chair” comes in. A second chair is a second observer, usually “behind the glass”, who can concentrate on the participant and the design. Usually when I run usability testing in my company, I am the second chair. As the person who will be identifying and analysing issues, it is more important for me to watch what the user is doing and take good notes than for me to walk the participant through the activity. So in order to gather useful feedback, the LoCo running the usability test would need to have someone experienced in design to take notes for them. Unfortunately, the requirement of having an experienced designer as second chair limits the activity’s autonomy and creates requirements which not all LoCos would be able to fulfill. But hey, it’s better than nothing, right? Last Saturday, I met up with members of the Washington, D.C. Loco and ran a pilot usability study. The purpose of the pilot was to test the lab location, the computers used for testing, and the testing protocol. In addition to practicing moderating and running through the protocol on ourselves, we had two library patrons and a LoCo member’s “friend and family” participate. Since this was a pilot test, I will not be discussing the results only the logistics and lessons learned. The LoCo has a small computer lab (3 computers) running Ubuntu Hardy 8.04 in a conference/storage room in a city library. The goal was to provide an computing resource for library visitors who are interested in learning more about open source software. Over time, the lab sessions turned in to general computer and Internet training for library patrons, with a few actually bringing in their Windows computers and asking for help. The LoCo members were happy to help anyone who came in, but their message of open source software was no longer getting through. The usability testing activities were seen to be a way to bring the “open source” back in to the lab. It would encourage more LoCo members to stop by the lab by participating in the activity, and it would also expose library patrons to open source software through volunteering as a participant while someone fixes their computer. I wanted the testing sessions to be short (15-20 minutes) for several reasons. One, being a participant in usability testing can be tiring, even if it is a simple activity. Also, if multiple people show up, they become a distraction if too many people have to wait. If there are no other participants waiting, then an additional small activity could be added to the current participant’s session without making it unreasonably long. Finally, we will be more flexible and get more out testing if we focus on pieces of problems instead of trying to gather too much data. For this pilot test, we focused on the Digital Camera experience. Participants were asked to plugin a camera, download photos, manipulate one, and share it. A digital camera with photos was provided. This activity tested the hardware notification dialog, and F-Spot functionality. (We had one participant use the GIMP to do some simple editing, but it was too heavy of a tool for simple editing activities.) The testing environment was a PIII with 512MB RAM and a 17″ monitor running at 1280×1024. In addition to testing the protocol with LoCo members, we had 3 “real” participants. Participant 1 was about 45-55, owned a computer and had some computer skills, owned a digital camera but only downloaded photos from the camera and never really edited them. Participant 2 was about 55-65, owned a computer and had some computer skills, didn’t own a digital camera but was thinking about buying one. Participant 3 was about 35-45, owned a computer and had good computer skills, owned a digital camera and liked to use “scrapbook” software for editing photos. This was a pretty good sampling from audiences we don’t typically get feedback from (the highly adept and opinionated). We expect that participants recruited by DC LoCo members will have average to above average computer experience and walk-in library patrons will have average to below-average computer experience. The pilot was a success and I am confident we will be able to run several future activities and gather lots of usability feedback. Tentatively, we are planning to run the usability activity once a month for a few months to see how it goes and if we can continue to get participant recruiting support from our LoCo members. We will advertise to our LoCo members and encourage them to pick a date to bring a friend or family member, as well as encourage library patrons who stop by to participate. I also hope that we can do similar activities in LoCos around the world (if we can find usability engineers/designers to take notes) and at conferences. Some additional notes I’ve made to improve for the next session: Activities need to be 15-20 minutes, especially for walk-in library patrons. Having too many people in the lab is distracting and some participants may not have an hour to commit. We shouldn’t expect more than 1-2 walk-in library patrons and should try to encourage an additional 3-4 LoCo members to bring a friend or family by. This will give us 4-6 participants per session which I think is a good target for a recurring activity. A list of scenarios/activities would be useful so we can use the most appropriate scenario for the type of participant we have or allow participants with time to complete more than one activity. A standardized participant survey would help use gather data and better classify the participant in to a user group and match the data from one study to another. A big thanks to Washington, DC Ubuntu LoCoers Kevin Cole and Sanjay Jain for setting up and maintaining the Cleveland Park Library Ubuntu Lab. We would also like to thank Canonical for provided some nice Ubuntu pens, stickers, mousepads, and keychains as thank you gifts for our participants.'>Celeste Paul (seele): Pilot Usability Testing Activity</a></li><li><a class='rsswidget' href='http://blog.cryos.net/archives/193-New-Addition-to-the-Family.html' title='On Monday we had a new addition to the family arrive - an Asus Eee PC 1000! So far I am pretty impressed with the hardware. The Linux installation was pretty disappointing but I never really intended to keep that anyway. I played around with it on Monday as I built a chroot for the new arrival (pictured below). I went for the 10" model as I was worried about the size of the keyboard on the smaller ones. I also liked the sound of the SSD drive and it looked like a great little unit. I ended up building a custom stage 4 Gentoo tarball for it on my desktop and installing it here. I have it running the new KDE 4.1.2 ebuilds along with a few KDE 3 apps I can't do without. All in all it seems to be working pretty well. I only got round to installing Gentoo on it yesterday. So far I have the webcam, wired and wireless networking working. I am using WICD to control networking. I would love to see a Qt4/KDE 4 frontend that integrates better but it is an awesome little app. This is my first post on it, the screen isn't a bad size and the battery life seems to be good. I am on the road today and my wife acted as an unwilling hand model. I still haven't managed to get the asus_laptop or asus_acpi modules to load and so am missing all those devices. It claims no such device. I will hopefully be able to post more at some point in the future. I certainly think this is great for being on the road and Skype is working with the webcam. I did use the 2.6.27 kernel whicih made things a lot easier I suspect. I might try building a vanilla kernel soon to see if that lets me insert the asus_laptop module successfully. For now I have quite a few hours to kill in the BA lounge at JFK!'>Marcus Hanwell (cryos): New Addition to the Family</a></li><li><a class='rsswidget' href='http://liquidat.wordpress.com/2008/10/15/rpm-fusion-enters-testing-state/' title=' RPM Fusion, a merge of several former Fedora 3rd party repositories providing licence/patent problematic packages, has entered the public testing state. Fedora Rawhide users can now start using it, and the brave among the Fedora 9 and Fedora 8 users can also help testing. RPM Fusion was announced more than a year ago and is the attempt to merge several of the many existing 3rd party repositories for Fedora (Dribble, Freshrpms,. livna). The idea of the common repository is to enhance the compatibility as well as avoid duplication - in the former time many packages were provided by more than one repository. The aim of the new RPM Fusion is however just the same as it was for the original repos: provide high quality packages of software which cannot be part of Fedora due to licence/patent problems. There was a lot of development going on in the background, but RPM Fusion wasn’t ready for Fedora 9 unfortunately - there was just too much to do: importing the packages, sorting out incompatibilities, creating a common build- and mirror-system, etc. Now most of the work is done and the new repository is ready for testing - more details can be found in Thorsten Leemhuis’ blog post. There you will also find ready-to-install repository packages. With the new repository the situation for users regarding mixed repositories and the possible incompatibilities will hopefully improve a lot. Also, new users don’t have to make a choice between the repositories. And last but not least, with a common and clear infrastructure RPM Fusion will hopefully attract more users to submit their packages to the project so that RPM Fusion grows even more.        '>Roland Wolters (liquidat): RPM Fusion enters testing state</a></li><li><a class='rsswidget' href='http://wadejolson.wordpress.com/2008/10/15/camp-kde-2009-first-two-sponsors-announced/' title='One aspect of a new conference that may be under-appreciated is that of sponsorship.  Not only are we organically growing a conference identity over the first years, but we’re also working with new sponsors. If you haven’t guessed, sponsors and donors that are interested in European conferences may be different than those with Central and South American conferences. As such, I’m happy to announce that we (the Camp KDE organizers) have already come to agreements with two American companies to help our event.  As with other events, their donations will be used to secure facilities and subsidize the travel and lodging of attendees. The upcoming Dot article on the event announcement will more formally address this topic, but I want to thank: iXsystems:  You may know them because of their desktop initiatives at electronic chains, their server offerings, or their collaboration with the BSD family (notably our friends at PC-BSD).  If you’re in the Bay Area, you can meet both at the “meetBSD California’08″ conference coming up in November. Google: Have you heard of them before?  They were kind enough to host our Release Event in January and they’re back to assist with Camp KDE. Above and beyond sponsorship, we’re still working on further involvement of both companies; hopefully presentations will be given.  Thanks to both iXsystems and Google. Whether to come.  What speeches to attend.  How long to stay.  Giving a presentation yourself.  Hosting a developer sprint.  What side of the beach to swim on: As always, originals in my public Picasa Gallery. The event and registration site are still on track to be completed this weekend.  It put a smile on my face when I woke up on Monday morning, logged in - and within 5 minutes both Ruphy and Franz were asking me about the site.        '>Wade Olson: Camp KDE 2009: First two sponsors announced</a></li><li><a class='rsswidget' href='http://ariya.blogspot.com/2008/10/pimp-my-widgets.html' title=' You think you are good? Why don't you try to win a Segway or some N810. Head straight to: http://trolltech.com/pimpmywidgets! Update: our pimp announced the contest right after dinner here at DevDays 2008: '>Ariya Hidayat: Pimp My Widgets</a></li><li><a class='rsswidget' href='http://www.omat.nl/drupal/content/TVTAS' title='Probably everyone in The Netherlands learns this word at school. Translated to english it means nothing more than tv bag,but we learn it for another reason. It's the abbrevation of the five islands we have just north of the mainland: Texel, Vlieland, Terschelling, Ameland and Schiermonnikoog. The last couple of days I spend on the second t of tvtas. With family and friends we crossed the island a couple of times, went to see sunrise and ate Tappas at a Spanish restaurant. I'm avoiding some mailboxes, they simply contain a lot of new mail.. Maybe tomorrow... '>Tom Albers: TVTAS</a></li><li><a class='rsswidget' href='http://socceroosd.blogspot.com/2008/10/so-what-are-we-going-to-do.html' title='Ok, we've had our first WWW developers meeting. We had a stellar turnout! Plenty 'o people turned up and helped us start defining our direction.We had a lot of topics to cover, but ended up barely covering the first few. This was due to a larger than expected discussion about certain issues such as the use of a CMS or which demographic the site is meant for.Further meetings will need to be held to make more of these decisions.We talked quite a bit about the state of KDE's websites - needless to say, quite a number of them are in a state of bad repair. In our discussions on this we decided that it would be a good idea to consolidate many of the kde.org subdomains into the xBases (techbase and userbase). This especially applies for the websites that do not seem to be in 'good repair'.We will be compiling a list of the kde.org subdomains, their current state and their maintainers and contacting them regarding this plan. We're not saying that everyone has to shift to the xBases, but we are trying to move a lot more data there. All these subdomains are more a problem than a solution (maintenance wise, n00b user wise). If we can get rid of even half of the ~40 kde.org subdomains and consolidate them into the xBases then it will make our job a whole lot easier.Also, during our meeting it was pointed out that we need to define what content we want to go on www.kde.org . This was because there were differing opinions as to whether we have 'learning' information or 'community' information on the www.kde.org site landing page. There are very strong arguments for both views, but we will talk about this further in subsequent meetings.It was also discussed that we need a proper licence policy for all the content that goes on the KDE sites. This is especially applicable to user contributed content. We will be doing this with the help and guidance of the KDE e.V. board.So, in terms of what were going to do? We're going to start tidying up the kde.org subdomains and moving as much as we can into the xBases, we're also going to get the ball rolling on creating a licence policy for content.You can view the IRC meeting log here: http://www.valdyas.org/irina/stuff/kde-www/log-20081010.htmlWe didn't get around to discussing open collaboration services as we ran out of time. But this will be brought up in a future meeting.'>Sam Duff (Socceroos): So, what are we going to do?</a></li><li><a class='rsswidget' href='http://www.kuarepoti-dju.net//blog/2008-10-14-lokarest/' title='The KIO framework has been with KDE since eternity, in some parts long before KDE 2 came out if I'm reading the meta information correctly. It provides us with many useful slaves, including one for HTTP and WebDAV. However, despite the hours of work which went into it, and despite the fact that it works very well for most of the time, we can do better. The software world beyond the desktop is making its functionality increasingly available through well-defined interfaces. We, on the other hand, need a good API to make the ubiquity of services a reality. If we provide one, more developers will consider our libraries as a good choice for their applications. As one of these developers, the difficulty to access services with a REST interface has annoyed me for quite some time. At first I've thought that the mistake must be with me or my source code, but now that patches to KIO are available I know that it was simply impossible before. Now it is finally possible. (To be fair, SOAP users had a similar issue in early KDE 4 times. And with the new KXMLRPC library, operation-centric web services seem to have a good standing with KDE, too.) Back to the topic. How much functionality should such a framework contain? Everybody wants it to be as light-weight as possible, and I agree. Still I'd like to see some additional functionality over the state transfer handling it does right now. Its techbase page already mentions a resource cache and a transfer cache. The transfer cache will avoid forcing the application developer to handle network connection trouble. If a transfer fails due to a server being down or the laptop's ethernet cable being loose, why should the developer have to care? Robustness by automatic failure handling is therefore worth the additional couple hundreds lines of code in any case. The resource cache, on the other hand, will be more or less duplicating the kio_http cache, but on the other hand might give the developer more control about the amount and strategy of caching. Unfortunately there's no generic caching layer in KDE yet which we could simply use at this point even though many other libraries like KNewStuff or KGGZ could profit from such a layer. If access to services becomes ubiquitous, then caching will as well. Other than these two extensions to Lokarest, I can't think of any which I'd need in any or at least most applications using this framework. But there might be others hidden more deeply. Interestingly, Sun recently released a reference API for accessing REST services through their JCP, but beware that its licence is inherently non-free and tried to prevent alternative implementations. If that's not the intention and just the wording, the company should get better lawyers who can bring their point across more clearly. If it is indeed the intention, then good riddance JCP and welcome free, unencumbered alternatives from KDE's playground area. fup2 kde-services-devel'>Josef Spillner: How much service orientation do we need?</a></li><li><a class='rsswidget' href='http://frinring.wordpress.com/2008/10/14/better-width-with-open-sources/' title='While the Decoding table is being redone for KDE 4.2 there was a bug report pending about the old version of it, in that larger values do not fit into the witdh of the value fields. The culprit code: QFontMetrics metric( font() ); const int int16Width = metric.width( “88888888″ ); KLineEdit* mInt16Display = new KLineEdit( this ); mInt16Display->setFixedWidth( int16Width ); Bogus, as the width of the lineedit widget also includes the width of the frame plus some left and right margins, not just the width of the rendered string. While this report was filed as a wish, I considered it still as a bug. And because it looked simple (and to keep the Zarro-Boogs state for Okteta ) I navigated my editor to the 4.1 branch… to find out, it wasn’t that simple to fix. There is no such thing as a void QTreeView::resizeColumnToContents() for QLineEdit, or similar. So I tried QSize QStyle::sizeFromContents(), but the results were not as expected, the widget was always to small. Frustration. The night was becoming longer. This *peep* little thing should be solveable somehow. “Use the Source, Luke!” I remembered. Oh yes, of course, the Power of White boxes. A quick look at the implementation of QSize QLineEdit::sizehint() const showed that the content of a QLineEdit also includes the margins, for whatever reason. And, oh shame for the responsible, there are some hardcoded additional margins not exposed by functions like void void QWidget::getContentsMargins(), looks like work in progress. But then it was documented, by the source code itself, so that’s what makes it different from some Blackbox toolkit. Now the fixing code: KLineEdit* mInt16Display = new KLineEdit( this ); const int verticalMargin = 1; // hardcoded in gui/widgets/qlineedit.cpp const int horizontalMargin = 2; // hardcoded in gui/widgets/qlineedit.cpp const int mysticBonusMargin = 1; // no idea where it come from, but with one pixel more it is equally margined int leftMargin, rightMargin, topMargin, bottomMargin; mInt16Display->getContentsMargins( &leftMargin, &topMargin, &rightMargin, &bottomMargin ); QFontMetrics metric( font() ); const int int16Width = metric.width( “88888888″ ); const int lineSpacing = fontMetrics.lineSpacing(); const int minLineSpacing = 14; const int contentHeight = qMax(lineSpacing,minLineSpacing) + topMargin + 2 * verticalMargin + bottomMargin; const int contentOtherWidth = leftMargin + 2 * horizontalMargin + rightMargin + mysticBonusMargin; const QSize int16ContentSize( int16Width + contentOtherWidth, contentHeight ); QStyleOptionFrameV2 option; option.initFrom( mInt16Display ); option.lineWidth = mInt16Display->hasFrame() ? style()->pixelMetric( QStyle::PM_DefaultFrameWidth, &option, mInt16Display ) : 0; // rest of QStyleOptionFrameV2 does not seem to have an influence const int int16DisplayWidth = style()->sizeFromContents( QStyle::CT_LineEdit, &option, int16ContentSize, mInt16Display ).width(); mInt16Display->setFixedWidth( int16DisplayWidth ); Not wonderful, should be rather a service function in QLineEdit, but well, it works. And so the rest of the night was saved, and some users will be more happy after the release of KDE 4.1.3. Thank you, Open Sources Knights. PS: Still I can not believe it had to be solved this complicated. What did I miss?        '>Friedrich Kossebau (frinring): Better width with Open Sources…</a></li><li><a class='rsswidget' href='http://people.fruitsalad.org/adridg/bobulate/index.php?/archives/660-Enter-panic-mode.html' title='I moved my main workstation this morning, to plug it into the power meter [[ note to yoyo: the advantage of a hardware power meter is it doesn't force me to use Linux. Similarly, I can measure the total power usage of my workspace by ganging things together on a power bar through the meter. ]] and to bung in another 2GB of RAM, and in doing so the data connector for one of my hard drives just snapped off. That's the little plastic 9 (?) pin L-shaped thingy. The one on my boot drive. OK, it's just a boot drive, one 15GB partition on an otherwise unused disk, but it's still mightily annoying, not to mention fatal to my startup routine. Enter panic mode. Fortunately, the metal foil pins that were laminated on the plastic did not break off and were only bent a little. So I retrieved the snapped off bit of plastic and jiggled it into position next to the pins, then gently slid the cable-side connector (female) over the crumbling connector on the hard drive itself. It held. Fetch spare 250GB drive out of my box-o-components, and dd is running now. Exit panic mode. Speaking of box-o-components, free to a good home: 2x512MB DDR2 PC5300 SO-DIMM. Send me email and I'll drop 'em in a postbox for you.'>Adriaan de Groot (adridg): Enter panic mode</a></li></ul></li> </ul> </div> <!--/sidebar --> <div id="footer"> <!--recent comments start --> <div class="footer-recent-posts"> <h4>Recent Posts</h4> <ul> <li> <strong><a href="http://blog.guillermoamaral.com/2008/09/28/no-need-for-replacement/" rel="bookmark" title="Permanent link to No need for replacement">No need for replacement</a></strong><br /> <small>09-28-2008</small> </li> <li> <strong><a href="http://blog.guillermoamaral.com/2008/09/18/no-need-for-kphone/" rel="bookmark" title="Permanent link to No Need for kPhone">No Need for kPhone</a></strong><br /> <small>09-18-2008</small> </li> <li> <strong><a href="http://blog.guillermoamaral.com/2008/09/16/no-need-for-hell-dell/" rel="bookmark" title="Permanent link to No need for HELL… DELL">No need for HELL… DELL</a></strong><br /> <small>09-16-2008</small> </li> <li> <strong><a href="http://blog.guillermoamaral.com/2008/08/31/no-need-for-wordpress-update/" rel="bookmark" title="Permanent link to No Need for Wordpress Update">No Need for Wordpress Update</a></strong><br /> <small>08-31-2008</small> </li> <li> <strong><a href="http://blog.guillermoamaral.com/2008/08/24/no-need-for-dell/" rel="bookmark" title="Permanent link to No Need for Dell">No Need for Dell</a></strong><br /> <small>08-24-2008</small> </li> </ul> </div> <!--recent comments start --> <!--recent comments start --> <div class="footer-recent-comments"> <h4>Recent Comments</h4> <ul> <li><strong><a href="http://blog.guillermoamaral.com/2007/10/13/the-knotes-of-unrest/#comment-553" title="on The KNotes Of Unrest">Dom</a></strong>: Hehehe... After all this time I have yet again searched the ...</li> <li><strong><a href="http://blog.guillermoamaral.com/2008/09/28/no-need-for-replacement/#comment-544" title="on No need for replacement">Pavel Koshevoy</a></strong>: I had the same overheating/shutdown problem with an HP DV400...</li> <li><strong><a href="http://blog.guillermoamaral.com/2008/09/28/no-need-for-replacement/#comment-543" title="on No need for replacement">gamaral</a></strong>: The problem with this laptop was that the fan failed thanks ...</li> <li><strong><a href="http://blog.guillermoamaral.com/2008/09/28/no-need-for-replacement/#comment-542" title="on No need for replacement">Tony Murray</a></strong>: Usually when a laptop is having overheating issues like that...</li> <li><strong><a href="http://blog.guillermoamaral.com/2008/09/18/no-need-for-kphone/#comment-536" title="on No Need for kPhone">Dread Knight</a></strong>: :-) Sheep in wolf clothing... heh......</li> </ul> </div> <!--recent comments end --> <!--about text start --> <div class="footer-about"> <h4>About</h4> <p>This is the personal blog of <a href="mailto:me@guillermoamaral.com">Guillermo Antonio Amaral Bastidas</a>, the views expressed here are my personal views, not the views of my employeer or the <a href="http://www.kde.org/">KDE project</a>. </p> <p><a href="http://www.google.com/search?hl=en&q=gamaral+guillermoamaral">Follow me on the net.</a></p> </div> <!--about text end --> <hr class="clear" /> </div><!--/footer --> </div><!--/page --> <!--credits start --> <div id="credits"> <div class="alignleft"><a href="http://www.ndesign-studio.com/resources/wp-themes/">WP Theme</a> & <a href="http://www.ndesign-studio.com/stock-icons/">Icons</a> by <a href="http://www.ndesign-studio.com">N.Design Studio</a></div> <div class="alignright"><a href="http://blog.guillermoamaral.com/feed/" class="rss">Entries RSS</a> <a href="http://blog.guillermoamaral.com/comments/feed/" class="rss">Comments RSS</a> <span class="loginout"><a href="http://blog.guillermoamaral.com/wp-login.php">Log in</a></span></div> </div> <!--credits end --> </body> </html>