|  | | Re: Re: Nonononono
Mar 6 2009 on content 2ManDVD |
Yes, I switched to Qt 4.5. I don't know if they really are. But if they are, it must be because of significant changes in the QObject class (you can read more in the Qt4.5 Documentation online. I din't have a deep look at the changelog yet.
PS
Do you use a text editor or an IDE like QtCreator? If you use an editor, you could download and install the QtSDK installer (it contains a precompiled Qt4.5) and debug step by step your application and find out what is going on in fact. |
| | | Add media crash
Mar 5 2009 on content 2ManDVD |
Hi. You forgot to initialise the hdlparp/b] pointer in the [b]media class and therefore 2ManDVD crashes when importing media.
PS
You should initialise class' members like this:
AClass::AClass(QWidget *parent):
QWidget(parent),
m_aClassMember(this)
{
// constructor operations here
}
not:
AClass::AClass(QWidget *parent):
QWidget(parent)
{
m_aClassMember = ClassMember(this);
// constructor operations
}
- because the first way is faster - it initialises the members with given values. In the second way, objects are first created (initialised with default values) and then (in the constructor body) new objects are created and then assigned to the members (by copy methods).
PS
Here is a link to the updated Polish translation: http://rapidshare.com/files/205735721/pl_translation.zip.html |
| | | Re: Can't be compiled over here
Mar 2 2009 on content 2ManDVD |
Simply run make distclean, then again qmake and make. |
| | | A mess in the main directory.
Mar 2 2009 on content 2ManDVD |
Hi!
Currently, there is a big mess in the main directory. I mean all object, moc and other qt-specific files are generated in this directory. You can add such lines to the .pro file to make files be generated in a separate directory:
MOC_DIR = build
OBJECTS_DIR = build
UI_HEADERS_DIR = build
UI_SOURCES_DIR = build
RCC_DIR = build
Moreover, you can do checking for the Bibliotheque directory on startup, whether it is in the app path or in app_path/../share/2ManDVD/Bibliotheque. Then you could add install instructions to the .pro file, so application could be installed and run from /usr/bin:
target.path = /usr/bin
BIBLIOTHEQUE_DIR.files = Bibliotheque
BIBLIOTHEQUE_DIR.path = /usr/share/2ManDVD
INSTALLS += target BIBLIOTHEQUE_DIR
You can do the same with the translations (to be looked up in /usr/share/2ManDVD/translations and loaded from there).
Cheers, Adrian. |
| | | Re: Re: Re: Translations
Mar 2 2009 on content 2ManDVD |
Thanks. Besides, I recommend you to load also Qt translations (Qt dialog windows will then also be translated), by using code like this:
QString qtLocale = "qt_" + QLocale::system().name();
QTranslator qtTranslator(this);
if (qtTranslator.load(qtLocale, QLibraryInfo::location(QLibraryInfo::TranslationsPath)))
{
qApp->installTranslator(&qtTranslator);
}
else
{
qDebug() << "Failed to load Qt4 language file:"
<< QLibraryInfo::location(QLibraryInfo::TranslationsPath) + "/" + qtLocale;
} |
| | | Re: Translations
Feb 28 2009 on content 2ManDVD |
Oops, I made a typo. Here is a link to the corrected translations: http://rapidshare.com/files/203777692/2mandvd_translations.zip.html |
| | | Translations
Feb 28 2009 on content 2ManDVD |
Hi!
Yeah, it's me again ;) I've just translated 2ManDVD to Polish and corrected the English one. I hope I didn't waste my time and you will add the translations.
Zipped translations: http://rapidshare.com/files/203768487/2mandvd_translations.zip.html |
| | | Re to the previous comments
Feb 16 2009 on content 2ManDVD |
Hi. No one blames on you but Elv13 is right. I mean that if you want other people to help in the development, it would be *much* easier for them if the code is in English. And an SVN repository (for example on sourceforge.net) would also be needed. From your statement I understood that you are the only developer and you *want to be*. If it is so, then ok, write your code as you want.
PS
Writing strings in English doesn't mean you can't translate your app into French. Many developers do so (as for example me) - write the strings in English and provide a dranslation by themselves.
My English was much worse until I started writing C++ code reading the Qt4 documentation and writing strings in English. I'm a proud Polish but this doesn't bother me in using English in such areas as C++ application, so don't be angry withe me for my comment ;) |
| | | Re: Re: Re: Re: ubuntu only support
Sep 8 2008 on content UbuDSL |
Quote:i red that on your anwer to madsheytan, if i'm wrong i'm sorry...
That's why I wrote that it was, but not is (look at the date of the comment you were suggested by - since that comment UbuDSL has been rewritten).
Quote:that confirm that you support ubuntu only, let me try to explain why 64bit list should be on /usr/lib64 and not in /usr/lib
It's not my fault that 64-bit Ubuntu version has native libraries in /usr/lib (32-bit libraries on a 64-bit version of Ubuntu are placed in the /usr/lib32 directory). You can easily install the UbuDSL library in the /usr/lib64 directory, by adding argument 'CONFIG+=lib64' while invoking the configure script. For example for openSUSE packages building the script command looks exactly like that:
./configure "CONFIG+=amd64\ lib64\ SoundModule"
But yes, it is my fault that I haven't written about it in the README file. I'll add note about this.
Quote:consider that like constructives critics
That's what I do. I just simply reply to your comments. I don't blame you about anything.
Finally, according to the attached libraries. The only application using the atm library is br2684ctl and only for this command the LD_LIBRARY_PATH macro is set to point this library. So, the only problem that would happen (in my view) is a trouble with invoking the br2684ctl command (if I'm wrong, correct me). |
| | | Re: Re: ubuntu only support
Sep 8 2008 on content UbuDSL |
Quote:ubuntu is one the thousands linux distro.. what make it so special to make you able to support only ubuntu?
Tell me where is written that Ubuntu is the only one supported distribution? It was, but, the project grew up and now more distros are suppoted.
Quote:does ubudsl search for a particular configuration file or what?
UbuDSL depends on the package manager. Currently supported are apt and zypper, so the distros that UbuDSL should work on are Debian, Ubuntu (and Ubuntu based), PCLinuxOS, openSUSE.
Quote:on 64 bit is /usr/lib64
Not in Ubuntu. On Ubuntu, system architecture libs are placed in /usr/lib.
Quote:you should not provide precompiled binaries and libs because they are linked with ones available on the system, thay may break program because for example
the lib wants hello.so but i may have hello1.so
The application was originally created for Ubuntu and, as you know, Ubuntu is contained on only one CD. And if only there were placed also the packages with needed software, the mentioned binaries wouldn't be attached to UbuDSL. Moreover, attached br2684ctl binaries are depended only on the atm library which is also attached (this lib does'nt require anything else than what the system provides). |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
| |
|
