This is so not the issue with the ending of Mass Effect 3:
The company is now devoting all of its efforts to producing an "extended cut" DLC for the summer, but fans expecting a fourth ending where they can watch Commander Shepard on a sun-lounger, margarita in hand had better start complaining now -- the new content will only offer more depth and an extended epilogue to those tragic scenes you've already witnessed.
The issue is far simpler: the endings - based on established canon - render all of Shepard's choices moot, as the destruction of the relays destroys all extant galactic civilizations. Period. as I've said before, BioWare will retcon that - it's all a matter of when. They either do it now, and have some chance of not looking like complete idiots - or they do it later, when it finally dawns on Casey Hudson that future storytelling in the ME setting has been destroyed.
Today's Smalltalk 4 You looks at the Searchlight tools in VisualWorks (also available in ObjectStudio). If you have trouble viewing it here in the browser, you can also navigate directly to YouTube. To watch now, click on the image below:
If you have trouble viewing that directly, you can click here to download the video directly. If you need the video in a Windows Media format, then download that here.
James Foster explains how to get going with Gemstone and shared memory:
One of the most common problem people have installing and starting GemStone/S is getting shared memory configured properly. This post will discuss shared memory in general and GemStone’s use of shared memory in particular.
Today's Smalltalk 4 You looks at taking screencaps within the VA Smalltalk environment. If you have trouble viewing it here in the browser, you can also navigate directly to YouTube. To watch now, click on the image below:
If you have trouble viewing that directly, you can click here to download the video directly. If you need the video in a Windows Media format, then download that here.
You can also watch it on YouTube:
Today we'll look at a simple feature of VA Smalltalk that is easily overlooked: the ability to take screen captures (full or partial) from within VA. That includes the ability to focus on individual windows and widgets. To get started, go to the Options menu in the launcher:
<
Select the Screen option. If you select a region or window, you'll get a (configurable) delay during which you can bring the desired window to the front. If you decided to capture the entire screen, you should see something like this (using paste into Paint):
Need more help? There's a screencast for other topics like this which you may want to watch. Questions? Try the "Chat with James" Google gadget over in the sidebar.
I just watched the ending again as my daughter finished it; the destruction of the relays is utterly unambiguous. The Normandy fleeing (with people you had in the final battle) makes no sense at all. The only way any of that works is if some variant of the indoctrination theory is what happened. Anything else, and BioWare has shutdown the possibility of further gaming in that setting. Why? Well:
The destruction of the relays took out every advanced civilization in the galaxy, including humanity. Those soldiers you saw celebrating on earth? They did that for about two seconds, before earth got vaporized. Sorry Hudson, your existing lore states that a destroyed relay takes out the system - hell, the Batarian's anger over that fact is part of ME3.
What few civilized remnants remain on outer colonies are now cut off from galactic trade - no relays, no communication - no home systems to even go back to.
Even if the knowledge to rebuild the relays exists, getting them back in place will be the work of centuries, if not milleniums. Never mind that it'll probably be the work of the next cycle's set of races, as this cycle's races were wiped out by the relay destructions.
It's not about having a "happy" ending; it's about having one that makes sense. The one we saw? Outside of Indoctrination, it simply doesn't work. Either BioWare retcons it now, or they do it later when they decide to release a new game in the same setting. They have to do it regardless. Here's what they have to say:
Although some have expressed concern that Bioware could compromise the integrity of its writers' original intentions, co-founder Ray Muzyka claims: “We think we have struck a good balance in delivering the answers players are looking for while maintaining the team’s artistic vision for the end of this story arc in the Mass Effect universe.”
So at this point, the intransigence on the part of EA and Hudson is all about not wanting to look like "they caved to the fans". Guys - you have to retcon the ending eventually, or there's no setting for any future games. Full stop, period. That means you can salvage some small measure of fan (read: future customer) support by doing it now, or you can look as stupid as the Highlander writers did when they did Highlander 2, which was ignored by the subsequent movies and TV show.
Join the Facebook Group to discuss the tutorials. You can view the archives here.
To watch now, click on the image below:
If you have trouble viewing that directly, you can click here to download the video directly. If you need the video in a Windows Media format, then download that here.
Today's Smalltalk 4 You looks at Toothpick for logging in VA Smalltalk. It's a lot like log4s, which we covered in other screencasts. The difference? Tootpick works across all the major Smalltalk dialects. If you have trouble viewing it here in the browser, you can also navigate directly to YouTube. To watch now, click on the image below:
If you have trouble viewing that directly, you can click here to download the video directly. If you need the video in a Windows Media format, then download that here.
You can also watch it on YouTube:
Today we'll take another look at logging in VA Smalltalk, but we'll use Tootpick - the cross platform logging solution for Smalltalk systems. First, download the ENVY package from Metaprog.
Once you have that, import the .dat file into your repository (see this screencast for an example of doing that). Then load SUnit support - it's an unlisted pre-req for the configuration map:
Once you have SUnit it, load the Toothpick config map:
Now we can proceed to use the same code that works in other Smalltalks. First, set up the logger (we'll use a Transcript logger here), and start the logging system:
"create a logger"
logger1 := TranscriptLogger new
name: 'My first Logger'.
"where do logging events go"
logger1 format: SimpleLoggingFormatter defaultFormat.
"logging policy"
logger1 policy: (LoggingPolicy category: #debug level: #debug).
"register the logger"
(LoggingMultiplexer current)
addLogger: logger1.
"Start the loggers"
(LoggingMultiplexer current) startAllLoggers.
A quick look at the Transcript shows that it works as we intended:
Need more help? There's a screencast for other topics like this which you may want to watch. Questions? Try the "Chat with James" Google gadget over in the sidebar.
Join the Facebook Group to discuss the tutorials. You can view the archives here.
To watch now, click on the image below:
If you have trouble viewing that directly, you can click here to download the video directly. If you need the video in a Windows Media format, then download that here.
Today's Smalltalk 4 You looks at logging with Toothpick in VisualWorks and Pharo (the code is available for VA, and Dolphin as well - and the VW code works in ObjectStudio, while the Squeak code is what I used in Pharo). If you have trouble viewing it here in the browser, you can also navigate directly to YouTube. To watch now, click on the image below:
If you have trouble viewing that directly, you can click here to download the video directly. If you need the video in a Windows Media format, then download that here.
You can also watch it on YouTube:
The logging code used in the screencast, which you can find documented at metaprog:
"create a logger"
logger1 := TranscriptLogger new
name: 'My first Logger'.
"where do logging events go"
logger1 format: SimpleLoggingFormatter defaultFormat.
"logging policy"
logger1 policy: (LoggingPolicy category: #debug level: #debug).
"register the logger"
(LoggingMultiplexer current)
addLogger: logger1.
"Start the loggers"
(LoggingMultiplexer current) startAllLoggers.
LoggingEvent
category: #debug
level: #warn
message: 'using obsolete protocol'.
LoggingMultiplexer current stopAllLoggers
.
.
