Sebastian Krzyszkowiak wrote:
Please try to avoid judging without knowing anything about what you're
talking. With odeviced IT WORKED as you wanted - settings was stored
and they were easly changable by SHR Settings UI. It changed when
migrating from odeviced to fsodeviced, which is regression in FSO
stack, not "usability decision"...
The migration from odeviced to fsodeviced is in itself a usability decision.
Why else would you want a new deviced if not for flexibility and feature
addition?
I completely understand the value of the FSO roadmap, and I sincerely
hope it does get implemented, but I also think that the critical bugs in
the system should have higher priority than ANY new features or refactoring.
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
