trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] common/admin - TQTDCOPIDLNG is not set

From: Slávek Banko <slavek.banko@...>
Date: Mon, 17 Feb 2014 22:43:18 +0100
On Monday 17 of February 2014 21:39:40 Darrell Anderson wrote:
> >Please, can you assess whether any of these unintended renaming
> >should be
> >added to the script convert_existing_qt3_app_to_tqt3? The script
> >is still
> >actively used for convert KDE3 applications to Trinity and for
> >preparing
> >updates for existing applications.
>
> I am not intimate with the conversion scripts. If I understand
> correctly the following additions will help.
>
> CAM_RETQ_/CAM_REQ_
>
> CHARFRETQ_/CHARFREQ_
>
> CHISTQ_DOF/CHISQ_DOF
>
> CPUFRETQ/CPUFREQ
>
> ETQBACK/EQBACK
>
> ETQ_CHANNELS/EQ_CHANNELS
>
> ETQ_MAX/EQ_MAX
>
> ETQ_NOT/EQ_NOT
>
> ETQ_SET/EQ_SET
>
> ETQVIEW/EQVIEW
>
> ETQUALIZER/EQUALIZER
>
> ETQGAINS/EQGAINS
>
> ETQDATA/EQDATA
>
> FRETQUENCY/FREQUENCY
>
> GETETQDATA/GETEQDATA
>
> HTQ_VIDEOCD/HQ_VIDEOCD
>
> INCRRTQ_WAIT/INCRRQ_WAIT
>
> IRTQ/IRQ
>
> IRTQ_/IRQ_
>
> KONTQ/KONQ
>
> KONTQ_/KONQ_
>
> KONTQSBC/KONQSBC
>
> KONTQFEED/KONQFEED
>
> KONTQFILE/KONQFILE
>
> KONTQSIDEBAR/KONQSIDEBAR
>
> KWTQ_/KWQ_
>
> MPEG_SETQ/MPEG_SEQ
>
> PTQ_/PQ_
>
> RETQSEN/REQSEN
>
> RETQBUF/REQBUF
>
> RETQ_/REQ_
>
> RETQIMG/REQIMG
>
> RTQ_IFS/RQ_IFS
>
> RTQ_SIZE/RQ_SIZE
>
> SAMPLE_FRETQ_/SAMPLE_FREQ_
>
> SETQNO/SEQNO
>
> SETQNO_/SEQNO_
>
> SETQ_NO/SEQ_NO
>
> SETQ_MASK/SEQ_MASK
>
> SETQACCESSMGR/SEQACCESSMGR
>
> SETQLINEWIDGET/SETLINEWIDGET
>
> SETQMAN/SEQMAN
>
> SND_SETQ_EVENT/SND_SEQ_EVENT
>
> SUBTQ_/SUBQ_
>
> KTQ_CLASSNAME/KQ_CLASSNAME
>
> TDETQ_CLASSNAME/TDEQ_CLASSNAME
>
> TQUIET/QUIET
>
> etqdialog/eqdialog
>
> Litquids/Liquids
>
> RetqCount/ReqCount
>
> retquis/requis (French)
>
> Retquisiti/Requisiti (Italian)
>
> setqCount/setCount
>
> "setq "/"set "
>
> stquid/squid
>
> Stquiggle/Squiggle
> stquiggle/squiggle
> stquiggly/squiggly
>
> tquerytable/querytable
>
> Kontqui/Konqui
> kontqui/konqui
>
>
> Of course, none of these unintended renames affected compiling
> because the compiler does not "read" variable names the same way as
> humans. to compilers, variables are only "tokens." As long as the
> unintended renames are 100% consistent the program compiles just
> fine. Fixing the unintended renames is important to us humans only,
> to improve readability and establish a degree of professionalism.
>
> Darrell
>

Thank you, exactly what I needed.

Slavek
--