[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libreoffice-documentation] Chapter 2 of Base Guide progress
[Thread Prev] | [Thread Next]
- Subject: Re: [libreoffice-documentation] Chapter 2 of Base Guide progress
- From: Dan Lewis <elderdanlewis@gmail.com>
- Date: Sun, 11 Mar 2012 19:37:25 -0400
- To: documentation@global.libreoffice.org
On Sun, 2012-03-11 at 22:15 +0000, Mark Stanton wrote:
> > I think it might be fastest for Hazel to complete it.
>
> Too late! Update in the drafts folder just now.
> Mostly content, since Hazel's proof reading is great.
>
> Since a lot of it is about the content, there are many "notes" rather than changes of
> text.
>
> It's really important to make the distinction between a DBMS (that's a program that
> manages a database), and the data that we put into a database that we've built
> using a DBMS.
>
> I also think that's it's REALLY important to make it clear that HSQLDB is not THE
> Base DBMS, just the default setting. There is no "Base DBMS", it can use many
> different engines. And, sticking my neck out even further, I'd say it'd be good
> to play down the built in version of HSQLDB, or at least not play it up. Since it's
> limitations have upset even one of our most famous "Base" names, Mr Pitonyak, I think
> it would be good to play up the ability to use (almost) whatever DMBS you want rather
> than giving the impression that HSQLDB is "it".
>
> Ok, steady.. Aim... Fire!
>
> Regards
> Mark Stanton
> One small step for mankind...
Fire one! [;-) ]
The one thing that has always confused me: What is Base? What
should be put as the answer to this question? Just how much information
do people need to know? How do we tell them that Base may not be the
program for them? [Personally, I would prefer to stay away from all the
technical such as DBMS or RDBMS. What matters is what should a person do
to use Base for the tasks that they have [if Base can do them].(IMO, of
course)
I have not downloaded what you have done yet, but I have a feeling
that I will have many questions for you for a while when I have a chance
to look over what you have done.
This definitely going to be a learning experience on my part, and I
look forward to that.
--
Unsubscribe instructions: E-mail to documentation+help@global.libreoffice.org
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
| Re: [libreoffice-documentation] Chapter 2 of Base Guide progress | drew jensen <drewjensen.inbox@gmail.com> |
| Re: [libreoffice-documentation] Chapter 2 of Base Guide progress | Mark Stanton <mark@vowleyfarm.co.uk> |
| Re: [libreoffice-documentation] Chapter 2 of Base Guide progress | Rogerio Luz Coelho <luz.rogerio@gmail.com> |
| Re: [libreoffice-documentation] Chapter 2 of Base Guide progress | Tom Davies <tomdavies04@yahoo.co.uk> |
| Re: [libreoffice-documentation] Chapter 2 of Base Guide progress | Mark Stanton <mark@vowleyfarm.co.uk> |
- Prev by Date: Re: [libreoffice-documentation] Chapter 2 of Base Guide progress
- Next by Date: Re: [libreoffice-documentation] Chapter 2 of Base Guide progress
- Previous by thread: Re: [libreoffice-documentation] Chapter 2 of Base Guide progress
- Next by thread: Re: [libreoffice-documentation] Chapter 2 of Base Guide progress
- Index(es):
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License (LGPLv3). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.