[PyKDE] Back to work..
Hi Phil,
here is the diff against build.py v3.4, I'm using for the RPMs.
I'm confident about the first hunk, but unsure about the second:
--- build.py.orig 2002-10-08 19:11:40.0 +0200
+++ build.py2002-10-08 20:13:35.0 +0200
@@ -1147,7 +1147,7 @@
f = open("Makefile","a")
f.write("\ninstall-eric:\n")
-ericdir = modDir + os.sep + "eric"
+ericdir = os.path.join(modDir, "eric")
# Create the platform specific wrappers.
ename = createPyWrapper(ericdir,"eric","eric")
@@ -1162,6 +1162,7 @@
f.write("\t-%s eric%s*.py %s\n" % (platCopy,os.sep,ericdir))
f.write("\t-%s eric%s*.pyc %s\n" % (platCopy,os.sep,ericdir))
f.write("\t-%s eric%s*.qm %s\n" % (platCopy,os.sep,ericdir))
+f.write("\t-%s eric%s*.ts %s\n" % (platCopy,os.sep,ericdir))
f.write("\t-%s %s %s\n" % (platCopy,ename,platBinDir))
f.write("\t-%s %s %s\n" % (platCopy,uname,platBinDir))
f.write("\t-%s %s %s\n" % (platCopy,hname,platBinDir))
Hans-Peter
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Where & What ?
On Wednesday 23 October 2002 10:10, Phil Thompson wrote: > On Wednesday 23 October 2002 9:02 am, Jonathan Gardner wrote: > > On Tuesday 22 October 2002 12:25 pm, Rob Hooft wrote: > > > Jonathan Gardner wrote: > > > > 3. Web designer. Needs to be familiar with PHP, or willing and able > > > > to learn. > > > > > > What you describe might actually be served very well with a WikiWiki. > > > And with MoinMoin there is a very nice python implementation available. > > > That would just leave you with the requirement to find a place that can > > > host a Wiki for you. > > > > Sounds great. Where can we do it? Can you administer something like this? > > Why don't you use the Wiki on python.org? There is a section for PyQt which > I put introductory, "PyQt is great" type stuff in. It would be one way to > give PyQt greater exposure to the wider Python community. Also regular Freshmeat release entries would serve this purpose. Last one of PyQt is from july with version 3.3, and for PyKDE from may with 3.2.4. > Phil Hans-Peter ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] Screenshots: PyQt/KDE Development-Portal
Can be found here : http://members.fortunecity.de/dwisp/ (Warning, images are large ~200k each) Luckily, one of my old accounts was still alive, so I put the files there. Some things to remember when looking at them : They're a draft. The pictures are more or less placeholders (to see how colors, layout and geometry work together) Comments welcome No, I dont want to keep the name ... Colors were inspired by riverbankcomputing (Now I understand your logo ..., but I took some time) :) Have fun -Marc ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] Getting control over the Tab key
This is more a Qt than a PyQt question, but Pythoneers are so knowledgeble... :-) I am trying to get control over the tab key in my application's main widget. But even redefining keyPressEvent() for the main widget doesn't help, the tab key events never arrive. At what level are they filtered out, and what can I do against that? Konrad. ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
On Mittwoch, 23. Oktober 2002 13:13, Marc Schmitt wrote: > Can be found here : > > http://members.fortunecity.de/dwisp/ v3: o moved yellow box o added different navigation-bar background o added "logo" o some geometry cleanups The whole stuff looks a bit kde-ish, but that will change with different images. Some thing I totaly forgot : I only have a LCD panel here, so the colors may be a bit off on normal screens. Also, jpeg produces some artefacts ... -Marc ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Getting control over the Tab key
On Wed, 2002-10-23 at 15:04, Konrad Hinsen wrote: > I am trying to get control over the tab key in my application's main > widget. But even redefining keyPressEvent() for the main widget > doesn't help, the tab key events never arrive. At what level are they > filtered out, and what can I do against that? They may be filtered out by the widget that has focus, it's hard to tell. If you want to make sure that you catch all the tab key events, have a look at QObject::eventFilter() and QObject::installEventFilter(). Installing an event filter in the QApplication will catch all events, but it also means routing all events through the event filter, which takes it share of resources. //Fredrik ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
Marc Schmitt wrote: Can be found here : http://members.fortunecity.de/dwisp/ (Warning, images are large ~200k each) Luckily, one of my old accounts was still alive, so I put the files there. Some things to remember when looking at them : They're a draft. The pictures are more or less placeholders (to see how colors, layout and geometry work together) Comments welcome No, I dont want to keep the name ... [snip] Hmm... "Py.Heaven" does seem random... So here is an idea: I've long thought that the name 'PyQt' was backwards... it should be 'QtPy', because it sounds like "cutie-pie" (a term of endearment, for those "not from around these parts" ;) ) Anyway, it might be something you could play with in a name. Have fun! Eli . "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram eli.carter(a)inet.com `- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
On Mittwoch, 23. Oktober 2002 16:51, Eli Carter wrote: > Hmm... "Py.Heaven" does seem random... So here is an idea: > I've long thought that the name 'PyQt' was backwards... it should be > 'QtPy', because it sounds like "cutie-pie" (a term of endearment, for > those "not from around these parts" ;) ) Anyway, it might be something Ehm, could you define "cutie-pie" in some other words please ? (my Longman DCE defines "endearment" as "an action or word that expresses your love for someone", ... I just don't get it :) The name Py.Heaven is really more or less random. I wanted the tokens "Py", "Qt" and "KDE" to appear within the name, but I found nothing sensible. I appreciate your feedback about the name, but I'd also like to hear your impressions about the site as a whole. Sure, lots of details will still change (also depending on your input), but do you think the general layout (like topics, amount of information) is ok ? -Marc ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Back to work..
Am Mittwoch, 23. Oktober 2002 12:37 schrieb Hans-Peter Jansen:
> Hi Phil,
>
> here is the diff against build.py v3.4, I'm using for the RPMs.
> I'm confident about the first hunk, but unsure about the second:
>
> --- build.py.orig 2002-10-08 19:11:40.0 +0200
> +++ build.py 2002-10-08 20:13:35.0 +0200
> @@ -1147,7 +1147,7 @@
> f = open("Makefile","a")
> f.write("\ninstall-eric:\n")
>
> -ericdir = modDir + os.sep + "eric"
> +ericdir = os.path.join(modDir, "eric")
>
> # Create the platform specific wrappers.
> ename = createPyWrapper(ericdir,"eric","eric")
> @@ -1162,6 +1162,7 @@
> f.write("\t-%s eric%s*.py %s\n" % (platCopy,os.sep,ericdir))
> f.write("\t-%s eric%s*.pyc %s\n" % (platCopy,os.sep,ericdir))
> f.write("\t-%s eric%s*.qm %s\n" % (platCopy,os.sep,ericdir))
> +f.write("\t-%s eric%s*.ts %s\n" % (platCopy,os.sep,ericdir))
> f.write("\t-%s %s %s\n" % (platCopy,ename,platBinDir))
> f.write("\t-%s %s %s\n" % (platCopy,uname,platBinDir))
> f.write("\t-%s %s %s\n" % (platCopy,hname,platBinDir))
>
> Hans-Peter
>
> ___
> PyKDE mailing list[EMAIL PROTECTED]
> http://mats.gmd.de/mailman/listinfo/pykde
The .ts files should not be installed just the .qm files. Qt doesn't even
look for them if called the way it is within eric.
Detlev
--
Detlev Offenbach
[EMAIL PROTECTED]
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
Marc Schmitt wrote: I've long thought that the name 'PyQt' was backwards... it should be 'QtPy', because it sounds like "cutie-pie" (a term of endearment, for those "not from around these parts" ;) ) Anyway, it might be something Ehm, could you define "cutie-pie" in some other words please ? (my Longman DCE defines "endearment" as "an action or word that expresses your love for someone", ... I just don't get it :) That's what he means. It's similar to... "liebschen" if my high-school German serves me correctly. It can also be used as a descriptive word meaning that some person _looks_ cute or attractive. I actually tend to think of it in these terms rather than a term of endearment. Ciao, Gordon ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
> > Ehm, could you define "cutie-pie" in some other words please ? (my > > Longman DCE defines "endearment" as "an action or word that expresses > > your love for someone", ... I just don't get it :) > > That's what he means. It's similar to... "liebschen" if my high-school > German serves me correctly. QtPy -- the flirtatious python widget set! -- F R E D E R I C K P O L G A R D Y J R. Bodacion Technologies 18-3 E Dundee Road - Suite 300 - Barrington, IL 60010 Phone: 847/842.9008 - Fax: 847/842-1731 Web: http://www.bodacion.com ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
On 23-Oct-02 Marc Schmitt wrote: > On Mittwoch, 23. Oktober 2002 16:51, Eli Carter wrote: >> Hmm... "Py.Heaven" does seem random... So here is an idea: >> I've long thought that the name 'PyQt' was backwards... it >> should be 'QtPy', because it sounds like "cutie-pie" (a term of >> endearment, for those "not from around these parts" ;) ) >> Anyway, it might be something > Ehm, could you define "cutie-pie" in some other words please ? > (my Longman DCE defines "endearment" as "an action or word that > expresses your love for someone", ... I just don't get it :) > The name Py.Heaven is really more or less random. I wanted the > tokens "Py", "Qt" and "KDE" to appear within the name, but I > found nothing sensible. My German is virtually non-existent any more, but it would be somewhat of a cross between "liebchen" and "scho/"ne Ma/"dchen". Scho/"n ~= cute -> cutie (sounds like 'Q t'), which is sort of a "diminutive", like adding "-chen" on the end of word auf Deutsch (??) It's more like baby talk. Sorry, I can't do umlauts, and my spelling is probably off too. (Babelfish was no help either) It's kind of like trying to translate one of my mother's favorite jokes (she was born in the US but grew up in a German speaking household): if you asked her "Was ist los?", her reply was always "Alles was nicht angebundant ist". In English that becomes "What's wrong?" - "Everything that isn't tied down". It loses something in the translation. Jim ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Getting control over the Tab key
> They may be filtered out by the widget that has focus, it's hard to At least they never appear in keyPressEvent(), neither for the main widget nor for the widget in focus. > tell. If you want to make sure that you catch all the tab key events, > have a look at QObject::eventFilter() and QObject::installEventFilter(). I tried that, but how does one define an event filter in Python? Here is what I tried: class FilterObject(QObject): def eventFilter(self, object, event): sys.stderr.write(repr(object) + ':' + repr(event) + '\n') return 1 app = QApplication(sys.argv) ... app.installEventFilter(FilterObject()) ... app.exec_loop() This doesn't crash, but doesn't do anything either, the event filter routine is never called. Konrad. ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Getting control over the Tab key
On Wednesday 23 October 2002 7:28 pm, Konrad Hinsen wrote: > > They may be filtered out by the widget that has focus, it's hard to > > At least they never appear in keyPressEvent(), neither for the main > widget nor for the widget in focus. > > > tell. If you want to make sure that you catch all the tab key events, > > have a look at QObject::eventFilter() and QObject::installEventFilter(). > > I tried that, but how does one define an event filter in Python? > Here is what I tried: > > class FilterObject(QObject): > > def eventFilter(self, object, event): > sys.stderr.write(repr(object) + ':' + repr(event) + '\n') > return 1 > > app = QApplication(sys.argv) > ... > app.installEventFilter(FilterObject()) > ... > app.exec_loop() > > This doesn't crash, but doesn't do anything either, the event filter > routine is never called. That's because you aren't keeping a reference to the FilterObject instance so it gets garbage collected immediately. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Where & What ?
On 23-Oct-02 Marc Schmitt wrote: > On Dienstag, 22. Oktober 2002 21:16, Jim Bublitz wrote: >> Sounds like a user-generated FAQ - I think I'll steal that idea >> too. I'd definitely be interested in seeing that info, as I >> haven't used anything but SuSE for quite awhile. It would be >> helpful to me for improving the install process and users >> wouldn't have to fix the same stuff with every new release. > > I think, out of a *user* point of view (user is everyone who > wants to use Py*, not develop it) binary packages are far more > important then source packages. While improving the source > setup surly is something important, providing painless binary > packages for all major distributions will have (imho) more > impact. I pretty much agree, but if something won't build on a particular platform at all, it's kind of hard to do the binary. > Ack. I haven't thought about it, when I last uploaded the binary > packages to sf. But I guess we have to time it anyway, because > the files within /incoming tend to get remove quite often. It does make international collaboration more difficult. > See, this is one of the largest problems I currently have > (besides my fundamental lack of money) : Where to put files ? > It's alway a pita publish something thats larger then 40k. Same here. >> I don't have a problem mirroring the source tarballs on SF, but >> I still think there are a lot of good reasons to make riverbank >> the "official" site for the base source packages. Phil and I >> have discussed this in the past and decided against making SF >> the "official home" of the source code for various reasons. I >> think from "our" perspective (Phil will certainly disagree if >> the "our" doesn't apply) it makes a lot of sense to have a >> home for development, and a separate home for >> users/binaries/everything else. If nothing else, riverbank is >> much more convenient on this end and Phil has it highly >> automated. > Personally, I tend to "one place to rule them all". Again, simply > out of a users point of view. Out of political reasons, I surely > understand that you want to host your files there, as it gives > you some part of image (i hope you understand what i mean) and > serves as advertisement. So there's nothing wrong with it, but > I wouldn't duplicate the sources (at least not if riverbanks > host is stable enough). What about this solution : > Keep the sources on rbc, everything else on (e.g.) sf. And > provide transparent links on sf that link to the sources, with > a comment "maintained at riverbankcomputing". That seems the perfect solution to me. The two concerns are really access and control (along with co-ordination and convenience), and linking is sufficiently transparent to solve the access part without doing any harm to the control part. A lot of projects seem to do something like this. >> > In my mind, the best way to handle this is to keep your RPMs >> > as close as possible to the distribution's RPMs. If RedHat >> > and SuSE package PyQt differently, then our RedHat and >> > SuSE RPMs would be different as well. We'll need a little >> > document telling people what they need to get and how to >> > install it, but they would need that anyway. > Distributions won't be able to afford this way much longer - in > longterm, It leads to fragmentation and weakens their position. > And personally I find it insane, that if Phil or Jim relase a > new version, d*v(*k) new packages had to be generated (d=number > of distribution, v=number of version, k=number of kdes) - just > for this package. Imaging what a waste of resources it is. So if > we here could at least minimize d, AS LONG AS we can provide a > drop-in replacement, why shouldn't we do so ? If we can't, we > have to find another solution, but I really prefer unification. This is open source - we love to duplicate efforts (look at the number of IRC clients on freshmeat, for example). > Out of this reasons, I'd like to use a unified .spec, which > builds on every platform. I've seen good examples (the one > Hans-Peter provided) about using flexible macros which can > configure nearly anything. So at least we should give it a try. I don't know enough about rpm to know if this is feasible, but I've wondered if it's possible, and it certainly seems desireable. If someone can make a start on a .spec file that does this and provide me a little support, I'll be happy to try and maintain it for PyKDE. We used to autmatically generate a .spec file (in the Makefile I believe), but I never paid much attention to it. > Debian will probably have to go their own way, but hey - Debian > always does this ... :) (I've used it exclusivly for over a > year) >> I agree - consistency is nice if you can achieve it, but >> I don't think it's ever a strong reason for choosing a course >> if action. I'd trust the package maintainers to use their best >> judgment and hopefully provide enough documentation to make >> their releases usable.
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
Jim Bublitz wrote: On 23-Oct-02 Marc Schmitt wrote: On Mittwoch, 23. Oktober 2002 16:51, Eli Carter wrote: Hmm... "Py.Heaven" does seem random... So here is an idea: I've long thought that the name 'PyQt' was backwards... it should be 'QtPy', because it sounds like "cutie-pie" (a term of endearment, for those "not from around these parts" ;) ) Anyway, it might be something Ehm, could you define "cutie-pie" in some other words please ? (my Longman DCE defines "endearment" as "an action or word that expresses your love for someone", ... I just don't get it :) The name Py.Heaven is really more or less random. I wanted the tokens "Py", "Qt" and "KDE" to appear within the name, but I found nothing sensible. My German is virtually non-existent any more, but it would be somewhat of a cross between "liebchen" and "scho/"ne Ma/"dchen". Scho/"n ~= cute -> cutie (sounds like 'Q t'), which is sort of a "diminutive", like adding "-chen" on the end of word auf Deutsch (??) It's more like baby talk. Sorry, I can't do umlauts, and my spelling is probably off too. (Babelfish was no help either) It's kind of like trying to translate one of my mother's favorite jokes (she was born in the US but grew up in a German speaking household): if you asked her "Was ist los?", her reply was always "Alles was nicht angebundant ist". In English that becomes "What's wrong?" - "Everything that isn't tied down". It loses something in the translation. Jim That's a better explanation than I could give. Thanks Jim. :) Eli -- . "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram eli.carter(a)inet.com `- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
Frederick Polgardy Jr wrote: >>>Ehm, could you define "cutie-pie" in some other words please ? (my >>>Longman DCE defines "endearment" as "an action or word that expresses >>>your love for someone", ... I just don't get it :) >> >>That's what he means. It's similar to... "liebschen" if my high-school >>German serves me correctly. > > > QtPy -- the flirtatious python widget set! > I have this image of a green cartoon snake with big, blue eyes, long lashes... If nothing else, "Cutie-Pie" should be the name of the PyQt "mascot". ;) Eli . "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram eli.carter(a)inet.com `- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
On Mittwoch, 23. Oktober 2002 13:13, Marc Schmitt wrote: > Can be found here : > > http://members.fortunecity.de/dwisp/ v5 : o changed name to Qt.Py o changed left menu, according to some of Jonathans suggestions o this release featuring sweet katie o replaced logo with new beta-logo of portal for more details, see text below. On Mittwoch, 23. Oktober 2002 18:54, Jonathan Gardner wrote: > Overall, it is really really nice. When I look at that page, I feel relaxed > and happy. Also, I really got interested in learning more. Ahhh. Thanks, that feels good :) > The birds are a very nice touch. I also like the subtle gear in the upper > left corner. Would it be possible to add Trolltech, Python, and/or > Riverbank's logo as well? I don't think KDE should take center stage, even > though they do have the best logo. Yes, making the page look like kde wasn't my intention (althogh all icons you can see are were stolen from several kde-iconsets - i hope i can use them). I replaced the logo in the upper left with a quick-and-dirty replacement, until I get something better. Placing all logos on the page is impossible. I tried it. I downloaded all logos, but even with two it looks terrible. Adding more than one logo to the top-bar would only be possible with a complete redesign. The only place which has some additional room is the top right, but this place is reserverd for a very small graphic to loosen things up a bit. All those logos certainly will appear (at least if I get permission from the copyrightholders) somewhere, e.g. under "Background". > The splash/home page is really nice. The wording and the style is > comfortable and inviting. It is my intention to reserve the main-eyecatching field within the middle of the screen for pictured advertisements. I'd like to keep this one for a couple of week and replace it when major changes appear. The logo top-right is meant for this purpose too, to get changed from time to time. This should make the page a bit more living (and makes you hopefully come back to see what "they" invented this time). > The sidebars, which tell me about the site layout, is comfortably laid out. > The sections are perfect. It is missing a few things: > > - Links to Riverbank Computing, Trolltech, KDE, and python. It is best if > these were on the home page, in text or image links. Links to them will be placed, but imho they should be placed one level below. They are not that important and the space on the left is very valuable. Also, I'd like to keep the information on each level (especiall the top) easy, to allow users to "pull" what they need. > - Link to SourceForge with the SourceForge logo. If we were not hosting on > SF, this is not an issue, but if this page is hosted on SF, it needs to be > there on the home page and every page, I think. Here's the code for that. > > http://sourceforge.net";> src="http://sourceforge.net/sflogo.php?group_id=61057&type=5"; > width="210" height="62" border="0" alt="SourceForge Logo"> Thanks. I added it to the down-left. It fits pretty nice there and is (in a positive sense) a bit complimentary to the green bar. > - Your name at the bottom should link to your home page or email as well. > You have to take credit for your work. ;-) :) But I'm not that important, too. So, in order to find the appropriate place for the sf-logo, I removed the (c) link. It will appear either within the document-source, on the end of the page or on "authors" > - Download Now link can be a single link that leads to a page with > instructions on what to download from where. Separating it out into source > and binaries without instructions is confusing for new people unfamiliar > with free software development. That should happen on the page with > instructions for downloading and installing. ack. fixed. > This was just a couple of ideas, and you can use it or not, I won't care > either way. Again, I really, really like it! When you want it put up, send > me a tarball of the pages and images, and I'll post it at SF. You don't > have to have it 100% perfect before you post it. You can rework the design > as much as you like, and I'll even get you set up with shell access on SF. Again, thanks a lot for the feedback. Thats helps me to go an, and shows me I'm not producing too much garbage. - merged to produce fewer mails - On Mittwoch, 23. Oktober 2002 18:54, Jim Bublitz wrote: > My German is virtually non-existent any more, but it would be > somewhat of a cross between "liebchen" and "scho/"ne Ma/"dchen". > Scho/"n ~= cute -> cutie (sounds like 'Q t'), which is sort of a > "diminutive", like adding "-chen" on the end of word auf Deutsch > (??) It's more like baby talk. Sorry, I can't do umlauts, and my > spelling is probably off too. (Babelfish was no help either) Wow. Very good. :) Except "liebchen" is no german word I know, I'd rather use "Schatz" (which you call your loved one) or "Scha/"tzchen" (which you *should
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
On Mittwoch, 23. Oktober 2002 22:39, Eli Carter wrote: > > > > QtPy -- the flirtatious python widget set! > > I have this image of a green cartoon snake with big, blue eyes, long > lashes... If nothing else, "Cutie-Pie" should be the name of the PyQt > "mascot". ;) If you can draw it, I'd really be interested for a replacement for the logo on the page. I'm a terrible artist, so I tend to make everything geometric - but I love courved, living, colorful stuff without angles. If you have something which fits into the upper, left corner - just send it to me. Bye -Marc ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
On 23-Oct-02 Eli Carter wrote: > That's a better explanation than I could give. Thanks Jim. :) My pleasure - I liked the QtPy name, too. Jim ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Back to work..
On Wednesday 23 October 2002 18:42, Detlev Offenbach wrote: > The .ts files should not be installed just the .qm files. Qt doesn't even > look for them if called the way it is within eric. This would allow users to prepare translations without digging in source/build trees, wouldn't it? > > Detlev Hans-Peter ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Screenshots: PyQt/KDE Development-Portal
On 23-Oct-02 Marc Schmitt wrote: > On Mittwoch, 23. Oktober 2002 18:54, Jim Bublitz wrote: >> My German is virtually non-existent any more, but it would be >> somewhat of a cross between "liebchen" and "scho/"ne Ma/"dchen". >> Scho/"n ~= cute -> cutie (sounds like 'Q t'), which is sort of a >> "diminutive", like adding "-chen" on the end of word auf Deutsch >> (??) It's more like baby talk. Sorry, I can't do umlauts, and my >> spelling is probably off too. (Babelfish was no help either) > Wow. Very good. :) Except "liebchen" is no german word I know, > I'd rather use "Schatz" (which you call your loved one) or > "Scha/"tzchen" (which you *should not* call a (sexual > attractive) woman) - I guess there's no direct translation. Now that you mention it, I can't remeber every hearing "liebchen" at home, but definitely "Schatz" or "Schatzie". "Liebchen" is the stereotypical "Hollywood" word used in dialog with German characters - I'm pretty sure it occurs in a scene is "Casablanca" for example - as in "my little liebchen". Now I wonder what the derivation of that word is ... Jim ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Where & What ?
On Tuesday 22 October 2002 12:25 pm, Rob Hooft wrote: > Jonathan Gardner wrote: > > 3. Web designer. Needs to be familiar with PHP, or willing and able to > > learn. > > What you describe might actually be served very well with a WikiWiki. > And with MoinMoin there is a very nice python implementation available. > That would just leave you with the requirement to find a place that can > host a Wiki for you. > Sounds great. Where can we do it? Can you administer something like this? -- Jonathan Gardner [EMAIL PROTECTED] ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Where & What ?
On Wednesday 23 October 2002 9:02 am, Jonathan Gardner wrote: > On Tuesday 22 October 2002 12:25 pm, Rob Hooft wrote: > > Jonathan Gardner wrote: > > > 3. Web designer. Needs to be familiar with PHP, or willing and able to > > > learn. > > > > What you describe might actually be served very well with a WikiWiki. > > And with MoinMoin there is a very nice python implementation available. > > That would just leave you with the requirement to find a place that can > > host a Wiki for you. > > Sounds great. Where can we do it? Can you administer something like this? Why don't you use the Wiki on python.org? There is a section for PyQt which I put introductory, "PyQt is great" type stuff in. It would be one way to give PyQt greater exposure to the wider Python community. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] Who ?
On Dienstag, 22. Oktober 2002 13:59, Phil Thompson wrote: > I would also like to keep a list of package maintainers so that I can give > them some warning of a new release. I'm preparing SuSE packages. I'm trying to pack them for the lastest version thats available via YOU. In addition, I'm experimenting a bit with a PyQt/PyKDE development-portal. -Marc ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Where & What ?
On Dienstag, 22. Oktober 2002 21:16, Jim Bublitz wrote: > Even plain old HTML to begin with would be fine - you can always do > the PHP for v2.0 Yesterday I started to layout of a page within a design-tool. I made a screenshot and sended it to this list, unfortunatly, the mail is ~90k, and it still awaits moderator approval. > > It would be really nice to have everyone write a short page for > > how they get their system to work and what mods they like to > > make. A page for Windows, subcategoried into 95, 98, 2000, NT, > > XP and whatever is useful would be good. A page for Linux, > > subcategoried into Debian, Redhat, SuSE, Mandrake, and > > whatever distribution any of you use out ther would be really > > nice. This way, a new user can come to the website, read up on > > what they need to do for their system, and we can hopefully > > expand our user base. Ack. > Sounds like a user-generated FAQ - I think I'll steal that idea > too. I'd definitely be interested in seeing that info, as I haven't > used anything but SuSE for quite awhile. It would be helpful to me > for improving the install process and users wouldn't have to fix > the same stuff with every new release. I think, out of a *user* point of view (user is everyone who wants to use Py*, not develop it) binary packages are far more important then source packages. While improving the source setup surly is something important, providing painless binary packages for all major distributions will have (imho) more impact. > > The best way is to send an email to me saying that you have the > > latest package. Then we can discuss the best way for you to get > > it to me. I can set up a temporary FTP server that you can > > upload to. We can also agree to a time that you can upload > > directly to SF and I can get it then. > > Sounds good to me. Or else people can just send you links and can > handle the uploads/ftp on their own favorite server. Ack. I haven't thought about it, when I last uploaded the binary packages to sf. But I guess we have to time it anyway, because the files within /incoming tend to get remove quite often. > >> Somebody probably needs to tackle (1) at least. I feel like I > >> should be responsible, but as is apparent from the slack release > >> schedule of late, it's difficult to find the time and I'm also a > >> terrible web site designer. I'm happy to keep PyKDE up-to-date > >> at the source level, but realistically I can't handle much more > >> than that - I haven't kept up on promises I've made here on > >> some other stuff like code for doing panel applets. > > > > You should definitely NOT do it. As I said, I made a draft for review. But currently, I dont know where it is :(. The one who's responsible for giving approval - please ... (Or does anyone have a place where I could upload this ?) See, this is one of the largest problems I currently have (besides my fundamental lack of money) : Where to put files ? It's alway a pita publish something thats larger then 40k. > >> I agree with Phil that riverbankcomputing is not an option for > >> binaries - Phil gets stuck paying for extra bandwidth from a lot > >> of large downloads, and in addition it ends up being a lot of > >> extra maintenance work for Phil. Yes. > > SF is more than willing to host everything. I think hosting the > > tarballs at SF is far better than hosting them at RiverBank > > because of that. Maybe the commercial version of PyQt and such > > should still be at RiverBank, but the free version should > > definitely find its home on SF for bandwidth reasons. Yep, but see below. > I don't have a problem mirroring the source tarballs on SF, but I > still think there are a lot of good reasons to make riverbank the > "official" site for the base source packages. Phil and I have > discussed this in the past and decided against making SF the > "official home" of the source code for various reasons. I think > from "our" perspective (Phil will certainly disagree if the "our" > doesn't apply) it makes a lot of sense to have a home for > development, and a separate home for users/binaries/everything > else. If nothing else, riverbank is much more convenient on this > end and Phil has it highly automated. Personally, I tend to "one place to rule them all". Again, simply out of a users point of view. Out of political reasons, I surely understand that you want to host your files there, as it gives you some part of image (i hope you understand what i mean) and serves as advertisement. So there's nothing wrong with it, but I wouldn't duplicate the sources (at least not if riverbanks host is stable enough). What about this solution : Keep the sources on rbc, everything else on (e.g.) sf. And provide transparent links on sf that link to the sources, with a comment "maintained at riverbankcomputing". > > In my mind, the best way to handle this is to keep your RPMs as > > close as possible to the distribution's RPMs. If RedHat and > > Su
Re: [PyKDE] Where & What ?
> > > SF is more than willing to host everything. I think hosting the > > > tarballs at SF is far better than hosting them at RiverBank > > > because of that. Maybe the commercial version of PyQt and such > > > should still be at RiverBank, but the free version should > > > definitely find its home on SF for bandwidth reasons. > > Yep, but see below. Let me make this clear - Riverbank will be the home of all software that Riverbank develops. Whether or not people take copies and put onto other sites is up to them. > Personally, I tend to "one place to rule them all". Again, simply out of a > users point of view. Out of political reasons, I surely understand that you > want to host your files there, as it gives you some part of image (i hope > you understand what i mean) and serves as advertisement. So there's nothing > wrong with it, but I wouldn't duplicate the sources (at least not if > riverbanks host is stable enough). What about this solution : > Keep the sources on rbc, everything else on (e.g.) sf. And provide > transparent links on sf that link to the sources, with a comment > "maintained at riverbankcomputing". That, to me, is the ideal solution. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re [PyKDE] Who ?
Title: Message On Dienstag, 22. Oktober 2002 13:59, Phil Thompson wrote:> I would also like to keep a list of package maintainers so that I can give> them some warning of a new release.I have recently packaged PyQt/PyKDE for Mandrake 8.2 and planed to do it as soon as I have upgrade my box. Jérôme
