Wed 27 Feb 2008
I’ve watch a very interesting presentation about Aspect Oriented Programing. I didn’t knew exactly what it was but I find that this is a a very interesting approch.
This is not a revolution, it’s more like somting added to the classical object oriented programing. I’m wondering if this king of mecanism can be added to a classical C++/Java/C# project without changing everything (compiler, IDE, other libraries,…) just by adding a new library or something like that…
Sun 24 Feb 2008
This weekend I’ve been working on a Akregator’s synchronization tool.
I’ve made some samples for the user interface that would manage and trigger this feature in Akregator. For the moment there is not much thing. Nothing really works and nothing is integrated yet but I’ve tried to think about something easy to use and consistent with other KDE tools.
Here are 2 screenshots of the GUI I’ve made (inspirated by Digikam camera management tool):
Wed 20 Feb 2008
I’ve begun a project on KDEPIM/Akregator.
This is a module aiming at synchronizing Akregator with online readers.
I created a wiki page to detail the project specifications: kde:AkregatorAynchronization in the Wiki
Wed 20 Feb 2008
UseIt.com has released a very good article on a application usability:
It’s hard to write a general article about application design mistakes because the very worst mistakes are domain-specific and idiosyncratic. Usually, applications fail because they (a) solve the wrong problem, (b) have the wrong features for the right problem, or (c) make the right features too complicated for users to understand.Any of these three mistakes will doom your app, and yet I still can’t tell you what to do. What’s the right problem? What are the right features? What complicating curlicues can safely be cut from those features? For each domain and user category, these questions have specific and very different answers.