[wp-testers] Google Gears

John O'Nolan john at onolan.org
Mon Feb 22 13:30:39 UTC 2010


Hi Darren,
This has been discussed at length - you can check out the ticket here http://core.trac.wordpress.org/ticket/11301

John

M: 07515 360 723
E: john at onolan.org

http://john.onolan.org
http://twitter.com/johnonolan
http://www.lyricalmedia.com


This email is intended for the above recipients only, if you are not  
the intended recipient please delete this email immediately. You are  
hereby notified that any disclosure, copying, distribution or use of  
any of the information contained in or attached to this transmission  
is strictly prohibited.

On 22 Feb 2010, at 13:27, Darren Mackintosh wrote:

> Google gears is dead. HTML5 is to replace it
> http://www.theregister.co.uk/2010/02/22/ 
> google_gears_phase_out_html_5/.
> One thing I have noticed is that Google Gears doesn't work with the
> Firefox 3.6 (or at least it didn't last time I checked). Wouldn't it  
> be
> prudent to remove this functionality altogether?
>
> Darren
>
> -----Original Message-----
> From: wp-testers-bounces at lists.automattic.com
> [mailto:wp-testers-bounces at lists.automattic.com] On Behalf Of
> wp-testers-request at lists.automattic.com
> Sent: 22 February 2010 12:00
> To: wp-testers at lists.automattic.com
> Subject: wp-testers Digest, Vol 60, Issue 12
>
>
> Send wp-testers mailing list submissions to
> 	wp-testers at lists.automattic.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.automattic.com/mailman/listinfo/wp-testers
> or, via email, send a message with subject or body 'help' to
> 	wp-testers-request at lists.automattic.com
>
> You can reach the person managing the list at
> 	wp-testers-owner at lists.automattic.com
>
> When replying, please edit your Subject line so it is more specific  
> than
> "Re: Contents of wp-testers digest..."
>
>
> Today's Topics:
>
>   1. Re: Google Gears (Brian Layman)
>   2. Re: Google Gears (Andrew Nacin)
>   3. Re: Automated Testing Failing (Peter Westwood)
>   4. WooNav Issues (John O'Nolan)
>   5. Re: WooNav Issues (Andrew Nacin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 21 Feb 2010 12:49:44 -0500
> From: "Brian Layman" <Brian at TheCodeCave.com>
> Subject: Re: [wp-testers] Google Gears
> To: <wp-testers at lists.automattic.com>
> Message-ID: <00ae01cab31e$40a9efb0$c1fdcf10$@TheCodeCave.com>
> Content-Type: text/plain;	charset="us-ascii"
>
> It's has been discussed in the weekly IRC chats.  I believe the
> consensus was that it would be left until an (html5?)  alternative was
> ready. At least that's where I remember the discussion ending. -Brian
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 21 Feb 2010 12:53:46 -0500
> From: Andrew Nacin <wp at andrewnacin.com>
> Subject: Re: [wp-testers] Google Gears
> To: wp-testers at lists.automattic.com
> Message-ID:
> 	<4cc4de141002210953p546387acicf1bd5b9bda9e3cf at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Unfortunately, that isn't going well either:
> http://core.trac.wordpress.org/ticket/7262
>
> On Sun, Feb 21, 2010 at 12:49 PM, Brian Layman
> <Brian at thecodecave.com>wrote:
>
>> It's has been discussed in the weekly IRC chats.  I believe the
>> consensus was that it would be left until an (html5?)  alternative  
>> was
>
>> ready. At least that's where I remember the discussion ending. -Brian
>>
>> _______________________________________________
>> wp-testers mailing list
>> wp-testers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 21 Feb 2010 22:09:37 +0000
> From: Peter Westwood <peter.westwood at ftwr.co.uk>
> Subject: Re: [wp-testers] Automated Testing Failing
> To: wp-testers at lists.automattic.com
> Message-ID: <989AF5FF-8732-429F-8935-BA72F5C815F9 at ftwr.co.uk>
> Content-Type: text/plain;	charset=us-ascii
>
>
> On 21 Feb 2010, at 11:52, Dion Hulse (dd32) wrote:
>
>> Its not the tests that will need fixing in most cases, but WordPress.
>>
>> Altho, In some cases, Its just that the test cases are out of date.
>>
>> If you'd like to just run one set of tests (to see what is failing)
>> you can run them like so: php ./wp-test.php -t  
>> Test_Sanitize_File_Name
>>
>> Peter Westwood (westi) is the main man behind the tests, he'll
>> probably chime in here sometime with some better answers.
>>
>
>
> Well.  In truth I inherited the tests from someone else who wrote the
> bulk of them - I can't take the credit for the work that was done  
> before
> me by others - https://www.ohloh.net/p/wordpress-unit-tests/contributors
>
> In general for every test that currently fails we need to look through
> and try and understand if
>
> a) The test is wrong or out-of-date
> b) The code has been changed and a bug has been introduced
>
> If its (b) it would be really good if someone could raise a trac  
> ticket
> which hilights the bug and even better if you can track it back to  
> which
> version introduced it.
>
> At the moment because so much fails I tend to focus on running tests
> which relate to something I am changing or fixing up code/tests for
> individual test classes.
> -- 
> Peter Westwood
> http://blog.ftwr.co.uk | http://westi.wordpress.com
> C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 22 Feb 2010 04:50:35 +0000
> From: John O'Nolan <john at onolan.org>
> Subject: [wp-testers] WooNav Issues
> To: wp-testers at lists.automattic.com
> Message-ID: <004CAA02-E1DC-4686-BCF1-FB2515A8F291 at onolan.org>
> Content-Type: text/plain;	charset=US-ASCII;	format=flowed;
> delsp=yes
>
> Hi Guys,
> Some notes on the Woo Custom Nav that was implemented over the  
> weekend:
>
> Grammatical Error
> When enabling, the status message says:
> "(site name)s Custom Menu has been updated!"
>
> This should say:
> "(site name)'s Custom Menu has been updated!"
> Where the added apostrophe is possessive.
>
> Confusing Element
> It is unclear that the user is expected to "add a menu" prior to
> creating menu items. This should either have a large call to action,
> or the other options should not be available until a menu has been
> created.
> When adding menu items without having first "created a menu", clicking
> on "save all changes" causes all the menu-items to be immediately
> deleted.
>
> Links Opening in a New Window
> When adding a custom url to the menu, the default functionality
> assigned to "open link in a new window" is "yes" - causing any site
> using this to immediately fail xhtml1.0 strict validation, as well as
> being of questionable usability value!
>
> Feature Request
> It would be incredibly helpful if the "edit menu item" options
> included a way of adding a custom class to the <li>
>
> John
>
> ------------------------------
>
> Message: 5
> Date: Sun, 21 Feb 2010 23:56:03 -0500
> From: Andrew Nacin <wp at andrewnacin.com>
> Subject: Re: [wp-testers] WooNav Issues
> To: wp-testers at lists.automattic.com
> Message-ID:
> 	<4cc4de141002212056w2d2484bahaf56e736d0bf7829 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Much of the navigation is broken functionality and unpolished UI. It
> just landed in trunk and we're getting the schema settled first.
>
> You're welcome to comment on http://core.trac.wordpress.org/ticket/11817
> as you find things, especially as it progresses. Thanks for the
> feedback.
>
>
> On 2/21/10, John O'Nolan <john at onolan.org> wrote:
>> Hi Guys,
>> Some notes on the Woo Custom Nav that was implemented over the
>> weekend:
>>
>> Grammatical Error
>> When enabling, the status message says:
>> "(site name)s Custom Menu has been updated!"
>>
>> This should say:
>> "(site name)'s Custom Menu has been updated!"
>> Where the added apostrophe is possessive.
>>
>> Confusing Element
>> It is unclear that the user is expected to "add a menu" prior to
>> creating menu items. This should either have a large call to action,
>> or the other options should not be available until a menu has been
>> created. When adding menu items without having first "created a  
>> menu",
>
>> clicking on "save all changes" causes all the menu-items to be
>> immediately deleted.
>>
>> Links Opening in a New Window
>> When adding a custom url to the menu, the default functionality
>> assigned to "open link in a new window" is "yes" - causing any site
>> using this to immediately fail xhtml1.0 strict validation, as well as
>> being of questionable usability value!
>>
>> Feature Request
>> It would be incredibly helpful if the "edit menu item" options
>> included a way of adding a custom class to the <li>
>>
>> John
>> _______________________________________________
>> wp-testers mailing list
>> wp-testers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>
>
>
> ------------------------------
>
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
>
> End of wp-testers Digest, Vol 60, Issue 12
> ******************************************
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> The information contained in this message or any of its attachments  
> is confidential and may be privileged.
>
> Unauthorised disclosure, copying or dissemination of the contents is  
> strictly prohibited.
>
> The views expressed may not be official policy, but the personal  
> views of the originator.
>
> If you are not the intended recipient or have received this message  
> in error, please delete this e-mail and advise the sender by using  
> the reply facility in your e-mail software.
>
> All messages sent and received by Argos are monitored for viruses,  
> high-risk file extensions, and inappropriate content.
>
> The registered office address of Argos Limited (registered in  
> England and Wales, number 1081551) is Avebury, 489-499 Avebury  
> Boulevard, Milton Keynes MK9 2NW.
>
> Please visit our website at http://www.argos.co.uk for further  
> information about Argos.
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers



More information about the wp-testers mailing list