I did not mean to imply porting from qt3 to qt4 precisely, I meant to the tqt framework. At least what I read made it sound like once the porting to the tqt framework was completely done that it there would no longer be a need for qt3 as a dependency. Was I wrong? An idea for art: 1. A triquetra-type image of either penguins or overlapping circles or something (ideas welcome) 2. We could replace the shutdown, standby, and power buttons with images of a penguin's ace with eyes open, half-closed and sleeping. I could do these in 3D or in 2D. Pauline Martin On Mon, Dec 3, 2012 at 7:47 PM, Darrell Anderson <humanreadable@...> wrote: >> I would like to contribute in any way that I can. I have some experience >> with graphics creation 2D and 3D, also I do program a llittle and would >> like to know how the progress to porting programs to Qt4. I would like to >> help in porting applications for the next version of TDE. > > Hi Pauline and welcome, > > Much of the image work done thus far has been in the nature of updating files for rebranding, which is the process of establishing a Trinity identity rather than KDE. Much of that work is changing things like "K" to "T." With that said, there have been past discussions about creating new art work. You might want to search the developer list archives for those discussions: > > http://trinity-devel.pearsoncomputing.net/ > > Probably a sane approach is to propose new art work before creating anything. Mostly to save you time. :) > > Most of the Trinity programming is C++. If you have experience with C++ or feel confident enough with other programming languages and just want to jump in, the bug tracker is the best place to start. The bug tracker includes enhancement requests. Find some bug reports or enhancement requests that look palatable to you and then start hacking. > > http://bugs.trinitydesktop.org/ > > You should have a local build environment if you want to help with code, in order to test your patches before posting as an attachment in the bug tracker. > > The general approach is to create a local copy of the GIT repository and then copy or create build scripts to support building packages. Debian, Ubuntu, OpenSuse, Fedora, Arch, and Slackware are represented here. Therefore finding build scripts is a matter of asking. The GIT repository is > 4GB therefore even with a broadband connection expect the process of creating a local repository to take a few hours. > > The wiki contains information about building packages: > > http://www.trinitydesktop.org/wiki/bin/view/Developers/WebHome > > Please ask questions. A new perspective will help us improve the wiki. :) > > We don't port anything to Qt4. We use an interface layer that allows certain apps to use some Qt4 code but we don't port directly to Qt4. We now maintain the Qt3 software collection and we have modified those sources many times to support Trinity. > > The next official release is scheduled for spring and will be version R14.0.0. The new version scheme is intentional to break from KDE and to better establish a Trinity identity. The current stable version is 3.5.13.1. Slavek Banko is the lead for all things 3.5.13.x. There are plans for a 3.5.13.2 release. You can download 3.5.13.1 packages by following the links at the home page of the Trinity web site. > > There are no official GIT development branch packages available. All of us build our own GIT packages. Some folks provide GIT packages but you'll have to ask around for where those packages might be and whether they are available for your distro. > > I hope that helps. :) > > Darrell > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: trinity-devel-unsubscribe@... > For additional commands, e-mail: trinity-devel-help@... > Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting >