Originally Posted by chrometest

Can you implement rocker gestures. That's the only one i use.

What is Rocker Gestures?

Thanks Kryptyx, I just fixed that myself, too. lol
Just haven't finished the rest of what I was adding though, yet, so I haven't posted it.
Afraid to say that after this it won't really be usable as a User Script, but that's no real harm done, right?

Okay updated.
I don't have the .pem yet so I couldn't pack it.
Just install Kryptix's last .crx then unrar this into the chlbjhngbajmncdidibolcjokpchfhlf folder.
http://logicplace.com/pc/projects/ch...meGestures.rar

EDIT: Oh right lol.. forgot to mention what I added.
Well firstly I kept my fix over Kryptix's to the page hiding because it hides the background image as well. (I of course fixed it to just hide the body rather than erase it)
Secondly, I added options. Open the options menu using the mouse gesture up then down.
It took me so long since my last post to make this cause I made a slider bar library and it was kinda hard. Also it looks kinda crappy so if someone wants to style the options page that would be super.
To get around the broken communication right now, I had to communicate directly between this window and the content script to save and load data, which excluding technical explanation, leaves us with the fact that you'll have to refresh every tab if you want your new options to work on that tab after changing them. (Or just reload the browser.)
From the options menu you can set the new tab page URL, and a couple other settings you probably shouldn't mess with willy nilly. The first one is good though, like if you think you have to move your mouse too far to make it understand the gesture, you can turn it down. If you think it's not far enough (ie. too sensitive) you can turn it up.
The other two.. well to be honest I'm not entirely sure what they do. lol They were just editables in the ChromeGestures script so I added them.

EDIT AGAIN: Okay I found this bug where you could double-click and then right-click and it would hide the page. No good. Anyway, I fixed that.

@chrometest

I'm sure there's a rocker gesture somewhere on this site ...

@waha

You under estimate the importance of this extension as a user script (imo).

Currently there isn't a user script available for Stable/Beta users to customise the NewTab page ....

A quick question...

I was trying to add a gesture to open the chrome history page but

window.open("chrome://history/");

just opens a blank page... What should I be doing?


Thanks..

I was trying to do this by using Chrome's API, but as people here said, for security reasons you can't access it when using a user script.

The best way is as Waha said, to keep in mind this as extension and not as user script during it's development.

Some feedback:

On the "newtab" page, the options aren't displayed for me. It opens the popup, but with it as blank.

Also, instead of using window.open, wouldn't be better to put stuff as chrome.tabs.create({url:"chrome://newtab"}); there? As this is a extension now, and by what I understood have access to the API, would work, right? Would solve the problem of people having the newtab as a blank page.

Can I err on the side of caution here and hopefully be the voice of reason ...

I know the development of extensions is pretty exciting for you Guys (and Gals) but we are rapidly becoming a bit of an elitist forum ...

The Stable and Beta versions are still at 2.0.172.33 and User Scripts are still the order of the day ...

http://www.w3schools.com/browsers/browsers_chrome.asp

This is why yesterday I pushed Kryptyx so hard to create a User Script version of the Chrome Gestures extension ...

It's nice to be at the forefront (I for one certainly enjoy all your efforts and creations) but if we are to make Chrome the success we all want, we have to remember not everyone is adventurous as us ...

So all I'm asking, is if your extension would work as a User Script lets have both versions here and publish them to the world ;-)

I know that eventually the US version will fall behind the Extension version, but if its good enough to publish now (and be used) its good enough to be of use in the future ...

How many people still use the US version of AsSweep ?

I find nice to have both, for the simplicity that is to use US over extensions that are not packaged.

But also, as I understood here in this topic, the main goal must be make it available as an extension so Chrome's API can be used, and many features may become alive.

That means that yes, US can be made available, but as soon as more Chrome's API is used, the less can be done regarding US (that's what I understood with my basic knowledge of Javascript and programming)

Edit: Chrome's growing up really slow compared to Firefox in past. Just 2% increased in 6 months.

I agree that as extensions grow in functionality and complexity they will leave US behind.

At the moment a lot of extensions can function just as well as a US and we should endeavour to provide that functionality to the wider audience ...

If we take ChromeGestures as an example, once the API is fully implemented the extension version will be far superior to the US version ...

Hopefully those that have installed the US version will want to see what more can be achieved and move to the Dev channel and see what benefits extensions really have over a US ....

PS: FF didn't have a lot to compete with 5 years ago !!

Originally Posted by Firehalk

...
On the "newtab" page, the options aren't displayed for me. It opens the popup, but with it as blank.

Also, instead of using window.open, wouldn't be better to put stuff as chrome.tabs.create({url:"chrome://newtab"}); there? As this is a extension now, and by what I understood have access to the API, would work, right? Would solve the problem of people having the newtab as a blank page.

Options will not open from a chrome:// page, this is Chrome's doing.
You cannot use the Chrome API from a Content Script. This will be implemented when communication is back and I can add a Background Page to handle stuff like that.

Originally Posted by StevePaul

...
The Stable and Beta versions are still at 2.0.172.33 and User Scripts are still the order of the day ...
...?

It will still work as a UserScript more or less, however the options will not, and once a Background Page is implemented for saving/loading and opening a new tab that can be chrome:// tabs, that all will not either.