Slashdot Mirror

For a full list of sites that pulled April Fools Day Pranks this year check out this list here -

Here is a sampling:

dotget.net - Microsoft to put P2P software .GET into next version of Windows
kylewenda.com - the government records your phone calls... scary
rfc-editor.org - RFC for "Requirements for Morality Sections in Routing Area Drafts"
planet.gentoo.org - Various things, CFLAGS, etc
fark.com - Many Jokes (keep reloading): BOOBIES!, Logged in as admin, North-Central Kentucky Bunghole-Discharge, page from 1999, BEER
2600.com - Formal Attire required for 2600 meetings today
forumsector.com - Changed the name to Nascar Sector
wikipedia.org - Britannica taking over Wikimedia
google.com - Google releases Google Gulp
kellyosbourne.org - Sanctuary records group shut us down
nukefreezone.net - Making fun of atrios.blogspot.com
weebl.jolt.co.uk - Replaced with Cats-By-Mail
wingus.ampedhost.com - Site converted into Mingus' Gently-Used Furniture store. Oh dear. Why won't he be kind?
homestarrunner.com - Now a pay service.
whirlpool.net.au - Australia's biggest Luddite to head Australia's largest telco
theregister.co.uk - Bush twins to join Air Force tech unit in Iraq
creativebits.org - Site purchased by Microsoft
ocremix.org - Now partnered with EA (or something like that). Called EA ReMix.
spacedaily.com - Bush Cancels Space Shuttle Program
planet.gnome.org - Switched sites with planet.kde.org
planet.kde.org - Switched sites with planet.gnome.org
ietf.org - RFC: Efficient Transformation Formats of Unicode
beejaysworld.de - Gentoo dropping livecds for x86
nature.com - Apollo bacteria spur lunar erosion
antwrp.gsfc.nasa.gov - Water On Mars

For a full list of sites that pulled April Fools Day Pranks this year check out this list here Here is a sampling: dotget.net - Microsoft to put P2P software .GET into next version of Windows
kylewenda.com - the government records your phone calls... scary
rfc-editor.org - RFC for "Requirements for Morality Sections in Routing Area Drafts"
waferbaby.com - amusing php error
planet.gentoo.org - Various things, CFLAGS, etc
fark.com - Many Jokes (keep reloading): BOOBIES!, Logged in as admin, North-Central Kentucky Bunghole-Discharge, page from 1999, BEER
2600.com - Formal Attire required for 2600 meetings today
forumsector.com - Changed the name to Nascar Sector
wikipedia.org - Britannica taking over Wikimedia
google.com - Google releases Google Gulp
kellyosbourne.org - Sanctuary records group shut us down
nukefreezone.net - Making fun of atrios.blogspot.com
weebl.jolt.co.uk - Replaced with Cats-By-Mail
telecom.co.nz - Click 2 Brick
ytmnd.com - (NSFW) hacked by teens for christ
wingus.ampedhost.com - Site converted into Mingus' Gently-Used Furniture store. Oh dear. Why won't he be kind?
homestarrunner.com - Now a pay service.
whirlpool.net.au - Australia's biggest Luddite to head Australia's largest telco
thinkgeek.com - Fake product listings.
theregister.co.uk - Bush twins to join Air Force tech unit in Iraq
creativebits.org - Site purchased by Microsoft
ocremix.org - Now partnered with EA (or something like that). Called EA ReMix.
spacedaily.com - Bush Cancels Space Shuttle Program
planet.gnome.org - Switched sites with planet.kde.org
planet.kde.org - Switched sites with planet.gnome.org
ietf.org - RFC: Efficient Transformation Formats of Unicode
beejaysworld.de - Gentoo dropping livecds for x86
nature.com - Apollo bacteria spur lunar erosion
antwrp.gsfc.nasa.gov - Water On Mars

And they made unhappy a lot of old users in the name of new users, and ignored the a11y guys (see #14). This interface hack copies Photoshop and there's a comment in the blog about helping with the GIMP menu reorg. Let's hope this does not become trend: fuck your current users in the name of new users and never innovate, just be clones of something else, nevermind copies tend to be worse than originals.

...coming, and more, but not this month.

Sven Neumann AKA neo is working on real Colour Management as one of the many, many plates he has in the air. Expect to see it surface before GIMP 2.4.

Arbitrary colour channel depths is something of an elephant in the room at the moment. It was supposed to be inherent in a particular supporting library, but development on that library seems ot have petered out.

The people who are actually doing stuff do have this in mind, though, and regularly get asked about it, so it will happen, even if only to stop the whining.

If it (the PS-lookalike code) was contributed back upstream (which it doesn't have to be, but the code itself must still be available to those who download the binary in order to comply with the GPL) I do not think the GIMP developers would accept it since it then would no longer conform as it does to GNOME's Human Interface Guidelines.

Strictly, it's not Mozilla.org alone, and it's not Bugzilla alone either. Out of the box, the Bugzilla system does not block access from Referer: http://slashdot.org/* (for example see GNOME Bugzilla), but the specific instance of Bugzilla on mozilla.org does.

It took me a while, but I managed to find out what EWMH is (the linked page wasn't very helpful, didn't even explain the acronym):

From this page:

The EWMH, or Extended Window Manager Hints is a freedesktop.org- developed standard to support a number of conventions for communication between the window manager and clients. It builds on and extends the ICCCM (See Section 3). A copy of the current EWMH standard is available at http://freedesktop.org/Standards/wm-spec/

The flip side of that one is, anyone who knows how to type in a filename, can handle pressing ctrl-l to do that, or right clicking and selecting "Open Location". Autocomplete works nicely, and you can navigate to a new directory, or select a file or network resource.

There's one obvious problem with this "solution". There's no indication that this functionality exists! (I'll give you 10 to 1 that the way you found out about ctrl-L was via the web search or a mailing list.) Furthermore, this "Go to location" subdialog goes only to the directory, not the actual file indicated. For instance, you want to open "/usr/local/share/doc/foo.html". You bring up the filechooser. You strike the magic keys. You type in "/usr/local/share/doc/foo.html". You click "open". The file isn't opened, but rather the subdialog is closed and the filechooser changes directory to "/usr/local/share/doc". You now have to scroll through the listing and click "foo.html", and then open (again!). That's a problem.

This is simply looking at the filechooser as a usability issue with normal users. The situation gets worse when you consider accessability software like on-screen keyboards and speech-to-text converters. And before you even start calling me some troll, I suggest you read the corresponding bug.

Here's a link. It generates XML files with the UI that can be using by Python via libglade.

Well, if you're asking the question seriously, I think it's important to point out that an installable AbiWord binary is available for Windows; a word processor is, after all, the most important part of an "office suite," for most users. A testing build of Gnumeric is also available. I personally don't give a damn if OO.o relies on Java since most of my writing these days is in TeX, but if it's something that concerns you, there are options.

"progress meters or UI el;ements that look like them do not go back and forwards"

What? The Human Interface Guidelines explictly tells me to use that kind of progress bars for operations with unknown duration. I'm just following the HIG. How's that a usability mistake?

"make your dialogs all the same size/look"

They would look really ugly if they're all the same size.

"no cancel button"

This is a technical limitation and can't be done. The cancel button is removed on purpose.

"dont ask for passwords if they are not needed"

The thing is - they are needed. How else do you want to find out whether the user wants to install as root or not?

"progress meters should accurately reflect the install processes completion, i shouldnt see anything happening to the system beyond 100%
why have a progress meter for extracting files but nothing else ?"

Because it's technically impossible. Again - this has been thought of. It cannot be done.

"the uninstaller said one package needed root access to uninstall yet had no option to enter a root password"

Are you sure? It asks the password for me.

Time to feed the trolls..

• Idiots (as in "...for Dummies") like GNOME because of its consistent UI; because they can work out how to do something without a degree in Nerd Science.
• Idiots (as in Windows "Power User" feature-junkies) like KDE because they can show off the latest whizzy-feature.

OK, so I overstated it somewhat. Both desktops have their pros and cons, both from a user's and a programmer's perspective. Both are memory hogs, especially in EyeCandy(tm) mode, but both are looking forward to machines of tomorrow. You wouldn't want to run Beagle on a machine with 64MB RAM; you might prefer to stick with twm.

RPC is beautiful and very much in the UNIX philosophy of not writing the same program twice. If your distribution still uses sed and awk in its boot process, why shouldn't one bit of a desktop environment borrow another's print preview or file selector?

The only reason I use it over xpdf or gpdf is because Acrobat allows me to print multiple copies of documents, where gpdf/xpdf do not!

In that case, you're in luck. If you're using Gnome 2.10, you can use Evince, which uses the current Gnome printing dialog that allows you to print multiple copies. Sorry to beat a dead horse, but Evince really is a lot better than gpdf. If you're using KDE, I'm sure KPDF does the same thing.

Or you could use a PDF/PS viewer that's nicely integrated with your desktop, and has a sane feature-set and good usability. On GNOME we've got Evince, and on KDE there's KPDF. Evince (and now KPDF, I believe) is backed by the Freedesktop.org Poppler library (which is in turn backed by Cairo which can use hardware acceleration for faster PDF rendering). Kristian (as referenced earlier today on slashdot re: wobbly windows) is hard at work on adding nice features needed for desktop apps. Poppler is a fork from the Xpdf rendering code (with the maintainer's blessing, since he was using his own rendering infrastructure and didn't want to mix two backends into Xpdf).

We've been doing a lot of experimenting with making the "core features" of Evince better for on-screen reading, rather than working on the sort of extra packed in features in Acrobat. For example, when you press page down, evince will slightly darken the area on the screen where your page was as it smooth scrolls. That lets your eye track its position much easier, so once the scroll is over you just keep reading without a visual "seek". KPDF is cool too, so either way you swing you've got a good choice.

Acroread 7.0 is using GTK+ for its widgets, but this hardly makes it have a native "feel". Use it for a minute and its pretty clear its a cross-platform app port.

Actually they are very much seperate right now. See Seth's blog today Which given the /.ing is copied below: Relation to Metacity When it has proved itself, Luminocity's compositing manager will probably be moved into Metacity (along with any effects / extra features we consider good and stable). We originally considered doing the work in Metacity itself, but didn't want to destabilize it until various approaches were tested. Luminocity is, effectively, a testbed for Metacity. It provides a smaller/simpler codebase to test interesting rendering code with, and means we don't have to worry about fucking up Metacity in the process. Soeren's computer is (as of tonight, at least, that's the first I saw of it) running a version of Metacity that's apparently using the compositing manager code from Luminocity to render to a GL context. Relation to xcompmgr Luminocity has an internal compositing manager that performs the same function as xcompmgr. The compositing manager / window manager integration allows Luminocity to do things that an individual compositing manager or window manager couldn't. Of course, Luminocity composites using OpenGL, unlike xcompmgr. This apparently can be an upside and a downside, but I don't know anything about it so I'll shut my trap. Relation to Xgl This is the complicated one :-). I'm loathe to stick my toes in these waters because I'm the wrong person to do it, but I'm also afraid that we're going to end up with two rendering infrastructures down the road and no clarity for application developers as to which (if either) they can use. I don't know if that's where we're headed, I hope not, but I have this vague (probably, hopefully unfounded) fear... The effect will be slow adoption and general suck. I should premise this by saying that I have no direct knowledge of the Xgl codebase. I have knowledgable sources, and I know what Xgl generally is, but I haven't personally used Xgl, let alone looked at its codebase (I've barely looked at the Luminocity codebase either, for that matter). Xgl is an X server implementation that, rather than directly accessing chip specific hardware drivers, does its low-level drawing using OpenGL calls. That means Xgl is functionally equivalent to a traditional X server, it just uses a different rendering path. Put another way, Xgl is to X11 as Glitz is to Cairo: it provides the same APIs rendered in a much smarter way. Luminocity, on the other hand, is a compositing manager / window manager fusion that composites using OpenGL. Compositing and Window managing are all about what you do with client-rendered windows. Luminocity doesn't know what's inside windows, and it doesn't care. Xgl, on the other hand, I would characterize as primarily being about how the contents of windows are drawn (in this case: quickly and with less CPU load, *grin*). Xgl can do some other non-inside-window things like drop shadows, but I'm going to argue later those are mostly expedient demos of cool technology and Xgl is probably not the place we want to be doing those things long term. From the perspective that Luminocity is mostly about rendering windows and Xgl is mostly about rendering window contents, they are theoretically complimentary. At the moment, they can not be used in conjuction with one another (since they both want to directly drive the GL hardware), but they're goals are at least compatible. Neither Xgl nor Luminocity are complete on their own. Xgl provides an X server and requires a window manager (and a compositing manager?) (and an X server for doing GL calls into, but see below, that will hopefully cease to be an issue eventually). Luminocity provides a window manager and a compositing manager but requires an X server (currently using Xfake or Xephyr, though supposedly there's some plan for modifying the core fd.o X server so Luminocity will work using only the host X server?). With some hand waving (in particular there's no way to hand OpenGL textures residing in the video ca

Really they have to do something about those icons - it's obvious they were dreamed up in some manky, voodoo swamp while consulting the Hooch.

The squashy home icon is how many years old? Who lives in that ~/, Yoda? Not to mention those back, fwd arrows - like the kind of thing you'd use to take down a Mammoth.

With all the work gone into Gnome (it's an excellent DE BTW), these icons are a stoney anchor holding it back in the dark ages. They should catch up to KDE and actually choose a superior default Icon set from any one of the other excellent sets made by fans at http://art.gnome.org/. What's wrong with good old Gorilla for instance?

For those who don't know what Beagle is (like me) here is a link and some demos.

Saving a few people a few Google visits:
Beagle

Also interesting:
Beagle CVS repo.

Saving a few people a few Google visits:
Beagle

Also interesting:
Beagle CVS repo.

...the lists are active (and questions actually get answered authoritatively), the IRC channel is lively, and the development is in the open. They've even got the logs of the team meetings on line.

PLUG: I'm working on a Ruby wrapper for Evolution. Good times!

Unfortunately, the Mono Basic has thus far failed to materialize. I keep reading about how it's slowly creeping, but all the real focus is on C#. If it's gotten past the "Hello, World" state where it was a couple years ago, I haven't heard about it.

Each time I read how Mono is advancing, and how complete Mono web development is, I have another look at the status of MonoBasic. That means I go to the whopping one (count 'em!) page devoted to Mono Basic. It says (just as it did a year ago):

• The above features are fully implemented and are being checked for conformance to MS's implementation.

So what's the status? Is it 10% done? 90% done? Is there a timetable attached to the project? Will the Mono IDE support it?

I can't tell. It's pretty much the way it's always been.

The Visual Basic runtime has been ported over, allowing applications compiled on ASP.NET to run, but that's not the same thing, at all. Note that it was donated by Mainsoft, not developed by the Mono folk themselves.

It's too bad, because we're an ASP.Net shop, and we're not about to jump over to C#. Don't bother with the lecture about how the only difference between the two languages is just syntactic sugar, either.

... because we make the "copy" better, more secure and add more features all while adhereing to open, published standards.

Take http://www.spreadfirefox.com/, which is the Firefox webbrowser, for example. This piece of software is hardly new in the sense of being first of its kind, and yes it "copies" the same basic functionality that IE does (and IE copies from Mosaic - check out help->About Internet Explorer, it says clearly "Based on NCSA Mosaic."), but just because someone else invented the wheel doesn't mean we can't use it or make our own, or a better one.

And don't get me started on innovation. As a matter of fact FOSS has already beaten the mighty M$ to a better desktop search (Beagel http://www.gnome.org/projects/beagle/ vs. WinFS - though I will admit I can't quite predict what WinFS will be like IF it ever gets released or if the 2 are even comparable).

Oh, and we are creating new virtual machine architectures[VMA] (XEN http://www.xensource.com/ for example? Again, not sure if that is what you meant with VMA) and new visual interfaces (check out http://cairographics.org/introduction/ for Cairo, which may beat M$ again to the finish-line).

And while M$ buys 90% of the time the technology or licenses it, FOSS actually does develop their stuf from scratch.

Rehashing what's been done before and then claim we do not have freedom to do what we want to do. Interesting. I am not quite sure where these 2 opinions intersect to make sense. Please explain yourself further ...

All in all I think you are way of mark, Microsoft-Fanboy!

Here's the homepage for F-Spot, FWIW.

damn, beat me to it.

No, they beat you to it.

GConf anyone? Only less per-user oriented and more system-wide oriented?

If you're going to talk about WinFS/Google Desktop/Spotlight analogues, at least refer to something that actually seems to be developed actively. Beagle is actually usable already, and from the beginning, provided both a method for programmers to provide their own filters for file types, as well as a way to access search results from another application, unlike the offerings in the Windows world.

On an offtopic note, Microsoft is screwed if developers start using the Google Desktop API. All it takes is one killer application to depend on it before Microsoft supplies a comparable API. Then Google will have control of the desktop search market, because people will depend on it for the functionality of other programs. It'll be fun to see how that turns out.

On the Linux front, things are a bit more complicated. Beagle's nice and all, but it depends on Mono, which many people are reluctant to depend on. I haven't heard of anyone planning to integrate Beagle's searching into Gnome programs. Sometime soon, people are going to have to come to a final decision on Mono. When a stable version of Beagle is released, users and developers alike are going to want to use it.</OT>

Linux is actually ahead on two of them, at least:

http://www.cairogrpahics.org/ is bringing avalon-like stuff to linux, and you can download early versions now.

http://www.gnome.org/~seth/storage/ is bringing WinFS/google-desktop -like stuff to [gnome desktop] linux at the user interface level (and Hans Reiser is still saying he's going to do it at the system level, unlike Microsoft's revised WinFS approach), and you can download early versions now.

(Why patents on the areas in question are particularly sickening: not only was there prior art, there was widely publicised Open Source prior art!)

This? Except for the fact Microsoft's Central Soviet will be able to enforce its use, there are already several systems that are likely comparable on windows, linux and, heck, amiga.

Desktop Linux has, for the most part, stagnated because KDE and GNOME won't merge into one mega-standard.

Desktop Linux has stagnated because neither KDE or GNOME are good enough. They are incomplete. Merging the two together would just create a bigger incomplete, not good enough, system, and subsequently, other projects would be founded to make up for it's flaws.

If you're running GNOME, a KDE app, Mozilla Firefox, and OpenOffice, you've got at least four major libraries now sitting in your memory.

But *why* are you running those in the first place? If you're running GNOME, why use Firefox over Epiphany, the offical GNOME browser? Why run OpenOffice over Gnome Office?? If you're running KDE, why not use Konqueror and KOffice? Why do you need to run KDE apps when you're using GNOME as your environment (and vice versa)?

The basic answer that people give for using a "non-standard" app (eg using GNOME apps in KDE) is that the "standard" solution either isn't good enough or doesn't exist. The grass is always greener on the other side of the fence.

Merging the two would just be encircling them in a bigger fence. If wouldn't stop anyone else from doing something better on the other side.

Desktop Linux has, for the most part, stagnated because KDE and GNOME won't merge into one mega-standard.

Desktop Linux has stagnated because neither KDE or GNOME are good enough. They are incomplete. Merging the two together would just create a bigger incomplete, not good enough, system, and subsequently, other projects would be founded to make up for it's flaws.

If you're running GNOME, a KDE app, Mozilla Firefox, and OpenOffice, you've got at least four major libraries now sitting in your memory.

But *why* are you running those in the first place? If you're running GNOME, why use Firefox over Epiphany, the offical GNOME browser? Why run OpenOffice over Gnome Office?? If you're running KDE, why not use Konqueror and KOffice? Why do you need to run KDE apps when you're using GNOME as your environment (and vice versa)?

The basic answer that people give for using a "non-standard" app (eg using GNOME apps in KDE) is that the "standard" solution either isn't good enough or doesn't exist. The grass is always greener on the other side of the fence.

Merging the two would just be encircling them in a bigger fence. If wouldn't stop anyone else from doing something better on the other side.

There used to be talks of a Mozilla-GNOME alliance, perhaps even a merger, to stand united against .NET/XAML/etc. Any news on this?

Looking at this article there is indeed a native OS X port coming. Woo-hoo!

I have to admit it looks very nice. That being said it also appears not to have much in the way of content. Most of the stuff seems (except for the good how-to) appears to just release notes (http://www.gnome.org/start/2.10/notes/rnwhatsnew. html) repackaged. If that is what they were going for then okay, but I think they could do a whole lot more with this. (caveat: this is my first time reading the Gnome Journal).

beagle , lucene or swishe for *nix, MS-Land etc.

planet.gnome.org has a load of GNOME developers responding to the two articles in a far more logical and intelligent way than the articles deserve.

Somebody like Eugenia who runs such a badly-implemented news+comment site really shouldn't complain about GNOME not implementing features the users want.

They are devels working on it & they have their own opinions.

Never!

You choose to put a foot in your mouth and you just have to learn to like it!

They took my original quote verbatim but changed "received" from the correct spelling to an incorrect one!

[GNOME is] (...) very usability-test centric (...)

AFAIK, there's only one formally conducted usability-test , a small one at that, made a long time ago, with 12 people. And it was conducted by Sun, not by any Free Software organization.

I was perplexed why anyone would disagree with the following statement: "A feature will be implemented if and only if there is a developer who wants to implement it"

"The Eclipse [eclipse.org] project actively encourages its users and clients to log bugs and change requests as well as vote and comment on them through their Bugzilla. [eclipse.org]"

Perhaps you didn't read Eugenia's original post to desktop-devel-list... no shame in that. She neglected to link to it in her own article, which suggests at least a modicum of shame (though not enough to stop her from posting the article). It says, and I quote:

I currently have 20 feature requests for Gnome 2.1. Where should I place them? The Bugzilla is not where I want to place them because:
a. no one will pay attention ultimately (gazillion of feature requests never go anywhere there, let along bug reports)
b. I don't want to spend half an hour placing 20 features requests on the bugzilla one by one.

Her first point is bogus... I'm with many other volunteers in traiging GNOME Bugzilla regularly, and have worked on many enhancements myself.

Her second point... She is too lazy to file enhancements at bugzilla. However, she's got plenty of energy to send e-mail using Microsoft Outlook to a GNOME developer's mailing list, then write the article at OSNews.

Yes, GNOME encourages people to file enhancements at Bugzilla. Eugenia, however, rejects this, then says GNOME Developers doesn't listen to users.

Hi --

People like to give often the be-thankful-shut-up-and-code-and-submit-patches standard answer, but I would like to know if not even reviewing 19% of patches as evidenced here is "acceptable" (i.e., widely practised) or is there a problem?
How do other FLOSS projects stack-up against each other on this measurement?

Here are two fuckholes saying "Work for free, or don't make useful programs!"

Free software is not about getting software without paying for it, it's about making sure that when you DO pay for it, you will always have it!

I don't understand why that's so hard for people who are just being introduced to the Fedoras and the FreeBSDs of the world.

If you don't know how to write software, you can always learn! If you don't want to learn, consider making a bounty for the things you want.

They don't seem to understand the very basic concept that if they want a better Free desktop, then someone has to pay for it.

They also don't seem to understand that those wants are subjective.... Some users feel like they already have all the free desktop that they need

You're the same fuckheads that sue PBS for misappropriating public interests but never made a donation.

You make me sick.

The Eclipse project actively encourages its users and clients to log bugs and change requests as well as vote and comment on them through their Bugzilla.

IIRC, this concept was encouraged by ERS [sic] in Cathedral... It would be nice to see other mainstream OSS projects such as GNOME actively embrace this model of community involvement.

The Eclipse project actively encourages its users and clients to log bugs and change requests as well as vote and comment on them through their Bugzilla.

IIRC, this concept was encouraged by ERS [sic] in Cathedral... It would be nice to see other mainstream OSS projects such as GNOME actively embrace this model of community involvement.

GnomeLove is an initiative that aims to help people who want to get started contributing to GNOME

GnomeLove

They didn't tell her to STFU or to F off & die.

Sure ?

They didn't tell her to STFU or to F off & die.

Sure ?

For those just joining the discussion, you MUST read the whole thread, "roadmap status update/update request", Luis Villa, http://mail.gnome.org/archives/desktop-devel-list/ 2005-March/thread.html#00078

They didn't tell her to STFU or to F off & die. They gave her reasons why her idea for an official poll would not work. They gave her reasonable suggestions on how & why feature requests may go unfulfilled. She rallied & reiterated her points but they did not fall on dead ears. Read through the mailing list and see it for yourself. She is just one person and is guaranteed to have her own opinion. They are devels working on it & they have their own opinions.

See also a coincidental GNOME dev blog, March 10 Jakub Steiner's blog on how to request features: http://jimmac.musichall.cz/weblog.php

Was it removed or was considered not as important as the other announced features?

although I doubt that Google can index something that got released today

Yeah, it's beta 1. About a month old.

The "mold" is theme. It isn't the default one, either.

Bunch of better screenshots here http://www.gnome.org/~davyd/gnome-2-10/ and here http://www.gnome.org/start/2.10/notes/rnwhatsnew.h tml