[PATCH weston] ivi-shell: add screen_remove_layer API

[Pekka Paalanen]

On Tue, 7 Feb 2017 12:28:45 +0000
"Ucan, Emre (ADITG/SW1)" <eucan at de.adit-jv.com> wrote:

> Hi Pekka,
> 
> > -----Original Message-----
> > From: Pekka Paalanen [mailto:ppaalanen at gmail.com]
> > Sent: Montag, 6. Februar 2017 13:47
> > To: Ucan, Emre (ADITG/SW1)
> > Cc: wayland-devel at lists.freedesktop.org
> > Subject: Re: [PATCH weston] ivi-shell: add screen_remove_layer API
> > 
> > On Mon, 30 Jan 2017 14:42:42 +0000
> > "Ucan, Emre (ADITG/SW1)" <eucan at de.adit-jv.com> wrote:

> > > I want to implement a shared library for ivi-shell (libweston-ivi)
> > > similar to weston-desktop library, when I have time. Then, it would
> > > be easier to handle ABI breakages. Because it will be parallely
> > > installable. Another advantage is that adding an API would be just a
> > > minor version bump, because it would be backwards compatible.  
> > 
> > There are a lot of shared objects involved with ivi-shell already.
> > Would be nice to see some high level plans and architecture
> > documentation on how it all fits together and which parts can change
> > how. I fear there might be too many different interfaces that need to
> > be maintained.  
> 
> What is the preferred document type for a design document in wayland community?
> Should I put these information in READMEs or create some sequence diagrams ?

Hi,

we're pretty bad at that so far. It should probably be something in the
main affected repository, i.e. Weston in this case. I don't think we
generate any docs in particular in Weston (yet), so any way people can
read it is fine.

Plain text in a README is the most portable and easy to read with
anything, even through cgit links directly. If ASCII art is too
painful, then certainly you can use any common image format. If you used
e.g. Dia to draw it, I'd submit both the .dia file and a .png rendering
of it.

If you can host a web site somewhere, you could also just put link
there in a README in Weston.

You would need to explain the architecture in your submission too, at
least in the cover-letter, so that we can tune to the right mindset for
reviewing it. Pointing to a single place of doc would make things
easier.

It does not need to be a large fancy doc, just something that sets the
big picture.


Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20170207/a29ddf8d/attachment-0001.sig>