On 4/05/2010, at 8:02 AM, Bruno Busco wrote: > Hi Scott, > > 2010/5/3 Scott Gray <[email protected]> > >> Hi Bruno, >> >> Thanks for taking a look, here's a couple of points about your suggestions: >> - You can't mix and match attributes like that on a single element, you'd >> need to have a separate element for each attribute set. >> > > OK, I see what you mean. > > >> - I really wanted to avoid putting too much definition in the component >> file itself, I'd rather it simply declared them rather than try to define >> them. If you have a lot of extensions it would be much easier to break the >> definitions up into separate files. >> > > What I think we should try to do is to have a standard menu definition in a > menus file and have a the injection tag to specify where to inject the menu. > > This would keep the menu definition exactly the same as it is now. > A menu could be used alone as we use it right now and be injected somewhere > at the same time.
I thought about this but there were a couple of things I didn't like: - I don't think you should be able to alter the menu element, if multiple extensions tried to do that then it would just up end being a big mess (although I could be wrong about this and developers would just need to be careful) - Separating the two means more work when you want to extend a menu, you'd have to define a menu in one file and then also define how it should be merged with the base menu Although it should be possible to support both approaches, where you can either define new menu items inline or just point to a separate menu definition and then describe the merge. I'll have a think on what the schema might look like. Thanks Scott
smime.p7s
Description: S/MIME cryptographic signature
