Dear Chris,
About your can of worms....ah, yes I had this discussion before as well, with
Michael.
If I recall, the issue of not putting KDE or Qt in base was to allow for
portability. My understanding is that one of the founders was porting this to
Mac.
With KDE out of the way, doesn't our port line up more for a port to Mac.
I don't know what else is involved, but Qt Toolkit ports to Mac.
I think a limited switch might be beneficial. QString() for one. That would
simplify many aspects of interfacing the layers of code we have.
Say goodbye to many instances of qstrtostr(), and strtoqstr().
I'm not certain of any other benefits at this point in keeping base pristine
with regards to QString(), since it will fall under LGPL soon.
I have to admit that I don't see any benefit in polluting base with Qtr without
just cause though. Base does what it does pretty well, from my limited
perspective.
Sincerely,
Julie S.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
