live-keys / livekeys Goto Github PK

On scripts that require heavy computation, the GUI blocks for writing.

Need to switch from main.qml:

newItem = Qt.createQmlObject(
                                    "import QtQuick 2.3\n" + tester.program,
                                    tester,
                                    codeDocument.file.toString() !== '' ? codeDocument.file : 'untitled.qml');

With a separate implementation, info found at Qts sources, in Qt/Src/qtquick1/src/declarative/qml/qdeclarativeengine.cpp

Set global levels, and on a per channel basis:

Levels{
    white : 253 // from 0 to image max color, default : imageMaxColor
    black : 20 // from 0 to image max color, default : 0
    contrast : 155 // from 0 to image max color, default imageMaxColor / 2
    channel : { 0: [0, 255, 124], 1: [0, 255, 124]}
}

External modules fail to load in certain scenarios. Check cause.

LevelsBox{} adds sliders, and histograms to an image levels adjustment.

I will detail this later on.

http://docs.opencv.org/2.4/modules/stitching/doc/high_level.html#stitcher

Add HistogramControl, adding a dropbox to select image channel

ColorHistogramControl{
DropDown{...}
ColorHistogram{...}
}

Preview mode allows Live CV to open files without the editor. (Suggested command line argument flag '--preview')

Add support to determine auto-adjustment levels for an image.

Add HueSaturationValue{} component.

Compile started and compile ended signals from the engine should be available for the application in order to start specific behaviors during each one.

The main script interface defines the main project file. Currently, it's function would be to configure command line arguments and set up the version:

Main{
    args : [ 
        {key: ['r', 'read'], type: required, describe: 'input file'},
        {key: ['w', 'write'], type: required, describe: 'output file'}
    ]
}

Suggested names : Main, CVMain, MainScript, Script

Merge a set of hdr photos.

http://docs.opencv.org/2.4/modules/video/doc/motion_analysis_and_object_tracking.html#calcopticalflowfarneback

A multi slider lets you have an unlimited number of slideable elements in the same box. When a user
double clicks, a new slidable element is added. The dynamic property disables adding of new slider elements.

MultiSlider{
    id : ds
    elements : [0, 100, 255] // number of elements and their position
    dynamic : false // default: true
}

This is needed for the code completion model.

Add support for LK Optical flow tracker and MOG2 background extractor.

A Live CV project will be a directory containing one or more qml files. Project directories can be opened, and specific files can be set as the startup files.

We need a file-tree view in the GUI. A toggle on/off option. A 'set as startup' option. And an "Open Project" button.

This requires a custom parser to be implemented, since the scripts need access to command line arguments as well:

livecv.exe [--option value --option2 value] script.qml [args]

http://docs.opencv.org/2.4/modules/video/doc/motion_analysis_and_object_tracking.html#backgroundsubtractor

To not clutter the main script section, I would create a CommandLineArguments object, then use it as:

Arguments.qml

CommandLineArguments{
    CommandLineOption{
        key : ['r', 'read']
        type : 'required'
        description/help: 'Input file.'
    }
}

main.qml

Script{
    args: Arguments{}
}

RGB, HSV, Greyscale histogram.

ColorHistogram{
    type : RGB/HSV //default : RGB
    image: input image
    fill : true / false // histogram draw type, default : false
    channel : 0 // optional, default -1
}

Iterate each channel or selected channel from the image and calculate histogram. Display all channels overlapped if no channel is selected.

http://docs.opencv.org/2.4/modules/video/doc/motion_analysis_and_object_tracking.html#backgroundsubtractormog

It would be very useful if I tested the processing procedure and it works, now i want to add the processing procedure (API calls) to my application source code, i can just open the log window, copy and paste to my source code editor, followed by minor modifications to fit into the code context.
that will save a lot of time for developing.

i would also suggest to include both python and/or c++ calls