On Jan 11, 2008 9:08 AM, Edward Yakop [EMAIL PROTECTED] wrote:
On Jan 11, 2008 11:04 PM, Ryan Sonnek [EMAIL PROTECTED] wrote:
I don't care if it can be optomized if it introduces more complexity.
How often are people drag/dropping objects on webpages anyways? There
isn't a need to support
I don't care if it can be optomized if it introduces more complexity.
How often are people drag/dropping objects on webpages anyways? There
isn't a need to support 100,000 operations per second for this kind of
operation. Looping over components in a page is blazing fast unless
you have
On Jan 11, 2008 10:59 PM, Ryan Sonnek [EMAIL PROTECTED] wrote:
The committed code has improved
JavascriptBuilder#formatJavascriptValue to support array, set and list
value.
I didn't know about these changes. I'll try and take a look and see
if I can reuse the code. Do you have unit
On Jan 11, 2008 11:04 PM, Ryan Sonnek [EMAIL PROTECTED] wrote:
I don't care if it can be optomized if it introduces more complexity.
How often are people drag/dropping objects on webpages anyways? There
isn't a need to support 100,000 operations per second for this kind of
operation. Looping
It's not the code for finding the component that bothers me. as you
said, it's very easy. My problem is that now you have to muck with
the scriptaculous javascript callback to extract the component path
instead of just using the default behavior which is to transfer the
markup id. This
On Jan 10, 2008 10:10 PM, Edward Yakop [EMAIL PROTECTED] wrote:
On Jan 11, 2008 11:51 AM, Ryan Sonnek [EMAIL PROTECTED] wrote:
if there are other improvements to be made, let me know!
How about committing the [DraggableTargetBehavior] and its support for
multiple drag source type.
Not sure
On Jan 11, 2008 9:37 AM, Edward Yakop [EMAIL PROTECTED] wrote:
It's not the code for finding the component that bothers me. as you
said, it's very easy. My problem is that now you have to muck with
the scriptaculous javascript callback to extract the component path
instead of just using
don't see this as a very strong usecase. Most usecases will have some
kind of placeholder text instructing the user to drop objects on it.
Does this work for you?
I tried div, span and your example.
Neither work for firefox 2.0 and 1.5 (I haven't test it on another browser).
The only way
it
-Clay
-Original Message-
From: Ryan Sonnek [mailto:[EMAIL PROTECTED]
Sent: Friday, January 11, 2008 11:51 AM
To: users@wicket.apache.org
Subject: Re: Is wicketstuff-scriptaculous still active?
On Jan 11, 2008 9:37 AM, Edward Yakop [EMAIL PROTECTED] wrote:
It's not the code for finding
On Jan 12, 2008 12:50 AM, Ryan Sonnek [EMAIL PROTECTED] wrote:
I didn't mean you changed scriptaculoius. i meant that you really
customized the rendered *scriptaculous javascript*. I've seen the
sourcecode and remain unconvinced that this is simpler than using the
markup ID.
I'll leave this
On Jan 11, 2008 11:12 PM, Ryan Sonnek [EMAIL PROTECTED] wrote:
Also, I still don't see how this would work for the SortableListView?
Ok, hours as passed (I was thinking to only spent 1 hour, ended up
spending 4 instead).
Status:
After spending much time about SortableListView.
I couldn't make
Edward,
Thanks for the email. I'm currently working on revamping the drag
drop API. if you have any code you'd like to contribute feel free to
drop me an email. maybe we could hash out a great new api to simplify
it's use.
regarding the javascript issues, could you re-open this bug i filed in
The code is commited at
https://scm.ops4j.org/repos/ops4j/laboratory/users/efy/wicket-contrib-scriptaculous
I'm sorry that I couldn't sent a patch, when the modification was
done, it was committed to our project svn server.
Hence a diff couldn't be made.
regarding the javascript issues, could
regarding the javascript issues, could you re-open this bug i filed in
wicket?
https://issues.apache.org/jira/browse/WICKET-987
I can't re-open this bug, but I left a comment in the jira issue.
Regards,
Edward Yakop
-
To
i've reopened the issue.
It must only allow whoever filed the issue to reopen it...
On Jan 10, 2008 10:00 AM, Edward Yakop [EMAIL PROTECTED] wrote:
regarding the javascript issues, could you re-open this bug i filed in
wicket?
https://issues.apache.org/jira/browse/WICKET-987
I can't
On Jan 10, 2008 9:22 AM, Ryan Sonnek [EMAIL PROTECTED] wrote:
Edward,
Thanks for the email. I'm currently working on revamping the drag
drop API. if you have any code you'd like to contribute feel free to
drop me an email. maybe we could hash out a great new api to simplify
it's use.
Hey
On Jan 11, 2008 11:51 AM, Ryan Sonnek [EMAIL PROTECTED] wrote:
if there are other improvements to be made, let me know!
How about committing the [DraggableTargetBehavior] and its support for
multiple drag source type.
The committed code has improved
JavascriptBuilder#formatJavascriptValue to
I forgot to mention about the usage of markup id.
I think this is a less optimize way to find the drag source component,
especially if the page object graph is large.
For example,
If we have the following Page component structure.
Page
- Container1
- Table with a lot of rows
- other
Hi,
Boon Ping and I managed to modify scriptaculous to get wicket component to
be passed during onDrop callback.
We changed the DraggableTargetContainer? to become a wicket behavior.
We concluded by doing it this way, we can practically make any wicket
component (tested for label and img, so
Hi Lan
There was a discussion about it being a couple of versions behind, im
not sure if Ryan's active? Whats the problem?
Lan Boon Ping wrote:
Hi,
Is wicketstuff-scriptaculous still active?
Regards
Boon Ping.
-
To
Hi Nino and Ryan
Thanks for the reply.
Regard the DraggableTarget.onDrop(...) method, it has a String
(markupId) and AjaxRequestTarget as parameters, I found out that in
some circumstances, markupId is not desirable. For instance, I have a
FruitPanel and two subsclasses-ApplePanel and
I'm open to suggestions. The markupId is required for the
scriptaculous library to do it's magic, but how about something like
this?
When you call the DraggableTarget.accepts(Component) method, it could
store a reference to that component, and the onDrop() method could
take the string markupId
hmmm
this change doesn't really work when dealing with a SortableListView.
With the SortableListView, there's no Component for the
DraggableTarget to work with. It really only has the markupId. Maybe
another wicket dev has an idea for how to do this?
On Jan 7, 2008 9:44 PM, Ryan Sonnek
Hi Ryan,
I like the fact that I can drop components that the target doesn't
know about them, I think it is very useful especially when you have
many planes need to collaborate without knowing each other.
Is it possible to use component.getPath()? and the onDrop() method
could get the component
24 matches
Mail list logo
