This is repository of my old source code which isn't updated any more. Go to git.rot13.org for current projects!
ViewVC logotype

Contents of /trunk2/NEWS.pod

Parent Directory Parent Directory | Revision Log Revision Log

Revision 373 - (show annotations)
Sun Jun 20 15:49:09 2004 UTC (16 years, 5 months ago) by dpavlin
File size: 2602 byte(s)
a lot more logging, lookups are now working as expected (and documented)

1 =head1 NAME
3 Quick overview of things that are new in v2.x of WebPAC
7 This document will describe new features in WebPAC version v2.x.
8 It will also attempt to document upgrade procedure to migrate
9 WebPAC v1.x installations to new v2.x.
11 =head2 Input file handling
13 Database files are now read in memory (using swap if not enough
14 memory is not available) and used from there.
16 Also, in-memory structure will be dumped to temporary disk
17 cache, so that unchanged databases won't be re-read (and parsed) if source
18 database hasn't changed. Nice consequence of this is that memory lookups
19 are now for free (see below).
21 =head2 Two-step processing of databases
23 In first step database is read and in-memory structure is created (or
24 read from on-disk cache if source database hasn't changed).
26 In second step output formats are created.
28 =head2 Lookups
30 For a start, lookup files are no longer supported. Since memory lookups
31 are newer and more powerful (for example, each key can have more than
32 one value) it's not a great loss. However, you will have to re-write
33 your C<import_xml> files if you use lookup files to use memory lookups.
35 Lookups B<are not> specified by C<[v900^4]> as in v1.x. Now, you have
36 to use something like C<lookup{v900^4}>. Recursive lookups are also
37 possible: C<lookup{foo:lookup{v900^4}}>.
39 Memory lookups (referred as lookups for new versions of WebPAC) are now
40 always available. Since whole database is available when creating
41 output linking should be much easier now.
43 However, using new lookups require to define lookups in different way.
44 Additional benefit of that is conditional insert into lookup using eval
45 (TODO: explain new lookup format).
47 If you have any lookups in your tag (e.g. <isis>lookup{v900^5}</isis>)
48 smart delimiters will be turned off (this behaviour is consistent with
49 old in v1.x if you use C<type="lookup*"> or C<filter="mem_lookup">).
51 =head2 Field definition in C<import_xml>
53 Field definitions in C<import_xml> files has changed. Previously, you could
54 write something like C<250a> and expect to get data from field B<250> subfield
55 B<a>. Now you have to write C<v250^a> which is more ISIS-like and easier to
56 parse. Don't be afraid, there is migration script in C<import_xml> to do
57 this task for you.
59 =head2 Templates
61 Templateing engine has changed. WebPAC doesn't use C<HTML::Template> anymore,
62 but Template Toolkit. TT proved to be workhorse for many tasks
63 and limitations of C<HTML::Template> forced me to move from it.
65 For you, the user, that will result in changes to all templates. I'm sorry
66 about this, but it had to be done.

  ViewVC Help
Powered by ViewVC 1.1.26