From my inbox:
Blog About Mule Studio, Get a T-Shirt
Are you as excited about Mule Studio as we are? If so, blog about it and send a link to your blog and your postal address to reply@mulesoft.com and we’ll send you a Mule T-Shirt.
Even if you don’t need the T-Shirt download Mule Studio and take the tour.
Interfaces are always slightly different, range/ease of operations offered vary, documentation varies wildly, so if nothing else, you will learn something in the process.
And, if you blog about it, etc., you will get a new T-Shirt.
Something to look forward to in the mailbox!
A couple of notes on getting started, not that you need them but someone else may:
Step 1 reads:
Before you unzip the muleStudio
package, ensure that it has the permissions required for installation.
To set these permissions, open a console and execute the following command:
chmod u+x muleStudioThe muleStudio folder or directory appears when the unzip operation completes.
Err? Permission to install?
Permission to install is a user privilege question, not setting the file to be executable.
On Linux (Ubuntu 10.10) I just tossed it into my /home/patrick/working directory where I keep all manner of software. It’s just me on the box so I don’t have to worry about making apps available to others.
But, after you unzip the file you do have to:
chmod u+x muleStudio*
BTW, the folder I got was: MuleStudio, so my path is /home/patrick/working/MuleStudio.
Step 2 Execute reads:
Unzip the muleStudio package, which is located in the following path:
/MuleStudio
Enter the following command in the console to launch muleStudio:
./muleStudio
Alternatively, double click the muleStudio file in the Linux graphic interface, as shown above
Err, but we just unzipped it, yes?
Let’s re-write steps 1 and 2:
Step 1:
Unzip the MuleSoft package for your system into a convenient location.
The folder or directory name will be MuleSoft
Step 2:
Change to the MuleSoft directory.
Make the muleStudio* file executable with the command:
chmod u+x muleStudio*
Start the program by:
Double-clicking on muleStudio* in the graphic interface, or
entering the command:
/.muleStudio*
That is trivial in terms of improving the use of MuleStudio but when clear writing becomes a habit, more difficult topics become easier for users.