https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/amarok/ Recent content in Amarok on Nikhil's blog Hugo -- gohugo.io en-US Sat, 21 Aug 2010 00:41:00 +0000 https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/final-evaluations-results-processed-for/ Sat, 21 Aug 2010 00:41:00 +0000 https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/final-evaluations-results-processed-for/ Hi Nikhil Marathe, We have processed the evaluation for your project named Amarok and KDE UPnP Integration with KDE. Congratulations, from our data it seems that you have successfully passed the Final Evaluations. Please contact your mentor to discuss >the results of your evaluation and to plan your goals and development plan for the rest of the program Greetings, The Google Open Source Programs Team Yay! Posted via email from nikhil's posterous https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/upnp-searching/ Sat, 17 Jul 2010 18:40:00 +0000 https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/upnp-searching/ I’ve been pretty quite about GSoC progress. But I had a great time at aKademy and forgot all about blog posts. So the current status is thus. If programming was just about getting things done, I am done! But its not, which means although everything I was supposed to do is done in a big picture way, the next few weeks will see bug fixes, optimization and ensuring that certain things can be done faster, more accurately or in a more user-friendly manner. https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/gsoc-week-4-experimenting-with/ Fri, 11 Jun 2010 16:11:00 +0000 https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/gsoc-week-4-experimenting-with/ I didn't write a post last week, and it looks really bad in my form completion :) but I didn't have any user visible updates at all. This week is much better. First the visual then the text. That's cover art fetched from the UPnP device when the Content Directory has it available! Other updates include smoother full and incremental scanning of the Collection. This is one area which needs a lot more improvement. https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/how-bug-reporting-should-be/ Fri, 21 Dec 2007 16:49:00 +0000 https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/how-bug-reporting-should-be/ Amarok has the best way of reporting a bug. Whenever Amarok crashes it launches a KMail compose window with full debug information filled in and adressed. Which means you just click send. This is way better than having to go to the project's bug tracker and create an account - the worst part - and then submit a bug. I wish all of KDE ( and others ) went this way.