Where (what specific folder location) is the default XSLT for viewing XML in IE10 and in firefox? - firefox

I know that in firefox I can see the default xslt if I type in chrome://global/content/xml/XMLPrettyPrint.xsl BUT where is it in my computer? The actual file?
Where is it for IE10?
TIA

I think Mozilla uses a .jar file to pack such components but uses the file suffix .ja so that you don't find the stuff so easily :). So the file C:/Program Files (x86)/Mozilla Firefox/omni.ja is a jar package and in there you have the directory /chrome/toolkit/content/global/xml/ with the file. Of course the path C:/Program Files (x86)/Mozilla Firefox/omni.ja can be different depending on OS and your Firefox installation.

Related

Access Qt resource files in VS 2017 with CMake

I am having trouble accessing qt resource files in a VS 2017 project with CMake. I was able to access the qrc files using Qt Creator. I have the following questions:
Where do I put the resource files? Preferably I would like to put resource files in the root directory. I have tried to put the files in the root director and in the directory they will be called.
What changes I should make to the CMakeLists.txt files?
How can I refer to the resource files? I have tried all the instruction I can find on internet. But none of them seem to work. For example I have tried: ":/prefix/filepath/filename" or ":prefix/filepath/filename".
Thanks a lot!
You can put your .qrc file where you want, for my project I make it on /res folder but is your choice. You can add your files on the resources edit manually the .qrc file as a normal xml file. Here a simple example:
<RCC>
<qresource prefix="/menu_img">
<file alias="cancel_img">icons/cancel-512.png</file>
<file alias="open_img">icons/folder-512.png</file>
<file alias="print_img">icons/printer-512.png</file>
</qresource>
</RCC>
In this resource files the images are inside the folder icons and the .qrc is outside.
After that your .qrc file is ready (assuming that you use qt5) you must add to your CMakeList.txt this line:
qt5_add_resources(PROJECT_RESOURCE path_to_rosource_file/resources.qrc)
then on your target you must add this rosource:
add_executable(
${TARGET_PROJECT}
${PROJECT_SOURCES}
${PROJECT_HEADERS}
${PROJECT_RESOURCES})
Now your resources is available inside your project as usual :/menu_img/cancel_img

android-studio project error .zip extract: path too long

I just recently tried to extract a .zip file that contains a android-studio project from my usb key. I moved the .zip file on my desktop and then used the 'extract-all' from windows. During the extract, I get this message:
Now If I would change the name of the class, it would probably give me errors when I build gradle. Is there a way to simply override this error message ? Is this a windows issue or is it an android-studio problem (naming files too long)?
So far, I've tried extracting each file but it didn't work. I've also tried it on other computers and its the same result... Any ideas on how to proceed ?
Try using 7zip link, this will likely solve your problem!

Working directory vs output path in visual studio

What is the difference of the working directory vs the output path in visual studio?
Is it bad to set both setting to the same directory like '....\bin\'
By default they are the same. Assuming you're debugging some application it will be bin\debug.
Output Directory is where your output files goes. By default, Visual Studio builds each project in a solution in its own folder inside the solution. You can change the build output paths of your projects to force all outputs to be placed in the same folder
Working Directory is the location which Specifies the working directory of the program being debugged. It is the default place in which a program is looking up it's files. Normally the working directory is the directory the application is launched from \bin\debug by default.
So every opened file will be opened relative to the working folder.Let's say if you have an application installed in c:\myapp with all lib files in the same directory then you will set your working directory to myapp folder and you can do so from project properties.
By default, working directory is the output directory. Both can be changed, you can set another directory or common directory for all projects for output directory that determines a relative path for the output file that might be an executable or a static library.
Working directory also provides a relative path to put files that are used by the program. You can put a log file into a place that you can use its directory as a relative path in the code instead of absolute path. If your working directory is myproject\src and your log file is in myproject\src\log\log.txt then you can open or write the log file with log\log.txt in the code rather than c:\blabla\myproject\src\log\log.txt.

how to get executable application from .bin files

whene I extract a win32 application file.exe with (ressourcextract) I got .bin + .bmp and .txt files.
after some changes in one .bin file how to get my .exe application again , what must i do ? compile or assembly and how ?
thanks in advance
possible dupe of: Replacing Bitmap Resource in exe
You can undoubtedly find a tool to do so, but since this is a programming forum, these are the main APIs you would use:
BeginUpdateResource, UpdateResource, and EndUpdateResource.
Sample
For additional reference/information, here is the spec for the PE file format:
http://msdn.microsoft.com/en-us/library/windows/hardware/gg463119.aspx

STRINGS_FILE_OUTPUT_ENCODING not working for me in Xcode 3.2.5

The STRINGS_FILE_OUTPUT_ENCODING build setting in Xcode 3.2.5 isn't working for me.
My source code, including the .strings files, are UTF-8. I want the built application to have the .strings files stored as UTF-16.
The Project | Edit Active Target "Build" tab (there's only one target) is set up as follows:
"Convert copied Files" (APPLY_RULES_IN_COPY_FILES) is checked.
"Strings file Output Encoding" (STRINGS_FILE_OUTPUT_ENCODING) is set to UTF-16.
But the .strings files in the .app that is built are still UTF-8.
Am I wrong about the purpose of STRINGS_FILE_OUTPUT_ENCODING? Or am I doing it wrong? Or what?
For anyone else with this problem:
This was caused by not properly registering the .strings files in Xcode as being for translations. The structure of the localization folders was wrong. When I corrected the structure and properly registered the .strings files for localization, everything worked.
(This was a project I inherited.)

Resources