| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67793
|
Fri Jan 30 22:45:02 2015 |
 | Eric Quintero | ericq@caltech.edu | Question | All | 3.0.0 | Re: Link to full resolution image attachments | Since I am unable to attach an image to this logbook, I made a post over the the Linux Demo logbook showing an image that was uploaded with the CKeditor toolbar "Image" button that doesn't link to the full resolution image.
Incidentially, Dario Milicic's recent commit to the git repository (83a10a5), adds the exact functionality I'm looking for to drag-and-drop attachments with the "dndfiles" CKeditor plugin. I've looked througe the "image2" code myself, but I don't have much experience with javascript, and haven't figure out how to do the equivalent for that plugin.
Thanks for your time. |
|
67797
|
Mon Feb 2 10:40:38 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | 3.0.0 | Re: Link to full resolution image attachments | If you add the picture in the HTML editor, then you can add any link you like.
I don't see why the specific link to the full resolution picture should be the default.
If you want to have it, why not just add it by hand?
I took the liberty to edit your Linux Demo post accordingly.
For attachments that is a completely different story, since you cannot add any links there, only ELOG can do this for you.
| Eric Quintero wrote: |
|
Since I am unable to attach an image to this logbook, I made a post over the the Linux Demo logbook showing an image that was uploaded with the CKeditor toolbar "Image" button that doesn't link to the full resolution image.
Incidentially, Dario Milicic's recent commit to the git repository (83a10a5), adds the exact functionality I'm looking for to drag-and-drop attachments with the "dndfiles" CKeditor plugin. I've looked througe the "image2" code myself, but I don't have much experience with javascript, and haven't figure out how to do the equivalent for that plugin.
Thanks for your time.
|
|
|
67800
|
Wed Feb 4 08:51:37 2015 |
| Eric Quintero | ericq@caltech.edu | Question | All | 3.0.0 | Re: Link to full resolution image attachments | You make a valid point!
My perspective is from my lab's specific use case, in which we often post plots of data in the body of the text, and it is useful for the ELOG-generated thumbnails to link to the full resolution plot. In previous versions, I believe this was the behavior. It would be convenient for my users if this continued to be the case, but I understand that it is not neccesarily the appropriate default behavior for all users of ELOG.
| Andreas Luedeke wrote: |
|
If you add the picture in the HTML editor, then you can add any link you like.
I don't see why the specific link to the full resolution picture should be the default.
If you want to have it, why not just add it by hand?
I took the liberty to edit your Linux Demo post accordingly.
For attachments that is a completely different story, since you cannot add any links there, only ELOG can do this for you
|
|
|
67805
|
Wed Feb 4 13:32:21 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 3.0.0 | Re: Link to full resolution image attachments | I put the functionality you requested into the current GIT version of ELOG. It works now with Drag & Drop, but not (yet) with the toolbar uploader.
| Eric Quintero wrote: |
|
You make a valid point!
My perspective is from my lab's specific use case, in which we often post plots of data in the body of the text, and it is useful for the ELOG-generated thumbnails to link to the full resolution plot. In previous versions, I believe this was the behavior. It would be convenient for my users if this continued to be the case, but I understand that it is not neccesarily the appropriate default behavior for all users of ELOG.
| Andreas Luedeke wrote: |
|
If you add the picture in the HTML editor, then you can add any link you like.
I don't see why the specific link to the full resolution picture should be the default.
If you want to have it, why not just add it by hand?
I took the liberty to edit your Linux Demo post accordingly.
For attachments that is a completely different story, since you cannot add any links there, only ELOG can do this for you
|
|
|
|
67815
|
Wed Feb 25 08:41:59 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | 3.0.0 | Re: Enter past date for logbook | As an administrator of the logbook you could add an additional attribute, e.g. "when" of type datetime.
Each entry would then have the unchangeable entry time and an addtional time, e.g. of the event you are describing in the entry.
For more details look here: elog:67712
| Banata Wachid Ridwan wrote: |
|
Is it possible to enter past date in logbook
I forgot to enter log yesterday, is it possible to add up now?
|
|
|
67823
|
Sun Mar 15 16:41:49 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Comment | All | - | Re: Configure default time range in 'Find' | Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
67824
|
Sun Mar 15 17:53:44 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Comment | All | - | Re: Configure default time range in 'Find' | Law of unintended consequences came into play. If you use 0, then on the results page it says "Restricted search to last 0 Days". So that also needs tweeking, and that's really put my c coding (or lack of it) to the test. But I've changed that phrase to "Unrestricted search" followed by blank for when the parameter "last" is 0.
Oh, and a typo, "seach" instead of "search".
No doubt other features will show up...
| David Pilgram wrote: |
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
|
67825
|
Mon Mar 16 07:16:56 2015 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Comment | All | - | Re: Configure default time range in 'Find' | Hi David,
isn't the empty string "" doing already exactly what you want to achieve with "Show last all time"?
It is at least in my logbook.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
|