Tuukka Norri avatar Tuukka Norri committed aca9b94

Changed pre elements to code and fixed #import <>s in documentation

Comments (0)

Files changed (2)

Documentation/html-support/documentation.css

 {
     font-style: italic;
 }
+
+code
+{
+    white-space: pre;
+}

Sources/BaseTen.h

  * \end{lstlisting} 
  * \endlatexonly
  * \htmlonly
- * <pre> #import <Foundation/Foundation.h>
- * #import <BaseTen/BaseTen.h>
+ * <code> #import &lt;Foundation/Foundation.h&gt;
+ * #import &lt;BaseTen/BaseTen.h&gt;
  *
  * int main (int argc, char** argv)
  * {
  *     }
  *
  *     return 0;
- * }</pre>
+ * }</code>
  * \endhtmlonly
  */
  
  * \end{lstlisting}
  * \endlatexonly
  * \htmlonly
- * <pre>[ctx connectSync: NULL];</pre>
+ * <code>[ctx connectSync: NULL];</code>
  * \endhtmlonly
  *
  *
  * \end{lstlisting}
  * \endlatexonly
  * \htmlonly
- * <pre>BXEntityDescription* entity = [ctx entityForTable: @"table" error: NULL];</pre>
+ * <code>BXEntityDescription* entity = [ctx entityForTable: @"table" error: NULL];</code>
  * \endhtmlonly
  *
  * BXEntityDescriptions are used to specify tables for fetches. For getting a specific 
  * \end{lstlisting}
  * \endlatexonly
  * \htmlonly 
- * <pre>NSArray* result = [ctx executeFetchForEntity: entity predicate: nil error: NULL];</pre>
+ * <code>NSArray* result = [ctx executeFetchForEntity: entity predicate: nil error: NULL];</code>
  * \endhtmlonly
  *
  * BXDatabaseContext's method <tt>-executeFetchForEntity:withPredicate:error:</tt> and its variations may 
  * \end{lstlisting}
  * \endlatexonly
  * \htmlonly 
- * <pre>for (BXDatabaseObject* object in result)
+ * <code>for (BXDatabaseObject* object in result)
  *{
  *    NSLog (@"Object ID: %@ column: %@", 
  *           [[object objectID] URIRepresentation], [object valueForKey: @"column"]);
- *}</pre>
+ *}</code>
  * \endhtmlonly 
  *
  * Since BXDatabaseObject conforms to \em NSKeyValueObserving, methods <tt>-valueForKey:</tt> and 
  * collection of objects that reference the table in a foreign key. They key used is the other table's name.
  *
  * Consider the following example:
- * <pre>CREATE TABLE person (
+ * <code>CREATE TABLE person (
  *    id SERIAL PRIMARY KEY,
  *    firstname VARCHAR (255),
  *    surname VARCHAR (255)
  *    id SERIAL PRIMARY KEY,
  *    address VARCHAR (255),
  *    person_id INTEGER CONSTRAINT person REFERENCES person (id)
- *);</pre>
+ *);</code>
  *
  * Lets say we have two objects: \em aPerson and \em anEmail which have been fetched from the person and email
  * tables, respectively. <tt>[aPerson valueForKey: @"email"]</tt> will now return a collection of \em email objects. 
  * <tt>[anEmail valueForKey: @"person"]</tt> will return a single \em person object.
  *
  * If we modify the previous example, we get a one-to-one relationship: 
- * <pre>ALTER TABLE email ADD UNIQUE (person_id);</pre> 
+ * <code>ALTER TABLE email ADD UNIQUE (person_id);</code> 
  * Now both <tt>[aPerson valueForKey: @"email"]</tt> 
  * and <tt>[anEmail valueForKey: @"person"]</tt> will return a single object from the corresponding table.
  *
  * both tables' primary keys. It needs to be BaseTen enabled as well.
  *
  * Another example: 
- *<pre>CREATE TABLE person (
+ *<code>CREATE TABLE person (
  *    id SERIAL PRIMARY KEY,
  *    firstname VARCHAR (255),
  *    surname VARCHAR (255)
  *    person_id INTEGER REFERENCES person (id),
  *    title_id INTEGER REFERENCES title (id),
  *    PRIMARY KEY (person_id, title_id)
- *);</pre>
+ *);</code>
  *
  * Lets say \em aPerson has been fetched from the person table and \em aTitle from the title table. 
  * In this case, <tt>[aPerson valueForKey: @"title"]</tt> will return a collection of title objects 
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.