perfsonar development work

[Gina Kramer <>]

Good point Michalis - I added a bug (#303) a little while ago to make Boolean values consistent across all products. As they are going to be picked up my the interface it certainly would also make sense to stick to the same version (ideally on/off) when setting defaults. However, to ensure backward compatibility (and consistency between the products), I think all Boolean properties should also support the  other Boolean values (true/false, 1/0 and whatever else was used before).

Gina Krämer
Technical Author, Dante - www.dante.net
Tel: +44 (0)1223 371 351 

Michael Michalis wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Maciej Glowiak wrote:
| Hi,
|
| The problem of hidden blocks of properties was discussed before. AFAIR the solution was to hide (set to "off" and hide) all the blocks what doesn't seem to be a good choice.
|
| The solution can be very simple, I think. There is "window.onload" event in JS which can be handled and served. Then we can just check which elements need to be enabled. I do not have much time to investigate the problem (I do not fully understand the way how the properties names are: for, e.g. "Vl_...", etc.), but the simple code could be :
|
| ------------------------------------------------------------------
| window.
| {
|         if(!document.getElementById ||
|            !document.createTextNode) { return; }
|
|         els = document.forms[0].elements; //gets all children of form
|                                           //number 0
|         s=""; //just for debug
|
|         //iterate all childrens
|         for (i=0; i<els.length; i++) {
|
|             n=document.getElementById("Vl_"+els.item(i).name)
|             if (n!=null) checkIt(els.item(i));
|
|             s=s+"Element "+i+": "+els.item(i).name+"; "+n+"\n";
|
|         }
|         alert(s); //debug
| }
| ------------------------------------------------------------------
|
| Michalis, I hope you'll be able to re-write the code to make it fully work. I can help if needed.
|
Hi Maciej

This doesn't have to happen through _javascript_. This can be arranged inside the servlet code that creates the initial html output. The problem lays elsewhere...If I'm going to make such an arrangement I need to make it  generic enough so that everyone can use it without having to modify any code, right? But in order to do that I have to be sure that every one uses the same values for such properties(I mean on and off or anything else that is decided) and also that any new such properties follow the same rule. If all agree on what the values should be for this kind of properties then it would be very simple for me to do it. Off course I'll have to have the approval of the people that are in charge of content(Gina and Loukik)
| Maciej

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHp/8OoEWq51/Q/40RAuaQAJ9L3ossAWVcUBG1RiyysZrdOVONSACdGoxt
gaWUTJth+GWwtGN1vK6aYF8=
=KcDD
-----END PGP SIGNATURE-----