minor suggestions/requests for Tellico

[Robby Stephenson]

Hi Richard,

Thanks for the feedback,

On Tue, Oct 22, 2024 at 3:54 PM Richard Lyons <richard at lyons.art.br> wrote:

> Hi again.
>
> A few minor points I ran up against...
>
>  1. When editing or entering new data for an item in a collection, the
>     fields are presented in the order set up by the user, but zigzagging
>     between the two columns like this
>
>         AAAAAAAAAAAAAAAA                        BBBBBBBBBBBBBBB
>         CCCCCCCCCCC                             CCCCCCCCCCCCCCCCCCC
>         DDDDDDDDDDDD   ... etc
>
>     This seems to me at least to be illogical could there be an option to
>     have the fields presented in column order, so that sequential items are
>     adjacent, like a directory listing, thus:
>
>         AAAAAAAAAAAAAAAA                        FFFFFFFFF
>         BBBBBBBbBB                              GGGGGGGGGGGG
>         CCCCCCCCCCCCC                           HHHHHHHHHHHHHH
>         DDDDDDDDDDDDD                           I
>         EEE
>
> This would speed data entry and reading of connected data.
>

I need to think on this one a little more. I don't want to add too many
options so I'm hesitant on this one.


>  2. It would be good idea to warn users against using the $ character in
>     field names. I had two price fields in my initial data and could not
>     understand why one of them disappeared from reports. The same
>     applies to numerals, which I eventually discovered are simply
>     omitted from the field name by tellico internally. Everything works
>     fine after I eliminated field-names like 'price R$' (which is the
>     symbol for the Brazilian Real) and 'w3page' (which tellico stores as
>     'wpage')
>

In general, I don't expect users to need to know the internal field names.
THose are primarily helpful when dealing with the XML and XSLT aspects of
the data. I did add a tooltip to the field dialog that shows the internal
field name, which could be useful. I'm not going to add a warning since
it's not a problem to have field titles such as your examples.


>  3. I found the description in the configuration of the possible
>     locations for image storage unclear. Perhaps that is just me, but I
>     would suggest demonstrating by examples.
>

Good thought, I will add a label that shows explicitly where the images
would be saved for each option, probably in 4.1.

Robby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/tellico-users/attachments/20241126/aa50c08e/attachment.htm>