From: PCMan <pcm...@gm...> - 2012-11-24 18:46:35
|
Here are some news about lxpanel2. I just finished multi-screen / multi-monitor support. One can have different panels on different monitors. Besides, one can also have multiple panels on the same side. Positioning and sizing of the panels also becomes more flexible. The latest code in the online git repo is in a much better shape now. http://lxde.git.sourceforge.net/git/gitweb.cgi?p=lxde/lxpanel2;a=summary Currently you have to edit the config file manually. Later I'll finish GUI configuration dialogs. What's lacking now are good applets. Cheers! |
From: PCMan <pcm...@gm...> - 2013-02-10 10:38:29
|
Hello, Happy Chinese New Year! While the original lxpanel got a new maintainer, I'm still working on lxpanel2 as an experimental project. Here is a list of recent changes: 1. Multi-monitor support is done. You can put panels on different monitors. 2. Multiple panel support is almost done. You can have any number of panels, not just four. That means, you can have several panels on the same side of the screen if you want. 3. Sizing and positioning of panels have been reworked. Layout of panels became very flexible and can be easily configured via the preference dialog. Try it now! 4. The preference dialog is now 75% completed. It's Gnome HIG compliant and more user-friendly than the old lxpanel preference dialog. 5. The plugin system is redesigned. I'm going to port existing applets soon. Some problems that are not solved: 1. I really hate gtk+!! In gtk+ 3, the way it allocate sizes for widgets differs greatly from gtk2 and is not backward compatible. So every program using gtk_widget_set_size_request() API stop working and requires redesign. The API no longer works. Some widgets now use width-for-height/height-for-width, and others use get_preferred_width()/get_preferred_height(). It's hard to get them right. Some old applets need to be reworked to overcome the incompatibilities. 2. In old lxpanel, icons wrap automatically when there is enough height. I'd like to do that in lxpanel2 initially, but I'm not sure if this is the best way. So all the applets only support single row at the moment. 3. There is no good way to save config file. Normally, we write the config file on program termination. However, when logging out a desktop session, the panel is KILLed via SIGKILL, not SIGTERM in some window managers. That means, we don't have a chance to write the config file to disk. It's a old problem existed in lxpanel. I want to solve it in lxpanel2, but I haven't figure out a better way. Writing the whole config file everytime a tiny config value is changed is insane, but it's the only reliable way to get every config value correctly written to disk. :-( Anyway, please test the new code if you're interested. git://lxde.git.sourceforge.net/gitroot/lxde/lxpanel2 Cheers! |
From: Tomas F. <tfo...@fo...> - 2013-02-10 12:05:47
|
02/10/2013 11:38 AM, PCMan skrev: > Hello, > Happy Chinese New Year! > While the original lxpanel got a new maintainer, > I'm still working on lxpanel2 as an experimental project. > > Here is a list of recent changes: > > 1. Multi-monitor support is done. You can put panels on different monitors. > > 2. Multiple panel support is almost done. You can have any number of > panels, not just four. That means, you can have several panels on the > same side of the screen if you want. > > 3. Sizing and positioning of panels have been reworked. Layout of > panels became very flexible and can be easily configured via the > preference dialog. Try it now! > > 4. The preference dialog is now 75% completed. It's Gnome HIG > compliant and more user-friendly than the old lxpanel preference > dialog. > > 5. The plugin system is redesigned. I'm going to port existing applets soon. > > Some problems that are not solved: > > 1. I really hate gtk+!! > In gtk+ 3, the way it allocate sizes for widgets differs greatly from > gtk2 and is not backward compatible. > So every program using gtk_widget_set_size_request() API stop working > and requires redesign. The API no longer works. > Some widgets now use width-for-height/height-for-width, and others > use get_preferred_width()/get_preferred_height(). > It's hard to get them right. Some old applets need to be reworked to > overcome the incompatibilities. > > 2. In old lxpanel, icons wrap automatically when there is enough > height. I'd like to do that in lxpanel2 initially, but I'm not sure if > this is the best way. So all the applets only support single row at > the moment. > > 3. There is no good way to save config file. Normally, we write the > config file on program termination. However, when logging out a > desktop session, the panel is KILLed via SIGKILL, not SIGTERM in some > window managers. That means, we don't have a chance to write the > config file to disk. It's a old problem existed in lxpanel. I want to > solve it in lxpanel2, but I haven't figure out a better way. Writing > the whole config file everytime a tiny config value is changed is > insane, but it's the only reliable way to get every config value > correctly written to disk. :-( > > Anyway, please test the new code if you're interested. > git://lxde.git.sourceforge.net/gitroot/lxde/lxpanel2 > > Cheers! > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list Hello, Possible to fix autogen.sh to work with later automake? Getting error: You must have automake > 1.10 or 1.11 installed to compile this program. Install the appropriate package for your distribution, 1.12 and 1.13 has released. (in meantime, fixing it locally) // Tomas Forsman |
From: Julien L. <gi...@ub...> - 2013-02-10 13:36:25
|
2013/2/10 PCMan <pcm...@gm...>: > 3. There is no good way to save config file. Normally, we write the > config file on program termination. However, when logging out a > desktop session, the panel is KILLed via SIGKILL, not SIGTERM in some > window managers. That means, we don't have a chance to write the > config file to disk. It's a old problem existed in lxpanel. I want to > solve it in lxpanel2, but I haven't figure out a better way. Writing > the whole config file everytime a tiny config value is changed is > insane, but it's the only reliable way to get every config value > correctly written to disk. :-( Using GSettings may help you here ? You can split the setttings and only modify the ones which actually change. Since GSettings is included in Glib, it will not bring more external dependency. Regards, Julien Lavergne |
From: Jonathan N. <j.n...@ch...> - 2013-02-10 14:27:15
|
Thanks for your work on lxpanel2! It looks like you are really making a lot of progress. I'm a blind GNU/Linux user and I have a GNU/Linux distro called sonar using the LXDE desktop. it is located here. http://www.sonar-project.org The one problem I'm having with my distro is the lxpanel is not accessible and pcmanfm is not accessible. For now I had to use the gnome-panel and nautilus for the file manager. It would be great if accessibility could be considered in the development of lxpanel2. Thanks for all of your work and time. On 02/10/2013 06:24 AM, Tomas Forsman wrote: > > 02/10/2013 11:38 AM, PCMan skrev: >> Hello, >> Happy Chinese New Year! >> While the original lxpanel got a new maintainer, >> I'm still working on lxpanel2 as an experimental project. >> >> Here is a list of recent changes: >> >> 1. Multi-monitor support is done. You can put panels on different monitors. >> >> 2. Multiple panel support is almost done. You can have any number of >> panels, not just four. That means, you can have several panels on the >> same side of the screen if you want. >> >> 3. Sizing and positioning of panels have been reworked. Layout of >> panels became very flexible and can be easily configured via the >> preference dialog. Try it now! >> >> 4. The preference dialog is now 75% completed. It's Gnome HIG >> compliant and more user-friendly than the old lxpanel preference >> dialog. >> >> 5. The plugin system is redesigned. I'm going to port existing applets soon. >> >> Some problems that are not solved: >> >> 1. I really hate gtk+!! >> In gtk+ 3, the way it allocate sizes for widgets differs greatly from >> gtk2 and is not backward compatible. >> So every program using gtk_widget_set_size_request() API stop working >> and requires redesign. The API no longer works. >> Some widgets now use width-for-height/height-for-width, and others >> use get_preferred_width()/get_preferred_height(). >> It's hard to get them right. Some old applets need to be reworked to >> overcome the incompatibilities. >> >> 2. In old lxpanel, icons wrap automatically when there is enough >> height. I'd like to do that in lxpanel2 initially, but I'm not sure if >> this is the best way. So all the applets only support single row at >> the moment. >> >> 3. There is no good way to save config file. Normally, we write the >> config file on program termination. However, when logging out a >> desktop session, the panel is KILLed via SIGKILL, not SIGTERM in some >> window managers. That means, we don't have a chance to write the >> config file to disk. It's a old problem existed in lxpanel. I want to >> solve it in lxpanel2, but I haven't figure out a better way. Writing >> the whole config file everytime a tiny config value is changed is >> insane, but it's the only reliable way to get every config value >> correctly written to disk. :-( >> >> Anyway, please test the new code if you're interested. >> git://lxde.git.sourceforge.net/gitroot/lxde/lxpanel2 >> >> Cheers! >> >> ------------------------------------------------------------------------------ >> Free Next-Gen Firewall Hardware Offer >> Buy your Sophos next-gen firewall before the end March 2013 >> and get the hardware for free! Learn more. >> http://p.sf.net/sfu/sophos-d2d-feb >> _______________________________________________ >> Lxde-list mailing list >> Lxd...@li... >> https://lists.sourceforge.net/lists/listinfo/lxde-list > > Hello, > > Possible to fix autogen.sh to work with later automake? > Getting error: > You must have automake > 1.10 or 1.11 installed to compile this program. > Install the appropriate package for your distribution, > > 1.12 and 1.13 has released. (in meantime, fixing it locally) > > // Tomas Forsman > > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > > > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list |
From: David T. <dth...@wo...> - 2013-02-10 15:06:46
|
On 02/10/2013 09:27 AM, Jonathan Nadeau wrote: > Thanks for your work on lxpanel2! It looks like you are really making > a lot of progress. I'm a blind GNU/Linux user and I have a GNU/Linux > distro called sonar using the LXDE desktop. it is located here. > > http://www.sonar-project.org > > The one problem I'm having with my distro is the lxpanel is not > accessible and pcmanfm is not accessible. For now I had to use the > gnome-panel and nautilus for the file manager. It would be great if > accessibility could be considered in the development of lxpanel2. > Thanks for all of your work and time. > I would be interested in helping make lxpanel2 more accessible. I haven't made any contributions to lxpanel before, so I might need a bit of help getting started. |
From: Stephan S. <gma...@sp...> - 2013-02-10 16:25:57
|
Have you considered using a timeout to write changes 5 minutes after last modification in addition to on SIGTERM and SIGHUP? I've found that's usually a good way to deal with unexpected program death without saving too often or explicitly asking the user when to save. On 13-02-10 05:38 AM, PCMan wrote: > > 3. There is no good way to save config file. Normally, we write the > config file on program termination. However, when logging out a > desktop session, the panel is KILLed via SIGKILL, not SIGTERM in some > window managers. That means, we don't have a chance to write the > config file to disk. It's a old problem existed in lxpanel. I want to > solve it in lxpanel2, but I haven't figure out a better way. Writing > the whole config file everytime a tiny config value is changed is > insane, but it's the only reliable way to get every config value > correctly written to disk. :-( > |
From: Andrej N. G. <an...@re...> - 2013-02-10 17:26:48
|
Hello! Jonathan Nadeau has written on Sunday, 10 February, at 9:27: >The one problem I'm having with my distro is the lxpanel is not >accessible and pcmanfm is not accessible. The pcmanfm will be accessible in version 1.2. Part of this work is already done and some other work will be done later. I'm sorry for some delays with continuation of pcmanfm development but I hope to continue to work on it shortly. With best wishes. Andriy. |
From: Jonathan N. <j.n...@ch...> - 2013-02-10 18:36:43
|
That is fantastic! thank you for all your work on this! This is extremely important and awesome that you are doing this work. On behalf of the blind community I thank you sir. On 02/10/2013 12:26 PM, Andrej N. Gritsenko wrote: > Hello! > > Jonathan Nadeau has written on Sunday, 10 February, at 9:27: >> The one problem I'm having with my distro is the lxpanel is not >> accessible and pcmanfm is not accessible. > The pcmanfm will be accessible in version 1.2. Part of this work is > already done and some other work will be done later. I'm sorry for some > delays with continuation of pcmanfm development but I hope to continue to > work on it shortly. > > With best wishes. > Andriy. > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list |
From: nomnex <no...@gm...> - 2013-02-11 00:03:04
|
> On Sun, 10 Feb 2013 18:38:23 +0800 > PCMan <pcm...@gm...> wrote: > > Happy Chinese New Year! Happy Chinese new year to you, and thank you for this good news. > While the original lxpanel got a new maintainer, Any info it there will be a bug fix about the freeze issue on the current lxpanel, see https://bugzilla.redhat.com/show_bug.cgi?id=587430 and http://sourceforge.net/tracker/index.php?func=detail&aid=3030538&group_id=180858&atid=894869 Until lxpanel2 is released. --nomnex -- nomnex <no...@gm...> Freenode: nomnex Registered Linux user #505281. Be counted at: http://linuxcounter.net |
From: Henry G. <hsg...@gm...> - 2013-02-11 02:43:47
|
On Mon, Feb 11, 2013 at 09:02:51AM +0900, nomnex wrote: > Any info it there will be a bug fix about the freeze issue on the > current lxpanel, see https://bugzilla.redhat.com/show_bug.cgi?id=587430 > and > http://sourceforge.net/tracker/index.php?func=detail&aid=3030538&group_id=180858&atid=894869 Thanks for making me aware of the problem. Can you give a more detailed way of reproducing this? Does lxpanel crash/freeze every time you close pidgin, or only sometimes? Cheers, Henry |
From: Bengt F. <ben...@gm...> - 2013-02-11 06:18:58
|
Great News!!! :D [See also Debian Testing/"Unstable" (now on this platform) bugreport - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699414] 2013/2/11 Henry Gebhardt <hsg...@gm...> > On Mon, Feb 11, 2013 at 09:02:51AM +0900, nomnex wrote: > > Any info it there will be a bug fix about the freeze issue on the > > current lxpanel, see https://bugzilla.redhat.com/show_bug.cgi?id=587430 > > and > > > http://sourceforge.net/tracker/index.php?func=detail&aid=3030538&group_id=180858&atid=894869 > > Thanks for making me aware of the problem. Can you give a more detailed > way of reproducing this? Does lxpanel crash/freeze every time you close > pidgin, or only sometimes? > > > Cheers, > Henry > > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list > |
From: Christoph W. <chr...@gm...> - 2013-02-11 09:07:19
|
Am Sonntag, den 10.02.2013, 21:41 -0500 schrieb Henry Gebhardt: > On Mon, Feb 11, 2013 at 09:02:51AM +0900, nomnex wrote: > > Any info it there will be a bug fix about the freeze issue on the > > current lxpanel, see https://bugzilla.redhat.com/show_bug.cgi?id=587430 > > and > > http://sourceforge.net/tracker/index.php?func=detail&aid=3030538&group_id=180858&atid=894869 > > Thanks for making me aware of the problem. Can you give a more detailed > way of reproducing this? Does lxpanel crash/freeze every time you close > pidgin, or only sometimes? Only sometimes. It's not limited to Pidgin. Given the number of crash reports I receive, this is one of the most common crashes in Fedora and it's around for years. I reported it upstream already, but so far nothing has happened. Thanks for looking into it now. Kind regards, Christoph |
From: nomnex <no...@gm...> - 2013-02-11 14:06:30
|
> On Mon, 11 Feb 2013 10:07:08 +0100 > Christoph Wickert <chr...@gm...> wrote: > > Am Sonntag, den 10.02.2013, 21:41 -0500 schrieb Henry Gebhardt: > > On Mon, Feb 11, 2013 at 09:02:51AM +0900, nomnex wrote: > > > Any info it there will be a bug fix about the freeze issue on the > > > current lxpanel, see > > > https://bugzilla.redhat.com/show_bug.cgi?id=587430 and > > > http://sourceforge.net/tracker/index.php?func=detail&aid=3030538&group_id=180858&atid=894869 > > > > Thanks for making me aware of the problem. Can you give a more > > detailed way of reproducing this? Does lxpanel crash/freeze every > > time you close pidgin, or only sometimes? > > Only sometimes. It's not limited to Pidgin. Given the number of crash > reports I receive, this is one of the most common crashes in Fedora > and it's around for years. I reported it upstream already, but so far > nothing has happened. Thanks for looking into it now. > > Kind regards, > Christoph > Hello Gebhardt, To echo Christoph's feedback, LibreOffice and Firefox were Freezing the LXPanel for me. Firefox: anytime I opened several tabs and closed one of them. LO, same pattern. We already had a talk about it, some time ago, after Marty had left and the LXPanel had no maintainer. I copy our last message about the issue. Thanks again for looking into it. --nomnex --- From: Henry Gebhardt <hsg...@go...> To: nomnex <no...@gm...> Subject: Re: [Lxde-list] lxpanel keeps crashing with Libre Office Date: Tue, 31 Jan 2012 03:53:19 +0100 User-Agent: Mutt/1.5.21 (2010-09-15) On Tue, Jan 31, 2012 at 08:39:59AM +0900, nomnex wrote: > > Hello again Henry, I answer the thread chronologically. My time is JST > (+9), and I can answer my email on the morning only, after it gets too > busy. No problem. > > > On Sun, 29 Jan 2012 15:41:14 +0100 > > Henry Gebhardt <hsg...@go...> wrote: > > Assuming you have no other libreoffice writer windows open, does the > > bug trigger when you open two documents in libreoffice writer, and > > then close them in the same order they were opened? > > The lxpanel freezes constantly, but it is always random and I can't > reproduce the freeze on demand[1]. Effectively, closing Libreoffice > tabs seems to be the trigger. The panel does not freeze when when a > single document is opened. Yeah, it seems like it is important that at least two instances of the same application are opened, and it triggers when closing. When you say libreoffice, are you referring to the writer, or calc, or a different one? For the bug to trigger, I think it must be two of the same kind. > > Klaus and yourself have replied to my direct email address. I am not > sure if I should reply you in return directly, or on the list? Usually on lists you should reply directly and cc the list and everyone else involved in the discussion. That way someone who is not subscribed can also participate in a thread of discussion. I will not get your emails twice, because the mailing list server usually detects that you have emailed me personally, too, and doesn't send another copy to me. That being said, I am actually not sure how this list handles that. I should check. But I am pretty sure it does it that way. > > I copy below the answer I made to Klaus about the issue: > > --- [start] --- > [Klaus] > > Relating to your suggestion that the lxpanel crash is "hardware > > related": Maybe it matters how much RAM your computer has, but I > > think it's really a bug in the program itself if it crashes. > > [nomnex] > From my experience (not my expertise), some hardware configuration > trigger the bug, and some do not. For information, my PC has 1 GB of > RAM, lxpanel crashes >10 times a day, randomly, either when I close a > few LibreOffice tabs, either when I download a file using Firefox. > > I use LyX, Texmaker, & Gimp, Inkscape (more ram intensive) on the > same machine and not a single crash occur. My second notebook is an > older Intel 855 gpu, with 512 RAM, and I have never experienced a > single panel freeze using the same software. > > Anyway, without debugging information, the above is not relevant. > --- [end] --- > > I am not good technically, but if I can help providing relevant > information, I will do my best. Don't hesitated to ask me. > > Thanks again, > Marc > > [1] I will -- try -- to close the LO tab in the same order I open > them, to see if it trigger the bug or not, these coming days (I say > try, because I use writer to take my study notes, and I get rapidly > overwhelmed along the day). I get back to you in a day or two. Thanks, that would be great! Henry -- nomnex <no...@gm...> Freenode: nomnex Registered Linux user #505281. Be counted at: http://linuxcounter.net |
From: Henry G. <hsg...@gm...> - 2013-02-11 21:12:35
|
On Mon, Feb 11, 2013 at 07:18:50AM +0100, Bengt Frost wrote: > Great News!!! :D > [See also Debian Testing/"Unstable" (now on this platform) bugreport - > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699414] Thanks for the report. I am aware of the problem. I hope I will have time to investigate this soonish, but since it isn't critical, I can't promise. Cheers, Henry |
From: Bengt F. <ben...@gm...> - 2013-02-12 06:21:15
|
On Mon, Feb 11, 2013 at 04:10:42PM -0500, Henry Gebhardt wrote: > On Mon, Feb 11, 2013 at 07:18:50AM +0100, Bengt Frost wrote: > > Great News!!! :D > > [See also Debian Testing/"Unstable" (now on this platform) bugreport - > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699414] > > Thanks for the report. I am aware of the problem. I hope I will have time > to investigate this soonish, but since it isn't critical, I can't promise. > > > Cheers, > Henry No hurry - just a stylish 'matter', just refresh lxpanel/pager and the problem goes away... :) Cheers, Bengt |
From: Henry G. <hsg...@gm...> - 2013-02-11 21:42:00
|
On Mon, Feb 11, 2013 at 11:06:18PM +0900, nomnex wrote: > > On Mon, 11 Feb 2013 10:07:08 +0100 > > Christoph Wickert <chr...@gm...> wrote: > > > > Am Sonntag, den 10.02.2013, 21:41 -0500 schrieb Henry Gebhardt: > > > On Mon, Feb 11, 2013 at 09:02:51AM +0900, nomnex wrote: > > > > Any info it there will be a bug fix about the freeze issue on the > > > > current lxpanel, see > > > > https://bugzilla.redhat.com/show_bug.cgi?id=587430 and > > > > http://sourceforge.net/tracker/index.php?func=detail&aid=3030538&group_id=180858&atid=894869 > > > > > > Thanks for making me aware of the problem. Can you give a more > > > detailed way of reproducing this? Does lxpanel crash/freeze every > > > time you close pidgin, or only sometimes? > > > > Only sometimes. It's not limited to Pidgin. Given the number of crash > > reports I receive, this is one of the most common crashes in Fedora > > and it's around for years. I reported it upstream already, but so far > > nothing has happened. Thanks for looking into it now. > > > > Kind regards, > > Christoph > > > > Hello Gebhardt, > > To echo Christoph's feedback, LibreOffice and Firefox > were Freezing the LXPanel for me. Firefox: anytime I opened several > tabs and closed one of them. LO, same pattern. We already had a talk > about it, some time ago, after Marty had left and the LXPanel had no > maintainer. I copy our last message about the issue. I think this particular one is already fixed, see commits 0.5.8-105-g0c1fb08 and 0.5.10-86-g3a02bd0. On second thought, that last commit might even fix the current issue. Can someone check this with lxpanel-0.5.12? Thanks, Henry |
From: Christoph W. <chr...@gm...> - 2013-02-12 20:01:37
|
Am Montag, den 11.02.2013, 16:40 -0500 schrieb Henry Gebhardt: > On Mon, Feb 11, 2013 at 11:06:18PM +0900, nomnex wrote: > > > Hello Gebhardt, > > > > To echo Christoph's feedback, LibreOffice and Firefox > > were Freezing the LXPanel for me. Firefox: anytime I opened several > > tabs and closed one of them. LO, same pattern. We already had a talk > > about it, some time ago, after Marty had left and the LXPanel had no > > maintainer. I copy our last message about the issue. > > I think this particular one is already fixed, see commits > 0.5.8-105-g0c1fb08 and 0.5.10-86-g3a02bd0. Hi Henry, mind explaining this notation? I finally found the commit, but I would just call it 3a02bd07. What about 83d410c1, is it only clean-up or related? I wonder if it would fix https://bugzilla.redhat.com/show_bug.cgi?id=837379 - do you think it's worth cherry-picking it? > On second thought, that last commit might even fix the current issue. > Can someone check this with lxpanel-0.5.12? Let's see. I have issued two updates for Fedora https://admin.fedoraproject.org/updates/lxpanel-0.5.12-1.fc18 https://admin.fedoraproject.org/updates/lxpanel-0.5.12-1.fc17 Feedback welcome! Kind regards, Christoph |
From: Henry G. <hsg...@gm...> - 2013-02-12 23:11:31
|
On Tue, Feb 12, 2013 at 09:01:25PM +0100, Christoph Wickert wrote: > Am Montag, den 11.02.2013, 16:40 -0500 schrieb Henry Gebhardt: > > On Mon, Feb 11, 2013 at 11:06:18PM +0900, nomnex wrote: > > > To echo Christoph's feedback, LibreOffice and Firefox > > > were Freezing the LXPanel for me. Firefox: anytime I opened several > > > tabs and closed one of them. LO, same pattern. We already had a talk > > > about it, some time ago, after Marty had left and the LXPanel had no > > > maintainer. I copy our last message about the issue. > > > > I think this particular one is already fixed, see commits > > 0.5.8-105-g0c1fb08 and 0.5.10-86-g3a02bd0. > > mind explaining this notation? I finally found the commit, but I would > just call it 3a02bd07. It is what "git describe <commitid>" gave me. The format is <tag>-<number_of_commits_since_tag>-g<hash>. According to the man page, the 'g' infront of the hash stands for 'git'. > > What about 83d410c1, is it only clean-up or related? I wonder if it > would fix https://bugzilla.redhat.com/show_bug.cgi?id=837379 - do you > think it's worth cherry-picking it? No. It doesn't actually do anything. I was changing something in there the other day, and finally decided to commit only the cleanup. I wouldn't include it in any bugfix release. The bug looks a lot like another duplicate of the taskbar crash, since it seems to originiate in the flash_window_timeout() function. > > > On second thought, that last commit might even fix the current issue. > > Can someone check this with lxpanel-0.5.12? > > Let's see. I have issued two updates for Fedora > https://admin.fedoraproject.org/updates/lxpanel-0.5.12-1.fc18 > https://admin.fedoraproject.org/updates/lxpanel-0.5.12-1.fc17 > > Feedback welcome! Regards, Henry |
From: Henry G. <hsg...@gm...> - 2012-11-24 19:01:53
|
On Sun, Nov 25, 2012 at 02:46:26AM +0800, PCMan wrote: > Here are some news about lxpanel2. Cool. I need my usual automake-1.12 patch for autogen.sh. Should I make one? I think almost all LXDE packages are affected. So my question: Do we really need that version check in autogen.sh? Is there a better solution like using "autoreconf -i"? Thanks, Henry |
From: Giuseppe P. <gi...@gm...> - 2012-11-24 19:39:45
|
Hi, What's lacking now are good applets. > can you list what applets need to be ported? It would be also good if guys taking care of porting an applet would write it here. I would like also to take care of porting of a couple of applets. Could you give some more help on what changes generally are needed to the applets to port them? Cheers, Giuseppe. |
From: Andrej N. G. <an...@re...> - 2012-11-24 20:03:08
|
Hello! Giuseppe Penone has written on Saturday, 24 November, at 20:39: >can you list what applets need to be ported? I'm afraid they should be not ported but written from scratch on VALA since almost whole lxpanel2 is written on VALA. :) >It would be also good if guys taking care of porting an applet would write >it here. I don't know how to write on VALA and I'm afraid VALA code cannot be debugged at all so I cannot help in that, I'm sorry. But I like to have transparency without using any Compiz or another slow stuff, I really like Openbox and I like the transparency I have with lxpanel. So I'm not user of lxpanel2, I'm sorry. :) With best wishes. Andriy. |
From: Giuseppe P. <gi...@gm...> - 2012-11-24 21:12:06
|
Hi, On Sat, Nov 24, 2012 at 9:03 PM, Andrej N. Gritsenko <an...@re...>wrote: > I'm afraid they should be not ported but written from scratch on VALA > since almost whole lxpanel2 is written on VALA. :) > AFAIK most of the open source developers out there use C and C++, so since the lxpanel requires a good number of volunteers/open source developers to add their applets I'm not sure VALA is the good choice... > I don't know how to write on VALA and I'm afraid VALA code cannot be > debugged at all so I cannot help in that, I'm sorry. > Personally I could also look at VALA but seems to me that there's not a good reference + complete tutorial like gtk and gtkmm have. I don't understand why VALA code cannot be debugged anyway... you mean there's the lack of tools such as nemiver in VALA? Cheers, Giuseppe. |
From: Michael R. <mic...@ub...> - 2012-11-24 21:43:45
|
On 24/11/12 21:12, Giuseppe Penone wrote: > Hi, > > On Sat, Nov 24, 2012 at 9:03 PM, Andrej N. Gritsenko > <an...@re... <mailto:an...@re...>> wrote: > > I'm afraid they should be not ported but written from scratch on VALA > since almost whole lxpanel2 is written on VALA. :) > > > AFAIK most of the open source developers out there use C and C++, > so since the lxpanel requires a good number of volunteers/open source > developers > to add their applets I'm not sure VALA is the good choice... > > I don't know how to write on VALA and I'm afraid VALA code cannot be > debugged at all so I cannot help in that, I'm sorry. > > > Personally I could also look at VALA but seems to me that there's not a > good reference + complete tutorial like gtk and gtkmm have. > > I don't understand why VALA code cannot be debugged anyway... you mean > there's the lack of tools such as nemiver in VALA? > > Cheers, > Giuseppe. > > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > > > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list Personally, I was turned off contributing to this by the language choice. I fail to see how it was better than C. But that's just me. Vala code is first "compiled" to C + GLib, which makes the binaries hell to debug, if you can at all. I have been having a stab at my own (mostly for fun), just about got to the stage where it can load its own configuration file, set window hints, and load plugins. Anyway, good luck with it, contributors! Michael |
From: Andrej N. G. <an...@re...> - 2012-11-24 22:02:50
|
Hello! Giuseppe Penone has written on Saturday, 24 November, at 22:12: >On Sat, Nov 24, 2012 at 9:03 PM, Andrej N. Gritsenko <an...@re...>wrote: >> I'm afraid they should be not ported but written from scratch on VALA >> since almost whole lxpanel2 is written on VALA. :) >AFAIK most of the open source developers out there use C and C++, >so since the lxpanel requires a good number of volunteers/open source >developers >to add their applets I'm not sure VALA is the good choice... I should admit, VALA code is simpler than pure C due to built-in GTK classes handling. But I still don't trust it as VALA code is only part of libfm which generates a lot of warnings still, rest of code is written in C and is free of warnings, with all relevant warnings enabled. And lxpanel2 requires pretty new version of VALA, released this year, you cannot compile it on any older system. >> I don't know how to write on VALA and I'm afraid VALA code cannot be >> debugged at all so I cannot help in that, I'm sorry. >Personally I could also look at VALA but seems to me that there's not a >good reference + complete tutorial like gtk and gtkmm have. >I don't understand why VALA code cannot be debugged anyway... you mean >there's the lack of tools such as nemiver in VALA? I was overreacted about "cannot be debugged", I'm sorry. VALA doesn't generate binary code, it generates C code, like this: g_return_val_if_fail (_tmp18_ <= _tmp19_, NULL); _tmp20_ = start; _tmp21_ = end; _tmp22_ = start; _tmp23_ = g_strndup (((gchar*) self) + _tmp20_, (gsize) (_tmp21_ - _tmp22_)); result = _tmp23_; There is a lot of variables and all variables have names _tmpXXX and after compiler optimizations it is pretty inconvenient to debug. In any case you will have something under gdb, yes, but you rarely will get all the data and you have to find relevant vala code by hands. I hope PCMan can tell us more on the subject. Cheers! Andriy. |