I'm a newbie in TOSCA world. :)
Need help.. I wanted to scan an application by browser, but the 'Browser' option is not displayed. I'm using a trial version (self study purpose), not sure if I'm missing anything or do I need to do some configurations?
Thanks!
Scanning HTML applications in a browser can be triggered by selecting Scan Application -> Desktop on a Modules folder.
Desktop is used here as an umbrella term for all applications with a GUI. More information can be found in the Tosca XScan documentation
While doing the right click for scan options (on a folder in Module Section), do it holding shift key.
.i.e,
"Shift + Right Click" - > it will open the same context menu but additional scanning options would be shown under "Scan Application Option."
Go for Html in that list for browser.
Hidden in plain sight. We faced the same problem when we upgraded to TOSCA 10 from TOSCA 9.2.
In your screenshot, you can see that 'Desktop' option there (Scan Application > Desktop). Once you click that you can scan all that is open and scan-able! Desktop serves for all browser, non-browser.
See here: https://support.tricentis.com/community/manuals_detail.do?lang=en&version=10.1.0&url=tchb/create_modules_xscan.htm
Just FYI
From TOSCA Version 10 Scan -> Browser option is not available and you can use scan -> Desktop to scan. In the version 9.3 you will still find this option.
Related
We have built a WebDav Service with your Engine and have a one problem when we create a new Folder or File:
The new folder / file is created successfully, but not showing in the Windows Explorer. Only if you press F5, the new folder / file is showing (and the name is already selected to be edited).
This behavior is reproducible even with a blank WebDav Solution.
We can reproduce this on Windows 7 and Windows 8 (8.1) using WebDav .NET Server 3.8 and the latest 3.9.
Is there a way to get around this “refresh-problem”?
I solved this issue but clicking in the folder explorer at view > options > then i restored to default and everything is back to normal.
I assume this issue is in Windows Explorer on a single computer. Most likely the WebDAV server-side code is failing with with some exception. Here are some ideas how to detect what is wrong:
Unmount network connections executing 'net use * /DELETE' in a command prompt, this will unmount WebDAV connections too and simulate 'clean' environment.
Retry reproducing the issue and examine your WebDAV logfile. By default it is located in /App_Data/WebDAV/Logs/ folder. Are there any exceptions in it?
Use Fiddler tool or any other debugging proxy to capture and examine HTTP requests. Are there any failed requests?
In case you are creating a folder/file on one computer using Windows Explorer (Microsoft Mini-redirector driver) or IT Hit Ajax File Browser and expect the files list to refresh automatically on another computer this would not work. Mini-redirector does not support any notifications from server and WebDAV does not submit any notifications, you need to refresh the files list manually to see the new items created.
I found this video on Youtube that explains in very much detail how to fix this problem: https://www.youtube.com/watch?v=UUiCPsQquqc
It is a bit lengthy, so I'll just quickly sum it up here:
The reason for these problems are one or more (broken) Shell Extensions that prevent the refresh of the Windows Explorer
To fix it, open up regedit.exe (requires admin privileges), do a search for the Registry Key "DontRefresh". If it is "1", set it to "0". There might be multiple matches for that Key, so repeat until all Keys have the value "0".
This might not work immediately, you may have to kill and restart your explorer.exe process (easiest to do with the Task Manager). Or you can simply reboot your computer. In my case, it worked immediately.
According to the video, the Keys should only be located under HKEY_CLASSES_ROOT/CLSID, but in my case I could only find such Keys in HKEY_LOCAL_MACHINE/Classes/Wow6432Node/CLSID.
I figured it makes most sense to simply search the complete Registry, it does not take very long.
I tred a lot of hacks, from scanning the system, to recreating the profile to hacking Registry keys and hives.
Finally what worked for me -
Right click on desktop
Select Personalize
Click Themes
Click Change desktop icons
Click Restore default & OK
And instantly it began to auto refresh with a new folder, rename, delete, copy, etc.
I had recently upgrade our development machine to Xcode4 and after the initial interface change has gone quite smoothly.
I'm now in the process of using Ad-Hoc distribution on it for the first time so I followed this guide to set up profiles/schemes etc. http://diaryofacodemonkey.ruprect.com/2011/03/18/ad-hoc-app-distribution-with-xcode-4/
This is the process I took:
1/ Setup a new provisioning profile under distribution. I selected Ad-Hoc, the correct App and my UUIDs.
2/ Installed the profile within Xcode 4.
3/ In xcode duplicated the Release Configuration and named it Ad-Hoc.
4/ Under Code-Signing made sure Ad-Hoc had the new profile selected.
5/ Edit Archive scheme and selected 'Ad-Hoc' Build Configuration.
6/ Select Product > Archive and made sure the profile listed was correct.
7/ On save screen selected 'enterprise distribution' and entered the App URL and Title.
8/ Copied the resulting ipa archive, plist and mobileprovision (downloaded in point 1) to our http server.
9/ Added the required html to and pointed mobile Safari to it.
10/ Selected the mobileprovision which installed without a problem.
11/ Selected the App which begins to install resulting in "Unable to Download" at about 90%.
I've tried several potential solutions from other posts but they all result in the same thing. This is used to work fine in Xcode 3 (using normal developer account, NOT enterprise) and as far I can tell I'm not really doing anything different so what am I doing wrong?
Thanks.
Try this: Open the Scheme you are using to edit it. Then check if in ALL the build phases (Build, Run, Test, Profile, ...) the Build Configuration is set correctly. If not set it to the correct configuration and build it again.
If this does not work ad a new Entitlements.plist to your project and add a new value with the key get-task-allow to NO.
Edit: Have you tried to make Product > Build For > Build For Archiving and then Product > Archive.
This worked for me.
we just had the same problem (and we still have it for one device only working on iOS5 Beta, not sure if it is related. All other devices work.), some tips that could help :
Apple dev site:
your provisioning profile could need to be renewed on the apple web site.
on the apple web site check that the device is linked to the provisional profile in the "Device" section. In the "provisional profile" section, the "Edit" feature could lie to you. To add a missing device to a provisional profile, go the "provisional profile" section then uncheck and check back the missing device (the lying part from apple web site ;))
in xcode:
I switched deployment target OS from 4.0 to 4.2
I plugged my iPhone and selected it as target before to create the archive.
this issue doesn't depend on the "team provisioning file", we could build a working archive with another provisioning file too.
If it can help too, I created a doc for distributing the Moodle app but it's generic to any app I guess: http://docs.moodle.org/dev/how_to_distribute_iPhone_test_app
I'm new to web development so please, could you help me to understand if I'm working in the right direction?
There will be a webpage intended for our customers (not intranet) from where they can print labels. Some of the larger customers will have special label printers where configuration and printing using COM-port is the only acceptable option. Basically we have very limited knowledge and control over their environment.
The web-page itself will be a pretty simple html-page or more complex AJAX.
After the customer inputs all the data and happens to chose this type of printing we have following tasks:
1) get data about the printers on the customer's system installed to a comport and if possible get printer settings (like paper size and orientation). Ideally would like to be able to adjust the settings, but if it is a pain can just put into requirements that your printer must be installed to COM1 and configured correctly.
2) send commands and read answers and send PCL code to the selected com port
As I understand I'll need to install something on the customer's machine to be able to talk to com port and get any settings. Just HTML+Javascript are not capable of doing that. Right?
I found RXTX library which seems to communicate to com port on most platforms. Can it be called from JavaScript or I still need to do a Java plugin? Are there technologies other than Java plugin that would solve the task?
The web-page will be used in different environment - platforms and web-browsers. We would like to minimize the number of customized solutions. Will Java allow us to do the same plugin for all environments with minimal customization?
If we require the user to install a plugin will the user be prompted with our credentials to confirm the installation? Will our web-site require higher trust settings?
Thanks for you help!
Well, I've had to do this in the past. Here is what I did and the circumstances
1) I knew that our customers were in a windows environment so I wrote win32 software to handle the printing.
2) I created a file format to be read by the win32 software that allowed me to specify print parameters and the label data. XML works ok for things like this.
3) My web app created a file in the format used by the win32 software and returned it to the user when they clicked on the "Print Labels" button. The file extension on the file returned was registered by the installer of the win32 software. That means when their browser looked for a default app handler for that file, it found my win32 software.
Bottom line is that the browser is handing off the printer communications to a native application instead of talking directly to the printer.
Obviously you need to be able to dictate your end user's are using a windows machine (or mac or whatever you can write native code). Associating a file extension with my program and returning that file to the user was the key to making the process work for me.
Whether your native code sends pcl directly to the printer or translates into a print api (like the win32 api as mine does) is another consideration.
Another approach you could consider is instead of sending PCL codes, you could create a PDF of the document. Format the document to the size and orientation of the label printer. The user will still have to hit the print button, but that might work. I have done this for printing to bar code printers and it works fine. Sometimes getting the margin and orientation correct is a little tricky, but that can be figured out.
Using Flex Builder 3 :
I have been getting this problem in every single debug launch for past few hours.
I used to get this earlier too, but once in a while, not with every debug launch.
I found out that flex debugger uses a certain 7935 port but I can't figure out
how to change it?
I remember getting this problem a few times. It might have to do with the Flex Profiler (I used to accidentally click that every now and then trying to launch the debugger).
If you start the Profiler and stop it too fast, it will add something to a file in your home directory that it shouldn't.
Check out /path/to/home/mm.cfg on your operating system (on mac, you can open it in textmate with mate ~/mm.cfg). The mm.cfg file stores some information about debugging in Flex
Then in that file, make sure this is the only content:
ErrorReportingEnable=1
TraceOutputFileEnable=1
If there's an extra line (can't remember/find it, something like PreloadSwf=/Users/[username]/Documents/workspace/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999), delete it.
Let me know if that fixes it.
Lance
Also just make sure you're not using Chrome. Flash Player debugger (at the time of writing this) does not work in Chrome.
This worked for me: right click on a SWF, select "Open with...", choose "Other...", select the Debug player and check the "Always Open With" checkbox.
Mac OSX / FlashBuilder4
Right click your launched flash application, either in the browser or standalone flash player and click on debugger if enabled and change the radio button from localhost to other machine and enter the ip 127.0.0.1 and you are free to debug. I guess the problem maybe from your host file.
Changing the browser from default (chrome) to IE worked for me
Similar to danjp - This started happening to me after a Flash Player automatic update. I simply reinstalled the debug flash players from the Adobe Flash Player download page and everything works as expected.
Make sure there is a swf file with the proper name in your bin-debug directory and that name matches the swf name specified in index.template.html file for the project.
I had replaced index.template.html file by mistake with a similar one from another project. When I tried to debug, I got this "Waiting for flash player to connect to debugger…" status till it timed out.
To me the problem was that internet explorer opened and showed a certification problem, if i didn´t continue this the debugger would show this error. If i continued on ie, no problem happens.
Allope,
I've recently bough Flex Builder 3 and I am completely dissatisfied with its reluctance to debug. It manages to debug a few times, but after that, it just doesn't want to "connect to the debugger".
Help?
There is no easy fix for this. You now have to join the rest of us waiting for Adobe to update Flex Builder with a fix they say they have.
You can find the long sad story here: http://bugs.adobe.com/jira/browse/FB-16153:
Basically, this is an issue that has been around for months. Adobe says it has a fix - however - they've not released that fix yet. Adobe reports it's a threading issue...
For the rest of us (waiting for this) - if you need to move forward you can:
A) Live with the problem (painful)
1) Note that in the bug text there are several attempts to work around this - sometimes people find ways to soften the issue - but no one reports a full fix
2) Note that people trying the LocalHost fix - sometimes report a gain in productivity - but in most cases they do not.
B) Switch SDKs from 3.2 (or 3.3) to 3.1 ---- No one knows why - but it fixes the problem (you can then include the SWFs you need for 3.2 directly
C) Develop on Mac [Not a smart ass answer - honestly - for whatever reason this bug is not on Flex Builder for the Mac]
Join the bug discussion - on Adobe's site - it's still active as people are still waiting for the fix.
Make sure you have the required Flash Debug Player.
http://www.adobe.com/support/flashplayer/downloads.html
If that doesn't help, you might have to re-install Flex Builder.
Are you running it on windows vista? It may be this issue:
http://blogs.msdn.com/expression/archive/2009/03/16/page-cannot-be-found-issue-when-previewing-via-expression-blend.aspx
The page is about silverlight, but I ran into the same issue a while back with the flex debugger, and had to add the following to my host file (which windows defender removed):
127.0.0.1 localhost
This is expanded more upon here:
http://circstar.com/FlashLabUnderground/?p=64
I've had similar problems but every-time it refuses to connect to the debugger i have justed downloaded and reinstalled the flash debugger and it works fine. It's a pain but until adobe do anything what can we do?
Have you the tried FlashDeveloper ide? you can build flex project with it and it quite frankly alot better than flex builder for code writing (not ui work).
Hope this helps
Jon
I'm not sure if you have the same symptoms, but I came across a similar problem on one of our development machines after installing Flex Builder 3. When trying to run our app in debug mode, flex builder took a long time to launch the app and eventually timed out, displaying some message about not being able to connect to the debugger.
I found this solution which worked a treat. While Flex Builder is trying to launch the app:
Go to the browser page containing your app/swf, right-click on the swf to bring up the flash context menu.
Select Debugger
Select Other Machine
Enter 127.0.0.1 in the text field
Click Connect and hopefully it works.
NB: If Flex Builder tried to launch the app in Firefox, the page never appeared. It was only when it launched in Safari that I was able to access the browser page and the flash context menu.