Thank you for your answers.
I undrestand better why Struts2 use dojo. I think It's very important to
explain
in the Struts2 documentation the dojo choice (portlet environment,...),
because
a lot of people use prototype/scriptaculous (like AjaxTags).
I forwarded your mail into Rails forums, to
Sorry for the delay guys.
I see. Thx for the heads up. :-) Haven't tried it on eclipse yet.
Rainer have started playing with dojo 0.4 on his local box, will get it and
the patches into svn within these few days. Thx Rainer.
Cheers.
Musachy Barroso [EMAIL PROTECTED] wrote: I tried also
Feature added.
Please do review the code, if any one is interested. The details of the changes
are at the jira issue itself. Thx.
Cheers.
-
Posted via Jive Forums
Resolved issue.
Please do feel free to review comment the code. Changes details are at the jira
issue itself. Thx
Cheers.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=48630messageID=99258#99258
Musachy,
after applying your patch, all custom widget files do no longer have
content.
Is it correct, that all files under core/src/main/resources/org/
apache/struts2/static/dojo/struts/widget/ should be removed?
If yes, shouldn't core/src/main/resources/template/ajax/
dojoRequire.js
I'd prefer that we not have per-edit notifications. As Wendy notes,
the per-edit notifications just regurgitates the entire page and
provides a view changes link. If you click through the link, you do
get a nice change log, but you have to click. Aside from immediency,
the per-edit notifications
Ah, okay... So it looks like the complete folder with all moved widget files
is missing. The patch does not create the folder, nor does it create the
new/moved template files.
thanks for your help,
Rainer
I will take a look tomorrow (not on my box right now), but I do remember
that I changed
