I have very little experience with Flash but I need to edit an existing group of ActionScript and FLA and export it as a SWF file.
I have Flash Professional installed.
I am a .NET/Java developer, so the coding is not an issue.
The issue is I don't know how to "open" the source code as a "project" fit for "publication".
The program I want to edit is an open source quiz on OnGaurdOnline.gov:
Web - http://www.onguardonline.gov/media/game-0011-phishing-scams
Download - http://www.onguardonline.gov/sites/default/files/phishing_game_source.zip
What do I have to do in order to:
1)Open the "project" (Right now its a folder of .as, .fla and .swf files)
2) Makes changes to code (how do I open the script window)
3) "Publish" the changes so that the same output is created (2 SWF files; loader.swf, phishing.swf)
I would really appreciate any assistance you can give me.
1.- Open the fla file (project are no available in Flash CC)
2.- Press F9 to apen the "Action Window" or go to Window > Action
3.- change your code
4.- Pres CTRL + INTRO to test your changes
5.- Publish Shift + ALT + F12 to compile
Related
I am using epos sdks for printing in my app. I don't have printer to check the exact output of the printed bill. So is there any way to simulate the output without printer by using epos iOS SDK?
Please download the sdks from the following location https://download.epson-biz.com/modules/pos/index.php?page=single_soft&cid=4768&scat=50&pcat=7
1. Unzip the downloaded file(if it not done automatically) and go to the javascript folder.
2. Unzip "ePOS-Print_Sample_SDK_V5.0.1E" and check for the folder "editor".
3. Open the folder and right click on the 'index.html' file and open it using any browser.
4. Use the edit to enter the input and check the output in preview tab.
You can use EPSON's ePOS XML Editor. I've published the source code for it in a public repo and added a Github Page so it's easier to find and use.
You can find it here: https://franciscohanna.me/epson-epos-xml-editor/.
In the editor, you can drag and drop elements and use the Preview tab to have an approximate preview of the print.
When I browse online iOS docs for classes, it has an option to show swift, obj-c, or both. I have mine currently set on obj-c (I peek at Swift from time to time, but in my day to day work, it just clutters the docs).
Is there a way to do similar in the integrate help viewer for Xcode 6? Every time I browse a class document, I have to mentally filter out all of the swift variants.
The documentation is just a set of HTML files. If it's downloaded, you can edit a CSS file to completely hide Swift or Objective-C code.
Open Documentation window.
Select "Editor" > "Share" > "Open in Browser" menu.
Copy the corresponding part of the address of the page that opens up:
/Users/XXX/Library/Developer/Shared/Documentation/DocSets/com.apple.adc.documentation.XXX.docset/Contents/Resources/Documents/
Switch to Finder, and use "Go" > "Go to Folder" menu to open up the folder.
Browse to Resources/XXXX/CSS folder and edit "xcode5.css" file. You should add either of these blocks to hide Swift or Objective-C:
div .Swift {
display: none !important;
}
div .Objective-C {
display: none !important;
}
Restart Xcode and enjoy reduced clutter.
One way is to choose Editor -> Share -> Open in Browser. You can also make a shortcut via Preferences... -> Key Bindings or the Keyboard System Preferences.
It still opens Safari, but it is just one step, so it might be a good solution to your problem.
I navigated to the bottom of those folder trees, located the files specified (one for iOS docs, one for Mac OS X docs), duplicated each file for a backup (command D in Finder), opened each file and pasted :
div .Swift {
display: none !important;
}
at the end of each file.
Rock and Roll! Thank you pointum, you made my day.
Ref: My file path was like this. Note that your path may differ by the number just before the /CSS/
Mac OS X Documentation File (yours may differ by the 1058)
~/Library/Developer/Shared/Documentation/DocSets/com.apple.adc.documentation.OSX.docset/Contents/Resources/Documents/Resources/1058/CSS/xcode5.css
iOS Documentation File (yours may differ by the 1081)
~/Library/Developer/Shared/Documentation/DocSets/com.apple.adc.documentation.iOS.docset/Contents/Resources/Documents/Resources/1081/CSS/xcode5.css
I have some CSS in my hybrid iPad app files that I would like to edit. I came across iFunBox and iExplore, which allows me to move the file between iOS and macOS. But I cannot edit the files directly. I am doing the following:
Open and Edit the file in TextWrangler by clicking on the file in iFunBox UI
Reveal the file in finder
Copy the file to iPad by dragging it to iFunbox
It appears that it should be easy iFunBox or similar to automate this process and hance make the file editable directly.
Anyone aware of an app which achieves this?
Attached is a screenshot of my cluttered Desktop, showing the iExplore, TextWrangler and Finder window. Ideally, I would like to see an Edit option alongwith Open and Quick Look options.
Wait, do you just want to be able to edit files via FTP? If so use, Gusto
I am providing this for everyone to hopefully save you some brain damage in finding this yourself.
As I'm working on a BlackBerry project that will run on various devices I ran into an issue grabbing screenshots from the handset (including the Torch 9850 ... not quite as good as my iPhones or my Android EVO or Infuse, but much better than the Storm and finally starting to look like a real smartphone - great performance and battery life too).
Normally I'd use my trusty BBScreenShooter and everything would be fine, but it kept crashing when attempting to capture images on the 9850. I posted a couple of requests for help on this site, but nobody could tell me why my BBScreenShooter was crashing or why I'd get "Retrieving screen <active> data ... Error: buffer too small" when using RIM's JavaLoader utility directly.
For those who didn't know BBScreenShooter delegates the "heavy lifting" to JavaLoader to grab the images.
With the help of Mark Sohm (easily one of the most knowledgable BB guys I know walking the planet) he asked me to verify I was using JavaLoader that is included in the v7 SDK. Turns out I wasn't. Good catch Mark, and thanks!
From the looks of things it appears the earlier versions of the JavaLoader utility have byte[] buffers they use for image capture that are hardcoded ... and too small.
So, for all those who need to capture screen shots from RIM's new 480 x 800 based handsets I have included a quick "how to" guide to help you get productive ASAP.
Step 1 - Make sure you have the v7.0 SDK downloaded (doesn't have to be installed, though I cannot think of a good reason not to). For Eclipse users:
Step 1a) Go to the Help menu
Step 1b) Install New Software menu choice
Step 1c) Add the "BlackBerry - http://www.blackberry.com/go/eclipseUpdate/3.6/java" items in your "work with" field.
Step 1d) Under the "BlackBerry Java Plug-in Category", look for the "BlackBerry Java SDK v7.0.0.X" checkbox and click NEXT.
Step 1e) Accept the license agreements and continue the download and installation process.
Step 2 - Go to the installation directory for your newly added SDK. We're going to grab a copy of the path to the JavaLoader utility and use it within a BAT file that will automate the capture and naming of screen shots. This will be found at /plugins/net.rim.ejde.componentpack7.0.0_7.0.0.28/components/bin/JavaLoader.exe
Step 3 - Create a folder you'd like to use to save screen captures. This will also hold your BAT file as the BAT file is specific to this particular project.
Step 4 - Create the BAT file. In my example here I keep all my IDEs, SDK, ... effectively all development environments on a different hard drive than my OS. I keep these on drive D, but modify your BAT to reflect the location and needs of your configuration.
Step 4a) It's important to turn the echo off, otherwise you will probably be unable to use the icon on the desktop to launch this script/utility.
Step 4b) If your BAT file is running locally (same folder) as JavaLoader then this step will be unnecessary. On the other hand if your JavaLoader is on a different hard drive and tucked away deep in folders then you'll have to "change directory" to get to it. Notice the "/D" switch that is used with the "change directory - cd" command so that we can change drives and paths in the same step.
Step 4c) As I like to use timestamps for part of my file names ... set local variables to represent the current date and time.
step 4d) The following "for" statements parse out the current date and time from my Windows 7 computer into a format that I want to include as the file names for my screen captures ... file name == BlackBerry_<date image was taken>_<time image was taken>.bmp.
Step 4e) Copy the newly created device screen shot that JavaLoader captured to your target folder and use the file name we've just created.
Step 4f) Now that we've successfully got a copy of the screenshot saved in our desired target folder we can delete the temporary image that JavaLoader created.
Step 4g) I echo a little statement that lets me know it all worked.
Example BAT file:
#echo off
cd /D D:\Program Files (x86)\EclipseBlackBerry\plugins\net.rim.ejde.componentpack7.0.0_7.0.0.28\components\bin
JavaLoader screenshot tempImage.bmp
set timestampdate=%date%
set timestamptime=%time%
For /f "tokens=2-4 delims=/ " %%a in ('date /t') do (set timestampdate=%%c-%%a-%%b)
For /f "tokens=1-2 delims=/:" %%a in ('time /t') do (set timestamptime=%%a%%b)
copy tempImage.bmp "C:\Users\CirrusFlyer\Desktop\<project name>\Testing\Screenshots\BlackBerry_%timestampdate%_%timestamptime%.bmp"
DEL tempImage.bmp
echo Completed "...\<project name>\Testing\Screenshots\BlackBerry_%timestampdate%_%timestamptime%.bmp"
Step 5 - Close and save your BAT file. I kept the BAT in my actual project folder, then created a shortcut and placed it on my desktop. This way I can have my Eclipse up and running and be debugging the application on my handset, and when I want to grab a screen shot simply double-click the shortcut to execute the capture.
This will create screen shots and place them in the target directory: BlackBerry_2011-10-07_1015 PM.bmp, for example.
Step 6 - Your done. Happy coding. Hope this helps.
My next project: extending Eclipse so that I can do screen captures directly from within the IDE the same way I can when doing Android based programming.
At my job, I was tasked with making a prototype of a new audio device. The heart of the prototype will be an Analog Devices, Inc. Ez-Board with a SHARC 21469 chip.
Using VisualDSP++ 5.0, I wrote the necessary software in C, and it runs perfectly now. But I only know how to download the program into RAM using VisualDSP++ and the JTAG emulator.
I have been trying to figure out how to program the flash memory on the Ez-Board so that any time the board powers up, it will run my C program. How does that work?
I figured this out.
First, in VisualDSP++, under the "Tools" menu, there is a nice GUI for programming flash memory. However, different hardware platforms need different code to do the flash programming, so the GUI is designed to take a "plugin" program that will do the actual flash programming. The Analog Devices Inc. term for this plugin is a "driver". So, before you do anything else, you need to set the correct plugin for flash programming; you do this on the first "tab" of the flash programmer tabbed dialog (the "Driver" tab). Choose the correct driver .dxe file and click on the "Load" button.
Since I am using the 21469 Ez-Board, the "plugin" is available from the sample code for that board. Here is the full pathname of the driver file:
c:\Program Files\Analog Devices\VisualDSP 5.0\214xx\Examples\ADSP-21469 EZ-Board\Flash Programmer\Parallel\21469EzFlashDriver_Parallel.dxe
With that done, you can now build a "loader" file instead of the usual executable. Open your code project in VisualDSP++, and go to the Project Options dialog (Alt+F7). From the "Project" page, change "Type:" from "Executable file" to "Loader file". An "executable file" has the extension ".dxe" while a "loader file" has the extension ".ldr". There are some options that control how the .ldr file is built, but the defaults work fine (at least they did for me with an Ez-Board).
Now build your project as usual. Instead of building a .dxe file, it will build a .ldr file.
Finally, choose "Tools/Flash Programmer..." to bring up the flash programming GUI, and click on the second tab in the tabbed dialog, "Programming". For some reason the loader file is called the "data" file on this page of the dialog. Choose your .ldr file for programming, and hit the "program" button.