Working on 1.7.9 and advancing version 1.8.0

Post comments about KeyNote NF code and discuss with other developers
Forum rules
Rules | Pull Requests
Post Reply
User avatar
dpradov
Site Admin
Posts: 17
Joined: 27 Aug 2010, 16:40
Location: Seville (Spain)

Working on 1.7.9 and advancing version 1.8.0

Post by dpradov »

I know many of you are waiting the new version, 1.7.9. I have offered a Beta version, and I'm looking forward to release the final version, to concentrate in some other improvements I need (and that will be useful to others, I'm sure)

Since 17 september I could not proceed with the development, because I've been on vacation and then I've been reviewing some emails, issues, trying to organize in some way the project management (for example with the help of this new forum), etc.
My current development working is related to alarm management, as indicated in Issue 193 - Adjustments in alarm window

Personally I don't need that improvement too much, at least for now, but I know that is a demanding feature.

Although I marked the issue Issue 171 - "Node information Panel" to be included in the 1.7.9 version, I think I will release that version without that functionality, so that it is available, soon. That is also a very requested feature, and I think that perhaps I can't reuse the code of Marek (to not reinvent the wheel) cause I have verified that in Tranglos web there is now a reference to that version (it wasn't when I began this development). Although that will help me a lot, I will have to carefully check it.

Among the features I need and I want to include in 1.8.0 are the following:
  • Allow to make visible or invisible only the childs of a selected node
  • Enhance the search panel:
    • Allow searching only inside the node names, and considering the checked state.
    • Allow using boolean operators
    • We should be able to conmute between filtered mode and not filtered mode, without repeating the search.
    • Allow to include in the filtered set all the childs of a found node
    • Actually nodes selected by filtering are resalted in blue font. That should be only an option, because doing so we cannot see their own formats, and we can need it. We can resalt that a node of a filtered set is included because satisfy the search condition and not because it is a parent or a child (if marked the corresponding option) in other way.
    With some of that options, we can exploit the use of tags ad-hoc. Currently KeyNote NF doesn't understand of tags but we can easily overcome that limitation for now defining our own tags with texts of some predefined form, like enclosing a word between square brackets, for example. We can use that kind of tags inside the content of nodes and also in the name of the nodes. The latter allows, with the new option I want to include (searching only in the name of the nodes), to quickly filter a note or notes.
    For example, currently I'm applying that kind of tags having nodes named as:

    "Something wrong is happening.. [E]"
    "There is another thing to improve.. [F]"

    In that example I'm assuming that [E] means "Error" and [F] means "Functionality" or "New functionality" (or what we want..)
    That way I can filter a note viewing only nodes referring to some bug or error to resolve, searching "[E]"
  • Create dynamic notes, with the help of mirror nodes, including all the nodes satisfying a certain search criterion. This note will be updated incrementally, reviewing each modified node when abandoned, to verify if satisfy the condition, and so to add or remove it.
  • Moving a node to another note shouldn't break hyperlinks pointing to it
  • Allow the use of embedded images in a similar way to what we can find in forums like this, that is, including a link to an image and being able to see that image or the link, depending the mode we select. That links can be relative to the .knt file.
I recognize that, although the compressed format allows to include images without making the file growing too much, at least compared with the uncompressed format, the file is considerable bigger and the time to save is greater. For that reasons currently I don't use images in my .knt files, and I would like to do it, really.


And of course I will include in 1.8.0 the correction of bugs, and some others improvement requested by some of you (including "Node Information Panel")
Post Reply