Fix loading/saving of V1.1 documents.

[architektonas] / README

diff --git a/README b/README
index 144c76dfd4e45dd47a6d4dd08e5d17576bbc1da8..e402b44569e12635b9868068aee50250b06ec402 100644 (file)
--- a/README
+++ b/README
@@ -1,13 +1,12 @@
 @-~ Copyright and Licensing ~-@
 
 @-~ Copyright and Licensing ~-@
 

-Architektonas: Free Cross Platform CAD software
-Copyright (C) 2010 Underground Software.
-Portions copyright (C) 2001-2003 RibbonSoft.
+Architektonas: Free Cross Platform 2D CAD software
+Copyright (C) 2011 Underground Software.

 Trademarks used are the property of their respective owners.
 
 This program is free software; you can redistribute it and/or modify it under
 the terms of the GNU General Public License as published by the Free Software
 Trademarks used are the property of their respective owners.
 
 This program is free software; you can redistribute it and/or modify it under
 the terms of the GNU General Public License as published by the Free Software

-Foundation; either version 2 of the License, or (at your option) any later
+Foundation; either version 3 of the License, or (at your option) any later

 version.
 
 This program is distributed in the hope that it will be useful, but WITHOUT ANY
 version.
 
 This program is distributed in the hope that it will be useful, but WITHOUT ANY


@@ -35,26 +34,44 @@ it would work, and if it was worth doing. Positive results were obtained in
 both respects, so work started in earnest in doing a complete port to Qt 4
 without any reliance whatsoever on the Qt3Support module.
 
 both respects, so work started in earnest in doing a complete port to Qt 4
 without any reliance whatsoever on the Qt3Support module.
 

-Eventually, after much hard work and cursing, success was won and the author
-ended up with a codebase that was quite a bit different from that which he
-started with. And since the end goal was not just feature parity with QCad CE
-but to surpass it, a new name was needed to prevent confusion with RibbonSoft's
-product.
+Eventually, after much hard work, cursing, and gnashing of teeth, success was
+won and the author ended up with a codebase that was quite a bit different from
+that which he started with. And since the end goal was not just feature parity
+with QCad CE but to surpass it, a new name was needed to prevent confusion with
+RibbonSoft's product.

 
 Initial thoughts on naming centered around FooCAD or CADFoo (with Foo being
 whatever), but a long search on the internet brought forth the conclusion that
 such paths have been well trodden by just about anyone who has even given a
 
 Initial thoughts on naming centered around FooCAD or CADFoo (with Foo being
 whatever), but a long search on the internet brought forth the conclusion that
 such paths have been well trodden by just about anyone who has even given a

-thought towards creating computer aided design software. And so it was
-manifestly clear that a different naming scheme would be required. After
-several false starts, the name Architektonas was chosen as a rough English
-transliteration of the Greek word for architect. We like it; we hope you do
-too!
+passing thought towards creating computer aided design software. And so it was
+manifestly clear that a different naming scheme would be required. After much
+reflection and several false starts, the name Architektonas was chosen as a
+rough English transliteration of the Greek word for architect. We feel it's a
+good name and hope to live up to the expectations that such a name gives!
+
+An interesting postscript to this story arose with a certain Mr. Ries van Twisk,
+who is the author of another QCad fork called LibreCAD, arrived on the scene.
+For some time Mr. van Twisk had access to the author's private repository and
+rather than work with the author, he decided to create his own fork "from
+scratch". Of course this was burdened with all of the problems that surrounded
+the original QCad CE source done with Qt3 and the porting to Qt4 and the
+Qt3Support module. And so, stagnation reared its ugly head once more. Sad, but
+true.
+
+And so, in light of this prospect, and after the author of Architektonas having
+beat his head against the illogical class structure and general brain-deadness
+of the code, he decided it would be for the best to divorce himself from the
+QCad codebase he so painstakingly ported to Qt4 and start from scratch. The
+result, in our opinion, was worth the effort--and even the porting effort of
+QCad CE was not in vain as it helped the author to clarify that vision and
+arrive at something *much* better. We think you'll agree! And if you don't, we'd
+love to hear from you so that we can improve!

 
 
 @-~ Installation ~-@
 
 
 
 @-~ Installation ~-@
 

-Architektonas is built on the Qt 4 framework; it requires version 4.6.3 or
-later. We build it using gcc v4.4.3; we can't guarantee that it will compile on
+Architektonas is built on the Qt 5 framework; it requires version 5.3.2 or
+later. We build it using gcc v4.8.4; we can't guarantee that it will compile on

 lesser versions but you never know. Building Architektonas should be as easy as
 typing:
 
 lesser versions but you never know. Building Architektonas should be as easy as
 typing: