On 04.02.2006, at 21:23 Uhr, Andre wrote:
Well, just the ability to have some idea what the page would look like would be nice, after all there is a preview, and it shouldn't be too hard to accomplish I would think....
For my projects it would not be possible to get an idea how it would look like - for this you have rapid turnaround.
I have a project where, depending on the visitor and the displayed objects a choice between three different "PageWrapper" components and eight stylesheets (all working with every PageWrapper) has to be done at runtime. Currently this mostly changes behaviour and colors, but this is definitely not necessary the case.
And, after all: there is a reliable preview: run the application - you can work at every HTML part and binding while the application is running. Reload and you see your changes! For me this is far more helpful than a half-working solution in Webobjects Builder where no runtime information is involved.
Yes, I understand. I guess thats why they have 3 basic views, code, layout and preview.... I just wish preview actually previewed correctly.
Build components with styles and it works great. Everything that depends on runtime information or information from other components will not work. Yes, I know that this has nothing to do with real WebObjects development. And I don't believe that it is actually possible to have a working component preview without running the application.
cug -- PharmaLine, Essen, GERMANY Software and Database Development
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
