Hi,
I am planning to write a plugin to reproduce the "collected addressbook"
feature of thunderbird (ie: each email address you send a mail to is
collected in a special automatic addressbook, usefull for completion).
I need to store the completed addresses somewhere of course, watching at
some code and existing plugins, I see 3 ways to do that :
- store it into the main address book of the user, but it's not a good
solution as "explicit" contacts will get lost in collected addresses.
- store it in the "cache" table, but I then have only one field and I
need to use serializing/unserializing, that is bad for performances (&
with a quicly growing collected list...).
- creating a new SQL table for the plugin, that would be the cleaner
solution at the moment but I wonder if there is some caveats adding
"freely" tables to the roundcube base...
... Can you guys give me some advice on that ?
Thanks for your help & anyway for that great piece of code !
Jocelyn
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hello everybody
Here my first plugin based on the Mark As Junk one.
The goal is to archive selected message by moving them to an "Archive"
folder. The name of the archive folder is configurable using the same
scheme as the Mark as Junk plugin:
> $rcmail_config['archive_mbox'] = 'Archive';
The localisations are in english and french.
The icons comes from the Tango icon set.
I hope it will be useful.
All the best,
André.
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/tN/MtQUwbe2/archive.zip
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hi all, question about the addressbook. What exactly is the
difference between Display Name, and First/Last Name? It seems
Display Name is the only thing used. It's used for searching, and is
added to the email address for the recipient. I dont see what First/
Last name are used for. Are they just informational? You cant search
on First/Last for one.
The naming sortof led me to believe that Display Name is a UI thing
only, just to show you what the address is for.. lets say 'Mom'. If
thats the case, should it really be added to the address during
composing? To me that doesnt make sense. Id rather that only the
First/Last name get added, if filled in.
Regards,
Cor
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hi all, the Indonesia translation already updated. Please check the attachment.
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/Jw/765BOt7v/id_ID.zip
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hi all, in the past we've talked about caching busting. Especially
those that try to follow SVN with lots of customers it's quite
difficult to communicate to customers that they need to force reload.
Looking at the code it's pretty easy to add a ?v=XXXX for javascript
includes, but CSS is more difficult as it's hardcoded in the
templates. Has anyone thought about doing CSS cache busting yet? What
would be the easiest way to fix? Maybe add a roundcube object after
all template css includes that can be filled by a php function?
Also, an idea that was floated around before was to include a ?
v=a.b.c.d where a.b.d is the current version (0.2.2 for instance), and
d is default 0, but can be set in config.inc.php, to allow more recent
modifications of JS/CSS. Where would we put the a.b.c ? In preferences
as well? Maybe just the whole string in preferences?
Co
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hi,
as you are on the way to roundcube version 0.3 (stable) you might want
to close some tickets
or put some in another milestone (since no huge features shouldn't be
added unless you
don't want another beta version :))
I've found two tickets that you might want to close/move:
-first is this one: http://trac.roundcube.net/ticket/1485589
it seems that this is already fixed
-second is http://trac.roundcube.net/ticket/1485135
don't you think this is a bit more than just a tiny change
(especially if you want to implement
it with jQuery)? so you may want to set the milestone for 0.4-beta
Regards,
Martin
_______________________________________________
List info: http://lists.roundcube.net/dev/