openSUSE packages of the latest freetype2 (2.3.7) are available on opensuse-community.org, with subpixel hinting enabled. See SubpixelHinting for further details.
Posts and information from the SUSE world.
openSUSE packages of the latest freetype2 (2.3.7) are available on opensuse-community.org, with subpixel hinting enabled. See SubpixelHinting for further details.
A new release of Moonlight is now available. The team
has been working very hard on improving the performance of
Moonlight as well as improving our compatibility with
Microsoft’s Silverlight.
This release will also work with both Firefox 2.0 and
Firefox 3.0. We have also switched our installation system
to use signed XPIs, but we will also require a browser restart
(we could not figure out a way of avoiding this).
Some of my favorite work that happened on this cycle is the
effort to improve our multi-browser support, work
towards supporting WebKit and Opera is underway and will
improve over time. This work benefitted from our own work to
support both Firefox 2.0 and 3.0 in the plugin.
Windowless mode (the mode that allows blending of HTML
content and Silverlight content) is vastly improved but is
only available on Firefox 3.0. This is a feature that is
used extensively by Silverlight designers.
More details from the release:
It’s been roughly two weeks since my last post and I’ve been incredibly busy with work the past few days, so I thought I’d pause to post a quick update.
In Firefox 3, SSL certificate errors are displayed in the browser as error pages.
I really like this improved new error page, because the click path you have to follow requires that you read through all information once and hopefully remember the correct click path next time you encounter a SSL certificate with an unknown signature.
Unfortunately this new feature gets after a while really annoying. Luckily users may configure this feature using about:config. I suggest you change browser.ssl_override_behaviour to 2.
The latest Miro (1.2.4) is now available for openSUSE 11.0, 10.3 and 10.2 in the Packman repository.
This is from Andreas. THANKS!!!
Last weekend I finally found some time to upload pictures that I had taken during various events that I attended in the past few months. So here are my impressions from the following events:
These are probably the last pictures that I have taken with my trusty old Pentax Optio S4 - I just received my new camera, a Canon PowerShot A720 IS. I have just started to toy around with it, but the first results look promising! The Pentax served me well for several years - I’ve taken 9745 pictures with it. But it had a few deficiencies, particularly the slow startup and flash recharge time and the bad quality of pictures indoors bothered me for quite a while. But it is very small and handy and the metal housing makes it quite sturdy.

The first picture taken with my new camera: a picture of the old one.

And probably the last picture taken using the old camera: my new Canon.
There happens to be something called DVCS. People said its gonna solve all our problems. But then, different people had different view on our problems, and they had different ideas how to solve them. Out of the flux came to life generation one, followed by generation two and finally generation three. Evolution, they say. So we have Mercurial, Bazaar, Git as representatives from the latest DVCS evolutionary branch.
Now, there is this project that we’ll call GNOME for needs of this little essay. There are a lot of smart folks there doing some amazing work, pushing boundaries of what can be done with every release at least a little bit further. They’ve been using CVS for quite some time, and altough they didn’t really like its deficiencies, they always somehow managed to chum along with it. The “In good and evil” kind of relationship, you know. And then one day, enough! Decision was made to make a migration to Subversion, since it was supposed to make things better. As it happens to be, like with everything else, it brought good and bad things on the table. But eventually most of the things were polished by the rocking GNOME sysadmins, even if there is only a few of them.
Today, we’ve got some other winds blowing. There is an ongoing campaign to make a switch to a DVCS. Here is where things become a little more trickier. People usually discuss things before doing them, and that is actually good! But it becomes quite useless when all you’re doing is throwing balls at each other, and not actually listening to what others have to say. Personally, I am not a fanboy of any DVCS, am quite involved with both bzr and git communities, and have at least tried other DVCSs like Mercurial and Darcs. So before you even mention it, I’m not promoting any of those. What would *really* rock, and I know that upstream developers would appreciate it, is pointing out all those use-cases where you’ve experienced problems with a certain DVCS. If we can do that, upstream developers could work on improving their tools where needed. Perhaps, just perhaps, we can even give them a hand? At least one developer to the developers pool of some DVCS project would really make a difference, because those projects are quite young and don’t have many hands behind them.
Our administrators are worn out from SVN migration, and they are cautious of yet another migration just for the fun of it. If you really want to migrate to your favorite DVCS, write a plan and develop tools needed for the proper migration, do the required testing, and collaborate with upstream developers to improve their DVCSs in needed areas. Let us talk. For quite some time now I’ve been working with KDE to prepare a GitoriousKDE specification which could be further discussed at Akademy. Basically the specification defines a variation of Gitorious project specifically tailored to the needs of KDE project. Perhaps we can do something similar for the Gnome? Then, a moment before you start thinking about it, forget that it supports only git and let your imagination work. Perhaps we can let the developer of individual module to choose desired VCS from range of {bzr,git,hg} trio? Adding others would be fairly trivial anyway, since VCS stuff would be abstracted through not-yet-existant rvcs.
If you tell me that a common base for one of the key infrastructure pieces for KDE and GNOME is not useful, just stop for a moment, get a glass of water, and read this post again. Lets show FOSS collaboration in all its glory with this effort.
I am far from done with expressing my opinion on this matter, but I challenge you now …
With openSUSE 11.0 out the door, it’s time to start thinking about openSUSE 11.1. The public release of openSUSE 11.1 is scheduled for December 18, 2008, six months after the release of openSUSE 11.0.
The full schedule for the release cycle is as follows:
Thu, Jul 24: openSUSE 11.1 Alpha1
Thu, Aug 21: […]
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jun | Aug » | |||||
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 | |||