As the development of FileTagger started partly months ago, the DEV-Blog sadly starts somewhere in the middle of development. Although, that much isn’t done due to prototyping of other projects… But let’s look at the progress of this weeks development.
For those not familiar with software development, ‘Refactoring’ describes the restructuring of code, altering its internal structure without changing its external behaivor.
Some parts of the architecture weren’t as good as first thought, therefor these got changed accordingly, creating a complete new structure for some features, to improve their usability and make development easier and therefor faster.
As the previously planned implementation of the more advanced meta-data isn’t the best idea for handling this data, I thought about ‘Data Groups’.
These groups will be configurable through the settings menu and contain multiple fields to store data in. This data is then saved as one set and therefor will be perfectly suitable for meta data like characters or actors in movies, band information for music and so on.
Whats already done?
As already many hours where invested developing FileTagger, whats already done? Good question, let me answer it as good as I can.
An already bretty good looking UI got implemented, containing buttons and other elements for all features planned for version 1.0. It’s not 100% final and still could use some improvement as well as removing many bugs. Ideas and thoughts would be very usefull as adjusting the UI now is much easier than after implementing all features.
Besides the UI, you’re already able to tag all your files with self written tags as well as simple meta data like the length of the movie for movies. That said, the more complex part of meta data, characters, actors etc. made many problems due to an unsuitable architecture making way to many problems and using nearly a week worth of work (approx. 10h) for effectively nothing. Mainly because of this, the currently ongoing refactoring was started.
As this is mainly it, another question arises….
What’s still missing for version 1.0?
First of all, version 1.0 was planned with more features than it will has when it’s released. This is due to other projects, currently just prototyped and not yet publicly announced. As both tools need to be done until the end of the year (and yeah… it’s nearly november already) some, mainly visual, features where cut and moved to the next release in order to hopefully have enough time for both tools.
But v1.0 will definitly release with these features:
As described on the main page for FileTagger, the meta data will contain, who would have thought, meta data of its files. But just to make sure, the meta data won’t be written to the file directly and is only stored within FileTagger. It’s definitly planned to add as much meta data as possible directly to the file.
Also file categories will be part of v1.0. What is meant by categories is strictly the file type of the file, which will be editable by the user. You will also have the ability to create custom categories with your own defined meta data if you wish.
The settings is the best part of FileTagger; well at least it will be when all currently planned features, beyond v1.0 are implemented, as you will be able to customize nearly everything to meet your demands. Thats the main reason why FileTagger was started. Other, already available ‘file tagger-tools’ didn’t have everything I hoped/expected from a file tagging programm. Within the settings in v1.0 you will still be able to customize your viewport to display the info about the file, you are interested in. Also you can add and edit categories and tag groups here and some more little things.
As you may guess there is still a lot of work to do, and time is limited, not just because of the self set deadlines. But if you want to know why for example ’10 h’ of development in this project are considered ‘a week full of work’ for me; you may want to have a look at our FAQ