api variables
api variables
- Subject: api variables
- From: Laetitia Orsini <email@hidden>
- Date: Mon, 04 Sep 2006 23:45:42 +0200
Hello,
I'm a newbie and after having developed my first "complex" webobjects
application I wonder if it was the right way to do it... The aim of the
application is to offer an interface to manage contents stocked in a
database. I have at the end many reusable web components with many api
variables. Within these api variables I send the edited objects and a
lot of booleans to deal with the layout with conditionals. Is it a
common way to do things in a web objects application ? Doesn't it look
like dirty javascript ?
What are the differences between api variables and non synchronized
variables ?
I also wonder if this kind of applications would be more quickly
implemented with Direct To Web. I've made some tests with Direct To Web
on my database model but it seams I'll still have a lot of work to
customize things if I want the same features as in my own application.
For example, if I have an entity Album that contains Singles, I would
like to be able to edit Singles just by clicking on a Single listed in
my edited Album. It seams it's not easy to customize relationships with
Direct To Web. If I have to freeze each component to customize
everything will it still take less time than if I do the entire
application by myself ? Is Direct To Web a common used tool to make
advanced interfaces to manage data or it is more for testing models ?
Thanks for your precious advices
Laetitia
_______________________________________________
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