Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- [SOMETHING LIKE CONKY - but more efficient]
- * Information
- ** What information is needed?
- *** Examples
- **** Time and date
- **** CPU (load,number,frequency,temperature)
- **** Memory (free/used)
- **** HDD (free/used/temperature)
- **** Battery (capacity/remaining time)
- **** Network (connection/quality/bandwith)
- ** How do we get that information?
- *** Possible Sources
- **** acpi
- **** /proc/
- **** powertop
- **** du
- * Optimization
- ** How do we reduce unnecessary operations?
- *** Refresh information context-based - That means that e.g. free space on the harddrive doesn't have to be update as often as the cpu load.
- ** How do we organize memory?
- * Output
- ** How do we print stuff on the screen?
- *** Dzen?
- *** Own solution?
- **** How do we achive bar-like behavior?
- * Language
- ** Pure C as it is faster!
- *** How "structured" should the programm be?
- *** Easy approach: Array with [name], [command], [timing]
- *** Use fopen on files like /proc/meminfo -> Loads a lot of unnecessary data but is there another way?
- *** Don't use system as it outputs directly...
- *** Are real systemcalls faster than <stdio.h> functions?
- ** Why not use python?
- *** Advantages of C are more critical if a lot of data is handled...
- ** Which libraries are needed?
- *** Do we need anything non-standard?
- * Configuration
- ** How much should the user be able to configure the programm without having to recompile it?
- *** Should this even be possible?
- *** Loading a configuration only takes constant time. How about evaluation? Does having a dynamic configuration anyhow influence the programms performance?
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement