Which config.js option controls the format of the date that is used in
alerts? Currently my alerts use the DD-MM-YYYY format. I'd like to
change this to MM-DD-YYYY.
--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
Hi list,
CalDavZAP 0.10.0rc3 available:
demo: http://www.inf-it.com/caldavzap-new/
changelog: http://www.inf-it.com/caldavzap-new/changelog.txt
download: http://www.inf-it.com/CalDavZAP_0.10.0rc3.zip
This release contains lot of fixes (many of them reported here in the mailing list) and one minor new feature - if the client is loaded in the browser and then ./cache_update.sh is executed on the server (or newer version of the client is installed), then the client will show "There is an update available on the server, please reload the page!" and will force users to click to "Reload".
Thanks for your bug reports!
JM
Hello,
i have a strange "sorting" problem within entities of address records.
In my address records, i love to have telephon numbers ordered like this:
1) Mobile number
2) Office number
3) Office fax number
4) Number of assistant
...
and so on.
In this order i enter all the entities. Either in the contact app (iOS
and OSX) or in CardDAVMate. In the Apple apps this sorting is
persistent. In CardDAVMate, the behaviour is a little bit strange.
I enter the entities in the order i want, by changing the label of the
entry appropriate. In the following example, i use the german names, as
this may be the problem?
1) "Büro"
2) "Fax (Büro)"
3) "mobil"
After saving the new or changed contact, the entities are saved in the
order i specified. I can see this in the iOS ans OSX apps. But in
CardDAVMate, the contact refreshes and reorders the entities ON THE
SCREEN like this:
1) "mobil"
2) "Fax (Büro)"
3) "Büro"
So well... In the iOS/OSX apps all is still ok. But now, when changing
the contact again, whatever entry, and save the record, the order of the
entities is changed to the order displayed on the screen (mobil, fax,
...)! In the iOS/OSX apps the order is changed too.
This is annoying, because, if mobil is missing, the fax number is always
on the first position. Is there any reason why the entities (labels?)
are resorted?
Again, like always, thanx a lot for the great work you do on this software.
Regards,
Rudolf
Great! What is your timetable on this? I wouldn't hold you to any
particular date. Just wondering if we are talking about weeks, months,
years.
On 09/17/2013 09:09 AM, Ján Máté wrote:
> Hi Ken,
>
> YES ... we will add this feature.
>
>
> JM
>
> On Sep 17, 2013, at 3:01 PM, Ken Murchison <murch(a)andrew.cmu.edu> wrote:
>
>> Hello,
>>
>> Is allowing ATTENDEES on events/tasks on the roadmap? If the server supports the DAV:calendar-auto-schedule feature, the client really doesn't have to do anything other than a normal PUT of the resource because the server handles delivery of the scheduling request and subsequent replies. The only other request that the client might want to make is displaying the results of a free-busy query to the user to aid in selecting a meeting time.
>>
>> --
>> Kenneth Murchison
>> Principal Systems Software Engineer
>> Carnegie Mellon University
>>
>>
--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
Hello,
Is allowing ATTENDEES on events/tasks on the roadmap? If the server
supports the DAV:calendar-auto-schedule feature, the client really
doesn't have to do anything other than a normal PUT of the resource
because the server handles delivery of the scheduling request and
subsequent replies. The only other request that the client might want
to make is displaying the results of a free-busy query to the user to
aid in selecting a meeting time.
--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
That works.
On 09/12/2013 03:31 PM, Ján Máté wrote:
> :-) ... sorry, here is the fixed version:
>
> http://www.inf-it.com/fixes/0.10.0rc1-fix1x.diff
>
>
> JM
>
>
> On Sep 12, 2013, at 9:25 PM, Ken Murchison <murch(a)andrew.cmu.edu> wrote:
>
>> On 09/12/2013 03:05 PM, Ján Máté wrote:
>>> Hmmm,
>>>
>>> looks like Andrej forgot to commit my regexes to this branch ...
>>>
>>> please try this fix: http://www.inf-it.com/fixes/0.10.0rc1-fix1.diff (+ execute the cache_update.sh)
>>> cache.manifest.rej
>>> Tomorrow we will also check the redundant settings and will fix.
>> With the patch, the client doesn't appear to want to logout. No traffic is sent to my server when I click the key icon and all existing connections just timeout.
>>
>> --
>> Kenneth Murchison
>> Principal Systems Software Engineer
>> Carnegie Mellon University
>>
>>
--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
On 09/12/2013 03:05 PM, Ján Máté wrote:
> Hmmm,
>
> looks like Andrej forgot to commit my regexes to this branch ...
>
> please try this fix: http://www.inf-it.com/fixes/0.10.0rc1-fix1.diff (+ execute the cache_update.sh)
>
> Tomorrow we will also check the redundant settings and will fix.
With the patch, the client doesn't appear to want to logout. No traffic
is sent to my server when I click the key icon and all existing
connections just timeout.
--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
On 09/12/2013 12:44 PM, Ján Máté wrote:
> Hi list,
>
> CalDavZAP 0.10.0rc1 available:
>
> demo: http://www.inf-it.com/caldavzap-new/
> changelog: http://www.inf-it.com/caldavzap-new/changelog.txt
> download: http://www.inf-it.com/CalDavZAP_0.10.0rc1.zip
>
> this relase contains LOT of internal changes and MAJOR improvements
> (e.g. time-range filtering support) so please test it
>
> ... and do not forget to read the changelog
globalDatepickerFirstDayOfWeek appears to be broken. I have it set to
zero and my month and week views still start with Monday.
--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
