Home / Community & Support / Developer Productivity Tools Forums / ASP.NET AJAX > Scheduler > RecurrenceRuleToString

• Jon Master

  Posted on Mar 4, 2010 (permalink)

  Hi,
  
  I'm using the recurrence code outside of the scheduler.  It's great code, incerdibly fast at what it does (in the past I wrote my own code for calculating dates and it was a nightmare).  What seems to be missing is some of the code from the Winforms implementation.  How do I make and translate string representation of the recurrence rule using the Web dlls.  In Winforms I can use the following to convert to and from a stored string representation :
  

  Telerik.WinControls.UI.Scheduler.ICalendar.CalHelper.RecurrenceRuleToString

   

  Telerik.WinControls.UI.Scheduler.ICalendar.CalHelper.TryParseRecurrenceRule
  
  Also do you have any documentation that describes the structure of the resultant string?  This kind of thing REQ=DAILY;INTERVAL=2.
  
  Best Regards,
  
  Jon

  Reply

• Jon Master

  Posted on Mar 4, 2010 (permalink)

  Not to worry on the first question re the TryParse and ToString - I missed the bit in the docs about that.
  
  I'm still interested in seeing a full list of the string config though as that would be very handy for me testing the application.
  
  Regards,
  
  Jon

  Reply


• Answer Tsvetomir Tsonev Tsvetomir Tsonev

  Posted on Mar 8, 2010 (permalink)

  Hi Jon,
  
  Glad to see that you've managed to solve the first problem. The structure of the recurrence rule is based on a subset of the iCalendar recurrence rule format (RFC2445, 4.3.10 Recurrence Rule).
  
  I hope this helps.
  
  Best wishes,
  Tsvetomir Tsonev
  the Telerik team

  
  Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

  Reply

• Jon Master

  Posted on Mar 8, 2010 (permalink)

  Thanks for that Tsvetomir.
  
  App is coming together now - rather complex but it will be superb when done.
  
  There are a few more scenarios that the recurrence form doesn't cover,  I'll make a list when I'm done,  would it be possible to have these added to the basic form in the scheduler in a later release?
  
  Regards,
  
  Jon
  

  Reply

• Tsvetomir Tsonev Tsvetomir Tsonev

  Posted on Mar 11, 2010 (permalink)

  Hello Jon,
  
  Sure, we'll consider them if they make sense for a reasonably large group of users. We'll discuss them once you have the list ready.
  
  Greetings,
  Tsvetomir Tsonev
  the Telerik team

  
  Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

  Reply

• Jon Master

  Posted on Mar 11, 2010 (permalink)

  Hi Tsvetomir,
  
  One of them that I can remember off the top of my head is day x (Mon,Tue, Wed etc) of the first FULL week in a month year etc.
  
  So for example if we assume that Mondays are the first day of the week (and that could of course change to Sundays etc) then if we want the date of the Friday in the first full week of a month then this month it would be the first friday of the month (5th March 10) whereas next month it would fall on the 9th which is actually the second friday of the month but the first Friday in a full week..
  
  I suppose that the trick on this one is determining whether to allow the user the choice of when the week starts or make it a setting that the programmer sets.
  
  On the subject of the Scheduler I have found working with the WinForms version very cumbersome compared with the Web version.  The classes are very different - is this by design or is it something that will be addressed in the future.
  
  Finally I personally feel that the recurrence side of things is a big enough thing that you really should put it out there as a separate module.  I'm using it outside the scheduler in two scenarios - one of which is for providing a custom control that I reuse in a set of report and system event scheduling pages.
  
  Best Regards,
  
  Jon

  Reply

• Tsvetomir Tsonev Tsvetomir Tsonev

  Posted on Mar 17, 2010 (permalink)

  Hi Jon,
  
  We prefer to keep compatibility with the iCalendar format and such recurrence mode is not part of it. Deviating from it will make importing and exporting data a real headache.
  
  We're more likely to consider generic API for generating occurrences according to custom rules.
  
  We agree on separating the recurrence functionality. The current recurrence API has no external dependencies and we plan to extract the recurrence editing part of the advanced template in a separate control for the upcoming service pack.
  
  We don't try to maintain API compatibility between the different suites in order to take full advantage of the respective platform. I know this is not ideal when moving between suites and we apologize for the inconvenience.
  
  All the best,
  Tsvetomir Tsonev
  the Telerik team

  
  Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

  Reply

• Jon Master

  Posted on Mar 17, 2010 (permalink)

  Hi Tsvetomir,
  
  That makes sense - to be honest I'd not considered the fact that the ical format wasn't going to include that.
  
  Sounds good - recurrence is such a massive headache to program that having this as a stand alone control will be a major addition for the control set.
  
  It's a shame about the API commonality and being completely frank I feel that it's a mistake not to try and keep them common or at last some form of common crossover code at the data level - UI yeah I can accept that there will be differences but not the data level. 
  
  Given the fact that many of the Telerik users will be using the suite for a big application with crossover between web code, PCs with web service access to data and also possibly silverlight connectivity, it strikes me as imperative to keep a certain amount of common code.  Discounting the crossover it would be helpful for us users of the system so that at least it's not like a different product that we have to learn from the ground up.
  
  Regards,
  
  Jon
  

  Reply

Back to Top

Home / Community & Support / Developer Productivity Tools Forums / ASP.NET AJAX > Scheduler > RecurrenceRuleToString