Qt 5 Port - An Introduction to Design Patterns in C++ with Qt(2nd Edition)
-
Hey all! Currently there are no books written on Qt 5 yet. BUT I am learning Qt 5 with a Qt 4 book, "An Introduction to Design Patterns in C++ with Qt(2nd Edition)":http://www.amazon.com/Introduction-Patterns-Prentice-Software-Development/dp/0132826453/ and what I learned is that a lot of the material there is still very relevant. We shouldn't discard it as obsolete simply because it is written in Qt 4. However, porting the "source code":http://www.ics.com/designpatterns/dist/src.tar.gz is tedious, so I decided I would post up the port in github!! :D
https://github.com/bruceoutdoors/Intro-Design-Patterns-Cpp-Qt5
I did this after spending hours trying the port the source files from chapter 7(on dynamic libaries). It's tiresome, so I could save ppl a lot of time for not needing to port it again.
-The port is not finished, however- I hope ppl here can join me(contribute code and help others learn as well) and pick up this book(which is an awesome book!!). As if this writing I'm halfway through chapter 8.
-
Are you sure you're allowed to do that? Not to be picky or something, but someone does own a copyright for that code, and I haven't seen a license file in the package or on your github repo
If you are, though, then this is a nice initiative. You can use the scripts prvided with Qt5 to automatically convert Qt4 apps to Qt5 (basic include stuff, that is).
-
Truth be told... I don't know. Lol. The 1st commit of the repo was the original source that is freely available for download... Which also did not have any licensing to begin with. The most I could really do was acknowledge that it is Ezust's work(which I did) and wait for them to say something if it is illegal.
-
First, thank you for your enthusiasm in helping others learn Qt! There are some protocols we should respect, however.
[quote author="bruceoutdoors" date="1369248482"]The 1st commit of the repo was the original source that is freely available for download... Which also did not have any licensing to begin with.[/quote]Unless a piece of work is explicitly released into the public domain, or a long long long time has passed (many decades), the authors automatically own the copyright.
Open-source licenses say, "Hey, we own the copyright, but we also give you the right to fork our work, but you must also let others do the same". Creative Commons (CC) licenses might also give you the right to fork, but some CC licenses only let you share the original work without modifying it.
If they have not specified a licence, then they have not given you permission to fork their work.
[quote author="bruceoutdoors" date="1369248482"]The most I could really do was acknowledge that it is Ezust's work(which I did) and wait for them to say something if it is illegal.[/quote]That's the wrong way round.
Out of courtesy, you should at least first ask the authors for permission, even if you think they wouldn't mind. If they give you permission, great! :) If not, please respect their wishes, even if it means disappointment for yourself and lots of other people. Try reaching the authors at http://www.ics.com/company/contact
-
Thanks! I'll contact them and see what they have to say
-
I've already finished the book along time ago... I completed as much of the porting as I could, but certain parts left me clueless a bit. You're more than welcome to finish where I couldn't.
On the rights... honestly, I have no idea. I have sent a message months ago to the authors but they didn't reply me... so...
...I guess you can use it until they decide to shut that repo down?
-
bq. Unless a piece of work is explicitly released into the public domain, or a long long long time has passed (many decades), the authors automatically own the copyright.
I don't think this is true. The author probably still owns some sort of copyright but for instance, nothing that has been released publicly can be patented, and without a proper copyright notice, publishing something publicly is equivalent to entering the public domain AFAIK.
Anyway nice job.
-
Hi, and welcome to the Qt Dev Net!
[quote author="LaRainette" date="1398106709"]nothing that has been released publicly can be patented[/quote]Correct. But patents and copyrights are "not the same thing":http://www.uspto.gov/trademarks/basics/definitions.jsp. In this case, we're talking about a book which has been published -- it receives a copyright, not a patent.
.
[quote author="LaRainette" date="1398106709"]without a proper copyright notice, publishing something publicly is equivalent to entering the public domain AFAIK.[/quote]No, copyright is "automatic":http://www.ipo.gov.uk/c-auto.htm.[quote author="LaRainette" date="1398106709"]The author probably still owns some sort of copyright but... publishing something publicly is equivalent to entering the public domain AFAIK.[/quote]Note that "public domain" means "no copyright".
