Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backend API of moving one or multiple nodes to an other location #3

Open
fodor0205 opened this issue Aug 16, 2011 · 3 comments
Open

Backend API of moving one or multiple nodes to an other location #3

fodor0205 opened this issue Aug 16, 2011 · 3 comments
Labels
back end
Milestone
Luxury features

Comments

@fodor0205
Copy link
Contributor

No description provided.

@fodor0205
Copy link
Contributor Author

The backend gets 5 parameters:

  • The current parent ID of the nodes
  • The moved node (or nodes) ID(s)
  • The new parent (always one node ID)
  • The ID of the node, which is above the new position (or 0 when it has to be on the top)
  • A boolean if it is an atomic relocation (the childs of the node is going to be childs of the original node's parent), or it is a tree-style relocation (with the childs)

@ghost ghost assigned fodor0205 Aug 16, 2011
@fodor0205
Copy link
Contributor Author

Tree-style moving is done.

In which new position should the atomic relocation put the childs of the moved nodes? @Wizek

  • at the end?
  • at the top?
  • after the moved ones?

fodor0205 added a commit that referenced this issue Sep 6, 2011
@fodor0205
Added tree-style moving of node(s) #3
1b78ffb
@Wizek Wizek mentioned this issue Apr 10, 2012
Open
@Wizek
Copy link
Owner

Wizek commented Apr 10, 2012

@Fodi69 Is this issue still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
back end
Projects
None yet
Milestone
Luxury features
Development

No branches or pull requests
2 participants
@Wizek @fodor0205