On Nov 15, 2012, at 8:31 PM, "A.L.E.C" alec@alec.pl wrote:
On 11/15/2012 12:48 AM, Michael Heydekamp wrote:
Therefore I herewith apply for that both skins share the same core functionality. This is currently not the case, as I had to learn yesterday (using the addressbook during composing).
For me there's no reason for using contact widget in compose screen. It's useless.
I really dont think you can make such bold statements. I made the compose_addressbook plugin not because I like writing and maintaining plugins, but because i got tons of questions and complaints from actual users about how to add contacts from their addressbook in the compose screen. It was just not obvious that starting to type something would actually search in your addressbook. If you have 100,000 customers, if only 10% ask you this, is starts to become _really_ annoying.
Maybe some of them would have been fine with just typing, but it turns out a lot of people dont really want that. They want to see what they have. Maybe they cant quite remember the person they're looking for, maybe they type really slow, maybe they're elderly and dont remember how things work very well. A visible, clickable, item on the screen helps. Having a clickable addressbook in your mail client is pretty much a standard item, for a reason.
Having said that, i dont think you should backport it to classic. I dont agree with Michael that classic should remain to be supported. It's hard enough supporting 1 skin for you guys (let alone plugin developers!). And this is open source, so if someone wants to maintain the classic theme, no one is stopping them. And besides that, my plugin functionally works fine for classic so why put time in that at all?
It's good to hear you guys might be looking at adjusting the vertical and horizontal spacing of the larry theme. It is pretty much the only recurring complaint people seem to have about larry.
Cor