Opened 8 years ago

Last modified 7 years ago

#242 accepted task

Complete initial Qt# UI for WarFoundry

Reported by: ibboard Owned by: ibboard
Priority: major Milestone: WarFoundry Qt 0.1
Component: WarFoundry-GUI-Qt# Version: Trunk
Keywords: qt ui Cc:
Blocked By: #243, #244, #245, #246, #247, #302, #303 Blocking:

Description

The GTK# code is horrendous to work with for anyone who is used to Object Orientation (it uses a C-like API). Qyoto is now sufficiently mature and although QyotoDevelop is broken it can be replaced by built-in file associations and the "uics" .ui compiler.

Change History (32)

comment:1 Changed 8 years ago by ibboard

(In r460) Re #242: Create Qt# UI for WarFoundry

  • Initial commit of project

comment:2 Changed 8 years ago by ibboard

(In r461) Re #242: Qt# GUI

  • Attempt to import to correct location

comment:3 Changed 8 years ago by ibboard

Owner: set to ibboard
Status: newaccepted

comment:4 Changed 8 years ago by ibboard

(In r462) Re #242

  • Delete incorrect commit

comment:5 Changed 8 years ago by ibboard

(In r463) Re #242

  • Delete incorrect commit

comment:6 Changed 8 years ago by ibboard

(In r464) Re #242: Create Qt# UI for WarFoundry

  • Convert to Visual Studio 2005 project
  • Add Solution file
  • Update compile script to be more readable and to check whether rebuilds are needed

comment:7 Changed 8 years ago by ibboard

Blocked By: 243 added

comment:8 Changed 8 years ago by ibboard

Blocked By: 244 added

comment:9 Changed 8 years ago by ibboard

Blocked By: 245 added

comment:10 Changed 8 years ago by ibboard

Blocked By: 246 added

comment:11 Changed 8 years ago by ibboard

Blocked By: 247 added

comment:12 Changed 8 years ago by ibboard

(In r465) Re #242: Create Qt# UI for WarFoundry

  • Add initial Tango icons until Qt4.6 becomes standard with QIcon.fromTheme() method to get native icons

comment:13 Changed 8 years ago by ibboard

(In r466) Re #242: Qt# UI

  • Make use of icons

Re #243: Create "New Army" dialog in Qt# app

  • Create initial rendering of dialog (non-functional)

Re #247: Implement menu options in Qt# app

  • Add initial hook for New Army dialog from menu item

comment:14 Changed 8 years ago by ibboard

(In r468) Re #242: Create Qt# UI for WarFoundry

  • Add logging library
  • Set up WarFoundry environment
  • Log load errors

comment:15 Changed 8 years ago by ibboard

(In r469) Re #242: Create Qt# UI for WarFoundry

  • Fix warnings about Connect strings not being signals

Re #243: Create new Qt# "Create Army" dialog

  • Change from List View to List Widget (views need models, which only handle QVariants and not arbitrary objects)
  • Populate Game System list
  • Populate races list on game system selection changed
  • Set text on some labels

comment:16 Changed 8 years ago by ibboard

(In r473) Re #242: Create Qt# UI for WarFoundry

  • Fill in AssemblyInfo information

comment:17 Changed 8 years ago by ibboard

(In r478) Fixes #243: Create "New Army" dialog in Qt# app

  • Make dialog not show in task bar (add parent to constructor)
  • Add methods to retrieve values

Re #242: Create Qt# UI for WarFoundry

  • Copy lots of implementation from the WinForms app to get some core army loading working

(looks like we need to investigate refactoring commonality)

comment:18 Changed 8 years ago by ibboard

(In r480) Re #247: Implement menu options in Qt# app

  • Hook up army close (can now create, save and close armies)

Re #242: Create Qt# UI for WarFoundry

  • Fix initial window title

comment:19 Changed 8 years ago by ibboard

(In r482) Re #246: Create army tree implementation

  • Create model for the army tree view

Re #242: Create Qt# UI for WarFoundry

  • Add actions directly rather than creating a list

Re #247: Implement menu options in Qt# app

  • Implement enable/disable on undo/redo menu items

comment:20 Changed 8 years ago by ibboard

(In r483) Re #242: Create Qt# UI for WarFoundry

  • Add log4net logging output
  • Output as "WarFoundry.exe"
  • Wrap execution in try...catch to try to debug occasional crashes
  • Refactor common "connect action to menu" method

Re #247: Implement menu options in Qt# app

  • Implement "open" action
  • Make "create" check for closing the old army

comment:21 Changed 8 years ago by ibboard

(In r485) Re #242: Create Qt# UI for WarFoundry

  • Fix MonoDevelop's annoying auto-formatting
  • Remove debugging "true" from IF condition

comment:22 Changed 8 years ago by ibboard

(In r486) Re #242: Create Qyoto GUI

  • Fix ordering of parameters for warning dialog
  • Change dialogs to error dialog, since load failed

comment:23 Changed 8 years ago by ibboard

(In r487) Re #242: Create Qt# UI for WarFoundry

  • Stop translation scanning on images
  • Make open and save dialog start in sensible locations

comment:24 Changed 8 years ago by ibboard

(In r488) Re #242: Create Qt# UI for WarFoundry

  • Fix last check-in, which caused MainWindow not to be compiled

comment:25 Changed 8 years ago by ibboard

(In r490) Re #242: Create Qt# UI for WarFoundry

  • Add preferences and translations (based on GTK# app)

comment:26 Changed 8 years ago by ibboard

(In r492) Re #242: Create Qt# UI for WarFoundry

  • Try resolving SIGSEGV crashes
  • Add more logging
  • Add dialog on major crash so that user gets a message somewhere other than the log file

comment:27 Changed 8 years ago by ibboard

(In r497) Re #242: Create Qt# UI for WarFoundry

  • Tidy up logging
  • Set log rolling to once per start

comment:28 Changed 8 years ago by ibboard

Summary: Create Qt# UI for WarFoundryComplete initial Qt# UI for WarFoundry

comment:29 Changed 7 years ago by ibboard

(In r636) Re #242: Complete initial Qt# UI for WarFoundry

  • Made New Army dialog behave more like WinForms:
    • Disable everything until we need it
    • Make default selections where we can (single items)

comment:30 Changed 7 years ago by ibboard

Blocked By: 302 added

comment:31 Changed 7 years ago by ibboard

Blocked By: 303 added

comment:32 Changed 7 years ago by ibboard

Milestone: WarFoundry 0.1WarFoundry Qt 0.1

Separate UI milestone from API milestone

Note: See TracTickets for help on using tickets.