Category Archives: Personal

Update on the Open Source Bluetooth Watch Initiative

It has been more than month since Open Source Bluetooth Watch Initiative first announced.There has been some improvements.Hardware side of the project completed.But there is a lot to do on the software side to make it a nice developer-friendly watch.So i started programming an API for the watch.But this last month has been very very busy for me.But still there has been somethings done.

Hardware Updates :
5 pushbuttons added for navigation.
Tilt-Sensor added.

Software Updates:
I designed watch UI on top of Vertical Screens called Widgets.In these Widgets, we’ve got buttons , labels etc.

There still some lacks & issues to solved.As soon as i have some free time i will work on those and release source code with Android & Maemo Apps. to talk to watch.If there is anything about the code that is bothering you please dont hesitate to comment or contact me :) .Suggestions are welcome.

Here is a scheme of the Class Structure:
Continue reading

Maemo5 Apps those compete with Responsive & Userfriendly UI of Android – 1

Hi my fellow readers,

It has been quite a while since i switched to N900 from my old smartphone the N95.And finally im finding some Apps with very nice UIs and features.
Continue reading

My new Development Board : MSP-EXP430FR5739

Hi everybody,

I just got back home from Sakarya. One of the reasons i came back to Istanbul this weekend was a delivery received from Farnell. It was the MSP-EXP430FR5739 Experimenter Board :) . As soon as i came home , i reach the shipment box and opened it. I was already very excited about this board whole week. This development board is going to be a complete new journey for me after my long journey with the Arduinos… anyway enough with the chit chat :)

Lets get into some detail… Why i choosed this board?
You might have already noticed my interest in motion-controlled apps & technologies. It was first started with the Nokia Symbian smartphones with built-in accelerometers.I developed two apps for those devices one called AlertMe and the other was nGUN. I also developed some experimental apps too which are not released for public use. I kept experimenting with accelerometers on my N95 with Python s60 on the go. It is fun and very entertaining to play with accelerometers.

Continue reading

Quadrotor… Long story short…

Hi fellows

Actually it is quite late to blog about this.. But i think at least i can share the materials rather than just keeping those in my archives.I’m not going to go much into details.We’ve started a project to build a Quadrotor at University.We’ve made presentations to some companies & foundations to get financial support.After 5-6 months of presentation we finally found some financial support.But the project start to evolve in a way that totally bother me.So i quit the project and the project ended a couple of days later… Anyway… as i already said im not going to blog about that part of the story because i think it would be ethically incorrect.

So… what i wanted to share here is the material i create for the presentations etc…Maybe it helps some people who are interested in Quadrotors…
Continue reading

Redo & Undo : different approaches on logging the Action

Here we are with another riddle to be solved. Undo and Redo feature , it’s everywhere , you can come across to it on any software you use on a daily basis.It has become an inevitable piece of feature on every application.
But im sure that you do experience too that sometimes it does fail to understand how much of action to undo.And sometimes you stuck at where you’ve end up after undoing and become unable to redo.
Well… I’ve been thinking about how to implement an undo & redo algorithm for a freelance project i have been working on.It’s kind of a start-up web project and will be a new thing online.Thus i wanted to make sure everything matches users expectations and works efficiently. It has a practical graphical editing interface.If you are already familiar with a couple of graphical productivity softwares.You might have already experienced the difference between them in undo&redo feature.Everyone has a unique way of its own to handle the data.So to speak every application requires a different approach on redo & undo algorithm to match its user’s expectations.
I’ve thought of 2 possible techniques and a third one which is actually a combination of those two.

History Data logged for each action:

OBJECT , ACTION , POST_DATA , PRESENT_DATA
I guess those are self-explanatory…

[kml_flashembed movie=”http://mclightning.com/wp-content/uploads/2011/06/unredo.swf” width=”550″ height=”400″]

Method A :

There is no ruling or filtering in this method whatever user does added into history log.
Cons:
Even the sequential smallest amount of movements logged.
Thus it consumes too much of memory
And User has to click over and over again to skip back while undoing.

Pros:
It is possible to undo every action as it is logged no matter how small effect it had on the design.

Method B:
Rule:
if (
last_logged_action->object==present_action->object
&&
last_logged_action->action==present_action->action
)
{
last_logged_action->present_data=present_action->present_data;
}
else
{
// Log present_action as a new record.
}

Pros:
User can directly undo just before the first of the sequential action.
So it comforts user from clicking over and over again to the undo button.

Cons:
There is no way to go back into the somewhere in the middle of the sequential action.

So… Here comes the Third Method The combination of these two methods above.

Method A+B : Convenient name huh :D ?
Rule:

sensitivity=5;
if (
last_logged_action->object==present_action->object
&&
last_logged_action->action==present_action->action
&&
last_logged_action->present_data – present_action->present_data>sensitivity
)
{
last_logged_action->present_data=present_action->present_data;
}
else
{
// Log present_action as a new record.
}

I guess you noticed that sensitivity comparing line addition to Method B.
By presetting a sensitivity value for each action type we can decide when to go with Method A or Method B.

Algorithms & Prog.2 HW: OpenCV Tutorial (Turkish) + Source Code

Hi fellows, Here is the source code of the OpenCV Homework. Each line on the source code commented with the explanation. A Pdf doc. added to explain :

  • The main purpose of homework,
  • Where to acquire required libraries ,
  • OpenCV Installation Instruction,
  • Setting up a OpenCV project on VS2010.

Download

Proposed Input & Output :