On Mon, 06 Feb 2012 08:10:43 -0500 Dan Lewis <[email protected]> wrote:
Yes, that would be a good solution too. I have put a cut-down version of the existing GS chapter in the feedback folder along with the edited full-length version, just for people to look at. It does no harm to provide alternatives! > I would prefer to cut down Introducing Base and making it the > Gettting Started with Base chapter. It could be reduced to using only a > flat database with its single table created by the Tqble Wizard., a > form, one or more queries, and one or more reports. > Presently, the Getting Started chapter uses a relational database > which is more involved than the flat database. That seems to make it a > better candidate for the first chapter of the Base Guide. Even then it > probably could use some cutting down as well. > Hazel: the section that I sent you on copying a table from Calc > should really be a part of chapter 5. So, if you have not done anything > with this, don't. > > --Dan > > On Mon, 2012-02-06 at 11:04 +0000, Hazel Russman wrote: > > On Sun, 5 Feb 2012 19:04:08 -0200 > <SNIP> > > > > Yes, I think this would be the best approach if we were starting from > > scratch. Use one of the wizard's standard databases and show the > > creation of the table(s) and input form(s), a couple of simple queries > > and a simple report. Design from first principles would then be covered > > in the Base User Guide. > > > > But we are not starting from scratch. Dan has put a lot of work into > > this and I'm sure he doesn't want to see it wasted. Also it is high > > time we got *something* out. It seems that Base has always lagged > > behind the other modules where documentation is concerned. So cutting > > down the existing GS guide and moving the deleted sections elsewhere > > would seem to be the best option. I am going to try and produce a > > cut-down version and see if it will work. If I succeed, I will put it > > into the drafts folder for review. > > > <SNIP> > > > > > > 2012/2/5 Dan Lewis <[email protected]> > > > > > > > Perhaps, but I'm thinking that Base like the other guides will > > > > have people using only parts of the guide. Some will use the simple, and > > > > others with use the complex. So, I wonder about splitting Base or any of > > > > the other guides. Who knows, someone beginning with the simple might > > > > decide to try something more complex. Would they do so if it was not in > > > > the guide they had? And what about maintenance of the guides? That seems > > > > to be adding extra work. I suppose I like the idea of having the guide > > > > go from the simpler to the more complex using one outline. This seems to > > > > be simpler than using two outlines when writing: the simple, and the > > > > advanced. Just some of my thoughts. > > > > > > > > --Dan > > > > > > > > On Sun, 2012-02-05 at 19:45 +0000, Tom Davies wrote: > > > > > Hi :) I like that plan :) I think splitting the guide would be easier > > > > > after this incarnation of it is completed. I think we need something > > > > > solid and "out there" (released and published on Lulu) before we can > > > > > really make sense of exactly what does and what doesn't work well in > > > > > those sorts of splits. I guess that since this one is looking like > > > > > being the advanced one then a slimmer one for a flat database might be > > > > > easier for someone afterwards? > > > > > > > > > > Regards from > > > > > Tom :) > > > > > > > > > > --- On Sun, 5/2/12, Dan Lewis <[email protected]> wrote: > > > > > > > > > > From: Dan Lewis <[email protected]> > > > > > Subject: [libreoffice-documentation] Getting Started with Base > > > > > To: [email protected] > > > > > Date: Sunday, 5 February, 2012, 19:33 > > > > > > > > > > What I have been thinking about for some time but never really > > > > > got > > > > > a round to doing: > > > > > 1. Getting Started with Base chapter containing a flat database > > > > > created > > > > > by the Wizards with the basics of what to do. > > > > > 2. Base Guide: (first four chapters that is) > > > > > a. Introduction to Base: creating a relational database with the > > > > > basics of what to do. > > > > > b. Planning/Designing databases: what is needed when planning a > > > > > database and how to > > > > > turn the plan into the database's design. Contains examples of > > > > > a > > > > > flat database and a > > > > > more complex relational database. (Thorough explanation of the > > > > > principles.) > > > > > c. Data Input and Removal: thorough explanation of the principles > > > > > of > > > > > the tables and > > > > > forms including use of SQL in creating, modifying, and deleting > > > > > tables. > > > > > d. Data Output: thorough explanation of the principles of queries, > > > > > views, and reports. > > > > > > > > > > --Dan > > > > > > > > > > On Sun, 2012-02-05 at 19:03 +0000, Tom Davies wrote: > > > > > > Hi :) > > > > > > I used to think that Base might need 2 "Getting Started" guides. > > > > > > 1. for people just doing data-entry and normal user perhaps with > > > > routine maintenance > > > > > > 2. for designers building a database and front-end and for > > > > > > advanced > > > > maintenance. > > > > > > > > > > > > Writing for 1 would be a nightmare due to the huge variety that is > > > > possible when building a database with Base as the front-end. I don't > > > > think we can really do even a basic generic enough guide until after the > > > > one for 2 is done. > > > > > > > > > > > > Hazel are you saying my 2 would really need to be split into two > > > > > > too? > > > > If only 2 sections need to be moved out of the GS Chapter then would > > > > that > > > > chapter still make sense? Wouldn't it remove something crucial? The GS > > > > Guide is just meant to be an appetiser rather than go into tons of > > > > detail. > > > > Chances are that most users will only use Base through using mail-merge > > > > and stuff like that so we really need to keep it as simple as possible. > > > > If > > > > the chapter still makes sense then moving those sections to the full > > > > guide > > > > for Base would be great imo too. > > > > > > Regards from > > > > > > Tom :) > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Unsubscribe instructions: E-mail to > > > > [email protected] > > > > Problems? > > > > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > > > > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > > > > List archive: http://listarchives.libreoffice.org/global/documentation/ > > > > All messages sent to this list will be publicly archived and cannot be > > > > deleted > > > > > > > > > > -- > > > Unsubscribe instructions: E-mail to > > > [email protected] > > > Problems? > > > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > > > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > > > List archive: http://listarchives.libreoffice.org/global/documentation/ > > > All messages sent to this list will be publicly archived and cannot be > > > deleted > > > > > -- > > Hazel Russman <[email protected]> > > > > > > > -- > Unsubscribe instructions: E-mail to [email protected] > Problems? > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/global/documentation/ > All messages sent to this list will be publicly archived and cannot be deleted -- Hazel Russman <[email protected]> -- Unsubscribe instructions: E-mail to [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
