Wednesday, December 26, 2012
But this didn't solved the problem as well. But this extension will stop gnome shell from being idle, which will avoid locking your screen. So now it was time to dig more into this problem. After going through various forums i found out that the xserver has a power management mode and a screensaver which will actually turn off the display to save power. And for my surprise this had a default timeout of 10 mints :).
Util.spawn(['xset', 's', 'off']);
And on enabling screen locking :
Util.spawn(['xset', 's', 'on']);
What the above "xset s" does is enabling and disabling the screensaver of xserver.
So at least now i have a solution for VLC when watching movies. Hope that this support will added into VLC core soon so that we don't need to have a extra extension installed.
Thursday, December 13, 2012
I was sick of unity because of the slowness and high memory usage which is believe its really unnecessary. Yes Yes i know the memory are cheap these days, but still i don't like to wast my memory unnecessarily.
So i went on searching for a DE that fits my needs, i tried gnome shell but gave up because of this problem.
Then KDE ................ Hmmmmm nop not my choice feels bit odd, may be due to the fact that i was a gnome user for very long time now.
Then i tried Cinnamon, well it was not the one i was looking for either. But for for my surprise it didn't had the right click problem. I knew that cinnamon was a fork of gnome shell and if cinnamon can fix this why not gnome :).
Well i did some search on the cinnamon issue list and came across the following issue https://github.com/linuxmint/Cinnamon/issues/482
Great now its time to find the change that they have done. So i went through the cinnamon commit history to find the changes and end up with the following commits.
Now you need to clone mutter and gnome shell code from the gnome git repository. Then you need to create new branches based on the 3.6.1 tag for both the projects.
When appling changes you will need to map some files from cinnamon to gnome shell, muffin to mutter as follows since there are some file name differences.
Cinnamon : src/cinnamon-global.c
Gnome Shell : src/shell-global.c
Muffin : src/meta/compositor-muffin.h
Mutter : src/meta/compositor-mutter.h
Now compile and install the changes. The problem will be solved :). I wonder why gnome shell developers are not considering taking this fix in from cinnamon :(.
Saturday, December 1, 2012
Above Gnome 3 add-on will make your firefox looks more like a gnome 3 application with Adwaita theme.
Above will hide titlebars when you maximize firefox.
Thanks for generous people who contribute on making those two plugins.
Monday, November 5, 2012
Monday, October 8, 2012
Below command will clone the artifacts:
eclipse -nosplash -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication -source
Below command will clone the meta data to same location:
eclipse -nosplash -application org.eclipse.equinox.p2.metadata.repository.mirrorApplication -source
Below command is optional, But if there are any missing meta data it will create them for you:
eclipse -nosplash -application org.eclipse.equinox.p2.publisher.EclipseGenerator -source
Friday, August 31, 2012
So i patch the original plugin with the new API and ran the plugin using eclipse and it works successfully. Now it was time to make it a package so i can install the patch without modifying jar files manually. So i read about how to create a eclipse feature patch which was exactly what i was looking for. So i created the patch and when i try to install it i was getting the following error:
[patch name] is not applicable to the current configuration and will not be installed.
So what i though was that some thing wrong with the plugins that contained in the feature patch. So i first tried by replacing the new classes in the original plugin jar and changed the manifest to include the new API dependency. And it worked. So now i was sured that my plugin code was not the problem. So i them replaces the original plugin jar with my patched plugin jar and this cause the plugin to disappear. So now it seems some thing wrong with my manifest of my patched jar.
So i went through the manifest of my patched plugin once again and i saw that i have messed with a dependency. The problem was a dependency plugin version was mentioned with a qualifier which actually didn't included in my feature patch. So my patched plugin fails to load because that version cannot be found at runtime. But when i run through eclipse that it works because the dependency plugin project is there in my workspace. Fixing the version solved the problem with the installation and the feature patch was successfully installed.
So for starters with eclipse platform plugin development like me, if you get the above error check you plugin manifest whether it is correct for the target runtime environment.
Thursday, July 5, 2012
This is a more frequent question I hear from my colleagues. Well my answer yes provided that the code will not thrown out tomorrow and the cost of writing will not eat up your budget.
Well there are some challenges to this especially with legacy code. Well you need to refactore your code so it's mockable in areas you need to mock. I know there are people who says "Don't touch that code if its working." Well aren't you already touching it. What harm it will do if I do bit more changes and refactor the code so that's testable and I can test it and make sure I don't break any thing. Do we need to live with that stinking code forever. The more you modify the more it will stink if you don't clean it today.
Well personally I don't agree with it. If the cost you put today will have good ROI then we should do it. This will secure your legacy code from future modification too.
Well we should consider unit testing as tool that you will use to verify your code you just wrote. if you are following TDD this really easy.
So I wish some day the people who say no to unit testing or people who thinks its a wast of time will find its advantages and power :)
Sunday, April 22, 2012
Well when i tried to start to update in the Nokia Suite it just switch of the phone which will be in kind of like sleep mode. After some time the Nokia Suite reports the connection is interrupted. Well first i though its some thing to do with the phone. Well then again i though may be i should look at the usb connections available. Because in the Nokia Suite massage it says to restart the phone to try to run the update process again. So that means the phone is not switched off, its in a mode which the user interactions are disabled.
So what i did was, i created a empty filter criteria in the vm usb settings and then start the update operation again. So as soon as the phone screen switch off for my surprise when i look at the usb device connections i saw some thing like "Nokia ROM .....". So i selected that. This cause the Nokia Suite to show some progress in the progress bar. The easiest way to find out whether your phone is switched it's mode is the usb activity indicator in the VM status bar. If its idle that means the phone has switched it's mode.
So for this phone it switches in the three modes before it restarts the phone. After the restart the phone had the new version of the software and the feature that is stated in the update information. Hope this will be help full for some one who is primarily not running windows but on a OS which can run VirtualBox.
Friday, March 23, 2012
Well then i though of giving a try with git-svn so i can create topic branch and work on it, share it and then when things ready, commit it to central repo. But the first thing i saw from my fellow developers was a unhappy face :(.
Well there is a reason for this. Because git have lot of advance functionality which make you possible to do things that you even don't think of. And their alternative commands for same task which make most of people confuse (including me some time back) and using those in wrong places will put you in trouble.
Well i tried git-svn for first time and the cloning of the repo was fine. But it was fine on command line not in the tortiseGit UI. And before committing back to central repo i was force to svn rebase (even though there was no changes in the central repo after i cloned) and dcommit which i guess is bit confusing for some users. It also took a long time to commit a change with few local revisions which got success after retrying for the second time. Even though it was OK with me, but we need some thing more simpler which gets the job done quickly with out the need for going through manuals to find out descriptions of various commands.
So i though to give a try to bzr which also have a svn integration. But that will be in another post :).