At 05:19 PM 12/7/2007 -0800, Bryan Stearns wrote:
Fixing that will take a lot more work, both on the plugins, on the sizer, and on the existing attribute editors (sizing behavior is distributed all over the place!), but I don't think now is the right time to figure those issues out, since the rearchitecture effort will obsolete all of this soon.

Currently, we're proceeding under the assumption that the rearchitecture is experimental, so this shouldn't be given too much weight in a decision.


To accomplish this, I changed the way detail views are declared (since layout information needs to be persisted differently). I got this generally working for the core detail view, but once I tried to update all the plugins' detail views, I found that some of my earlier assumptions didn't hold, and that in some cases, the plugins don't follow (what I thought were) the rules for how new items and detail views are added to Chandler.

The latter isn't a problem for the rearchitecture branch, since porting is assumed as a requirement anyway. So if the issues can be addressed in the form of a pure-wx sizer that isn't specifically tied to blocks or attribute editors, we can *definitely* make use of it in the rearchitecture branch.


So: I'm setting aside this work in favor of the other stuff that's piling up and prioritized for 1.0. It's possible that the sizer work will be useful in the rearchitected world - I'll be talking with Grant about this soon.

We planned to raid your work for ideas as soon as practical, since we should be doing some detail view work soon. :) I'd rather we not duplicate your efforts. Maybe at some point we could talk about resurrecting and enhancing the sizer you made?

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to