Hi All, I would like to offer OxygenOffice Collected and Managed templates here. We created and collected a plenty of templates during the half decade. This template pack is available for a free license. The collection is a bit mixed in term of quality, usability and language support but we have good base to start the work here and many languages are supported and also we have common (language independent section to). I tried to organize and collect more information about the collected templates. I hope they maybe useful for the LibO community. Tempates are available in extension site and they are collected in a svn repository.
https://ooop.svn.sourceforge.net/svnroot/ooop/trunk/extras/source/ http://extensions.services.openoffice.org/en/taxonomy/term/34 Best regards, KAMI 2010/11/3 jonathon <toki.kant...@gmail.com> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 11/02/2010 05:43 PM, Marc Paré wrote: > > >The members would be picked according to their expertise in these > categories. > > The ability to create a template is more important that knowledge of the > field. > > > If we were to setup a Templating Team group and published a large variety > of templates, then the LibO suite would become more valuable as an Office > suite for everyone. > > My suggestion would to be provide a templating_team with the > specifications for the template, and let them create the template. A > clean room implementation of the template. > > > creating some templates for Evangelical church routines. > > For some things, such as membership records, a database is required. > (I'm not going to get into a PICK v RDBM debate here.) > > For others, a simple Write, Calc, or Impress template is suitable. > > In an ideal situation, there is a database_creation team, that works in > conjunction with the template_creation team. > > The template_creation team create a calc, impress, or write template, > that is then passed on to the database_creation team. This (database) > team then determines whether this is something that is suitable for a > database, and if so, creates a database, and the associated interface > requirements. > > [Database rant: LibO should either add SQLite as a built in database > engine, or else replace Base database engine with SQLite.] > > My guess is that some, if not most of the databases, will have to be > constructed as extensions. For example, a genealogical database would > have to be able to both import, and export data in GEDCOM format. > > With experience, the database_creation team and the template_creation > team can construct templates, extensions, databases, and other items > that are on a par with those for MSO that have an MSRP of US$10K+. > > jonathon > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkzQ8jUACgkQaC1raifmCuFdBACeOL6NHxl6m2WfZcwh0vASoVZH > x4kAnRY+92531vKb9MwmQ3ZOopPcl/l+ > =pbjt > -----END PGP SIGNATURE----- > > -- > E-mail to marketing+h...@libreoffice.org<marketing%2bh...@libreoffice.org>for > instructions on how to unsubscribe > List archives are available at http://www.libreoffice.org/lists/marketing/ > All messages you send to this list will be publicly archived and cannot be > deleted > > -- E-mail to marketing+h...@libreoffice.org for instructions on how to unsubscribe List archives are available at http://www.libreoffice.org/lists/marketing/ All messages you send to this list will be publicly archived and cannot be deleted
