Status of Input Proposals?

[Klaim - Joël Lamotte]

I am having trouble gathering info about the status of the different proposals

for input and their feedback:

 - n4463
 - p0249r2 (I found the report from Micheal Wong for R0  in this discussion group, but not after that)

Does someone around here have some info?

I'm resuming my work on an alternative input proposal since p0669r0 and CPPCON/SG14 meeting

convinced me it would be a good thing and I need to compare my ideas

to these proposals and feedback from the committee to them.

A. Joël Lamotte

[Guy Davidson]

Be advised that the graphics paper must include an input proposal (Beman says so): if you have something to offer, please do consider joining us.

[Michael McLaughlin]

Input proposals are definitely welcome! But as a suggestion, consider writing it conceptually rather than with direct code bits. The code bits for P0267 are still evolving so right now writing a full interface specification (excluding pseudo code) would be a waste of your time.

 

Once P0267 is sent to LWG, the interface for "output" should be stable enough that it would no longer be a waste of time to go through the effort of drafting a proposed input interface.

 

Regardless, input concerning 2D graphics input is most definitely welcome! (No pun intended.)

 

-Mike

 

--
You received this message because you are subscribed to the Google Groups "SG13 - HMI" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sg13+uns...@isocpp.org.
To post to this group, send email to sg...@isocpp.org.
Visit this group at https://groups.google.com/a/isocpp.org/group/sg13/.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/sg13/67c3f694-35be-45f1-ae57-0893fedb8260%40isocpp.org.

[Klaim - Joël Lamotte]

On 12 October 2017 at 22:00, Guy Davidson <elgu...@gmail.com> wrote:

Be advised that the graphics paper must include an input proposal (Beman says so): if you have something to offer, please do consider joining us.

Thanks for the heads up, I thought it was supposed to be a separate but complementary subject - apparently not so much.

What about the audio proposal, that seem related, which was presented at last SG14 meeting (at CPPCON)? The author

was interested into doing the same than the 2D graphics proposal but with audio.

 

On Thursday, 12 October 2017 14:55:52 UTC+1, A. Joël Lamotte wrote:

I am having trouble gathering info about the status of the different proposals

for input and their feedback:

 - n4463
 - p0249r2 (I found the report from Micheal Wong for R0  in this discussion group, but not after that)

Does someone around here have some info?

I'm resuming my work on an alternative input proposal since p0669r0 and CPPCON/SG14 meeting

convinced me it would be a good thing and I need to compare my ideas

to these proposals and feedback from the committee to them.

A. Joël Lamotte

[Klaim - Joël Lamotte]

On 13 October 2017 at 01:42, Michael McLaughlin <mike...@gmail.com> wrote:

Input proposals are definitely welcome! But as a suggestion, consider writing it conceptually rather than with direct code bits. The code bits for P0267 are still evolving so right now writing a full interface specification (excluding pseudo code) would be a waste of your time.

 

 

I'm not totally sure I understand this remark, but maybe that's because I'm not familiar with any input part from P0267?

 

Once P0267 is sent to LWG, the interface for "output" should be stable enough that it would no longer be a waste of time to go through the effort of drafting a proposed input interface.

 

I will have to go back to current P0267 proposal to make sure I'm not missing anything,

but so far I believed (from reading previous versions of the proposal that not much code would be directly shared between what I was going to propose and P0267.

Except maybe some basic types.

My understanding of input and output is that, unfortunately, they cannot share a similar interface.

However they can share the same principles, which is what I tried to do. Anyway I'll try to redact something high level for you all to tell me if it goes on par

with input you got.

 

Regardless, input concerning 2D graphics input is most definitely welcome! (No pun intended.)

 

Haha cool. :)

 

-Mike

 

On Thu, Oct 12, 2017 at 4:00 PM, Guy Davidson <elgu...@gmail.com> wrote:

Be advised that the graphics paper must include an input proposal (Beman says so): if you have something to offer, please do consider joining us.

On Thursday, 12 October 2017 14:55:52 UTC+1, A. Joël Lamotte wrote:

I am having trouble gathering info about the status of the different proposals

for input and their feedback:

 - n4463
 - p0249r2 (I found the report from Micheal Wong for R0  in this discussion group, but not after that)

Does someone around here have some info?

I'm resuming my work on an alternative input proposal since p0669r0 and CPPCON/SG14 meeting

convinced me it would be a good thing and I need to compare my ideas

to these proposals and feedback from the committee to them.

A. Joël Lamotte

--
You received this message because you are subscribed to the Google Groups "SG13 - HMI" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sg13+uns...@isocpp.org.
To post to this group, send email to sg...@isocpp.org.
Visit this group at https://groups.google.com/a/isocpp.org/group/sg13/.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/sg13/67c3f694-35be-45f1-ae57-0893fedb8260%40isocpp.org.

--
You received this message because you are subscribed to the Google Groups "SG13 - HMI" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sg13+uns...@isocpp.org.
To post to this group, send email to sg...@isocpp.org.
Visit this group at https://groups.google.com/a/isocpp.org/group/sg13/.

To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/sg13/CAL_%3DNOruBF%3D5dHRGm7-vebcALYcchW8Co2Gb-F-heLNXfo7_GQ%40mail.gmail.com.

[Michael McLaughlin]

As for audio, it probably falls more in SG14 but I can't speak for Herb.

 

> My understanding of input and output is that, unfortunately, they cannot share a similar interface.

 

I apologize for the misunderstanding. The intent is, and always has been, to have the 2D graphics proposal (P0267) include both. The intended design is that output types will serve as base classes for types that combine input and output. The original focus has been on output for the simple reason that output is useful by itself while input only means something if it serves as feedback to output. At least as far as 2D graphics is concerned.

 

That said, while there's a broad consensus among the P0267 authors that input should include keyboard, mouse, and touch, how to do that is still under consideration. Specifically, we are still thinking about ways to make input be as non-platform specific as possible while still providing the desired functionality. It's likely that in some places we will need to rely on "implementation-defined" behavior (and possibly features), but we want to minimize that.

 

Anyway, right now the focus is on getting output done. But the thought that input would be an "add on" to output using derived classes has always been in our thoughts as we've worked on the output API.

 

-Mike

 

To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/sg13/CAOU91OMGH7MExSwwW53Ki8YvFReU2KjJevUGcnw88Qp%2BWy-nVQ%40mail.gmail.com.

[Klaim - Joël Lamotte]

On 13 October 2017 at 02:52, Michael McLaughlin <mike...@gmail.com> wrote:

As for audio, it probably falls more in SG14 but I can't speak for Herb.

 

> My understanding of input and output is that, unfortunately, they cannot share a similar interface.

 

I apologize for the misunderstanding. The intent is, and always has been, to have the 2D graphics proposal (P0267) include both. The intended design is that output types will serve as base classes for types that combine input and output. The original focus has been on output for the simple reason that output is useful by itself while input only means something if it serves as feedback to output. At least as far as 2D graphics is concerned.

 

That said, while there's a broad consensus among the P0267 authors that input should include keyboard, mouse, and touch, how to do that is still under consideration. Specifically, we are still thinking about ways to make input be as non-platform specific as possible while still providing the desired functionality. It's likely that in some places we will need to rely on "implementation-defined" behavior (and possibly features), but we want to minimize that.

 

Ok so my ideas seems to matches this description, so I'll try to redact something understandable asap.

 

Anyway, right now the focus is on getting output done. But the thought that input would be an "add on" to output using derived classes has always been in our thoughts as we've worked on the output API.

 

Could you point me to some of the classes you thought might be used as base for some input API?

Or did you mean "derived" in style, not in class inheritance?

 

To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/sg13/CAL_%3DNOrtBumO6ypKB2PCk38GrL20rUdc16MdZYDANKgKtR7C1A%40mail.gmail.com.