Your support is needed and is appreciated as Amigaworld.net is primarily dependent upon the support of its users.
|
|
|
|
amigabounty.net announces a bounty to get WxWidgets ported to AmigaOS4.1.
UPDATE - 27.05.2009: Alexandre Balaban has been assigned to the bounty and deadline has been changed as agreed with Alexandre. Please consider making a donation to the bounty if you haven't done so already.
Having WxWidgets available on AmigaOS4.1 will help give us easier access to a huge number of cross-platform applications and it will allow AmigaOS4 developers to reach a wider audience if they develop using WxWidgets. A few examples of applications using WxWidgets include: KiCAD, Audacity, Code::Blocks IDE and (originally from the Amiga) Audio Evolution 5.
Read more...
Please visit amigabounty.net by clicking the link below to learn more about the WxWidgets bounty.
Links: WxWidgets bounty project site.
WxWidgets website. |
|
|
|
| STORYID: 4910
|
Goto page ( 1 | 2 | 3 )
Poster | Thread | Georg
| |
Re: WxWidgets bounty opened. Posted on 29-May-2009 9:46:48
| | [ #41 ] |
| |
|
Regular Member |
Joined: 14-May-2003 Posts: 451
From: Unknown | | |
|
| Quote:
Would be good if AROS and Morphos could benefit from this also but as it will be Reaction based I don't know how much use it will be |
I don't know much about WxWidgets, but I would almost bet that you will end up with a mess if you are trying to map it to Reaction or Intuition boopsi gadgets in general. Because that's a completely different way to handle GUIs compared to just about all other GUIs other there which all run in app task(s) and not partly (input handling, sometimes rendering) in some system task (input.device) with a lot of limitations: stack usage, spend to much time there and you get short freezes (mouse stutter), cannot use functions which require a Process, what about timers, etc.?
And apps using WxWidgets certainly have some way to define their own GUI classes, so even if you turn all standard GUI classes provided by WxWidgets into Boopsi Classes with all the required hacks and stuff (for things which are not possible/too slow in input.device task, use hacks to handle it (MUI like) in app task, or use helper sub processes, ...) what about the custom classes used by the apps? |
| Status: Offline |
| | Trixie
| |
Re: WxWidgets bounty opened. Posted on 29-May-2009 10:28:21
| | [ #42 ] |
| |
|
Amiga Developer Team |
Joined: 1-Sep-2003 Posts: 2090
From: Czech Republic | | |
|
| Quote:
Here is a work-in-progress screenshot of AE5.1 with MIDI sequencing: |
Looks cool! _________________ The Rear Window blog
AmigaOne X5000/020 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition
|
| Status: Offline |
| | andres
| |
Re: WxWidgets bounty opened. Posted on 29-May-2009 11:54:27
| | [ #43 ] |
| |
|
Regular Member |
Joined: 3-Nov-2008 Posts: 329
From: Firenze (Italy) | | |
|
| @DaveAE
Seems very interesting! _________________ A1200/020+68882 - 6 MB RAM - AmigaOS 3.0
Home Recording Audio
|
| Status: Offline |
| | Hans
| |
Re: WxWidgets bounty opened. Posted on 29-May-2009 22:24:40
| | [ #44 ] |
| |
|
Elite Member |
Joined: 27-Dec-2003 Posts: 5067
From: New Zealand | | |
|
| @Georg
Quote:
I don't know much about WxWidgets, but I would almost bet that you will end up with a mess if you are trying to map it to Reaction or Intuition boopsi gadgets in general. Because that's a completely different way to handle GUIs compared to just about all other GUIs other there which all run in app task(s) and not partly (input handling, sometimes rendering) in some system task (input.device) with a lot of limitations: stack usage, spend to much time there and you get short freezes (mouse stutter), cannot use functions which require a Process, what about timers, etc.? |
WxWidgets is designed as a wrapper for whatever the native GUI system is. We'll have to see, but I think that it should be okay.
Quote:
And apps using WxWidgets certainly have some way to define their own GUI classes, so even if you turn all standard GUI classes provided by WxWidgets into Boopsi Classes with all the required hacks and stuff (for things which are not possible/too slow in input.device task, use hacks to handle it (MUI like) in app task, or use helper sub processes, ...) what about the custom classes used by the apps? |
It should be possible to create a wrapper that allows wxWidgets custom gadgets to be custom ReAction gadgets. In fact, that's the first thing that I would do if I were involved, since this would make wxWidgets immediately usable, even though the native look and feel wouldn't be there yet.
HansLast edited by Hans on 29-May-2009 at 10:30 PM.
_________________ http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project. https://keasigmadelta.com/ - More of my work.
|
| Status: Offline |
| | joeled
| |
Re: WxWidgets bounty opened. Posted on 2-Sep-2009 8:26:22
| | [ #45 ] |
| |
|
Cult Member |
Joined: 25-Dec-2007 Posts: 724
From: Uppsala, Sweden | | |
|
| | Status: Offline |
| |
|
|
Goto page ( 1 | 2 | 3 )
[ home ][ about us ][ privacy ]
[ forums ][ classifieds ]
[ links ][ news archive ]
[ link to us ][ user account ]
|