Le 09-02-25 à 06:49, Anders Peterson a écrit :
> Anjo Krank wrote:
>> Am 25.02.2009 um 09:09 schrieb Anders Peterson:
>>> The best part WOBuilder - why I was reluctant to abandon it - was
>>> that hybrid/conceptual component view (in combination with the
>>> drag-and-drop binding functionality). It was neither a wysiwyg
>>> preview nor an html (outline) view/editor, but it gave me a very
>>> good idea about what my page would look like and what the code
>>> looked like.
>> Except for tables, this always looked pretty ridiculously wrong and
>> is pretty much worthless with "modern" layouts that use style sheets.
>
> I maintain (incl. adding new functionality) old applications. They
> contain components build the old way using the old tools. Some of
> the components have become very complex, exploiting the possibles of
> the old techniques and tools to the max. I worry about how I will be
> able to maintain these applications/components in the future. I'd be
> very surprised if I was the only one in this situation.
I must admit that the WO Component editor is a pain for those old
applications. We also have old apps with > 20 tables and multiple
WOConditionnals and those not-so-useful binding names that WO Builder
was creating (ie : "String1", "Conditionnal1", etc.). In a certain
way, WOLips enforce best pratices so that you start your new projects
in a good way, and it's excellent at that. But it's certainly doable
to work with old apps in WOLips, and it will encourage you to at least
change the binding names to something you can identify. Just renaming
the bindings will help you a lot.
This archive was generated by hypermail 2.0.0 : Wed Feb 25 2009 - 07:20:13 EST