I was going through lena's tutorial and now I gotta use some plugin, but it doesn't seem to work, (Lena's 2nd tutorial), I created a "plugins" folder and copied the files to that directory, but it's still not working, I was searching in google for an answer for like an hour, and haven't found any solution for that.
Anyone has succeed putting that plugin?
Thank you.
Do you use OllyDbg v1.10 ? Because the current 2.01 was not supporting plugins until alpha4, and is not backward compatible with the existing plugins for 1.10.
Also, did you set the plugins folder in ollydbg settings ? Look in Options / Appearance / Directories tab page.
Related
I bought this template but I don't know how to edit its files on my computer. It seems the file extensions are .tpl
How can I edit them like HTML files and then upload them to the server?
Whmcs (a webhost and billing manager software) uses the .tpl files to allow for customisations. There is no way to edit them like html, that I know of.
Tpl files basically need a bit of trial and error in modifying them.
The best way would be to install a trial version of Whmcs or if you have it already installed, perhaps install a second development version (you can apply for a free development license from whmcs).
Then use a txt editor like notepad++ (or another html editor software) to edit the tpl files - then upload to your test site - tweak and repeat as needed... yes, it's not user friendly - but that's whmcs for you.
The whmcs documentation gives a helping hand too.
I have before worked with Python extensions and configured PIP to point to our artifactory in my company, now I would like to do the same with VS Code.
I would like to be able to change the path of where VS Code downloads its extensions, to our own artifactory.
We want to control what users have which extensions, and don't want them to be able to download freely.
Can anyone please help me to which file or configuration I can make to point it to another site?
This is not possible at the moment. There is already an issue concerning this feature https://github.com/Microsoft/vscode/issues/21839 .
You can however disable the Gallery as mentioned by Thally by removing the "extensionsGallery" part from VSCode\resources\app\product.json.
And offer the vsix you want your users to have via any differnt path for selfservice or even just preinstall them under %USERPROFILE%\.vscode\extensions.
VSIX can be downloaded from the store for offline use as Mentioned by t3chb0t in his answer to how-to-install-vscode-extensions-offline
If you are still running into this, an updated answer is to use https://github.com/LOLINTERNETZ/vscodeoffline
So far it has worked well for us in a completely offline environment. The only gotcha that we have run into is that some extensions attempt to reach out and download additional things from github or elsewhere when first run which does not work if you are offline like in my situation. However, if you are online and simply want to control which extensions are available, I think this project will do the trick for you.
Anyway, by adding a product.json file to their user directory or setting env vars, your coworkers will be able to change the marketplace again: https://github.com/VSCodium/vscodium/pull/674
Xcode 4.5.2 Mountain Lion , Mac App
I follow the documentation precisely. The Help Folder and its subfolders are added to the projects /Resources folder and appears blue in color.
Folder References were added by xcode if necessary.
Whether I view the HTML file in Xcode or externally in a text editor, I see the new version of the file.
Inside the app, the Help pages all display, the anchors work, but the pages are older versions.
A particular file that is not being shown with the latest version is DgxFiles.html
It is located in the scheme below as ../pgs/DgxFiles.html.
When I access Help inside the app, I see an older version of the HTML file. It seems the old help files are cached somewhere.
App's Info.plist has
<key>CFBundleHelpBookFolder</key>
<string>HungryMeHelp</string>
<key>CFBundleHelpBookName</key>
<string>com.DrummingGrouse.HungryMe.help</string>
The Landing page,HungryMe.html has:
<meta name="AppleTitle" CONTENT="com.DrummingGrouse.HungryMe.help"/>
The folder I drag into the project is named: HungryMeHelp
The Help Folder structure is:
HungryMeHelp/
Contents/
Info.plist
Resources/
shrd/ <shared artwork>
English.lproj/
HungryMe.html <title page>
HungryMe.helpindex
pgs/ <the rest of the content pages>
sty/ <style sheets, generated list template>
scrpt/ <scripts>
I have:
0. Deleted /HungryMeHelp and re-added it.
1. Cleaned the project.
2. Reloaded Xcode
3. Rebooted Mac
Trash the following files in your Home > Library > Preferences folder
com.apple.help.plist
com.apple.helpui.plist
com.apple.helpviewer.plist
Trash the following folders in your Home > Library > Caches folder
com.apple.helpui folder
com.apple.helpdata
com.apple.helpd
com.apple.helpviewer
What am I missing?
Thanks for reading. Mark
I found answers to my Apple Help Viewer Cache questions here:
http://www.cocoabuilder.com/archive/cocoa/312037-updating-an-app-help.html
http://macergun.blogspot.com/2011/06/dealing-with-help-viewer-cache.html
I found the posting below at cocoabuilder.com
As a result, I deleted existing copies of the app from my system.
The Help System updated immediately thereafter!
On Dec 13, 2011, at 5:17 PM, Graham Cox wrote:
With each update of our app, we typically change the help book. We're finding that the system is very poor at recognising this and caches old versions of the help which causes new stuff we add to be unavailable. While I can manually trash the help caches and force an update, this isn't something we can ask or expect of our users.
Search the archives, and you will discover that you are likely experiencing a well-known issue that has been around for a very long time. It typically only affects the developer, not your users. It is especially annoying to the developer if another, older version of the application is still on your computer, in the Applications folder or perhaps in the form of earlier build products that are still sitting around, because then trashing the help caches and forcing an update won't necessarily stop the system from using the old version of your Help folder in an older version of your application.
When I am working on my Help folders, I routinely compress all older versions of the application into zip files for the duration, and I trash the Help caches before every test.
The typical user trashes the old version of the application when they install the new version, and all is well.
--
Bill Cheeseman -
I just get mad about the helpd cache while developing a help book as anything I found on the web, including what is found here, about clearing the cache of 'helpd' turn to not work anymore (at list on MacOS 12 - Monterey).
I found what do clear looking at files opened by HelpViewer Networking process while my help (not updated) was opened using Apple 'Activity Monitor.app'.
It turns that the cache is now built in the Container directory within your Library Folder.
~/Library/Containers/com.apple.helpviewer/Data
In this directory you find your cache help files in the form of
.*
e.g.
com.johnsmith.johnapps.com.johnsmith.johnapps.help*1.0.help/
doing a rm -rf of this directory will clear the help cache used by HelpViewer for the help book you are developing
You still need to kill the helpd daemon for this to work.
e.g.
rm -rf com.johnsmith.johnapps.com.johnsmith.johnapps.help*1.0.help/
pkill helpd
Note that changing the version of your help book in the plist file does not help.
In my case even if I increase the version of the plist help book (see Authoring Apple Help) , the cache generated still have version 1.0 even if it has been regenerated after the version update.
I am developing an NPAPI Firefox plugin and I have a question.
I need to load a third-party DLL (such as D:\mydll.dll), but on some computers mydll.dll is not in the system path or in c:\windows\system32 and I get loading errors.
Here is the code:
SetCurrentDirectory ("d:\");
m_hModule = LoadLibrary ("mydll.dll");
LoadLibrary returns 126. I checked with DEPENDS.EXE to view the dependent modules and everything looks fine. I do not know what the problem is.
Another problem is that I want the plug-in to work in Safari (my safari is version 5.17). I copy it into Safari's Plugins directory and it tells me it cannot find the plug-in. I want to know how to solve this.
Thank you, and please excuse my poor English.
Setting the current directory will not always work when in a plugin because you don't own the process. The command that you want is SetDllDirectory.
SetDllDirectory("D:\");
m_hModule = LoadLibrary("mydll.dll");
Of course, I don't recommend that you ever assume a DLL is in the root of the drive =] What I would do is put the DLL you need in the same directory as the plugin DLL and then you can get the path of the DLL using GetModuleFilename.
For installing, rather than putting the plugin in the plugins/ directory in the firefox (or safari) directory you should install it through the windows registry. This will make it visible for firefox, chrome, and safari.
You may want to consider using FireBreath instead of implementing the NPAPI interfaces yourself; it takes care of most of the tricky parts and leaves you free to focus on the important parts of your plugin.
plz anyone can tell me how to open our project at Appmobi XDK. i am facing a problem that i have install it but its not allow me to open projects. when i tried to open my project a message comes unable to open a project.
now i need your help guys.
Thanks
The very first thing you need to do is to go to xdk.appmobi.com (in google chrome) and download/install our xdk. (Need Java installed also)
During the install you will need to set a default appmobi directory. This is where your app files will be stored.
Create a new app from within the XDK. You can then click the edit the source code button in the tool bar to edit your code. Here you can update the file with your own code.
You can check out a video that explains the xdk at http://www.youtube.com/watch?v=MWV8kOJlGmc Some things might have changed visually with the current version of the XDK, but essentially its the same.
Some things have changed/moved around the screen since we made the video, but essentially its functionally the same.
Check it out as it will give you tips/how To's to using the XDK.
Also, posting in our forums (forums.appmobi.com) will get your questions answered sooner!