mozilla

Mozilla Nederland LogoDe Nederlandse
Mozilla-gemeenschap

Flash Player Mozilla Firefox'a Geri Döndü - Tamindir

Nieuws verzameld via Google - mo, 20/07/2015 - 09:02

Tamindir

Flash Player Mozilla Firefox'a Geri Döndü
Tamindir
Geçtiğimiz hafta Flash Player eklentisini tamamen bloke eden Mozilla Firefox, bu haftadan itibaren uygulamaya tekrar izin veriyor. Geçen hafta Mozilla, Firefox sürümlerinde Flash Player eklentisini tamamen engellediğini açıklamıştı. Mozilla bu önlemi ...
Firefox tehlikeli buldu Flash'ı kapattı!Arca Haber Ajansı

alle 2 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Emily Dunham: Printing

Mozilla planet - mo, 20/07/2015 - 09:00
Printing

The office printers have instructions for setting them up under Windows, Mac, and Ubuntu. I had forgotten how to wrangle printers, since the last time I had to set up new ones was half a decade ago when I first joined the OSL.

Setting up printers on Arch is easy once you know the right incantations, but can waste some time if you try to do it by skimming the huge wiki page rather than either reading it thoroughly or just following these steps:

Install the CUPS client:

$ yaourt -S libcups

Add a magic line to /etc/cups/cups-files.conf:

SystemGroup username

With your username on the system, assuming you have root and will log in as yourself in the dialog it prompts for. That line can go anywhere in the file.

Make the daemon go:

$ sudo systemctl enable org.cups.cupsd.service $ sudo systemctl start org.cups.cupsd.service

Visit the web interface at http://localhost:631.

Then you have a GUI sufficiently similar to the one in the instructions for Ubuntu!

There is no GUI client for CUPS to install. If you find yourself mucking about with gpr, xpp, kdeprint, or /etc/cups/client.conf, you have gone way too far down the wrong rabbit hole.

Categorieën: Mozilla-nl planet

This Week In Rust: This Week in Rust 88

Mozilla planet - mo, 20/07/2015 - 06:00

Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust or send us an email! Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.

This week's edition was edited by: Brian Anderson, Vikrant Chaudhary

From the Blogosphere New Releases & Project Updates
  • chan. Multi-producer, multi-consumer concurrent channel for Rust.
  • cargo-check. Wrapper around cargo rustc -- -Zno-trans.
  • Raft: New Crates!. Two new crates wrapped_enum (use multiple try!() with different errors) and scoped_log (log log context to logs) from Raft developers.
  • rust-memalloc. Raw allocation APIs in stable rust.
  • newtype_macros. Tuple structs with a single member, intended to be used for wrapping types to create new semantics for an underlying type.
  • capnp-ffi. Use Cap'n Proto as a better method of FFI communication.
  • rust-farmhash. Port of Google's Farmhash version 1.1 to pure Rust.
What's cooking on nightly?

bors underwent a sudden unscheduled uprade this week, incurring unusual ammounts of downtime. Thankfully, Manish crafted an epic rollup to make up some of the slack.

98 pull requests were merged in the last week.

New Contributors
  • arthurprs
  • Frank McSherry
  • Jose Narvaez
  • Kristof Söderström
  • Ryan Pendleton
  • Vincent Bernat
  • Vladimir Rutsky
Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

Final Comment Period

Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now. This week's FCPs are:

New RFCs Internals discussions Upcoming Events

If you are running a Rust event please add it to the calendar to get it mentioned here. Email Erick Tryzelaar or Brian Anderson for access.

Quote of the Week

Rust is very much about only paying for what you need, and often you don't need much, but when you do need something, Rust is more than ready to rummage in your wallet for loose change.Manish Goregaokar

Thanks to llogiq for the tip. Submit your quotes for next week!.

Categorieën: Mozilla-nl planet

Bump and grind is Mozilla's plan for future Firefox OS releases • The Register - The Register

Nieuws verzameld via Google - mo, 20/07/2015 - 02:01

IBNLive

Bump and grind is Mozilla's plan for future Firefox OS releases • The Register
The Register
The Mozilla Foundation has formalised Firefox OS development, pledging that henceforth new versions will emerge every six months. “To deliver upon this vision we are immediately moving to a development model where we will drive a single open source ...
H5OS is a Firefox OS-spinoff for smartphones, tablets, and more - LiliputingLiliputing
Firefox OS fork "H5OS" gets a $100 million boost · LinuxGizmos.comLinuxGizmos
This new mobile operating system aims to take on Android; to be released in ...IBNLive
IT Business Net
alle 8 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Air Mozilla: Gestión ágil de proyectos comunitarios

Mozilla planet - snein, 19/07/2015 - 22:00

Gestión ágil de proyectos comunitarios En esta formación explicaremos cómo gestionar proyectos de la comunidad utilizando metodologías ágiles y cómo utilizar waffle como herramienta.

Categorieën: Mozilla-nl planet

Air Mozilla: Gestión ágil de proyectos comunitarios

Mozilla planet - snein, 19/07/2015 - 22:00

Gestión ágil de proyectos comunitarios En esta formación explicaremos cómo gestionar proyectos de la comunidad utilizando metodologías ágiles y cómo utilizar waffle como herramienta.

Categorieën: Mozilla-nl planet

Michael Kohler: Mozilla Weekend Berlin – Day 2 / Feedback

Mozilla planet - snein, 19/07/2015 - 20:38

At the Community Meetup of the German-speaking community back in February we decided to organize a Mozilla Day or Mozilla Weekend in 2015 to get more visible in Berlin, tell people about Mozilla’s mission and projects, and recruit new Mozillians. We did this on July 11th and 12th. This is the post about Day 2. You can read about Day 1 in a previous blog post.

Introducing participants to Bugzilla, quick session by @axelhecht #mozweekend pic.twitter.com/KeZyZgLnbz

— Michael Kohler (@KohlerSolutions) July 12, 2015

Day 2 On Sunday we had several workshops going on in parallel in the Mozilla Office in Berlin. Around 30 attendees joined us and hacked on Firefox, Firefox OS and brainstormed about involved in the Community Creative Team. Since we had coders and designers there, we had a good balance of workshops to participate in.

Heads down hacking at #mozweekend Berlin day 2 pic.twitter.com/tYJw7io7mQ

— Brian King (@brianking) July 12, 2015

Work done (or started) in the workshops:

  • Bug 547401 – worked on by Stefania and David Bryant
  • Bug 1180314 – fixed by David Bryant, his first patch on Mozilla code (as it is for all other volunteers)
  • Bug 1170460 – worked on by Nils, but was blocked due to unclear specifications
  • Bug 965211 – fixed by Nils, I love this, already tested that one on my Flame with Nightly
  • Bug 796319 – Asma has started to do this after our introduction into Gaia
  • Bug 1055357 – worked on by Oleksandr who had great ideas on how to improve code not in the scope of this bug
  • Bug 1044275 – worked on by Claas who is an experienced Android developer

Florian will send out an invitation for a follow up in Berlin later this week. See below for more information.

Further Elio started the Community Design Creative in Germany. They will have their first meetup (physically with Vidyo participation) at the end of the month. This was a group of about 7 persons interested in design. Since we currently only have 2 designers in our German-speaking community I think this is a great addition and has great potential. Let’s keep focus on this and keep them engaged!

Deep thinking with @axelhecht and @david_bryant, thanks! :) #mozweekend #Berlin #gratitude pic.twitter.com/5GvMfVxPRb

— Stefania Delprete (@physte3) July 12, 2015

Followup with potential new contributors

Florian, Markus and Mario will follow up with the code contributors in Berlin and organize regular meetups. We still have to figure out a few location questions, but we’re on the right track. We had 14 people from the workshops interesting in meeting up again and talk about Mozilla and writing some code. Like that we could also have a group that meets regularly to help out with contribution problems and talk about new things they’ve been working on. I think that at least 6 people will stick around long-term. This would basically be a 300% increase of volunteers in Berlin!

As already written, Elio will follow up with the designers to create amazing creative assets and improve UX.

Further I think it might be beneficial to organize another Mozilla Weekend style event next year. Let’s see how that turns out.

Feedback from participants

At the end of Day 1 we asked people to give feedback. Here’s the result (out of 14 responses):

What people liked:

  • “Ask us anything” session (mentioned as best session by more than 50% of feedback givers)
  • Speech Recognition talk by Kelly
  • Firefox OS talk by André

What people would improve:

  • More technical talks (for example Servo)
  • Introduction session to get to know all the participants
  • Have a session on Webmaker
  • Reach more people (Michael: not sure what exactly is meant by that, maybe attendence?)
  • More live demos

How the understanding of Mozilla and its mission changed:

  • A lot: 7
  • Somewhat: 6
  • Barely: 1
  • Not at all: 0

Other input:

  • “Please less audience involvent next time :-)”
  • “Much more interactive. Much much more interactive.” (mentioned by 2), also less slides
  • “Don’t let speakers use the hand microphone”
  • “Don’t give the mic to audience to avoid them giving monologues.”
  • “Does any meetup really need a talk about women in X? Really? Please give us more *tech*, less replacement topics.”
  • “i expected a more technical insight into mozilla projects. i am just a web developer / mozilla user”

For day 2 I think that all participants were involved enough and could do whatever they wanted to contribute to. We did not do a specific survey for the workshops though. Judged from the interest to follow up I think this was amazing!

Lessions learned

  • Organizing a 2-day event takes quite a lot of time
  • Finding a free venue for talks for a whole day in Berlin, contrary to our initial believes, seems impossible
  • People are interested and we need to keep doing follow up and do more local events in Berlin. Berlin is a big city with a lot of IT people who are interested in learning about Mozilla and contributing. Until now we haven’t done enough there.
  • For the next event we should have a budget which is laid out for a 50% no-show rate.
  • It is easy to get people starting on contributing, but we need to do good follow ups to keep them.
  • We can achieve our goal to have more women in our community when we continue like that. But we need to make sure that we stay inclusive.
  • There is a demand for recordings for these kind of talks, fortunately we have air.mozilla.org :)
  • People want to know information directly from the leadership team, since not many know what’s going on behind the curtains.
  • Have more demos for topics we talk about
  • We should keep going and have fun with it!

Thanks again for everyone who made this possible! We achieved a lot, let’s keep the momentum going!

Categorieën: Mozilla-nl planet

Michael Kohler: Mozilla Weekend Berlin 2015 – Preparation & Day 1

Mozilla planet - snein, 19/07/2015 - 19:24

At the Community Meetup of the German-speaking community back in February we decided to organize a Mozilla Day or Mozilla Weekend in 2015 to get more visible in Berlin, tell people about Mozilla’s mission and projects, and recruit new Mozillians.

Preparation

First we had a “Call for Speakers” which did not turn out as hoped, since we didn’t have a lot of proposal for talks. Further we were missing quite a few people to facilitate the workshops. Fortunately there was a Mozilla Leadership Meetup on July 10 in Berlin, so we contacted the Leadership team and asked, if they wanted to participate and have a few talks about Mozilla and its projects. This worked out really well and it was great to have part of the Leadership Team at the event as well. I think this helped to get contributors as well.

It was the first time we created a website for an event in the German-speaking community. We decided on mozweekend.de which we will be able to use also for future Mozilla Weekends in Germany. I think we need to do that as well for future, big events since we had quite a lot of visitors and registrations. Until one day before the event we had about 120 registrations.

CI6ryViWcAALYGP.png_large

Day 1 – July 11

For the first day, we had planned talks to introduce Mozilla, and dive deeper into the different projects. Since we had about 120 registrations we applied our standard 33% no-show rate and expected about 80 participants. In the end, we had around 55 participants, but nevertheless the attendees were very interested. This is a sign that quantity is not always the goal, quality is way more important.

Begin Topic Presenter 10:00 Welcome & Introduction to Mozilla Elio Qoshi & Michael Kohler 10:15 What’s new in Firefox? Michael Kohler 10:30 Speech Recognition at Mozilla Kelly Davis 11:15 Ask us anything Mitchell Baker, David Bryant, Axel Hecht 12:00 Lightning Talks Elio Qoshi & André Fiedler & Axel Hecht & Mario Behling & Per Guth/td> 13:30 Firefox OS – Current status and the future André Fiedler 14:00 Why I am at Mozilla David Bryant 14:30 Shape of the Web Mary Ellen Muckerman 15:00 WoMoz – Women at Mozilla Kristi Progri 15:45 Leaving behind the designer ego in open source communities Elio Qoshi 16:00 Opportunities to Contribute at Mozilla George Roter & Michael Kohler/td> 16:45 Closing Session Michael Kohler

 

All these talks will be available on air.mozilla.org once their uploaded as well! I think we had quite a good mix of projects, even though Firefox was not represented as good as it could have been.

Awesome talk about @firefox OS by @sonnenkiste at #mozweekend @mozilla pic.twitter.com/fcd39pdK6R

— Mario Behling (@mariobehling) July 11, 2015

What an eye-opening talk about Women in the Tech industry by @KristiProgri #mozweekend pic.twitter.com/LaCGMJ2dIY

— TheOne (@wagnerand) July 11, 2015

The “Ask us Anything” session was very important and it was great to have Mitchell Baker, Chairwomen of the Mozilla Foundation, and David Bryant (VP of Platform Engineering), and Axel Hecht (contributed since the beginning of Mozilla). We had a lot of interesting questions from the audience.

QA with @MitchellBaker @david_bryant and @axelhecht at #mozweekend pic.twitter.com/uzLgfNKUd8

— Brian King (@brianking) July 11, 2015

You can find all the pictures and tweets with the hashtag #mozweekend.

Excited to see @geroter and @KohlerSolutions talking about Contributing at Mozilla, incl. fun exercises! #mozweekend pic.twitter.com/dicfLSJGhE

— TheOne (@wagnerand) July 11, 2015

#mozweekend #berlin 2015 pic.twitter.com/laK02rAP6Q

— ANIL KUMAR (@anilbms75) July 16, 2015

Go ahead and read about Day 2 as well!

A big thanks goes out to the organization team and the 10 speakers, you all did great work! And thanks to everyone who showed up even though it didn’t rain!

Categorieën: Mozilla-nl planet

Michael Kohler: #FoxYeah in the German-speaking community

Mozilla planet - snein, 19/07/2015 - 18:19

Back in the beginning of June Mozilla has released Firefox 38.0.5, together with a campaign to promote Firefox all over the world. This also included offline events, which we did in Zurich, Bern and Berlin.

Zurich

On June 3rd we met in Zurich to talk about new Firefox features and why you should use Firefox. Unfortunately my planning wasn’t that good and we picked a date where there were 4 other meetups going on in Zurich. This is one thing we definitely need to keep an eye on for the next events. Nevertheless we could talk to a few people and have great discussions about Firefox and the Open Web. We basically hijacked a work session at liip.ch (amazing company which hosts us for our Zurich based meetups) and involved them in the discussion.

CGl8b8cXIAA6ilS.jpg_large

For this meetup I baked some cupcakes and tried to decorate them with a Firefox logo. I won’t share any pictures of this, since it was not really that good. Nevertheless the attendees liked them. But hey, I knew I had a second chance for the Bern meetup!

Bern

5 days later I organized the next event in Bern, my hometown, to talk about how Firefox and Mozilla impacts the Open Web. You can find the slides on my other website. We had about 10 attendees, most of them not familiar with Mozilla and Firefox. I thought that I can take this chance to begin an “Open Web Meetup” group in Bern. This is also how the event was promoted.

There were a lot of interesting questions, which I tried to answer to my knowledge. I’m sure we can have another Open Web Meetup after the summer break to discuss more on Open Web technologies and Mozilla.

For this event I had my second chance to bake cupcakes, this time I had some advice on how to improve from a professional. I took Marzipan, colored it and cut out the Firefox logo out of it. Since it was quite hot, the Marzipan was not easily cutable without breaking, so not all of the logos looked like a fox. Nevertheless it was still recognizable. This took about 4 hours in total, but it was totally worth the effort! But psst, let’s not show that to the Brand Engagement team ;)

CHDl2EWUQAAa-Qv

Also many thanks to netcase.ch (my employer) for hosting us there!

Berlin

Since I’m not based in Berlin, I delegated this event to Florian Merz, who did a great job on June . Here’s his recap:

We held a nice meetup with a talk about “What’s new in Firefox” . Located in the Berlin Mozilla office we gathered a round of diverse people, regarding both background and motivation to attend this meetup. From addon developer, contributor, to “I just wanted to see what’s going on with Firefox, since I switched to another browser a couple of years ago”. During the talk we saw some of the newer features of Firefox like “Firefox Hello” or the Pocket integration. Furthermore, we discussed the privacy implications of such features and Mozilla’s contribution to the users ability to maintain its privacy in general.  talk Florian also baked amazing Firefox cupcakes, which I’m sure they tasted fantastic! cupcake

 

After the talk we had some time left for discussion and some cold beer along with home made firefox cupcakes. Thanks for a great evening to all attendees. And also a great “Thanks” to Florian for pulling this off all by himself, great job!

Even though there are reports for #FoxYeah from other countries which were a lot more focused on #FoxYeah graphics, I still think that we had quite some impact in Switzerland and Berlin. If you would like to spread the world even though the #FoxYeah campaign is over, you can do this on friends.mozilla.org! Let’s keep rocking the free Web together!

Categorieën: Mozilla-nl planet

Mozilla: Firefox OS 2.5 kommt im November heraus - AreaMobile

Nieuws verzameld via Google - snein, 19/07/2015 - 18:06

Mozilla: Firefox OS 2.5 kommt im November heraus
AreaMobile
Mozilla wird die nächste Version seines mobilen Betriebssystems im November veröffentlichen. Firefox OS 2.5 soll den Anwendern mehr Personalisierungsmöglichkeiten als die Vorgängervarianten und verbesserte Sicherheits-Funktionen bieten.
Mozilla: Firefox OS für alle entsperrten Android-SmartphonesComputerBase
Zukünftige Firefox OS-Versionen für alle Android-Smartphonessoeren-hentzschel.at

alle 3 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Jared Wein: Default Browsers and Windows 10

Mozilla planet - snein, 19/07/2015 - 00:31

Microsoft is set to release Windows 10 pretty soon and with it comes a new way to set the default browser for your system.

Previous versions of Windows had an API that allowed applications to set themselves as the default application. This worked well and allowed web browsers like Firefox and Chrome to have a single click within their interface to set themselves as the default browser. No extra work was needed by the user after clicking the button within the respective app.

Starting in Windows 10, references to this API now generate the following error dialog on the machine:

gotosettings

Obviously, this message isn’t that helpful. First, users who click on a button to “Make Firefox my Default Browser” now get a dialog telling them what to do instead of doing it for them. Secondly, the message is given in a prompt that blocks interaction with the rest of the computer until the OK button is clicked. Combining this second issue with the lengthy list of steps that the dialog provides makes the situation even worse, as the user will have to memorize this 3-step process before clicking OK.

This experience isn’t something that we want to ship to Firefox users. When I first saw this experience, I sent an email to some people working on Chrome to ask them what their plans were to solve this. They said that they had looked in to this and decided they would instead just open the Settings app to the Default Applications view.

Settings app

I brought this approach back to some of my coworkers and we decided we would match the behavior that Chrome was using. After all, it didn’t seem like a better solution existed and we certainly didn’t want our users to be seeing the ugly dialog described above.

After I landed the changes in Firefox to open the Settings app, Masayuki Nakano provided an alternative implementation that would open a friendlier looking dialog to set the default application.

Alternative approach

This dialog looks a lot better, but it only sets the choice as the default browser if the small “Always use this app” checkbox at the bottom is checked before the OK button is clicked.

Once we had two implementations, we ran an A/B test of them for a week with our Nightly audience.

Key Count Percentage set as Default Alternative Approach/OpenAs (users who did not set the browser as default) 2.35k 53% Alternative Approach/OpenAs (users who did set the browser as default) 2.65k Settings (users who did not set the browser as default) 2.76k 50% Settings (users who did set the browser as default) 2.86k

The table above shows the data that was collected through the A/B test from June 22 to June 29 with Firefox Nightly 41. This data showed that 53% of alternative-approach users set Firefox as default, whereas 50% of the Settings-app users set Firefox as default.

With only a week of data, we didn’t see a statistical difference between the two approaches and decided we would stick with the Settings app due to it’s wider adoption. We also had issues with the OpenAs approach where we weren’t able to register all protocols and file extensions.

Next Steps

The default browser situation on Windows 10 is pretty bad. There is more work that we can and should do in the Windows 10 upgrade experience to retain users (the default upgrade changes the default browser to Edge).

We also would like to improve our telemetry tracking of the default browser dialog. Ideally we could use some accessibility or automation APIs to scroll into view the Default Browser option within the settings app (it’s scrolled out of view when it is first opened).


Tagged: chrome, firefox, planet-mozilla, usability, windows
Categorieën: Mozilla-nl planet

Mozilla: Firefox OS für alle entsperrten Android-Smartphones - ComputerBase - ComputerBase

Nieuws verzameld via Google - sn, 18/07/2015 - 22:27

Mozilla: Firefox OS für alle entsperrten Android-Smartphones - ComputerBase
ComputerBase
Bei Mozilla stehen derzeit Strategieanpassungen auf der Tagesordnung. Nachdem vor wenigen Wochen eine neue Strategie für den Browser Firefox bekanntgegeben wurde, steht nun Firefox OS im Fokus. Künftig soll Firefox OS der neuen Strategie zufolge ...
Zukünftige Firefox OS-Versionen für alle Android-Smartphones - soeren ...soeren-hentzschel.at

alle 2 nieuwsartikelen »Google Nieuws
Categorieën: Mozilla-nl planet

Mozilla's Firefox OS 2.5 is coming in November | VentureBeat | Business | by ... - VentureBeat

Nieuws verzameld via Google - sn, 18/07/2015 - 18:54

VentureBeat

Mozilla's Firefox OS 2.5 is coming in November | VentureBeat | Business | by ...
VentureBeat
Are you a growth marketer? Do you want to know what it takes to be one? Join us at GrowthBeat, on August 17-18 in San Francisco. Thought-leaders from the biggest brands and most disruptive companies will share winning growth strategies on the most ...

Categorieën: Mozilla-nl planet

Arky: Webmaker tools on Raspberry Pi

Mozilla planet - sn, 18/07/2015 - 11:18

Last year in Bamako, Mali I watched the participants struggle with slow Internet connectivity during a web literacy WebMaker event. I thought it is very important to make Webmaker tools available offline on a local server. I started working on a custom Rasbian based SD-card image with Mozilla Webmaker tools on Raspberry Pi. The setup uses the most minimal setup without any connectivity to Internet. The Raspberry Pi Server will host Web maker tools like Thimble with some learning templates. The users could connect to the server with WiFi from their laptops or using school computers using local Ethernet connection.

The goal was to finish the project by MozFest East Africa in July, 2015 and release it for testing.

How to use Webmaker tools on Raspberry Pi?

Download the testing version of the image here. It is large 2.8GB file, it will take some time to download. In this setup I am using an older Raspberry Pi B model with 8GB SDCard with a TP-Link TL-WN322G+ USB WiFi dongle. The WiFi dongle is optional, you can connect the Raspberry Pi to your router or networking hub with an Ethernet patch cable.

  1. Download and write the image to the SD-card (Tutorial)
  2. Boot the raspberry Pi with the SD-card
  3. Connect the Raspberry Pi to your local Ethernet network. (If you have USB Wifi dongle then you can connect to 'Webmaker' WiFi network with 'raspberry' password.)
  4. On your computer, Open browser and type 'http://webmaker.local' You should see the Thimble App UI.
Webmaker Thimble running on Raspberry Pi server

Please do report any problems and bug reports!


Categorieën: Mozilla-nl planet

Sicherheitslecks: Mozilla sperrt Flash Player aus - Wochenblatt.de

Nieuws verzameld via Google - sn, 18/07/2015 - 10:15

Wochenblatt.de

Sicherheitslecks: Mozilla sperrt Flash Player aus
Wochenblatt.de
Mit der aktuellen Blockade setzt Mozilla ein deutliches Zeichen. Für Nutzer des Firefox-Browsers wird Flash nun entweder automatisch gesperrt oder der User erhält vor der Verwendung eine Nachricht, in der er ausdrücklich gefragt wird, ob er die als ...
Mozilla und Apple blockieren zeitweise Flash Player von AdobeIngenieur.de - Das Nachrichtenportal für Ingenieure
Adobe Flash Player: "Installieren Sie immer alle Updates"WirtschaftsWoche
Apple blockiert ältere Flash- und Java-Versionen in OS XElektronikpraxis

alle 24 nieuwsartikelen »Google Nieuws
Categorieën: Mozilla-nl planet

What to Look Forward to from Firefox OS

Mozilla Futurereleases - sn, 18/07/2015 - 01:30

Firefox OS is an important part of our mobile strategy, in addition to Firefox for Android and other initiatives. We believe that building an open, independent alternative to proprietary, single-vendor platforms is critical to the future of a healthy mobile ecosystem. And it is core to our mission to promote openness, innovation and opportunity in online life.

As an open source project, we are different from other tech companies and do most of our work and planning in the open, so we want to share a brief update of what we’re planning and what we’ll be experimenting with for the next phase of Firefox OS.

Ignite Initiative

Earlier this year, we shared that we were moving to the next phase of Firefox OS, where we would focus on the core product experience to ensure that it is clean, modern and easy-to-use, and yet powerful through its extensibility, clever design and features that put users in control of their experience.

Our aim is to build the next generation of Firefox OS with a stronger, more unified product experience and developer platform that exemplifies our values by showcasing the best of the Web.

To accomplish this, we are bringing threeignite image key ideas together:

  1. User focus: Ensuring that we’re delivering an experience that people love through user-centered design, research and product iteration
  2. Web platform: Bringing more of Mozilla and the Open Web to people than just the Web technologies upon which our products are built
  3. Community: Rallying and fully empowering our global community of developers, designers, and more to help build the future together

To deliver upon this vision we are immediately moving to a development model where we will drive a single open source core of Firefox OS, with major releases every six months, based upon weekly sprints.

Each major release will strive to deliver significant user and platform value, and will be available directly to anyone who wants to flash an unlocked Android phone or run through B2GDroid (an app that allows you to experience Firefox OS on Android) to get the latest experience, help test new features and to contribute back to the overall project. We will also support our partners (i.e. OEMs and operators) who will build and ship Firefox OS-powered devices based upon these major releases.

Firefox OS 2.5

The next major version of Firefox OS is now scheduled for this November.  You can view the draft roadmap and plan here.

Firefox OS 2.5 will be the most customizable, secure, locally relevant and empowering Firefox OS experience yet. In addition to local content, personalization and privacy features, we plan to enable the mobile equivalent of “View Source” (note: we’re still evaluating and designing the final feature set), revamp our security model to expose more of the new mobile Web APIs to developers and enable a Firefox-like extension mechanism to add to the user interface and phone capabilities.

New Product Development

We are also ramping up focused new product development efforts with key partners, building on recent announcements about Firefox OS Smart TVs and Smart Feature Phones, and active explorations into the Internet of Things and other connected device opportunities.

Stay tuned for more.

Categorieën: Mozilla-nl planet

Wladimir Palant: JavaScript Deobfuscator reloaded

Mozilla planet - sn, 18/07/2015 - 01:00

A few weeks ago I released JavaScript Deobfuscator 2.0 — finally something that works with current Firefox versions again. Why did it take me a year to fix this compatibility issue? Well, it really wasn’t that simple. After considering all the possibilities I decided that rewriting it from scratch was the only possibility, and that was hard to accomplish in my spare time.

Before I continue with the technical details, allow me to introduce JavaScript Deobfuscator in its new reincarnation: it now adds a panel to Firefox Developer Tools. Instead of messing with filters your view is limited to the current tab automatically. Both compiled and executed scripts go into the same list, with some text indicating whether we’ve seen the script being compiled or executed or both. Starting with Firefox 39 even code running in Web Workers will be displayed. And JavaScript Deobfuscator will beautify the code instead of relying on the JavaScript engine to do so.

JavaScript Deobfuscator screenshot

The downside is that only Firefox is supported now — other applications simply don’t have Developer Tools to integrate with. Also, debugging add-ons or the browser itself isn’t possible—— Developer Tools run in a separate process for that, no add-ons installed there. Finally, the search functionality is absolutely rudimentary right now, that’s something I hope to improve eventually.

Now to the technical details. The reason for this overhaul is the new debugging interface which replaced the one JavaScript Deobfuscator was using. The old debugging interface was conceptually different, it was designed as a single hook to collect all data. The new one on the other hand collects data about individual compartments and it’s up to you to figure out which ones you need. After a few unsuccessful attempts to continue collecting all data in JavaScript Deobfuscator I realized that it made a lot more sense to look at individual tabs.

Using the new debugging API turned out to be tricky to say the least. Did I link to MDN above? Sorry about that, I should have linked to the SpiderMonkey source code. It’s very similar to the MDN documentation but the later is outdated. And even if you look at the SpiderMonkey source, much of the documentation is merely wishful thinking, listing features that were never implemented.

A new UI concept had to be developed as well, and the only good option for per-tab debugging would be integrating into the Firefox Developer Tools. That’s where the fun really started. I tried to make sense of the documentation, studied the source code, figured out that ToolDefinition.build() is supposed to return a promise. Then I looked at what TargetType is and how existing tools work with it — this was the point where I realized that there are so many implementation details involved that an extension cannot possibly do it. So I gave up.

When I came back a few months later things improved, slightly. Somebody wrote an Add-on SDK module to create new Developer Tools panels. While I didn’t use that module directly, it showed nicely which parts of the API are contractual and which ones are merely implementation details. It also showed that things aren’t too bad if you limit yourself to a single target type — a local tab. Handling remote connections to browser and add-ons is more complicated, but as I mentioned above extensions cannot do that anyway.

Now that article stops at the point where you “merely” need to use the remote debugging protocol to communicate with the built-in debugging actor. Well, maybe it is really simple but I couldn’t figure out how to do this — and whether that protocol is something I can rely on. See, the built-in tools will certainly be adjusted when the debugging actor or/and the protocol change. My extension on the other hand will be broken, and I’ll need to invest time into figuring out what changed and how my code needs to be adjusted while staying compatible with older Firefox versions.

So JavaScript Deobfuscator uses the debugging interface directly, without relying on the debugging actor of the Developer Tools. And it beautifies JavaScript code using its own copy of a library rather than relying on code used by Developer Tools — JavaScript beautification in Developer Tools is currently an implementation detail that extensions cannot rely on. JavaScript Deobfuscator also duplicates the styles of the two Developer Tools themes to make sure it looks similar to the existing panels — just using the styles from Developer Tools would have likely caused a disaster after only a few Firefox releases. Not that the built-in styles are really defined in a generic way, there is really lots of inconsistencies there and each panel is styled somewhat differently.

These are only some examples, there is more code duplication. Developer Tools aren’t currently built to allow extensions to reuse their code. Still, I’m fairly happy with the result, and I hope that the largest chunk (JavaScript beautification) will go away eventually. From the usability point of view the new version is a huge leap forward, getting there could have been easier however.

Categorieën: Mozilla-nl planet

Air Mozilla: Webdev Beer and Tell: July 2015

Mozilla planet - fr, 17/07/2015 - 23:00

 July 2015 Once a month web developers across the Mozilla community get together (in person and virtually) to share what cool stuff we've been working on in...

Categorieën: Mozilla-nl planet

Air Mozilla: Webdev Beer and Tell: July 2015

Mozilla planet - fr, 17/07/2015 - 23:00

 July 2015 Once a month web developers across the Mozilla community get together (in person and virtually) to share what cool stuff we've been working on in...

Categorieën: Mozilla-nl planet

Matt Thompson: What we learned. What’s next.

Mozilla planet - fr, 17/07/2015 - 20:01
What we learned

“Spending time right after workweeks to knock out documentation, to-dos, and reflection puts wind in our sails.” –Michelle

Allocate time for documentation and follow-up after work weeks. Be intentional about spending time to write up documentation / key decisions made. At the MozFest prep in Scotland, for example, we had a whole day to wrap, document, prep blogs and wikis, etc. — it really helped.

“PTO requires more prep to keep everyone in sync and unblocked … and keep PTO enjoyable.” — Matthew

  • Be more intentional about vacation hand-off and planning. PTO and calendar confusion slowed us down last Heartbeat. Be more intentional about planning and hand-off. In heavy PTO season, we may need to adjust our roadmap / expectations.
  • The “Pledge to Teach” we shipped on teach.mozilla.org doesn’t have a strong conversion rate yet. (Though the pledge -> next step conversion rate is really good.) Need to iterate. (Blog post on this coming soon.)
  • The CRM project is big and hard to keep a track of. So we spent time making the ‘Plan of Record’ a more useful view: http://mzl.la/CRM
  • Working with communities may be easier and more effective (and appreciative) with a dedicated community manager. We’re collaborating with Participation Team, but have more work to do to on-board community.
  • It’s hard to have engineers jump onto tasks with same results as regular team. Continuity helps. Discontinuity slows us. (See: PTO.)
  • Read this: Mozilla Clubs: 2015 Half-Time Report

What we’re doing next

This Heartbeat (July 31):

Highlights:

Learning Products:

Fundraising and Metrics:

Learning Networks:

Vacation time to be aware of this Heartbeat:

  • Matthew: off July 27-31
  • David Ascher: Jul 20-24
  • Claw: July 22- 27
  • Mark: July 24 — Aug 10
  • Cassie: July 20-24
  • Bobby: August 1-14
  • Laura D: July 24
  • Michelle: July 20, 21
Categorieën: Mozilla-nl planet

Pages