ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1309
|
Mon Jul 25 13:29:23 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: <img> in Display Attribute |
Stefan Ritt wrote: |
Emiliano Gabrielli wrote: | I'd like to be able to do what I explained in elog:1289 ... |
Ok, got it. So I implemented conditional display in the list mode. If that works for you, it was the last wish fulfilled before Christmas!  |
ok now it works .. can I request a simple regression and then shut up untill heaster ?!? 
I think that the conditional view in the Single Entry is not so good (at less in my test case) ..
My scenario should be:
- List View (full,summary,3d):
it's perfect as is now
I have a "Problem" and a "level" attribute, I don't display the level directly but only show an icon in the
field of the category
- Sinlge entry view
In this view It's supposed to go in details .. so I'd like to display both a "Category" (with its icon) *and*
a "Level" (with its own icon too) ...
nowaday in the single view the category can only have the same icon it has in the list view..
donno if a "List Display <Attribute>" could be *the* solution ... having this way the total contol over conditional displaying in every view 
btw:
the calendar is at good point 
|
1314
|
Mon Jul 25 21:29:52 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | | Re: <img> in Display Attribute |
Emiliano Gabrielli wrote: | donno if a "List Display <Attribute>" could be *the* solution ... |
That's a good idea. Unfortunately, "List Display" is already used to specify which attributes to display in list mode. So I changed "Display <attibute>" to "Change <attribute>" and added "List change <attribute>", just to be different from "List display". In principle "List display =" and "List display <attibute> =" can be distinguished by elog, but it could be confusing to have the same option for two different things. The downside is that everybody using "Display <attribute>=" has to change this to "Change <attribute>=". |
1323
|
Tue Jul 26 10:45:14 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: <img> in Display Attribute |
Stefan Ritt wrote: |
Emiliano Gabrielli wrote: | donno if a "List Display <Attribute>" could be *the* solution ... |
That's a good idea. Unfortunately, "List Display" is already used to specify which attributes to display in list mode. So I changed "Display <attibute>" to "Change <attribute>" and added "List change <attribute>", just to be different from "List display". In principle "List display =" and "List display <attibute> =" can be distinguished by elog, but it could be confusing to have the same option for two different things. The downside is that everybody using "Display <attribute>=" has to change this to "Change <attribute>=". |
It works perfectly now thank you Stefan |
934
|
Sat Feb 12 17:45:39 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | All | 2.5.6 cvs | Re: [patch]: fixed wrong extention check |
> current version uses strstr() to check if the file has the expected ascii
> text extension ... this is buggy becouse this way a file named
> ".txt_hidden_file" or "foo.config.dat" are both seen as .txt files.
I added your routine chkext() to the code, but actually use it differently. I
display now ASCII files not by their extension, but the code checks for each file
to contain non-printable characters. If it contains all printable letters, and does
not have the extension PDF, PS or EPS, it's shown inline. |
948
|
Wed Feb 16 08:48:52 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug fix | All | 2.5.6 cvs | Re: [patch]: fixed wrong extention check |
> > current version uses strstr() to check if the file has the expected ascii
> > text extension ... this is buggy becouse this way a file named
> > ".txt_hidden_file" or "foo.config.dat" are both seen as .txt files.
>
> I added your routine chkext() to the code, but actually use it differently. I
> display now ASCII files not by their extension, but the code checks for each file
> to contain non-printable characters. If it contains all printable letters, and does
> not have the extension PDF, PS or EPS, it's shown inline.
I totally agree with you choice :-) |
67658
|
Tue Jan 21 13:17:52 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.9.2 | Re: [Not] Submit on pressing enter key |
Daniel Campora wrote: |
Hello community,
I have a feature request for the form of the ELOG.
For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.
Cheers, keep up the good work,
Daniel
|
Have a look at this forum. If you press <enter> on the subject field, you get asked "do you really want to submit this entry" and you have the chance to cancel and continue editing. You should get the same with the current elog version. |
Attachment 1: Screen_Shot_2014-01-21_at_13.16.48_.png
|
|
1216
|
Fri Jun 24 22:44:03 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.0beta2 | Re: [BUG] show only new entries |
Emiliano Gabrielli wrote: | the new link "show only new entries" is very useful but seems to still have some problems:
- I can't find any simple way to return to the "every entries" display .. may be the link has to be switched to a checkbox to be actived or not
- I found a way (at least)... following the "config" link, doing nothing and coming back restores the view .. this is a feature now, but when a less tricky mechanism will be implemented will become a bug

|
I added a "Show all entries" link to go back.
Emiliano Gabrielli wrote: | another entry for my wishlist:
writeing the above code I noticed that the elcode buttons are lacking of a "[ *]" shortcut .. it will be very usefull  |
I added that to elcode.js . So if you click on the list button, the (LIST) tag and the the first (*) are inserted.
Emiliano Gabrielli wrote: | Writeing the wish above I noticed that the [ *] is interpreted as an item also otside the LIST tag .. so .. or the LIST tag is optional, or the [ *] should not be interpreted outside of it ... it's another bug ? P |
Well, the ELCode stuff if a poor man's version of HTML. So each [ LIST] gets converted into a <UL> tag, and each [ *] gets converted into a <LI> tag. This makes the interpretation very simple, but the code does have no clue if your are inside a [ LIST] or not. Common bulletin boards have exactly the same problem. To fix it, you would really have to interprete all the ELCode, and I don't want to write my own parser. |
1217
|
Mon Jun 27 15:09:12 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | 2.6.0beta2 | Re: [BUG] show only new entries |
Stefan Ritt wrote: |
Emiliano Gabrielli wrote: | the new link "show only new entries" is very useful but seems to still have some problems:
- I can't find any simple way to return to the "every entries" display .. may be the link has to be switched to a checkbox to be actived or not
- I found a way (at least)... following the "config" link, doing nothing and coming back restores the view .. this is a feature now, but when a less tricky mechanism will be implemented will become a bug

|
I added a "Show all entries" link to go back.
|
I think you only committed the changes to elcode.js but not the ones relative to elogd.c ... the Attribute quick filter is now empty, and no "show all entries" is ever displayed |