Problems adding help bundle to Mac app in Xcode 5 - xcode

I'm trying to add a help bundle into my Mac app and the help viewer just can't seem to find it. I must be missing something.
Here is what I've done.
1: Created a help document in iWeb and exported it into a local desktop directory /Helpbook
2: Got a 16x16 png for an image and put it into /Helpbook (icon_16x16.png)
3: Copied the help director into the lprog directories for base and for en (base language)
4: Added those directories into the project
I know this worked because I'm seeing the (Base) and (English)
indicators within Xcode
5: Added plist entry CFBundleHelpBookFolder and set it to 'Helpbook'
6: Added plist entry CFBundleHelpBookName and set it to 'TestHelpBuild Help'
7: Went into the index.html file for both the base and English lprog versions and added:
meta name="AppleTitle" content=“TestHelpBuild Help">
meta name="AppleIcon" content=“Helpbook/icon_16x16.png">
dropped initial less than sign so you could see the tag in the post
added them within the tag along with another meta name
generated by iWeb
8: Ran Help Indexer over both Helpdesk directories
Got some errors but got a .helpindex file
Not sure what to think about that
Help Indexer didn't like the meta names added above
Worked ok without them
Clicking on the app menu entry to bring up 'app-name Help' shows me a box with no topics.
Anybody have any idea as to what might be wrong or areas that I might review more closely?
Here is the directory structure of the skeleton app I'm writing...
And here's the actual file structure via Finder...
Thanks in advance.

Well, I got it to work and I'm not sure how.
First thing is that I made the folder name 'TestHelpBuild Help' and made sure the index file meta name was also 'TestHelpBuild Help'. Then I put those two names into the plist and, lo, my help text appeared.
This meant deleting the help folder out of the app, copying the new folder into the .lprog folders, and then re-adding it back into the app via Xcode.
If you're having trouble with this, try taking the help out an app bundle with working help and knitting it as is into your app. This will help you get the procedure straight and give you some confidence that it can work.

Related

Duplicated Xcode project issue

I've duplicated my Xcode project - basically I'm creating an app with similar functionality but with different content. I duplicated the main folder and updated the names in the new project for the new app following a guide on Youtube that was on another thread, but when I updated the background of the storyboard for the new app, I've now seen it has changed the storyboard of the original app, so it must be using the same story file, or be linked somehow.
Please can someone suggest what I might have done wrong, or what I need to do when duplicating the project to avoid the same story file being used.
Please check the "Full path" of your file like shown below. Make also sure, that all your other files are linked correctly.

Xcode 6.4 CFBundleIconFiles

When I try to submit my app to the app store i get this error: "error itms-90032 invalid image path no image found at the path referenced under key CFBundleIconFiles"
The problem is that I ma not even using CFBundleIconFiles. A search of the entire app shows that it is not present. I just can't figure this out. Any help would be appreciated.
They are in AppIcon in Images.xcassets
Okay, but it sounds like you forgot to tell the app target about that. Edit the app target, go to the General tab, and make sure that the target knows where to find the icons:
You won't necessarily see CFBundleIconFiles in the plist that Xcode created for your project, but CFBundleIconFiles does get added to the Info.plist that is submitted to the App Store.
Your bundle icon files are automatically generated from your Asset Catalog icons and added to the bundle.
The details for the icons are contained in Images.xcassets.
Check to make sure that the Asset Catalog was not relocated, or the validation will fail, since the icons could not be generated.
I double checked everything you guys posted and everything is good, but still getting the error. I finally just decided to add iconfiles (ios5) to the plist and it worked when I tried to upload. I don't know why that did the trick.

Dreamweaver Spry Menu2 widget not working

apologies if this has been covered but I have searched for an answer on the internet.
I need to create a spry menu in dreamweaver. First I used sprymenu 1, but found that it didn't work on an ipad. So then I was directed to the SpryMenu2 widget.
My problem is that when I try to upload this onto my server I keep getting the error message 'SpryMenu.js requires SpryWidget.js!' I have checked, and these files are all uploaded.
Question: how do I fix this error, OR is there an alternative to create a spry-type menu that will work on an ipad?
many thanks for any help
I've recently encountered this. Make sure the file size of SpryWidget.js is the same size as the on in dreamweaver.
I first uploaded with Filezilla and got this error. Then I tried DW upload and still got the error. Lastly, I went directly to GoDaddy's FTP file manager and uploaded and it fixed the problem. For some reason it was being changed when uploading on DW or FZ. Now if I can only find out why mine won't work on mobile...
Best of luck

Joomla and JomSocial Error

I'm having problem with a client site. I'm not good with Joomla (we mostly do Wordpress), but one of my long-time clients asked me to move a site from another developer that never finished it, so I obliged. The problem is, everything is working great except for the Community page:
http://gettingripped.com/index.php/community
The only errors I'm finding are with the Facebook integration (which they told me the previous dev never finished/fixed). I'm really confused here...anyone out there have any ideas? It seems instead of showing the proper titles that Com_community_somethingElseHere is replacing everything.
Thank you guys in advance for your help!
Seems something is wrong with the en-GB.com_community.ini file.
Location: gettingripped.com/language/en-GB/en-GB.com_community.ini
I could not find the file in the above location!!!
Put this file in that folder and it will work!!!
If you can't find the file to put in the folder, create your own and place it there.. how? Well, google for this string as it is (including double quotes) "en-GB.com_community.ini" and open the first couple of results.
Then copy paste the displayed file content into your own ini file (name it en-GB.com_community.ini) and place it in your en-GB folder.
Load the page and it will show up as it should!

Remove a magento theme - Rollback to default

This is my first time working with Magento and here is what happend: I spent two days reading the documentation and tweaking the settings to fit my needs. I then installed this theme:
http://themeforest.net/item/decostore-magento-theme/1876494?WT.ac=category_thumb&WT.seg_1=category_thumb&WT.z_author=8theme
The problem is that the theme didn't work the way I was expecting and now I'd like to rollback to the default theme and completely remove everything added by this theme to my installation.
Unfortunately, I didn't backup the installation and database before I installed the new theme and I have no idea where to start.
Thanks in advance.
1. Switching back to default theme
Go to the admin area and then system > configuration > design
Change "Current Package Name" to 'default' and make sure all inputs under the "Themes" section are empty. This will return you to the default theme.
2. Completely remove everything added by this theme
I take it from your question that you are not using any form of source control. Might be an idea to look into this for the future :)
Magento 1.7 has introduced backup and rollback features so you may also want to check that out.
If this is the case, backup everything before you start removing files and directories as described below
Anyway, to completely remove all files and directories added when you installed the module, unfortunately it will simply be a case of manually finding the files and directories deleting.
The easiest way to do this will be to find the original source code you received when you purchased the theme and removing the corresponding files from your site. When removing directories be careful to only remove those specific to the theme - It will have been sent to you structured so that you can easily drag straight in to your web root - so will contain some other directories required by Magento, simply to give it the correct hierarchy.
At the very least there will be files and folders specific to the theme located in the following directories:
app/design/frontend
skin/frontend
js
and also most likely some more in the following:
app/etc/modules
app/design/adminhtml
app/locale
I know the result for this can be different for everyone, but in case someone else comes across my specific case, it was the N98 folder under app/code/community/N98 that caused the problem. Particularly their CustomerGroupCheckout plugin as shown here: https://github.com/amenk/N98_CustomerGroupCheckout
Removing the N98 folder brought back the configuration page.

Resources