SeaMonkey/StatusMeetings/2008-07-15: Difference between revisions

Jump to navigation Jump to search
Line 36: Line 36:
* We'll be building up and moving to the [http://hg.mozilla.org/comm-central/ comm-central] hg repository soon, see {{bug|437643}} - basically only waiting for Thunderbird to cut alpha2 and reviews for the build system patches in {{bug|444686}}
* We'll be building up and moving to the [http://hg.mozilla.org/comm-central/ comm-central] hg repository soon, see {{bug|437643}} - basically only waiting for Thunderbird to cut alpha2 and reviews for the build system patches in {{bug|444686}}
* Mozilla 1.9.1 platform is probably going to feature-freeze in mid August (beta1), anything we want to get in there should be done before that
* Mozilla 1.9.1 platform is probably going to feature-freeze in mid August (beta1), anything we want to get in there should be done before that
* Is someone, preferably who's not working on any major SM2 thing right now, up for porting the history UI to places? (backend works fine with --enable-places)
* Is someone, preferably who's not working on any major SM2 thing right now, up for porting the history UI to places? (backend works fine with <tt>--enable-places</tt>)
** The core of that work would be creating a custom treeview, probably based on one available in the places/library UI.
** The core of that work would be creating a custom treeview, probably based on one available in the places/library UI.
** Note: If you builds SeaMonkey with <tt>--enable-places</tt>, you only get the places history backend, not the bookmarks one.
** Note: If you builds SeaMonkey with <tt>--enable-places</tt>, you only get the places history backend, not the bookmarks one.
* typeaheadfind will still be pulled from CVS when we switch to comm-central, blocks us from doing static or libxul builds and duplicates code that toolkit has - this badly needs some love
* typeaheadfind will still be pulled from CVS when we switch to comm-central, blocks us from doing static or libxul builds and duplicates code that toolkit has - this badly needs some love
** Ideally we shoul migrate to toolkit typeaheadfind <b>and</b> do a wrapper around the toolkit implimentation that does what we want of it.
** Ideally we shoul migrate to toolkit typeaheadfind <b>and</b> do a wrapper around the toolkit implimentation that does what we want of it.
** wanted: move the find bar to the top (like in safari), but without pushing the content down. stefanh has some ideas on this.
** Wanted: move the find bar to the top (like in safari), but without pushing the content down. stefanh has some ideas on this.
** We should also have a pref for not being shown on normal autocomplete though.
** We should also have a pref for not being shown on normal autocomplete though.


Confirmed users
2,595

edits

Navigation menu