Thanks jsr. RE DialogReBar. I finished that one this weekend. Thanks for the tip RE FontDrawer. I hadn't even looked at it yet. As you might tell there's still some hooking up of things to do--and I haven't yet turned the menu on. And the toolbar isn't quite finished yet.
I'll let you know when I've got an 0.4.1-based version ready. How about I start with versions 0.4.1.0 and increase the last digit? That way I can release bugfixes for the Qt FamiTracker and I can maintain alignment with your versioning.
Svetlana: thanks for the link. I'll be sure to try your tunes!
Interestingly enough, I noticed that your transparent PNG icons under the instrument list are showing up with fuchsia backgrounds. Perhaps it might be safer to use the same background colour as the other main editing/saving icons near the title bar, or use transparent GIFs.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
TechEmporium: Thanks. I'd noted that and put it low on the list of things to address. Once the functionality of the instrument toolbar is complete, for example. It's about half-way there. The BMP resource for the instrument toolbar has fuschia background. Not sure why.
Actually, the fuchsia background will only appear in Windows when using PNG images that have transparent backgrounds (no other mainstream OS does this). As a matter of fact, the only Windows program that fully supports transparent PNG images is the Pictures & Fax Viewer (&, to a lesser extent, Office XP's Image Editor). If you were to use such a PNG file as a resource in a Windows program, or view it in Internet Explorer, you'll get the fuchsia background because the OS itself doesn't support rendering images with alpha transparency properly.
FamiTracker Qt BURN-DOWN LIST [note: repo version not updated]:
90% 1. Implement following APIs for OSX compatibility:
The APIs have been implemented to the point that a Linux build is functional. Yay! I believe though that I've stumbled into a bug in Ubuntu/Nautilus/whatever RE drag/drop. I can't drop FTMs on top of the running FamiTracker. Looking into other Linux distros.
70% 2. Finish implementing configuration dialogs.
a. Flesh out implementations of CPropertyPage, CPropertySheet.
Implementations of CPropertyPage and CPropertySheet largely complete. Configuration dialogs are functional. Implementation of "General" tab and "Appearance" tab is complete.
30% 3. Finish implementation of CMenu.
a. Finish support for sub-menus.
b. Implement hooks to UI for triggers and updates.
Menu, schmenu... =]
0% 4. Finish implementation of accelerator keys.
a. Implement hooks to UI for triggers.
Acceleratoer schmelerator... [ok I'm just kidding...I know these are very important I just haven't worked them yet].
100% 5. Implement triggers for status bar updates.
0% 6. Finish implementation of custom controls [instrument list!]
For now I'm bypassing the custom control subclassing because I haven't figured out how to draw the Qt-widget equivalents on top of existing Qt widgets. The custom control functionality seems limited to things that are already largely available in the Qt-widget equivalents of the MFC controls, anyway [context menu, default text, etc].
0% 7. MIDI
a. Find out how to do it OSX-ish or Linux-ish.
b. Consider leaving MIDI a "Windows only feature" for now.
100% 8. FontDrawer.cpp? DialogReBar.cpp? Exception.cpp?
a. Might not need these or at least not entirely. Figure this out.
DialogReBar implementation complete. Exception and FontDrawer are being ignored.
9. Test, test, test...
Ongoing...
0% 10. Port 0.4.2 functionality.
Hopefully stuff hasn't moved around much in the dialogs...if so I'll need to get hyarion's MFC RC-file parser working so it can do the MFC-to-Qt resource conversion for me automatically!
FamiTracker Qt BURN-DOWN LIST [note: repo version not updated]:
100% 1. Implement following APIs for OSX compatibility:
90% 2. Finish implementing configuration dialogs.
Configuration dialogs are functional. Implementation of "General", "Shortcuts", and "Appearance" tab is complete.
100% 3. Finish implementation of CMenu.
70% 4. Finish implementation of accelerator keys.
There's some nastiness here. Still slogging through it. Need to write a virtual key translator.
100% 5. Implement triggers for status bar updates.
60% 6. Finish implementation of custom controls [instrument list!]
For the first release I'm just going to leave these as Qt-based controls with adaptations to cover the functionality added by the MFC subclassing.
0% 7. MIDI
a. Find out how to do it OSX-ish or Linux-ish.
b. Consider leaving MIDI a "Windows only feature" for now.
Needed to register just to say this is awesome! I came across FamiTracker the other day and have been messing around at work. Have a Mac at home and would love to continue using it (Currently with WineBottler). It works..okay...
Is this the only place for status updates or do you have a development website somewhere I can keep checking?
RandomSkratch: thanks for the feedback. Unfortunately I don't have time to maintain a web-site actively for status updates. So yes, this is really the only place I've been tracking status.
I must say, I was ignoring this for a while, and, well, now that I need it, I feel silly for not checking on it before.
this is also really just a post so that I get updates on this thread whenever someone posts in it, because if there's a way to subscribe to threads elsewise in this forum software, I haven't found it yet
Honestly I'd hoped to have had a release ready by now, but progress has been slow lately. I am still working on shortcut key translations. There is an issue with GetFocus/SetFocus that impacts copy/paste. Also, before I can have a release ready for Linux or OSX I need to work on control realignment. I don't use Qt's widget-layout system because it'd preclude supporting MFC's arbitrary widget placements. But that has size/alignment issues on Linux and OSX. It's worse for instrument dialogs.
_______________________
"im going to continue making this crazy stuff then after a while my style will be so sick that you will be like damn suuun that shit is so sick i dont even get it. i will be like bro its ok.. you dont have to." -omgdonut
Very understandable. Hopefully you can figure it out without too much more headache.
Also, side question that hardly has to do with this, do you know how difficult it might be to port a Qt application to GTK+? I'm curious as, once I get myself learned and practiced in C and such, I wish to do exactly that.
Also, side question that hardly has to do with this, do you know how difficult it might be to port a Qt application to GTK+? I'm curious as, once I get myself learned and practiced in C and such, I wish to do exactly that.
I don't know GTK+--yet. There's really two different ways you can go about these kinds of port, I think. One is creating a "high level emulation of Qt in GTK+", like I did for MFC in Qt; the other is rewriting all of the visualization portions of the program in whatever screen widget system GTK+ uses. NukeThePotato took the latter approach for a Qt version of FamiTracker...and came up with something useful, though I'm not sure how complete.
Some of your decision will revolve around how well the visualization portions of the program are segregated from the algorithms. If the program is not your original work, some of your decision will revolve around how you want to keep alignment with the original author's updates to the original code-base.
I'd be happy to help you try to figure it out if you want to share more in PM or whatever.
I think it'd make sense to put out a release even though it's not complete. Give people a chance to use it and give feedback on what's right, what's almost right, what's sorta not working, and what's just plain broke/unimplemented. I'll work on that.
Honestly I'd hoped to have had a release ready by now, but progress has been slow lately. I am still working on shortcut key translations...
When using FamiTracker via WineBottler one of the more frustrating missing key commands was the lack of Delete (Windows Delete, not Mac Delete which is Backspace). Not sure how you will implement this - maybe Option + Delete or something similar?
cpow wrote:
I think it'd make sense to put out a release even though it's not complete. Give people a chance to use it and give feedback on what's right, what's almost right, what's sorta not working, and what's just plain broke/unimplemented. I'll work on that.
Yes I'd definitely be interested in testing it out to see what's right/not quite/etc.
Thanks again for all the hard work you're putting into this!
) .png)
