headers
Matthew Wilson | 9 Apr 2007 22:57
Picon
Picon

wmlbrowser 0.7.14 released

wmlbrowser version 0.7.14 has been released. This fixes a couple of 
minor bugs. It also adds Firefox 3 (Gran Paradiso) alpha 3 compatibility.

Firefox users who installed from wmlbrowser.mozdev.org (not 
addons.mozilla.org) can upgrade automatically.

wmlbrowser no longer supports Firefox 1.0. (Neither do the Mozilla 
Foundation, so hopefully all users have already upgraded to the 1.5 or 
2.0 versions.)

As a reminder, WBMP support is available for Windows users running 
Firefox 3.0 alpha 3 in a separate build: 
http://wmlbrowser.mozdev.org/wbmp/index.html

Matthew
Permalink | Reply | 0 comments |
headers
Stegozor | 11 Apr 2007 02:39
Picon

Re: WBMP progress

Matthew Wilson wrote:
> Matthew Wilson wrote:
>> Stegozor wrote:
>>> On 3/24/07, Matthew Wilson <matthew <at> mjwilson.demon.co.uk> wrote:
>>>> I've been able to create an XPI for WBMP which is binary-compatible with
>>>> the official Firefox Windows nightly builds. This is tested with Gran
>>>> Paradiso alpha 3, and no other versions have been specified in the
>>>> install.rdf file.
> 
> Version 0.2.1 has now been released which fixes the image corruption.

Yay! I tested it with wmlbrowser 0.7.14 & Gran Paradiso Alpha 3 and it 
works quite fine. Some remarks follow:

Firstly, I know you don't want to add user defined options to wmlbrowser 
so it is my distinct pleasure to remind you that Gran Paradiso doesn't 
know what to do when it's asked to open a .wbmp file from a local disk. ;-)

Second, out of curiosity, what changes have you made to wbmpviewer since 
version 0.2 to make it work properly? If you adapted it (cairo 
changes...), maybe it would make sense to add your recent work as an 
attachment to bug 182621 ( 
https://bugzilla.mozilla.org/show_bug.cgi?id=182621 ) with an 
explanation. The last comment reads "This really probably needs to be 
updated after the Cairo changes"...

Also from your first post:
> 3. I'm not planning to worry about SeaMonkey compatibility until the 
> faults are ironed out.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Matthew Wilson | 14 Apr 2007 11:41
Picon
Picon

Re: WBMP progress

Stegozor wrote:
> Matthew Wilson wrote:
>> Matthew Wilson wrote:
>>> Stegozor wrote:
>>>> On 3/24/07, Matthew Wilson <matthew <at> mjwilson.demon.co.uk> wrote:
>>>>> I've been able to create an XPI for WBMP which is binary-compatible with
>>>>> the official Firefox Windows nightly builds. This is tested with Gran
>>>>> Paradiso alpha 3, and no other versions have been specified in the
>>>>> install.rdf file.
>> Version 0.2.1 has now been released which fixes the image corruption.
> 
> Yay! I tested it with wmlbrowser 0.7.14 & Gran Paradiso Alpha 3 and it 
> works quite fine. Some remarks follow:
> 
> Firstly, I know you don't want to add user defined options to wmlbrowser 
> so it is my distinct pleasure to remind you that Gran Paradiso doesn't 
> know what to do when it's asked to open a .wbmp file from a local disk. ;-)

Thanks for the tip.

> Second, out of curiosity, what changes have you made to wbmpviewer since 
> version 0.2 to make it work properly? If you adapted it (cairo 
> changes...), maybe it would make sense to add your recent work as an 
> attachment to bug 182621 ( 
> https://bugzilla.mozilla.org/show_bug.cgi?id=182621 ) with an 
> explanation. The last comment reads "This really probably needs to be 
> updated after the Cairo changes"...

I did need changes for Cairo, along with a couple of other things.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthew Wilson | 14 Apr 2007 11:50
Picon
Picon

Setting the user agent

Recently an email came to the mailing list which I thought I had 
approved, but which seems to have gone missing. The message was as follows:

> Hi,
> 
> Can you please point me to the document that has a step wise discription on how to simulate a particular
mobile phone using firefox browser ?
> 
> Regards,
> Parthraj Sarvaiya 

Before answering, can I recommend that, if you're asking a questino of 
the list, it's best to sign up to the mailing list, and to use 
descriptive subject lines in their mails.

Anyway, to do this, install the User Agent Switcher extension from 
https://addons.mozilla.org/en-US/firefox/addon/59 . This gives a new 
menu option, Tools/User Agent Switcher. (That's on Firefox under 
Windows.) Use Tools/User Agent Switcher/Options/Options, then choose 
User Agents (in the left hand pane) and then Add to add the details of 
your desired mobile phone. You can now choose this user agent to set the 
browser details appropriately.

Matthew
Permalink | Reply | 0 comments |
headers
Xavier Morel | 18 Apr 2007 12:02

<fieldset> element

WML has a fieldset element to group related "form" elements together.
The fieldset is usually displayed as a box with solid or slanted
borders, and an optional title punched into the border.

The issue here is that in WML the fieldset title is set by the  <at> title
fieldset attribute, while in regular HTML the fieldset title (the one
punched into the border) is set by a <legend> element as first child of
the fieldset (http://www.w3.org/TR/html401/interact/forms.html#h-17.10),
and the  <at> title is only used for regular title purposes (hover hint and
stuff). Yet wmlbrowser translates the WML fieldset <at> title into an HTML
fieldset <at> title, giving it quite different semantics than the WML ones.

Would it be possible for wmlbrowser to translate fieldset <at> title into a
<legend> element?

Side-question: in WML, content can only be contained in <p> elements
(many devices refuse to render the content and display an error if there
is anything out of a <p>, apart from cards of course). Would it be
possible for wmlbrowser to throw an error if it finds a	page where
regular text, <table>, <fieldset>, <go>, <a> and any other "inner"
element is found at the root of a card, without being enclosed by a <p>?

Thank you.

Xavier Morel
Permalink | Reply | 1 comment |
headers
Matthew Wilson | 18 Apr 2007 21:20
Picon
Picon

Re: <fieldset> element

Xavier Morel wrote:
> WML has a fieldset element to group related "form" elements together.
> The fieldset is usually displayed as a box with solid or slanted
> borders, and an optional title punched into the border.
> 
> The issue here is that in WML the fieldset title is set by the  <at> title
> fieldset attribute, while in regular HTML the fieldset title (the one
> punched into the border) is set by a <legend> element as first child of
> the fieldset (http://www.w3.org/TR/html401/interact/forms.html#h-17.10),
> and the  <at> title is only used for regular title purposes (hover hint and
> stuff). Yet wmlbrowser translates the WML fieldset <at> title into an HTML
> fieldset <at> title, giving it quite different semantics than the WML ones.
> 
> Would it be possible for wmlbrowser to translate fieldset <at> title into a
> <legend> element?

Yes, that sounds straightforward.

> Side-question: in WML, content can only be contained in <p> elements
> (many devices refuse to render the content and display an error if there
> is anything out of a <p>, apart from cards of course). Would it be
> possible for wmlbrowser to throw an error if it finds a	page where
> regular text, <table>, <fieldset>, <go>, <a> and any other "inner"
> element is found at the root of a card, without being enclosed by a <p>?

Definitely possible, although a little more work. In fact, wmlbrowser 
allows all kinds of element nesting which should be illegal. I did make 
a start on this once, but I found that all manner of pages were 
breaking, so I kind of gave up on it. But it certainly could be done.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthew Wilson | 22 Apr 2007 15:40
Picon
Picon

wmlbrowser 0.7.15 has been released

wmlbrowser 0.7.15 has been released with the following fix:

     * Bug 16841, improve appearance of "fieldset" with title. Thanks to 
Xavier Morel for suggesting the improvement.

Firefox users who installed from wmlbrowser.mozdev.org can upgrade 
automatically to the new version.

Matthew
Permalink | Reply | 0 comments |
headers
Paul Denize (DSLWN | 26 Apr 2007 02:55
Picon
Favicon

Cool idea


I just loaded the latest version 0.7.13 and cant seem to find any menu item or toolbar to actually make it do anything.

It appeared to load and install ok - tried it several times.

Maybe it needs a bit more documentation so users know what to expect or how to get it going.


Paul Denize 

_______________________________________________
Wmlbrowser mailing list
Wmlbrowser <at> mozdev.org
http://mozdev.org/mailman/listinfo/wmlbrowser
Permalink | Reply | 2 comments |
headers
Xavier Morel | 26 Apr 2007 10:33

Re: Cool idea

Paul Denize (DSLWN) wrote:
> 
> I just loaded the latest version 0.7.13 and cant seem to find any menu
> item or toolbar to actually make it do anything.
> 
> It appeared to load and install ok - tried it several times.
> 
> Maybe it needs a bit more documentation so users know what to expect or
> how to get it going.
> 
> 
> Paul Denize
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Wmlbrowser mailing list
> Wmlbrowser <at> mozdev.org
> http://mozdev.org/mailman/listinfo/wmlbrowser

WMLBrowser will activate as soon as your browser will receive a page in
WML (mime type text/vnd.wap.wml).

To make the changes of receiving WML pages (instead of HTML/XHTML when
browser sniffing is activated on the platform), set your User Agent to a
WML device's UA (via User Agent Switcher) e.g. "SAGEM-myX-2/1.0
UP.Browser/5.0.5.3.100 (GUI)" for the Sagem my X-2, which should be
recognized as a WML phone by most sniffers.
Permalink | Reply | 1 comment |
headers
Xavier Morel | 26 Apr 2007 11:25

Re: Cool idea

Xavier Morel wrote:
> WMLBrowser will activate as soon as your browser will receive a page in
> WML (mime type text/vnd.wap.wml).
> 
> To make the changes of receiving WML pages (instead of HTML/XHTML when
> browser sniffing is activated on the platform), set your User Agent to a
> WML device's UA (via User Agent Switcher) e.g. "SAGEM-myX-2/1.0
> UP.Browser/5.0.5.3.100 (GUI)" for the Sagem my X-2, which should be
> recognized as a WML phone by most sniffers.
> 

Wow, I just realized that my post barely made sense, I really should've
proofed it before sending it.

here's a more readable version:

* WMLBrowser will activate when Firefox receives a WML page (e.g. MIME
type text/vnd.wap.wml)
* Many mobile platforms perform client-sniffing in order to serve cHTML
to cHTML devices (NTT DoCoMo's iMode phones), XHTML to modern
XHTML-compatible phones and WML to older WML devices. To have higher
chances of getting WML content, you should identify yourself as a WML
phone using the User Agent Switcher extension, the User Agent
"SAGEM-myX-2/1.0 UP.Browser/5.0.5.3.100 (GUI)" (Sagem MyX-2) usually
works fairly well in my experience.
* You'll notice right away when your browser gets into WML mode (when
wmlbrowser activates), because there will be fairly big solid gray
borders all around your screen.
* To get a better "feel" of the pages (although it definitely doesn't
replace actually testing the pages in mobile devices), I recommend that
you also install the "Small Screen Renderer" extension
(http://disruptive-innovations.com/products/index.html).

Have fun.

Xavier Morel
Permalink | Reply | 0 comments |

Gmane