That's good information, but it does nothing to answer the question that I asked. If current EeePC come with Windows rather than the Xandros that the original models came with, presumably they have the Windows interface rather than the one that lxlauncher was built to resemble. Is that true? And if it is, the lxlauncher customer base will dwindle to nothing.
On 04/14/2010 07:25 AM, PCMan wrote: > It's mainly for users of netbooks, such as EeePC. The UI resembles the > one of EeePC a lot for easy conversion. > The current feature branch contains totally re-designed infrastructure > and master branch only contains out-dated code. > I haven't merge the branch to master due to a lot of conflicts in > translations. Anyone knows how to solve this cleanly? > It's time to merge it to master for further development. > > On Wed, Apr 14, 2010 at 6:37 PM, Marty Jack <[email protected]> wrote: >> I agree with the idea that the packages should be kept on independent >> schedules where possible. >> >> I do not have a good sense for how many people are using lxlauncher. I do >> not know a lot about the history here, but I notice that eee are now coming >> with Windows, so I would assume that the interface that lxlauncher supports >> is trending toward only being of historic interest. Can someone shed light >> on this? >> >> On 04/14/2010 06:22 AM, Christoph Wickert wrote: >>> Am Mittwoch, den 14.04.2010, 18:06 +0800 schrieb Andrew Lee: >>>> Hi, >>>> >>>> Since menu-cache 0.3 series are already released for long. Should we >>>> freeze the strings in lxlauncher and make new release on lxlauncher to >>>> support 0.3 series soon? >>> >>> Yes please. We should at least make an updated release because the fixes >>> are only available in GIT. >>> >>> IMO there is no need to do complete releases of LXDE, I'm afraid this >>> will slow down development too much. But we need to release dependent >>> packages together, e.g. menu-cache, lxpanel and lxlauncher just as we >>> release libfm together with pcmanfm. >>> >>> Regards, >>> Christoph >>> >>> >>> ------------------------------------------------------------------------------ >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> Lxde-list mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/lxde-list >>> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Lxde-list mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/lxde-list >> > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
