English > Feature Suggestions

Vote: Features for 0.9.9

<< < (22/39) > >>

nostra:

--- Quote ---I hope you've included the ability to save searches
--- End quote ---

I have not done this yet, but I will


--- Quote ---how about an auto save function like MS Word or auto back-up and tool bar icon for easy save as is - thanks for this software and this site - Paul
--- End quote ---

Yes, it is planned for the next version

rick.ca:

--- Quote ---how about an auto save function like MS Word or auto back-up and tool bar icon for easy save as is
--- End quote ---

"Auto-save" and "save as is" are not necessary. It's a database—all changes are recorded as they are made. I suppose what is going to be added is some kind of automated backup and/or backup reminder feature.

nostra:

--- Quote ---I suppose what is going to be added is some kind of automated backup and/or backup reminder feature.
--- End quote ---

Yes

meriator:
...an other little wish
to have custom fields for persons
like they are existing for movies already
and
(this might be more difficulty)
an integreation of custom fields into advanced search

this would be great
thanks a lot anyway

cu meriator
 

meriator:
An other suggestion
I think that most users relay on IMDB for their movie-data,
especially on unknown/uncommon movies they do not own yet.
Unfortunately these data is mostly only in english available
and there are a lot of other good site in the web with
different languages from the users own.

to solve language related problems
in a proper way it might be usefull to have
a language specific replace-list

language specific means if I use the app with english translation
only phrase marked as translated into english will be used
and so on


for genres, countries(names), languages(names), categories, tags, mpaa-ratings, ....
and maybe for phrases used by the program it self (to customise the viewable output),
as i have seen in other apps aka "data crow" -> sourceforge.net

means
id;lang;fieldtype;phrase;replacement

so all incoming data will be setted up
language-specfic correctly to users-needs
at capture-time (db-data will be changed to his native language)
or
at view-time (db-data is keeped in orginaly language and will be only processed for viewing)
or
nothing (means like it is)
(this all should depend on the users-preferences
if he, the user needs this and if he takes the time to use it)
 
with out the need to know all these phrases at the development process

the replace-list could also contain a generaly list off
letters/phrases
which might be lead to output-errors or which simply unwanted
this list should be processed always on all incomming data

but these lists should be keept either in the specific movie-DB
or for all in an other settings-db or how ever a simple list
(again users-preferences)
(on export/import the user should asked for the language,
especially if he has choosed view-time-processing)

and so after a while(may be) language-specfic replace-lists
could be shared here in the forums or where ever

I know that native english-speakers dont think so much about these language-specfic things
but all others may do a little more

these is one of the most important features
Sadly to say, I miss in most apps

this are only a few ideas I'll had to handle this language-specfic things
without having so much development-work
on handling unknown phrases (which besides might be wrong)


@nostra special greetings and thanks
while I'm reading here, recognizing your allways friendly open ears to all questions
which is not allways usual

cu meriator

Navigation

[0] Message Index

[#] Next page

[*] Previous page