<div dir="ltr">Good rationale :) </div><div class="gmail_extra"> <div class="gmail_quote">On 30 July 2013 12:29, Manuel Quiñones <<a href="mailto:manuq@laptop.org" target="_blank">manuq@laptop.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">MenuPalette landed in sugar-web. It is a palette that contains clickable items. Like the ones in GTK, they have a label of text and can have an icon. When an item is clicked, the palette emits a signal with information that contains the clicked element. The API to create a MenuPalette is this: menuData = [{label: "One", id: "one-button", icon: true}, {label: "Two", id: "two-button", icon: true}, ...]; menuPalette = new menupalette.MenuPalette(invoker, undefined, menuData); The icon is added in CSS right now, like: .palette #one-button span { background-image: url(../icons/one.svg); } But when we have an icon lookup, it would be nice to pass the name of the icon with the data, directly. Note that this is a different approach we are taking in the toolbars, where you can define the buttons in the HTML. Daniel N asked me for an explanation. I think writting HTML directly makes sense for simple and static content. Like adding a <button> element copy/pasting another one from index.html as explained here: <a href="http://developer.sugarlabs.org/activity.md.html#adding%20a%20button%20to%20the%20toolbar" target="_blank">http://developer.sugarlabs.org/activity.md.html#adding%20a%20button%20to%20the%20toolbar</a> And also it makes the developer understand how HTML, CSS and JS work together. Of course that doesn't inhibit the developer to add the button from JS, as explained here: <a href="http://developer.sugarlabs.org/activity.md.html#adding%20html%20content%20dinamically" target="_blank">http://developer.sugarlabs.org/activity.md.html#adding%20html%20content%20dinamically</a> For the palette in question, its content is a bit complex: it can have icons or not, and elements are used for that. So I decided to provide a cleaner API and hide the details of the structure. Structure that is very likely to change as we improve palettes, but the data is less likely to change. Opinions? -- .. manuq .. _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div> -- Daniel Narvaez </div>