Some questions about file handling + some other things

Dear Users / Developers,

My first question is about the web interface (and in fact, more
general). My observations after playing with @file and @file-1 etc.
form variables. Maybe it will be useful to others, and you can correct
me if I am wrong:

1. Multiple file upload is supported via @file: You can use a
<input type="file" name="@file" multiple> form input, or you can
add <input type="file" name="@file"> multiple times. (The second
solutions seems a bit ugly to me, it may depend on the browser.)
This is documented in the source code, but not on the website.

2. By inspecting, it seems that if you want to use @file-1, @file-2,
@file-3,... instead of the above method (because you also want to set
some properties in the creation step), then some "-N" can be omitted.
For example if @file-1 and @file-3 form variables are set, but @file-2
is not then it works as expected. This needs some more testing though.
:) [This is handy, when the file upload page is created using JS,
and the user is allowed to remove files from the to-be-uploaded list.
Then you do not have to renumber everything.]

3. You can create files (of FileClass) in the database even with
roundup-admin, simply just do "create file ..." and setting the content
property accordingly. (This was not obvious to me, sorry.)

4. I do not really understand how indexing works yet, and
the documentation is a bit terse on that topic. I just vaguely looked
into the code, but it seems that
The content of files (file, msg, etc.) are indexed (?), but only if
their type is text/plain (?). This indexing can (?) be disabled by
explicitly setting

file = FileClass(db, "file",
                name=String(),
                content=String(indexme='no'))

in schema.py. Btw shall I install Xapian, or not? :)

5. The other thing I was interested in is journaling: As I see, the the
journaling of String() property changes cannot be disabled. (In my db
there is a "memo" for issues, which always increasing, but I did not
want to use a FileClass for this, and the history looks ugly. But the
history needs rewriting, anyway. ;)

6. Logical negation (or exclude_spec) is missing from filtering
machinery. :) Stuff like "status_notresolved string:-1,1,2,3,4,5,6,7;"
looks a bit strange in the page.html of the default templates... :)

I hope I can deeply understand the code at some day, and I can commit
patches at some point. :)

Regards,
Gábor




_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users