Welcome, Guest. Please login or register.

Author Topic: Sponsor AROS or AWeb development  (Read 4908 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline 23JUL

  • Newbie
  • *
  • Join Date: Mar 2002
  • Posts: 32
    • Show all replies
    • http://amiga.name
Re: Sponsor AROS or AWeb development
« on: June 26, 2002, 12:27:18 AM »
Well, I can't sponsor, because I  lack money, a usable Amiga and money.

Though,
I think the Amiga Web Experience (hmm, that sounds like a MS commercial), only could benefit ultimately if Mozilla/Gecko could be compiled for the Amiga platform.

So who starts a framework to get that code compiled?
 

Offline 23JUL

  • Newbie
  • *
  • Join Date: Mar 2002
  • Posts: 32
    • Show all replies
    • http://amiga.name
Re: Sponsor AROS or AWeb development
« Reply #1 on: June 26, 2002, 03:50:13 AM »
> What IS missing on the Amiga side of things is the plugins.

Come on, the plugins should plug in *somewhere*... ;)

So why not use the codebase that
a) has its standard way for plugins
b) is proven to work under different OS'es.
c) is being developed by many people.
d) is more compliant towards w3c standards than any other browser!

http://www.alistapart.com/stories/tohell/
 

Offline 23JUL

  • Newbie
  • *
  • Join Date: Mar 2002
  • Posts: 32
    • Show all replies
    • http://amiga.name
Re: Sponsor AROS or AWeb development
« Reply #2 on: June 26, 2002, 05:36:14 AM »
Quote
Tell me how much harder it is to adapt plugin code from another platform/browser to this platform/browser combination vs porting Mozilla and then the plugin code.
Too be honest, I haven't got a clue. I guess the first option would be less harder, and is more in the line of the Amiga way of doing things. Nevertheless, by following that path, you are still stuck with an outdated browser. (*) In other words: I can't garantuee my pages are correctly interpreted.

(*) On the other hand: I can't say much about the currently used browsers on the Amiga, since I don't have access to a properly configured and fast enough machine. I don't know whether there are xhtml, xml, html, xls, css1/2,  dom1/2, dtd, javascript/ecmascript compliant and/or capable browsers for it, but these are at least the 'technologies' which are counting for the other half of the 'webexperience' without plugins.

Quote
Note that you are conversing with someone who has ported Mozilla before onto two platforms.
Share your experience with the third ;)

Quote
I dont think AmigaOS needs Mozilla, I think it needs a *better* browser than all the other platforms - the Amiga edge. With Mozilla there is no value add to using AOS.
I think AmigaOS needs Mozilla, although I admit I would love to see a better browser for AOS. The value added by Mozilla is at least a choice how to browse and how a page may be interpreted by the rest of the world...

Quote
>d) is more compliant towards w3c standards than any other browser!

Note this is not true. I suggest you poke around http://www.w3c.org and do a bit of reading from the proverbial horses mouth.
Okay, that may not be 100% true, but it is at least my experience by assigning some css and javascripts to pages, Mozilla did the job better (than ie, o and konq) by being more consistent with the proposals the w3c made (especially the boxing model and event handling).

Getting offtopic.

Main reason I wrote here was that someone wanted to program for money, I don't have money, only the suggestion for a Mozilla port framework, because I think that really is worth the money.