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

Feature: task list #21

Closed
Maschette opened this issue Jul 22, 2019 · 6 comments
Closed

Feature: task list #21

Maschette opened this issue Jul 22, 2019 · 6 comments

Comments

@Maschette
Copy link

Similar to the project list idea (#3) (which I assume would just list projects?) would be to have a todo_list() option where you can output the the task list for a project in a nice html format.

You could use this internally for the project list function where project list uses the project title as the header of a tabset and calls task list to populate the tab.

It is hard with githubs auto formatting but something like:

project_list(projects=c("project_1","project_11","project_42"), tabset=TRUE){
if(tabset){Title<-"#Project list: {.tabset}"} else(Title<-"#Project list: ")}

(' should be a back tick but github formats them)
'r Title'

.## 'r view_jobs(projects[1])$name'
'''{r}
todo_list(projects[1])
'''

which would output:

`#Project list: {.tabset}

Project 1

alll of the things....
`

ok tabset doesn't for in issues but I think it makes sense....

@djnavarro
Copy link
Owner

I like this! I'll see what I can do 😁

@Maschette
Copy link
Author

It did occur to me that I was slightly more confused than I originally thought about the difference between a job and a project so I am not sure how it would work (or the package) across multiple projects?

@djnavarro
Copy link
Owner

Yeah, in my ideal world I'd have referred to "projects" everywhere instead of "jobs" (and that's how I wrote it initially), but I felt that would cause confusion with RStudio projects. So instead I've used "job" throughout (where one job could map onto one RStudio project or one git repo, or whatever), and allowed each job to be linked with a set of "tasks". However, there are still some stray references to "projects" in the documentation and the API (e.g., goto_project() should really be goto_job()) so right now it's really confusing.

@Maschette
Copy link
Author

Ahh ok that clears it up in my head projects were projects and jobs were tasks.

@djnavarro
Copy link
Owner

Opened #24 as a reminder to fix the documentation on this

@djnavarro
Copy link
Owner

It needs some tidying, but here's the basic idea. There's a new function view_site() which I'll probably rename later, and it generates a tabbed HTML page as output. It has tabs for the task list, the job list, the table of known people and a details tab that allows you to click on and expand a job. Some screenshots below. Setting aside the fact that it's not very pretty right now, is this the sort of thing you were thinking of?

Here's the job list:

Screenshot from 2019-07-26 17-20-36

The expandable details tab (obviously needs nicer formatting):

Screenshot from 2019-07-26 17-21-00

The tasks view:

Screenshot from 2019-07-26 17-21-20

People tab:

Screenshot from 2019-07-26 17-21-47

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

2 participants