Either way, Steve, they're going to have to know JavaScript to add the code for gestures. ;P

Anyways, yeah, I know an incredibly disgusting hack I can do for loading that I can probably get around to implementing later tonight.

As for trails, I was thinking of trying to implement that with HTML 5 Canvas, but this would require that it can have a transparent background, and I'm not really sure it can. (But I will test for it!)
I also want to make it draw arrows or text telling you what the gesture was registered as at that line. Arrows would probably look nicer..

Ii wouldn't even know where to start looking at how to do this or what skills you'd need ...

I don't know if you can do this in JS but could you have a main JS that is just the gestures and other variables (that way you can replace it 'on block') that then calls the main processing JS to do all the other stuff...

So if you look at your CG all the code down to where the Functions start is the main JS and everything after is the processing JS ...

That then obviously leaves the array that links gestures and actions, not sure where you'd put that...

Leave it to you to have a think ;-)

You could make it like AJAX download the script or something silly like that, but it's far too much work when comments directing users to the correct editables is just as effective.
I can try to add more instructions. But I suppose if you just don't know how to do it, you can post a feature request for it.

Originally Posted by Waha

You could make it like AJAX download the script or something silly like that, but it's far too much work when comments directing users to the correct editables is just as effective.
I can try to add more instructions. But I suppose if you just don't know how to do it, you can post a feature request for it.

I was going to use AJAX for the loading but I ran into some snags along the way. It would be ideal if we can make a local ajax call a settings.html file which would get defined from their cookie data. I've seen some other extensions make calls to servers where they host a users setting... that is overkill IMO but gives them good feedback on what people want if they parse the users data...

Anyway, I'm not familiar at all with the canvas yet so I'd be interested in peaking at how you do that. The projects on http://chromeexperiments.com are just nuts.

I personally don't have a problem ..

I'm just trying to come up with a way of adding more value to the project for 'Normal' users ...

There are actually 3 areas in the script that a user has to edit to add function (I think)..

1. The Gestures (ie Var)
2. The Functions
3. Gestures array (Gestures to Actions)

If you were to highlight these areas in the script, something like this (start and finish) ...

/////////////////////////////////////////////////////////////////////
// 1. Gestures (Var)
////////////////////////////////////////////////////////////////////

You've already got in the header some description about what gestures are and how you use them ....

Put a complete example in the header (one that actually works), then relate that to the sections in the script ...

var newTabGesture2 = ["down","right","down"]; // Sect 1 - Gestures

function newTabAction2() {
window.open("http://mail.google.com/mail/"); // Sect 2 - Functions
}

myGestures[newTabGesture2] = newTabAction2; // Sect 3 - Gestures Array

Explain what the gesture is supposed to do, that way they can try it out for themselves to make sure they've edited things right, before they try one of their own ;-)

That's about the best I can come up with ...

There's a lot of detail in the script (7 pages at last count) so highlighting the relevant areas to be edited will hopefully help people get over their fear of editing it themselves ...

I'd suggest putting it in the Help as well but that looked a bit like too much trouble - lmao

Hope this makes some sense ;-)

Originally Posted by Kryptyx

I was going to use AJAX for the loading but I ran into some snags along the way. It would be ideal if we can make a local ajax call a settings.html file which would get defined from their cookie data. I've seen some other extensions make calls to servers where they host a users setting... that is overkill IMO but gives them good feedback on what people want if they parse the users data...

Anyway, I'm not familiar at all with the canvas yet so I'd be interested in peaking at how you do that. The projects on http://chromeexperiments.com are just nuts.

Nope I've got a much better solution with a background page.
Like I said though...really disgusting hack. lol Yours would be good if we could write to files, however.

And yeah those experiments are awesome.

EDIT: Pffffffffffff, that hack idea didn't work.
EDIT: Oh god this one's even more grotesque...well I'm out of ideas really, I can't release this one. xD Sorry all, you'll have to wait on options until they fix communication.

Okay last update for a bit, I mostly just wanted to stabilize the extension.
You can see all changes and additions in the changelog of the project page of course. But just to mention, I added the ability to toggle the popup loader via variable in the script. So for people that worked fine with (like me), enable it and you get your options back.

I made a quick fix to the crx to update the manifest so it includes the css file again. No version changes just an update to the extension.

Download from the project page is 1.0.5 ?

Kryptyx, can you send me and Waha an email so we can discuss the extension there instead of on this forum ?