On 28 April 2016 at 19:09 Danilo Schöneberg <danilo.schoeneb...@googlemail.com> wrote: > > Moin, > > There is one system left I'm checking out the build for - Linux From > Scratch. I'm building it right now (the system. Not CDE yet). > > I have ten days of vacation coming up, I was thinking about what to do. > I'm completely useless at sitting around idly for more than two days. So I > was thinking about some ideas: > > 1) A CDE-based Live-CD > 2) researching integration of some modern technologies (like automount of > devices, udev, sound systems) > 3) "modernizing" some of the dt apps (mail, text editor, dtlogin) > 4) code cleanup (warnings) > > What would be the preferred option from the team point of view? This also > brings up another question. What is the long-term goal? Do we try to keep > CDE running as it is or are there plans to actively develop it into a next > generation? For instance, I would love to see some more applications > developed (like a really good ftp client, image viewer, perhaps adding some > HTML support to the mail client (either via XmHTML or maybe even webkit). > All based on Motif of course. It has all a UI needs. It may look a bit > dated, but I love it, much more than all the new-fangled stuff that blinks, > beeps and dances, but gobbles up resources. > > One thing I noticed on my old Compaq nx8220, running NetBSD: CDE makes > other DE's that were deliberately designed to be lightweight (LXDE, LXQT) > look positively bloated and sluggish. It could really be an alternative on > low-end systems. > > Cheers, > Hippo >
My opinion, for what it's worth, is that I'd like to see the priority on code cleanups with new features only added at this stage if they can be done in a "clean" way. For example, where there are well defined boundaries in the code that would allow something like XmHTML to be integrated into the mail client with minimal hooks into the mail client code itself. There's still a lot of inelegant code in CDE that could do with clean up and encapsulating. For example, I tried to turn the ISAM code into a well encapsulated library with a clear API. I spent roughly twenty to thirty hours on it, but ran out of time and junked my progress. I would have liked to have completed this and added some tests that would amount to a unit test suite. It was hard work, since there is quite a lot of dependencies between code across the whole of CDE that should be much more independent. Adding some kind of automated support for Coverity would be a cool addition as well. It's provided excellent information for projects like NetBSD. Ultimately though, this is an open source project and I'm sure any well written changes will be gratefully received, regardless of whether they are cleanups or new features :-) Chris ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
