Release Notes For 3.5.12
New or Improved from 3.5.11
This section highlights some of the most useful improvements to the Trinity system.
KDE3 development has been handed off to the Trinity project, and all of the Trinity code is now in a KDE SVN branch, from which packages are built on a regular basis. Many bugs have been fixed and new features have been added; a partial list follows.
Back End Improvements
- 3.5.12 development starts at SVN revision r1154613
- Added the TQt interface (lays groundwork for eventual Qt4 compatibility)
- Compiles on Slackware 12.2
- Added caldav and carddav support to Kontact
- Applicable OpenSUSE patches imported
- Applicable Chakra project patches imported
- Applicable Slackware patches imported
- Fully XDG compliant; desktop files in ~/.config/autostart with [Hidden] directive honored
- System detects and compiles with newer libraries
- Utempter found in correct location
- API documentation updated and available online at the Trinity project website
- kdebindings patched to work with upstream sip, pyqt3, and pykde3 packages
- Repaired stdout/stderr messages to improve readability in xsession-error log
- Removed superfluous stdout/stderr messages from xsession-error log
- startkde script updated, more robust, and not distro-dependent
- Many bug fixes and crash fixes, too numerous to list individually
- Trinity rebranding
- Greater stability, more features
- Recurring meetings follow applicable standards including RECURRENCE-ID support
- KAddressbook resource configuration enhanced
- Timezones handled properly
- Drifting appointments repaired
- Full Zimbra integration support
- KMail system tray works properly when launched from Kontact
- Import of KMail fixes from Enterprise branch
- Kopete supports newer Yahoo IM protocol
- Hide Menu Bar feature restored Add screen shot?
- Wikipedia loading repaired
- Ark supports XZ/LZMA compression
- Optional K-Menu search field for application name or description Add screen shot?
- Kickoff menu added as a K-Menu option Add screen shot?
- Added ability to configure launch feedback on both panel and desktop Add screen shot?
- XDG Documents folder is optionally created when not yet existing Add screen shot?
- Russian translations for Yakuake available
- No Busy Cursor launch feedback is the default (no more bouncing mouse cursor!) Add screen shot?
- Double-click to open files and folders is the default Add screen shot?
- Added options to enable/disable desktop and panel icon activation effects
- KDM themer supports user configurable backgrounds
- KDM uses a new, clean, semi-transparent theme by default
- Added six new user-configurable icons to Desktop for convenience in accessing common tasks and areas of the system
- Desktop icons no longer wander on logout/login
- Desktop icon grid is automatically applied on login when in use
- Old style selected icon text is available as an option
- GTK applications, such as Firefox and the GIMP, use Trinity file open/save dialogs when kgtk-qt3 is installed
- GTK applications, such as Firefox and the GIMP, use Trinity look and feel when gtk-qt-engine is installed
- Additional art work and wallpapers
- Fixed warning messages in Control Center Wireless module
- Crystal SVG is the default icon set
Trinity can be installed alongside KDE4.x with no problems. Trinity automatically detects and adjusts for KDE4.x programs, so that users can easily run KDE4 applications from within the Trinity environment.
Assisting the Project
If you are interested in helping out, please contact:
A Bluetooth developer who could re-activate Trinity's Bluetooth functions would be greatly appreciated!
None at the moment.
There is a mailing list for Trinity users available here: http://trinity.pearsoncomputing.net/mailing_lists This is a great place for users to share tips and tricks, and you can also sign up to receive announcements related to Trinity.
We want to hear what you think about the current release of Trinity. We want to know if it Rocks, if it is just OK, or if it is flat out wrong. No matter the feedback, as long as it is in line with the FOSS Code of Conduct, we would like to hear it.
So what are you waiting for? Head on over to the Feedback Page and let us know!