Results 1 to 9 of 9

Thread: Current Development Status and Future Plans. Your Feedback Requested

  1. #1
    Administrator
    Join Date
    Oct 2019
    Posts
    184

    Current Development Status and Future Plans. Your Feedback Requested

    At BlueAdept's suggestion, I'd like to detail where I think we are with regard to ShowEQ development, my near term plans, and my vision for future development. I also want to solicit feedback from everyone to get their opinions of how things are, and where you think they should go from here.

    Current Status:

    The release of the first ShowEQ 6 release candidate marks what I would consider "code complete" for the Qt3 to Qt4 migration. Any changes in the near future will be limited to bug fixes to "shore things up" before the official release. Bugs reported in ShowEQ 6 that are not present in ShowEQ 5 will mostly likely be fixed before the final release (though there could be exceptions). Bugs that are in both ShowEQ 6 and ShowEQ 5 may be fixed now or may be put off until after the final release, depending on the bug. As bugs are found and fixed, we'll produce additional release candidates for general use/testing. Your testing and feedback here is crucial.

    Plan for ShowEQ 6 official release

    Once we feel things are ready and outstanding bugs have been addressed, we'll promote ShowEQ 6 to be the primary release. I'm currently expecting this to be around the first of the year (give or take), but this could change depending on the quantity/severity of bugs that are reported, how the CoV release impacts ShowEQ, etc. Once 6.x is promoted to be the primary release, 5.x will be deprecated. Afterwards, we'll continue to update 5.x with new opcodes/structs for a short period of time (maybe a few months), but there are no other changes/fixes planned for 5.x. As such, please plan to upgrade to 6.x before support for 5.x is completely stopped. (There will be one or more posts about it before it actually happens)


    The road to ShowEQ 7 (and beyond)

    Once ShowEQ 6 is released, I'll start working toward ShowEQ 7. This will move us from Qt4 (which is end-of-life) to Qt5. Qt5 will allow us greater flexibility with things like themes and interface customization (hello dark theme!), and should also add support for running on distros that use Wayland instead of X11.

    In addition to 7.x moving to Qt5, I have a number of features and fixes I'd like to implement. These may not all make it into 7.0 (in fact, I expect that many won't), but then there's always the possibility of 7.x point releases or even 8.x...

    (in no particular order)


    1. Autodetect the network interface if it's not specified (or if the specified interface doesn't exist)
    2. Overhaul interface styles/themes, including more customization options
    3. Where possible, fix functionality that used to work but doesn't any more
    4. The ability to show/hide certain things from the map display (at minimum, corpses. But it might useful to be able to specify an arbitrary filter similar to the search/alert filters) Edit: Apparently, this is already possible and I missed it... The "filtered" type in filters/zonefilters will hides things rather than highlight them. Still, it might be nice to have menu toggles for pc/npc corpses
    5. Multi-layer map support (to remove the need to squash multi-layer maps into a single layer).
    6. Implement per-zone preferences (for things that can change from zone to zone, like depth filter head/floor settings)
    7. Add handling for some additional opcodes I've figured out, and maybe figure out a few more
    8. Internal code cleanup to leverage things that exist in Qt4/Qt5 but didn't exist when ShowEQ was written
    9. Improve the UI for adding/editing filters

    There are also some old TODOs (which I think were originally from Zaphod) that I think would be worth implementing if I can pull them off (#10 in particular is not going to be easy).
    10. Specify structs like we do opcodes (via XML) to make it possible to update without recompiling
    11. Assuming 10 can be implemented, add the (opt-in) capability to automatically download the opcode/struct updates from SEQ site
    12. Split the UI part from the capture part, so everything doesn't have to be run as root, and to possibly allow capture on one machine with the UI running natively on another

    13 (added due to my previous edit) Better help/docs on what ShowEQ is capable of and how to do various things.

    Your feedback is wanted!

    What do you think about the above? Love it? Hate it? Which parts? Have additional ideas? Have examples of things that used to work but need fixing?

    Let me know! I'll use your feedback to adjust my TODO list and to help prioritize what I work on.
    Last edited by cn187; 11-09-2020 at 06:00 PM.

  2. #2
    Administrator
    Join Date
    Sep 2005
    Posts
    315

    Re: Current Development Status and Future Plans. Your Feedback Requested

    Thank you for creating a plan to keep SEQ going and keeping the QT foundation from obsolescence!

    I am happy to help with #7... I have a long list of opcodes I've discovered along the way that had no use in the current implementation. Many were added to the zoneopcodes.xml file as a placeholder with the thought someone more ambitious might come along and want to make use of them. It's easy enough to update with current opcodes if/when that data is needed for new functionality or development.

    As for #10, of late it seems the structs have remained fairly stable and they do not mess with them nearly as much as they did in Zaphod's days. That said, some variable length structs were moved out of everquest.h to read data from the variable-length data i.e. the charPlayerProfile struct in zonemgr.cpp. I've become okay with reading structs and adjusting them if that skill is needed.

    Happy to help in whatever limited way I can!

  3. #3
    Administrator
    Join Date
    Oct 2019
    Posts
    184

    Re: Current Development Status and Future Plans. Your Feedback Requested

    Quote Originally Posted by fransick View Post
    I am happy to help with #7... I have a long list of opcodes I've discovered along the way that had no use in the current implementation. Many were added to the zoneopcodes.xml file as a placeholder with the thought someone more ambitious might come along and want to make use of them. It's easy enough to update with current opcodes if/when that data is needed for new functionality or development.
    Awesome! We should definitely compare notes at some point.

    Quote Originally Posted by fransick View Post
    As for #10, of late it seems the structs have remained fairly stable and they do not mess with them nearly as much as they did in Zaphod's days. That said, some variable length structs were moved out of everquest.h to read data from the variable-length data i.e. the charPlayerProfile struct in zonemgr.cpp. I've become okay with reading structs and adjusting them if that skill is needed.
    Agreed. Normally it's really just the 3 structs that change, plus occasionally the spawnshell code when the size of the posData changes. We could start with those, and then worry about converting the others if/when they change.

  4. #4
    Did you SEQ today? BlueAdept's Avatar
    Join Date
    Dec 2001
    Posts
    1,719

    Re: Current Development Status and Future Plans. Your Feedback Requested

    I think this is a good road map of the future of SEQ. Thanks again everyone for helping and keeping it alive.
    Filters for ShowEQ can now be found here. filters-5xx-06-20-05.tar.gz

    ShowEQ file section is here. https://sourceforge.net/project/show...roup_id=10131#

    Famous Quotes:

    Ratt: WTF you talkin' about BA? (Ok.. that sounds like a bad combo of Diffrent Strokes and A-Team)

    Razzle: I showeq my wife

  5. #5
    Registered User
    Join Date
    Nov 2010
    Posts
    82

    Re: Current Development Status and Future Plans. Your Feedback Requested

    Awesome news (and hi once again, I awaken from my slumber )
    I'll have a poke about on the pi to see about getting this release built. Hopefully I can find one of them and remember what I'm doing
    Your dad.

  6. #6
    Administrator
    Join Date
    Oct 2019
    Posts
    184

    Re: Current Development Status and Future Plans. Your Feedback Requested

    Quote Originally Posted by Spanners View Post
    I'll have a poke about on the pi to see about getting this release built. Hopefully I can find one of them and remember what I'm doing
    FYI, there's a recent commit (that didn't make it into RC1) that should fix an issue with detecting Qt on non-x86 platforms. So you'll want to either pull the latest from the pre_6_0_beta branch of svn, or use the --with-qt-* configure flags in order to specify your qt lib/include/bin locations.

  7. #7
    Registered User
    Join Date
    Nov 2010
    Posts
    82

    Re: Current Development Status and Future Plans. Your Feedback Requested

    Quote Originally Posted by cn187 View Post
    FYI, there's a recent commit (that didn't make it into RC1) that should fix an issue with detecting Qt on non-x86 platforms. So you'll want to either pull the latest from the pre_6_0_beta branch of svn, or use the --with-qt-* configure flags in order to specify your qt lib/include/bin locations.

    Noted, thank you.
    I have located 2 Pi's so I'll see what the latest distro's offer in the next couple of days or so and hopefully will get a good run at it all on the weekend.
    Your dad.

  8. #8
    Registered User
    Join Date
    Nov 2010
    Posts
    82

    Re: Current Development Status and Future Plans. Your Feedback Requested

    Apologies: For clarity, Raspberry Pi, clean image of Raspbian/Debian on a Model b Rev 2 512MB


    Initial notes.
    Pulled showeq-6.0.0.0-rc2
    Compile was unhhappy even when using --with-qt-libraries=/usr/lib/arm-linux-gnueabihf as it then went on to be unable to find Qt Documentation, and providing any --with-qt-docs options failed so I skipped the qt validation.

    On running, x-forwarded to xming on my PC (as I did withe the previos version), it loads up and runs, client detection is good and skittles are alive.
    The UI is very "laggy" for want of a better word.

    sidenote: downloaded maps from eqresource, oddly they had very little content for brotherisland and a mapconvert still showed nothing interesting, so I copied my other map accross from the old pi and that works like a charm.

    Map - fixed with import from other pi, dubious source or something ... tbi.

    I'll give it a run to see what else occurs, but if you need any specific feedback on anything please ask and I'll see if I can arrange some

    Cheers!

    Addendum: After about 40 minutes the xming session was unworkable, but nothing really showed up in taskmanager suggesting it was having issues.
    Attached Images Attached Images
    Last edited by Spanners; 11-26-2020 at 04:07 PM.
    Your dad.

  9. #9
    Administrator
    Join Date
    Oct 2019
    Posts
    184

    Re: Current Development Status and Future Plans. Your Feedback Requested


Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

You may post new threads
You may post replies
You may post attachments
You may edit your posts
HTML code is Off
vB code is On
Smilies are On
[IMG] code is On