[chromium-dev] Re: Chrome Bookmarks/Passcards
On Oct 7, 10:55 pm, Ben Goodger (Google) [EMAIL PROTECTED] wrote: Scott Violet is probably going to begin doing work on a new Bookmark Manager in the next few weeks. We'll have mocks soon. You should look at this work and see if it meets your needs. Great to hear this. About your previous question Can you identify what specifically you think needs doing? may I refer to my other posting about this problem in which I tried to summarize basic needs: http://groups.google.com/group/google-chrome-help-suggestions/browse_thread/thread/0870bd05917d7e42?hl=en# --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Chromium-dev group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Mac build is (sea foam) green again - let's keep it that way
After a few days of hard work, we've gotten the Mac build back in shape following the recent WebKit merge. A special thanks to Jeremy, Amanda, and Mike, who worked with me to get this done. This puts us back where we were last week, but with an updated WebKit snapshot. We're currently building a TestShell that runs, loads web pages via our own http implementation, and has WebKit render them. We're currently working on getting it to draw, but in the mean time, Chromium's TestShell for Mac is the browser for you if the only web pages you want to visit are a solid blob of sea-foam green. We've also gotten all of the tests green again, although in this case, green is actually what we want to see. Now that we're back at this point, we'll resume treating the Mac as a priority platform. If the Mac bot at http://build.chromium.org/ turns red for any reason (build failure, test failure, any other failure), you should consider the tree closed until it's fixed, the same as you would any other red buildbot. Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Chromium-dev group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] PSA: Review mail best practices
Two recommendations for folks participating in code reviews using Rietveld ( codereview.chromium.org): (1) When uploading a patch, make sure you Edit Issue and add at least one review email; then use the Publish+Mail Comments link (with a blank body, usually) to send out the review request. When uploading subsequent versions of the patch, use Publish+Mail Comments again to send mails noting that you've uploaded a new version (if you're ready for it to be re-reviewed). We've had a number of patches with no initial review mail, or no reviewers listed, or the reviewer set to the person who uploaded the patch, or whatever. If you don't know whom to ask for review, yell for help on #chromium-dev. (2) When reviewing a patch or responding to review comments, use the same Publish+Mail Comments link to converse. Tempting as it is, try to avoid using your mail client to respond to the comment emails directly, because that doesn't put your comments online on the issue where others can see and respond to them later. This helps avoid strange half-broken threads when someone else tries to look over and comment on an issue after it's been in review for a while. Feel free to share other best practices you've encountered. PK --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Chromium-dev group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Chrome Bookmarks/Passcards
Peter, For a bookmark management UI design just look at the manage subscriptions page in Google Reader! I would code a cross between that and the existing history page! Chris On Oct 8, 5:15 pm, Chris G [EMAIL PROTECTED] wrote: Thanks Ben, How will I find the mock ups? A couple of features that I missed from my list above: * Ability to select passcards, like a bookmark. Selecting will goto the page, fill the form, and submit with not further user intervention. * When on a page with a form, show all matching (based on URL) passcards (In case multiple apply). * Allow user to select any passcard (not just matching), then fill and submit current form automatically. On Oct 8, 5:01 pm, towo [EMAIL PROTECTED] wrote: On Oct 7, 10:55 pm, Ben Goodger (Google) [EMAIL PROTECTED] wrote: Scott Violet is probably going to begin doing work on a new Bookmark Manager in the next few weeks. We'll have mocks soon. You should look at this work and see if it meets your needs. Great to hear this. About your previous question Can you identify what specifically you think needs doing? may I refer to my other posting about this problem in which I tried to summarize basic needs: http://groups.google.com/group/google-chrome-help-suggestions/browse_... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Chromium-dev group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
