Re: [PyKDE] PyKDE on mandrake 10.1?
On November 26, 2004 12:56, Knut Morten Johansson wrote: > On Tuesday 23 November 2004 20:13, Jérôme Martin wrote: > > Le mardi 23 Novembre 2004 15:48, Knut Morten Johansson a écrit : > > > On Tuesday 23 November 2004 15:20, Jérôme Martin wrote: > > > > Could one of you make the rpm for Mdk10.1 available somewhere ? > > > > > > RPMs and SRPMs are avalible at: http://83.108.52.87:8001 > > > > It doesn't working now (I had to get before seing your email). > > Sorry, was using my bandwith .torrenting a iso. Should work now. > > Knut mirror: http://pykde.gemlog.ca/ I can't afford the time to upgrade to 10.1 myself, but I hope this helps someone (and Knut -- I felt guilty throughout the whole wget :-) ) Please post this list on success, so that Knut can take his down. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] kouvert
On Tuesday 10 August 2004 07:49, Lionel Roubeyrie wrote: > Any suggestions welcome. > Kouvert : http://members.chello.fr/lionel.roubeyrie/ > Lionel My system crash, I want to kill you. :-) Just kidding -- I liked that part of your webpage. Very nice. Even kept my comments which I wondered about. A diff against the backup though showed that it nuked one commented entry. It was the only one that was followed by another line that was commented out. Maybe something to look at. I like how you layed it out too. Plus thanks for jcombo. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Superkaramba theme could not load PyKDE
On Friday 23 July 2004 12:05 pm, Maciej Sitarz wrote: > Hi > I'm using Mandrake 10 and I have a problem with superkaramba and a theme > called Slickbar http://kdelook.org/content/show.php?content=5658 Hi, Not prescriptive help, but I too am running Mandrake 10 and all my own pykde stuff works fine. I played with Slickbar, but it kept going south on me (ala kill -9), so I just put it on the shelf for a while until a new release comes out. It's not like I *need* it or anything ;-) I do have some db output on one desktop using Superkaramba and it's been stable and happy for months now. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] 10.0 official rpms for PyKDE
On Tuesday 25 May 2004 10:03, Jim Bublitz wrote: > > The problem is that during the last couple of weeks there was not a > > single day when all of the parts of the whole were stable at the same > > time ;-) > > I believe you'll find that mentioned in the Book of Revelations as sign of > the end of the world. :) I think it's actually '1st Bublitz, Ch 3, verses 7-9' :-) I was only asking, because I'm not as handy as many on this list and I often have a tough time compiling it all, so I really dread when I have to install something elsewhere. I've used chkinstall before to make rpms, but then the target box seems to need to be *just* like mine or it will fail to install. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] 10.0 official rpms for PyKDE
Hi Simon, Have you made any moves that way or...? -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE-3.11rc1 release
On Wednesday 12 May 2004 23:04, Simon Edwards wrote: > > I now have a working PyKDE under Mandrake 10 Official: > > > > sip-snapshot-20040510.tar.gz > > PyQt-x11-gpl-3.11.tar.gz > > PyKDE-3.11rc1.tar.gz > > Just for sanity's sake, can you do an "import kdeui" from the python > console and not get linking errors? Python 2.3.3 (#2, Feb 17 2004, 11:45:40) [GCC 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)] on linux2, Qt-Version >>> import kdeui >>> Looks ok to me. No errors at all. That was from within Eric3, but the regular console is the same - no probs. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE-3.11rc1 release
On Saturday 08 May 2004 11:43 am, Jim Bublitz wrote: > Requirements: > > sip3.10.1 or sip4 (20040504 snapshot or a later snapshot or > release - earlier snapshots or 4.0rc3 will NOT work), PyQt-3.11 > or a later snapshot or release, Python2.2.2 or later (earlier > versions may work but haven't been tested), KDE3.0.0 - 3.2.2. :-) I now have a working PyKDE under Mandrake 10 Official: sip-snapshot-20040510.tar.gz PyQt-x11-gpl-3.11.tar.gz PyKDE-3.11rc1.tar.gz Thanks again you guys! -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] eric3: Request for comment
On April 17, 2004 02:51, Detlev Offenbach wrote: > Hi, > > due to the fact, that most distributions nowadays include Python 2.2 or > newer I would like to drop support for older Python versions in eric3. > If there are substantial reasons for not doing this, please let me know. Fine here too. I'm also on 2.3 :-) -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Bionic vision
On January 30, 2004 20:51 pm, Jim Bublitz wrote: > seems to be responding faster. It's looks a lot worse because I > had a little bleeding in the white of the eye (and all the blood > accumulates in the eyeball - kind of gross looking), but that > has no effect on vision, recovery, or even comfort. Plus I have > a black eye from the anesthetic - had a different guy do it this > time and he wasn't as good as the previous one. I had surgery You have our prayers Jim. Take all the time you need to recover properly. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] Mandrake 9.2
Someone wrote recently to find what works on 9.2 mdk. I haven't upgraded lately, but a few melty caps on my old mobo forced a reinstall, so I went back to an old dir I had for 9.2. The following packages work fine with just a Uvh: libqscintilla2-1.1-1mdksbe.i586.rpmPyQt-3.7-1mdk92.i586.rpm libqscintilla2-devel-1.1-1mdksbe.i586.rpm PyQt-devel-3.7-1mdk92.i586.rpm libsip10-3.7-mdk92.i586.rpmsip-3.7-mdk92.i586.rpm libsip10-devel-3.7-mdk92.i586.rpm PyKDE-3.7-1mdk92.i586.rpm I know there are newer rpms, but these are known to work for sure. Twice now :-) After I'm done 'nesting' with apache,sqlledger,postfix etc I'll get around to actually upgrading to the new rpms posted the other day thanks to Simon. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] PyQt application packagers for windows?
On January 23, 2004 01:01 am, Ulrich Berning wrote: > Greg Fortune schrieb: > >My e-mails and phone calls with Trolltech addressed exactly that clause > > and they said it was fine even after I explained that strictly speaking > > it was a violation of that clause. They did say that if I exposed the Qt > > api in my app and made it available to the end user (aka, the qt > > scripting component), that would be a violation. ... > For me, this license clause has a clear meaning: Make it impossible for > the end user, to create new software with any component of your > software, but making the software customizeable with a scripting > language like Python, so the end user can write Python macros to > add/modify/delete use cases or dialog components of the application, is > ok. If this is not true, we can stop our software development now and > search for another toolkit, because scripting will be one of the key > features of our commercial application. IF the above is true, could one not use py2exe to distribute to your customer? I used it once last with the free version of pyqt for windows and it was quite painless. It runs quickly and you end up with a few dlls and an exe. It turns a harmless looking small script into a few megs of files, but they are entirely self-contained for distribution. The downside for me was that I couldn't make any quick changes on the target box, but that sounds like just what you are looking for if your interpretation of the license is correct. Perhaps things have changed since then as I don't follow the windows side of things much. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] AttributeError: setBackgroundColor
On December 13, 2003 11:50 am, Stefan Seefeld wrote: > I'v been playing with pyqt a bit, and I run into > a problem with some of the examples. the QWidget's > 'setBackgroundColor' method doesn't seem to be > accessible: > > bash-2.05b$ examples2/splitter.py > Traceback (most recent call last): >File "examples2/splitter.py", line 39, in ? > t1.setBackgroundColor(Qt.blue.light(180)) > AttributeError: setBackgroundColor You need to use colour groups instead like this: self.cg = self.cus_listView.colorGroup() self.bgcolour = self.cg.color(self.cg.Highlight) self.fgcolour = self.cg.color(self.cg.HighlightedText) self.todayBtn.setPaletteBackgroundColor(self.bgcolour) self.todayBtn.setPaletteForegroundColor(self.fgcolour) I grabbed the cg from an existing object, but you could use the default cg instead. The above is just swapping some colours around. BTW, it's also how you get custom highlights or text colours in listviews, if you subclass the QListViewItem. That might look like this: class TodoChildItem(QListViewItem): def paintCell(self, painter, qg, column, width, align): #c = qg.base() #colour = qg.color(qg.Background) #Qt.red #qg.color(qg.BrightText) #qg.setColor(QColorGroup.Base, colour) #QListViewItem.paintCell(self, painter, qg, column, width, align) #qg.setColor(QColorGroup.Base, c) c = qg.text() colour = qg.color(qg.Dark) qg.setColor(QColorGroup.Text, colour) QListViewItem.paintCell(self, painter, qg, column, width, align) qg.setColor(QColorGroup.Text, c) I chose the above, because it was the first time I did it and you can still see where I was playing with things. Hope that helps. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] KTrader woes?
On October 31, 2003 23:52 pm, Jim Bublitz wrote: > I'd recommend using the second method in my previous post - > calling KCmdLineArgs.init. The next release will have a number > of simple program templates, and all but one are written that > way. It seems to be the way KDE wants to go in the future. It's > 5 or so extra lines of code. Thanks very much Jim. I'm just now starting to use the KDE part of things and didn't know about KCmdLineArgs.init - just looked up the widget I was interested in and thought the rest would be the same as Qt. Makes sense now that I know about it though, given the error I was getting. Passing a different, single element list to Kapplication and processing sys.argv with python was something that I tried, it got me in, but provoked the big KDE Crash Handler dialog on exit. Past time for me to wget all the kde docs then too... Everything else is going great. I'm really enjoying this over the other two kits I've used over the years. Just now getting to the point where I don't have to read too much when I write something new. I thought :-) -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
re:[PyKDE] KTrader woes?
Sundance sundance_at_ierne.eu.org: >Well, more precisely, it works if I copy the KCmdLineArgs.init line from >mimetype.py. If I call KApplication([], "SomeName") it dies. Apparently >KApplication REQUIRES a non-empty list as its first argument, unlike >QApplication (with which the [] trick works). Jim, sorry if this has been fixed in newer versions than the 3.7-3 version - I haven't been able to follow some of the discussion on the topic (c++). I recently had to change one program from QApplication to KApplication to support a kde widget and found that not only does it require a non-empty list as Sundance noted, but there can only be One element in that list or it will fail on 'Unexpected argument '. Of course, the program still works fine when its main class is instantiated from another script with args. I got around it by passing [sys.argv[0]] to KApplication when run stand-alone. This way it starts fine and the main class can pick off the args it needs. However, the kde crash handler kicks in when the program exits now. Sorry if this is fixed, I can certainly handle it for the time being until I upgrade. If not, can you suggest a proper cure over my work around? -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] retrieve Highlight colour value
I've tried things like: QColor(QColorGroup.Highlight) and variations - and completely different too of course. I need to set a widgets background and foreground colour to values retrieved from the current users theme/prefs. So far my attempts have only netted me a single integer number for the highlight or texthighlight - I assume these int are a palette entry? but I don't know how to map that to a value I can feed to qcolor. e.g. I'd like to change the background of a text widget to be the current colour of a scroll bar (where I don't know the colour at runtime, but want it from the user's theme). -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] PyQT and QPE/Zaurus coding tips
On October 16, 2003 05:39 am, Trevor Phillips wrote: > Firstly, how can I associate an icon with my Widget/App, such that the > icon will appear in the Qtopia/Opie task-bar? from qtpe import QPEApplication then use QPEApplication throughout instead of QApplication Sorry, I don't know how to disallow multiple instances on the Z. I have my own question on this too: I can't use popen unless I exec myself from a script rather than directly from an icon. Does anyone know the fix for that? This is only under qtopia on the Zaurus. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] [kiohuge0.o] Error 1
I thought I'd give compiling it myself a go, but it chugged away for an hour or so and I got this instead: ... /usr/lib/qt3/include -o kiohuge0.o kiohuge0.cpp /usr/include/kservice.h: In constructor `sipKService::sipKService(const KService&)': /usr/include/kservice.h:47: `KService::KService(const KService&)' is private sipkioKServicePtr.cpp:159: within this context make[1]: *** [kiohuge0.o] Error 1 ... PyKDE-3.7-2mdk.src supplied the source. I'm using PyQt from the other regular rpms - I didn't compile for pyqt since they work fine for me. I'm just trying to compile PyKDE if that makes a difference. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: piemenu widget
On September 13, 2003 18:20 pm, Richard Jones wrote: > Very, very cool :) si, very. I'm going to use it as a popup to switch between the major tasks in what I'm writing now. In the meantime, I couldn't leave it alone. I put it on a global X11 hotkey (useless left windows key) after adding chdir(path[0]) to it and QCursor.pos()x/y so it opens at the mouse pointer. Then I just have it run things with os.spawnlp. Man I love this stuff. It was a nice present for the weekend. -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: piemenu widget
On September 13, 2003 07:33 am, Peter Strath wrote: > A simple piemenu widget for PyQt is available at; Thanks Peter! What a cool idea that is. Grabbed it. Been up all night and was just going to go to bed. Now I'm going to be laying there trying to think of an excuse to use that widget somewhere instead of sleeping :-) Are there anymore interesting custom widgets around? -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] dateEdit error msg on signal
On September 11, 2003 12:57 pm, Paul Evans wrote: > but it spits out: > 'schededit.dateStart_valueChanged(const QDate&): Not implemented yet' Found it in the .ui file as print statement in a slot. Must have clicked on something to cause qtdesigner to throw that in when I looked up the args for it. sorry for the bother. That means using pyQT is still *all* good :-) -- Regards, Paul Evans ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] dateEdit error msg on signal
Hi,
This isn't hurting anything, I just wonder how I caused it. I have this
signal:
self.connect(self.dateStart, SIGNAL("valueChanged(const QDate&)"),
self.slotsyncWeekday)
and I thought it was working quietly last night just fine (I could be wrong).
I *think* all I did after was rename some unrelated widgets. Now, it
continues to function fine; it still sends me the date and everything, but it
spits out:
'schededit.dateStart_valueChanged(const QDate&): Not implemented yet'
Any idea what I should change? QdateEdit is fully implemented, so I must have
done something wrong.
I'm using PyQt3.7-1.mdk
--
Regards, Paul Evans
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
