Hi,

my first post here, great extension we have here, tnx!

I'd like to suggest something, and it's that the default gestures should be the same as in Opera (I think firegestures for Firefox uses same mappings as Opera), so the people can effortlessly continue using them in Chrome. For example,
your
Create a new tab [DOWN, RIGHT]
Close current tab [DOWN, LEFT]

in Opera would be
Create a new tab [DOWN]
Close current tab [DOWN, RIGHT]

and that's the first thing I did last evening after installing your extension. Here you can see complete Opera mappings
http://www.opera.com/browser/tutorials/gestures/

One more thing, can the gesture for creating new tab be (and how?) set to open default Chrome new tab (ie. the one with most speed dial with most visited pages) instead of opening about:blank?

Cheers and thanks for your hard work.

BTW, yeah, colour trail would be awesome.

Welcome to Chromeplugins ! Thanks for the comments !

The default gestures I included with the extension were my personal preferences. In a way, they force you to edit the gestures and are a sort of introduction to the customization capabilities of the extension.

I tried to have the default new tab open when creating a new window. The problem is that you can only reference subdomains of the current tab in window.open() so you can't access chrome://newtab/
This will be fixed when access to the Chrome API is available.

Color trail should be available sometimes next week. No promises though

The close tab also not works here. I figure you may refer to Marble's script (Mouse Gesture UserScript )for modification since that script works here:
if(event.clientY-25>posy) //down + right: close
{
window.open('', '_self', ''); //bug fix
window.close();
}

Originally Posted by Kyrax

Hey everyone ! Here is ChromeGestures beta 0.1 !

Features :

• Execute Chrome commands using a simple gesture
• Easily create your own gestures
• Endless custom command possibilities by using Javascript

On the default config, you can use the following actions :

Create a new tab [DOWN, RIGHT]
Close current tab [DOWN, LEFT]
Back button [LEFT]
Next button [RIGHT]

Feel free to customize those.

In order to customize the gestures and create your own, go to
...\Chrome\User Data\Default\Extensions\cigjdpglbacblgokjombkbbdfpkkedde\0.1

Open ChromeGestures.js with your favorite text editor
Follow the instructions there.


Download it here.

Please give me feedback !
Report any issues here.
Keep in mind that it's a beta.

Known Issues :
Chrome's window.close() does not seem to work all the time. For my next release, I'm going to work on a way to communicate with Chrome's API. It will provide a much more reliable way to open and close tabs as well as a whole lot of other things !

Enjoy !

Originally Posted by Kyrax

Welcome to Chromeplugins ! Thanks for the comments !

The default gestures I included with the extension were my personal preferences. In a way, they force you to edit the gestures and are a sort of introduction to the customization capabilities of the extension.

I tried to have the default new tab open when creating a new window. The problem is that you can only reference subdomains of the current tab in window.open() so you can't access chrome://newtab/
This will be fixed when access to the Chrome API is available.

Color trail should be available sometimes next week. No promises though

The tabs API is implemented, you can open a new tab with:

Code:

var myTabID = null,expected = false;
chrome.windows.getCurrent(function(focusedWindow){
	var blah = new Object();
	blah.url = "chrome://newtab/";
	blah.windowId = focusedWindow;
	blah.selected = false; //Set this to true if you want it to be automatically in focus
	expected = true;
	chrome.tabs.create(blah);
});
chrome.tabs.onCreated.addListener(function(tab){
	if(expected){ //Rudimentary checks to see if it was YOUR tab that was created.
	if(tab.url == "chrome://newtab/"){
		myTabID = tab.id;
		expected = false;
	}}
});

From a toolstrip or background page.
Not entirely sure this works with "chrome://" URLs per-say, but I imagine it would.
Also the listening for a new tab is only relevant if you wanna modify it later.

@Waha

What I meant to say is that opening a new tab will be much simpler once ChromeGestures has support for Chrome API (which it does not right now)..

I'm already aware that Chrome's tab API already exists

Originally Posted by Kyrax

@Waha

What I meant to say is that opening a new tab will be much simpler once ChromeGestures has support for Chrome API (which it does not right now)..

I'm already aware that Chrome's tab API already exists

Oh okay. ^^;

By persistant request from Steve, ;P I've modified this to add double-click to hide page functionality.
Of course, as it is a gesture, you have to hold down right-click while you do it.
Here's the js file: http://logicplace.com/pc/projects/ch...omeGestures.js

Thanks Waha !

I think we should start an open source project. I can't be the project owner as I'm extremely busy these days..

If anyone wants to volunteer, we could have a single chrome gesture project instead of all the little projects going on everywhere working toward a similar goal.

I seem to recall you saying you made some advancements to the chrome gestures script, perhaps you can upload those and someone can polish it off. :]

@Waha

Thanks loads for this, I'll go to bed a happy man now ;-)

Everything worked OK apart from Facebook, hides it OK but won't reinstate it ...