While I think that it's mostly okay, with maybe a few big problems , now is the chance to revamp it.
Sorry for top posting.
Calvin
On 02/06/2012 10:34 AM, Calvin Morrison wrote:
>> Calvin, I responded to your request for suggestions toward improving KControl. Let me know when you need help with testing.
>
> Thanks! It's rather lengthy I need to review each of those ideas.
> Overall they look like valid choices. I like the idea of separating
> peripherals and other customizations. If not it's an 100% agreement,
> maybe a few small details.
>
> I am going to create a Etherpad with your ideas copied into it. After
> doing my own review I will be asking Trinity users and developers for
> further ideas and modifications.
>
> Spot on,
>
> Calvin
>
Calvin,
Drop a link to the etherpad. I just googled and found nothing. I agree a small
clean up is in order, but not too much. The kcontrol for 3.5.13 wasn't bad as of
10 months ago or so. I haven't had time to think lately, but I did install, test
and dump 4.8 when released on Arch and system settings was garbage.
3.5.12->3.5.13 was not in too bad of shape, so I want to help with the review to
make sure we don't throw the baby out with the bathwater :)
--
David C. Rankin, J.D.,P.E.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting