• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
(no subject)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(no subject)


  • Subject: (no subject)
  • From: "Paul D. Yu" <email@hidden>
  • Date: Fri, 5 Sep 2003 08:12:37 -0400

Xavier

This is my development approach with the tools.

1) Model the database design.
If new then
you'll need to select the database to use, e.g. OpenBase, Frontbase, Oracle;
you'll need to design every entity, attribute and relationship using EOModeller
In order to use EOModeler to your database, it has to exist and you use JDBC to connect
if database already exists then
you'll need to get the DBA permission to the database
use EOModeler to reverse engineer the database schema into EOModeler


Note: Try very hard not to use human meaningful attributes as primary keys to your entities, use instead an attribute like PK or ID

2) Use D2W to load test data into the database
Create new project in Project Builder, style of D2Web
Select the EOModel that you created in 1.
Launch the D2W application
You can now select an entity and add records to it,
Start with the lookup tables, e.g. postal code, items, etc.
You can use the Wizard (Assistant) to customize the D2W app to make the fields appear in a more logical order than the alpha order of D2W.
Using D2W, you should find that you've made modeling mistakes and will iterate back to EOModeler, and make corresponding changes in the database.
Once you have some good test data you are now ready to move on to the WebApp


3) I would not Use D2W to do a production app other than an Admin app.

4) Identify existing frameworks that will make the WebApp development even easier, e.g. Project Wonder and WOStas.

5) Create New WebObjects Application Project in Project Builder
Add the frameworks that you identified in 4.
Add the EOModel(s) from exercise 1. Yes you can have multiple EOModels in the same project, as long as you don't have naming conflicts at the EO level (I think).


6) I would build display components first with navigation. Since you have test data in the database already, once you've made connection, the data just shows up

6a) You can add Query components. I was always afraid of the EOQualifiers, but really it is not that hard.

7) Then I would add new data components.


     8)  Then  add edit components

    9)  Finally the deletion components.

10) since you're building a public site, you should only need deletion (removeObject...) in the Shopping Cart page.

Hope this helps.

Paul
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: Using WebObjects
  • Next by Date: Re: Using WebObjects
  • Previous by thread: Re: Where is the wizard? -- question about a tutorial
  • Next by thread: (no subject)
  • Index(es):
    • Date
    • Thread