andrehunter / openassembler Goto Github PK

There is an entry is needed on the timeline to store the tree-output node..
same attribute will be needed for the node000000 (scene settings node) on
the same way like in the endframe beginingframe settings..

This is not an essencial changes but will affect the speed of the gui.
It will affect the complet dbase management script and maybe some other gui
element likethe main gui windows.
I have to kill the old "keep runtime and connection list in memory"
variables to use less memory and to be sure that the settings are handled
on a right way.
This have to be done before implementing the save-load-new feature. (or
would be nice)

 with all the acceptable variable inside, checking if the value is correct
if not, it will replace it with the type 0.

Opening a saved scene will multiplicate the recorded connections on the
inputs....

There will be a need for empty the recorded connections before we preparing
for the new one...

There are only one type of node shape untill, so we need to make some new ones.

1. Node with no input
2. Nodes with no output
2. Nodes with no input and output (tis is good for predefination and some
general setup things)

New contollers will save the settings back imadiately to the
self.startfame... variable. And I have to care about the changes to save
the frame range back when I set it on a timeline.

 it would be a nice to work with queue on the server

 And when the connection is broken the in need to remember to the latest
value of its ex-output pair.

6 different testnode will be needed.
For test reason it will edit text files (sequential files if it is needed)
So I need the followings:
TXT_FileIn (seq. able, no input)
TXT_In (a manual node to type texts in, no input)
TXT_Combine (combines two text, 2 input)
TXT_Replace (looks for a sting and replace it with an other, 3 input)
TXT_FileOut (saves the txt file, 1 input no output)
OutputCollector (a node to collect several input nodes, and batch run
them.. this is a no-in no-out node)

OANodeCreator is a tool to create new nodes and place them on the slider bar...

I need to rewrite the folder handler part (not yet existing :D) To be able
to use the same script by several user. It have to find the userfolder
automatically and it have to check for the temp folder too..

 The idea is to first create the node, than set the settings with the
already represented writebacksettings function

Separator will be good for makeing a little space betwean the different
contollers. Example:
______________________________________________
Name of the following contoller group
______________________________________________

I need to collect the usefull function to generate a header file, as a
collection of the most important functions.
Nice unique nameing, and so.....

During the time I will do this, a deep code review will be needed, and this
will be the perfect occasion!

 This is the same issue wit the menu selection of the nodes.
But this is more sophisticated..

Well, this is just a checker cycle for the mouse-movement script

Write back the connection settings to the runtime xml file.
This is esencial to be done before the run mechanism developement.
Maybe there will be some changes in this part later when the running is
under development so it has to be flexible for changes

This is essential to save the scene based settings (frame range,
description...) It will be a new node in the runtime xml with the id of 000000.
I have to make it sure that the other nodes id never can be 000000
Structure can be variable later...

I need a color picker interface.

Well, this is just a checker cycle for the mouse-movement script

 I can simply switch off the value checker method...

Maybe we have to duplicate a node, so I need to write a node duplicator.
Button will be next to the delete.
There are two option needed:
1. Duplicate copy the settings but it will be a free node after then
2. Instance except the imputs everything else are linked to an other node
(mayabe it is nice to have an attribute on every node that this node is the
source of something otthers, and when I write back the settings, this
script could check if it is a source and the write back the settings to the
otther node stoo... and on the pref. panel the things would become yellow
or something like this...)

 This ones have to be marked as a different color? I do not think so...

I need to find out how..... but this will be the first step for the
automatic node recognation system

It would be nice to improve the aprse loop, becouse it is quite restricted now.

 Yep, point and vector can be the same, but color need a proper color picker
we can use 1 line in the xml to store this values for examples like this:
;128;252;015;

It can collect the nodes from separate dirs. (user level, show level, comp.
level)
It needs to automaticaly short and arrange the nodes...

We need to check the connections if input and output are compatible in a
connection.
There will be a need for a new dbase handler to ask and compare boot the
parameters when a connection is made.
It will require a small tweek in the mouse handling script too.

I have to redesign the node description database to be more flexible with
te connection.

The new method will trnasfer the inputs to the Data subnode with several
attributes like connectable and connected for the nodes which are actually
connected (we need to take into consideration the multiple input connections)

This will affect the base node shape generation with the extended feature
to be able multiple-inputs to connect
Some changes is needed in the mouse handling and checking process to make
sure that we can conect the multiple nodes
Will affect the dbase handling and the xml structure too...
Rihgt in time there is a pooseability to re-think the complete structure of
the node description xml

 Yep, this is an interesting part to get back values forexampel from an
opengl window..

 if there is no "" in the file, than there is no space in the variable, if
there is a "" than it contains a multiple-space variable.

 I o not know the solution yet.

In the preference plane it would be nice, If the values geting be saved
without pressing the enter key, it is quite boring to press an enter
several times to input a matrix.
Maybe when the preference plane is refreshing than it would be nice to save
all the walues..

I have to investigate this, I am not sure it will work or not.

.. or maybe the enter key event bind can be changed to anykey or so...

This is for adjusting colors.
I will make a new window where you can adjust the colors. I am not
satisfied with the colorchooser integreted in python so I will create my
own one.

In the preference palne htere will be represented like a label and a
rectangle filled with the original color. 

I think the best solution is the hex color value excange inside our
programcode.

The problem is that the mass-text is writen back to the note section.
Solution: I need to separate the settingsnode note, and the masstext variable.

:)

Need to check the node deletion script to adress this...

There are some problem with the layout under running it from OSX.
(Maybe)The problem is come from the different button and font types..
Need to check...

Just an optional thing. There current mechanism which is just made is not
working so nice, so I need to redesign the sliding process.
Criterias:
1. Slide only when the controller list is longer than the pref window.
2. Not to float over the section border

Multiple node selection for moving nodes and for deleting nodes

If you click a node it will be selected and holding the shift key down you
can highlight other nodes too. You can move the selected nodes togother.
You will be able to delete the nodes by clicking the del button on the
timeline.

It will affect the mouse handlig script and maybe the dbase management. I
need to add a new global variable (an array) to store the nodes which are
selected.
I need to add a nev tag for every item in the node to mark as "selected"
Need to modify the deletion script to be able to delete multiple node and
need to re-think the connection redraw.
Maybe it would be nice to use area selection with the mouse..... maybe..

This is a low priority comment now... maybe for for later milestones

Essential!!!
I need to implement the save-new-load features.
Save ass too....
It will be a standard xml file, containing everything which is inside the
scene.
Load have to reset the gui at all and load the settings

I need to save back the node positions too, to be able to load the scene again.
Essential to do it before the run mechanism!

It can be a bounding-box error.

I am not sure this is good, but I need to have a try..

This is only appears when I delete the nodes by the right-click menu.

 I o not know the solution yet.

It is not showing the sourcecode for the python script

Write back every node positions to xml to prepare the save option.
Maybe the release event is good for this....