113477 - Group outlinercols.

Status: RESOLVED FIXED

(Core :: XUL, defect, P1)

Description

[Jan Varga [:janv]]

Current outliner schema is:
<outliner>
  <outlinercol/>
  <outlinercol/>
  <outlinerbody/>
</outliner>

but for easy conversion of old tree to outliner we want to group outlinercols
<outliner>
  <outlinercols>
    <outlinercol/>
    <outlinercol/>
  </outlinercols>
  <outlinerbody/>
</outliner>

This includes modifications of chrome files, rdf liner, content model view
outliner itself, and some CSS frame constructor fu maybe.

Comment 1

[Jan Varga [:janv]]

accepting

Comment 2

[Jan Varga [:janv]]

Attachment: patch for review

Comment 3

[David Hyatt]

sr=hyatt.  Awesome!  Next up after this one is patching the XULOutlinerBuilder
syntax in <template>s to match the outliner content model way of doing things.

Comment 4

[David Hyatt]

Plus we're going to need to add a flag to the templates "flags" attribute that
says whether or not to build a content model for your tree.  e.g.,
flags="dont-build-content".  By default, the template should build content and
we should just attach the content model view.  We can then patch those outliners
that don't need content (e.g., the folder pane in mailnews) to have the flag set
in their <template>s, which will cause them to get the outliner builder view
instead.

Comment 5

[Brian Ryner (not reading)]

Comment on attachment 61697 [details] [diff] [review]
patch for review

r=bryner

Comment 6

[Jan Varga [:janv]]

Fixed. I'll file a new bug for templates.

Comment 7

[Håkan Waara]

Did you post a heads-up to npm.xpfe?  Or is this change merely internal?

Comment 8

[Jan Varga [:janv]]

Attachment: patch for security/

Comment 9

[Jan Varga [:janv]]

jag, could you check in the last patch ?

Comment 10

[Blake Ross]

Anyone can check into security/manager now.