Should this be "core"?

[Daniel van Vugt]

Named cursors were not my first choice. There was some arguing when it 
was proposed. I personally prefer a set enums, which matches what common 
toolkits use:

    https://developer.gnome.org/gdk3/stable/gdk3-Cursors.html#GdkCursorType
    http://qt-project.org/doc/qt-5/qt.html#CursorShape-enum
 
http://www.opengl.org/resources/libraries/glut/spec3/node28.html#SECTION000513000000000000000

But you can't kill named cursor support unless you replace it with 
equivalent enums.

BufferStream (or just plain bitmap) cursor support is also still 
required. I think that's what Xmir uses mostly.


On 06/10/15 07:17, Christopher James Halse Rogers wrote:
> On Tue, Oct 6, 2015 at 2:33 AM, Alan Griffiths
> <alan.griffiths at canonical.com> wrote:
>> On 05/10/15 12:12, Alexandros Frantzis wrote:
>>>  but we should ensure
>>>  our built-in cursor images support all the predefined cursor types. In
>>>  our client API we are exposing a set of predefined cursor names, which
>>>  the BuiltinCursorImage implementation doesn't currently support.
>>
>> To clarify, BuiltinCursorImage does support retrieving a cursor image
>> for the predefined cursor names. It is just that it always returns one
>> based on "black_arrow".
>>
>> Is that good enough default behaviour?
>
> Not really.
>
> I think we should do one of two things:
> 1) Remove that cursor-names interface entirely and just rely on getting
> a BufferStream for the cursor, or,
> 2) If the *shell* wants to use the named-cursor support (I don't believe
> it does?) then we should install an xcursor theme on the phone and
> remove BuiltinCursorImage.
>
>