appversion question

7 views
Skip to first unread message

Brij Charan

unread,
Apr 23, 2009, 4:55:15 PM4/23/09
to northwe...@googlegroups.com
Hey guys.

I got a question for you app version gurus.

in chrome.manifest.

If I'm trying to say I want a certain file to be loaded for all 3.1 betas and 3.1 itself, so greater than 3.1 beta up..how the heck do I do that?
MDC's docs are confusing for me.

So like.

bla chrome://bla bla appversion > 3.1b
or
bla chrome://bla bla appversion > 3.1

But 3.1 is technically higher than 3.1b right, so I dunno.

Does someone have a dummies explanation on how this works?

Thx.



--
Brij Charan
Director, Technology and Design
Brand Thunder.

Doug Schlenker

unread,
Apr 23, 2009, 5:39:03 PM4/23/09
to northwe...@googlegroups.com
My understanding is next beta of FF will have the 3.5 numbering. They've already branched out and have a 3.6pre available.

But yes, I believe it's like this (let's say targetting FF 3.5)
## cross-platform files ##
[override/content/etc] chrome://path/file.oof appversion>=3.5
[override/content/etc] chrome://path/file.oof appversion<3.5
## OS X targeted version for FF 3.5 ##
[override/content/etc] chrome://path/file.oof appversion>=3.5 os=Darwin

Steven Bengtson

unread,
Apr 23, 2009, 5:39:18 PM4/23/09
to northwe...@googlegroups.com
A string-part that exists is always less-then a nonexisting string-part (1.6a is less than 1.6).
3.1a < 3.1b < 3.1bb < 3.1bc < 3.1b3 < 3.1  < 3.1.1

so the appversion>3.1b should work

Brij Charan

unread,
Apr 23, 2009, 6:02:32 PM4/23/09
to northwe...@googlegroups.com
Kaply suggested this.

for current
appversion<=3.0.*

for higher
appversion>3.0.*

Works like a charm.

Thx guys.
Reply all
Reply to author
Forward
0 new messages