• 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: Picking up .wo changes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Picking up .wo changes


  • Subject: Re: Picking up .wo changes
  • From: email@hidden (Anjo Krank)
  • Date: Fri, 6 Jun 2003 11:05:03 +0200
  • Xx-reply-to: email@hidden

Am Freitag, 06.06.03 um 08:41 Uhr schrieb Anders F Bjvrklund:

It all started when I had modified a component and was looking for the "reload definition"
method on the component... It seems that the current caching is either never or forever.

I get the impression that you want to change .wo files in the deployed application? You can do this by overriding "template", but I wouldn't do this.


WO is *not* PHP. You don't go along and edit pages on your live server. One may argue if that can be streamlined, but in general, a WO app is and Application, not a distinct set of pages. Normally you do more than just edit the .wo (changing code etc) and you simply can't do this reliably on a live server. The normal way to cope with this is to add more quality control up front so you don4t get used to this edit-the-live-app thing.

I consider this partly bad, partly good: for tiny changes like editing some text, it seems overkill to have to restart the app. But on the other hand, in my experience it is better on your health and the discipline of your customer if you get them used to a more release-oriented workflow ("hey, add this edit box over here right now" ... "what do you mean 'that's not possible'? You also changed that text and those links the other day":)

IMO, WO is a rather poor tool for building web sites because it integrates poorly with how a normal web site is supposed to work. But It is the arguably the best tool for building web *applications*, though. But when building apps, you also do things like write automated tests, version control, bug tracking, releases etc.

I just thought it would have been nice if WebObjects could pick up changes
in the templates (or in the java code or in the database) in an easy manner...

For the "java" part, you can look at my ERXCompilerProxy from Project Wonder. It recompiles classes on the fly. I don't know what you mean with "pickup changes in the templates"? WO does this already...and what is "in the database" supposed to mean?


Cheers, Anjo
_______________________________________________
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.

  • Follow-Ups:
    • Re: Picking up .wo changes
      • From: Anders F Björklund <email@hidden>
References: 
 >Re: Picking up .wo changes (From: Anders F Björklund <email@hidden>)

  • Prev by Date: Re: Picking up .wo changes
  • Next by Date: Re: Picking up .wo changes
  • Previous by thread: Re: Picking up .wo changes
  • Next by thread: Re: Picking up .wo changes
  • Index(es):
    • Date
    • Thread