[sldev] Automatically backing up scripts locally.
Adam Frisby
adam at gwala.net
Thu Dec 20 03:15:59 PST 2007
Why not save it as the name + UUID to avoid any kind of collision
between objects (IE, I'd have ten thousand New Script.lsl's)
Regards,
Adam
Argent Stonecutter wrote:
> On 2007-12-19, at 19:16, Dale Glass wrote:
>
>> I like the idea, although I'm quite busy already, unfortunately.
>
>
> Me too. :(
>
>> Sounds easy enough, although there's a potential issue with scripts
>> being
>> edited inside objects. I guess an easy solution would be taking note of
>> where the object being edited was, and if the script can't be reuploaded
>> tell the user and save to the inventory.
>
>
> Well, I was thinking more like letting the user know there was an un-
> uploaded script when they connected, and let them decide what to do
> with it. I mean, you wouldn't want it to overwrite a script in an
> object inventory with an old version because you'd already re-done the
> edits elsewhere.
>
> Hell, I'd be satisfied with a preference option "Save copy of scripts
> and notecards in [~/Documents/SL]", and have it ALWAYS write
> "scriptname.lsl" or "notecardname.txt" in that folder when I hit save.
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
More information about the SLDev
mailing list