Hi There,

As you might have noticed I've closed the old liteEditor thread, as a lot of people were downloading the old and buggy v0.2 version of the editor. In this thread i want to present you the new and final alpha version of liteEditor. This implys that there should be much less bugs and an pretty stable coding experience.

Please download the latest version from http://www.dev-software.com/led/liteEdit.exe
==> This will always be the link to the latest version of led in the future.

As some kind of sitenote: This is the final version of liteEditor 1.0. From now on no new features will be implemented - only existing bugs will be fixed.

New Features:
- Own Publish dialog: keep the folder structure while publishing. Enhanced WRS packing.
- Performance Measures: Check the performance of your script and projects. Check the following video: http://www.dev-software.com/led/video/performance_1/Performance_Video_1.html

Screenshots:
enhanced coloring


debugging of global variables and structures


enhanced auto-complete


A lot of plugins (for e.g. anet)


Thanks a lot for checking.
Regards,
Timo

Does the editor have an auto backup feature? I couldn't find any setting in the options dialog.

Is that an required option for you? Currently auto-backup is not implemented, as i've never used it myself in my programming history (actually i'm using svn or similar tools to backup my data).
As this is an interesting feature: What would you expect? Backup-Interval? Backup all files or only single files?

Sounds great, downloaded it and will test it on the weekend.
I would like to see auto-backup, too, as it saved me a few times already some hours of work. The SED backup is somehow a little flawed, though, because when you check the file and the backup happened after the incident it's useless. Thus I would like to see 2 options for this feature: The intervall length of backups and the amount of backups your editor cycles through, example:

5 backups:
superku_LEDBU1.c // does not have to be the most recent backup but would be nicer, of course
superku_LEDBU2.c
superku_LEDBU3.c
superku_LEDBU4.c
superku_LEDBU5.c

If the intervall length is set to 15min and I made a bad code decision 30+mins ago, backup 3 saves my day.

No it's not an required option, but it would be very nice. I find the SED backup feature very useless, because it overrides instantly backups.

A better feature would be to have the option to create a new backup file each interal. For example, if I set an backup interval time of 30 minutes, every 30 minutes will be created a unique copy of the current scripts, maybe with date in the name:

main_2012-11-21_20-35.c (backup at 20:35h, 21st of november 2012)
main_2012-11-21_21-05.c (backup at 21:05h, 21st of november 2012)
main_2012-11-21_21-35.c (backup at 21:35h, 21st of november 2012)
main_2012-11-21_22-05.c (backup at 22:05h, 21st of november 2012)
main_2012-11-21_22-35.c (backup at 22:35h, 21st of november 2012)
...

I ask this, because in the past I've had some HDD errors. I make backups manually every 1-2 day. And after the HDD errors occured, some script files where crashed. The last backup I have was 1 day old and the SED backup was already overwritten with the broken script. So I had lost a whole business day. If I had multiple backups from every 30 minutes, I maybe lost only 1 or 2 hours. And to lost a day of work sounds not that much, but if you are near a deadline it can be really annoying to rewrite the script of a whole day.

[EDIT] While I wrote my post, Superku had almost the same idea

Timo, das Ding ist mal richtig abgefahren!

That's an awesome piece of software! Especially the performance measurement!

@Oliver: if its about HDD-erros:

Systems like Git and SVN where you save your work regulary on an external server in a source managementsystem.(commits are VERY usefull )
In-Editor-Backups are usually designed to fetch the risk of loosing data when the editr crashes.

And if you have constant HDD errors, you should check you'r hardware

First of all: great work!

I couldn't get the Performance test working. While compiling it says "Could not find PROGRAM.c". Am I missing something?

Is there any chance to allow ctrl+c in the 3dgs-help-frame (to copy text into clipbaord)? As in SED this is not supported (and this drives me insane! :-))

Thanks a lot for your critics.
I've just released version 1.12. You can download it from http://www.dev-software.com/led/liteEdit_112.exe or by pressing help-->update in liteEdit 1.11.


This was a bug, when you installed liteEdit to "program files" (or better said, folders with a space in it). Fixed.


This was actually the most complex one.. Should work now..

Auto-Backup is implemented. You can define the backup-interval. All files are automatically zipped and added to a standard backup folder. See the following three screenshots.

[edit]As i see now, the auto backup functionality contains a bug, that the files are never deleted.. therefore the directory will be pretty full after some weeks of work..I'll implement a solution for this in the next version 1.13. Until then I think this is okay - as the files are zipped, and should not be larger than 200kb every backup (==> 200kb * 4 backups per hours * 24 hours * 30 days = 500mb even if you program for 30 days.. so not the worst bug ever)[/edit]







Additionally some bug fixes have been applide to the code templates, which should now be more stable.