Of course those dependencies are already on the long term goal list, because the long term goal is compatibility with Cocoa. We need to walk before we can run. Right now we don't have a consistent, usable desktop environment. That needs to be a goal before we start trying to go for 100% OSX API compatibility, otherwise in 5 years time, we are going to be back here, posting about how we still don't have a browser, or enough programmers to maintain one, and still can't use GNUstep as a desktop, while GTK4 and QT6 have thousands of programmers hacking on them.
I think most people here can agree that GNUstep hasn't exactly taken off into the stratosphere despite the rise of OSX and interest in the languages/APIs used. I seriously think the first step to that goal is getting people using GNUstep every day. That means a desktop, whether it's on BSD/HURD/Linux/Darwin/NEXT clone kernel. From a desktop perspective, I want to listen to music, watch movies, hack in a tabbed terminal (I use a 4k monitor but still multiple terminal windows is crazy.) use a wysiwyg gui designer, have IRC, and use a web browser. Cynthiune.app, GSMplayer (needs a little love but mostly there), Terminal.app, Talksoup.app, Gorm.app, and now Gregory's project, makes a working desktop environment. Network/Sound gui's would be nice, but to be honest I can get by with network-manager's CLI and with alsamixer. The dream would be for the Etoile Apple style menubar volume control app to be updated to pulseaudio, and have SystemPreferences.app applets for Network-Manager, Pulseaudio, and Xrandr (steal the code from Arandr it's great). On 7 December 2015 at 04:14, Maxthon Chan <[email protected]> wrote: > If you don’t feel like implementing them now I would suggest at least put > them on the long term goal list. There will be a time when SWK or CEF start > to meet their shortcomings. > > > On Dec 7, 2015, at 12:11, Gregory Casamento <[email protected]> > wrote: > > > > Chan, > > > > On Sun, Dec 6, 2015 at 10:53 PM, ChanMaxthon <[email protected]> wrote: > >> No matter how we wrap around a Linux browser it stays a major > out-of-tree > >> patch set but if we implement the dependencies ourselves it would be > only > >> minimal patching if any. > > > > While it does remain out of tree, it is foolish to think that > > implementing all of the things needed to either get SWK working to the > > point where it can take over from WebKit or that we can port WebKit > > itself in any reasonable amount of time. > > > > The only way to have a practical usable browser NOW is to do what I > > have proposed. > > > > GC > > -- > > Gregory Casamento > > GNUstep Lead Developer / OLC, Principal Consultant > > http://www.gnustep.org - http://heronsperch.blogspot.com > > http://ind.ie/phoenix/ > > > _______________________________________________ > Discuss-gnustep mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnustep > >
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
