Bug 110191 - QtRuby: use symbols to reference signals and slots
Summary: QtRuby: use symbols to reference signals and slots
Status: RESOLVED UNMAINTAINED
Alias: None
Product: bindings
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kde-bindings
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-04 23:29 UTC by Caleb Tennis
Modified: 2022-12-22 06:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Caleb Tennis 2005-08-04 23:29:20 UTC 
Version:            (using KDE KDE 3.4.2)
Compiler:          gcc 4.0.1 
OS:                Linux

Currently, in QtRuby we do something like this:

class MyClass < Qt::Object
  slots 'mySlot()', 'mySecondSlot()'
  signals 'mySignal()'
end

It would be nice if for convenience we could do this:

class MyClass < Qt::Object
  slots :mySlot, :mySecondSlot
  signals :mySignal
end

For signals and slots which take no argument.
Comment 1 Richard Dale 2005-08-05 22:31:04 UTC 
On Thursday 04 August 2005 23:29, Caleb Tennis wrote:
[bugs.kde.org quoted mail]
Yes, that wouldn't be too difficult. 

But it would be nice to invent a syntax that worked with slots and signals 
that have arguments too, and specify the arg types in ruby terms like 
'Integer' instead of int and 'String' instead of 'QString' and so on.

-- Richard

-- Richard
Comment 2 Justin Zobel 2021-03-09 05:24:42 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 3 Mathieu Jobin 2022-12-22 06:52:42 UTC 
QtRuby only existed for Qt4 and Korundum, which never got updated for 5.x

This is unmaintained and any effort towards QtRuby for Qt6 will be from scratch.

Therefore, closing this ticket