Current problems with settings, and why I think an overhaul is
required as mentioned in my last post.
1. It is a cludge to code for, you have to check the option array, add
to setScreenOption, all sorts of other stuff, I think a nicer system
would be something like
BerylSettingsSetting *
On 2/12/07, Robert Carr [EMAIL PROTECTED] wrote:
Beryl stands in uneasy grounds between a branch of Compiz and an
independent project. When we port every change from Compiz and then
merely add our own we are a branch of Compiz, flat out true. Ending
the 0.2.0 release cycle gives us a great
Too much to quote, but I understand your views.
First of all, I am not willing to let go of core. That's where I think
beryl has a real chance to make a difference.
I also belive we have to be brave enough to NOT add flashbang. We have
a situation with a core that is quite messy, and we need to
We all know we need to clean up, so to get some specifics up, here's a
few tasks I belive we can split up. Please pick tasks.
* Cleaning up the event handeling
I volounteer for this, heck, I even want to do it. And I belive it is
quite important.
* Error handeling
This would involve creating a
Kristian Lyngstøl wrote:
* Error handeling
This would involve creating a log-system of sorts that would be easy
to use, and allow us to use the --verbose options. It shouldn't be
much work, to create it, but we need to get it in there so we can
start outputing stuff that might be important.
On 2/12/07, tommy [EMAIL PROTECTED] wrote:
Kristian Lyngstøl wrote:
* Error handeling
pCritical(char *fmt, ...)
pWarn(char *fmt, ...)
pInfo(char *fmt, ...)
pDebug(char *fmt, ...)
pVDebug(char *fmt, ...)
While not a real dev so my $0.02 probably isn't worth it but I actually
