Should make this more clear. To be honest, I think we should restrict
icons to be SVG, and require them to use the CSS styles we specify so we
can enforce a consistent visual style. That way, we don't get into the
whole file extension mess, and where if you specify the extension it's
looked up in the activity first, etc. If the visual characteristics of
icons in the panel are important, which they are, we should enforce
that.
I think it make sense, yeah.
We also need to specify the icon format (maybe thinking a bit more to
the css properties and possibly improving them). Something I was
thinking is that the css should be external, only the class attributes
should be required in the svg files... librsvg does not support external
css yet but we can just add the whole css to the svg file after loading.
Sounds good. We should then reject icons that don't have every element
be part of one of the CSS classes Sugar specifies.
default_type = _web_olpc._udp
Each activity must have a default type. This must follow the
mDNS specification for serivce types and must be globally unique. This
key is required. It is used as the service type for the mDNS service
when the activity is shared.
Do we actually want to make this required? There are activities that
might not be sharable (terminal for example) or that haven't implement
sharing yet.
They should probably all have a default type though... the other
alternative is to reverse the D-Bus service name, s/./_/ and use that as
the default type. I'm not sure that having two such unique identifiers
is useful. The simpler the better.
It might be a good idea, yeah.
Marco
_______________________________________________
Sugar mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/sugar
