ETScript v0.6 released! - UPDATES!!!

(Flippy) #1

Hey,

I’m glad to announce that I finally released ETScript v0.6.

This version solves most, if not all, problems running the program that people are having.

I also included a new readme file (readme.rtf) and 3 new features:

  • Intellisense
    Works together with AutoComplete and shows you the correct usage of the select command.

  • Error List
    Instead of getting annoying error messages every time you load a script, the error messages now appear in the Error List. Doubleclicking an error will show it completely.

  • AutoBackup
    Automatically backs up your script files every few minutes. The interval can be changed in the Options.
    Backups are stored in the “ETScript\Backups” folder.

Screenshot

Download
http://rapidshare.com/files/48610322/ETScript_06.zip.html
http://www.megaupload.com/nl/?d=X9FVBKEP

Readme file(s) inside the ZIP file.

Enjoy!

(Miki) #2

downloading, i hope this time it works, not like the 0.5 ;).

(-SSF-Sage) #3

Cool! Still need 0.41 to be installed though… :slight_smile: Great work anyway.

(aaa3) #4

Very nice very nice :smiley:

(Flippy) #5

I’ve been thinking about the AutoBackup function and decided to ask the forum what is best…

I have two options on how to do it:

  1. The way it’s done now:
    Save the file to ‘<mapname>_backup.script’ in the Backups folder, and overwrite it every time a new backup is made.

  2. Save the file to ‘<mapname>backup<time>.script’ and thus don’t overwrite, but create multiple backups for the same script.

The second way seems best to me since you can go back further in time.
If you made a large mistake 5 mins ago now, while autobackup is set to 3 mins, the mistake has already been saved and thus the backup is useless…
However, this second way will also create a new file every 3 mins orso and I can imagine the number of files becoming very large quickly.
I might build in some ‘number of files’ check to see if there are already 10 backups of the same file for example, and if there are then delete the oldest or something…

(==Troy==) #6

make a queue.

Basicly a cvar to how many copies to store. 0 - autobackup all with no deletion. 5 - keep a record of 5 last backups. etc.

(aaa3) #7

i clearly suggest the second. and without maximum nmuber as troy suggested. whoever maps and writes scripts can empty the directory manually when he need disk space. (few kilobytes lol.)
i also dont think u even need a selection menu.(the simpler - the safer and better prgoram.). its enough (in my opinion) to only have the option to turn it on and off.

(DC9) #8

JMO - I like the first option for backups. This follows the same pattern as Radiant. Making a backup of work that has significance can be done manually/consciously before proceeding with new work. Having the application creating a ton of backup files will actually create more work for people since they will need to go back and clean up when they are finished (something coders don’t do very well in my experience). The auto-backup feature is a good idea however it will loose value with experienced people who will only turn it off.

(broloi) #9

Hmm… I really think number 2 would be best…

(murka) #10

nr 2 with queue like troy suggested.

(aaa3) #11

first it sounded logical to me but i thought about it and it depends on how fast u work. except if u work very very (unrealistically) slow, it is a much less work to select 5-10-20 or even 100 files (so simple in total commander but not much harder in windows explorer too) with almost a single mouse right click and pull down, and then shift del (whole process is 2 seconds), than rewriting even 10 or 20 lines of code. but this is unrealistic that u produce in 2-5 minutes only 10 20 line, more realicstic if i say 50 (?)

to sum up; it depends on how autosave name the files. use the same start as original file and put the date(or much simpler to code to simply number them 1,2,…98, 99, et c.) to the end of file name. to make simple the selection of related files.
it depends on how often it saves. but no one will want it less than 1-2 minute i guess.
it depends on the style u work. how much time u spend to just think and write nothing. in this cases u may get the same files but after such a period u start writing, and then u may lose very lots of work even in 1-2 minute (and much more in 5…)

i wanted to adress the work issues concerning to delete the files after project finished, and not the file sizes and disk space problems, as that was u mentioned as contra, correct me if im wrong

(Flippy) #12

I managed to do some work again… Here’s a quick update (not yet released for download):

New features:

  • Increased Backup functionality
    Backups are now stored in seperate folders for each map. They are no longer overwritten, but are simply named differently (map_1, map_2, map_3 etc).
    The last saved backup can be seen in the Statusbar at the bottom.
    A “Backups >” menu item in the ‘Edit’ menu makes it easy to delete all existing backups for the current map, or view the folder containing the backups of the current map.

  • Recently opened scripts list
    Inside the ‘File’ menu, alongside the ‘Open…’ item, there is now also an ‘Open Recent >’ menu item, which expands into a list of the last 5 (may become 10) last opened scripts. Clicking any of them will open that script.
    Opening a script already in the list will not add it, to avoid having a list of the same map 5 times.
    See the screenshot.

  • Transparent Find and Replace dialogs
    A small improvement is a slider at the bottom of both the Find and the Replace dialog windows, which lets you control the transparency of the windows. This prevents you from missing out any found text which may be hidden behind the dialog window.
    See the screenshot.

  • Quick Search bar
    A completely new feature is the Quick Search bar, similar to Mozilla Firefox’s search bar.
    The Quick Search bar is essentially the same as the Find dialog, only confined in a very small area at the bottom of the program, making it easier to quickly search for simple things.
    Press Ctrl+Shift+F to show or hide the Quick Search bar.
    See the screenshot.

Screenshot:

Finally I’m working on creating a Help file (F1) similar to that of most programs, covering all functions, features, uses etc of the program.

Also, Troy is trying to recreate the script parser that is included in ET so I can use it for my program. This way, you will be able to check the script for bugs the same way ET does before running a map, which will save you some precious time.

This will take some time though so be patient!

(==Troy==) #13

Yeah… you are very right Flippy… It will take a while… Considering that this is my 42nd non-sleep hour… :smiley: But ill get it done… sometime. :slight_smile:

(DC9) #14

Good job Flippy. That is an interesting way of implementing the solution to the backup … very convenient. The other work sounds good too.

@Troy - great dedication, now go get some sleep :wink:

(aaa3) #15

very nice! hey i have some new ideas… CTRL+D delete all backups of current script, CTRL+SHIFT+D delete all backups. with mouse clickable menu list too, just have a hotkey in addition. because earlier dc9 said its a pain to delete, adding this feature may ease it :wink:

what about marking with a * in the title bar when changes made in the file after the laste save or backup, and if ctrl-z-ing (undoing) back then disappears. like in notepad2 or iirc radiant too.

and maybe a bad idea but what about if the quick search bar is on by default (and can turned off and on the same ofc)?

(Flippy) #16

About the hotkey for deleting backups, is it really necessery? I mean, it’s not like you have to constantly delete backups? It’s not really alot of trouble clicking two menu items is it? :stuck_out_tongue:
Although the option is still open, as Ctrl+D is not used yet. :stuck_out_tongue:

About the * in the titlebar, it already has this exact feature! The only thing ‘missing’ is that it dissapears when you Undo, although afaik notepad2 and radiant have this same behaviour, right?
Thanks though, now you mentioned this I tried undo-ing again in a long time and noticed it’s not working properly anymore… So that’s another todo thing…

And the Quick Search bar on by default, imo it’s much better off by default. The sole purpose of this search bar is to quickly search for something without the find window getting in the way or without even having to move your mouse.
Having the bar on makes the screen a bit too crowdy imo and is only useful when you actually need it. After that, you hide it again. :slight_smile:
I might make an option to do this though…

(kamikazee) #17

I agree with this vision, a delete operation should never have a hotkey, rather it should be placed in some menu structure. This reduces the chance that a user accidentally clicks/activates this feature and deletes his backups just when he needs them the most.

You could also make an option to this feature so it deletes all backups except for the last x backups.

(aaa3) #18

:stuck_out_tongue: ok im convinced… and that “all but the last x” sounds good :idea:
(btw i always liked the keyboard and disliked mice… maybe its coz i grew up on dos and i still love it :smiley: … anyway, i always like to have a keyboard alternative and h8d when i was forced to use the mouse. sometimes it can be reallly cumbersome. and if the hotkey is a 3 key combo then no one will press it accidentally :wink: ) (ah and what about shift-del or f8 in windows or total commander? u always right click? :banghead: )

(==Troy==) #19

I have pressed Ctrl + Alt + Del accidentally about 5-6 times in my life in MS-Dos… I didnt really like it :evil:

And with new FireFox features of Delete all Private info, Shitf + Ctrl + Del, its even worse :confused:

(Flippy) #20

Two new small features added… Still having trouble with Undo/Redo so no release yet… I think I’ll wait till I finish the help file and hopefully when Troy finishes the script parser, then I’ll make it the first final version.

The new features:

  • Show Properties…
    Clicking the “File - Properties” menu item will show the properties of the current script file.

  • Bookmarks…
    You can now use up to 5 bookmarks, which save the position of the caret (cursor). You can save a bookmark using Shift+Fx and you can load (go to) a bookmark using Ctrl+Fx (where x is 1 to 5) (or you can use the “Tools - BookMarks” menu).
    Bookmarks are stored in the registry, for each map seperately, so you can always use them even after opening a new map or closing the program alltogether.
    Bookmarks make it easy to navigate from and to different points in your script if you have to switch often.