Originally Posted by Kyrax

...
Waha, really I don't think PMs will cut it. Unless you don't want to plan the development of the extension in advance and do not want any code review.

We don't have any structure. Everyone is releasing new versions left and right. Every single feature request goes through without any consultation with the other developpers.

If we want to work this as a team, we need to work as a team.
If you are fine with the current chaos, then much more serious management issues will come in the near future.

1) We stopped releasing new versions so constantly.
2) As I said, my project name is my gmail. Drop me a line as I don't know your email.
3) The only feature request that really seemed spontaneously added was the search one.
Lastly) You're being over dramatic. I, at least, am fine discussing stuff before adding it if you want. I also have Google Chat so you can talk to me there. I dunno about Kryptyx's e-mail though so you'll have to wait on that.

@Waha ...

I know your busy, but just want to finish off what I'm doing with your extension (I think you'll like it, hope so anyway)...

As I mentioned the script by default is set to False (for Options) yet it still works in 1.0.6
with Up/Down gesture ...

Am I missing something ?

Originally Posted by StevePaul

@Waha ...

I know your busy, but just want to finish off what I'm doing with your extension (I think you'll like it, hope so anyway)...

As I mentioned the script by default is set to False (for Options) yet it still works in 1.0.6
with Up/Down gesture ...

Am I missing something ?

The variable has nothing to do with the options window.
It only affects whether or not your variables are loaded automatically when the script loads. (Since this has to be done via popup (hence the variable name) people were complaining about the pop-up blocker showing so I made it an option via this variable.)

I'm really struggling with this, exactly which variables are we on about (been a long day) ?

Anyway, I've spent some time today revamping the script and including the suggestions I had for making it more easily understood by normal users.

I've put a lot more detail into each of the sections so that they stand out more and 'normal' users should be able to see where they need to be, to customise the script the way they want.

I've obviously used the latest version 1.0.6 ...

I just need to know where to send it for you and the others to have a look at ...

I was thinking your Email address at logicplace, unless there is somewhere else I should send it ;-)

If you have another Email address you want me to send it to send it me on a PM here ;-)

I'm currently using the dev channel ver. 3.0.193.1 and under my chrome://extensions/ it's listed there, so I didn't have any problems installing it. But I can't seems to get any of the gestures to actually work.? Confused

Originally Posted by 3D SownZ

I'm currently using the dev channel ver. 3.0.193.1 and under my chrome://extensions/ it's listed there, so I didn't have any problems installing it. But I can't seems to get any of the gestures to actually work.? Confused

See if this helps you at all.

@Steve; I'd prefer to not have lots of documentation inside the script itself, as it gets kind of bulky. You're welcome to mass PM the three of us your comments or whatever though.
But for real, adding gestures isn't really something a user who doesn't understand JavaScript should be doing. However, I suppose they could edit the gesture of an already existing gesture and could use better documentation for that.. I threw thisup earlier which should be able to guide them adequately for now. But I may add an Editing Gestures section as well, to cut out all the stuff non-techies don't care about.

One of the 'selling' points when you first embarked on developing this extension was that you could 'easily' create your own gestures ...

All I've done is to highlight the areas that you need to pay attention to if you want to create your own, basically everything above the 'UNLESS YOU KNOW WHAT YOU ARE DOING, DON'T EDIT PAST HERE' ...

In addition if people customise your current defaults (gestures), the next time you issue a new version these will be effectively overwritten, again the documentation just highlights this fact ...

You already have the ability to change the NewTab page and Popuploader (which again will be overwritten with any new release)

The 'art' of good programming is to document your code adequately in order that your 'logic' (everybody's is different) can be understood and that any future modifications can be easily implemented ...

Remember when it comes to programming ...'There are No Good or Bad Solutions, Only Better Solutions'

I think you'll find what I have done is a healthy addition to what is already a good product and makes it easier to understand what the script is all about...

Anyway, the three of you have a look and see what you think ;-)

PS: Just emailed your account at LogicPlace with my version of the script (1.0.6) ;-D

As you already know, I'm having trouble keeping up with this single thread..

But I think I'm on StevePaul here. The first and primary goal of ChromeGestures is to enable users to customize and create their own gestures.

Also, this is now a team project.

So because of these two points, I have to agree with StevePaul. He's one of the user of the extension and can easily spot the usability issues.

If I ever have to do a modifications to your code, I will appreciate it if I can understand the logic within 30 minutes

Simply document every classes with it's goal and methods with the value of it's params, its return value and simple uses cases. That usually goes a long way into making the difference between a programmer team and a good programmer team.

@Kyrax ...

I've sent Waha I copy of what I did to document your (collective) script ...

If you want me to send you a copy just let me have your email via PM and I'll send it to you ;-)

You don't forget years of teaching 'youngsters' to program ;-)

I'm following this topic almost everyday.

I did suggest before for people to be able to suggest features in the project's page. That is available already - it's on the issues tab in case someone didn't see yet. (I'm niko.pufal there)

Isn't a good idea to put in the first post that new features requests or bugs should be posted there? (and if any other user suggests a feature from now on, just make him go to that page)

Many people that see this for the first time are going to suggest or report issues in this topic, so it's going to become even a bigger mess.

That way would be much easier for the developers, since all the really important stuff would be in the project's page and no need to follow up the "chat" here.

Also, soon I think would be wise to create some support topic for this, as the number of people asking for help may increase. Would be good to split development ideas and support questions.