Re: Incorporating a scanned form into a user interface
Re: Incorporating a scanned form into a user interface
- Subject: Re: Incorporating a scanned form into a user interface
- From: "David Wilson" <email@hidden>
- Date: Thu, 22 May 2008 21:02:41 -0400
On Thu, May 22, 2008 at 8:53 PM, Hernandez & Associates, Inc
<email@hidden> wrote:
> Creating program for office administration use, I would like to use an
> employee information (paper) fill in the blank form consisting of six (6)
> pages, text fields, numerical fields and check boxes as the user interface
> so that the office administrator will be familiar with the layout and
> information required, allowing the office administrator to fill in each
> field, the same way office administrator would if they were filling out the
> paper form and be able to scroll down to the next page as needed (6 pages).
> The information placed in the Text/Numerical and check box fields will be
> stored in the employee file similar to an address book with more information
> in it.
1) Create a data model (core data, NSDictionary, whatever) to describe
the data being entered.
2) Scan your pages as images.
3) Create a view in interface builder for each page.
4) For each page, set up text fields/check boxes/etc in the
appropriate locations in the views. Bind the input fields to the
appropriate keys in your data model.
5) Add each page as a subview of a tab view.
6) Place the tab view in a document window.
7) Save or Load just writes out the data model or reads into the data
model, respectively. I can't offer much help here without knowing how
you're currently storing stuff. If you're not and this is all new, I
strongly recommend doing the data modeling in Core Data - all
employees and their associated data would be contained in one big core
data file (XML if you're a small company, SQLite if larger). Core Data
would then handle the saving/loading for you.
It's hard to give more than an overview without knowing more details.
Look up the docs for the tasks above and it should get you started.
That said, Core Data has some fairly hefty knowledge requirements- if
you don't understand key-value coding and paths, or if you don't
understand bindings, or if you don't understand MVC and dealing with
object controllers and the like, you can get yourself into a bad
position very quickly.
--
- David T. Wilson
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden