As a tutorial about SynProject, the documentation for the SQLite3 framework itself has been generated for the first time.
You asked for documentation about our Synopse SQLite3 framework, we'll generate it automatically, thanks to SynProject!
The resulting documentation of our SQLite3 framework (in draft status) can be downloaded from sampledoc.zip.
If you want to know how this documentation was created in a few click using SynProject, follow this link:
http://synopse.info/fossil/wiki?name=Sy … t+Tutorial...
This documentation will progress, and the associated .pro file will be available in our source code repository.
Documentation updated today.
http://synopse.info/files/synproject/sampledoc.zip now contains DI, SAD, SWRS, Risk and SDD documents.
Still in draft status, but you'd be able to guess more about SynProject...
The associated .pro file has also been updated in our repository.
The documentation has been updated to refresh the status of the 1.12 release.
From the same link:
The SAD document has been enhanced - same download link above.
It now contains the UI-related units interfaces.
And a lot of general presentation have been added:
- MVC and Multi-Tier architecture;
- Why a Client/Server ORM;
- Writting RESTful Services;
- fixes and enhancements (to the SQLite3 related paragraphs e.g.).
More to come!
The SAD document has been enhanced a lot:
- An Index has been added;
- The Main Demo has been commented within;
- New 1.13 related features (Virtual Tables, TDynArray, logging, new fields...) have been introduced;
- A lot of improvements, especially for the integrated diagrams (now vectorial).
The documentation is now in the 1.15 version.
It has been updated, and contains now a description about the main feature of this 1.15 version, i.e. "database agnosticism".
My compliments for the excellent mORMot Framework and the documentation.
Going through the SAD pdf document, what I missed the most in the functionality of the documentation is
the lack of hyperlinks in the documentation. I find it helpful to go deeper into a subject that I was reading and
be able to jump back.
Is there any chance some kind of a Wiki Doc being setup in the future?
Just my two cents ...
We already reached somewhat a limit of Word generation, with the corresponding links.
Up to now, do not forget there is a "keyword index" at the beginning of the document.
I may easily add a reference back from each keyword appearance from the text to this index, if you find it useful.
Did you expect also a link to the class/units/function definitions (as extracted from source comments)?
A simple Ctrl+F in Adobe Reader to find it is also worth trying.
SynProject tool used to create the documentation only creates RTF/Word documents by now.
A HTML generator is started, but not finished yet.
I do not like very much wikis, since it tends to have a non homogeneous content quality, and fragmentation in small pages.
The SAD document was refactored several times, and if you take a look at the upcoming 1.18 version, you will find out that it has been a lot changed.
See http://synopse.info/files/pdf/Synopse%2 … 201.18.pdf
Having one source file for the whole content (the .pro file) is IMHO a plus. Such a deep refactoring should have been more difficult to do with a wiki.
Any help is welcome to maintain the .pro file!
The Documentation is great but there's one small English grammar mistake which keeps cropping up and can be confusing: "Either this either that" should be written in English as "Either this OR that". I guess it's because in French it's "ou...ou" see: http://www.wordreference.com/enfr/either%20or
Could the most current documentation be given a static link without the version number one gets with:
http://synopse.info/files/pdf/Synopse%2 … 201.18.pdf
Then I could create a bookmark in my web browser which is always up to date.
Thanks for the report.
I've created a ticket http://synopse.info/fossil/info/54af269043 and will fix it.
And this is "neither... nor", isn't it?
About the link, I'll do it.
"neither... nor" is different to "either.. or"
"neither Peter nor Jane will go to the party" means none of them will go to the party. neither is a bit like "not... either... or..."
"either Peter or Jane will go to the party" means only one of them will go to the party.
Last edited by esmondb (2013-01-22 13:54:52)
Is this a typo in the document (several lines before 21.2.2. Additional safety)?
Be aware than this per-table access rights depend on the table order as defined ...
I think it should be read:
Be aware that this per-table access rights depend on the table order as defined ...
I'm afraid there are a lot of typos and mistakes...
Any feedback is welcome!
Anyone can open and edit the .pro file, then propose the corrections.