| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1
|
Sat Mar 24 08:24:01 108 |
| | | | | | |
|
|
1
|
Sat Mar 24 08:24:01 108 |
| | | | | | |
|
|
68417
|
Tue Sep 6 14:51:19 2016 |
 | Daniel Sajdyk | like daniel.sajdyk@gmail.com | Question | Windows | 3.1.1-3f311c5 | Re: Highlight code? |
Looks like it works :)
Code need to be put in tags:
<pre><code class="sql">...</code></pre>
but it works.
Thank you :D
Best Regards
Daniel Sajdyk
| Stefan Ritt wrote: |
|
I did not know about highlight.js . You can put it into any elog page with "Bottom text = ...". I tried it for this forum and put in some C code:
#include <stdio.h>
int main()
{
// printf() displays the string inside quotation
printf("C Programming");
return 0;
}
Seems like this works nicely. Thanks for that hint.
| Daniel Sajdyk wrote: |
|
I thought so.
One more question :) I want manually add that parser (https://highlightjs.org), but I'm newby in that and don't know where ....
I know that downloaded hightlight pack I must put into folder scripts, but where to add this line:
<script>hljs.initHighlightingOnLoad();</script>
| Stefan Ritt wrote: |
|
You can manually highlight code, but there is no automatic language parser.
| Daniel Sajdyk wrote: |
|
Hello :)
Is there any way to highlight code (for example php, SQL) in elogs entries?
Best Regards
Daniel Sajdyk
|
|
|
|
|
| Attachment 1: screen.png
|
|
|
68424
|
Mon Sep 12 18:44:09 2016 |
 | Chris Smyth | chris.smyth@comcast.net | Question | Windows | ELOG V2.7.8-229 | Body Width |
How do I make this section Wider or Shorter in the 2.7.8 version?
Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box. |
|
67171
|
Wed Jan 25 15:40:17 2012 |
| Yoshio Imai | $user_email | Comment | Linux | 2.9.0 | Re: problems with https in Chrome and IE |
| Might this be related to the problem reported by Allen? |
|
67179
|
Mon Jan 30 18:23:39 2012 |
| Yoshio Imai | $user_email | Question | Windows | 2.9.0 | Re: Return Code |
It depends on how you actually call the elog client, but it outputs a message
Message successfully transmitted, ID=(new message id)
to the console upon successful transmission. Maybe you can catch this and evaluate? |
|
67269
|
Thu May 10 15:34:39 2012 |
| Yoshio Imai | $user_email | Question | Linux | 2.9.0 | Re: HW Requirements to run elog / Performance issues running on ARM |
Hi!
Looking at your config file it seems that a lot of the attributes are not user-specified but rather auto-generated content. You may want to consider using the elog client to submit such entries; this might avoid performance issues related to communication of the server with the web browser used for entry generation. This way, event entries can even be automatically created by other software rather than having a user to submit them.
Yoshio |
|
67427
|
Mon Jan 14 13:33:19 2013 |
| Yoshio Imai | $user_email | Question | Windows | 2.7.8 | Re: Dual Time display and entry times |
Depending on whether I understand your requirement correctly, the following solution should work:
- define an additional logbook attribute, say "UTC Date"
- preset it on entry creation and submission with the UTC timestamp (cf. section "Attributes" of the ELog configuration guide):
Preset UTC Date = $utcdate
Subst UTC Date = $utcdate - prevent the attribute from being changed manually by adding it to the
Locked Attributes = < ... > andFixed Attributes Edit = < ... > lists, respectively.
You may also have to add it to theRemove on reply = < ... > list if replies turn out to keep the "UTC Date" value of the original entry.
Regards, |