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.

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

User interface for managing argument graphs in a project #98

Open
tfgordon opened this issue Oct 18, 2014 · 3 comments
Open

User interface for managing argument graphs in a project #98

tfgordon opened this issue Oct 18, 2014 · 3 comments
Assignees
Milestone

Comments

@tfgordon
Copy link
Member

On project pages, add user interface elements for managing the argument graphs of the project:

  • listing existing argument graphs
  • selecting an argument graph, navigating to the argument graph page, for example by clicking on a hyperlink.
  • creating a new argument graph
  • deleting argument graphs

Commands for editing and deleting argument graphs can be on the argument graph page, rather than the project page.

Commands for importing and exporting arguments are in a separate issue.

@tfgordon tfgordon changed the title User interface commands for managing argument graphs in a project User interface for managing argument graphs in a project Oct 18, 2014
@tfgordon tfgordon added this to the Dec2014 milestone Oct 22, 2014
@sekaiser
Copy link
Contributor

further discussion needed. implementing this feature involves a heavy rewrite of routing logic in the rest api and frontend.

@pallix
Copy link
Member

pallix commented Dec 11, 2014

I confirm that "listing existing argument graphs" requires a heavy rewrite of all most all routes. Not doable for M2.

@pallix
Copy link
Member

pallix commented Dec 15, 2014

The path should probably be something like /:pid/ags/:ag and not use the ':db' parameter anymore as it is not precise enough (there are different kind of databases (schema) in the project)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants