As I said, as more features are added to extension functionality it will become obvious that the US cannot keep up with it's development ...

However I still think it is a worthwhile exercise to take the US as far as possible, already it is giving Stable/Beta users functionality that they haven't previously enjoyed (in particular the customisation of the NewTab) ...

PS I noticed that if you open the NewTab (Ctrl+T) and then use the Mouse Gesture to open a NewTab (down & right) you get the Blank page ...

Originally Posted by StevePaul

As I said, as more features are added to extension functionality it will become obvious that the US cannot keep up with it's development ...

However I still think it is a worthwhile exercise to take the US as far as possible, already it is giving Stable/Beta users functionality that they haven't previously enjoyed (in particular the customisation of the NewTab) ...

PS I noticed that if you open the NewTab (Ctrl+T) and then use the Mouse Gesture to open a NewTab (down & right) you get the Blank page ...

Similar to the problem with opening options from there. window.open just does not work correctly on a chrome:// page.

Hey Waha those changes look pretty good. I'm also a graphic designer so I'll work on making the slider look a little more fancy :P

As far as the options go, the last option (timeout between clicks) which is the one I added basically stops a user from being able to Right-Click, then left click <wait 30s> and left click again. It's designed to force the user to click faster, so basically if there is more than a 1 second delay in between clicks, it will reset the click count.

As far as the user-script goes, I think the userscript that I supplied last time will be the last version of it that this extension will officially support. Users can easily modify the userscript to add their own gestures but in general all the new functionality changes we are adding to the extension is beginning to go outside a userscripts capacity.

Remember that eventually chrome will support extensions officially, that is what we are working on here. If someone really wants to use an extension they should switch to the dev channel... if they dont want to do that then they can use the userscript i provided.

While I was pondering the above situation I had the following thought ...

Over the 10 months of Chrome's existence much has been made of the NewTab ...

Some people like it, some don't ...
Some people want a blank page, some don't ...
Some people want a page of their own choice ...

Thanks to you and Kryptyx we now have the last option ...

Rather than having to make a choice, what would be nice (to make this complete and all things to all men (women)) is a gesture for the Chrome NewTab and a gesture for a blank page ...

Is there any mileage in this suggestion ...

Anyone can add their own gestures, the default ones included are just there to give an example on how to add your own.

For example:

Code:

var newTabGesture2 = ["down","right","down"];
function  newTabAction2() {
	window.open("http://mail.google.com/mail/");
}
myGestures[newTabGesture2] = newTabAction2;

The above will open Gmail.

I think it's my 35 years in IT taking over here ...

Having read thousands of posts on Chrome, and what people would like to see implemented, I feel I have a good understanding of what people would like to see from an extension such as yours ...

It's like anything, once you experience it and like it, you want to improve on it ...

I know it's reasonably easy to add your own gestures, but as is always the case people want it already done for them ...

As you mentioned to Waha in your post above this is probably as far as the US version goes so it would be good to go out with a 'bang' ...

So what would I do ?

Implement the NewTab and Blank page gestures ...

Have a section of pre-defined gestures (say 5), commented out, so that people could then customise them as they see fit and just remove the comment markers to make them live ...

Have a description in this section explaining how to customise the gesture and also which bits to copy and where to place them if they need or want additional gestures ...

At this point, you've got a User Script to be proud of, with exceptional functionality which will prove to be of benefit 'till the Stable/Beta channels catch up with the Dev channel ...

Again, as you mentioned, people can always move to the Dev channel ...

Unfortunately, for most, that's not going to be an option ...

People only trust something if it has the magical word Stable attached to it ...

PS: Obviously this only needs to be implemented in the US version and a note saying this is the very last release of the US version, if people want further functionality they need to update to the Dev channel ...

Plus, it stops me coming up with ideas !!!!! - lmao

The functionality that Waha has added is not compatible with userscripts its really that simple. Its not possible because of the restrictions userscripts have.

There is absolutely no way to open the default new tab from a gesture in a User Script. And until communication is back, none for Content Scripts either.
And like he said, if people want the extension badly enough, they'll move to dev for it, we can't help them if they can't help themselves a bit.
If you want a separate blank page gesture you can add something like:

Code:

var newTabGesture2 = ["down","right","down"];
function  newTabAction2() {
	window.open("about:blank");
}
myGestures[newTabGesture2] = newTabAction2;

(copy/paste ftw.)

Hopefully we can eventually add a recording feature. Though I don't know how we can record what it will do..

The original Chrome Gestures did a blank page if I remember rightly ...

function newTabAction() {
window.open("chrome://newtab/",null);

Unfortunately your not quite grasping what I am trying to say here ...

It's about filling a hole ...

Go to somewhere like the Chrome Help forum and see how many questions there are about the NewTab http://www.google.com/support/forum/...d4d774f3&hl=en

Your (combined) Extension (User Script) fills that hole ...

Before the Stable became Beta, people wouldn't move to the Beta channel so there's no chance of them moving to the Dev channel ...

As Idon't have a site to put an amended version of your script on I guess I'll just have to post some instructions with the link ...

Just thought it would be easier to download a script with all the necessary in it ;-)

Originally Posted by StevePaul

The original Chrome Gestures did a blank page if I remember rightly ...

function newTabAction() {
window.open("chrome://newtab/",null);
...

That only opened a blank page because trying to open a chrome:// page like that is invalid, using "about:blank" would be more appropriate.
And seriously, if you're going to be that upity about it when extensions will likely be coming out for stable here soon considering the progress anyway. I MIGHT be able to adjust the script to work as both a full-featured content script and a User Script using default values.