Official script registry - discussion

I attached a json file.

p.s. incredible doubleplus thanks for this. I cleaned it up a tidbit and threw in a blank forumThread field, which we just now decided on. Posted it on a gist.

I just pushed the initial version of the Script Manager. Lots of things need to change (especially on how the repo file is hosted/moderated) but I figure having the thing within reach should galvanize people into action. Ball is out of my court on that.

On my side of things, I'll be adding some cutesy user experience features as I have time to code them - more context menu options, more highlighter options (see which scripts are at-HEAD at a glance...), etc. The core functionality should be working - click a script, install. Click an installed script, delete. Everything past that is icing.

Report bugs here for a little while.
 
Awesome. Thanks.

I may have a bug to report in that some of the same scripts are showing up in Installed and Can Be Installed. If I can reproduce when I am back on a mafia enabled machine, I 'll report details.
 
I may have a bug to report in that some of the same scripts are showing up in Installed and Can Be Installed. If I can reproduce when I am back on a mafia enabled machine, I 'll report details.

I see all those I have installed that are on the list in both tabs, so I guess it's deliberate.
The ones I have on the Manage tab that aren't on the full list are:
Bale's Top Menu - svn checkout https://svn.code.sf.net/p/bale/relay/code/topmenu
Bordemstirs' Raid log - svn checkout http://almighty-saplings-ash.googlecode.com/svn/trunk/raidlogs
Nappa's KOLHS Items - svn checkout https://svn.code.sf.net/p/mafiarelaykolhs/code-0/
 
The ones I have on the Manage tab that aren't on the full list are:
Bale's Top Menu - svn checkout https://svn.code.sf.net/p/bale/relay/code/topmenu
Bordemstirs' Raid log - svn checkout http://almighty-saplings-ash.googlecode.com/svn/trunk/raidlogs
Nappa's KOLHS Items - svn checkout https://svn.code.sf.net/p/mafiarelaykolhs/code-0/

The first and third ones appear to be missing from the repofile. The middle one.. you appear to have the scheme wrong? (http vs https)
 
Bordemstirs' thread and Bale's thread seem to disagree.

I'm sure the http one redirects to the https one, but for the purposes of the manager I won't consider the two equal.
 
Roippi, is there any way I can get access to edit the jsonfile? I guess I was "awfully sneaky for finding this, btw." My github id is balefull.

I know that this is not the final destination for the file, but I'd like to be able to keep it up to date and flesh out the information with thread ids and long descriptions.
 
Last edited:
I know he is hoping that. I'm just hoping that I can update the file before that event occurs since I have no long it will take.
 
Haha.

I don't think there's an easy way to give push/pull authorization to a gist, they're really not meant for collaboration. I should probably just make a real repo and link against that so we can have multiple users on it.

Doing that now.

And yes, I'm very much hoping we come up with a better long-term solution than "throw it up on github." This works for now.
 
Thanks for adding me to the repro. Added all thread links and a few long descriptions. Will do much more work on those long descriptions later.
 
Last edited:
If any script maintainers want access, there's no problem with marking them a collaborator so they can tweak the file themselves.

As a reminder, the longDesc field will correctly render (most) HTML markup, so feel free to use that.
 
Every script in the script manager now has an informative longDesc field. Sheeezus, that was a lot of work!

Some of them I copied directly from the forum thread, some were copied with minor edits, some I had to make up myself. I tried to make the descriptions helpful and I am very much open to modifying them if the script author requests as long as the author is conscious of the rather limited size of the text window.
 
Kudos for doing that. I do hope that scripters take interest in maintaining their own repo entries as time goes by.

re: "the rather limited size of the text window" that is mostly by aesthetic design, but if authors want to go off the bottom of the reservation, I'm fine with that. r13702 makes the text area resizable.
 
re: "the rather limited size of the text window" that is mostly by aesthetic design, but if authors want to go off the bottom of the reservation, I'm fine with that.

I'm not sure I'm okay with that. It would be unfortunate if people started making big descriptions that require me to resize in order to read their descriptions. The limit is also a feature because it encourages brevity so that the user can get the gist of their script easily. We shouldn't encourage the scripters to put an entire user manual in their description.

If you really want to allow longer long descriptions it would be a much better idea to simply allow a scroll bar. That's a lot easier for the user to deal with. I don't like the idea though.

Could you revert r13702, please?
 
No, I will not revert it. Resizability means you can squash it down to one line if you want. I like that. You can even try squashing it down to one line, going to a script with a multi-line description, then clicking the divider - it auto-resizes to fit your text. I like that too.

Also, some look & feels may render text differently, causing overflow that's not visible in the majority of L&Fs. This gets around that.

Informally discouraging authors from writing novels by not providing scrollbars seems sufficient.
 
You can even try squashing it down to one line, going to a script with a multi-line description, then clicking the divider - it auto-resizes to fit your text.

Though actually I value this behavior less than the ability to squish it down all the way, so r13703.
 
Back
Top