Besides the new skin in 0.8 I'd like to start working on Roundcube
Framework. It means Roundcube will provide a set of classes that can be
used by other projects. Now, rcube_imap_generic class is known as one of
the best IMAP handling classes, but there are people that would like to
use something more abstract i.e. rcube_imap class. This is not simple
now because of its dependencies.
So, here are some steps I want to make:
- create abstract rcube_storage class and build rcube_imap as
rcube_storage implementation (driver) - this is to allow creation of
other drivers, e.g. SQL-based, POP3,
- exclude mime related functions from rcube_imap into new rcube_mime class,
- split main.inc and rcube_shared.inc functions into a few classes:
rcube_converter, rcube_ui, rcube_utils and maybe some into existing classes,
- create rcube_framework class, that can be a parent for rcmail class,
- framework-related changes to existing classes, e.g.
- get rid of $rcmail object usage in classes,
- can we exclude rcube_user class?
- make output/html/template classes optional,
- unify codestyle according to our CS ruleset
--
Aleksander 'A.L.E.C' Machniak
LAN Management System Developer [http://lms.org.pl]
Roundcube Webmail Developer [http://roundcube.net]
---------------------------------------------------
PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
Hi Devs,
I'm currently implementing Timezone support in my calendar plugin.
I think this should be integrated with Roundcube Timezone settings.
Is there a special reason why you save only the offset and DST
in prefs?
This way I can't detect the appropriate Olson Timezone:
F.e.: America/Denver and America/Phoenix are both in GMT offset -07:00,
Denver use DST while Phoenix doesn't.
I really would like to see the Timezone selection list showing Olson
Timezone
identifiers [timezone_identifiers_list()].
This change would it make possible to detect DST automatically as well
...
$stz = date_default_timezone_get();
date_default_timezone_set( ... indentifier from config ...);
$is_dst(date('I', time());
date_default_timezone_set($stz);
Regards,
R.
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
Dear developers,
We should update password plugin to support LDAP SSHA password with PHP 5.3.
SSHA requires PHP module mhash in PHP-5.2 and earlier versions, but it's discontinued in PHP-5.3, hash extension has full mhash compatibility, all existing applications using the old functions will continue to work.
Reference: http://php.net/manual/en/migration53.removed-extensions.php
So we don't need to check mhash extension if we're running PHP-5.3 in plugins/password/driver/ldap_simple.php (Line 219):
if (function_exists('mhash') && function_exists('mhash_keygen_s2k')) {
After modified:
if (function_exists('mhash_keygen_s2k')) {
Works fine with PHP-5.3, Debian 6.0.3. i know it's dirty, so i'm looking forward to an official patch.
Thanks. :)
----
Zhang Huangbin
iRedMail: Open Source Mail Server Solution for Red Hat Enterprise Linux,
CentOS, Scientific Linux, Debian, Ubuntu, openSUSE, FreeBSD:
http://www.iredmail.org/
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
Hi,
I wanted to update the Arabic language translation, but noticed it's now move to LaunchPad and nothing is translated.
Are you moving the old translation over, or do we have to redo everything from scratch?
thanks,
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
hei Thomas
I think this is fixed in SVN since before 0.7... but the fix is not in
0.7... can that be?
the problem is that the GUI is not showing more than one address fields
even when configured as home and work in the LDAP fieldmap.
fact is, I can reproduce this in 0.7 as Feisar and Andreas Oster, but I
observe that it works well in SVN...
could it be that it is a new bug in 0.7 or is the fix not in 0.7?
thanks
Andreas
-------- Original-Nachricht --------
Betreff: Re: [RCU] question regarding fieldmap for LDAP addressbook in
RC 7
Datum: Thu, 29 Dec 2011 13:36:12 +0000
Von: feisar <f3isar(a)gmail.com>
An: users(a)lists.roundcube.net
> my question was, what do you see in the gui?
> -> a dropdown left from the address? or even something like "Address"?
> if you change the dropdown, do it not change?
> or what does not work?
> Andreas
Hi, did this get resolved?
I too am having trouble with the alternative work/home addresses. The
email and phone number fields work as expected but there is no 'Add
Field> Address' option (only email, phone and website in my case).
I'm not really sure what the config should look like but here is mine
(using the evolutionPerson schema). There are a couple of things
commented out but that's just from previous experimentation:
'fieldmap' => array(
// Roundcube => LDAP
// Main information
'firstname' => 'gn',
'jobtitle' => 'businessRole',
'name' => 'cn',
'organization' => 'o',
//'photo' => 'jpegPhoto',
'prefix' => 'title',
'surname' => 'sn',
// Contact Properties
'email' => 'mail',
'phone:home' => 'homePhone',
'phone:work' => 'telephoneNumber',
'phone:mobile' => 'mobile',
// Work address
'address:work' => 'street',
//'zipcode:work' => 'postalCode',
//'locality:work' => 'l',
// Home address
'address:home' => 'homePostalAddress',
//'zipcode:home' => 'postalAddress',
//'locality:home' => 'otherPostalAddress',
//'region:home' => 'st',
//'country:home' => 'co',
'website' => 'labeledURI',
// Personal information tab
'anniversary' => 'anniversary',
'birthday' => 'birthDate',
'manager' => 'managerName',
'spouse' => 'spouseName',
// Notes tab
'notes' => 'note',
),
Thanks
--
List info: http://lists.roundcube.net/users/
BT/f0a00374
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
hei feisar
I think your config should be more like:
// Work address
/// 'address:work' => 'street',
'zipcode:work' => 'postalCode',
'locality:work' => 'l',
// Home address
/// 'address:home' => 'homePostalAddress',
'zipcode:home' => 'postalAddress',
'locality:home' => 'otherPostalAddress',
'region:home' => 'st',
'country:home' => 'co',
I think that 'address' is not supported but 'street' would be...
but I suppose it do not work anyway with 0.7 since it should with curent
SVN... can you please test that?
Andreas
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
Hi,
I'm not sure whether that's the right place to comment on the new skin,
but since I just tried it out for the first time, I want to point out
something that immediately caught my eye:
The search field on the upper left is very confusing. Everyone is used
to it being on the upper right, from about any web-app and even
non-web-app I know, including the old skin, Thunderbird, etc.. MediaWiki
even moved their search field to the upper right, just for that reason.
Can it be moved to the right side?
Patrick.
--
Key ID: 0x86E346D4 http://patrick-nagel.net/key.asc
Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
Hi list,
Those who have seen the drafts for the new UI, codename "Larry", may
have noticed that Roundcube will have combined icon & text toolbar
buttons. Now the existing text labels for the toolbar buttons are way
too long to be displayed inline. They worked perfect as hover-titles
but need to be shorter for the inline display. And I'm uncertain how
to approach this change. We could either do one of the following:
A) Change the existing labels to shorter versions
+ There's at least something displayed in every language
- Most of the translations need to be updated with shorter versions
- Hard for a translator to find the labels which need to be shortened
- No alternative longer hover-titles on the buttons or new labels have
to be created for that
B) Define new labels for the short button texts and keep the existing
ones as hover-titles
+ Perfect description of a toolbar button with icon, text and
description (hover)
+ Easy to "track" that new translations are required as launchpad will
show many "untranslated texts"
- Texts will be missing in all translations and English versions will
be displayed until translated
I slightly tend to B) because there are more positive aspects even if
it probably takes longer until all the translations are updated to
form a perfect new UI.
Any votes, opinions or gripes are welcome!
Best,
Thomas
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
Hi
Thomas, is possible to translate the first page of project[1] and use
the browser location to show the translated page (and english, when
haven't it) ? I think that can bring more users and helps in promote
the project. What you think?
[1]http://roundcube.net
Cheers,
Claudio
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80
Arne Berglund wrote:
> On 12/22/11 11:16, Thomas Bruederli wrote:
>> On Wed, Dec 14, 2011 at 16:23, <list(a)airstreamcomm.net> wrote:
>>> Thanks for the lastest release. We are curious what the time line
>>> for the
>>> new skin is going to be, and if you have any dates in mind for
>>> release?
>> We don't have a concrete deadline but I'd expect a first 0.8-alpha or
>> beta release with the new skin in early February. Then all the plugin
>> developers need some time to adapt their plugins to the new UI. And
>> of
>> course a lot of Internet Explorer Hacking will be necessary...
>>
>> ~Thomas
>
> Thomas, is the plan to completely replace the existing skin, or will
> both co-exist for a release or two? I don't imagine that anyone wants to
> maintain 2 skins for very long...
Then plan is to put the new skin in place of the "default" skin once it is
complete and tested while keeping the old default skin as "legacy" skin for
at least one major release. We'll most likley drop support for IE6 with the
new skin and old IEs will therefore get to see the legacy skin.
Of course, we're not keen on maintaining two skins in parallel so expect
the legacy skin to stay at the current state and being removed after a
while. But in case somebody is willing to "bring back the old design" and
to maintain the old skin, there's still a chance for it to survive the
armageddon.
Regards,
Thomas
_______________________________________________
List info: http://lists.roundcube.net/dev/
BT/aba52c80