OLD -- Re: Bit Che - Scripts (current scripts & submit new)

[Bovski]

woot git has added a + button

t411.me
torrentkit.com

[loninappleton]

Are these the automatic updates?  I still have to learn this.

[Bovski]

Are these the automatic updates?  I still have to learn this.

It's for people without git access to post scripts

if you restart BitChe it should auto update and t411.me.ini should be added.

[chip!]

woot git has added a + button

t411.me
torrentkit.com

thats awesome!  sure made git even easier to use   thanks Bovski

[CuF]

Excuse my ignorance, but what is 'git'?

[chip!]

hi CuF.. git is a tool that software developers use to keep track of changes in projects and collaborate/share changes to the code.. http://en.wikipedia.org/wiki/Git_(software)

since 2.0, we have moved the entire default script pack to a git so that anyone can freely copy/merge.. or edit/make their own changes to the script pack.

here is the script pack: https://github.com/convivea/bit-che-2-scripts

and, there might be better guides out there, but here is a quick 'learn about git' page:  http://learn.github.com/p/intro.html

it can be kind of complicated at first, but thankfully github has a pretty easy web interface

[Bovski]

well now they have the + button it is usable for adding scripts the editing has always been cool.

[CuF]

Cinemageddon script for v2.  First of probably many to come now that I have a better grip on the new scripting.

I welcome critiques of my method.  Also, do new/custom scripts go into the .\scripts\default folder or somewhere else?

Edit: And Cinematik.

(Edit: Removed. See below)

[chip!]

thanks CuF.. i'll get those added to the pack!

regarding where should they go:

.\scripts\default = protected folder.. when Bit Che updates the default script pack, it will be fully synced (add, delete, modify) all the scripts in the folder so that it matches the default script pack.

while this is great for the users, it does present a small "issue" for developers who edit or create new scripts.

what I suggest (and I am doing the same).. is make a new dev folder for your personal new or edited scripts. then, if you submit them and/or add them to the default pack, you can delete them from your personal folder.

for example, make this folder:
.\scripts\dev

and put your new scripts and any others you are working on in that folder.  restart bit che and it will find those scripts and keep them active (as long as you keep your new 'dev' pack active using the Script Pack menu)

if you leave them in .\scripts\default and you update the script pack, your changes will be moved to the .\scripts\backup folder (so you will not accidentally lose your edits), and then .\scripts\default will be synced.

[CuF]

Cool.  Will there be additional script packs in the future?  I can see an Adult pack being a useful category so they can be better maintained, but not something everyone would want.

[CuF]

Bit of a mix up, here's a repost of the two scripts.

[chip!]

Cool.  Will there be additional script packs in the future?  I can see an Adult pack being a useful category so they can be better maintained, but not something everyone would want.

Yes bc2 allows anyone to create/host their own script pack.

Here is the guide I wrote. I can probably help with the web hosing if you or anyone wants to create their own specialty pack. Let me know.

http://convivea.com/forums/index.php?topic=2195.0

[CuF]

Ran into a rough patch with the scripts I was working with so I figured I'd post the ones that are working so far.

Pirate Bay members script, BakaBT (updated to include Alternative Version results), BitHq.org, TheBox.bz and TheEmpire.bz.

[CuF]

I'm not actually familiar with Take.fm, but I noticed it was generating a bad result named "//" if it had no hits.
Checking it, it also didn't seem to grab every hit either.

Script updated.  It's sort of a shame we can't use something =code($page,#) for seeds, leeches and dates.

I guess we have to settle for 1:1 for all results from Take.fm (until Bit Che v3 ).

[chip!]

looks like we got all these updated in the script pack.. thanks CuF and Bovski!

oh, and if we did =code($page,#) for seeds, leeches and dates would be kinda obnoxious because it would fetch multiple pages per request on the initial search.. meaning for 50 results you could have 200+ additional HTTP requests from the 1 single search HTTP request...   to me, i think its best to just force dummy data if its not available.