<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Is it possible to run wayland apps on all platforms?"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93086">93086</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Is it possible to run wayland apps on all platforms?
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>wayland
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>zupexad@mailzi.ru
</td>
</tr></table>
<p>
<div>
<pre>To ensure cross-platform each toolkit has its own low-level API for drawing
widgets. In search of another bike I wanted to write a Toolkit, but after I
came to the conclusion that the low-level API for primitives will be the same
as those of wayland. And I thought: what if the layer responsible for the
platform, slipping a little lower? Wayland Protocol will be ported to all
platforms (including microsoft windows) that greatly facilitate the writing of
new cross-platform Toolkit. The only problem when porting wayland, in my
opinion, will be the file descriptor when you create wl_pool. However,
applications must have their own abstractions for shared memory. If wayland
will be a single API on all operating systems, you'll be sure to native
composers, which will render the primitives wayland applications. What do you
think about this?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>