Hi all,
We will be entering feature freeze mode today, Jan 26th, as mentioned in the bug status message on 1/24, unless anyone has any objections.
At this point, changes to the codebase should be restricted to bugfixing activity. If you have feature work still needing wrapped up, please try to do so today.
For the next couple of weeks, if you wish to continue to do development work while the release is coming together, you're encouraged to do so on a branch or in the experimental module. See Wiki for details.
Around Feb 1st, we'll switch to a hard freeze mode. At this point the focus will narrow to showstopper and packaging bugs. We'll be putting out release candidates at this point for folks to test out.
The final release will probably come a few days after the hard freeze, assuming everything goes well.
Thanks, Bryce
On Wed, 26 Jan 2005 14:03:14 -0800 (PST), Bryce Harrington <bryce@...260...> wrote:
Hi all,
We will be entering feature freeze mode today, Jan 26th, as mentioned in the bug status message on 1/24, unless anyone has any objections.
I would very much like Mental to create the "move selection to layer below/above" commands if possible. They're really needed for layer work. Otherwise, I'm OK with the freeze.
On Wed, 26 Jan 2005, bulia byak wrote:
On Wed, 26 Jan 2005 14:03:14 -0800 (PST), Bryce Harrington <bryce@...260...> wrote:
Hi all,
We will be entering feature freeze mode today, Jan 26th, as mentioned in the bug status message on 1/24, unless anyone has any objections.
I would very much like Mental to create the "move selection to layer below/above" commands if possible. They're really needed for layer work. Otherwise, I'm OK with the freeze.
Okay, although I know mental is putting in some long weeks at work... Mental, is this something that is within your capacity between now and the 1st?
If not, could someone else be interested in being Mental's wingman on this issue? If it's what I think it is, it shouldn't be too hard, you just need to grok how the layer data structures and hook up some UI code, I think.
Bryce
Quoting Bryce Harrington <bryce@...260...>:
Okay, although I know mental is putting in some long weeks at work... Mental, is this something that is within your capacity between now and the 1st?
No.
If not, could someone else be interested in being Mental's wingman on this issue? If it's what I think it is, it shouldn't be too hard, you just need to grok how the layer data structures and hook up some UI code, I think.
See layer-fns.h for functions for determining the next/previous layer relative to another (you can use SPDesktop::currentLayer to determine the current layer). They're already used for the non-selection-moving commands (you can look at those for more specifics).
The more "interesting" part is grabbing a bunch of arbitrary objects and moving them to the same destination while preserving transforms, etc (and preserving relative stacking order!). The copy/paste code might prove somewhat helpful as a model just to get something out the door, even if it's kind of icky.
What I had hoped to do is write a couple generic functions that took lists of SPObjects and either moved or copied those objects as children of a specified SPObject. That's the hard part I probably don't have time for...
-mental
participants (3)
-
unknown＠example.com -
Bryce Harrington -
bulia byak