In response to having views generate items, Alec said: > God no. Thats more or less what we're trying to avoid.. since views CANT > generate events, we need to generate them automatically. The only other > place for events to be generated would be in the query system, and I it > seems like we don't really have the bandwidth to be dealing with that > right now.
It seems to me that the options for having the calendar view see occurrences of indefinitely recurring events for 20 year in advance are: 1) Make the view responsible for creating the relevant occurrences (yes, I know, thunderous -1's from the list) 2) Make the query system responsible for generating the relevant occurrences 3) Generate enough events that we're sure the apocalypse will have arrived before we run out (I support avoiding theology in Chandler :) 4) Don't generate occurrences past a certain point, warn the user visually if they're past that point 5) Get the model/view contract refined to the point that we can use proxy objects and avoid generating occurrences Does this seem like a complete list? I've been convinced that 5) is overreaching for 0.6. 1) is inelegant and liable to incite insurrection. 2) seems fine to me, I don't know if it would be OK with Ted. 3) is reasonable, but really ugly, in my humble opinion. 4) seems like a great 0.6 solution to me Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
