Jump to content
We owe you an explanation.
June 30: An important update for readers in Japan.

You deserve an explanation, so please don't skip this 1-minute read. It's Tuesday, June 30. Our fundraiser won't last long, but fewer people are seeing our message this month and we might not hit our goal. If you've lost count of how many times you've visited Wikipedia this year, we hope that means it's given you at least ¥300 of knowledge. If everyone who finds Wikipedia useful gave ¥300, we'd hit our goal in a few hours.

It's been 25 years and Wikipedia is still free. It's still created by people, not machines, and we don't run ads or put up paywalls because we're not here to make a profit off your attention. In other words, it's still the internet we were promised.

Less than 2% of our readers donate, so if you've never given and Wikipedia has provided you with at least ¥300 worth of knowledge, donate today. If you are undecided, remember any contribution helps.

Proud host of Wikipedia and other free knowledge projects
How often would you like to donate?
Support Wikipedia year-round
Thanks for your generous support
Please select an amount (JPY)
The average donation in Japan is around ¥800.
  • Preferred Amount
Please select a payment method
Please select an amount (minimum ¥154)
We cannot accept donations greater than 3850000 JPY through our website. Please contact our major gifts staff at benefactors@wikimedia.org.
Please select a payment method
Can we follow up and let you know if we need your help again? The support and advice we get from donors in Japan is priceless, but many donors don't let us stay in touch. Will you commit today, this Tuesday, to staying in touch with the Wikimedia Foundation?
Sorry to hear that. We don't email often; would you consider changing your mind?
Thanks for changing your mind! We’ll respect your inbox.
Your information is handled in accordance with our donor privacy policy, and each email you receive will include easy unsubscribe options.
Please select an email option
Almost done: Please, make it  monthly.
Monthly support is the best way to ensure that Wikipedia keeps thriving.
How would you like to be reminded?
Whether you give now or later, any contribution helps. We can send you an email or text message reminder to join the 2% of readers who donate.
🎉 Thank you for donating recently! 🎉
Your support means the world to us. We'll hide banners in this browser for the rest of our campaign.
Where your donation goes
Accountability and transparency are core values at the Wikimedia Foundation. We manage funds and resources to ensure that every contribution supports our mission. We have earned the Platinum Seal of Transparency from Candid (formerly GuideStar), and Charity Navigator awarded us its highest rating. You can read our most recent annual report for more information about our financial health.
45% $85.4M Technology 32% $60.7M Support 12% $22.8M Fundraising 11% $20.9M General $189.7M Total Funding
45% Investment in Technology

Nearly half of our budget goes toward supporting the technology that powers Wikipedia and other Wikimedia projects. We are constantly working to enhance the user experience for both contributors and readers, improve site security, and ensure reliable access to our websites globally. This infrastructure and product support sustain one of the top ten most visited websites in the world, all at a fraction of the cost of popular for-profit websites.

32% Support for Volunteers

The global reach of Wikimedia projects is made possible by the hard work of volunteers from across the globe. We provide grants, legal support, and other resources to help build vibrant volunteer communities. Additionally, we promote community engagement through outreach initiatives and advocate for the growth and protection of free knowledge.

12% Allocation to Fundraising Efforts

Donor support is crucial to sustaining Wikipedia and our other free knowledge endeavors. Our team is committed to efficient and effective fundraising throughout the year, ensuring that every contribution helps advance our mission.

11% General and Administrative Expenses

Operational costs are essential for the smooth management and governance of the Wikimedia Foundation. These expenses help us recruit top talent and support staff around the world, empowering them to carry out the mission of the Wikimedia Foundation.

XaAES

From Wikipedia, the free encyclopedia

XaAES is a graphical user interface for the OS kernel MiNT (now known as FreeMiNT), and is aimed at systems that are compatible with 16/32 bit (hence ST) Atari computers such as the ST, TT or Falcon. The combination of MiNT and XaAES is the natural successor to MultiTOS.

History

[edit]

XaAES - The beginning

[edit]

XaAES is a free AES (Application Environment Service) written with MiNT in mind, originally developed by Craig Graham (Data Uncertain Software) back in September 1995. Taken from the XaAES beta6, here is a snippet of the readme.txt in which Craig explains his motives for initiating XaAES:

"After using MultiTOS, then AES4.1, I became frustrated at the lack of a decent GUI to use the real power of the MiNT kernel - X Windows is all very well, but I can't run GEM programs on it. MultiTOS (even AES 4.1) is too slow. Geneva didn't run with MiNT (and, having tried the new MiNT compatible version, I can say it wasn't very compatible - at least AES 4.1 is quite stable, if a little slow). MagiC lives in a very fast, very small world all its own, with no networking support, few programs written to exploit it."

NOTE: MagiC later became available on Mac OS (and still later on the x86 PC) with built-in networking, and network drivers also began to appear for the Atari ST. A lot of MagiC software was MiNT compatible, and vice versa, but that came later than the time period of the above quote.

Craig worked actively on XaAES until 1997 when he stopped the development, at that time a plethora of applications were already usable under XaAES.

In 1998 the project was taken up by Swedish programmer Johan Klockars. He had been involved already during Craig's maintainership and at this point he stepped forward after a period of inactivity.

Johan's work resulted in several bugfixes which eventually were released as Beta7+. Shortly after this beta Johan also made the decision to hand over the project to someone else. This time it really seemed like XaAES had hit the end of the road, with no one interested in taking up the project again.

After a period of complete standstill Dutch programmer Henk Robbers took over the project in November 1999. During Henk's maintainer-ship loads of progress was made, and XaAES went from interesting to becoming rather usable and showing great potential. The visual appearance was made to look closer to that of N.AES, as this was the obvious reference target - the AES that at the time was the GUI for FreeMiNT. XaAES also become a lot more robust although the response for key and mouse input was still somewhat of a problem.

Odd Skancke (aka Ozk) continued the development of XaAES, and together with Frank Naumann (then FreeMiNT maintainer), XaAES graphical improvements (skinning) were released with FreeMiNT 1.16. Alan Hourihane, as then FreeMiNT maintainer, was left to do bug fixes until round 2009, when after a resurgence of interest in the FreeMiNT OS, XaAES was then maintained and extended considerably by Helmut Karlowski (who maintains his own branch), especially in the area of Atari TOS application compatibility.

XaAES goes CVS

[edit]

In early 2003 Henk Robbers (of AHCC fame, also makes XaAES beta6 source available) decided it was time to let someone else carry on his work, as he wanted to move on to other computing issues. When Henk went looking for someone who could take care of the continued development, the idea that XaAES should be part of the FreeMiNT project was suggested. After all, it was developed to be an AES for MiNT exclusively, and since FreeMiNT is being administrated via CVS, anyone could access the sources and contribute.

The move to CVS was made possible thanks to great efforts from the FreeMiNT maintainer Frank Naumann, who made the necessary changes to allow XaAES to compile under gcc. In earlier XaAES builds, one of the major problems has been the somewhat irregular response to mouse buttons. This was reworked by Odd Skancke (aka Ozk), something that also resulted in a complete rewrite of the XDD. The moose.xdd (mouse device driver) is now coded in C too, just like the rest of the XaAES code.

Development was later moved from AtariForge to an SVN repository at SourceForge, and from there to the publicly browsable FreeMiNT Git repository on GitHub.[1]

XaAES - A FreeMiNT kernel module

[edit]

In order to get a clean and fast XaAES, the best solution turned out to be changing XaAES into a kernel module. To achieve this goal a completely new API was constructed, and it was quickly apparent that the new kernel module offered massively improved performance. Most noticeably, the response time was significantly improved, resulting in a much more snappy and responsive experience when trying to click a button to see live window redraws, etc. All in all, XaAES reached a whole new level after being integrated this tightly with FreeMiNT and as of the 1.16.1 FreeMiNT release it must be considered highly usable. With the implementation of window shading the list of missing features was getting short.

(This section is used on Wikipedia with permission from http://xaaes.atariforge.net Archived 2003-05-27 at the Wayback Machine)

See also

[edit]

References

[edit]
[edit]