Sunday, March 29, 2009

Firefox Minefield 3.6a1pre released

Congratulations! You've downloaded or compiled a "trunk build". This means that you've volunteered to become part of the testing community.

Helping out won't take much of your time, doesn't require special skills, and will help make future versions of Mozilla Firefox even better.



Download
[DIR]Parent Directory
-
[   ]firefox-3.6a1pre.en-US.win32.zip28-Mar-2009 06:50 11M
[   ]firefox-3.6a1pre.en-US.win32.installer.exe28-Mar-2009 06:50 7.6M
[   ]firefox-3.6a1pre.en-US.win32.complete.mar28-Mar-2009 06:50 10M
[   ]firefox-3.6a1pre.en-US.mac-shark.dmg28-Mar-2009 06:03 23M
[   ]firefox-3.6a1pre.en-US.mac.dmg28-Mar-2009 04:31 17M
[   ]firefox-3.6a1pre.en-US.mac.complete.mar28-Mar-2009 04:31 17M
[   ]firefox-3.6a1pre.en-US.linux-i686.tar.bz228-Mar-2009 04:01 9.4M
[   ]firefox-3.6a1pre.en-US.linux-i686.complete.mar28-Mar-2009 04:01 9.4M
[   ]firefox-3.6a1pre.en-US.linux-x86_64.tar.bz228-Mar-2009 04:00 11M
[   ]firefox-3.6a1pre.en-US.linux-x86_64.complete.mar28-Mar-2009 04:00 11M

Warning: This is NOT A FINAL OR PRE-RELEASE VERSION. This program is provided without any guarantees of stability, so please use it at your own risk. It is recommended that you back up your profile regularly, as there may be bugs that corrupt your data. If that sounds scary, you'd probably be better off with the latest version of Firefox that you can download here.
How Can You Help Test Minefield? QMO logo

Testing Minefield is easy for new and old users alike. The list of ways to get involved below are just the start. For more information on how to help, check out QMO.

Run Testcases in Litmus
One of the simplest ways to test Minefield is by running Litmus tests. These tests are easy to use, so create an account and dive in.
Reporting Bugs
Found a problem in Minefield? Reporting bugs is another simple way to help. You can file bug reports to Mozilla's bug tracking system which gets triaged by volunteers. As you learn more about Minefield, you can help triage bugs as well!
Submit crash reports
Please use the Crash Reporter and turn it on when it asks. The Crash Reporter reports give us really valuable data on which crashes are the most serious, and how often people are encountering them. All you have to do is make sure the "Tell Mozilla about this crash" box is checked. After reporting, you can view your crash reports by typing about:crashes in the Minefield location bar.
Use the Reporter Tool
Minefield comes with a tool for reporting broken web sites. From the 'Help' menu, select 'Report Broken Web Site' and provide as much information as you can about the issue that you are encountering. You can view reports on the Reporter website.
Mozilla QA Companion

The Mozilla QA Companion (QAC) is a new tool that was created after discussions between the QA team and community about how to make it easier for anyone to get involved with the Mozilla project and help us test Firefox.

The QAC is meant to be an easy way to get community members involved in the QA process. It pulls testcases from Litmus and provides a response form, all within the QAC interface. The QAC also includes notifications for important QA events such as Bug Days, and keeps users up-to-date with live feeds from the QMO site and forums. Chatzilla is also bundled in with the extension, with one-click access to the #qa channel on IRC.

This is currently in a Beta form, so there are likely to be minor issues. If you find a bug, please help us by reporting it in Bugzilla under the "Other Applications" product and "QA Companion" component (if you are using the simple chooser for reporting bugs, please click the "Other Products" link first). Be sure to check the current QAC buglist to make sure the issue isn't already filed. Let's work together to make the Mozilla QA Companion even better!

Features

  • General QMO tab -- updates on news, forums, etc.
  • Litmus tab -- This is the heart of the extension. It allows users to get testcases to run and to submit results from within the extension. A setup wizard detects most system settings and helps new users set up a Litmus account if they don't have one already.
  • Bugzilla tab - Look up bugs by id, run keyword queries, or check all bugs filed today!
  • Chatzilla tab -- This is a one click launch into the wacky world of the #qa channel!
  • Settings/Help -- This is for the confused or misconfigured.

Installation

You can install the QA Companion like any other Firefox add-on by visiting https://addons.mozilla.org/en-US/firefox/addon/5428

Getting Started...

Once it is installed, just click the orange and blue "Q" QMO logo in the browser's status bar at the lower right. This will bring up the extension for you.

You can see an example of the main window below. This main page contains links to QA content, upcoming events , and forum discussions and posts from QMO.

If you select the "Litmus" tab at the top of the extension window, it will allow you to run test cases in Litmus.

The "Bugzilla" tab allows you to search for bug or run a few simple queries. You search by keyword or just click "Show all bugs filed today" for a quick look at the latest reported issues:

Here is a quick rundown of the other tabs:

  • The "Chat" tab allows you to log into irc.mozilla.org by launching the built-in Chatzilla client.
  • You can setup your Litmus account info on the "Settings" tab.
  • And if you need some help, you will find some useful links in the "Help" tab.

The interface is fairly intuitive and easy to follow, but please let us know if you have any questions. Find us on IRC or post to the QMO forums. We hope you find the Mozilla QA Companion a useful tool that helps you get more involved with the Mozilla QA community

Get Chitika | Premium


Related Post


Yahoo!    Personals


123inkjets.com    - Printer Ink, Toner, & More

  • Get Paid     to Blog About the Things You Love


iPowerWeb    Web Hosting


Linux Links


Firefox Mobile (Fennec) 1.0 beta 1 released

Mozilla released Fennec 1.0 beta 1 last week, which Stuart Parmenter announced on his weblog. “Fennec 1.0 beta 1 includes lots of great improvements, especially around performance. We’ve done heavy optimizations to our frontend code and made a number of optimizations to the platform.

We’ve enabled TraceMonkey, bringing to mobile the huge JavaScript speed improvements the JIT has brought to Firefox 3.1 betas.

On the feature front, we’ve enabled plugins so you can now watch videos on your favorite sites, and we’ve got in our first pass at improved bookmark management.” For more details, see Stuart’s original post or check out the release notes.

I’m super happy to announce the first beta release of Fennec for the Maemo platform.

Fennec 1.0 Beta 1 includes lots of great improvements, especially around performance. Starting with this beta, I’m able to use Fennec as the primary browser on my N810. We’ve done heavy optimizations to our frontend code and made a number of optimizations to the platform, resulting in greatly increasing zooming speed and making panning pretty smooth. We’ve also been able to improve startup performance by reducing a good bit of unnecessary work. We’ve enabled TraceMonkey bringing to mobile the huge JavaScript speed improvements the JIT has brought to Firefox 3.1 betas. A number of performance hotspots have been identified that we’ll continue to focus on until we ship final – in fact, we have fixed number of issues already for the next beta.

On the feature front, we’ve enabled plugins so you can now watch videos on your favorite sites, and we’ve got in our first pass at improved bookmark management and support for bookmark folders. A lot of time was spent on infrastructure that we could use to build the rest of our app with. You’re now able to scroll things like preferences and the new bookmarks list. One of our main focuses for the next milestone will be on polishing the user interface — areas like the extension manager will get a face lift and we’ll start working more on some of the usability issues people have reported.

Madhava Enros, our lead user interface designer for Fennec, has put together a great video of Beta 1 that not only shows off many of the things we’ve done but also does a great job of explaining many of the choices we’ve made.


Add-ons are starting to pop up and are already showing some of the great possibilities that Fennec provides.

The Weave guys have been working hard and have an extension for Fennec now that allows you to sync data from your desktop to Fennec. Having your desktop’s tabs, bookmarks, and awesome-bar contents on your mobile device really make a huge difference.

Mozilla Weave


Related Post


Yahoo!    Personals


123inkjets.com    - Printer Ink, Toner, & More

  • Get Paid     to Blog About the Things You Love


iPowerWeb    Web Hosting


Linux Links

Monday, March 23, 2009

The Android vs. LiMo Conflict: What’s the difference?

Although not discussed often, LiMo (Linux Mobile Foundation) is a formidable competitor for the Android platform. So isn’t LiMo, a consortium of partnered companies, inherently a competitor of the Open Handset Alliance?

Core companies that support Android’s cause are members of the Open Handset Alliance, defined as, “a group of mobile and technology leaders who share this vision for changing the mobile experience for consumers.” They claim that their, “first joint project as a new Alliance is Android.”

So although Android is technically owned by Google, the OHA website makes it clear that Android is a product of this “group effort”. Furthermore, the OHA site identifies that the goal of Android is: “to be the first open, complete, and free platform created specifically for mobile devices.”

Get Chitika | Premium

Hmmmm… so what is the goal of LiMo? Directly from their website:

LiMo Foundation is an industry consortium dedicated to creating the first truly open, hardware-independent, Linux-based operating system for mobile devices.

So it would appear they have the same goal. Since that goal includes the word “first” only one of them can accomplish that goal. It appears that Android will be first to market with an enabled handset, but we can’t help but note that word “truly” stuck between “first” and “open” in LiMo’s mission statement.

Are they taking a carefully calculated swipe at Android and the OHA because it’s not truly open? Maybe, but LiMo was formed at the beginning of 2007, before Android was announced.

Does that word “truly” have significant value in the battle between Android and LiMo? You can bet your boxers on it. (Female readers can bet their panties or underwear or whatever else, “boxers” just sounded much more cool.)

The fact that Android isn’t completely open really isn’t news to anyone. The fact remains: the practice of mobile carriers to strictly limit (and inhibit) the software capabilities on otherwise perfectly capable handsets presented an opportunity for Google to wedge themselves between Manufacturers and Carriers, supplying invaluable potential to consumers. Nobody is naive enough to believe they’re doing it simply for the “the love of the game” so to speak… they’re doing it for profit.

This could be considered an irritation to mobile carriers who purposefully restrict consumer’s abilities, force them to use their own proprietary software and then charge them an arm and a leg for additional features.

While LiMo may seem to be taking the high road by providing the first Linux OS that is “truly” open… we ask them the question… Open for who?

On page 3 of the Limo Foundation Overview (PDF), they claim to be “Middleware OS Only - avoiding conflict with operators, handset vendors and content providers.”

And thus is the reason that the two biggest carriers in the United States, AT&T and Verizon, haven’t joined the Open Handset Alliance. As Ralph De La Vega, CEO of AT&T Mobility, explained the hesitance of offering an Android handset, “One of the things we were looking for was that it was truly open and that you could put other features and applications on it.”

You mean like AT&T revenue generating features instead of Google revenue generating features?

Interesting to point out that Ralph uses that golden word “truly open”… including the word “truly”. AT&T isn’t a member of LiMo or anything, but the bottom line is that these companies want a “truly open” platform so they can close it right back up to their liking. The LiMo Overview outlines that Applications and Content is “as decided by user,” but how much flexibility will they have in the decision making process?

Had the stakeholders in the Mobile Industry done more to benefit the customer instead of worrying exclusively about their pockets, a “LiMo” type organization would have been formed much earlier and they never would have left the door open for Google. Instead, they’re stuck in a precarious situation wondering how they can open their phones to provide consumers more without giving Google the keys to the mobile content house.

For some of these companies it looks like LiMo will be the answer. Unfortunately for LiMo it’s simply too late. If LiMo was so promising, why would 3 out of their 8 founding members join the Open Handset Alliance (Motorola, NTT Docomo, Samsung)? Why would half of their self proclaimed “Core Members” join the OHA (Aplix, LG, Texas Instruments, Wind River)? Especially considering they share the same exact mission… only Google’s end result will be a better, more polished and capable product.

The fact is that LiMo is doomed to either fail completely or be rendered inconsequential. Nonetheless, LiMo today announced the addition of 7 gullable companies and 1 spiteful Verizon. Did anyone know that LiMo has already announced 18 handsets from 7 companies that will utilize the platform?

Take the small number of people who knew and multiply by the percentage of people that cared and you have, coincidentally, the exact same number of combined employees working for LiMo member companies.

Perhaps we’re being a little harsh on LiMo. Afterall, in the incredibly unlikely scenario that Android doesn’t shine, somehow fizzles and ultimately goes under, the mobile industry will have a Plan B. Not to mention, for cheaper devices that aren’t expected to do as much extra-curricular stuff anyways, LiMo could be a quick, easy alternative.

With LiMo’s recent announcement that Verizon had hopped onto their Board of Directors, things are starting to heat up between the LiMo platform and Google’s competing product, Android. Both are open-source Linux-based platforms, and both are aiming to rock the handset market sometime in the next year or so.

LiMo is Linux-based. Android is Linux-based. But they’re far from the same. Below, I’ll try to explain some of the key differences without going too heavy on the tech jargon. (Fiiine. It gets a bit heavy for a paragraph or two. But I’ll avoid it where possible.).

1) Backers/Funding

LiMo: The LiMo platform is backed by the LiMo Foundation, which was founded by Motorola, NEC, NTT DoCoMo, Orange, Panasonic, Samsung, and Vodafone, and has since added 34 other members to the list.

In membership fees alone ($400k a year for each of the 9 “Core” members, and $40k a year for each of the 25 “Associate” members) , the foundation has raised at least 4.6 million before adding in whatever funds the founding members pitched in at the start.

Android: Android is backed by the Open Handset Alliance (OHA). OHA has 33 founding members besides Google, including 3 of the LiMo Foundation’s 7 founders (namely Samsung, Motorola, and NTT DoCoMo). No word on Android’s budget so far.

While the way Google flashes cash with things like the $10 Million Dollar Android Developer Challenge doesn’t absolutely prove that their budget is larger, it certainly implies it.

In other words: Both platforms have massive companies as partners, and presumably a good amount of money behind them. Android is largely touted as a Google project, where LiMo isn’t really pushed as being under the wing of a single company.

2) Dev Status

LiMo: LiMo was announced in January of 2007, the first handsets hit in early 2008, the API (Application Program Interface, a set of pre-defined routines for developers to utilize) is available now , and their software development kit (programming tools and documentation for developing and testing applications) is set to release in the second half of 2008.

Android: Android was announced on November 5th of 2007, and an early version of their SDK was released within a week. The first Android handsets are planned for the end of 2008.

In other words: LiMo has devices on the market and an API available, but no SDK. Android isn’t available on any handsets yet, but already has an SDK in the hands of developers. Before anyone has really began working on LiMo applications, we’re already seeing Android apps being demoed.

3) Applications

LiMo: LiMo applications can be written in C/C++, allowing them to run natively.

Android: Android applications are written in Java, so all applications will be running in a Virtual Machine. Virtual Machines mean CPU overhead, meaning applications that may not be as efficient as if they were running native. However, it almost absolutely guarantees a standard application environment across Android devices.

In other words: LiMo applications are running in a language the operating system (OS) inherently understands, while Android applications are running in a virtual environment on top of the operating system.I was wrong - Android apps aren’t running in a Java VM, they’re running in a Dalvik VM. As such, portability in either direction is unlikely.

4) Handsets/Carriers

LiMo: There are a number of LiMo based handsets on the market, from Panasonic, NEC, Motorola, Purple Labs, LG, or Aplix. Current carrier partners are Vodafone and NTT DoCoMo, and Verizon has announced plans to offer LiMo devices in 2009.

Android: HTC has mentioned that they’re working on at least 2-3 Android handsets for 2008, and LG is working on at least one for 2009. The other handset manufacturers registered as Open Handset Alliance members are Motorola and Samsung. Current carrier partners are Sprint Nextel, T-Mobile, China Mobile, Telefonica and Telecom Italia.

5) Hype

LiMo: Fairly low. There just isn’t much chatter about LiMo, besides articles summarizing press releases. I couldn’t find any LiMo enthusiasts, or communities focused around LiMo devices.

Android: High, largely because of Google’s involvement and all the speculation that went on before it was announced. I found a number of opinion articles on Android, and a handful of budding fan forums.

6) Design Aspects

LiMo: Middleware only, meaning LiMo only handles things that are tucked below what the user actually sees. User experience items, such as the interface, are the responsibility of those developing the device.

Android: Android is a full software stack, meaning it consists of an operating system, middleware, user interface, and applications. Android will have a standard user interface, but as it is open source, the carrier/manufacture, and potentially the end user, are free to change it.

In other words: LiMo is only part of the software package that goes on a device, while Android is pretty much the whole package. If those developing the device are looking to start with a complete software solution, they’d probably go with Android. If they’re looking to write their user experience layer from scratch, they’d go with LiMo.

So who will win?

That’s a hard question to answer, as they both offer a totally different solution. Google offers a complete solution, which can be remolded from the top down. LiMo’s solution provides a foundation, on which developers can build the user experience from the ground up.

In terms of adoption, I’m willing to bet Android will reign victorious in the end. The crowds are already buzzing about it, and a number of developers are already cracking out code for it. Thanks to Google’s name being beside it at all times, it’s the first time I’ve ever heard a mobile operating system discussed amongst my non-gadget-obsessed friends (Even though it was just another “OMG! Is this going to be better than what’s on the iPhone?!?!” conversation,) and it hasn’t even hit the market yet.

Related Post


Yahoo!    Personals


123inkjets.com    - Printer Ink, Toner, & More

  • Get Paid     to Blog About the Things You Love


iPowerWeb    Web Hosting


Linux Links


Sunday, March 22, 2009

YES Linux Basic Edition 3.0.0 available now

YES Linux a distribution that is focused on ease of use, user experience, and the internet. In 2 screens a secure server is installed and administered from a browser. A user should not have to use the console, but can if they wish.

Primary Download Servers
Download Mirrors
Source - Subversion
Source - CVS
Binary - Packages (Web)
Binary - Packages (Ftp)
Binary - Packages rsync://rsync.gtlib.gatech.edu/yeslinux-cvs/ (rsync)

Packages: YES Linux 2.2.3 Dated 09th May 2005

Check the YES Linux packages list for 2.2.3.
Package List

Packages: YES Linux 2.2.2

Dated 03rd Apr 2005


Check the YES Linux packages list for 2.2.2.
Package List

Packages: YES Linux 2.2.1

Dated 15th Mar 2005


Check the YES Linux packages list for 2.2.1.
Package List

Packages: YES Linux 2.2.0

Dated 04th Mar 2005


Check the YES Linux packages list for 2.2.0.
Package List

Packages: YES Linux 2.1.2

Dated 07th Feb 2005


Check the YES Linux packages list for 2.1.2.
Package List

Packages: YES Linux 2.1.1

Dated 02th Feb 2005


Check the YES Linux packages list for 2.1.1.
Package List

Packages: YES Linux 2.1.0

Dated 18th Jan 2005


Check the YES Linux packages list for 2.1.0.
Package List

Packages: YES Linux 2.0.13

Dated 04th Jan 2005


Check the YES Linux packages list for 2.0.13.
Package List

Packages: YES Linux 2.0.12

Dated 09th Oct 2004


Check the YES Linux packages list for 2.0.12.
Package List

Packages: YES Linux 2.0.11

Dated 21th Sep 2004
Screenshots




Gif Euro 728x90






Recent Posts

Linux News

My Blog List

Flickr Photostream

Antipixels & Counters

BlogESfera Directorio de Blogs Hispanos - Agrega tu Blog Add to Technorati Favorites BlogItalia.it - La directory italiana dei blog Il Bloggatore Find the best blogs at Blogs.com. Computer Blogs - BlogCatalog Blog Directory AddThis Social Bookmark Button page counter