<< Weekly Status Report, W32/2010 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>

Weekly Status Report, W33/2010

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 33/2010 (August 16 - 22, 2010):

This has been a really busy week for me - actually, when writing this up today, it looks even more busy then it felt while it was underway. Unfortunately, we didn't get as far as I hoped on the third alpha, but I hope we'll be able to push it out to the public in the next few days, so our full concentration can be on the beta development cycle. A lot of work has already happened, and some more stuff is underway - both in SeaMonkey-specific code and in the platform, so it feels really great to be in the project right now - even if not always everyone agrees on specifics, but I'm sure we can work out a lot of that to a degree where we all can be happy. And where we still diverge in what we want - well, that what prefs and add-ons are for, after all! :)

Beitrag geschrieben von KaiRo und gepostet am 23. August 2010 20:52 | Tags: L10n, Mozilla, SeaMonkey, Status | 8 Kommentare | TrackBack

Kommentare

AutorBeitrag

Tempest

zitieren
2.1 Alpha 3
Can we please have a preference to select between a find dialog and a find bar ?
25.08.2010 15:57

KaiRo

Webmaster

zitieren
No, the find dialog is dead for good. Write an add-on if you want to change that.
26.08.2010 15:23

Tempest

zitieren
Why should this be the case ? You have the find dialog code in 2.0 and you have the find bar code in 2.1 Alpha 3, it is certainly no trouble to add a preference and use an if-else to call the appropriate routine based upon user preference or are the things that have been written about the stubbornness of the Mozilla people regarding user preference true ?
26.08.2010 17:36

Tempest

zitieren
Another point: doesn't the find dialog code need to remain to support window.find as the last parameter to the function is whether or not to show a *dialog* - https://developer.mozilla.org/en/DOM/window.find

A separate issue: is there some way that SeaMonkey could address the issue with downloaded files not getting the last modification date from the server (bug 178506) ? Again why is there an objection to having a preference for this ?

Finally I hope something is done about the places database handling with bookmarks being moved there. In 2.0 I've noticed that the table moz_historyvisits has several times as many entries as moz_places, shouldn't they be more or less one to one ?
27.08.2010 01:42

KaiRo

Webmaster

zitieren
1) No need to discuss the find dialog, it's dead and will stay that way. And a standard calling for any specific UI is flawed and needs to be changed anyhow. Modal dialogs are bad, bad, bad in cases where there's no reason they need to block doing other things.

2) The modification time of a download is a platform issue, we only control the UI, not the platform, so take this up with platform developers.

3) Ask the places team for details, again we only control the UI, not the platform, and the places database is part of the platform. Still, I guess you're just visiting pages multiple times so they get multiple history items but they stay single "places" after all.
27.08.2010 14:30

Tempest

zitieren
Geez could you tone it down with the modal dialog vitriol ? At least in this case it is a matter of personal presentation preference as find is a user-initiated function (Ctrl-F or F3 with no prior find string). Extra toolbars are bad because users want to maximize browser area not have additional toolbars coming up for stuff. Wasn't this lesson learned with the rather intrusive notification bars which have been replaced in Gecko 2.0 with the doorhanger notifications ?


Does SeaMonkey own the files in the SeaMonkey\components and SeaMonkey\modules directories or are they shared with Firefox ? I ask because it would be nice if there was a preference to disable forms autocomplete=off which is implemented in SeaMonkey\components\nsLoginManager.js. Currently I modify the file to disable this "feature" but I have to redo this with each update.
27.08.2010 20:33

Louis Epstein

zitieren
I guess preferring the Find to be a pop-up will be a reason to stick with 2.0.x as long as possible.Is a 2.0.7 planned?
31.08.2010 09:16

KaiRo

Webmaster

zitieren
We will still support 2.0.x for a while, but not forever.
31.08.2010 18:51

Kommentar hinzufügen