Slashdot Mirror

FAQ: http://mozilla.org/start/1.0/faq/

Don't bother looking at these in IE 5.0, its PNG support is rubbish.

Click here to download it.

You can download it here.

The basic strategy I would see for open source game development would be to keep the data proprietary, similar to the current situation with Doom and the first two Quakes (and I think some others).

This is based on the idea that game engines resemble each others to some degree and that the differentiating factor will be the maps/levels/artwork/scripting and so on. You can thus get improvement done on the engine contributed back to you, and others can make their own original games with your engine, but nobody is playing your exact game for free.

This strategy, of course, supposes that there is some significant amount of non-code data involved. If this is a puzzle game whose's only non-engine resources are backdrop images, this strategy is not effective.

Remember to mark down contributions from the outside somehow, because you might want to relicense the engine under a non-open license (or maybe just change the license to another open source one), and you'll have to ask permission from the copyright owners of these patches (remember what is happening to Mozilla!). Having them assign copyright to you, having a "clean" codebase branch or keeping contact information are three possible approaches.

Also, if you have some truly innovative technology in the engine that you think nobody else has, it might make sense to hold off the release a bit, so that you can build a market lead on that technology, then as competitors come up with equivalent technology, you can then release the source code.

See Software Secrets: Do They Help or Hurt?.

And work from there. It doesn't nessesarily have to be game related, RPGdev will be using XPCOM and other Moz tech. That is, when I can get back to dealing with RPGdev.

Making money is all a matter of licenses -- if you create the engine as MPL'd software, then you can later on use the engine in a closed-source game for the shelves.

don't you understand anything about how slashdot works? i mean, they cover the usual geeky tech things, but there are are number of things that always get the spotlight.. they are:
1. linux kernels
2. debian news
3. kde news
4. mozilla news

on slashdot, if you disagree with any of the above 4 topics, the bot-moderators automatically flamebait your ass into oblivion...

Try these Talkback enabled builds which transmit information about your crashes to a database where engineers can discover the most common crashes and fix them. Send a report for each crash you find during normal everyday use. Talkback is an easy way to report bugs and for a change, filing duplicate reports is good!

From my experience (#114517, if slashdot links are blocked), the maintainers/programmers have been really helpful and professional. But bug reports are almost useless if the person submitting them doesn't take the time to do it right. Reporting bugs is almost an art, and if approached with a humble and helpful attitude can be very helpful.

--Robert

Oh yes, jwz is throwing a Mozilla 1.0 release party at DNA Lounge. I wouldn't call it "being sorry about quitting the project and dissing it", though... As I understand it, he never said that he didn't want Mozilla to succeed; all he said was that it was moving to slowly for him and he wanted to spend his time on something else. In fact, he would like to use it at his terminals at DNA Lounge, but can't do so yet because there is no way to rebind the mouse buttons. (I'm not posting the bug number here since I don't want Bugzilla to be slashdotted once again.)

Also check out his backstage log entry about this party; interesting stuff.

The main change is that many APIs (Application Programming Interface) have been frozen, which means that you can now create skins, plugins, add-ons, XUL applications, applications which embed Mozilla's layout engine Gecko, etc., which will work with all future Mozilla 1.x releases. In the past, it wasn't unusual for, say, skins developed for Mozilla 0.x to break as soon as Mozilla 0.y was released.

Of course 1.0 is also more stable and polished than 0.9.9, just like 0.9.9 was more polished and stable than 0.9.8 and so forth, but the main thing is the API freeze.

See also the Mozilla 1.0 Manifesto.

The main change is that many APIs (Application Programming Interface) have been frozen, which means that you can now create skins, plugins, add-ons, XUL applications, applications which embed Mozilla's layout engine Gecko, etc., which will work with all future Mozilla 1.x releases. In the past, it wasn't unusual for, say, skins developed for Mozilla 0.x to break as soon as Mozilla 0.y was released.

Of course 1.0 is also more stable and polished than 0.9.9, just like 0.9.9 was more polished and stable than 0.9.8 and so forth, but the main thing is the API freeze.

See also the Mozilla 1.0 Manifesto.

The main change is that many APIs (Application Programming Interface) have been frozen, which means that you can now create skins, plugins, add-ons, XUL applications, applications which embed Mozilla's layout engine Gecko, etc., which will work with all future Mozilla 1.x releases. In the past, it wasn't unusual for, say, skins developed for Mozilla 0.x to break as soon as Mozilla 0.y was released.

Of course 1.0 is also more stable and polished than 0.9.9, just like 0.9.9 was more polished and stable than 0.9.8 and so forth, but the main thing is the API freeze.

See also the Mozilla 1.0 Manifesto.

Opera isn't open source. Mozilla and Galeon are. You are using Linux, right?

-dwc, trying too hard to troll

By applying the bugzilla patch #139682, you can roll your own 0.2.8 Chimera within about 8 hours on a 500 mHz iMac.

It is also the reason why the OSI keeps a list of approved licenses.

Far more apropos in the context of this thread is the FSF's license list and explanation of copyleft. Debian's concerns map far closer to Free Software movement's concerns than the Open Source movement's concerns because Debian cares about software freedom. The Open Source movement dismisses software freedom and advocates licenses that constitute gifts to proprietors (including the X11 license and the new BSD license) because businesses are the main target of the Open Source message. The Free Software movement, on the other hand, is concerned with software freedom and insuring these freedoms for all computer users. This insurance is one of the reasons why the GNU project (or perhaps it was the FSF) invented the concept of copyleft.

If you didn't take time to understand the license before contributing to the project, you can't complain that you don't like the result.

Just because you contribute something to a project doesn't mean you relinquish your copyright power. This is why the Mozilla project is currently looking for some authors who contributed copyrighted work to that project. The Mozilla project can't change the license on these contributions without the copyright holder's permission.

I know everybody finds it humorous that the main party is being held at the DNA Lounge, but it doesn't look like some tricky plot to rub the release in JWZ's face. Instead, it looks more or less like an act of goodwill from JWZ. The location was suggested by JWZ in Bug 10039, the bug slip that seems to have started the party idea:


------- Additional Comment #48 From Jamie Zawinski 2002-04-07 17:13 -------

You are welcome to have your party at DNA Lounge if you cover our staff costs,
and if it's on a night when we're not already booked.


So, heh. I don't know why people seem so quick to think that the Mozilla crew would do that sort of thing.

http://www.schnitzer.at/mozparty/#5

I'm organizing that party! However, I'd rather have someone else deal with organizing an managing it, especially after being staff for Canada's #1 anime con, Anime North.

It's an open invitation, just show up at Vinnie's (22 Duncan St.) in Toronto on the Saturday after release and follow the noise. I'd like to have a banner to hang, and Moz1.0 CDs to hand out.

I attended the original mozilla dot party in 1998, and there were more women there than I expected (including a fair share the non-geek type).

Cocoazilla

Provide a Cocoa NSView for embeddors - this is done with NSBrowserView.
...
Buildable from ProjectBuilder - we will provide a Cocoa framework for Gecko

Hope that helps,
-Ster

I don't see a retraction any time soon.... in fact, mozilla won't even be on his kiosks until this and this are fixed.

I don't see a retraction any time soon.... in fact, mozilla won't even be on his kiosks until this and this are fixed.

Here ya go, you're all invited... now why don't you print out a bunch of these onto glossy postcards and leave them around your local college campus like all the promoters do at mine?

21+, sadly. See this.

Not in my browser they can't. Edit -> Preferences -> Advanced -> Scripts & Windows -> Allow webpages to change status bar text.

Your using a CFM build... get you mach0 build from
Mozilla.org Nightly (working again) or Riscky Mach-O build... which tends to run a tad faster

Doubtly they'll strip it in Netscape thus you'll soon have it in Netscape 7 or whatever. BTW why not to install mozilla right now?

Or mozilla.

Where should one go to keep track of what features and what bugs are in a particular build?

Mozillazine build bar talkback,
Mozillanews build votes, or cc yourself on specific bugs in Bugzilla to find out when they're fixed.

Also, where is this "wild-west" repository? I don't see anything like that in http://ftp.mozilla.org/pub/mozilla/

nightly/latest-trunk

How the hell do I disable HTML rendering in the email client? There should be a bloody option for this! It's still not in RC3.

I read that page closely. Since you mentioned DOM in particular, have you perused Mozilla's list of open DOM-related bugs of late. 709 open bugs specific to DOM, 57 of which are specific to "DOM Core".

This is precisely why I said we probably don't want to get into a debate over which is closer to 100% compatible. Opera IS very near 100% standards compliant. One of Opera's stated goals is to BE 100% compatible with W3C standards.

They are in the same boat as Mozilla as far as standards compliance...they both are NEAR 100% compliance, neither IS, and BOTH are more compliant than IE.

It's better to file a Tech Evangelism bug in Bugzilla for sites that don't work. That way, the Mozilla team can track these sites and offer technical assistance to make them standards compliant.

With the latest versions of Mozilla, it automatically detects JRE 1.4.0 and uses it. Try the latest nightly and report a bug if it doesn't work.

This is completely bogus.

Try here, with the Widget example or sprite demo 4, or this Donkey Kong game rendered in DHTML. Maybe the most obvious example is Video pool which is very smooth with IE and totally unplayable with NS6 despite using virtually no code forking. (BTW, I'm not plugging my site gratuitously, it's just that I've written all these scripts and tried to address Mozilla's speed problems. There are plenty of other people commenting on this topic on other sites, eg Scott Andrew who amongst other things writes articles for Apple's website.)

Don't just take it from me though, Mozilla's OWN developers acknowledge the serious performance problems with DHTML. See here: http://bugzilla.mozilla.org/show_bug.cgi?id=129115 . I have Mac, Windows and Linux platforms here, and with the exception of Linux (for obvious reasons!) IE outperforms NS by an extremely wide margin with dynamic content.

Of course, if anyone would provide a link to a DHTML script that runs faster in NS6/7/Moz than IE then I'd love to see it. No? Didn't think so...

I did not specified the platform, sorry. Page setup from file menu may work under windoze but not under
linux nor under macosx. There is a bug open (look here).

user_pref("dom.disable_open_click_delay", 1000);

From: the customizing mozilla-guide:

When the dom.disable_open_click_delay pref is set to a non-zero number, window.open will fail when called more than that number of milliseconds after a mouse click.

Startup time: Use quick launch if you're on Windows.

Minimize: What? It takes a split second on my 333mhz laptop (64 MB ram).

UI terrible: Uh what? Why?

CSS: Support is better than *any other browser* so what's your point?

Supporting broken table layout: I believe this might be the ingenious quirks mode they have implemented.

AOL drivel: Then use Konqueror. I personally am aware that many Mozilla developers are paid by Netscape but it doesn't bother me. What's important is to get a standards compliant browser that kicks IE to hell in order to get a balance on the web again. I doubt Konqueror will be able to do that.

The 4 years: The reason it has taken so long is because they are trying to do it right this time contrary to build something with a bunch of hacks.

N 7.0PR1 is based on M 1.0RC2.

Answer to (2), probably not. That code is propietary and belongs to Netscape. But futurology is a very uncertain science.

There is a thingy called "Roadmap". While there is no definitive date for the final release, it may happen as soon as next week.

...the DHTML performance will increase?

The current series has a bad bug in DHTML animation performance that I've noticed -- performance regressed in the 0.97 -> 0.98 release, and ever since then rapid animations etc. have often not rendered correctly.

Read through the bugzilla entry there -- apparently some experimental builds have 450% increased JavaScript animation speed, some test are linked to try it out yourself. Does anyone more in touch with the Moz project internals than I have an idea as to when this will be integrated with the main branch of the code -- I heard 1.01 was the target a while back?

I say this as Moz is looking more and more likely to turn up on user's desktops as part of AOL/Compuserve/whatever as they escape from MS's browser licensing terms. Bugs in release candidates are fine (that's what they're there for) but if mass-market NS7 has shortfalls like these, it could spell trouble for JavaScript developers like me.

Anyway, more power to the Mozilla project! It's good to see a truly free, standards compliant, cross-platform browser out there. Looking back a year, I wonder what it'll be like in a year's time...

See: this page for a list of mozilla keyboard shortcuts. In particular, ctrl-n is new window, ctrl-t is new tab. ctrl-w close tab (or window if only one tab is present). ctrl-pgup/ctrl-pgdwn to cycle between tabs.

That would be bug 51584, which is marked as a dupe of bug 39057 (you may have to cut-n-paste the url(s) into your browser, in case Bugzilla is still blocking referrers from Slashdot).

That would be bug 51584, which is marked as a dupe of bug 39057 (you may have to cut-n-paste the url(s) into your browser, in case Bugzilla is still blocking referrers from Slashdot).

That would be bug 37867 (you may need to copy-n-paste the url into your browser, in case Bugzilla is still blocking referrers from Slashdot).

Can it get rid of those stupid animations that show up on top of the page you are trying to read?

Mozilla does have customizable key bindings, and has had for *ages*. What it doesn't have (and really needs) is a nice GUI interface, so that the average end user can make those sorts of changes. For more details, see http://www.mozilla.org/unix/customizing.html#keys

3. I don't want enter to submit a comment when I'm typing in a text box, I want it to add a new line. On input field it is differt, there aren't multiple lines so enter does what you want. Actually I wish tab didn't leave a text box sometimes.

Yes, you can blame yourself for not being super-cautious, but thosee keybindings really aren't helping. (I should probably have filed a separate bug for that; please don't hesitate to do so, I'll vote for it.)

And while at it, I found the whole tabbing behavior much better in 4.x. When on a web page it would put focus back into the location bar, not on the unpredictably positioned next link in the document. When reading mail I prefer it to cycle through window panes, not through the half dozen links that someone may have in their sig. Keep control-tab for that.

Uhhh, Mozilla? Or Netscape 7? Or Beonex? Or K-Meleon?

On my windows box, I Use mozilla as my primary browser (tabs, what is new about this?).

The bad history of IE security is the only problem I have with IE, and this is the reason why I won't use it.

As much as I personally don't like using netscape, I would really like to see them succed with a little help from AOL. My motivation isn't to prevent IE winning the browser wars, but more to make web developers accept that IE isn't the only web browser. I get very annoyed by random web pages that require internet explorer.

For what it is worth, I would like MS to win the browser wars, providing web pages like these become a thing of the past, this way all the script kiddies will continue to target IE users, making my browsing more secure with my prefered web browser.

On my windows box, I Use mozilla as my primary browser (tabs, what is new about this?).

The bad history of IE security is the only problem I have with IE, and this is the reason why I won't use it.

As much as I personally don't like using netscape, I would really like to see them succed with a little help from AOL. My motivation isn't to prevent IE winning the browser wars, but more to make web developers accept that IE isn't the only web browser. I get very annoyed by random web pages that require internet explorer.

For what it is worth, I would like MS to win the browser wars, providing web pages like these become a thing of the past, this way all the script kiddies will continue to target IE users, making my browsing more secure with my prefered web browser.

http://bugzilla.mozilla.org/show_bug.cgi?id=136915 - create yourself a bugzilla account and vote for that bug.