Hi,
Sure no worries, both options leave the date in the ISO format with the
'T' between the date and time because the format specifies it on
reconstruction. I am happy to go with an update on the reg expression
also, but I just tested \W+|T and it doesn't work for me.
Reg expr fix (doesn't work at the moment, but we just need to get the
regex right)
> var a = str.split(/\W+|T/);
Replace T fix (works but is kind of a hack)
> str = str.replace("T", ":");
> var a = str.split(/\W+/);
On another note I have an issue with IE and the date field clear link.
The link produces the "are you sure you want to navigate away from this
page" dialog using IE 7. If the link is converted to a button this issue
goes away and the dates are still clearable.
<td align="left" width="100%">
<xsl:text> </xsl:text>
<!--
<a href="JavaScript:clear{$ref}();">
<xsl:value-of select="/root/gui/strings/clear"/>
</a>
-->
<button class="content"
onclick="JavaScript:clear{$ref}();">
<xsl:value-of select="/root/gui/strings/clear"/>
</button>
<script type="text/javascript">
function clear<xsl:value-of select="$ref"/>() {
document.mainForm._<xsl:value-of
select="$ref"/>.value = ""
}
</script>
</td>
Does this change sound ok to also include in the date script updates?
Cheers,
Kevin
-----Original Message-----
From: John.Hockaday@anonymised.com [mailto:John.Hockaday@anonymised.com]
Sent: Tuesday, 2 December 2008 10:08 AM
To: Simon.Pigot@anonymised.com; Kevin Gunn
Cc: geonetwork-devel@lists.sourceforge.net
Subject: RE: [GeoNetwork-devel] BlueNet MEST Date field lose current
time valueon calendar.setup call [SEC=UNCLASSIFIED]
Hi Simon and Kevin,
I would support the option that Simon is suggesting. The ISO standard
for DateTime is to have a "T" as the separator for the delimiter between
date and time. Using the split using 'T' would be more ISO 8601
compliant.
My two cents worth.
John
-----Original Message-----
From: Simon Pigot [mailto:Simon.Pigot@anonymised.com]
Sent: Tuesday, 2 December 2008 12:43 AM
To: Kevin Gunn
Cc: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] BlueNet MEST Date field lose
current time valueon calendar.setup call
Kevin Gunn wrote:
> The cause for this is the 'T' in the date and the string
splitter reg
> expression used in the DHTML Date.parseDate in calendar.js.
>
> var a = str.split(/\W+/);
> var b = fmt.match(/%./g);
>
> One quick solution is to modify the script to sub the 'T' char for
> something like ':' which \W would match and split on. Any other
> suggestions/preferences for this one?
>
Could also add 'T' to the regular expression match ie. /\W+|T/ to make
it a little more obvious maybe. It should then split on one (or a
repetition of) non-ascii word char(s) or T if my reg-exp knowledge
doesn't fail me! To make sure the calendar stuff could
still be used
elsewhere for dates other than ISO types maybe we should only
use the T
option in the reg-exp if the fmt contains a 'T'.
Good bit of work finding this one - thanks Kevin and the AIMS users.
I'll commit the fix for this shortly.
There was also an uncaught javascript exception happening sometimes in
calendar.js with FF (not IE I think) - happens when attempting to get
the parentNode - I've shoved it into a try/catch block to shield it -
its an FF bug I think - I'll commit that with this one once its tried
out on IE and other FF versions.
Cheers,
Simon
--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your Move
Developer's challenge
Build the coolest Linux based applications with Moblin SDK &
win great prizes
Grand prize is a trip for two to an Open Source event
anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
--
------------------------------------------------------------------------
The information contained in this communication is for the use of the
individual or entity to whom it is addressed, and may contain
information which is the subject of legal privilege and/or copyright.
If you have received this communication in error, please notify the
sender by return email and delete the transmission, together with any
attachments, from your system. Thank you.
------------------------------------------------------------------------