Originally Posted by
MrGlenn Purchased! Sounds like a great addition to the OS, now that it will work headless.
Thanks a lot! :)
Sorry to let you wait so long for a reply. But I wanted to clarify some stuff before I got able to give you a qualified reply. :)
Originally Posted by
MrGlenn I like the LED feedback, a little confirmation the copied text is actually saved, curious to see what you are working on. :)
This is my current to-do-list for ClipMan:
- interchangeable color themes for the active frame of ClipMan
- mechanism to filter for write protected items in the list
- some kind of tag-cloud at which you add different "tags" to write protected items, later you're able to filter for those tags. You will get able to create tags at example for "Work", "BBM", "garbage", "draft", "CrackBerry", "shopping", "Important", "Family"
(But this feature may need some time until I get able to implement it. I have just some blueprints in my mind)
- maybe a "search and replace" function while editing a text
Originally Posted by
MrGlenn I would love for an app like this to get its own Hub entry. Just imagine for example having all your locked entries available in the Hub, easy access!
Brilliant Idea! Thanks.
I'm not sure how hard it may be to do and what is really needed. But it needs to apply for a "App Permission Request" like at long running headless apps and I just requested access for ClipMan some minutes ago at BlackBerry. This may need several weeks, I guess it was about 6 weeks for ClipMan headless if I recall correctly, but as soon as I got the permission I will look into how this could get possible. :D:yes:
Originally Posted by
MrGlenn Also it would be great to see an option to 'merge' saved entries!
I thought about this several months ago but find it personally not a useful feature.
The question here is how it should work in detail. In which order should the saved entries got merged and how should the user control this or get an idea how it works.
I'm merging myself over here often several items. I just copy one part to the clipboard and go to the second part and paste it exactly there were I want it. Sometimes in the beginning, sometimes at the end and in the most cases somewhere in the middle.
In my opinion simple enough and a well working mechanism. Fast enough and you have during the whole process the full control.
But if you could provide me a better idea of a use case and help me to stop doubting about the user expirience I will look again into it and maybe put it onto my 2-do-list. :)
I'm always open for suggestions.
Originally Posted by
MrGlenn And finally an option to 'clear clipboard' would be nice, I do not think the OS has that option either...
Yeah, there is not such a option. I'm also not sure about the use case but I will put somewere a button to do so. But maybe it is needed to put at least a whitespace into the clipboard. I will check this out. Thanks for the suggestion! :)
Originally Posted by
MrGlenn One thing though: out of all the headless apps I have running now, ClipMan seems the most active (almost never idle). It does not use much cpu/memory, but I thought it worth mentioning.
Yes, I tried to optimize it as much as I were able to do. But a minimal consumtion was unavoidable. If only the headless module is running it needs below 0.2%, the most time even below 0.05% CPU usage (hard to judge it over here on the graph because of the scale) and since the CPU is only one of several parts in the device which consumes battery power I see no problem over here. :)
But in case somebody is reading those lines over here and is sceptical, I have a additional thing to reassure everyone. The headless part goes idle, in average 750ms after the screen gets turned off. It consumes in this state every 30 seconds for a short time below 0.01% CPU power and gets then again completely idle. It gets back from sleeping less than 50ms after the screen gets turned on. So you can't see how it goes idle in the overview of the device monitor.
Since the headless module of ClipMan is only really active while the screen is active and sucking 100 to 1000 times more energy out of the battery I would be surprised if anyone will see any kind of impact in stand by time.
Version 2.0.0 was approved for public release by the BlackBerry World testing team without any problems and discussions. Despite this fact I've rewritten some parts of it just yesterday to improve the overal stability and added a fall back mechanism to be even more reliable. It should appear as a update at the beginning of next week and it will need then even less memory while active. In case only the headless module is running the soon released version 2.0.1 will need only 1.2 MB RAM instead of 4.4 MB like the current version does. :cool: