Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix broken headings in Markdown files #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix broken headings in Markdown files #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
#Positronic Net
# Positronic Net

Positronic Net is an attempt to add some MVC flavor to the process of
developing Android apps, and to reduce the amount of boilerplate code
Expand All @@ -18,11 +18,11 @@ Available documentation includes:
There are also two simple sample apps bundled with the library (as
SBT subprojects).

#Features
# Features

What's in the package right now includes the following:

##Event handler declarations in a style reminiscent of jQuery:
## Event handler declarations in a style reminiscent of jQuery:

listsView.onItemClick { (view, posn, id) => viewListAt( posn ) }

Expand All @@ -37,7 +37,7 @@ premixed into `PositronicActivity`, `PositronicButton`, and so forth.
don't have a Positronic shorthand for something, or just don't like
it, the standard API is fully available.)

##A fairly simple, lightweight ORM
## A fairly simple, lightweight ORM

Designing an object-relational mapper for Android means dealing with
some unusual constraints. Most notably, it's generally good practice
Expand Down Expand Up @@ -71,7 +71,7 @@ can include ORM-managed records going either way, which are considered
to be immutable snapshots of the mutable persistent state that's managed
by the ORM --- or requested changes to that state.

###Basic ORM usage
### Basic ORM usage

To try to make that clear with a concrete example: Imagine we have
TodoItems which have a task description, and a "done" state.
Expand Down Expand Up @@ -113,7 +113,7 @@ and similar requests, on the thread that invoked them --- so if an
activity does a `Fetch` on its main UI thread, it's safe to manipulate
UI components within the `Fetch` body.)

###"Change notification" framework
### "Change notification" framework

It can still be bothersome to have to explicitly re-query the ORM
to refresh displays when relevant state changes. If you have an
Expand Down Expand Up @@ -157,7 +157,7 @@ If you're doing something idiosyncratic, the underlying machinery
is also available to be used directly, e.g. by `AddWatcher` and
`StopWatcher` requests.

###One-to-many associations
### One-to-many associations

The ORM also currently has some support for many-to-one and
one-to-many associations. An app which manages multiple to-do
Expand All @@ -184,7 +184,7 @@ Full examples of this can be seen by viewing the todo-list sample app
in the `sample` directory; the above has been (slightly) simplified
excerpts.

##Miscellaneous shorthands
## Miscellaneous shorthands

The library also provides alternate overloads for a lot of standard
framework APIs (usually to give them functional arguments instead of,
Expand Down