Re: Respository vandalism by r...@...fd.o
Luc, I completely agree with you. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [Qt-creator] Cpp parser documentation
Thanks for the tips. Over the weekend I had a look at the source code of the cpp parser and the tests for it (which helped me a lot). I have it all working pretty well at the moment. I still need to look into preprocessing files. And it's a bit of work to make it all available in QtScript files ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Install support files together with plugin
On Mon, Oct 18, 2010 at 9:31 AM, Eike Ziller eike.zil...@nokia.com wrote: But, if you consider to provide your plugin cross-platform, you should notice that resources are at a different place on Mac builds. You should definitely use $$IDE_DATA_PATH/myplugin/scripts and in you plugin sources Core::ICore::instance()-resourcePath() + QLatin1String(/myplugin/scripts) Thanks for the tip. INSTALLS creates an additional make target make install. If you don't call make install the files will not be copied. If you want to actually copy files during the make step, you'll unfortunately need to do some fancy stuff, similar to share/qtcreator/static.pro /me wonders if we couldn't provide most of the stuff for this task as functions in qtcreator.pri ? I was, and still am, confused by how the plugin gets build and installed. When I build the plugin from within Qt Creator, it gets installed automatically, I never have to use make install. Running make install from the build dir works, but results in an error. It wants to create a directory called /lib/qtcreator. Thanks for the reply. I have an answer to my question. Just run make install in the build dir regardless of building the plugin in Qt Creator. ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] Install support files together with plugin
Hello, I'm creating a plugin that needs to install a couple of script files. In doing so I encountered a problem. First a question. Is it allowed to install these support files in share/qtcreator/myplugin/ ? Or is there some etiquette that says not to do that? In trying to install these files, I modified the .pro file of the plugin like so: Note: ... replaces several other lines. 1. ... 2. 3. OTHER_FILES = ... \ 4.tests/testscript.qs 5. 6. ... 7. 8. testscriptfiles.files += tests/testscript.qs 9. testscriptfiles.path = $$IDE_BUILD_TREE/share/qtcreator/myplugin/scripts 10. INSTALLS += testscriptfiles 11. 12. ... However, the script doesn't get installed. How can I do this? ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] Get the type of project (qmake, cmake, ...) and the list of files in the project
Hello, I'm writing a pluging that needs to make changes to the .pro file. Is there a way to know from within my plugin which type of project is opened? I mean, is it a project based on QMake, based on CMake, etc. And I need to have a list of all the files in the project to see if a certain file already exists. This is something I can also do without the help of other Qt Creator plugins, but I think it would be nicer to use already existing functionality. How can I access this information? ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: Qt 4.5.0 tp1 and Plasma
2008/10/23 Aaron J. Seigo [EMAIL PROTECTED] On Thursday 23 October 2008, Riccardo Iaconelli wrote: * No applet handle on the desktop. (that doesn't need much description. ;-) ). You put your mouse on it... and simply nothing happens. that's disconcerting. could you pop some debug output into Containment::sceneEventFilter and see what's going on there? e.g. does it get to the point where it creates the AppletHandle at all? (i'm assuming this is broken without compositing turned on as well?) See https://bugs.kde.org/show_bug.cgi?id=164575 I forgot to report it to Trolltech though :-( ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: playground plasmoid redux
2008/10/2 Aaron J. Seigo [EMAIL PROTECTED] broken debugapplet - really cool idea; needs kdelibs patches commited, lots of problems in the applet itself Sorry about that. I don't have enough time to keep it working. And I think using dbus is not ideal. The idea behind it was that I could print debug messages while using the program being debugged without switching to console every time. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [Desktop_architects] The reason Adobe does not want to port Photoshop?
On 10/13/06, Segedunum [EMAIL PROTECTED] wrote: I mean, even if Adobe do create a Linux desktop port, how does Adobe package it up and how on Earth is anyone going to install it? Anybody think of things like that? Why can some companies do this and Adobe not? What do they need? An installer api that is used by each and every linux/unix distro? Why do people consider Windows the same as the whole of all linux/unix distro's? One version of one distro is equivalent with one version of Windows. What I mean is, each distribution is a completely different operating system but built with common parts like the linux kernel. Yet, conveniently, some think that everything that uses the linux kernel is by definition the same operating system. That does not mean that it's not necessary to work together of course and make it more easy for software developers to deploy their products. Where are the development tools? The question is: What do they need? It looks to me that there needs to be more communication. What licenses do I have to buy for development tools? Yes - ISVs *will* ask that question. Depends on which tools they want to use which in turn is not an operating system problem as far as I can see. Where are the stable libraries I use on the platform, akin to the Win32 API on Windows, or are there separate libraries that all have completely different looking interfaces? By that I don't just mean having libraries at a desktop level, but libraries with the same kind and style of APIs for doing all manner of things throughout the OS. And by 'APIs', no I don't mean just throwing out a CLI command and 'parsing' the 'stuff' that comes back. Many programmers in organisations with lots of servers and desktops to deploy on will ask if you can do things remotely as well. I think that's a good point. Although some software (and their development files, like include files) are available on most if not all linux platforms. How does someone install, and configure, a piece of software graphically? This is a desktop, right? Of course. One needs to write an install program, it's as simple as that. GTK? Well, most distro's include GTK Qt? Most do include it as well. Other toolkits? The same. Or, you can link it in such a way that all the code needed is included and you do not depend on the system anymore. Disadvantage is size of course. Will all those interfaces stay sane and compatible for any period of time? I think for KDE (and Qt) the interfaces stay sane and compatible. I don't know the policies for other libraries. But there's always a choice I think. What can I at least guarantee to my customers that it will work on? How can I support it if the interfaces are there but the implementations are all different? The last point is relevant to something like the LSB. People want a set of known and set binaries they can build against and use. Heck, even doing that can be difficult enough. Anything else is useless, no matter how many test suites it's been through. Where's the online documentation for doing all of this? A lot of libraries are fairly well documented. Usually searching for the library via google gives enough information. But not always. Tick the boxes on most of this and you also start attracting people who write 'free' and open source software on Windows as well. By doing this you also start to attract a wider userbase. Criticise Microsoft all you like, and I personally think Adobe are slitting their own throats in the long run, but Microsoft provide all that - for all the ways in which they inexplicably screw many things up that should be good. Microsoft does not provide everything though. On the other hand, it looks like some people become lazy and expect everything to be served on a dinnerplate. I want to write Photoshop: I need: - Graphics lib - Color management - UI - ... And I just link one to another. That's not programming (at least for me). Sometimes one needs to do some dirty work and create something yourself. But it's of course a bonus for Windows if they do serve all this. On the other hand, most of these libraries have equivalents on Linux. My opinion of course, don't take it too seriously. -- BT Tools http://bttools.blogspot.com/ ___ Desktop_architects mailing list Desktop_architects@lists.osdl.org https://lists.osdl.org/mailman/listinfo/desktop_architects
Re: koffice/karbon
On 8/4/06, David Faure [EMAIL PROTECTED] wrote: On Thursday 03 August 2006 19:43, Tim Beaulen wrote: SVN commit 569387 by beaulen: -fPIC is needed on AMD64 it seems Well, amd64 detects it, but isn't -fPIC needed always? I have no idea. Someone on IRC told me he had problems compiling Karbon on his AMD64 computer. I looked around on the internet and saw that ia64 computers also had problems with -fPIC. (Browsing through the CMake code I saw that -fPIC is only added to the c-flags and not the cxx-flags.) Since it looks like this is a problem on 64 bit computers, I added this temporary hack. The correct solution is, like BCoppens told me on IRC, to add a check to see if -fPIC can be used and if it needs to be used. So compiling a little test program to see if it fails, and if it does, add -fPIC to the cxx flags. ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
[kde-doc-english] [Bug 66045] Karbon needs documentation
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=66045 tbscope gmail com changed: What|Removed |Added CC||tbscope gmail com
