use speech_recognition_msgs instead of jsk_gui_msgs

[furushchev]

This is related with jsk-ros-pkg/jsk_common#610 and #1.
We intend to move GUI related messages (jsk_gui_msgs) to upstream.

[k-okada]

If we move jsk_gui_msgs to upstream does that include VoiceMessage message? or are you going to remove that?

[furushchev]

I think It depends on the generality of messages.
VoiceMessage, for example, is now more generalized messages, not only used with smart phone, so I think it' better to graduate as independent message. (and it is speech_recognition_msgs). (Also I doubt this message is related to jsk_"GUI"_msgs)
Of cource, gui_msgs is still needed because of gui specific messages such as Swipe or some gui specified messages.
Anyway, I think, VoiceMessage is now not needed for jsk_gui_msgs, because we should now use more common message speech_recognition_msgs.

[k-okada]

in that case, we do not need entire jsk_gui_msgs, for example Imu is more
general message, camera is as well, I think there are no message that only
used smart_gui. So basic idea of jsk_gui_msgs is to provide set of sensor
message that is provided from smart phone and that should correspond to
some class of android SDK (and may be iphone SDK as well),

so you're proposing that we should consider the smart phone as robot,
they're collection of sensors and we do not define the set of available
sensors for Android/iPhone. That's ok, so please create apk and upload to
GooglePlay, and also tell @kochigami that there are API breaking changes.

◉ Kei Okada

On Sat, Dec 6, 2014 at 3:06 PM, Furushchev [email protected] wrote:

I think It depends on the generality of messages.
VoiceMessage, for example, is now more generalized messages, not only used
with smart phone, so I think it' better to graduate as independent message.
(and it is speech_recognition_msgs). (Also I doubt this message is related
to jsk_"GUI"_msgs)
Of cource, gui_msgs is still needed because of gui specific messages such
as Swipe or some gui specified messages.
Anyway, I think, VoiceMessage is now not needed for jsk_gui_msgs, because
we should now use more common message speech_recognition_msgs.

—
Reply to this email directly or view it on GitHub
#36 (comment)
.

[furushchev]

OK. To create apk seems to be really tough work, but I try to do it.
And, when I make jsk_gui_msgs deprecated, I'll inform her.

[k-okada]

what was the conclusion of this discussion?

[furushchev]

Sorry for late response.
I think it would be better to migrate message that is used as speech recognition from jsk_gui_msgs to speech_recognition_msgs.
message of speech_recognition_msgs includes all functionality of the one of jsk_gui_msgs, so we can just substitute messsage name to use in android codes, but there is no test environment. When I find time to make document to build android project, I'll do this migration.

[k-okada]

ok, move to #63