Tabbles with index 2012-07-05T05:39:44+00:00

Home Forums Feature requests Tabbles with index

  • Author
    Posts
  • Rinat
    Participant
    Post count: 5

    Okay, I see myself that idea about all that hashes and "Data dd/mm/yyyy" tabbles is a bit specific and it will tear the conception into peaces.
    But 😉 what about making some tabbles to have numeral suffixes-endings which can be used to combine or to make ranges when combining?
    For example, I make Tabbles Year 2001, Year 2003, Year 2006, Year 2008 with a template Year ####, where Year is my own word, and #### is a wildcard for any integer 4 digits value. All of that helps system to manipulate with these tabbles using also mathematical operations >,< and creating ranges such as Year 2000-2007, which means, can you imagine :mrgreen: , just a combination of the tabbles Year 2001 or Year 2003 or Year 2006. In GUI it can be implemented, for example, in the following manner: you right-click one of the tabbles Year XXXX and see there is a menu item "Use the field from Tabble", click there and get a new tabble (which can be temporal or normal) with and ability to make range or comparison operation (Year ####>2001, Year 2001-2004, 2005-2008, similar to the pages field in printing dialog), which looks like you type inside the template >#### or <#### or ####-####.
    Also it can be implemented in a form of nested tabbles: Parent tabble Year and child pure digital tabbles 2001 etc. The main idea is to find the tabbles with values (which are made using wildcards or digit fields) with flexibility other than selecting one-by-one from rather high amount of tabbles.

    About enumerations – this may be too complex to be neccessary at all, but I’ll explain. Using not only bare numbers as described before, but also literal values from a kind of table/list (obviously – days, months names, all the things in our life, that have strong sequence and own names rather than numbers).

    😆 Don’t tell me, that you already have a solution for all of that

    Good luck

  • mrdna
    Participant
    Post count: 220

    This looks kind of like it could be handled with a logical OR for the most part? The idea of being able to run mathematical operations on tabbles is definitely intriguing but I wonder if it might either balloon the size of the DB or slow down the program if not narrowly implemented – possibly via a separate search panel?

    I have asked for auto-tagging based on file date and time (though it hasn’t made it into release yet…) would that help you in any way?

    regards,
    jay

  • Rinat
    Participant
    Post count: 5

    "mrdna" wrote: This looks kind of like it could be handled with a logical OR for the most part? The idea of being able to run mathematical operations on tabbles is definitely intriguing but I wonder if it might either balloon the size of the DB or slow down the program if not narrowly implemented – possibly via a separate search panel?

    Well… I cannot see any reason to baloon the size of the DB and to slow down the program. This feature just uses the DB, but doesn’t change it at all. Also the operation itself is the same as making an OR combination of some tabbles, but with slightly added machine work to generate only the names of other tabbles to work with.
    The operation should be processed only when you are combining tabbles to work with a set of files, this also can be done with a separate search panel, although you can make a new combined tabble in general way but through a kind of wizard which will ask you to fill the wildcards to define the parameters of operation.

    "mrdna" wrote:
    I have asked for auto-tagging based on file date and time (though it hasn’t made it into release yet…) would that help you in any way?

    Really not, I meant that the date tabble is about some inner date of the information in files, which is not the same as the file date. For example, date of the book issuing, and the file with the book. I can add this tabble manually, it’s not about auto-tagging, it’s about autotabbling when there are already some tabbles defined, with some sequence in nature.

    I think, the way to make normal DB queries (such as of SQL) through the tabbles conception is rather simple, light and natural. And it’s rather flexible.

    A propos, autotagging also could be done with some inner info, for example id3 tags in mp3 files (but not for me).

    Good luck,
    Rin

You must be logged in to reply to this topic.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close