Re: Directions

[Peter H. <pet...@hu...>]

Philippe Mingo said:
> Hi!
>
> To continue some decisions should be taken:
>
> - To continue with step 2 of foo_once we need the conf.pl to rewrite
> includes. If someone wanna do this or else I'll try to do it myself.
>
> - Plugins internationalization need to be defined. Only two possibilities.
> 1 to include all plugin strings in the main po file.
> 2 to include plugin string into a private gettext domain.
> The second system offer the following advantages:
>   * Hosts doesn't carry strings that are not used.
>   * Plugin's authors coordinates plugin po files.
>   * Users doesn't have to download CVS po files to translate latest
> plugins versions.

2 additionally comes out ahead of 1 in that 1 is unacceptable :-P

> - The imap session id. Now I've got a working version that uses the 4 last
> chars from session_id. Anyway it does it through an internal
> sqimap_session_id that can be changed any time. Do I commit?

Sure.

> - Shouldn't we consider the benefit of including some plugins into the core
> ? (the plugin that gives focus to the init field in forms, new mail, etc.)

No, but thanks for asking.

Seriously, there are some good reasons for this.  I'll let Tyler do the
arm-waving on this, though.  He is more passionate about the philosophical
reasons than I.

That aside, specifically regarding new_window and focus_change, they both use
JavaScript.  We are committed to keeping the SM core JS free.  There are several
reasons, but I'll save that for another time.

> - Date format. When reading messages, a long date format is displayed. Day
> name is truncated to 3 chars. Shouldn't we display it entirely ? (there is
> plenty of space) Or should we define it in internationalization.

I think it is fine how it is.  Remember, not everyone runs at 1600x1200,
Philippe!  At school the systems are set to 800x600 and Netscape is set up with
some HUGE font.  Those extra characters don't deliver any additional
information, so why mess with success?

-Peter