| 20200504.content | ||
|
English
Today, Google announced the projects accepted for this year's [Google Summer of Code](https://summerofcode.withgoogle.com/), a yearly event with the goal to encourage students to participate in open source projects. For many students, it's the first time working in a collaborative environment. We are especially delighted to announce that the ScummVM Team will support and mentor four fellow adventurers during their journey. Dylan Servilla and Nathanael Gentry will both work on our *Director* engine. While Dylan's goal is to help with Lingo-related stuff like factories, Nathanael will start working on rendering routines. Both will eventually lead us to support at least [*Spaceship Warlock*](https://www.mobygames.com/game/spaceship-warlock) and [*The Journeyman Project*](https://www.mobygames.com/game/journeyman-project). We want ScummVM to be easily accessible to as many people as possible. This obviously includes localisation to help removing language barriers. This year, Aryan Rawlani will help improving support for languages written from right to left ('RTL') as well as adding proper Unicode support to the ScummVM GUI. Imagine ScummVM being available in every possible language one day and you might understand how important Aryan's work is. Besides that, Aryan will also work on the mechanics we use to detect your games in order to improve reliability and performance, which includes deep rework on how our plugin system works. During GSoC, ScummVM also acts as an umbrella organisation for its sister project [ResidualVM](https://www.residualvm.org). Gunnar Birke will work on implementing support for the Wintermute 3D engine to ResidualVM. Wintermute 3D is the - you guessed it - 3D counterpart to the Wintermute engine supported by ScummVM which is only able to play 2D games due to the project's scope. Adding support for Wintermute 3D to ResidualVM will eventually allow you to run games like [*Alpha Polaris*](https://www.mobygames.com/game/windows/alpha-polaris). Brace yourselves - Summer 2020 is coming. Prepare for supporting our students on their glorious adventure. When your watch begins, follow their process on the [ScummVM Planet](https://planet.scummvm.org/). |
||
| 20200514.content | ||
|
English
Get your season (of docs) pass ready! We are excited to announce that ScummVM has been accepted as a participant of [Google Season of Docs 2020](https://developers.google.com/season-of-docs). One of the most important parts of every open source project is its documentation. Good documentation is vital for making the project accessible to both end users and new developers wanting to have a deeper look into the project's internals so they can start contributing on their own. Season of Docs, a recent initiative by Google to connect technical writers with open source projects. The program offers a great way to gain practical project experience, as well as explore the world of free software and the great communities that evolve around them. For ScummVM this is a wonderful opportunity to improve our documentation. You can check out our [ideas page](https://wiki.scummvm.org/index.php?title=Season_of_Docs/GSoD_Ideas) or if you want to bring up your own ideas - get in touch with us on our [Discord server](https://discord.gg/6TBm9hJ). We've had a lot of successful student projects as part of Google's Summer of Code in previous years - we’re looking forward to carrying that success into Google's Season of Docs and inspire you to work with us and add your very own success. The deadline for proposals is July 9. Please make sure to read the program timeline, guidelines and FAQ on [the Season of Docs website](https://developers.google.com/season-of-docs) for additional information. |
||
| 20210518.content | ||
|
English
Yesterday, Google announced the list of students accepted for this new edition of the [Google Summer of Code](https://summerofcode.withgoogle.com/). We are very proud to welcome 6 students this year who will be working on various parts of the project during the upcoming months. * Aashwin Vaish (aka av_dx) will improve the GUI by adding a graphical interface for game library management, so that games are displayed with cover art thumbnails, grouping options and various filtering fields * a-yyg (aka a/) will be working on writing a new engine for Faery Tale Adventure II, based on original sources kindly provided by The Dreamers Guild * Crane yang (aka sheep) will join the effort to improve the current Director engine * Divyam Ahuja (aka Hikigaya) will be working on finishing the implementation of some engines which are currently stalled, with a priority on MacVenture and Avalanche engines * Dylan Servilla (aka djsrv) will also work on the Director engine, continuing his previous GSoC work and aiming to reach Director 2-4 support * taylorzhancher (twan) will focus on adding Text To Speech functionality to various games to improve the gaming experience of people having troubles reading texts on screen We haven't had the opportunity to support and mentor 6 GSoC students since 2008. So, let's celebrate and give a particularly warm welcome to the 2021 GSoC students! |
||
| 20210817.content | ||
|
English
After 5 years of active development, we are glad to finally announce the first MacroMind/Macromedia Director-based games to be supported.
Iskrich, a GSoC student, laid down the engine’s first lines of code, based on the initial reverse engineering efforts of fuzzie, which she wrote in Python as part of the _continuity_ project. Then, the work was continued by sev in 2017 when Lingo compiler development was started and stevenhoefel started adding Director 5-related code. In 2018, there was practically no development, but in 2019, moralrecordings made some advancements for Director 4. Finally, in 2020 and 2021, there was a big chunk of development, first by npjg and djsrv, then by sheep and djsrv, while rvanlaar set up a continuous integration buildbot for the project. Long story short, after 3738 commits, we are now announcing support for Director 2-based titles such as _Spaceship Warlock_. Selected Director 3-based titles may work, and in particular, we support _L-ZONE_. Grab your CDs and give these titles a go. We are also actively collecting info on any Director-based (and Shockwave) titles that we catalogue on [our Wiki](https://wiki.scummvm.org/index.php?title=Director/Games), so, please, help us with this task. We are actively working on deepening Director 3 compatibility, particularly the original _Journeyman Project_ and advancing with Director 4 support, having _Meet MediaBand_ and _Chop Suey_ as our primary test targets. For running the games you will need the [latest daily build](https://www.scummvm.org/downloads/#daily) of ScummVM. And as usual, if you see any issues, please file them in the [issue tracker](https://bugs.scummvm.org/). |
||
| 20220308.content | ||
|
English
This year our project once again was accepted to the [Google Summer of Code](https://summerofcode.withgoogle.com) program.
In previous years, Google only allowed students to participate. This year, however, both students and non-students are welcome to join us and hack together. There are now two sets of tasks, for 175 hours and for 350 hours. Some of our tasks could be either of the two. ScummVM is looking for applicants! A list of suggested projects can be found on [this page](https://wiki.scummvm.org/index.php?title=Summer_of_Code/GSoC_Ideas_2022), but we’re open to your own ideas too. Please make sure you provide the [required information in your application](https://wiki.scummvm.org/index.php?title=GSoC_Application) before submitting. We have gathered some information to guide you, based on our previous 14 years of experience in the program. You may start your exploration from our [Google Summer of Code miniportal](https://wiki.scummvm.org/index.php?title=Summer_of_Code). Also, please join our [Discord server](https://discord.gg/4cDsMNtcpG) and follow the #scummvm-gsoc channel where you can engage with our mentors and the rest of the team. We are looking forward to your fine application and participation! |
||
|
The translation has come to an end.
| ||
| 20200504.content | ||
| 20200514.content | ||
| 20210518.content | ||
| 20210817.content | ||
| 20220308.content | ||
|
The translation has come to an end.
| ||