Componenti aggiuntivi
Benvenuto in SeaMonkey Add-ons.
Aggiungi nuove funzionalità e stili per rendere SeaMonkey veramente tuo.
ChiudiRichard
Informazioni utente
| Nome | Richard |
|---|---|
| Utente da | Luglio 6, 2007 |
| Numero di componenti aggiuntivi sviluppati | 0 componenti aggiuntivi |
| Media delle valutazioni sui componenti aggiuntivi di questo sviluppatore. | Nessun voto |
Le mie recensioni
Deutsches Wörterbuch (de-DE), alte Rechtschreibung
Assegnate 5 su 5 stelle
Funktioniert tadellos. Großer Dank an den Entwickler dieser wichtigen Erweiterung. Damit haben wir die altbewährte Rechtschreibung auch für Thunderbird.
Questa recensione riguarda una versione precedente (2.1.8) del componente aggiuntivo.Lightning
Assegnate 5 su 5 stelle
Thank you for the important Calendar add-on for the nice Thunderbird, or TB in short.
There's one little problem when Lightning uses ICS calendar files on a FTP server (like ftp://server.com/Kalender.ics) _and_ events with reminding alarms:
When Lightning first opens such an ICS file, it asks for the FTP user-name and password and stores these two words in TB's keyring (if you ticked the store option). So next time when Lightning synchronises its calendars or when you start TB, Lightning opens the ICS file from the FTP server with the stored user-name and password from TB's keyring.
So far, so good. But, when an event in such a FTP calendar uses a reminding alarm, the reminder window pops up asking when to repeat the reminder, and then asks for the FTP user-name and password _again_. In the next TB+Lightning session this asking will happen again, and so on.
Looks like Lightning ignores these two stored words in the case of reminding events. Is this a bug?
(Some people suggested to use the ftp://username:password@server...etc syntax, which works but is not nice for non-private environments when you've to double-click the calendar name which shows the entire URL including passwords in clear-text.)
British English Dictionary
Assegnate 5 su 5 stelle
Excellent. Thank you very much for this fine add-on, dear developers.
One little question, though: When I open the add-on page/tab in Thunderbird, the other Thunderbird dictionaries (like for example the German one) are being listed under the icon/section "Dictionaries".
However this British dictionary is not being listed there, but under the icon/section "Add-ons".
Is there a simply way to move the British dictionary from the latter section to the first one named "Dicitionares"?
Greetings from Germany to my British friends!
Encrypt if possible
Assegnate 5 su 5 stelle
Unverzichtbare Erweiterung für Benutzer von S/MIME. Diese Funktionalität sollte von Haus aus in Thunderbird vorhanden sein. Herzlichen Dank an den scharfsinnigen Autor, und schöne Grüße nach Österreich!
And now for my English friends:
This add-on is a must have for S/MIME users. Its functionality should be implemented in Thunderbird per default. A warm thank-you to the smart author, and many greetings to Austria!
Lightning
Assegnate 4 su 5 stelle
I'm a long time Thunderbird and Lightning (formerly: Sunbird) user, but when Thunderbird upgraded from version 8 to version 9, suddenly Lightning version 1.0 didn't work at all anymore...
Then I upgraded Lightning from version 1.0 to 1.1 and it showed up but doesn't work correctly because it justs shows an empty calendar where I can't create any new alarm, let alone a new calendar...
In Thunderbird's settings in the tab "Lightning" there's the selection box "Timezone" but I can't select anything there because it's just an empty field. This seems to be an error, related to what the Russian Ubuntu user reported here some time ago, but I don't know what it is.
How can I solve this serious problem, because for now I've to stick with an outdated Thunderbird 8 (dangerous) because of Lightning 1.1 not working on my German Windows XP SP 3... ?
Any help much appreciated! Thanks.
Toolbar Buttons
Assegnate 5 su 5 stelle
Excellent!
A must-have.
Should be integrated into Firefox Version 3.2+, really.
YesScript
Assegnate 5 su 5 stelle
It's a must have add-on.
For cookies a whitlist is the way to go, but with Web2/Ajax more and more sites rely on JavaScript to work at all, so a whitelist will basically render the WWW hard to use. This is what NoScript would do. Aside that, NoScript is not lighter at alle (look at the size!) and much more difficult to use.
So, because of Web2/Ajax, a blacklist is the way to go for JavaScript. This is what YesScript does and it does it very well. Thanks a lot for it and please keep up the good work!
Per creare una tua raccolta devi avere un account per Mozilla Add-ons.
