Scognito's Nautilus script for DLDI patcher

[shaunj66]

Scognito's Nautilus script for DLDI patcher

For all you Linux users









GBAtemp member scognito has created a small application for Linux users for easier DLDI patching.

This script designed for Nautilus offer right-click ability to patch nds files.
After unpacking, copy the folder Patch with in /home/youruser/.gnome2/nautilus-scripts or double click the install.sh file and then select execute.

Download it from our Downloads Centre below!

Download

Home page

 

[sylver78]

It's not bad, but the DLDI drop for MacOS is really better : http://www.blogadresse.de/2007/01/29/dldi-...er-the-mac-way/
Maybe someone would do something as great on linux ?

 

[Costello]

hopefully such tools won't be of any use in a near future, when flash card manufacturers add a "DLDI autopatching" feature to their flash card operating systems or firmwares!
I will personally ask the R4 team about this feature, as I'm in contact with them (writing the official french translation and also fixing the english version).

 

[pelago]

Nice to see some people supporting Linux.

 

[enarky]

Ay! Nice! No idea why I didn't think about this myself...

 

[dg10050]

Yay! Someone remembers us Linux users.

 

[enarky]

After having a closer look this script collection seems to be a little bit over the top... I don't think all these DLDI files and the patching util should be in Nautilus' script folder and most of these scripts are useless to most people who only have one or two cards anyways.

Here's what works for me:

#!/bin/sh
/media/EXT3/Backup/NDS/DLDI/dlditool /media/EXT3/Backup/NDS/DLDI/sclt.dldi $@

Put this into a +x chmodded file in your ~/.gnome2/nautilus-scripts folder and change the path to dlditool and the dldi you want to use. Same result, much less overhead.

 

[Azimuth]

After having a closer look this script collection seems to be a little bit over the top... I don't think all these DLDI files and the patching util should be in Nautilus' script folder and most of these scripts are useless to most people who only have one or two cards anyways.

Here's what works for me:

#!/bin/sh
/media/EXT3/Backup/NDS/DLDI/dlditool /media/EXT3/Backup/NDS/DLDI/sclt.dldi $@

Put this into a +x chmodded file in your ~/.gnome2/nautilus-scripts folder and change the path to dlditool and the dldi you want to use. Same result, much less overhead.

it just copies a bunch of scripts to the nautilus script folder so that they appear when you right click, the dldi utility and patches are stored in the same folder for easy referencing. It isn't complicated but is pretty useful and elegant. Don't want all the files then just delete the scripts you don't need from the patch with folder.

 

[enarky]

it just copies a bunch of scripts to the nautilus script folder so that they appear when you right click, the dldi utility and patches are stored in the same folder for easy referencing. It isn't complicated but is pretty useful and elegant. Don't want all the files then just delete the scripts you don't need from the patch with folder.

Well, if this is elegant, then what would you refer to as clumsy? Having all that crap in the script directory is the exact opposite of elegant, IMHO. For example, why even have an install script when you can't choose what to install and where? Also the recursive calling of several scripts doesn't exactly look very stylish to me - you have the possibility to script all this, after all.

I'm not saying I could do it better, I just say that you can do it with much less overhead.

 

[Azimuth]

it just copies a bunch of scripts to the nautilus script folder so that they appear when you right click, the dldi utility and patches are stored in the same folder for easy referencing. It isn't complicated but is pretty useful and elegant. Don't want all the files then just delete the scripts you don't need from the patch with folder.
Well, if this is elegant, then what would you refer to as clumsy? Having all that crap in the script directory is the exact opposite of elegant, IMHO. For example, why even have an install script when you can't choose what to install and where? Also the recursive calling of several scripts doesn't exactly look very stylish to me - you have the possibility to script all this, after all.

I'm not saying I could do it better, I just say that you can do it with much less overhead.

As I mentioned before if you don't want overhead then delete the unwanted scripts from the patch with folder before the install, there are many scripts to accommodate all the different cart owners out there.

The installer has to install in that directory otherwise it won't appear in the nautilus right click menu, thats why there isn't an install option.

Its simple to script this but im sure some people are not great with shell scripts and will find this useful.

If you could explain to me a better arrangement then I would love to hear it

 

[enarky]

The installer has to install in that directory otherwise it won't appear in the nautilus right click menu, thats why there isn't an install option.

Of course, the scripts can't be anywhere else. But dlditool and *.dldi can. Making a tutorial like you did for dldi patching would've been the far better solution for this problem, IMHO (like, tell people where to put dlditool, open a text file in the nautilus script folder, copy & paste there). If you're working with Linux knowing these basic things about scripts is essential knowledge. People who don't know these things won't know how to execute a shell script, too

.

 

[Azimuth]

The installer has to install in that directory otherwise it won't appear in the nautilus right click menu, thats why there isn't an install option.Of course, the scripts can't be anywhere else. But dlditool and *.dldi can. Making a tutorial like you did for dldi patching would've been the far better solution for this problem, IMHO (like, tell people where to put dlditool, open a text file in the nautilus script folder, copy & paste there). If you're working with Linux knowing these basic things about scripts is essential knowledge. People who don't know these things won't know how to execute a shell script, too

.

good point, but remember not all the people that use Linux are gurus, we have to accommodate the newbies/lazy people until they have learned enough to do these thing on their own. If people want I can write a small menu to install scripts for their carts only

 

[scognito]

it just copies a bunch of scripts to the nautilus script folder so that they appear when you right click, the dldi utility and patches are stored in the same folder for easy referencing. It isn't complicated but is pretty useful and elegant. Don't want all the files then just delete the scripts you don't need from the patch with folder.
Well, if this is elegant, then what would you refer to as clumsy? Having all that crap in the script directory is the exact opposite of elegant, IMHO. For example, why even have an install script when you can't choose what to install and where? Also the recursive calling of several scripts doesn't exactly look very stylish to me - you have the possibility to script all this, after all.

I'm not saying I could do it better, I just say that you can do it with much less overhead.

I wrote in the README.txt to delete the dldi you don't want.
I think my solution is the best for user who just doesn't want to bother with shell and such, just double click as in windows for install.
Most people doesn't take care of having some small 1k file in script dir...
It is simple, fast, and functional: no superuser permission, no files anywhere in the filesystem etc... Don't want it anymore? Delete that dir and everything will disappear. I think THIS is what most newbie/lazy user want. Who is able to use CLI can use that or make some shell script, but i repeat most people like it for the fast and easy way to patch.
Cheers.

 

[scognito]

Version 0.2 out!
This update add an improved installer and an uninstaller, and also GTK windows instead of old xterm text.
From this version I suggest to double-click install.sh for installing/uninstalling, as it automatically detect older installations.

http://scognito.drunkencoders.com/projects/misc.php