View Single Post
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#19
Originally Posted by ysss View Post
Sounds like an awesome project!
But the requests list seems to have grown unnecessarily long already.. I think the features list has to be cut really short to cater to the biggest audience first so the development can go swiftly and focused on the core functions intended..
Then implement the rest as plugins\future developments.
They're all going to be plugins, anyway, so the least I can do is put placeholders there so people can see the ideas, and join in on implementing them. Most of the ideas outlined here were not THAT difficult to implement (CPU/RAM the easiest and location being probably the most complex). In any case, having some ideas how things might develop in the future makes it easier to avoid inadvertently placing nasty dev roadblocks for future development.

Oh, a more descriptive name would help too
It's an established fact that I'm bad at naming projects It started off as something that you know, herds applications out when the weather is nice and there is grass, takes care they don't run away, and such... hence the shepherd association. Thought it would be lame calling it YASA (yet another scheduling app), Puli would probably also mean nothing to most of of the world... But I'm open to suggestions, at least until the stuff enters extras.

PS. For people too lazy to click on the above link:
 

The Following User Says Thank You to attila77 For This Useful Post: