Ability to change the permission setting of a workspace once it has been created
Ways to improve nodes
to be able to set your nodes and links to be different colors
the option of having variety in your node shapes.
using tags to show color
putting color in the nodes themselves
ways to make the workspace work for you
By this I mean that you could choose to move one node, and have all of it's child nodes move with it.
Add a lock child node feature to the select menu or add in the node properties?
Ways to make moving and connecting nodes easier.
To be able to select all nodes within a designated area and move them all at once. Somewhat like the "lasso tool" in drawing programs.
a way to display multiple attributes of a single node.
to be able to attach files to your workspace
Making workspaces easier to find.
Adding a chat feature to workspaces
aViva Sedai: I thought we were calling this Number 6? *grin*
Be able to grant permission to edit, or possibly even view, on a node by node basis.
You can make a workspace private to public, and allow users A, B and C to view it, and allow users X, Y, and Z to edit it. Maybe if you feel like it you can make workspace public, but hide it from certain users.
To be able to choose several nodes to move at once. Similar to shift-clicking on icons.
I think some might find it useful to be able to click on a parent node and see a visual trail through the other nodes. Maybe a "pulse" of color would travel down the links starting at the selected node. Or the 1st generation would turn red, and then when you push a button they would return to normal and all of it's 2nd generation would turn red, and so forth.
Be able to zoom the workspace display with the mouse's scroll wheel
Provide some mechanism to have links to external websites. I have found myself wanting to make a node refer to a particular company or product.
Be able to make a "legend" where you can label colors
Maybe they are already in place and I have just not found the list? It's easier to use the keyboard than to switch back and forth with the mouse.
I believe this node refers to a way to tell if a given node has text. If so, it's done (italics).
Instead of having to create two separate links between two nodes to get arrows pointing both ways (which would then have the labels overlapping so only label could show, anyway), how about two-way links? (Siblings?)
Notation objects other than nodes and links.
These are just visual objects that exist behind the node graph that allow visual demarcation of groups of nodes. These boxes should have titles and note text of their own.
Extending this, a node could be linked to a group box, representing an abstract relationship to a sub-network of nodes. This simply equates to a node that can "contain" other node groups.
Comments are not connectable, but are just short text boxes that can be positioned in the workspace. This can also be implemented as an alternate visual appearance for nodes (since many workspaces just throw in another node and give it the comment text as a name).
How about a Favorite Worspaces list? Add an 'owned by' column to the 'My Workspaces' list, and you can combine the two.
My profile should save my last search, including the sort order and page I was on in the 'Other Workspaces' list.
A list of saved searches would be great, too.
--Dks says: Good thought. It looks like profiles are our top story right now; I'll talk to the devs about putting this in the profile data.
It would be convenient to be able to search for worspaces created by a specific user, workspaces a given user has write access to, as well as public workspaces a given user has edited.
Some of these are obviously pending permissions changes.
Basically a private workspace that is visible and or editable by a named list of users, or by a group of user names. That would make Kayuda useful in private brainstorming sessions for new ideas etc.
The ability to backup my data or export to a printable format would be nice.
1. Ability to import parent / children relationships from tabbed text files.
1.1 This subheading, for example, would appear as a child of 1.
1.2 This subheading, for example, would appear as a child of 1.
1.3 This subheading, for example, would appear as a child of 1.
2 This heading, for example, would appear as a sibling of 1.
2.1 This subheading, for example, would appear as a child of 1.
It would be nice to have the workspace either automatically rearrange nodes to prevent overlapping, or take advantage of the subtree feature to show all overlapping nodes under the cursor.
If option 1 is chosen, perhaps make this optional (disabled by default - see background map node) with a tooltip prompt the first time an overlap occurs.
If option 2 is chosen, this would be a good feature to have enabled by default. It could also eliminate the need for the Node list panel for those who are very familiar with their workspaces.
Or to search for users in general this would help greatly in inviting people to participate in a workspace. When you're not sure of exactly how they put their name when they signed up.
For that matter, simply and alphabetical listing of users would help.
being able to invite more than three people to work on a project would be really nice.
The ability to sort or filter k-spaces would be helpful, either by a system of tags and filters, or by a folder heirarchy.
קבלת פניה
תיאום המשך
טיפול מעקב
Allow the background of the workspace to be customized with an image file, stored/referenced on the local user's machine if there isn't sufficient file storage bandwidth (especially for high-resolution images). Users that wish to share the background images stored at their system can easily upload to an image host and reference file placement within the workspace.
Have custom backgrounds locked to the node map.
Create rotation mechanism allowing users to 'turn' their nodes - simplest way would be to add a rotation command in the select menu or have a mouseover event when hovering over the corner of a node (with a different cursor icon appearing).
Possibly import map data with a linked google map or mapquest map. Bandwidth issues may make the application extremely laggy, however.
Multiple links from a single node that expand in multiple directions and do not overlap.
The abillity to move a group of nodes to a different layer (rather than 1 at a time) would save tons of time when you finally decide to put in a layer for that huge subtree of your project.