tde-devels November 2011

devels@trinitydesktop.org

44 participants
150 discussions

by Darrell Anderson

At our web site page for joining mailing lists, we have a section titled "Mailing List Etiquette." Should we expand that section with a short policy statement about expected attitudes? I don't want to discourage healthy debates and discussions, which always will include a wide range of opinions, but if we post a policy we establish nominal knowable boundaries and basic CYA. Perhaps in list messages we could add a reminder sentence in the footer with something to the effect about thinking positively and not to attack the goals of other projects? Just thinking out loud with respect to our recent "damage control" discussion... Darrell

13 years, 3 months

IRC Client

by Darrell Anderson

Not directly related to development but almost. :) Quite a few IRC clients available with Trinity. Recommendations? Darrell

13 years, 3 months

[qt3] Qt3 licenses and configure

by Laurent Dard

I think that in Qt, the irritating question about licenses, that appears when executing 'configure', must be removed. So I suggest to change it. I saw that other things should be modified as well: README* INSTALL FAQ... And a lot of references to trolltech should be converted into references to Trinity: qt-bugs(a)trolltech.com --> http://bugs.pearsoncomputing.net/ etc. I need a clarification about licenses. According to /usr/share/doc/libqt3-mt/copyright (Trinity version): "Qt 3.3 is triple licensed under the QPL, GPL 2 and GPL 3." But Trinity web site says: "any Qt3 version released by this project is licensed under the GPL only" http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13 Does it means there is a bug with 'THE Q PUBLIC LICENSE' which should be removed? And about modules, may the lines (225-227) MODULES="styles tools kernel widgets dialogs iconview workspace inputmethod" [ "$PLATFORM_QWS" = "yes" ] && [ "$Products" = "qt-professional" ] && MODULES="$MODULES network" [ "$Products" != "qt-professional" ] && MODULES="$MODULES network canvas table xml opengl sql" be replaced by MODULES="styles tools kernel widgets dialogs iconview workspace \ inputmethod network canvas table xml opengl sql" without breaking things? A third question: will Trinity Qt support Mac and QWS? I reported a bug: http://bugs.pearsoncomputing.net/show_bug.cgi?id=628 with a patch for the 'configure' file, to be reviewed: http://bugs.pearsoncomputing.net/attachment.cgi?id=128 * Free edition GPL 2 & 3 only (no QPL) * Interactive part about licenses removed * Defined modules: "styles tools kernel widgets dialogs iconview workspace inputmethod network canvas table xml opengl sql" -- Laurent Dard

13 years, 3 months

TDE Environment Variables

by Darrell Anderson

I was browsing the patches list and noticed some patches a while ago that said "Use TDE_FULL_SESSION instead of KDE_FULL_SESSION." What environment variables are now changed from KDE? Is that the only one or have others? Which KDE environment variables remain the same in TDE? Darrell

13 years, 3 months

Web Site Audit

by Darrell Anderson

I was asked to audit the Trinity web site and provide suggestions to list members. My comments are nothing formal or official and I don't have the last word. I also am not the webmaster. Hopefully my observations help improve the web site and hence, perception of the Trinity community. Everything I offer here is intended to be constructive! I like gray and light colored backgrounds. Great for readability. Dark backgrounds are challenging for many people to read. Gray is a good neutral color. In color schemes gray also represents dignity. =================================================== Consolidate navigation links. * Provide only one top level nav bar. Currently there are two and the smaller one is easy not to notice. * Rename the "Support" link to "Contact and Support." * Remove the "Screenshots" link from the nav bar (Will move the link to the main page body.). * Create a new link named "Get Trinity." * Move the "Development" link to the main nav bar. * Rename the "Development" link to "Developers." * Move the "News" link to the main nav bar. * Move the "Wiki" link to the main nav bar. * Combine the "Installation" and "Release Downloads" pages into "Get Trinity." * Move the "Contributors" page text to the "About" page. Refer to the etherpad draft, bottom. * Move the "Donate" link link to the "Contacts and Support" page. * Move the "Bugs" link to the "Contacts and Support" page. * Move the "Mailing Lists" link and page to the "Contacts and Support" page. * Move the "Documentation" link to the "Developers" page. * Move the "RFEs" link to the "Developers" page. * Move the "GIT" link to the "Developers" page. * Move the "Nightly Builds" and "Patches" links to the "Developers" page. * Move the "Related Projects" link to the "Developers" page. * Delete the "Community Content" link. (Part of the wiki.) =================================================== Top Level Nav Bar, all pages: Home About Get Trinity News Contact and Support Developers Wiki Make the link text larger. Consider repeating the top level nav bar at the bottom of every page. Visitors dislike scrolling back to the top of a page. Layout of the bottom nav bar can be different. =================================================== Some Page Cleanup: * Center the top level nav bar. * Use left-justified margins for text but center the layout on each page with wide outside margins. * On the main page, top of page, add an introduction/welcome statement. * On the main page, leave the most recent News item from the News page as is, after the intro statement. * On the main page, move the "Help Wanted!" ad to the "Developers" page. * On the main page, move the "Official Trinity Binaries" section to the "Get Trinity" page. * Main page should include new links, off to either side: "Get Trinity" (Yes, duplicates the "Get Trinity" link.). "Release Notes" (Same link as current.). "Screenshots" (Link removed from main nav bar and restored here.). * A new About page with FAQ is available for review in etherpad. * Need a few more screenshots. * The screenshot thumbnails should be a tad larger. * Screenshots should highlight good features of Trinity, not be casual screenshots. * Use links in the thumbnails to allow people to view a full screen size of the picture. * Use the new logo when approved by the team. * Refrain from using small or tiny text on any page. Leave fonts at default size. Let users adjust font sizes. =================================================== New page: * In the "Get Trinity" page, add a link to an Applications page providing descriptions of all apps in the repository. * New Applications page: divide the new page into sections based on the T-Menu. For the new Applications page, we can grab content from the old KDE 3 web site, but other apps in the repository will need to be written new. Descriptions need not be long and exhaustive. A paragraph or two and one or two screen shots will be adequate. We need this page very much. I agree to help. =================================================== At this point pages will need to be reviewed after rearranging. Perhaps a mockup site should be used until ready. I agree to help review mockups and changes. Considering the public attention Trinity has been receiving of late, I hope we move quickly to revamp the web site. I hope this helps! Darrell

13 years, 3 months

Slackware 13.1 Binary Packages

by Darrell Anderson

My packages for Slackware 13.1 are ready --- except for one major bug: KDM. I can't login using the Trinity KDM. At least one other Slackware/Trinity user has confirmed this behavior. I am uncomfortable uploading packages when I know KDM is broken. Yes, Slackware users can use the KDE 4 KDM, which is part of the stock Slackware, but that is...icky. :( I know everybody is busy but if I can get help with a patch then I would feel much better. If the patch succeeds then I'll submit the bug report to ensure SVN/GIT gets updated. I'm fairly certain the problem is authentication. When I login all I see is a "Login failed" message. Slackware does not use PAM. Slackware supports PolicyKit but using that layer is not required by users. Indeed, the KDE 4 KDM, which is part of the stock Slackware, is not built or dependent upon PolicyKit. I can login with the KDE 4 KDM just fine. As a note, I built KDE 3.5.10 for Slackware 13.1 and KDM there works fine. I built kdebase 3.5.13 with the WITH_PAM=OFF option. No change. Allowing root logins through KDM fails too, so the problem is unlikely to be file permissions. I also have tried enabling and disabling SAK. No change. Thanks! Darrell

13 years, 3 months

Last Reminder: Trinity Developer Meeting TODAY at 12PM EST

by Calvin Morrison

Hey all! one last reminder for the meeting, Which will take place at 12PM EST (approximately 45 minutes away) in #trinity-desktop-meeting @ irc.freenode.net Calvin Morrison

13 years, 3 months

Trinity Developer Meeting, 11/15/11

by Calvin Morrison

Hello all! We will be having a meeting on Tuesday 11/15/11 at 12pm (noon) EST. At this meeting we be discussing and laying out ideas and plans for the next release and making important decisions regarding the future of the project. Please refer to my original post for more information http://trinity-devel.pearsoncomputing.net/?0::3280. Please let me know if you cannot attend Calvin Morrison Trinity Desktop Team

13 years, 3 months

Error Message When Opening Panels Control Center

by Darrell Anderson

In 3.5.13, when I select Desktop/Panels in the Control Center or from the T-Menu, I receive the following error message: ================================================ Error - KDE Control Module ================================================ Error loading theme image file. /opt/trinity/apps/kicker/wallpapers/default.png /opt/trinity/apps/kicker/wallpapers/default.png OK ================================================ The message box title bar needs some branding attention. :) I have an /opt/trinity/share/apps/kicker/wallpapers/default.png. Is this error message a build error? I notice in the cmake files I might need to specify DATA_INSTALL_DIR (kde_datadir in autotools). If yes, then is that location $PREFIX/share? Or is this an error in the panel configuration sources? Thanks. Darrell

13 years, 3 months

patch fails with qt 3.3.8d

by Robert Xu

Hi all, Usually I get the already applied message for patches, however I seem to have something different now: This patch fails completely. Can anyone make heads or tails out of it, or should this patch be significant enough to keep or throw away? Patch #28 (fix-key-release-event-with-imm.diff): --- src/kernel/qapplication_x11.cpp +++ src/kernel/qapplication_x11.cpp @@ -3294,11 +3294,7 @@ // filtering opportunity first to ensure all input methods work // properly regardless of application design. -#ifndef QT_NO_IM_EXTENSIONS if( keywidget && keywidget->isEnabled() && keywidget->isInputMethodEnabled() ) { -#else - if( keywidget && keywidget->isEnabled() ) { -#endif if( ( event->type==XKeyPress || event->type==XKeyRelease ) && sm_blockUserInput ) // block user interaction during session management return TRUE; @@ -5220,11 +5216,12 @@ } else { key = (int)(long)keyDict->find( keycode ); if ( key ) - if( !willRepeat ) // Take out key of dictionary only if this call. + if( !willRepeat && statefulTranslation ) // Take out key of dictionary only if this call. keyDict->take( keycode ); long s = (long)textDict->find( keycode ); if ( s ) { - textDict->take( keycode ); + if( statefulTranslation ) + textDict->take( keycode ); ascii = (char)(s-256); } } --- src/kernel/qwidget_x11.cpp +++ src/kernel/qwidget_x11.cpp @@ -2699,11 +2699,10 @@ { QInputContext *qic = 0; -#if !defined(QT_NO_IM_EXTENSIONS) if ( isInputMethodEnabled() ) { +#if !defined(QT_NO_IM_EXTENSIONS) qic = icHolderWidget()->ic; #else - { // icHolderWidget is always topLevelWidget QTLWExtra *topdata = icHolderWidget()->topData(); qic = (QInputContext *)topdata->xic; @@ -2754,10 +2753,8 @@ */ void QWidget::createInputContext() { -#if !defined(QT_NO_IM_EXTENSIONS) if( !isInputMethodEnabled() || QApplication::closingDown() ) return; -#endif QWidget *icWidget = icHolderWidget(); #ifndef QT_NO_IM -- later daze. :: Robert Xu :: rxu.lincomlinux.org :: protocol.by/rxu

13 years, 3 months

← Newer
1
...
5
6
7
8
9
10
11
...
15
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels November 2011