If I understand you correctly, your aim is to be able to rapidly prototype
processes to be reviewed by customers/POs etc. Wouldn't a tool like "Balsamiq
Mockups" or some other wireframing tool be more suitable for that purpose?
You also mentioned that the prototype should be created "by some one who do not
know how to program", with your solution this person at least needs to have
knowledge about Wicket Validators (including der Java package + class name +
parameters).
In my experience it is best to create a throw-away wireframe Mockup, and after
the customer agreed to it, you start coding this in HTML/JS/Java. I don't like
the idea too much to introduce additional complex logic into Wicket just fore
wireframing/mockup purposes (as mentioned, a person without Wicket knowledge
can't use this anyway).
Just my $0.02,
-Tom
On 29.05.2012, 15:03h Fernando Wermus wrote:
> Tom,
> Something else. I experienced the advantages to have mock up pages
> working in another company with Adobe Flex. These pages are added to the
> analysis and the clients could have in advance a vivid experience.
>
>
> Fernando Wermus.
>
> www.linkedin.com/in/fernandowermus
>
>
>
> On Tue, May 29, 2012 at 10:00 AM, Fernando Wermus <fernando.wer...@gmail.com
>> wrote:
>
>> Tom,
>> Thanks you for the review.
>>
>> The idea is that some pages are not implemented, tough they are declared
>> by some one who do not know how to program. A page implemented by us read
>> the form and instance all the components. We have wizards and they can
>> show the mock up to third workers. When they are accepted, the programmers
>> finish the work.
>>
>>
>> Fernando Wermus.
>>
>> www.linkedin.com/in/fernandowermus
>>
>>
>>
>>
>> On Tue, May 29, 2012 at 4:01 AM, Thomas Götz <t...@decoded.de> wrote:
>>
>>> I'm not convinced yet that this is really a good idea (how to deal with
>>> constructor arguments for validators? What is the advantage of having all
>>> in html effectively?) but as a starting point you could look at
>>> AbstractMarkupFilter (e.g. see how WicketRemoveTagHandler and other
>>> implementations work).
>>>
>>> To add your own MarkupFilter implementation, do the following:
>>>
>>>
>>> public class MyMarkupFactory extends MarkupFactory {
>>>
>>> @Override
>>> public MarkupParser newMarkupParser(MarkupResourceStream resource) {
>>> final MarkupParser markupParser = super.newMarkupParser(resource);
>>> markupParser.add(new MyMarkupFilter());
>>> return markupParser;
>>> }
>>>
>>> }
>>>
>>> and register MyMarkupFactory in your Application class:
>>>
>>> @Override
>>> public void init() {
>>> super.init();
>>> getMarkupSettings().setMarkupFactory(new MyMarkupFactory());
>>> }
>>>
>>>
>>> Cheers,
>>> -Tom
>>>
>>>
>>>
>>> On 28.05.2012, 21:25h Fernando Wermus wrote:
>>>
>>>> Hi all,
>>>> I was wondering if there is some solution already done like this:
>>>>
>>>> <input type="text" wicket:id="txtMyTextField" *
>>>> wicket:fieldtype="java.lang.String"*
>>>> *wicket:validators="com.mycompany.MyValidator1,
>>>> com.mycompany.MyValidator2"* />
>>>>
>>>> The idea is that HTML is allright for rendering, but It lacks some
>>>> behaviors. Therefore , instead of making up another markup, there is the
>>>> chance to decorate with wicket behaviors and validators.
>>>>
>>>> This is flexible enough to have differents specifications and
>>>> implementation to rich HTML.
>>>>
>>>> The idea we have at my work is to allow junior programmers to design
>>> mockup
>>>> pages for funcitonal analyst without adding a line of code. We were
>>> mocking
>>>> up pages with Adobe Flex and would like to have this behaviour with
>>> wicket.
>>>>
>>>> thanks in advance
>>>>
>>>> Fernando Wermus.
>>>>
>>>> www.linkedin.com/in/fernandowermus
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
