Today KDE released updates for its Applications and Development Platform, the second in a series of monthly stabilization updates to the 4.13 series. This release also includes an updated Plasma Workspaces 4.11.10. Both releases contain only bugfixes and translation updates, providing a safe and pleasant update for everyone.
More than 40 recorded bugfixes include improvements to Personal Information Management suite Kontact, Umbrello UML Modeller, the Desktop search functionality, web browser Konqueror and the file manager Dolphin. A more complete list of changes can be found in KDE's issue tracker.
Additional and noteworthy: this release of KDE Applications includes a number of important fixes for Kopete: a decrease in the exit time of Kopete with enabled statistics plugin, a fix for the compilation of jabber libjingle for non x86 architectures and another fix for voice call support in the jabber libjingle library. Without this last fix, voice calls worked only with the old Google Talk windows jingle client. Now after applying the patches it was tested with GMail web plugin, old Google Talk windows client, telepathy-gabble and other Kopete versions.
To find out more about the 4.13 versions of KDE Applications and Development Platform, please refer to the 4.13 release notes.Dot Categories:
Ya está disponible la nueva entrega del informe de KDE e.V. Quarterly Report de 2013, en decir, una pequeña revista trimestral que nos proporciona una visión oficial de algunas de las cosas que la Comunidad KDE ha hecho durante estos últimos meses. Cuarto informe de 2014 de KDE e.V. Quarterly Report Estos informes son [&hellip
Una de las metas de la Comunidad KDE es aportar software de calidad para cada una de las necesidades, desde las más básicas a las más específicas. Knowthelist, el reproductor de música para fiestas, es un gran ejemplo. Knowthelist, el reproductor para DJs de KDE Si en la actualidad quieres montar una fiesta y deseas [&hellip
Como ya he comentado en otras entradas, KDE participa de forma muy activa en el programa Google Summner of Code (GSoC) mentorizando diversos proyectos: KDE Telepathy, digiKam, KDE Edu, etc. Hoy quiero comentaros un proyecto del programa enfocado en Marble. Proyecto GSoC 2014 para Marble Uno de los proyectos del GSoC 2014 para KDE [&hellip
La personalización de KDE va más allá de los aspectos gráficos (fondos de pantalla, iconos, decoraciones, etc). También podemos configurar el comportamiento del ratón, los atajos de teclado e, incluso, los menú contextuales que aparecen pulsando el botón derecho del ratón. Esto último se realiza mediante los service menu, como el que hoy anuncio una [&hellip
Una de las novedades presentadas en el último congreso de Apple ha sido la transferencia de archivos entre su sistema operativo para móviles iOS 8 y su sistema operativo para portátiles, Mac OS X Yosemite. Una gran novedad que los usuarios de KDE hace tiempo que disfrutan gracias a KDE Connect. Transfiere archivos con KDE [&hellip
Today KDE makes available the third beta of Frameworks 5. This beta release is part of a series of pre-releases leading up to the final version planned for July 2014.
This beta features multiple bug fixes, and the finishing touches required to ease the transition for developers to the newest iteration of the KDE Frameworks. This process has included contributions back to Qt5, the modularisation of the kdelibs, and general improvements to the components that developers can use to improve their applications and user experience. This pre-release improves co-installability with kdelibs4 and with future versions of KDE Frameworks (i.e. 6). This is also the first release with translations for Frameworks using the KDE's i18n translation system.
For more information about Frameworks 5, see this earlier article on the KDE News site.Dot Categories:
Algo tenía que escribir al respecto. No es que sea una cosa de importancia, pero sí que es una cosa de la que me gusta dejar constancia. Tal día como hoy hace 3 años comenzaba la aventura de Caledonia, mi primera incursión seria en el artwork (especialmente para KDE). Probablemente lo que considero el mejor logro hasta el momento, tanto en éxito como en longevidad. Concretamente hablo del tema plasma sobre todo, un tema que evolucionó mucho desde que nació como un fork del tema “Ember” de Garth Johnson hasta que fue tomando forma de manera muy seria. La consolidación del estilo no sería hasta las versiones 0.9.x y sobre todo la 1.0, sacada en abril del 2012. Hay temas plasma más antiguos, por supuesto, pero Caledonia siempre ha estado ahi, actualizándose en tiempos apropiados para mantenerse actualizado e ir afinando aún más el diseño y el estilo.
Desde que lo comencé no lo he abandonado nunca, ni siquiera en su uso (llevo todo este tiempo usándolo ininterrumpidamente, y jamás me aburre, otro logro más viniendo de mi). Y es que ya no sólo eso. Siempre creí que Caledonia llegó en el momento justo para KDE ante la ausencia de temas muy trabajados por aquel entonces (sobre todo oscuros), y que silenciosamente abrió alguna que otra puerta hacia nuevos trabajos de otra gente, ya sea porque ha inspirado, porque han derivado cosas de él, o porque sencillamente siempre procuró innovar y aportar como tema “amateur”. Fue de los primeros en experimentar con un estilo más plano por pura estrategia visual cuando éste no gozaba de popularidad, y me atrevería a decir que el primero con gran éxito (ya por aquel entonces se decía que se veía “muy GNOME” y que algo tan plano no pegaba con KDE… cosas de la vida, ahora Plasma Next y algunos de los temas plasma más exitosos siguen la misma línea o incluso más radical…). También ostenta el título de haber sido siempre el tema con más iconos monocromo dedicados (a día de hoy ya alcanza las 200 compatibilidades), añadiendo soporte para aplicaciones de terceros, aplicaciones de las que no constaba en ningún lado que tuvieran compatibilidad (conseguido a base de ensayar, explorar y probar), e incluso pionero en alguno de ellos como Plasma-nm o KDE Connect, pedido bajo demanda a Albert Vaca. En general, es una enciclopedia andante de todo lo que un tema plasma puede personalizar (y aún no lleva todo lo que quiero…).
¿Cifras? Muchas. Y la verdad es que me sorprenden un poco. Desde sus comienzos, entre KDE-Look, Sourceforge y DeviantArt (cuando por aquel entonces también se podía obtener desde ahi), se ha descargado nada menos que más de 100.000 veces (perdí la cuenta en esa cantidad), sin contar las descargas que son imposibles de cuantificar, como los paquetes en las distribuciones o cualquier otro medio. También veo como un logro el haber salido del “mercado” español e hispanoamericano para que países como EEUU o Alemania sean los primeros en descargas y usuarios del tema. En fin, para lo poco que he contado, ya es bastante.
Ahora no es un tema que goce de tanza popularidad, pero creo que no me importa mucho. Incluso casi lo prefiero asi. Se ha convertido en un tema clásico, elegante, sobrio, atemporal, con sus fans, usuarios y hasta fanáticos (me los he encontrado por el camino) a los que les debo esa fidelidad. No es un tema que busque la aprobación de todos, siempre ha sido un proyecto muy personal, hecho más para consumo propio y dejar constancia de mis ¿pequeñas? locuras que para contentar a la gente. Y asi ha salido. Como he dicho, creo que ya se le puede llamar “clásico”, fiel a su estilo, fiel siempre a renovarse en los detalles y fiel a seguir aumentando compatibilidades. Para que podamos seguir usándolo al menos otros 3 años ininterrumpidamente…
Y por supuesto, gracias a los que siempre estáis ahi con él. A todos esos que habéis contribuído las cifras, y en concreto a las más de 7.600 descargas que ha supuesto la última versión, la 1.6.2, lanzada hace unos dos meses. Eso es lo que demuestra esa fidelidad. Una silenciosa fidelidad efectiva. No necesita más ruído para hacerse más popular. No necesita competir con nadie. No necesita copiar a nadie. No porque sea lo mejor que se haya hecho, sino porque es un tema que cuando lo ves y lo usas es inconfundible. Al menos yo distingo un escritorio con Caledonia a kilómetros de distancia. Y eso me basta: estilo y escuela propios.
From January 18th to 25th, Kate, KDevelop and Skanlite developers met in Barcelona. The sprint was focused on the work of the upcoming few months, and covered a wide range of aspects of these projects.
left to right, back row: Kevin Funk, Gregor Mi, Dominik Haumann, Christoph Cullmann, Milian Wolff, Joseph Wenninger
front row: Sven Brauch, Aleix Pol, Heinz Wiesinger, Miquel Sabaté
One of the big initiatives that the developers have been working on recently is the KDE Frameworks 5 migration. During the sprint, Kate's port to Frameworks 5 matured while KDevelop received its first push towards the adoption of the new Frameworks. This is an important step because it lets the team think ahead about adopting the technologies that will be developed on for the next years.KDevelop
KDevelop also improved on the supported languages front. The new KDevelop Clang plugin got a big push, and, while it is not going to be released yet, it is expected to supersede the current C++ plugin in the long term. Clang is expected to improve the support for standard C++, and also offers an opportunity to support C projects properly. Eventually, an Objective-C plugin could be built on top of Clang. Clang integration reduces the maintenance burden compared to the self-written C++ parser. During the sprint, we carved out a roadmap for the Clang plugin and also extended what we already have so far. The main focus was on polishing infrastructure inside KDevelop for providing a solid base for integrating Clang's useful diagnostics and fixits module.
Currently, the kdev-clang plugin consists of only about 4000 lines of code, compared to nearly 55000 in the old plugin. Further good news—there will be a Google Summer of Code 2014 project that will take care of delivering a first releasable version. There's still *a lot to do* to make this as usable as the previous C++ support plugin. Read more about kdev-clang.
KDevelop's code assistant popup has gotten a revamp, which will -- after some polishing -- provide a more flexible and better integrated UI for the assistant features. The useful "blame" feature, which shows who touched each line in the current file as provided by the project's VCS, was improved as well. It now shows the commiter's name instead of the commit identifier and also works properly with dark color schemes. KDevelop's interface is now more customizable, toolviews can be detached (for example, source code documentation can be detached from the main window and moved to another screen). KDevelop's codebase was cleaned up and quite a few optimizations were added. This and other improvements will give a noticeable performance boost when operating on large projects consisting of thousands of files.
Find out quickly who the writer is Python
Much internal cleanup was done in Python support and some long-standing bugs were fixed, such as the debugger not working properly. Python 3 support is now finished, and future development will focus on that.Ruby
The KDevelop Ruby plugin was also greatly improved during the sprint. Lots of bugs have been fixed and a first stable release is closer now.PHP
The sprint also provided a good opportunity to improve the language support within the PHP plugin. A lot of progress was made on completing syntax support for the new features introduced by PHP 5.4. Most notably there is now full support for PHP's trait syntax. While catching up with newer syntax features is important, so too is improving support for older features. One of the most requested improvements for the plugin is proper support for PHP's namespace syntax. During the sprint we worked on making this a lot more usable. However, there are still some kinks to be worked out.Kate
For Kate, the focus was mostly on the Frameworks 5 port. The port already started back in December 2013, resulting in the KF5-ready KTextEditor framework and stable KF5/Qt5 versions of the Kate and KWrite applications. During the sprint, the Kate team worked on a lot of details, polishing the KTextEditor framework.KTextEditor Interface Cleanup
The KTextEditor interfaces are responsible for all the interaction between the editor component Kate Part and the host application (eg. KDevelop, Kile, Kate, ...). So it is important that these interfaces allow good integration of the editor into the host applications. During the sprint, these interfaces were cleaned up and optimized for speed. In addition, the default colors were extended to allow for better color schemas in the future.New Status Bar
Previously, Kate Part did not provide a status bar. All host applications (KDevelop, Kile, ...) had to write their own variant of a status bar, displaying the cursor position and similar information. In the KTextEditor framework, Kate Part will ship a default status bar, showing the cursor position, the edit mode, the modification state, the highlighting, encoding and the indentation settings. Further information can be found in this blogpost.KTextEditor Plugin Architecture
KTextEditor's plugin architecture was improved substantially. Plugins written for the KTextEditor framework will be available in all applications embedding Kate Part, making it possible to share a lot of features such as collaborative editing, search & replace in multiple files, and similar tools. This is possible because the plugin interfaces are now much more powerful than the former interface for shared plugins.
As a byproduct, the Kate application interfaces were completely dropped in favor of the KTextEditor plugin architecture. Most of the Kate plugins are already turned into KTextEditor plugins, such as the Documents sidebar, the Filesystem Browser, Search & Replace, the Build Plugin, the Backtrace Browser.Kate Application Changes
The Kate application saw several changes; among the most visible is the new built-in tab bar. Previously, Kate provided the Documents sidebar to navigate through files. The Documents sidebar has the advantage that it stays usable when working on a large number of files. However, a lot of users want an integrated tab bar for quick file navigation. Therefore, the Frameworks 5 version of Kate will have both—the Documents sidebar as well as the tab bar. Since the number of visible tabs is often limited, only the tabs that were most recently used will be displayed. Users will be able to navigate quickly through the files being worked on. Besides quick navigation, the tab bar also allows the view to be split the view vertically or horizontally, to show the quick-open view, and to maximize the currently active view by hiding all other view spaces. A preliminary version of this tab bar as well as a KF5 version of Kate is described further in this blogpost.vi mode
Kate's vi input mode also gained several improvements and polishing.Wrap-up
All in all, a lot of work was done under the hood in both Kate (detailed sprint wrap up report) and KDevelop. The Kate developers are still improving and extending the KDE 4 version of Kate, KWrite and Kate Part, while the KF 5 port is being finalized. The KDevelop team started porting to KF 5 as well, but continues to improve the KDE 4 version in the meantime. A major effort is being made to rework KDevelop's C++ language support to be more reliable, powerful and easy to maintain in the future.Thank you
Thanks to Blue Systems for hosting the Kate+KDevelop sprint in Barcelona! Your support is greatly appreciated!Dot Categories:
Las II Jornadas Libres del 2013-14 fueron presentadas el 7 de octubre en un acto sencillo en la UNED de Vila-real. Tras 14 charlas y talleres llega al fin su segunda edición (la tercera está en el horno). La última charla será sobre uno de los proyectos más extraordinarios de la Comunidad KDE: Plasma Active. [&hellip
Though the Krita team was one of the first to start the tradition of having sprints, with the first Krita Sprint in Deventer, in 2005, Krita sprints are rather infrequent! But, of course, we also meet each other during the more regular Calligra sprints.
Anyhow... Krita developers and artists met again in Deventer in May 2014. It was the most awful weather you can imagine for a sprint—warm, sunny, bright, lovely to be outside! Long and lazy lunches, discussions out on the roof terrace until after midnight, walks through the park. Is it a wonder nothing much got done?
Wait, that's wrong! Bravely resisting the lure of the fine spring weather, three artists and six developers got down to some serious work! In the week before the Krita sprint, Boud, Dan, Arjen and Stuart already had a week-long sprint working towards the final release of Krita Gemini on Steam, and on Thursday the others started to arrive. And only by Tuesday the house was empty again...
Krita Sprint Team Let's see what got done:
We've been working on the Krita 2.9 Fund Raiser since April. It took more work than we'd ever imagined, but now we've got a great promo video thanks to Björn Sonnenschein, and together we set up and created the Kickstarter campaign. We've got ambitious goals here: not only do we want Dmitry to go on working full-time on Krita, we want to extend that and have Sven (who's been a Krita hacker for over ten years) work full-time on Krita, too. And if we exceed that goal, well, there's OSX to conquer! Stay tuned, we expect to go live really soon now!
Krita 2.9 will probably be the last release based on Qt4 and KDE4. It's a huge and ambitious release, with the fund raiser being based around 24 ambitious goals and then -- we also want to finish the resource bundle manager that Victor Lafon from Toulouse started and make it possible to have more than one image open in a window. After the 2.9 release, it's time to port to Qt5 and KDE Frameworks 5. We spent some time discussing which tiers from the Frameworks we want to use, and how to best approach the port.
With the interest in Krita growing by leaps and bounds—the Windows installer has seen more than half a million downloads—interest in translations is growing, too. It takes some effort to get the volunteers who want to work on translating Krita to push their efforts through the right channels, but that is working out well. And Dmitry Kazakov is in close contact with the Russian translation team. We discovered that Krita's terminology is a bit of an organically grown mess, and that there are many places where context is missing. So we decided to get Dmitry together with Alexander Potashev and Paul Geraskin in Russia, and they would go through Krita, figure out what needs fixing, and fix it. That effort is underway right now, and might already be merged by the time you're reading this.
The Krita Foundation was created to support the development of Krita by, well, actually paying for development. Time is money, and money gets us time, and accelerated development. Thanks to a big sponsor, Dmitry has been able to work full-time for the entire development period of Krita 2.8. The Foundation is pretty healthy, with money coming in from donations and sales of the DVD, as well as the Krita Development Fund, but we still want to grow and do more and more!
During the sprint, we got mail from Blender's Ton Roosendaal, proposing to cooperate on having a stand at SIGGRAPH 2014, the foremost conference and trade show for graphics. We've found at least one sponsor, and have already reserved some floor space. Now we need to furnish it and find money to travel to Vancouver. It's an awesome opportunity to be the first KDE project to show off at SIGGRAPH!
Last sprint, in Amsterdam at the Blender Institute in 2011, we sat down our attending artists and made them work with Krita for half an hour, videotaping and recording their work. They were allowed to gripe and whine to their hearts' content, and the developers were allowed to listen and make notes and fix Krita! Back then, Krita 2.4 hadn't been released yet, and Krita was, in the words of one of the artists, a very nice amateur application for amateur artists, but not suitable for production work. Well, we've come a long way! Sure, one artist made Krita crash (and we fixed the crash within fifteen minutes...), but there was almost no whining, no griping, people could just draw and paint. Still, Dmitry's notes were extensive, and we've got work to do!
One thing that's missing is a book on Krita. Wolthera is busy with the manual on userbase and Timothée Giet has proposed to organize a book sprint for Krita. He is currently investigating whether we can get a subsidy for the book sprint!
Yes, in the end, we did enjoy the sunshine, too... It turns out that our lunches were just as productive as the meeting and the hacking sessions, and it's true about the late nights on the roof, where we were busy sketching, painting, hacking, discussing and planning.
Thanks are due to KDE e.V. who sponsored travel for our hackers and artists! The Krita Foundation paid for the t-shirts. We managed to mostly fit into my place in Deventer, which helped keep the accommodation costs down. It was an awesome sprint, and we're going to make Krita better, better and better!
The KDE Applications 4.13 announcement highlighted the delightful new capabilities of Palapeli, the KDE jigsaw puzzle application. What the announcement did not mention is that the Palapeli maintainer, Ian Wadham, is celebrating 50 years of software experience. He’s ready to hand off Palapeli and his other KDE software development responsibilities. Albert Astals Cid called attention to Ian’s achievements and suggested a Dot interview.
A Portrait of the Programmer as a Young Man
Ian Wadham's bio at a glance
- 1938 - Born in England
- 1959 - Graduated in Physics and Mathematics at the University of Cambridge
- 1960 - Migrated to Australia
- April 1964 - Became a computer programmer 50 years ago
- KDE Games developer for about 12 years
- Currently lives in Melbourne, Australia
What are your thoughts about cutting back on software development?
Regret, but I have had a long innings. I will still potter around on my own, but not following any schedules. If something turns out well, I might commit it.
This is my second retirement. My first, from the workforce, was in 1998. This time I am withdrawing from writing programs for public use. I will continue to present a Science course for seniors at the local U3A (University of the Third Age) .
I seem to be getting involved in moves to make KDE's portability work better on the Apple Mac OS X platform. And my grandchildren are always a joy.
How did you get started as a coder?
I prefer to call myself a programmer - and never a hacker. A hacker is someone who carves wood with an axe. I see programming as a craft. Sometimes I hack, to get a quick answer to a question, but when I have the result, I always like to go back and program it "properly". If I do not, I find I cannot understand my own code a few months later.
How I started was one of those accidents of fate. My Ph.D. studies were not working out and I was looking for a new career. My girl-friend at the time was a programmer and she told me no qualifications were required, only an aptitude test, and that the job was interesting and the pay excellent. This was 1964 and I was nearly 26.
So I put in some applications and accepted the offer of my first programming job the night before I was interviewed as a Physics Instructor in the Australian Navy. All next morning I was saying that I had already accepted another job, but the military has its own ways of doing things. I went through the full medical check, the eye test, the IQ test, the psychology interview... Finally I entered a room with a long table and wall-to-wall admirals and captains - gold braid everywhere - and was finally allowed to deliver my news. "Oh, thank you for telling us," they said.
At that time in Australia, very few physicists were using computers. Computer use was more common in the US, UK and Europe, especially in large, well-financed organizations such as NASA, the Atomic Energy Commission and the US Military.
Computers for individual physicists were an exotic and trendy means of avoiding lengthy and tedious calculations, if you could afford the time and money to acquire one and learn how to use it, but were not yet a routine tool as computers became within the following 10 years.
What major technology shifts have you been involved in?
You name it. It was good luck to join in when transistor hardware, assembly language and Fortran II were taking hold. Some people were still using valve machines and machine language. As a programmer I was involved in the beginnings of operating systems, real-time systems, on-line screens, minicomputers, structured programming, supercomputers, LANs, desktop systems (Xerox Star), relational database systems, C and multi-host commercial Unix systems.
The best company I ever worked for was Control Data Australia, 1965 to 1969. We have a website of memories, and we still keep in touch. On 17 May, we had a biennial reunion. I do not know of any other company group like it.
Control Data Corporation, our US parent company, made the largest and fastest computers in the world. Our chief designer was Seymour Cray and for decades he designed the world's largest and fastest computers: later in Cray Research, his own company. At Control Data he insisted on seclusion and freedom to work in his private laboratory in his home town, Chippewa Falls, Wisconsin. There were many legends about him. One of my favorites is that each morning he would walk down to the river near the Falls and an eagle that nested there would fly down and perch on his shoulder.
CDC-160A Personal Computer
My first computer was one of Seymour's lesser-known designs, a Control Data 160-A. The desk in the foreground is the entire machine. Some say it was the first minicomputer, even the first PC. It was significant too because essentially the same design, shaped as a 20cm cube, went into the ten peripheral processors on the CDC 6600 supercomputer. The 160-A was a wonderful first machine because it was possible for one person to learn everything about it - something that has been impossible with most machines since.
This was your "personal" computer? Wow!
Er, no! I was a young, penniless guy and it cost US$60,000. I meant it was the first computer I worked on, not the first one I owned. It belonged to Australia's telephone research labs and I was programmer in charge, bureau manager and general dogsbody. If I stayed late at work, I could have a play...
KDE is my only official FOSS project, but I feel that, by avoiding the IBM and Microsoft worlds, I have been able to work on FOSS all along. Free because it came with the hardware and you could modify it or fix bugs (i.e. also free in the Stallman sense). In the 80s and 90s you could still obtain access to source code (UNIX) on minis and megaminis for a fee, but I never found the need.
How did you come to KDE? And how long have you been part of KDE?
Microsoft and its business practices had always turned me off. My first IBM compatible PC (1995) was mainly for work purposes. After retiring in 1998, I started programming again in 2000. My son gave me a set of SuSE CDs for Christmas and it included this new desktop system called KDE 1.
Among the source code, in the Alpha section, I found the first version of KGoldRunner, by Marco Krüger. I had always liked Loderunner's unique combination of action, strategy and puzzle solving and had always wanted to do something non-trivial in object-oriented programming, ever since Simula and Smalltalk days. So I set to work to learn C++ and Qt and with Marco's permission produced a new version of KGoldrunner, committed to kdenonbeta (a precursor of playground and review) in March 2002.
Akademy is being held this year in Brno, Czech Republic. Have you been to Akademy?
Yes, Akademy 2008 in Belgium. The talks were great and so were the BOF sessions on games. That Gouden Carolus beer on the river trip and on the dinner night at the brewery in Mechelen was something else again. I now know it to be one of the world's most powerful beers - and they were serving it in half-litre glasses! The high point of Akademy 2008 for me was to meet my fellow workers on KGoldrunner and take them to dinner in the main square at Mechelen.
You maintain several KDE applications, mostly games. What are they?
KGoldrunner, Kubrick, KJumpingCube, KSudoku and Palapeli. They are about 13% of the KDE Games, but 20-25% of the lines of code.
KGoldrunner is based on my all-time favorite game: Loderunner. One intriguing thing about it is the way bugs become features. One day I was sitting with my son (grown up) when he found out that it was possible for the hero to dig holes while falling through the air. Before I could fix the bug, he had made up a level that exploited it. Now that "feature" is an important part of many creative new games that people from around the world have contributed.
Kubrick was an effort to branch out into 3-D and OpenGL. It's fine, but I am no good at cubing and I wonder if others enjoy Kubrick.
KJumpingCube and KSudoku I rescued from unmaintained. In KJC I added features and AI to make it more intelligible and also more challenging. In KSudoku, there was a half-finished re-development which left it so that it would generate mainly easy puzzles - no good at all for a serious player like my wife. I found a Python puzzle-generation algorithm on the net and, with the author's permission, adapted it to C++ and KSudoku. I like KSudoku because it supports so many variations on the basic puzzle. I do not know of any other Sudoku game that does that.
My favorites games to play are KPat (solitaire card games), KSudoku (X and Aztec variations) and Palapeli.
You've gotten the applications into good shape, and are ready to hand them off. What type of person would you like to see take over? What will they get out of working on these applications?
I would like to see KDE set up a maintenance group and standards for "maintainability" of code. Programs that reach a reasonably good standard could then be maintained interchangeably by members of the group.
The group could be continually changing. Nobody can stay interested in such work for long. Also the group and its stock of programs would be a good source of Junior Jobs and a place for newbies to start. It would need to have some experienced members, or ready access to such people, because some bugs are too hard for trainees to solve.
This is not a new idea. It is roughly what has been happening everywhere I have worked since about 1967, when the burden of people quitting jobs and leaving behind unmaintainable, half-finished messes became intolerable for most organizations.
What was your experience in the various game transitions from early days to now? Did you play computer games when they were first available?
Games go back a very long way. Some of the earliest computers played music and a few played games. I remember a fellow-student in 1959 giving me a copy of a paper tape as a souvenir. It contained an EDSAC II program to determine if the king was in check.
Even the first supercomputer, the Control Data 6600, in 1966, had a game similar to KSpaceDuel (spaceships orbiting the Sun and shooting missiles). Only the elite and hardware engineers got time late at night to play games on those multi-megadollar machines.
Things became easier with minicomputers. In 1978 I was at a customer's DEC PDP-11 site presenting a new version of their application system and was asked to finish up early. Why? It was the night the users all got on the computer to play Adventure, the original adventure game. They had made a wall-chart mapping out all the caves.
On our first PC, an Apple IIC, my children and I played a lot of Loderunner and Zork ("You are in a maze of twisty little passages, all of them alike."). That was in 1983. We wore out several joysticks on Loderunner. We made up levels and challenged each other to solve them. Many of the current KGoldrunner levels come from that time. My Apple IIC still runs and can still play the Loderunner demo, but I used up the last gasp of the last joystick working out design details to be used in KGoldrunner. So I cannot play Loderunner now.
Later I had a Commodore Amiga 500 and became very hooked on Flood and Populous I and II. The Amiga had much better graphics and OS than the IBM PC and Windows, but sadly the Commodore company lost its way. My Amiga also is still in working order.
Later still, on Windows, I worked my way through Myst, Riven and Alpha Centauri. I never liked first person shooters, though.
You've added a lot to Palapeli, the jigsaw puzzle application. The new capabilities make it possible to do puzzles with a lot of pieces. It's fun and challenging. The manual is quite helpful, especially with a lot of pieces. What was the thought process to create the latest version?
Several of us in the KDE Games group had kicked around ideas in 2010. Johannes Löhnert wrote the puzzle Preview class then, but it did not get implemented.
The Book by Juan Gris in Palapeli; 320 pieces; main screen, right edge piece-holder, preview
It seemed necessary to resolve the issues with a practical test, so I bought a 1000 piece puzzle and tried to solve it on a small table, no larger than the completed puzzle, using only the table and the box to hold pieces. As I played, I noted difficulties that arose and how they could be overcome. At the same time, I was mentally trying out analogues of what might be feasible on a computer screen. And of course, I had already tried solving large puzzles with Palapeli 1 and had seen what physical difficulties arose there.
Most of the manual was already written by Johannes Löhnert and Stefan Majewsky. I just added the chapter on large puzzles.
When I was growing up, we often had a jigsaw puzzle on the dining room table. It was a social event. What about adding a capability for working with others on a puzzle with a lot of pieces?
That's a nice idea. I have never understood how networking is done in KDE Games. Maybe it is time I found out.
It's hard to beat the computer at KJumpingCube. Do you have any strategy tips?
Only what is in the Handbook. KJC is about to become harder. Inge Wallin has an AI library he would like to try out on it. You have met the AI players Kepler and Newton. Prepare to meet Einstein!
What would you recommend to young programmers?
Read as many of other people's programs as you can - even bad programs. Try and figure out what makes them good or bad, easy or hard to understand and maintain.
Can people learn to program when they are older?
Yes. My friend Glen, a retired airline pilot, taught himself on an IBM PC when he was fifty something. Within a year or two he became good enough to get work as an independent contractor.
Windows, Mac or Linux? Why?
Apple Macbook Pro, with OS X 10.7, Lion.
One day my Windows/Linux dual-boot system's hardware died suddenly. I bought a new machine and installed the latest OpenSuSE. When I booted up KDE, my carefully constructed four-part Plasma desktop had been long gone, and I found myself in some new, empty and quite alien-seeming version of KDE and Plasma. It took me two days just to find out how to get rid of the blue glow around active windows, which was hard on my tired old eyes.
Ian Wadham - older, wiser, still gaming
It was important for me to keep working rather than play with settings, so I turned to the MacBook I had been messing around with, which was also supporting my wife's iPhone and iPad (pre iCloud). I had some KDE and Qt software already installed, with MacPorts, and I was soon able to set up a KDE development environment. OS X really is quite a lot like Unix and Linux.
I like working on the Macbook. The desktop is quiet, unobtrusive and easy on the eyes. I can work for hours without getting tired or being distracted. Also the battery is long-lived, Time Machine does regular backups and the Spotlight indexer collects everything (even my source code) with no perceptible overhead. I feel I am more productive with Mac OS X than I ever was with Windows or KDE because I do not have to think about what the desktop is doing.
I feel as if I have come home.
The traditional KDE interview question—Richard Stallman or Linus Torvalds?
Thank you for the many years of work you've dedicated to the advancement of FOSS, and the KDE games in particular. Thanks also for sharing some of your experiences on the front lines of computer development over the fifty years of your active career.
Many thanks to Albert for the idea of interviewing Ian, and to Bob Potter for bringing in technical perspectives.Dot Categories:
In this week's KDE Commit-Digest you can find an interview with Aaron Seigo about KF 5 and a look into KDE SC on devices. And of course, the overview of the development effort is there as every week and includes:
- Ktexteditor adds keyword-based completion model
- Smb4k changes the implementation of notifications correctly, as a side-effect the notifications can be edited via system settings
- libtmdbqt adds basic tv show support.
Las grandes posibilidades de personalizar nuestro KDE es una de las bazas con las que contamos a la hora de defender nuestro escritorio libre favorito. Hoy os presento Ardis, otro pack de iconos redondeados original, coloreado y eleganante, una alternativa a Flamini, del cual ya hablé en el blog hace unos meses- En KDE todo [&hellip
No es el informe semanal de KVDG pero Jens, como nos prometió, ha publicado una entrada comentando las novedades que se quedaron pendientes por publicar del trabajo del grupo de diseño. Concretamente el trabajo en las preferencias del sistema de Plasma Next, así como las decoraciones de las ventanas. Progresos en las Preferencias del Sistema [&hellip
Una de las forma de promoción más efectivas es la de realizar concursos, y eso lo saben en SUSE. Y es por ello que acaban de lanzar un pequeño concurso para promocionar openSUSE a través de su mascota, Geeko. Concurso: ¿Dónde está el camaleón? Para presentar el concurso me voy a hacer eco de la [&hellip
La cantidad de blogs sobre gnu/linux que existen son numerosos y variados, no obstante nunca está de más conocer nuevos proyectos como Planet Linux, un sitio al estilo de Planet KDE o Planet KDE Español, pero como es de esperar mucho más diverso. ¿Qué es Planeta Linux? Como es habitual, lo mejor es que los [&hellip