tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

Start a nNew thread

Re: [trinity-devel] tdesvn svgz branding cleanup
by Darrell Anderson 12 Jan '14

12 Jan '14

>Looks great here! All affected files updated in git commit b4e10193. :) Darrell

1 0

tdesvn svgz branding cleanup
by Darrell Anderson 12 Jan '14

12 Jan '14

All, Would one of you graphics experts please update the tdesvn svgz icon? In the git sources: applications/tdesvn/src/icons/hisc-app-tdesvn.svgz The text string in the image should be updated to T D E S V N. All of the respective png files in that same directory are created from that svgz. Thanks! Darrell

4 3

Re: [trinity-devel] tdesvn svgz branding cleanup
by Darrell Anderson 12 Jan '14

12 Jan '14

>Ugh, it probably saved as "Compressed Inkscape SVG" rather >than "Compressed Plain SVG". The attached version should fix >that. >I rendered the PNG anyway, though (150 x 127, because it just >would >not give me that extra pixel). Thank you! Darrell

1 0

Re: [trinity-devel] tdesvn svgz branding cleanup
by Darrell Anderson 12 Jan '14

12 Jan '14

>This good? Looks great. Thank you! I am unable to convert your svgz to png using gwenview. I've used gwenview in the past to convert, but this time the resulting png is NOT the same as the original svgz. Would you please create a 150x128 png from the svgz? Thanks much. Darrell

2 1

Re: [trinity-devel] kscope FTBFS
by Darrell Anderson 12 Jan '14

12 Jan '14

>> Hello, there was too much KDE/TDE renaming in kscope, causing FTBFS at >> this time. >> >> The "KDE_IS_VERSION" macro is defined in "admin/acinclude.m4.in" >Fixed in GIT hash 7d55c452. >Thank you for your heads up. Sorry about that! I checked the full source tree. Looks like that was the only inadvertent KDE_IS_VERSION->TDE_IS_VERSION conversion. Darrell

2 1

Commit web page is not updating
by Darrell Anderson 12 Jan '14

12 Jan '14

The last update was Jan 8. Darrell

1 0

kscope FTBFS
by François Andriot 12 Jan '14

12 Jan '14

Hello, there was too much KDE/TDE renaming in kscope, causing FTBFS at this time. Here it is: http://git.trinitydesktop.org/cgit/kscope/commit/src/editorpage.cpp?id=974a… The "KDE_IS_VERSION" macro is defined in "admin/acinclude.m4.in" . François

2 1

Re: [trinity-devel] Slavek: Digikam and Showfoto help handbook files are available
by Darrell Anderson 11 Jan '14

11 Jan '14

>And what if we incorporate documentation for all languages into >an existing >git repository digikam and generate documentation could be done as >build >options? For example --with-doc and --with-doc-i18n or --without- >doc and --without-doc-i18n. That could be palatable. On reflection, I notice there are some apps that automatically include i18n docs when building the package. For example, amarok and kipi-plugins. Pushing the digikam docs into the existing digikam sources would be no different. If we add configuration options, the default should be --with- doc=true and --with-doc-i18n=false. Using --with-doc=true as a default ensures at least the English handbook is built with the standard package, just like most Trinity apps. Yet explicitly adding the --with-doc option allows for not building the docs. For example when people prefer building minimal footprint packages. If we add those configuration options then we should do likewise for all affected apps like amarok and kipi-plugins. So how about this: I push the digikam docs into the existing digikam sources. Right now that means all i18n docs are compiled when compiling digikam. No different than amarok and kipi-plugins. I open a bug report to add --with-doc and --with-doc-i18n configuration options to all Trinity apps, and equivalent cmake options. Darrell

1 0

Re: [trinity-devel] Slavek: Digikam and Showfoto help handbook files are available
by Darrell Anderson 11 Jan '14

11 Jan '14

>I acknowledge the history of the digikam help handbooks, but I'm >uncomfortable with that approach for Trinity. > >Let's split the English component only and merge that directly >into >the existing Digikam sources. That is how all other apps are >designed. I have already tested that. > >The remaining languages can move to a new module, >applications/digikam-doc-i18n. > >Most users who do not speak i18n languages don't want to install >all of those components just to obtain access to the >digikam/showfoto handbooks. Further, as is common with all other >Trinity apps, there should be a default handbook installed with >the package. :) I have this all tested. I have a single patch to push for the existing Digikam, which will build the English handbooks for Digikam and Showfoto. I have the proposed digikam-doc-i18n contents tested so only the i18n handbooks are built and installed. My digikam-doc-i18n files also include copies of the master admin and cmake files. All I need now is for somebody to create a new module in the main repository named digikam-doc-i18n. With the new upstream module I can push the whole directory and we'll be done. I would create the new module myself but I don't know whether I have permissions to do that and I also don't know all that is involved. Digikam and Showfoto handbooks standing by! Darrell

2 1

Re: [trinity-devel] Slavek: Digikam and Showfoto help handbook files are available
by Darrell Anderson 10 Jan '14

10 Jan '14

>Because the original package was purely a standalone package with >all >documentation, I suggest to keep it as well as a git module >applications/digikam-doc - all languages, including English. I acknowledge the history of the digikam help handbooks, but I'm uncomfortable with that approach for Trinity. Let's split the English component only and merge that directly into the existing Digikam sources. That is how all other apps are designed. I have already tested that. The remaining languages can move to a new module, applications/digikam-doc-i18n. Most users who do not speak i18n languages don't want to install all of those components just to obtain access to the digikam/showfoto handbooks. Further, as is common with all other Trinity apps, there should be a default handbook installed with the package. :) Darrell

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels