On Jan 13, 12:09 pm, Jan Rychter <[email protected]> wrote:
> Well, what I did with my code was almost a search-replace, you basically
> need to:
Good, this will serve as a migration guide that will accompany the
next release.
> What I initially wanted was to have a (setf (my-children x) children)
> and (my-children x) thing, which would automatically determine the type
> of x and use it as a key. It might be possible to do and it would make
> the interface somewhat nicer -- but I'd still want to keep the
> {get|set}-children-of-type methods, because I have widgets that maintain
> two or three lists of children
So are you going to implement this convenience interface?
I would like to have this.
> This solves my immediate problem, but one could certainly implement a
> real split navigation where one part would influence another. I just
> couldn't justify the effort involved.
Yeah, let's worry about it later.
> You can supply arguments to (setf) functions?
Works fine around here. ;)
How about the tests? Have you written tests for your new nav system
and/or adapted the current tests?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
