PyGTK upgrade
When is PyGTK going to be upgraded to 2.12? gtk.CellLayout has 7 methods that all require the cellrenderer. gtk.ComboBoxEntry creates and packs the cellrenderer automatically, so without the get_cells method there doesn't appear to be a way to use any of those methods nor to change attributes of the cellrenderer. get_cells is available only in PyGTK version >= 2.12. I've been waiting since April for the upgrade. -- Jeffrey Barish ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: RE: Integration with hildon desktop
Daniel Martin Yerga wrote: > While I don't know as it's your .desktop file, I always add everyone of > this parameters to .desktop files of my apps, perhaps some of them are > useful in your case: > > Icon=name of the icon without the suffix > X-Icon-path=/usr/share/icons > X-Window-Icon=again the name of the icon without the suffix > > Note, you should have a 26x26 icon in > /usr/share/icons/hicolor/26x26/hildon/, but I think this step is in the > documentation. Yes, I have all three of those parameters in my .desktop file. My icon is in the directory that you indicated. One of the many mysteries I encountered during this exercise was that making the icon 26x26 resulted in an icon that was much smaller than all the other icons in the menu. I had to make it 64x64 before it was the same size as the others. So I have a 64x64 icon in the 26x26 directory. I got the default icon in the task navigator bar even when my logo was 26x26. Another mystery was that changing the icon did not change what appeared in the menu. I tried gtk-update-icon-cache -f /usr/share/icons/hicolor. That command updated the icon-theme.cache in the hicolor directory, but I still got the old icon. The only way I could get the new icon to display was to reboot. Evidently, there is another cache. The Diablo Reference Manual says to create a symbolic link in /etc/others-menu/extra-applications to control the order in which applications are listed in the menu. I find that what I put in that directory has no effect. Buried deep in documentation I discovered that the application must create and hold an osso Context or the application will run for ~2 minutes and spontaneously exit. -- Jeffrey Barish ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: RE: Integration with hildon desktop
Hi. - Original message - Jun Xu wrote: > To my knowledge, there are many parameters to determine what to show in > the navigator bar. So I guess that you can try the parameters > "StartupWMClass" in your desktop file. To know more info about desktop's > parameters file see: > http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-0.9.4.html > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Barish > Sent: 2008?9?27? 3:52 To: maemo-developers@maemo.org > Subject: Integration with hildon desktop > > After much fiddling, I managed to integrate my application in the hildon > desktop. It appears in the Extras menu along with its logo. I get the > loading message when it's starting, and then it runs. However, when it's > running, I get the default icon in the task navigator bar. Any idea what > I forgot to do? Thanks for the suggestion. I didn't see anything in that document that looked relevant, but perhaps I just missed it. I really don't understand why the Icon parameter isn't responsible for setting the icon in the navigator bar. I wish that Nokia had a document summarizing the steps for integrating an application into the desktop. The required information seems to be buried in many unrelated documents. -- End of Original Message -- While I don't know as it's your .desktop file, I always add everyone of this parameters to .desktop files of my apps, perhaps some of them are useful in your case: Icon=name of the icon without the suffix X-Icon-path=/usr/share/icons X-Window-Icon=again the name of the icon without the suffix Note, you should have a 26x26 icon in /usr/share/icons/hicolor/26x26/hildon/, but I think this step is in the documentation.___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 3D Games
Hi, Am Dienstag 30 September 2008 schrieb Sparr: > [most of] the platforms that run maemo have no 3D hardware. You mean: [most of] the platforms that run maemo don't include drivers for their 3D hardware. Till ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 3D Games
[most of] the platforms that run maemo have no 3D hardware. you will need software 3D libraries. I suggest looking at the development communities for the GP2X, an ARM-based gaming handheld, for relevant information on software 3D rendering. On Tue, Sep 30, 2008 at 11:25 AM, Felipe França <[EMAIL PROTECTED]> wrote: > > How could i make 3d games on maemo. > I didn't find none lib 3D ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Problem with Treeview drag and drop
Glade sets the POINTER_MOTION_HINT_MASK by default. With that flag set, GTK produces only one motion-notify event on pointer motion. Pretty much kills DnD. If Nokia had an FAQ, this tip could go in it. It's strange that GTK seems to ignore the mask in an empty treeview. -- Jeffrey Barish ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Integration with hildon desktop
Jun Xu wrote: > To my knowledge, there are many parameters to determine what to show in > the navigator bar. So I guess that you can try the parameters > "StartupWMClass" in your desktop file. To know more info about desktop's > parameters file see: > http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-0.9.4.html > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Barish > Sent: 2008?9?27? 3:52 To: maemo-developers@maemo.org > Subject: Integration with hildon desktop > > After much fiddling, I managed to integrate my application in the hildon > desktop. It appears in the Extras menu along with its logo. I get the > loading message when it's starting, and then it runs. However, when it's > running, I get the default icon in the task navigator bar. Any idea what > I forgot to do? Thanks for the suggestion. I didn't see anything in that document that looked relevant, but perhaps I just missed it. I really don't understand why the Icon parameter isn't responsible for setting the icon in the navigator bar. I wish that Nokia had a document summarizing the steps for integrating an application into the desktop. The required information seems to be buried in many unrelated documents. -- Jeffrey Barish ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
3D Games
How could i make 3d games on maemo. I didn't find none lib 3D _ Cansado de espaço para só 50 fotos? Conheça o Spaces, o site de relacionamentos com até 6,000 fotos! http://www.amigosdomessenger.com.br ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: trouble autobuilding python bindings, configure barfs on python2.5
Thanks for the off-list message. The answer was indeed a missing build-depends section in the control file. owen On Tue, 2008-09-30 at 09:17 -0400, Owen Williams wrote: > I am trying to upload my package to extras, and it keeps failing. While > my application is mostly python, I have to build python-gtkmozembed > support for it. I thought I set up the debian/rules file correctly but > it's failing now. > > The build log is here: > https://garage.maemo.org/builder/diablo/penguintv_3.8-1/armel.build.log.FAILED.txt > > debian/rules runs configure with this line (host and build are > autodetect): > PYTHON=/usr/bin/python2.5 ../../gtkmozembed/configure\ > --host=arm-linux-gnueabi \ > --build=arm-linux-gnueabi \ > --prefix=/usr \ > --with-gtkmozembed=gtkembedmoz > > > and then it bombs here: > > checking whether /usr/bin/python2.5 version >= 2.3... configure: error: too > old > make: *** [configure-stamp] Error 1 > > > which makes no sense. python2.5 is clearly newer than 2.3, but whatever > configure is using to test the version number is failing. Am I doing > something wrong? > > thanks, > Owen Williams ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Running sofsip-cli-0.13 on N800 and N810
Hi all I build sofsip-cli-0.13 for Mameo OS 2008 chinook by passing --with-farsight --with-default-audio=N770 to configure and running it with ./sofsip_cli --media-impl=fsgst on N800 and N810, and able to get DSPPCM audio sink support i am able to make call , but not getting audio :( My installed sofia-sip lib is sofia-sip-1.12.7 did i miss something ? how to test and set the microphone setting of N810 and N800 ? can anyone help me ? Thanks in advanced Minti Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: how long to get from autobuilder to extras-devel?
Perfect, thanks! Frank On Tue, Sep 30, 2008 at 8:58 AM, Niels Breet <[EMAIL PROTECTED]> wrote: > On Tue, September 30, 2008 15:48, Frank Banul wrote: >> Hi, > Hi, > >> >> I got an email last night that my autobuilder upload completed >> successfully. I see the results in >> https://garage.maemo.org/builder/diablo/coverfinder_0.1.1/. How long >> until extras-devel gets populated? >> http://repository.maemo.org/extras-devel/pool/diablo/free/c/coverfinder/ >> > In this case never. You are using an invalid category or section for your > package: "maemo/Applications" > > Please see the Maemo Packaging Policy: > https://maemo.org/forrest-images/pdf/maemo-policy.pdf > > I would suggest user/tools or something like that. > > The fact that it didn't end up in Extras is because you using a capital > letter and the queue-manager bugs on that. But I would suggest you to fix > your section, so your package complies to the policy. > >> >> thanks, Frank > > -- > Niels Breet > maemo.org webmaster > > > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: how long to get from autobuilder to extras-devel?
On Tue, September 30, 2008 15:48, Frank Banul wrote: > Hi, Hi, > > I got an email last night that my autobuilder upload completed > successfully. I see the results in > https://garage.maemo.org/builder/diablo/coverfinder_0.1.1/. How long > until extras-devel gets populated? > http://repository.maemo.org/extras-devel/pool/diablo/free/c/coverfinder/ > In this case never. You are using an invalid category or section for your package: "maemo/Applications" Please see the Maemo Packaging Policy: https://maemo.org/forrest-images/pdf/maemo-policy.pdf I would suggest user/tools or something like that. The fact that it didn't end up in Extras is because you using a capital letter and the queue-manager bugs on that. But I would suggest you to fix your section, so your package complies to the policy. > > thanks, Frank -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
how long to get from autobuilder to extras-devel?
Hi, I got an email last night that my autobuilder upload completed successfully. I see the results in https://garage.maemo.org/builder/diablo/coverfinder_0.1.1/. How long until extras-devel gets populated? http://repository.maemo.org/extras-devel/pool/diablo/free/c/coverfinder/ thanks, Frank ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: trouble autobuilding python bindings, configure barfs on python2.5
Hi Owen, On Tue, September 30, 2008 15:17, Owen Williams wrote: > I am trying to upload my package to extras, and it keeps failing. While > my application is mostly python, I have to build python-gtkmozembed support > for it. I thought I set up the debian/rules file correctly but it's > failing now. > > The build log is here: > https://garage.maemo.org/builder/diablo/penguintv_3.8-1/armel.build.log.FA > ILED.txt > > > debian/rules runs configure with this line (host and build are > autodetect): > PYTHON=/usr/bin/python2.5 ../../gtkmozembed/configure\ > --host=arm-linux-gnueabi \ > --build=arm-linux-gnueabi\ > --prefix=/usr \ > --with-gtkmozembed=gtkembedmoz > > > > and then it bombs here: > > checking whether /usr/bin/python2.5 version >= 2.3... configure: error: > too old make: *** [configure-stamp] Error 1 > > > > which makes no sense. python2.5 is clearly newer than 2.3, but whatever > configure is using to test the version number is failing. Am I doing > something wrong? > Looking at your .changes file, it seems that you haven't specified any Build-Depends. You need to specify everything you need for building your package there, whatever is on available in a clean SDK install. (python2.5 for example) Please see https://wiki.maemo.org/Uploading_to_extras for tips, especially the part about dpkg-depcheck. > thanks, Owen Williams > > -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
trouble autobuilding python bindings, configure barfs on python2.5
I am trying to upload my package to extras, and it keeps failing. While my application is mostly python, I have to build python-gtkmozembed support for it. I thought I set up the debian/rules file correctly but it's failing now. The build log is here: https://garage.maemo.org/builder/diablo/penguintv_3.8-1/armel.build.log.FAILED.txt debian/rules runs configure with this line (host and build are autodetect): PYTHON=/usr/bin/python2.5 ../../gtkmozembed/configure\ --host=arm-linux-gnueabi \ --build=arm-linux-gnueabi \ --prefix=/usr \ --with-gtkmozembed=gtkembedmoz and then it bombs here: checking whether /usr/bin/python2.5 version >= 2.3... configure: error: too old make: *** [configure-stamp] Error 1 which makes no sense. python2.5 is clearly newer than 2.3, but whatever configure is using to test the version number is failing. Am I doing something wrong? thanks, Owen Williams ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
ANN: hop-1.9.0
Hop is a programming language designed for the Web 2.0. It is a higher-order language for programming interactive web applications such as web agendas, web galleries, music players, etc. Hop can be viewed as a replacement for traditional graphical toolkits. HOP is implemented as a Web broker, i.e., a Web server that may act indifferently as a regular Web server or Web proxy. HOP features: * a versatile Web server supporting HTTP/1.0 and HTTP/1.1, * an optimizing native code compiler for server code, * an on-the-fly Javascript compiler for client code, * an extensive set of widgets for programming fancy and portable Web GUIs, * a native multimedia support for enabling ubiquitous Web multimedia applications. * fast WebDAV level 1 support, * an extensive set of libraries for the mail, calendars, databases, Web technologies, ... HOP is available at: http://hop.inria.fr A pre-compiled version for the N8x0 can be found at: ftp://ftp-sop.inria.fr/mimosa/fp/Hop/hop_1.9.0_armel.deb This depends on the Bigloo compiler whose .deb can be found at: ftp://ftp-sop.inria.fr/mimosa/fp/Bigloo/maemo/bigloo_3.1b_armel.deb The release 1.9.0 is a major release. It highlights are: * new linguistic forms (e.g., "comet" server events). * new APIs (e.g., multimedia, cryptography, ...). * new implementations (e.g., new fast Web server scheduling, new support for keep-alive connections, new compilation techniques, ...). Announce of previous Hop release (1.8.6): - The release 1.8.6 is a minor release that fixes minor installation bugs. * Minor bug fixes. Announce of previous Hop release (1.8.5): - The release 1.8.5 is a minor release that fixes minor installation bugs. * It mostly contains fixes that enable packaging Hop is standard Linux distributions. Announce of previous Hop release (1.8.4): - The release 1.8.4 is a minor release that fixes two important problems: 1- Hz timeout was expressed in micro-seconds instead of milli-seconds. Hence, synchronizations and installations where frequently failing because of timeouts. 2 Server events response text was not correct (although the value of server events was). It also adds a new feature to WEBLETS (the weblet in charge of making weblets easily available on Web) which is now able to automatically generate web pages. Announce of previous Hop release (1.8.3): - The release 1.8.3 is a minor release. It mostly fixes small glitches such as: * Eliminate multiple file authentications. * Bad support of inlined resources. * Broken proxy error messages. * ... It also adds a new feature to WEBLETS (the weblet in charge of making weblets easily available on Web) which is now able to automatically generate web pages. Announce of previous Hop release (1.8.0): - 1- A new packaging system (Hz) that allows end users to run and install Hop programs with a single click. 2- Support for MathML (with an extension that allows users to use TeX syntax). 3- Support for SVG (with an extension that allows users to inline SVG external images inside Hop documents). 4- Pre-compiled JVM version is now fully compatible with the native version. Announce of previous Hop release (1.7.0): - 1- Fast WebDAV level 1 support. 2- Various new APIs (such as audio support). 3- Support for fast server events (server-to-client communications). Announce of previous Hop release (1.6.0): - 1- Support for history and bookmarking. 2- MacOS X port (single-threaded). Announce of previous Hop release (1.5.0): - The version 1.5.0 improves the former version 1.4.0 in many directions. The three major improvements are: 1- Support all major browsers (Firefox, Safari, IE7, ...). 2- Add new widgets. 3- Improved authentication mechanisms. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
