Au3 Script Database Viewer

[MHz]

Summary

The program which I will abbreviate as ASDV was created with the intention of easily archiving AutoIt scripts that are loaded in a programming editor. Sometimes you may find many scripts open in your editor and may want an easy way to store them and release them from the editor. ASDV takes a single path parameter so the editor can pass the path to the script and the ASDV will insert it into a SQLite database. The whole process should be rather simple to store the script. Once done and satisfied, then you can close the script in the editor and have fewer scripts open at one time. ASDV allows you access to the stored script at any time. You can make routine backups of the database to prevent any data loss. Backups can be compressed by zip or similar and may take up a little amount of space.

ASDV supports adding scripts as mentioned previous and also does the following features when you right click on the title listbox.

About title
 - Output of information about the title selected from the database

Copy title
 - Copies for e.g. "Example 1" to the clipboard

Copy script
 - Copies the whole script in the viewer to the clipboard

Delete title and script
 - Removes the entry permanently from the database

RunWait script
 - Writes the viewed script to a file in @TempDir and runs it from there with @AutoItExe

Save script
 - Saves the viewed script to an au3 file

View script in your web browser
 - Perhaps a nicer way to view a script with some coloring done on keywords

Font size
 - For preference of those with great eye sight or near blind

Download

Au3 Script Database.zip

Under terms of GPL3

Requires SQLite.au3 which will is a standard include in AutoIt3. SQLite3.dll if you do not have it already here.

Tested with AutoIt 3.3.8.1 + and latest SQLite3.dll. Further details can be found in the help file included.

Homepage can be found here.

[mLipok]

I got this error:

 

Au3 Script Database.au3

OK

SQLite startup failed with error 1

 

What I must do to use your script ?

[MHz]

Startup opens the handle of the SQLite dll file. If you do not already have the dll file then you can download the latest dll here marked as sqlite-dll-win32-x86-3080100.zip. Unzip the dll and placed the file in the path of the script, which can be the working path or a path in your PATH environmental variable. SQLite3.dll is 32 bit so you will need to run the script as 32 bit to access the dll. If you want a 64 bit dll for a 64 bit script then look in the AutoIt archive here for a _x64.dll version and name it as sqlite3_x64.dll.

Give that a try.

[mLipok]

I try your script

Cool, even wonder about whether not to use it, because now I have a mess on my disk.

 

However, I miss its many functions.

 

1 Rename a group

2 add their own groups

3 adding a GUI script from file

4 adding a GUI script from the clipboard

5 adding information about the source of such a url to forum

6 display the recording date in the database

 

I'd love to, I would have added such features.

At the moment, however, I have many other projects in the open production process.

[MHz]

mlipok,

It is up to you if you want to use it or not. Its value depends on whether you have a need or not and how you would use it. The purpose of its creation was to release the build up of scripts that I tend to get in the editor. So I designed it for that purpose. I have yet to put it into good permanent use as I spent much time deleting the databases in testing. I even had ideas while making this that variations of it could happen, like an All Script Database viewer, or just CMD..., VBS... etc. Perhaps even store HTML files and such. I considered storing Au3 scripts would be enough for now and I focused on that.

Now, I do not know how you could miss something when you never had it from the start or at present.

As for your ideas.

1. That could be done though what a database editor can handle. Would need consideration and perhaps later may add.

2. There is a *.lst file where you can add table names so when the database is 1st setup, it sees the file and uses those names. Is that what you are referring to? Later can be done with a database editor or such. Or perhaps same as number 1.

3. Unsure of what you mean exactly. Remember this was designed as a backend application and perhaps you are suggesting for something that is more standalone design like a variation of it as I mentioned above.

4. Like 3 but ClipGet. The content would want to be known before inserting it into the database much like you view in a database editor. You would not want to accidentally store blobs of unknown data from the clipboard.

5. I could go into versions, authors, etc as well. I thought of that earlier and considered that is what a script header does as it stores whole scripts and not just bits of data. It would seem to be a double amount of input. I had more table names originally as default, and cut that back as I consider that I was adding too much for the average user to maintain. And once the database is setup then adding columns to the program in a new version could then make it incompatible to older existing databases.

6. Display the modified date stored as always shown. This is possible. I could try and prepend it to the bottom label. I added the bottom label so longer titles in the list box could be viewed across the width of the Gui and it helped with the larger font zooming.

Thanks for the ideas.