1. RE: Editor Developers.....Do Something
>
> You should REALLY REALLY use a UPS with a surge protector in it. Eu is
> useless to you if the hardware gets fried. They are in the ballpark of
> $100USD, and are the cheapest, most cost effective insurance you can
> have. They have saved my electronics and my programming code WAY too
> many times to count. Proper computer use is to plug it into a UPS when
> you
> get the computer home, install a firewall, and *only then* do you go
> online.
>
> Besides, it makes the neighbors wonder about you when the power for the
> whole county goes out, and your sterio didn't skip a note. 
>
> And save things when you make a significant or difficult or Eureka!
> change to
> any code. Mycode1.e, mycode2.e, mycode3.e, etc.
>
I agree. The cheapest ones are only $40 now, and give you 2-3 minutes
(the cheap ones do -- more money = more time) after a failure. That's
all I paid, and it will autosave any open files before shutting down if
you aren't around when the power goes out. After losing a whole hard
drive after a half-second power interruption I will never let that
happen again...
2. RE: Editor Developers.....Do Something
I use Jen's File Editor (JFE), and it works very well with EU.
JFE has autosave capabilities, but I never use it.
I don't think it's good programming practice to rely on an autosave
feature. I did try using it before, but found that it would save at
inopportune times, sometimes overwriting work that I wasn't fully
sure I wanted to be gone.
You are much better of to just get into the habit of saving your work.
This allows you to save when you want, and ensures that important work
doesn't get overwritten.
A GOOD option to have would be an autosave feature that will only save
if you haven't, within a set amout of time. EG. if you don't save within
the half hour, autosave. Autosave should also save to a unique filename,
not overwrite the original.
I can't stress enough. Save your work often! Don't rely on an autosave
feature, even if you do use one. Autosave should be a precaution, not
just a convenience.
Chris
jordah ferguson wrote:
>
>
> --To: any one concerned <euforum at topica.com>
> --Subject: Editor Developers.....Do Something
> --Date: Mon, 25 March, 2002.
> --From: Jordah Ferguson <jorfergie03 at yahoo.com>
> --Priority: 3
> --Saved by: Jordah Ferguson (Acc. Name: jordah ferguson )
>
>
> Hi all,
> This is a notice and humble request to all programmers out there
> developing windows editors. PLEASE,
> I REPEAT PLEASE....Add Autosave option to your editors in their next
> releases. Lazy freaks like me who
> get buried in programming and don't usually save, get really frustrated
> when all our work is lost due to power
> failure. This is a humble requset please some one release an editor with
>
> autosave.
>
> Ughh!!! Sorry if i'm not being polite enough, i have just lost a full
> include file, i was creating for parsing downloaded mail
> for my cirrus project.
>
> I am buying Euphoria full version, today and i'm contributing my first
> three dollars to a person who creates an editor
> with autosave.
>
> jordah ferguson
> jorfergie03 at yahoo.com
>
> --Processed and saved using: Cirrus Mail ver 0.2a
>
>
3. RE: Editor Developers.....Do Something
Use a journal file system, a raid 5 array, or move to
an area where your power is always on. My power is always
available at my house and there are plenty of generators
at Niagria Falls to back me up.
Bernie
4. RE: Editor Developers.....Do Something
Pete,
> Hmmm. What name/what recovery? If you are editing fred.txt & after 35
> minutes, the PC crashes, who/what knows what ~EMF037B.TMP holds after
> you have rebooted?
>
Backups should use the original name plus an increment.
If your system crashes, you reboot and find out you have 15 copies of
fred???.bak
The most recent file would be fred15.bak
If you go back into you editor, and open fred.txt without moving your
backup copies, they should be deleted.
A backup directory should be created in the working directory if one
doesn't already exist. All backup files for all open files are saved to
the common backup directory.
<SNIP>
> Also, when/if you press F5 to run the application in a trial, can I
> assume you are happy to have it saved?
> (You can still undo the last 100 changes, provided the app doesn't
> crash the PC, in which case tough)
<SNIP>
JFE will only let you execute a file that has been saved, obviously.
But it provides the autosave as an option. If you don't use autosave and
attempt to execute the an open, edited file, it will complain.
Pete, if you haven't already, I'd suggest taking a look at JFE. There
are a few things that I don't like about the editor. But overall, it's
simple to use, and has lots of flexibility. It's mainly designed for C,
but works well for EU too. I'm able to use it to catalog the routines in
my EU files, so I can use the C function list. If you have exoticaX, and
use JFE, you would see what I mean.
JFE also provides the ability to add 'Tools', which are externally
execute programs. You can specify the properties for executing each
tool, IE the command line. I like the macro system too. Although it
could be improved quite a bit.
Chris
5. RE: Editor Developers.....Do Something
Lucky for you, but most of the crashes are contributed by the unstable
OS. Windows has crashed too many times and i've lost all my work.
my suggestion
since windows allows long file names couldn't some one create an
autosave option in his editor asking the minutes between each save &
Create a file name such as "your current file"&"date,time in HMS"
think about it!
for example
bernie monday,12 march, 2002 12:23:32PM
so that the user can be able to trace each file.
Note: each file name will be unique
and more so, you could make the editor have a temp directory, where it
saves this other than filling your directory up!!!
whaddya think ???
Bernie Ryan wrote:
>
> Use a journal file system, a raid 5 array, or move to
> an area where your power is always on. My power is always
> available at my house and there are plenty of generators
> at Niagria Falls to back me up.
>
>
> Bernie
>
>
6. RE: Editor Developers.....Do Something
petelomax at blueyonder.co.uk wrote:
<snip>
> >A GOOD option to have would be an autosave feature that will only save
> >if you haven't, within a set amout of time. EG. if you don't save within
> >
> >the half hour, autosave. Autosave should also save to a unique filename,
> >
> >not overwrite the original.
>
> Hmmm. What name/what recovery? If you are editing fred.txt & after 35
> minutes, the PC crashes, who/what knows what ~EMF037B.TMP holds after
> you have rebooted?
>
> I strongly believe you should have to hunt down the original, rather
> than hunt down the most recent changes.
>
> Thoughts on that please.
> (full revision history is not practical just yet, sorry!)
I disagree. Ideally, the autosave should save to a unique temp file,
and load it back up when you open the app and it detects that there
has been a power loss; or, it should save to a temp file named similarly
to your document (i.e., MYDOC.TXT, MYDOC.TMP.)
The reason for this is that, more than once, I've used an editor not
knowing it had an autosave feature (and that it defaulted to "on".)
I opened a document, made a bunch of changes, and decided I didn't
like them. I decided to just keep the original and exit the app.
As soon as the thought entered my head... *autosaving* appeared
at the bottom of the screen, and the original was lost. That's
kinda annoying.
Rod
