ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 91 of 807

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6452 Entries

Goto page Previous 1, 2, 3 ... 90, 91, 92 ... 805, 806, 807 Next

Fri May 2 18:50:48 2003

Tomas Rudolf

tomas@mba.be

Question

Simulation of a submit

I have another tricky question.

Is there a way to simulate an ELOG SUBMIT?

We developed a module which automatically inserts new submits from ELOG 
into an SQL database. The module is in testing phase but we can already 
tell it does the job as it should. 

This allows us to copy ELOG entries into SQL database. But in some cases, 
we would like to transmit data in the other direction too - from SQL into 
ELOG (synchronization).

Now, one way to do that is to create .txt files with entries directly, but 
we find it too risky (file-locking mentioned in a question earlier today 
can be one of the issues). So we're contemplating a possibility that ELOG 
does these inserts for us by processing some simulated SUBMITS.

We're assuming that ON SUBMIT, you generate a POST (or a GET ?) over http 
which is then processed by the ELOGD server. This should be possible to 
simulate in our synchronization application. Are we correct in our 
assumptions?

Tomas

2145

Wed Feb 28 21:04:59 2007

Simple table implemented in ELCode

Starting from SVN revision 1801, simple tables are supported in ELCode tags. One can now embed tables in elog entries like this:

[table border=3 cellpadding=10]
One | Two
|-
Three | Four
[/table]

which produces following table:

One	Two
Three	Four

The syntax is explained in the ELCode help page.

1789

Tue Apr 4 06:18:18 2006

Steve Jones

steve.jones@freescale.com

Request

2.6.1

Simple math within an elog form

This may sound a little strange but I am trying to determine if it is possible to create a series of attributes that may be assigned an integer value via OPTIONS, and then take the selected values and perform some simple math and display the result. For example:

What we are trying to do is create a simple form that helps a person assign a risk value to a series of identified risks

Attributes = risk1, risk2, risk3, totalrisk
Type risk1 = numeric
Type risk2 = numeric
Type risk3 = numeric

OPtions risk1 = 10, 20, 30
Options risk2 = 10, 20 , 30
OPtions risk3 = 10, 20 , 30

Subst totalrisk = $risk1+$risk2+$risk3

I suppose I could use $shell to do this but I was trying to stay away from $shell for security reasons.

Thanks

66301

Mon Apr 13 07:26:39 2009

mike cianci

mike2.cianci@comcast.net

Sorry to bother you. I could see in past Forum entries that the question of "Simple Math" has come up before, although the answers were not all that simple.

Can you do simple math (i.e. attribute A + attribute B = attribute C) in ELOG ?

Thank you for putting up with my questions.

Mike

67940

Wed May 27 08:54:27 2015

Andreas Luedeke

andreas.luedeke@psi.ch

Question

Windows

3.1.0

Side effects of draft messages (was Fixed text)

Hi Stefan,

I got an answer to a forum entry before I actually finished writing my post! It is obviously possible to reply to a draft message.

I think it would be excellent if draft messages would only be shown to their authors (except maybe in case of an anonymous author).

It feels wrong if I watch people while they making an entry ;-)

Anyway, it is just an idea.

Cheers

Andreas

Neal Grafton wrote:

Thanks Andreas

We are still playing around with ideas, just thought I'd ask, didn't think it was possible.

We are ok with setting attributes but this is new to us as yet so may have more questions later.

Andreas Luedeke wrote:

Hi Neal,

you can preload words into one attribute field, but one field is either editable or not, you cannot protect single words in a field.

But the ELOG way to solve this would be to have multiple attributes: you would get one entry field for each attribute.

Just look at this logbook: it has the attributes Icon, Author, Author Email, Category, OS, ELOG Version and Subject.

You can change the content of each attribute (except of "Author", that field is made here to be not editable), but as a normal user you cannot change the names in front of the fields.

Did you've set up the demo logbook and played around with it? Because your question suggests to me that you don't figured out yet what ELOG does. Or as a direct answer: no, it does not make sense to me ;-)

But I'm sure you'll figure it out: ELOG is best learned by trial and error.

Kind Regards

Andreas

Neal Grafton wrote:

Sorry I call this field that you write in the subject field, a little confusing.

So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)

Neal

Andreas Luedeke wrote:

Dear Neal,

I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.

But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.

Or do you want to protect entries with specific content not to be deleted? That is not easy.

Please explain in more detail what you want to achieve, and I'll be happy to help.

Cheers, Andreas

Neal Grafton wrote:

I'd like to fix text or table in the subject field that can't be deleted or moved.

Can that be done in config? Example -

Time Off:

Reason:

Update By:

Estimated On time:

Detail:

67972

Tue Jun 9 13:01:50 2015

Side effects of draft messages (was Fixed text)

I changed it such that drafts are not shown at all in ELOG. The only way you realize them is if you hit "new", and you will be prompted if there is any pending draft.

Andreas Luedeke wrote:

Hi Stefan,

I got an answer to a forum entry before I actually finished writing my post! It is obviously possible to reply to a draft message.

I think it would be excellent if draft messages would only be shown to their authors (except maybe in case of an anonymous author).

It feels wrong if I watch people while they making an entry ;-)

Anyway, it is just an idea.

Cheers

Andreas

Neal Grafton wrote:

Thanks Andreas

We are still playing around with ideas, just thought I'd ask, didn't think it was possible.

We are ok with setting attributes but this is new to us as yet so may have more questions later.

Andreas Luedeke wrote:

Hi Neal,

you can preload words into one attribute field, but one field is either editable or not, you cannot protect single words in a field.

But the ELOG way to solve this would be to have multiple attributes: you would get one entry field for each attribute.

Just look at this logbook: it has the attributes Icon, Author, Author Email, Category, OS, ELOG Version and Subject.

You can change the content of each attribute (except of "Author", that field is made here to be not editable), but as a normal user you cannot change the names in front of the fields.

But I'm sure you'll figure it out: ELOG is best learned by trial and error.

Kind Regards

Andreas

Neal Grafton wrote:

Sorry I call this field that you write in the subject field, a little confusing.

So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)

Neal

Andreas Luedeke wrote:

Dear Neal,

I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.

But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.

Or do you want to protect entries with specific content not to be deleted? That is not easy.

Please explain in more detail what you want to achieve, and I'll be happy to help.

Cheers, Andreas

Neal Grafton wrote:

I'd like to fix text or table in the subject field that can't be deleted or moved.

Can that be done in config? Example -

Time Off:

Reason:

Update By:

Estimated On time:

Detail:

1585

Thu Jan 12 11:32:19 2006

Side effects from debugging

Stefan Ritt wrote:

Thanks for reporting this bug, I fixed it in revision 1597.

Thanks for your quick reaction! Unfortunately, there is one side effect. As far as I understand, you fixed the bug by preserving the command attributes

http://www.logbook.domain/logbook/pageN?command

when browsing with the Goto page links, so that when a filter is applied, it is still active upon page change. However, the same is true for all other commands, including the

?id=NNN

command which is active when clicking List from single entry view. If you click onto, e.g. Previous in this mode, the elogd has a conflict in that it is required to display one page and having to highlight an entry that resides on another.

http://www.logbook.domain/logbook/pageN?id=NNN

The highlighting supersedes, and the page browse links are effectively disabled. Is there a way to keep the bug fix but disable the side effects, e.g. selectively not preserving the

?id=NNN

upon page browsing? Maybe you could implement a "blacklist" of not-to-be-preserved commands, in case there are other problems like this one.

Thanks for the work (I saw the timestamp!)

Yoshio

1586

Thu Jan 12 11:38:13 2006

Side effects from debugging

Addendum: in the Forum, I found a very strange effect: When deliberately highlighting an entry (http://midas.psi.ch/elogs/Forum/?id=1858), the Elog server no longer keeps the page partitioning, but displays ALL entries of the logbook. I don't know if these problems are related, but maybe you could check (we use the "Full" mode for the list view, in case that matters). I have tried to reproduce the problem with our logbook in threaded mode, but we don't seem to have this problem there.

Yoshio

Goto page Previous 1, 2, 3 ... 90, 91, 92 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6