On Mon, Feb 16, 2009 at 3:46 AM, Leslie P. Polzer <[email protected]> wrote: > You want to connect with Ian to avoid duplicating work. Did Ian mention doing this? I spoke to him about this some time ago (back in the summer) but I don't think I heard anything about this since then.
> If the ID is an ephemeral symbol then it will not be an URL > that can be shared. Yes. Resolving by widget ID would probably happen only if there are two slots with the same name which should be rare enough. It would then be up to the programmer to provide the IDs for appropriate widgets. > How is this going to mix with AJAX updates? For the updates to show up on the query string, the relevant links and forms would have to be AJAX-free (at least until someone works on integrating the URL hash thing into weblocks). This might be done automatically (changing a state of a slot that is marked to be serializable into the URL would force a refresh), or the burden might be left on the user (which isn't that big of a deal, it seems). > Gladly, but you need to be a bit more specific. Are you talking about > upcoming merges, or a certain window that has already gone by...? I was thinking about everything from two months ago until now (plus upcoming changes). It's obviously difficult to come up with a detailed changeset (I can just look at the hg log), so instead if any reasonably major features come to mind, it'd be great if you could mention them with a very brief overview. I can then dig in deeper myself. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
