Search results

From Davical
Jump to navigationJump to search
  • === Future ===
    820 bytes (123 words) - 13:34, 30 June 2015
  • === Future ===
    1 KB (144 words) - 23:58, 8 January 2015
  • Pages under this are used for planning functionality future DAViCal releases.
    133 bytes (16 words) - 23:42, 11 September 2011
  • ...e, and DAViCal, and help new users through configuration problems, discuss future enhancements, or sometimes just say good morning to each other from their l
    627 bytes (91 words) - 05:08, 12 March 2014
  • ...ki. If you can't find it here, but do find it elsewhere, consider helping future visitors by adding the information in some relevant location. Refer to the
    748 bytes (121 words) - 11:18, 3 March 2021
  • ...or not, but I thought it worth mentioning should it become an issue in the future.
    2 KB (216 words) - 12:48, 23 March 2011
  • [[Category:Roadmap]] [[Category:Future]]
    1 KB (197 words) - 21:26, 1 January 2016
  • ...re used right now (and what version) and which are going to be used in the future ("Subpages", "UniversalLanguageSelector) * A new release should be prepared in the near future to make the accumulated bug fixes available to our users. We should probabl
    3 KB (380 words) - 15:00, 5 October 2015
  • ...are welcome, both code and/or translations are welcome. As my plan for the future is to convert the interface to web 2.0 (AJAX, JSON etc.) I am especially we
    1 KB (200 words) - 00:14, 18 October 2011
  • ...of the user friendly name. A WebDAV browse capability will be added to a future version to address this.
    1 KB (228 words) - 02:54, 27 October 2009
  • Next meeting: date TBD, but probably 3-4 months in the future.
    1 KB (174 words) - 05:13, 9 March 2018
  • ...you create a configuration file for this program to make it easier in the future.
    2 KB (319 words) - 21:17, 29 October 2008
  • to make it easier for future developers to understand and contribute to the
    2 KB (301 words) - 09:38, 2 October 2015
  • ...uld be a useful template for anyone else writing an [[Auth Plugin]] in the future. ...mous bind to the LDAP server, because it is behind the firewall but in the future I want to make the directory available outside the firewall! Before that c
    6 KB (942 words) - 23:29, 8 January 2015
  • ...authentication plugin may define it's own configuration settings. At some future point when configuration of DAViCal can be done other than through editing ...change will be required as other enhancements are added to DAViCal in the future.
    6 KB (932 words) - 02:13, 2 January 2016
  • ...nfortunately these did not ship in the past but they should be included in future versions in <code>/usr/share/doc/davical/examples</code>.
    3 KB (470 words) - 19:06, 31 December 2015
  • ...encoding setting and just let it be stored as LATIN1. What happens in the future when we do migrate to UTF8?
    3 KB (404 words) - 02:34, 15 July 2010
  • ...functionality available at present, but may need to be extended further in future.
    4 KB (559 words) - 22:07, 25 February 2008
  • ...nes to be named in line with the Olson timezone naming convention. In the future this might become less necessary as DAViCal adds support for the timezone s
    4 KB (498 words) - 07:49, 16 September 2011
  • * Need a roadmap and beta releases for future versions.
    2 KB (330 words) - 07:14, 17 December 2014

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)