Hi,
Check http://wicket.apache.org/
The latest API docs are at
http://ci.apache.org/projects/wicket/apidocs/6.0.x/ . I agree that 6.x
would be more correct link name.
The latest released version is
http://www.apache.org/dyn/closer.cgi/wicket/6.3.0.
6.4.0-SNAPSHOT is the current development
Hi,
InMethod Grid is more smarter. It supports column reordering, resizing,
better Ajax support. But it is no active maintainer at the moment.
Different community members provide patches when they need fixes but that's
all.
It is also based on Yahoo UI v.2.
On Tue, Nov 27, 2012 at 10:45 PM,
Hi,
You can add two different bundles. In DEV mode the bundle will contain A, B
and C and in PROD mode just A and D.
In your pages/panels you have to add only A. Wicket will serve the proper
bundle depending on the mode.
On Tue, Nov 27, 2012 at 10:54 PM, kamiseq kami...@gmail.com wrote:
hi,
Hi,
On Wed, Nov 28, 2012 at 9:14 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
InMethod Grid is more smarter. It supports column reordering, resizing,
better Ajax support. But it is no active maintainer at the moment.
Different community members provide patches when they need fixes but
Hi,
Let me see if I can find some time to give it a shoot this weekend. Drag
and drop and column re-size should not be that difficult to rewrite in
terms of jquery dd.
On Wed, Nov 28, 2012 at 9:25 AM, Martin Grigorov mgrigo...@apache.orgwrote:
On Wed, Nov 28, 2012 at 9:22 AM, Ernesto Reinaldo
Hi there,
I'm currently implementing a panel that is used for viewing and editing of some
entity. I wonder if there is an elegant solution for this.
The situation:
all my view/edit panels have a common abstract parent class (Panel), providing
some general markup, i.e. I'm using wicket:extend
Hi Thomas,
Bean edit panel is useful in this sort of scenarios.
http://londonwicket.googlecode.com/files/LondonWicket-BeanEditor.pdf
It is quite old, maybe there is a newer/better option.
Best regards,
Michal Wegrzyn
-Original Message-
From: Thomas Götz [mailto:t...@decoded.de]
Hi,
thank you for idea again :) But I have another question now. This textfield
belongs to wicket panel. And I don't really understand where should I place
script/script tags. Is it enough to place it in the panel.html or
should I define it in some other location?
Dmitriy
2012/11/27 Sven Meier
Actually I'd recommend not puting the placeholder in the input itself,
assuming you don't have to support old browsers that most other now have
stopped supporting a few years back. Depending on the browser of your
users, you can:
- use the html5 placeholder attribute (best way to do that, but
For the placeholder thing you can use the standard HTML5 way with a
polyfill such as the following (with Modernizr it will only be loaded if
the client need it) : https://github.com/ginader/HTML5-placeholder-polyfill
__
Cedric Gatay
http://www.bloggure.info | http://cedric.gatay.fr |
Okay. I digged out more deeply.
The bottom line is if the img inside a p or a div tag then the images
are broken. If there is no surrounding tag or a just a simple snap then
everything works fine.
Somehow wicket:link ignores those kind of tags.
This works fine.
wicket:link
Thank you guys, but unfortunately I have some constraints related to the
layout etc. and I can't avoid them...
Dmitriy
2012/11/28 Cedric Gatay gata...@gmail.com
For the placeholder thing you can use the standard HTML5 way with a
polyfill such as the following (with Modernizr it will only be
On Wed, Nov 28, 2012 at 8:28 AM, Marios Skounakis msc...@gmail.com wrote:
Hi Colin,
I find I am in agreement with your points about lazy loaded parts of the
data model and how this can be simplified if you use LDMs.
However, if you use LDMs for edit pages, you need to deal with concurrency
Hi everyone,
I'm currently building an application using wicket 1.4.21 and what I'm
trying to achieve is the following:
I have a protected area (stage 1) which requires the user to input his
credentials and I'm using an AuthorizationStrategy for this. This
Strategy throws a
See
https://cwiki.apache.org/confluence/display/WICKET/Modal+Windows
Opening a modal window on page load (no AJAX involved)
You could use one to block the page till pin is typed.
On Wed, Nov 28, 2012 at 1:29 PM, Karsten Gaul karsten.g...@exedio.comwrote:
Hi everyone,
I'm currently
Ive been working on an improved DataTables.net wrapper for Wicket. Its
applied as a Behavior on top of the existing Wicket repeaters/datatables -
with one caveat that the Behavior requires a table element to work with
that has a complete structure - table, thead, tbody. With some
assistance
You can set the Panel non-editable, and all those Form components will
become non-editable.
On Wed, Nov 28, 2012 at 4:06 AM, Thomas Götz t...@decoded.de wrote:
Hi there,
I'm currently implementing a panel that is used for viewing and editing of
some entity. I wonder if there is an elegant
Well with the library linked by Cédric which let's you have html5
placeholder for older browsers, you actually don't have to touch
anything in the layout to use that. All you need to do is have your
wicket component (TextField most likely) contribute to the header the js
dependencies (with
Hi Colin,
How much I hate to tell you, but your mostly on your own.
We are currently on Wicket 1.4 for our portlets and also planning an
upgrade to Wicket 6. But portlet support is at your own risk as non of
the core committers is comfortable with portlets so it's no longer a
core feature.
On Wed, Nov 28, 2012 at 4:10 PM, Thijs vonk.th...@gmail.com wrote:
Hi Colin,
How much I hate to tell you, but your mostly on your own.
We are currently on Wicket 1.4 for our portlets and also planning an
upgrade to Wicket 6. But portlet support is at your own risk as non of the
core
Hi,
the last link is indeed currently used in Liferay environment so I can't
vouch for anything else. There are neither unit nor integration tests.
The code there is based on the one found in mentioned issue for Wicket
6.0 branch.
We are currently in the final phase of project migration and
Hi Folks - has there been any progress on JQWicket for Wicket 6.0? I am
unable to upgrade to Wicket 6.3 because I am using several JQWicket
components. I would like to avoid switching over to Wi-Query since our
system is in production and it will have widespread impact at this time.
--
View
The current version on wiquery uses an older jquery version than does
Wicket 6.3.0 which was causing issues for us.
N
On Nov 28, 2012 1:23 PM, vishal vrvai...@gmail.com wrote:
Hi Folks - has there been any progress on JQWicket for Wicket 6.0? I am
unable to upgrade to Wicket 6.3 because I am
Martin
The approach of adding the Sub/Details Panel to a DummyPage works fine for
basic Panels, but there are a few problems I've hit:
1. onInitialize() isnt called - Im assuming this is because the Panel
doesnt go through a normal lifecycle before being rendered back to the ART?
2. None of the
Hi all,
I'm trying to implement a unit test for a page. The unit testing means I
should test one page only.
Suppose I have a page with a link. When I do
wicketTester.clickLink(myLink);
The WicketTester renders another page, the page rendering requires a lot of
other injected dependencies, and
I receive several of evaluate tags within ajax-response such as below, i
also receive several
priority-evaluate tags, what are these meant for, reworking an existing
application so i am not very clear how ajax response works in wicket, the
browser craps out parsing one or another of the evaluate
Hi,
We've written the following class to dynamically add components to a
page and then render them in an ajax request:
http://pastebin.com/p4cSNsUw
The rendered component is in the current page, not in a dummy page, so
everything works as expected.
The only thing that doesn't work is a full
Andrea:
Thanks for the tree sample code. Besides GIT, do you have a web site
where these examples are hosted live or your Wicket articles are posted?
best
*P
On 11/16/12 8:07 PM, Andrea Del Bene wrote:
I didn't write an article on tree components yet :) , but I've built a
very basic example for
I found a problem with the previous algorithm and fixed it. The problem
involved Panel markup that contained some markup with wicket:id tags
*outside* the
wicket:panel
/wicket:panel
element. These were resulting in components being added also but they
shouldn't. I now add an extra check with a
Martin
The approach of adding the Sub/Details Panel to a DummyPage works fine
for
basic Panels, but there are a few problems I've hit:
1. onInitialize() isnt called - Im assuming this is because the Panel
doesnt go through a normal lifecycle before being rendered back to the
ART?
2. None of the
30 matches
Mail list logo
