XcodePages 0.0.5 → 0.0.6

Sign up to get free protection for your applications and to get access to all the features.
data/README.rdoc CHANGED
@@ -61,6 +61,19 @@ settings provided therein *override* XcodePages defaults. This may include the
61
61
  default. You need to comment out or delete the setting to allow XcodePages to
62
62
  auto-generate the appropriate default.
63
63
 
64
+ ==== When Pushing to GitHub Pages
65
+
66
+ When your project uses GitHub for version control, you can conveniently publish
67
+ the HTML documentation pages by pushing the HTML to branch +gh-pages+. However,
68
+ is a caveat when doing this.
69
+
70
+ You will need to touch and commit +.nojekyll+ in the root of your branch.
71
+ Otherwise, the Doxygen pages will not appear. GitHub uses {Jekyll, a blog-aware
72
+ static site generator}[https://github.com/mojombo/jekyll] that monkeys around
73
+ with underscores within paths. Unfortunately, Doxygen uses underscore in path
74
+ names as delimiters, by default. You can switch this off with +.nojekyll+ or
75
+ tell Doxygen to use short names using +SHORT_NAMES = YES+ in your +Doxyfile+.
76
+
64
77
  === Step 4
65
78
 
66
79
  You can now switch target to +MyProjectPages+ and hit Build (Cmd+B) to compile
@@ -75,6 +88,13 @@ set.
75
88
  == Benefits
76
89
 
77
90
  * Takes the "fiddle" out of fiddling with Doxygen.
91
+
92
+ There is naturally more documentation, and better too, when generating the
93
+ documentation is _easy_. Would it not be easy if you could just type some
94
+ Doxygen comment blocks in Xcode, press Cmd+B to build the documentation and
95
+ then immediately read it within Xcode's documentation? Try out
96
+ XcodePages[http://rubydoc.info/gems/XcodePages]! It _is_ that easy.
97
+
78
98
  * You can easily identify undocumented classes and methods.
79
99
 
80
100
  Warning messages output by Doxygen make this possible. After building your
@@ -82,6 +102,10 @@ set.
82
102
  elements within your project. Press the Cmd+\' (Jump to Next Issue command) to
83
103
  navigate through the undocumented code.
84
104
 
105
+ Note, however, that you may still need to reload (or even restart Xcode) if
106
+ your major documentation sections change. Xcode document viewer appears to
107
+ cache them.
108
+
85
109
  == Examples
86
110
 
87
111
  You can find examples of projects using XcodePages here:
@@ -1,3 +1,3 @@
1
1
  module XcodePages
2
- VERSION = "0.0.5"
2
+ VERSION = "0.0.6"
3
3
  end
data/lib/XcodePages.rb CHANGED
@@ -104,7 +104,6 @@ module XcodePages
104
104
  SOURCE_BROWSER = YES
105
105
  HTML_TIMESTAMP = NO
106
106
  GENERATE_LATEX = NO
107
- HAVE_DOT = YES
108
107
  EOF
109
108
 
110
109
  # Let the user override the previous defaults by loading up the Doxyfile
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: XcodePages
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.5
4
+ version: 0.0.6
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -9,11 +9,11 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2011-12-23 00:00:00.000000000 Z
12
+ date: 2011-12-31 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: rake
16
- requirement: &70133083833920 !ruby/object:Gem::Requirement
16
+ requirement: &70105779299960 !ruby/object:Gem::Requirement
17
17
  none: false
18
18
  requirements:
19
19
  - - ! '>='
@@ -21,10 +21,10 @@ dependencies:
21
21
  version: '0'
22
22
  type: :development
23
23
  prerelease: false
24
- version_requirements: *70133083833920
24
+ version_requirements: *70105779299960
25
25
  - !ruby/object:Gem::Dependency
26
26
  name: activesupport
27
- requirement: &70133100116420 !ruby/object:Gem::Requirement
27
+ requirement: &70105779299540 !ruby/object:Gem::Requirement
28
28
  none: false
29
29
  requirements:
30
30
  - - ! '>='
@@ -32,7 +32,7 @@ dependencies:
32
32
  version: '0'
33
33
  type: :runtime
34
34
  prerelease: false
35
- version_requirements: *70133100116420
35
+ version_requirements: *70105779299540
36
36
  description: ! "\n Helps you publish HTML web pages on the Internet somewhere appropriate,
37
37
  e.g.\n on GitHub via the gh-pages branch feature.\n\n Works for Objective-C
38
38
  projects built using Apple's Xcode IDE and\n consequently focuses on documentation