Andres Valloud has announced Smalltalks 2012, set for early November, 2012:
This would be a good time to get a calendar and try blocking November 7th through November 9th. You see, we're inviting you to Puerto Madryn in beautiful southern Argentina so you can attend Smalltalks 2012! In the coming weeks we will send out research track calls for papers, calls for participation, and start the registration process. But get those presentations ready, Smalltalks 2012 will be here before you know it. We look forward to seeing you there!
Today's Smalltalk 4 You wraps up our look at log4s with an examination of some of the more useful API methods we've brushed over. 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 some of the useful API methods for log4s that we've brushed over in the last few screencasts. To get started, we'll add a Transcript appender to the root logger (which was set up in the ini file):
"logging apis"
logger := EsLogManager getLogger: 'root'.
"Add a transcript appender programmatically, but set at a higher level"
level := EsLogManager getLevel: 'Error'.
pattern := EsPatternLayout new: 'ڴe{ISO8601}: [%level] %message'.
transcriptAppender := EsTranscriptAppender level: level layout: pattern.
logger addAppender: transcriptAppender.
One of the things you can do is ask a logger for all of the appenders it has:
"get all appenders"
logger allAppenders.
Which gives us this, if we inspect that line of code:
You can also get a specific appender by name:
"get the transcript appender"
logger getAppender: 'Transcript'
If we inspect that, we'll see the following:
Next we'll remove the Transcript appender. Note that we need to send the appender, not the name, as the argument. The VA 8.5 document is not clear about that:
"remove the Transcript appender"
logger removeAppender: transcriptAppender.
Now inspect the all appenders API again, and you should see:
Note that we're back where we started just the appender specified in the ini file. Finally, you can remove all appenders:
"remove all"
logger removeAllAppenders.
And inspecting the all appenders api yields:
And that about wraps it up for log4s. You should definitely peruse the documentation for more information
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.
Welcome to episode 72 of Independent Misinterpretations - a Smalltalk and dynamic language oriented podcast with James Robertson and David Buck.
This podcast was recorded by Bob Nemec and I at the end of day 3 of STIC 2012 - we spoke about the "big data" keynote that I missed, and touched on a lot of the other talks. There's a bit of background muzak playing - we recorded in the conference hall.
You can subscribe to the podcast in iTunes (or any other podcatching software) using this feed directly or in iTunes with this one.
To listen now, you can either download the mp3 edition, or the AAC edition. The AAC edition comes with chapter markers. You can subscribe to either edition of the podcast directly in iTunes; just search for Smalltalk and look in the Podcast results. You can subscribe to the mp3 edition directly using this feed, or the AAC edition using this feed using any podcatching software. You can also download the podcast in ogg format.
If you like the music we use, please visit Josh Woodward's site. We use the song Troublemaker for our intro/outro music. I'm sure he'd appreciate your support!
If you have feedback, send it to jarober@gmail.com - or visit us on Facebook - you can subscribe in iTunes using this iTunes enabled feed.. If you enjoy the podcast, pass the word - we would love to have more people hear about Smalltalk!
Welcome to episode 72 of Independent Misinterpretations - a Smalltalk and dynamic language oriented podcast with James Robertson and David Buck.
This podcast was recorded by Bob Nemec and I at the end of day 3 of STIC 2012 - we spoke about the "big data" keynote that I missed, and touched on a lot of the other talks. There's a bit of background muzak playing - we recorded in the conference hall.
You can subscribe to the podcast in iTunes (or any other podcatching software) using this feed directly or in iTunes with this one.
To listen now, you can either download the mp3 edition, or the AAC edition. The AAC edition comes with chapter markers. You can subscribe to either edition of the podcast directly in iTunes; just search for Smalltalk and look in the Podcast results. You can subscribe to the mp3 edition directly using this feed, or the AAC edition using this feed using any podcatching software. You can also download the podcast in ogg format.
If you like the music we use, please visit Josh Woodward's site. We use the song Troublemaker for our intro/outro music. I'm sure he'd appreciate your support!
If you have feedback, send it to jarober@gmail.com - or visit us on Facebook - you can subscribe in iTunes using this iTunes enabled feed.. If you enjoy the podcast, pass the word - we would love to have more people hear about Smalltalk!
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
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.
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.
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.
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.
.
.
.
