3 Dec
2012
3 Dec
'12
10:07 p.m.
Hi,
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.
Pauline Martin
4 Dec
4 Dec
12:47 a.m.
New subject: [trinity-devel] Seeking to help in the development of Trinity
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
3:07 a.m.
New subject: [trinity-devel] Seeking to help in the development of Trinity
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(a)yahoo.com> 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(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
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
4:41 a.m.
New subject: [trinity-devel] Seeking to help in the development of Trinity
On Mon, Dec 3, 2012 at 7:47 PM, Darrell Anderson
<humanreadable(a)yahoo.com> 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
>
On Mon, Dec 3, 2012 at 10:07 PM, pauline martin <321eniluap(a)gmail.com> wrote:
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
I apologize for the top-posting of my last message (please forgive
me)
and hopefully it is fixed here. It was not intentional, just tired.
However I also had another idea for some art, I cold also do a 3Dish
image where 3 balls overlap with their overlapping colors changing due
to the overlap.
Pauline Martin
5:20 a.m.
New subject: [trinity-devel] Seeking to help in the development of Trinity
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?
Everything in GIT now runs on the tqtinterface layer. Other than new
ABI/API changes, there is no more related work to be performed.
Historically, we went through a rough time with the overall
conversion between 3.5.12 -> 3.5.13.1. Most if not all of those bugs
were found and most of the patches have been back ported to 3.5.13.1
too.
We still maintain Qt3, mostly as a base and reference, but the
preferred method of building packages is against TQt3. There will
always be a dependency on one or the other, but as development
continues, that dependency shifts more and more to TQt3. At least one
package builds only against TQt3 and no longer builds against Qt3:
tdebindings. There might be other packages, but I would not know
because I have been building against TQt3 since the GIT migration
almost a year ago.
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.
The penguin is symbolically linked to the Linux kernel and the gnu is
symbolically related to the gcc infrastructure. I think Trinity
should have its own symbolic imagery. :)
A triquetra type image sounds interesting, but where do you envision
these images to be used? Are you thinking project logos at this point
or other art work for packages?
I apologize for the top-posting of my last message (please forgive me)
and hopefully it is fixed here. It was not intentional, just tired.
However I also had another idea for some art, I cold also do a 3Dish
image where 3 balls overlap with their overlapping colors changing due
to the overlap.
Personally I don't care whether people top post or bottom post. I see
both styles in my emails outside this list and I use whatever the
other person uses. I have enough intelligence and patience to read
either. So does everybody else here, but old customs die hard. :)
Darrell
12:36 p.m.
New subject: [trinity-devel] Seeking to help in the development of Trinity
On Tue, Dec 4, 2012 at 12:20 AM, Darrell Anderson <darrella(a)hushmail.com> wrote:
I was thinking of making the triquetra-type image (overlapping balls
whatever) in place of the T in the gear (originally a K from KDE). As
that is one location that needs to be obviously be rebranded if we are
to trully become our own entity away from kde. Other imagery would of
course need to go as well and I will work on creating a list of other
apps and stuff that I think might be good to change their art for.
Suck as Chalk, and in sme cases it might be good to know what the
image for for the DE is before creating an entire set of icons and art
that would go with it. I do need to however, either find a list of
art that needs to go or to create one. Otherwise, it would almost be
like chasing a bouncing ball in the dark.
Pauline Martin
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?
Everything in GIT now runs on the tqtinterface layer. Other than new ABI/API
changes, there is no more related work to be performed. Historically, we
went through a rough time with the overall conversion between 3.5.12 ->
3.5.13.1. Most if not all of those bugs were found and most of the patches
have been back ported to 3.5.13.1 too.
We still maintain Qt3, mostly as a base and reference, but the preferred
method of building packages is against TQt3. There will always be a
dependency on one or the other, but as development continues, that
dependency shifts more and more to TQt3. At least one package builds only
against TQt3 and no longer builds against Qt3: tdebindings. There might be
other packages, but I would not know because I have been building against
TQt3 since the GIT migration almost a year ago.
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.
The penguin is symbolically linked to the Linux kernel and the gnu is
symbolically related to the gcc infrastructure. I think Trinity should have
its own symbolic imagery. :)
A triquetra type image sounds interesting, but where do you envision these
images to be used? Are you thinking project logos at this point or other art
work for packages?
I apologize for the top-posting of my last message (please forgive me)
and hopefully it is fixed here. It was not intentional, just tired.
However I also had another idea for some art, I cold also do a 3Dish
image where 3 balls overlap with their overlapping colors changing due
to the overlap.
Personally I don't care whether people top post or bottom post. I see both
styles in my emails outside this list and I use whatever the other person
uses. I have enough intelligence and patience to read either. So does
everybody else here, but old customs die hard. :)
Darrell
3:10 p.m.
New subject: [trinity-devel] Seeking to help in the development of Trinity
On Tue, Dec 4, 2012 at 7:36 AM, pauline martin <321eniluap(a)gmail.com> wrote:
On Tue, Dec 4, 2012 at 12:20 AM, Darrell Anderson
<darrella(a)hushmail.com> wrote:
I was thinking of making the triquetra-type image (overlapping balls
whatever) in place of the T in the gear (originally a K from KDE). As
that is one location that needs to be obviously be rebranded if we are
to trully become our own entity away from kde. Other imagery would of
course need to go as well and I will work on creating a list of other
apps and stuff that I think might be good to change their art for.
Suck as Chalk, and in sme cases it might be good to know what the
image for for the DE is before creating an entire set of icons and art
that would go with it. I do need to however, either find a list of
art that needs to go or to create one. Otherwise, it would almost be
like chasing a bouncing ball in the dark.
Pauline Martin
Just did a search through the contents of tde-tdeartwork and found a
few more images that I thought might be worth changing. These are
(without the file type):
about_kde
go_old
go
kfs_kde (might want a totally new mascot character /thing) I can make
a mascot/character if so desired)
kmenu
krec
krita_kra
krita
However, I do realize that by changing a subset of icons and imagery I
would have to force myself to stay within their style and feel. Where
as a completely new set (yes more work) could be desired more. I also
realize that only some of the art that might be desired to be replaced
is within tde-tdeartwork.
Pauline Martin
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?
Everything in GIT now runs on the tqtinterface layer. Other than new ABI/API
changes, there is no more related work to be performed. Historically, we
went through a rough time with the overall conversion between 3.5.12 ->
3.5.13.1. Most if not all of those bugs were found and most of the patches
have been back ported to 3.5.13.1 too.
We still maintain Qt3, mostly as a base and reference, but the preferred
method of building packages is against TQt3. There will always be a
dependency on one or the other, but as development continues, that
dependency shifts more and more to TQt3. At least one package builds only
against TQt3 and no longer builds against Qt3: tdebindings. There might be
other packages, but I would not know because I have been building against
TQt3 since the GIT migration almost a year ago.
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.
The penguin is symbolically linked to the Linux kernel and the gnu is
symbolically related to the gcc infrastructure. I think Trinity should have
its own symbolic imagery. :)
A triquetra type image sounds interesting, but where do you envision these
images to be used? Are you thinking project logos at this point or other art
work for packages?
I apologize for the top-posting of my last message (please forgive me)
and hopefully it is fixed here. It was not intentional, just tired.
However I also had another idea for some art, I cold also do a 3Dish
image where 3 balls overlap with their overlapping colors changing due
to the overlap.
Personally I don't care whether people top post or bottom post. I see both
styles in my emails outside this list and I use whatever the other person
uses. I have enough intelligence and patience to read either. So does
everybody else here, but old customs die hard. :)
Darrell
4401
days inactive
4402
days old
6 comments
3 participants
participants (3)
-
Darrell Anderson -
Darrell Anderson -
pauline martin