Data Pages and comics
Sometimes in comics you need to give the reader a lot of information in a short amount of time. The dreaded exposition.
Classical comic thinking is to do one of two things: a dialogue heavy page where one character is relaying the information to another (or the reader). This is usually done poorly:
But sometimes it can be done (subjectively) well:
The problem, though, is the As You Know trope. You have two characters, who know this information (or should know the info), but they are explaining it to each other as if they don't know. This is all for the reader's benefit. It's clunky and feels like Silver or Bronze Age comic writing.
Sorry Scrooge…
The other way is through captions.
Not all comics work well with narrative captions. Especially if captions are being used for internal character thoughts (I'm looking at you every-Wolverine-comic-ever).
A modern solution has been data pages. You've seen these a lot in works by Jonathan Hickman, like his creator work:
And in the X-Men, predominately by designer Tom Muller (@hellomuller and @hellomullerltd).
But they've popped up in manga like Gunnm/Battle Angel Alita:
And Darwyn Cooke's Parker books (which even includes prose from the books that have been adapted):
As well as classic comic books like Fantastic Four
And even webcomics such as Drive by Dave Kellet. He even includes the text in a blog post to be more readable on mobile devices.
These all convey information that the author feels the reader should know. Some are done as a document, others as illustrative piece, but they are all giving the reader information.
What makes the Hickman/Muller data pages interesting (particularly in X-Men) is that they are not outside the realm of the story; they are part of it. These pages are documents pulled from the canon of the story. A file from Nick Fury's database, or an historical archive. Dave Kellet even does this with his Enciclopedia Xenobiologica entries about races, places, and technology in his webcomic.
Unlike classic data pages, such as the Baxter Building cutaway, modern datapages are also placed within the reading of the story, not as an extra or appendix. Strip Panel Naked over on Youtube explains Hickman and Muller's approach in detail (spoilers by the way for X-men!)
So consider this as a solution to an exposition heavy sequence. Do a diagram showing your characters' heist plan. Create a schematic of a starship so your readers know where the characters are. Have a legal pad with a lawyer's notes about your character's story. And, if this is in a web or mobile comic, offer the text in a blog post (in fact it's a good practice to offer text of your dialogue).
This is just one solution to exposition. What's some other ones you've see work?
9 notes
·
View notes
A Step-by-Step Guide for Building Your First Mule Application
No matter if you are an experienced developer or new to integration, this blog will guide you through creating your first Mule application step by step.
But before delving into the step, let us first understand the basics!
What is MuleSoft?
MuleSoft is a popular and powerful platform that provides a seamless way to integrate various systems and applications within an enterprise.
What is MuleSoft used for?
MuleSoft Anypoint Platform streamlines API discovery and building, allowing for faster application development and delivery. Moreover, the one unified platform allows you to design, implement, secure, and scale APIs and integrations across many protocols, as well as test them in a variety of ways.
How to Create Your First Mule Application Step by Step?
Understanding Mule ESB
Before diving into the creation of a Mule application, it is essential to understand what Mule ESB is. Mule, as an integration platform, allows you to connect applications, data, and devices both in the cloud and on-premises. Further, it is a lightweight Java-based ESB and integration platform that can handle many integration scenarios.
Setting Up Your Development Environment
The first step in creating a Mule application is setting up your development environment. You will need:
Java Development Kit (JDK)
Mule is a Java-based platform, so you need to have the JDK installed on your machine.
Anypoint Studio
This is MuleSoft integrated development environment (IDE). And it simplifies the process of developing, testing, and deploying Mule applications.
Downloading and Installing Anypoint Studio:
Visit the MuleSoft website and download the latest version of Anypoint Studio.
Follow the installation instructions based on your operating system (Windows, macOS, Linux).
Launch Anypoint Studio and configure the workspace.
Creating Your First Mule Project
Upon launching Anypoint Studio, you will have to define your workspace. This workspace is where your Anypoint Studio project files will be stored on your computer. Moreover, after setting up Anypoint Studio, you are ready to create your first Mule project:
3.1. Create a New Project:
In Anypoint Studio, go to File > New > Mule Project.
In the Project Name field, enter the value HelloMule and, select a Mule runtime version, and then click Finish.
3.2. Designing the Flow:
Mule applications are built around flows. A flow is a sequence of message-processing events.
Use the drag-and-drop interface in Anypoint Studio to add components to your flow.
3.3. Adding Components:
The HTTP module should be pre-installed in your Mule Palette. If it is not present, you can add it by selecting Add Modules. Then, simply drag and drop the HTTP module from the right side to the left side in the Mule Palette. In addition, this process is how you incorporate new modules or connectors into your Mule Project.
The path you set is where your system will run your flow when it gets an HTTP request.
3.4. Configuring Components:
Next, add the Set Payload connector to your flow in the Process section. Further, look for the Set Payload connector in the Core module of your Mule Palette. After that, turn off the “fx” button and enter the text "Hello Mule."
Now go to File > Save��to save your project.
Testing Your Application
Once your basic flow is set up:
4.1. Run the Project:
Click on the Run button in Anypoint Studio to start your application.
Ensure there are no errors in the console and that the application starts successfully.
4.2. Testing the Flow:
Use a tool like Postman to send a request to your HTTP Listener URL.
Check the console in Anypoint Studio to see if the Logger component outputs the expected message.
Deploying Your Application
After testing and ensuring everything works as expected:
Export Your Application:
In Anypoint Studio, right-click on your project and select Export.
Choose to export as a Mule Deployable Archive (.jar file).
Deploying on CloudHub or a Local Server:
MuleSoft Best Practices
Version Control
Use version control systems like Git to handle your source code.
Error Handling
Implement proper error handling in your flows.
Testing
Write unit tests for your flows using MUnit, MuleSoft testing framework.
Next Steps
Explore More Components
MuleSoft offers a wide range of connectors and components. Experiment with them to extend the functionality of your application.
Learn DataWeave
DataWeave is MuleSoft expression language for data transformation.
Conclusion
Creating your first Mule application might seem daunting, but with Anypoint Studio, it becomes an intuitive and straightforward process. By following these steps, you will be well on your way to developing robust integrations using MuleSoft powerful platform.
0 notes