Hello Guys/Gals,
One of me colleagues at work just called to check if i had a solution on an IE to firefox porting issue. Glad to know that commercial applns are now being forced the firefox way..:D. Will mention the challenge in brief :
35000 html pages javascript written for IE DOM based on IE
What would be the best way for me to port this IE based application to firefox such that we can use it from Linux as well as MS???. Are there any automated tools/parsers that i can make use of??.
Secondly, the other through process i had in mind was...if the first part isnt feasible can we build plugin the IE javas script and DOM model support into firefox as a plugin. This sounds ambitious but am just trying to explore some options out here where none seem to exist.
Thanks in advance guys.
Trevor
Sometime Today, TW cobbled together some glyphs to say:
35000 html pages javascript written for IE DOM based on IE
what the heck are they doing with 35000 html pages and no CMS? Get them onto drupal or wordpress soon.
What would be the best way for me to port this IE based application to firefox such that we can use it from Linux as well as MS???. Are there any automated tools/parsers that i can make use of??.
don't port it - you'll be porting for the rest of your life with every new browser that comes out. follow a layered development approach (LSM). Read up on progressive enhancement and behavioural separation.
Pihlip
--- Philip Tellis philip.tellis@gmx.net wrote:
don't port it - you'll be porting for the rest of your life with every new browser that comes out. follow a layered development approach (LSM). Read up on progressive enhancement and behavioural separation.
Indeed. There are several well documented means of separating presentation from content and behaviour.
At work, we use the Behaviour Javascript library regularly, along with Prototype, Scriptaculous, Dojo, GWT, Yahoo UI Library, etc.
Using Behaviour lets us author code such that the generated/static HTML contains HTML markup + data + classes + IDs. Our CSS is stored in a separate file, and the Javascript is bound to the HTML elements via Behaviour's bindings. The HTML content doesn't even have any "onclick" or "onload".
See http://bennolan.com/behaviour/ (Ignore the mandatory AJAX mentions if your app's not AJAX).
-- Sriram
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Thanks Philip/Sriram.
Trevor
On 9/5/06, Philip Tellis philip.tellis@gmx.net wrote:
Sometime Today, TW cobbled together some glyphs to say:
35000 html pages javascript written for IE DOM based on IE
what the heck are they doing with 35000 html pages and no CMS? Get them onto drupal or wordpress soon.
What would be the best way for me to port this IE based application to firefox such that we can use it from Linux as well as MS???. Are there
any
automated tools/parsers that i can make use of??.
don't port it - you'll be porting for the rest of your life with every new browser that comes out. follow a layered development approach (LSM). Read up on progressive enhancement and behavioural separation.
Pihlip
-- There is a multi-legged creature crawling on your shoulder. -- Spock, "A Taste of Armageddon", stardate 3193.9
--- Trevor Warren trevorwarren@gmail.com wrote:
Hello Guys/Gals,
One of me colleagues at work just called to check if i had a solution on an IE to firefox porting issue. Glad to know that commercial applns are now being forced the firefox way..:D. Will mention the challenge in brief :
35000 html pages javascript written for IE DOM based on IE
What would be the best way for me to port this IE based application to firefox such that we can use it from Linux as well as MS???. Are there any automated tools/parsers that i can make use of??.
None exist. You'd have to resort to one or a combination of the following: 1. When accessing IE specific object attributes, replace the object.property calls with a function call that returns a browser specific property.
2. On document load, add to the object's prototype those IE attributes that FF does not have.
Secondly, the other through process i had in mind was...if the first part isnt feasible can we build plugin the IE javas script and DOM model support into firefox as a plugin. This sounds ambitious but am just trying to explore some options out here where none seem to exist.
This is not really far fetched. I'm teaching myself the Firefox architecture, and aim to write similar FF extensions. There is a market for such extensions, and willing customers. Getting the app to a wider audience would have higher priority as compared to making the app cross browser compatible.
Just a tip: Before your colleague gets started with the migration, ask him to use Sahi (http://sahi.sourceforge.net/)to record the app's behaviour in IE. Then as they port the pages to FF/Safari, they could run Sahi tests to ensure that the application behaves as on Windows.
-- Sriram
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Just a tip: Before your colleague gets started with the migration, ask
him to
use Sahi (http://sahi.sourceforge.net/)to record the app's behaviour in
IE.
Then as they port the pages to FF/Safari, they could run Sahi tests to
ensure
that the application behaves as on Windows.
Sahi looks like some seriously helpful stuff. Thanks for letting us know this tool.
Harshal.
On 9/6/06, Harshal Vaidya harshalx@gmail.com wrote:
Sahi looks like some seriously helpful stuff. Thanks for letting us know this tool.
A tool similar to Sahi is TestGen4web you can find it here: http://developer.spikesource.com/wiki/index.php/Projects:TestGen4Web
The above is also a good recorder and replayer of the actions done in a web page and it generates xml file as output, so it will be easy for further manipulations.
HTH.
-
Harshal Vaidya -
Philip Tellis -
Senthil Kumaran S -
Sriram N -
Trevor Warren