| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68466
|
Thu Nov 24 07:38:52 2016 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Request | All | 3.1.2 | Re: Cancel button missing when editing an entry | Hi Stefan,
actually what you refer to as the "quick and dirty" solution is probably the only feasible one: to store a copy of the entry in the browser and restore that copy with a "cancel" button.
Otherwise you would need a full-fledged revision management, to deal with multiple copies of the same entry open in several browsers.
Yet, that does not solve the "problem" of a crashed/closed browser: the entries will go back to drafts and might got overlooked. As you rightly say: this is a feature, not a bug.
This is only a problem when editing existing entries, not for new entries. Maybe a note right of the button "delete" would help, in case you edit an old entry: "This entry is now a draft; press Submit to make it a real entry again".
But as a first step, it might be worthwhile to document this behaviour in the ELOG "User's Guide". Drafts are currently only mentioned in the elogd.cfg syntax pages under "Save drafts" and "autosave". I'll try to propose a text :-)
Kind Regards
Andreas
| Stefan Ritt wrote: |
|
The problem is that the elog database does not allow for a copy of an entry before you make modifications (and therefore get a "draft"). This is actually very simila to other note taking programs. I use Evernote, which constantly synchronizes between devices, and there I also cannot go back to the version before I started making modification. What one would need is a version system (and Evernote has one), so you can go back to the previous verison, the pre-previous version and so on. But this requires a complete redesign of the elog database.
A quick and dirty solution would be to store the origianal entry inside the browser (using JavaScript). You could then restore the initial version with a "cancel" button. But this mechanism relies then on the browser. If you just leave the page, there is no way the browser can put back the old version.
Stefan
| Andreas Luedeke wrote: |
|
If I edit an old entry, and do some mistake while editing, then there is currently no way to savely discard the changes.
The problem is that the entry will become a draft: if I close the window without saving, then the whole entry is gone: it will be converted into a draft entry. But the draft does contain my changes, it is not the originally saved entry!
The draft mechanism should keep a copy of the entry before I opened it in edit mode, and allow to go back to that copy. The edit form has currently the buttons "Submit", "Save", "Preview" and "Delete"; it should have in addition the button "Cancel", that just closes the edit window without saving the entry and even deleting the draft that was saved while the entry was modified. This should bring you back to the previous list view.
Is anyone out there in favour of this change?
|
|
|
|
68467
|
Thu Nov 24 08:40:31 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 3.1.2 | Re: Cancel button missing when editing an entry |
| Andreas Luedeke wrote: |
|
But as a first step, it might be worthwhile to document this behaviour in the ELOG "User's Guide". Drafts are currently only mentioned in the elogd.cfg syntax pages under "Save drafts" and "autosave". I'll try to propose a text :-)
|
Yes, I would be more than happy to include your text in the documentation.
Stefan |
|
987
|
Wed Mar 16 22:14:19 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.7 | Re: Can't use the command-line client | > There is a read password ("Read Password=..." entry in elogd.cfg) on
> the logbook which I cannot bypass from the client.
This is correct. The elog utility works with write passwords and user level access
(specifying a password file), but not with read passwords, that's not implemented. Use a
password file and you should be fine.
> There is a required attribute called "Publiek", and it's defined as
> MOptions. Whenever I try to upload, I keep getting the message that
> it misses this attribute.
Your problem is that you try to combine a MOptions with a "-r <n>" (reply-to) option. I
have never tried that and found there is a problem. I changed the way MOptions are
submitted. Instead of using <name>_0, <name>_1 etc, you can now do a
-a "<attrib>=<value1> | <value2>"
This also solves the problem with the "-r" option. You have to upgrade elogd.c from CVS. |
|
988
|
Thu Mar 17 09:56:21 2005 |
 | Pieter Edelman | elog@pde.slimblondje.nl | Question | Linux | 2.5.7 | Re: Can't use the command-line client | This solved the problems, thanks for the fast response!
On a side note, one would expect that when "Fixed Attributes Edit" or "Fixed Attributes
Reply" is set, the attributes in this list shouldn't be supplied with the command line client.
Anyway, my problem is solved. Thanks for the great product.
Pieter. |
|
989
|
Thu Mar 17 10:02:45 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.7 | Re: Can't use the command-line client | > On a side note, one would expect that when "Fixed Attributes Edit" or "Fixed Attributes
> Reply" is set, the attributes in this list shouldn't be supplied with the command line client.
Well, don't shoot yourself in the foot! The communication between elog and elogd is limited. elog
more or less submits "blindly" whatever you give it on the command line. If "Fixed Attributes
Edit/Reply" is set in the configuration, this only affects the web page with the entry form, so
these attributes are not shown as edit boxes. They are not checked during submission by elogd. Now
to get the same functionality with elog, elog whould have to retrieve the full entry form, analyze
the HTML code, find out which attributes have edit boxes and which ones not. So that's a lot of
work. Since most people use elog in scripts, they set it up once and forever correctly. There are
actually a few people which even want the functionality that elog can change attributes which are
normally fixed.
- Stefan |
|
990
|
Thu Mar 17 23:06:54 2005 |
| Pieter Edelman | elog@pde.slimblondje.nl | Question | Linux | 2.5.7 | Re: Can't use the command-line client | Okidokie. May I then humbly suggest to mention this in the documentation of the elog command client? |
|
991
|
Fri Mar 18 08:02:52 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.7 | Re: Can't use the command-line client | > Okidokie. May I then humbly suggest to mention this in the documentation of the elog command client?
I did modify it already, see http://midas.psi.ch/elog/userguide.html at the bottom. |
|
1423
|
Tue Oct 4 19:40:27 2005 |
 | David Spindler | dsspindler@earthlink.net | Question | Windows | 2.5.7 | Re: Can't use the command-line client | I have a similar problem. I am using Windows version, and whenever I use the elog client to send entry, it will not take with MOptions set. I usually have 2 attributes required (both MOptions), and I get the message that it is missing a required attribute. When I use ROptions, or Options, it works fine. Is there a problem with MOptions, or am I perhaps using a badly formatted commandline?
Commandline as follows: C:\elog>elog -h IP_ADR -p 80 -l gbld -u username password -a Type=Other -a Operator=SCADA -a Category=Controls -a Subject=Alarm "Please ignore."
Type and Category are required and MOptions.
Below is the pertinent part of the config file:
;***** Attribute Section
Attributes = Log Date, Operator, Type, Category, Engine, Work Order #, EPN, Fuel Tank 1 (A&B), Fuel Tank 2 (C&D), Engine Hours Stop, Engine Hours Start, Email To, Subject
Comment EPN = (Equipment Piece Number)
Comment Fuel Tank 1 (A&B) = (West)
Comment Fuel Tank 2 (C&D) = (East)
MOptions Type = Alarm, Trouble, ESP, Haz. Wx.,Problem, PM, Routine, Load Test, Other
MOptions Category = Engine, Generator, Controls, Fuel, Oil, HV Switchgear, MLG&W, Other
Options Engine = All, 1A, 2A, 3A, 4A, 5A, 1B, 2B, 3B, 4B, 5B, 1C, 2C, 3C, 4C, 5C, 1D, 2D, 3D, 4D, 5D, A Bus, B Bus, C Bus, D Bus, A&B Busses, C&D Busses, West Gen (001), East Gen (002)
Required Attributes = Type, Category, Subject
If time permits, I would appreciate any help possible.
BTW, I like the additional elcode. |
|