I think its fair to say the Task repository hasn't taken off, even though it is a great idea. Today I can see 8 tasks in there, which is not a lot. I want to share my opinions about why it is not a raving success, because I think it should be.




1) No standard conventions: Some people use underscore in the names, others have spaces. There are no rules as to what the description should contain. Some people explain the parameters needed, some don't. We have conventions in our 'code' in VisualCron. By importing tasks from a repo where conventions are all over the place, I make my own code look like a mess.

2) No minimum standard: I know this is hard to implement, but having tasks like this in there should not be possible:


3) The resulting task name i awful.. sorry: A simple ToUpper task gets this horrible name (see pic below). I am not going to use that name in my tasks. It will make things harder, not easier to read and understand


I think at least 1) and 3) need to be adressed before the task repositoy becomes a success. My 2 cents anyway

I think its fair to say the Task repository hasn't taken off, even though it is a great idea. Today I can see 8 tasks in there, which is not a lot. I want to share my opinions about why it is not a raving success, because I think it should be.




1) No standard conventions: Some people use underscore in the names, others have spaces. There are no rules as to what the description should contain. Some people explain the parameters needed, some don't. We have conventions in our 'code' in VisualCron. By importing tasks from a repo where conventions are all over the place, I make my own code look like a mess.

2) No minimum standard: I know this is hard to implement, but having tasks like this in there should not be possible:


3) The resulting task name i awful.. sorry: A simple ToUpper task gets this horrible name (see pic below). I am not going to use that name in my tasks. It will make things harder, not easier to read and understand


I think at least 1) and 3) need to be adressed before the task repositoy becomes a success. My 2 cents anyway

Thanks for these great suggestions thomas. I do believe you have a good point in them - I also think it's a bit "hidden"/not presented well enough yet to see much usage with the average visualcron user.

We'll definitely brainstorm a little bit and figure out how to make this more appealing, because like you mentioned - it really is a great feature if it were to take off at some point.

---

Trying to view the task with the name "Powershell" crashed my 8.5.5 client.

Hi michael

Yes it really is a great feature and should be used more. Maybe one needs som kind of code review before a task is accepted. Something like github where somebody has to accept a pull request .