____  
 |  _ \ 
 | |_) |
 |  _ < 
 | |_) |
 |____/ 
        
        

  _____  
 |  __ \ 
 | |__) |
 |  _  / 
 | | \ \ 
 |_|  \_\
         
         

         
         
 ##   ## 
 ## # ## 
 ####### 
 ####### 
  ## ##  
         

_________
\__    _/
   )  (  
   |  |  
   |  |  
   |  |  
|\_)  )  
(____/   
         

         
         
  #####  
 #       
  ####   
      #  
 #####   
         

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
'''Why even go here?''' Because [http://www.trolltech.com/ TrollTech] has released a GPL'd version of QT4 for Windows. This is an awesome crossplatform toolkit that supports X11, Windows, and !MacOS X. I was going to let QT slide because of the lack of GPL Windows support, but now it's been announced, I think it's worth pursuing. I'm very concerned not to repeat the concept that was used in MegaTunix. It resulted in a tuningsoftware that is tied to GTK. A tuningsoftware that is tied to very simple IO (input and GUI operations) API can be made to run anywhere (GBA, win, linux, GTK, QT, etc...) - the other way around is not true. The resulting limitations to (for example compile-time language and font selection and screen optimization) is a small price for this app IMHO (unlike for a spreadsheet or office app). Features of interest: * platform ** Mac ** Windows ** Linux ** and maybe with limited functionality on OtherTuningSoftware/NintendoGameBoy ? *** [http://www.trolltech.com/products/embedded/index.html QT Embedded] (and [http://www.trolltech.com/products/qtopia/index.html QTopia]) doesn't seem to support much other than Linux on the embedded scene. I think much of the design should be usable, but probably not the code itself. * Multiligual - I propose compile time language selection (not runtime) ** PC platforms can handle runtime i18n easily, although I could imagine restrictions on GBA or similar? * IO support ** Serial IO * Object Oriented * Native == fast * Mature '''Why not Java?''' It seems to be too heavy for end-user applications. Installing the JRE is bad enough, but getting RXTX installed as well is too much for many end users. It's also slow on the old laptops many users will have. Light versions like Waba work fine on the PDA, but not ideal for PC use. ---- '''QTune''' General Features: * Easy installation and removal ** [http://www.rpm.org/ rpm]or [http://www.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html deb] packages for Linux ** [http://www.jrsoftware.org/isinfo.php Inno Setup] for Windows ** Application bundle "drag install" for !MacOS X * Drag and drop file loading - Config files, VEX files, and firmware * Follow [http://developer.apple.com/documentation/MacOSX/Conceptual/AppleSWDesign/index.html#//apple_ref/doc/uid/TP40001084 Apple Design Guidelines] as much as possible * Use the built-in QT 4.1 [http://doc.trolltech.com/4.1/qtestlib-manual.html unit testing] framework. GUI Features: * Task selector main screen ** Offers comms configuration, shared across task windows ** Initial setup wizard ** Firmware update wizard ** Full featured configuration and tuning application * Wizards for new users performing common tasks with standard code * Special fullscreen in-car table tuning mode. ** Simplified keyboard use only * Multilingual Tuning Features: * VE table * lambda table * Ignition timing * Ignition dwell * Idle speed * Enrichments * Boost limit * Compensate idle settings when lower VE is adjusted Monitoring (and logging) features: * Mixture (WBO2) * Pulsewidth * RPM * Temperature * Ignition advance * Voltage * MAP * MAT * TPS * Knock Alarm features (audible and visual): * Injector pulsewidth alarm * Mixture alarm * EGT alarm * Temperature alarm * MAP alarm * RPM alarm * MAT alarm * Knock alarm Testing features. Either command-oriented (simpler), or EC36/EC18 pinout oriented (more user-friendly). * hardware tests (small menu-command entry should be available almost everywhere?): ** mdh.. ** mdn.. * Forced variables ** mdi.. (iac) ** mda.. (advance) ** mdp.. (pulsewidth) ** .. System requirements: * Pentium / G3 CPU ** Pentium II / G4 recommended * Windows 95 / Linux 2.4 kernel with X11 / !MacOS X ** Windows 98 lite / Linux 2.6 with !XiG Accelerated X / !MacOS X recommended * 800x600 16 bit display ** 1024x768 24 bit recommended * 64 MB RAM ** 128 MB or more recommended * RS232 serial or USB with serial adaptor ** RS232 recommended (cardbus or built-in) * System speaker (for audible alerts) ** Sound card recommended ---- '''Development''' MembersPage/RichardBarrington/QTune/UseCases --MembersPage/RichardBarrington/QTune/TestCases-- --MembersPage/RichardBarrington/QTune/DesignDiagrams-- --MembersPage/RichardBarrington/QTune/GuiForms-- '''Related Project''' !SetupWizard - see some new GUI shots at http://www.vems.hu/files/MembersPage/RichardBarrington/setupwizard/ What's missing or wrong with it so far? Almost ready to implement the file output stuff? ---- '''See also''' * OtherTuningSoftware/NintendoGameBoy can we make a common grounds with the Nintendo software? ** Maybe...? Perhaps we should say both Nintendo and !QTune should work with !CommonInfrastructure... * OtherTuningSoftware/CommonInfrastructure ... heavy cleanup is needed - before or at the same time as qtune architecture ** Absolutely. ---- Back to MembersPage/RichardBarrington
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.