Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 206 of 801  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  2293   Tue Jul 17 11:50:44 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows6.5-1886Re: Show attributes

deletoille wrote:
I'd try again and that does not works. does the problem come from the windows version?


Certainly not. Double check that you have the current elog version (check the ELOG V2.6.5-1887 at the bottom). If you are on windows, you can try to install elog265-7.exe which is the most recent one.
  2294   Tue Jul 17 13:24:58 2007 Reply deletoillexavier.deletoille@synchrotron-soleil.frBug reportWindows6.5-1886Re: Show attributes

Stefan Ritt wrote:

deletoille wrote:
I'd try again and that does not works. does the problem come from the windows version?


Certainly not. Double check that you have the current elog version (check the ELOG V2.6.5-1887 at the bottom). If you are on windows, you can try to install elog265-7.exe which is the most recent one.


I am sorry but I have the same thing on a colleague PC. that functions works on the old version but not on the last 1886 (see at the bottom). When I push "new" boutton, all is displayed at the same time.

  2295   Tue Jul 17 13:28:29 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows6.5-1886Re: Show attributes
Grrrr. I already told you in elog:2287 to use Show Attributes Edit instead of Show Attributes. So put following into your config file:

show attributes edit = auteur,Icone, Type Equipement

Note the edit.
  2299   Tue Jul 24 08:30:02 2007 Reply Stefan Rittstefan.ritt@psi.chBug report 2.6.5-1872Re: CVS import + french = impossible

toumbi wrote:
Hi ,
I found a bug , when I want to import a cvs file and if i had set Language=french into global , I m not allowed.
Erreur : commande "CSV Import" non autorisée 
Utilisez le bouton "page précédente" de votre navigateur pour revenir en arrière  

there is no problem if i use english.


This bug has been fixed in SVN revision 1892 and will be contained in the next release.
  2300   Fri Jul 27 16:00:07 2007 Reply An Thaithaithan@gmx.deInfoWindows2.6.5Re: WYSIWYG (What you see is what you get)
Hi Stefan,

I have just found an open source for WYSIWYG text editor named FCKeditor at http://www.fckeditor.net/. It looks great. The download Zip-file for this tool is only 1 MB.
Dokumentation is here: http://wiki.fckeditor.net/

or TinyMSC

http://tinymce.moxiecode.com/index.php


Have you an idea how to integrate them in elog?

Best regards,
An
  2301   Thu Aug 2 12:24:26 2007 Reply Stefan Rittstefan.ritt@psi.chInfoWindows2.6.5Re: WYSIWYG (What you see is what you get)

An Thai wrote:
I have just found an open source for WYSIWYG text editor named FCKeditor at http://www.fckeditor.net/. It looks great. The download Zip-file for this tool is only 1 MB.


I had a look and it just looks great. I will certainly add support for this editor, but I have to fix a few things, like inserting of images and the preview feature need modifications of FCKeditor. So stay tuned.
  2303   Fri Aug 3 16:00:42 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.5-1903Re: Boolean

Grant Jeffcote wrote:
I've noticed in the latest release when using the 'Find' page that any boolean expression (tick box) is now shown as '0,1 or unspecified'. Is this intentional? My colleagues are finding it hard to get their heads around what to choose and preferred the old 'Tick Box' option. Have there been changes to the configuration arguments used for Boolean that I've missed?


Well, maybe you didn't realize, but searching for boolean attributes never really worked. If you want to search for entries where a boolean is true (or 1), then you could check the tick box in the past. But if you wanted to search for all entries were an attribute was false (not true) you could not do it, because the system assumed you are not interested in an attribute if the tick box was not checked. With the new way, you could either specify 'unspecified' meaning you are not filtering on this attribute, or you can explicitly specify '0', to look for entries where the attribute is false. The best would be to have a three-state tick box, which can be on/off/grayed. Under Windows API this does exist, but not in HTML. So I had to go with the three radio buttons.

Now one could argue how to name boolean states. There are several options:

  • 0 / 1
  • no / yes
  • false / true
  • off /on

I have chosen the first one, but that's kind of arbitrary. If the community believes that another one is better, I'm willing to change.
  2304   Fri Aug 3 17:03:46 2007 Reply Grant Jeffcotegrant@jeffcote.orgQuestionWindows2.6.5-1903Re: Boolean

Stefan Ritt wrote:

Grant Jeffcote wrote:
I've noticed in the latest release when using the 'Find' page that any boolean expression (tick box) is now shown as '0,1 or unspecified'. Is this intentional? My colleagues are finding it hard to get their heads around what to choose and preferred the old 'Tick Box' option. Have there been changes to the configuration arguments used for Boolean that I've missed?


Well, maybe you didn't realize, but searching for boolean attributes never really worked. If you want to search for entries where a boolean is true (or 1), then you could check the tick box in the past. But if you wanted to search for all entries were an attribute was false (not true) you could not do it, because the system assumed you are not interested in an attribute if the tick box was not checked. With the new way, you could either specify 'unspecified' meaning you are not filtering on this attribute, or you can explicitly specify '0', to look for entries where the attribute is false. The best would be to have a three-state tick box, which can be on/off/grayed. Under Windows API this does exist, but not in HTML. So I had to go with the three radio buttons.

Now one could argue how to name boolean states. There are several options:

  • 0 / 1
  • no / yes
  • false / true
  • off /on

I have chosen the first one, but that's kind of arbitrary. If the community believes that another one is better, I'm willing to change.


Stefan
Thanks for the great explanation.
What are the chances of having a choice of the four options (as mentioned in your list) somehow so that when boolean-x is used (for example) in the configuration file the applicable option text is shown in the 'Find' page?

ie.

boolean-x = 0/1
boolean-y = no / yes
boolean-z = false / true

etc.

A long shot perhaps but don't know until you ask? Wink

Thanks
ELOG V3.1.5-3fb85fa6