Just in line with that one last comment, Chip, I sometimes wonder if SC
should have been a bit more organized. Imagine, going to the grocery store,
and on the same shelf, you will find bred, milk, cheese, pop, toilet paper,
and tothpaste. True, some stores seem to throw almost whatever, whereever.
And, yes, truely convenient, if you want it all. but, the day your wife
asked you to RUN down to the store, and get her some baking soda for that
cake she's already started out on, - and would you please be quick? :) You'd
prefer the more organized store, wouldn't you?
In the 'childhood days' of Script Central, when there was 20 scripts or so,
throwing it all on one tray, might be nice enough. Now, on the other hand,
we are closing in on 200. Finding a script, might sometimes be quite
challenging. Specially so, when some people seem to have a bit of fun in
making 'funny' names for there script. OK, so far we haven't seen too much
of that stuff, but believe me, - just have a look at the general software
world, and see all the strange names of the software offered. (Smile!)
Would have been interesting to get things a bit more sorted. That way, if I
was really looking for some kind of 'toys and games', I would have skipped
right over to that section. Here would be the States-game, Lunar-Landing,
and so forth.
Was it, that I was looking for gadgets, I would go there, and find things
that would include scripts like Hourly-Chime, Time-And-Date, or the like.
Would I happen to need more of increased functionality, maybe there would be
shelfs holding things like the SecondGlass script.
And, would I be in the desperate need for a certain application, or suite of
software, to be more accessible - Well, I would jump right to the shelf of
application related scripts. Here, I would find the Office scripts, the
WinAmp script, well you name it.
Finally - or, should we rather say FOREMOST - there would be the BASICS
shelf. What would you find here? Things like GWToolkit, Homer Shared, and so
forth. Things that other scripts might base themselves on, and which need to
be installed first of all. OK, might as well throw in the InstallPackages
script, on this very BASICS shelf.
What then about all the rest of the scripts? The ones that does not fit in
on any of the above shelfs? You ever seen - in the store - they have this
little 'island' in the middle of the store? Go have a look up in the baskets
there, and it would look more like an Asian market. All sorts of things have
been thrown in there, for a pretty good price too! There would always be
room for such an 'island' on the SC as well.
Yes, indeed, we do have the chance to scroll through all the scripts. Using
the InstallPackages, you even will see the release notes, on each script.
But if I am after a script that will enhance my operation of Windows Live, I
will have to scroll through something like 150 scripts, before I ever hit
what I am looking for. Easy enough, long as I know there is a script for the
software, that has the name of - or close thereto - the software I have in
question. Then, I could always press W, and pretty soon find that
Windows-Live-Script. But in the case, I do not know, what exactly I am
looking for, or what kind of 'funny' naming the author has decided to throw
on me...
Then there is the times, when I want to check for new things that has come
around. Yet, I don't care about new games, since that is not my flavor of
using the computer. If the SC had been a bit sorted, I could quickly have
skipped the whole 'toys and games' department. If I only wanted to keep
up-to-date on the application side, then I would fix my attention on that
shelf; leaving the rest of the bulk on its own.
OK, this all would mean some kind of reorganizing of the SC. Yet, another
way to work around this, would be if there was a single instruction added to
the GWToolkit. It would be something like MyScriptGenre. It would be a
numeric value, that would be set to one number, indicating on which line
this script would be. I.e:
0 = Basics
1 = Application related
2 = Increased functionality
3 = Gadgets & tools
4 = Toys and Games
9 = Everything else
Things like the InstallPackages script, would then simply read this line of
each script, and would sort out the products you were looking for.
Just some ideas, likely to be modified, yet would be of great help, as we
see SC grow into the skies. :)
----- Original Message -----
From: "Chip Orange" <[email protected]>
To: <[email protected]>
Sent: Saturday, October 09, 2010 10:20 PM
Subject: RE: a little contest: who's got the biggest script?
thanks for the extra info.
I was just curious as to overall, what people were using scripting for:
extra functionality, accessibility, or writing convenience utilities and
games (the weather script, the states game, etc.).
When I first heard of windowEyes adding scripting, I thought it would all
be
for accessibility only.
Chip
-----Original Message-----
From: Jared Wright [mailto:[email protected]]
Sent: Saturday, October 09, 2010 3:12 PM
To: [email protected]
Subject: Re: a little contest: who's got the biggest script?
It's enough extra functionality that it seems as much a Winamp plugin as a
Wineyes one. *grin* I love Jeff's script, but Winamp was fairly accessible
from day one.
On 10/09/2010 01:26 PM, Chip Orange wrote:
I'm curious Jeff: is this because you add that much extra
functionality for convenience, or is it because it needed that much work
to be accessible?
In my Word script, it's pretty much all for accessibility.
thanks.
-----Original Message-----
From: Jeff Bishop [mailto:[email protected]]
Sent: Friday, October 08, 2010 9:06 PM
To: [email protected]
Subject: RE: a little contest: who's got the biggest script?
Winamp is almost 9000 lines, actually its over that if you include the
global script that ships with it.
-----Original Message-----
From: Chip Orange [mailto:[email protected]] On Behalf Of Allison
and Chip Orange
Sent: Friday, October 08, 2010 5:59 PM
To: [email protected]
Subject: a little contest: who's got the biggest script?
I'm curious: what's the biggest script out there?
Of course this isn't a fair contest or comparison; now we've got that
behind
us: my Word script is 4000 lines; how about it Jamal, what's the web
client script altogether? What else should be considered?
Chip
