Sorry that my attemp to explain misled you thinking, that everything
should be one file.
Trying again...
Taking the case of a panel. I still think working on different aspects
of the file (design and logic) can be a non-conflicting business. From a
desinger's point of view, the markup file, that corresponds to the
panel's Java class, is a well-formed and completely self-contained HTML
page with all resources included to make the panel appear the way it
should and can be statically opened in a browser as it is (not only at
runtime).
Next, the developer adds the <wicket:panel> tag just around the section,
Wicket should apply the logic.
So you as a developer have not necessarily anything to do with what is
changed aside/inside/around the <wicket:panel>. So design and logic
should evolve (virtually) independent from each other.
I admit, this may lead to an amount of redundant markup code in the
repo. But it will be stripped of at runtime and the page wicket delivers
is as compact as it is needed.
Am 29.01.2014 11:47, schrieb Steve:
I'm not sure how the MarkupParser would handle multiple <wicket:panel>
tags in one file? How would it identify which instance of
<wicket:panel> belonged to which java Panel?
On 29/01/14 20:44, Lucio Crusca wrote:
In data mercoledì 29 gennaio 2014 10:57:59, tho...@jarnot.de ha
scritto:
Is there really a need of splitting up the markup files?
Well, I don't know, I mean, I've always split them up because a Wicket
webapp
is typically a collection of {1 java file, 1 html file by the same
name} tuples.
However I have to admit that I had already broke that pattern over
time and it
actually worked (e.g. derived java class but html file only for the
base
class).
Do you think it's feasible to drive that practice to the extreme of
having
only 1 html file per page and several derived java classes? I'm afraid
that
model would suffer from a serious impedance mismatch against the OOP
pattern,
because you can't have one single MyAppPage java base class, but you
are
forced to create several java classes for each HTML page and use just
panels
inclusion in each one. I'm not saying that's not possible, but seems
to me
it's not very OOP-ish. Am i wrong?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
