Merging the runner and the panel into a single process makes sense and, if the people who actually maintain things don't see a problem with it, it sounds like an easy way to save ~5mb resident. In fact, that's how LXDE already does it. (Run Dialog = lxpanelctl run)
However, I don't see how you expect to save RAM beyond that. Every time you add something new to your lxde-core process, the potential harm caused by a bug goes up sharply because a bug in one component is no longer confined to that component. (If you remember pre-OSX MacOS or Windows 3.x and Windows 95, think about how common the restart-forcing bomb dialogs and blue screens were.) I'm not sure there's a way to justify that risk for more than just the panel, the runner, and various tray applets since most of the other components of a desktop tend to be things that: - cause the whole desktop to logout if they crash (lxsession) - have a history of crash bugs that are tricky to reproduce (PCManFM) - could cause data loss if they crash (lxterminal) - are used infrequently enough that they shouldn't be resident if you want to save RAM. (lxtask,lxappearance,lxinput,lxshortcut,lxrandr,lxkeymap) ...and I doubt it'd save RAM to have the panel also handle desktop icons since the only mature, lightweight desktop icon implementation I've ever found is the PCManFM one which already shares a process with file manager windows. Heck, even tray icons aren't without their gotchas in the event of a crash. Audacious Media Player, neap, and oDesk Team remain running but lose their tray icons when lxpanel crashes because lxpanel is apparently the only panel implementation that actually trusted that application developers would listen to "applications shouldn't expect the panel to recover icons after a restart" in the spec. On 13-09-09 03:28 PM, Alexis López Zubieta wrote: > Hello: > > I want to share with you an experiment that I have done. I have created > an application to load pluggings. Then I compiled the razorqt-panel and > the razorqt-runner as plugins for this application, adding only the > plugging interface. When the application runs with the two pluggings > loaded it consume less memory (about 5mb less) than the the > razorqt-panel and the razorqt-runner running alone. I suspect that this > reduction is produce by the elimination of a QTApplication instance and > the memory associated to each linux process. > > This could be a way to reduce the memory consumption of the new LXQT > desktop environment. > So please take a look into it. I will be working on it in order to make > some other improvements. > > You can download the source code from: > https://github.com/azubieta/lxqt-core.git > You can also take a look to https://github.com/azubieta/lxqt-core/wiki > > In order to build the application: > - get the source code > - install razorqt > - build the application > - Unpack the razor-qt-master.tar.gz file with my modifications of razorqt. > - build that version of razorqt > - finally run the lxqt-core application. > > Best wishes > > Alexis López Zubieta > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk > ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
