I suggest you to put version number of the document on its begin, maybe after your name.renowden wrote:I have corrected the PDF and uploaded a second draft.
It is OK, but I suggest you to make each chapter name in Contents to be a link to corresponding chapter. Also, each chapter should begin from the top of page (e.g. on a new page). Font size for titles should be different depending of the chapter level, e.g. Introduction could be 24 pt, and Getting Started could be 18 pt. Acknowledgements section should be after Contents or its page should be numbered by roman numbers. Contents page should be obligately numbered by roman number, e.g. first page after it should start from 1.The TOC is a bit rough as I can't figure out how to do it properly in OpenOffice!
There is some more comments:
- "Album Artist with Album - Album Artist followed by Album in parentheses" - Album is not inside of parentheses but after dash ("-"), please remove "in parenthesis".
- "Time since last played - A wordy description" - users should know if this field is used in Filter qualifier it could take a value from 0 to 5: 0 (Less than an hour), 1 (Between an hour and a day), 2 (Between a day and a week), 3 (Between a week and a month), 4 (Between a month and a year) and 5 (Over a year or never played).
- "Show tracks:yes|no" for local qualifier, please remove "Unlike the Global Qualifier, this does work in MM3".
- Top qualifier should be before Trim in table.
- You should write that Trim qualifier could take a negative values in which case it trims characters from the right side of fields.
- Path to INI file could be fully written as "x:\Documents and Settings\<your_name>\Local Settings\Application Data\MediaMonkey\) where x is system drive, blah, blah".
Yes, I agree about examples as I wrote in the previous message to paul_leclerc. Regarding to SQL... Well, this is relatively complex area which couldn't be covered in short. You need at least 10x more pages than this manual has. If you don't have enough knowledge about SQL language, maybe someone else could join in writing of this manual. If you want to learn about SQL, you could take a look on reference page of SQLite: http://www.sqlite.org/lang.html, especially on SELECT (http://www.sqlite.org/lang_select.html) and expression parts (http://www.sqlite.org/lang_expr.html).I feel we need to say a bit more about SQL filters but I don't know enough about it yet - perhaps a few more simple but informative examples would do the job. I think we also need to say a bit more about filter expressions and their syntax - or, in both cases, refer people to some external document for the parser if one is available.
Here are two most important thing about Filter and SQL Filter qualifiers:
1. text which you write after SQL Filter: part of SQL Filter qualifier should be exactly same as it is in WHERE part of SELECT queries (take a look on the mentioned Web page).
2. SQL filter qualifier has similar syntax as Filter qualifier. Difference is: SQL filter needs to specify table.field names as it is used in SQL queries, but Filter qualifier accepts Magic Nodes names for MM fields. For example, if you want to use SQL Filter you could write Songs.Artist = 'Pink Floyd', and if you want to use Filter qualifier you could write <Artist> = 'Pink Floyd'. Filter qualifier syntax is in many cases much shorter than SQL Filter syntax and in some cases works with both MM2 and MM3, when same SQL Filter don't (for example, Songs.AlbumArtist = 'Pink Floyd' works only in MM3, but <Album Artist> = 'Pink Floyd' works in both MM2 and MM3).
If you want to know which tables contain MM database and which fields contain some table, you could take some appropriate database viewer/editor. For SQLite I recommend SQLite Spy (http://www.yunqa.de/delphi/doku.php/pro ... espy/index)
Left of and Right of could be used to parse some text field and to display only left or right parts of it. For example, if you have Genre field with two possible values separated with "-", e.g. "Rock-Blues": Left of:- will return Rock and Right of:- will return Blues. This could be useful in MM2, but in MM3 there is much better solution using multi-item possibility of this genre with ";" as separator. In MM3 this qualifiers could be used for those fields which are not multi-items, as Custom.I had to dig the stuff about Left of: and Right of: out of the script as I could see no mention of it elsewhere.
OK, but maybe we should continue in this place with this to enable others to join with suggestions and comments.Feel free to PM me
It is OK to me, but I suggest some format which don't need some external program, only those which are already part of Windows: RTF, HTML. CHM. I personally prefer CHM, because I want to incorporate this text as help file, as I wrote before, but if you don't know how to do this I could convert it by myself when I find enough time.I was wondering if PDF was the right format or if it should be coded up as HTML?