• 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
Re: Project architecture
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Project architecture


  • Subject: Re: Project architecture
  • From: Miguel Arroz <email@hidden>
  • Date: Fri, 30 Mar 2007 00:26:28 +0100

Hi!

  Think on it like a desktop app.

WO builds applications, just like a desktop application. You cannot add windows to the application while it's running - unless your app is actually a "window creator", like Apple's Interface Builder! :) To add a window to a normal application, there's coding involved, and compilation. Just like in WO - to add a page, you need to change your app. WO is like a very very complicated application that receives HTTP requests and returns strings of HTML. As you cannot simply edit the binary executable of a desktop application, you cannot edit a WO App. You must change the source, and recompile.

Unless, like Interface Builder, your app *is* a content creator, a CMS. In that case, your app may create, as a side effect, HTML documents that are stored on the hard drive, and served by apache like any other normal HTML file. But even then you are changing your *site*, not your *WebObjects application*. In that case, the WO App would be the "editor" of the static site.

  Yours

Miguel Arroz

On 2007/03/29, at 23:56, David Holt wrote:

There's no "page" per se. You are creating instructions for your web app to assemble components and templates (and maybe data) into what would commonly be known as a "page". You tell your app to assemble these components by clicking a link or pressing a button, generally. This triggers an action in the application server.

I had a discussion with someone who wanted to protect the "pages" of a WebObjects application by creating a Realm on the folder. I had a hard time explaining that there is no folder full of pages to protect in the traditional web site development sense. Are you thinking in terms of static pages?

So yes, a programmer needs to become involved for any dynamically added content, whether it's data access, a swappable component, etc. The designer doesn't add pages. The templates that they provide are filled by the programmer with the functionality that is required. I hope that makes some sense.




"The world lies in the hands of evil
 And we pray it would last" -- Apocalyptica, Life Burns!

Miguel Arroz
http://www.ipragma.com




_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Project architecture (From: "Webobjects Developer" <email@hidden>)
 >Re: Project architecture (From: Guido Neitzer <email@hidden>)
 >Re: Project architecture (From: "Webobjects Developer" <email@hidden>)
 >Re: Project architecture (From: Robert Walker <email@hidden>)
 >Re: Project architecture (From: "Webobjects Developer" <email@hidden>)
 >Re: Project architecture (From: Robert Walker <email@hidden>)
 >Re: Project architecture (From: "Webobjects Developer" <email@hidden>)
 >Re: Project architecture (From: David Holt <email@hidden>)
 >Re: Project architecture (From: "Webobjects Developer" <email@hidden>)
 >Re: Project architecture (From: David Holt <email@hidden>)

  • Prev by Date: Re: CSS question and YUI
  • Next by Date: Re: Project architecture
  • Previous by thread: Re: Project architecture
  • Next by thread: Re: Project architecture
  • Index(es):
    • Date
    • Thread