Hi, all,
I am playing around with the blog post application, when users click on the
create post button, it brings up the inline form for users to put text in,
I
have another requirement, we need to write some code somewhere to
retrieve an image url from a database,, so when the inline form shows up
after
users click create post button, the image automatically shows up in the
inline
form, my question is where should I put the code in? also the BlogPostClass
and
BlogPostTemplate have TextArea objects, which create GWT inline form, this
is
where I need to put image in programmatically, so I am thinking about
accessing
the GWT code to insert image, could you all point me to the right direction
about how to approach this to put image into the inline form
programmatically?
Thanks very much in advance
David
Hi devs,
I see that in several pages we have a use the following:
{{error}}
$error.message
{{/error}}
Where error is an Exception returned by a script service.
This is done in the Scheduler, in the Extension Manager and in the my new IRC Bot application.
The problem is that this will only show the message but not the full stack trace which contains the real problem…
So here's what I propose:
1) Create an internal helper WrappingTextBlockGenerator.generate() class (I'd locate it in the Macro Transformation module for lack of a better place, see point 4 below) and method which returns the XDOM Blocks to do this. Namely two divs with the proper "class" set.
2) Introduce a VelocityTool to help deal with Exceptions. I propose to make ExceptionUtils from commons-lang available as a Velocity Tool: http://commons.apache.org/lang/api/org/apache/commons/lang3/exception/Excep…
3) Modify the Message Macro to support the feature of displaying only the first line of text and hiding subsequent lines and when the user clicks on the text, the rest unrolls. I propose to do this by introducing a new "format" parameter that you would use like this: {{info|warning|error format="compact|normal"}}….{{/info|warning|error}}. By default format would be "normal" which means everything displayed. This feature would use WrappingTextBlockGenerator.generate for the implementation.
4) Update MacroTransformation.generateError() to use WrappingTextBlockGenerator.generate
5) Modify Scheduler, Extension Manager, IRC Bot application to use this new feature.
For example for the IRC Bot application:
#set ($error = $botManager.getLastError())
#if ("$!error" != "")
{{error format="compact"}}
$error.message
$exceptiontool.getMessage($error)
{{/error}}
#end
WWDYT?
Thanks
-Vincent
Hi, all,
I am playing around with the blog post application, when users click the
create post button, it brings up the inline form for users to put text in,
I have another requirement, we need to write some velocity code somewhere
to retrieve an image url from a database, so when the inline form shows up
after users click create post button, the image automatically shows up in
the inline form, users then type in more text, my question is where should
I put the code in? also the BlogPostClass and BlogPostTemplate have
TextArea objects, which create GWT inline form, this is where I need to put
image in programmatically, so I am thinking about accessing the GWT code to
insert image, could anybody point me to the right direction about how to
approach this to put image into the inline form programmatically?
Thanks
David
Hello, my name is Andrey. I became interested in the idea of "Advanced
Email Integration" and "Annotations for images and other content types"
If possible, could you tell us more about these ideas?
Hi,
When the XWiki development team wants to introduce some new features or
when we need some improvements on existing functionality, I sometimes make
proposals on how these features/improvements should look like. You can see
some of my work at
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/WebHome
IMO XWiki is a great tool for developers because they can change anything
they like and make XWiki bend to their will. Also, XWiki talks a lot the
'developer/administrator' language that new users find cryptic. Some also
say that the learning curve for XWiki is steep and that beginners have lots
of problems in understanding the structure, finding the documentation,
navigating, etc.
I'm sure every developer that used XWiki as a base for constructing their
project got into these 'new user' issues and tried to fix them as best as
they could. Although XWiki is an open source project where anyone can
contribute, sometimes time is not on our side and makes it difficult to
contribute back.
I would be very curious on how some 'independent' XWiki developers solved
some of the usability issues XWiki is facing: how they made it more easy to
use, more good looking, more intuitive, more clear, more simple.
Right now I'm thinking on how to improve the homepage, but I would love to
see *screenshots* of any aspect that was improved (profile, administration,
rights, history, comments, anything).
Sharing these screenshots could inspire others make their project better
and would step outside the 'just an idea' mode. Also there is a chance we
could integrate them in the platform so that everyone can benefit.
Thank you for your help,
Caty
Hello XWikiers,
I've just had a demo of pontoon:
https://pontoon-dev.mozillalabs.com/
I wonder how applicable this can be for XWiki based platforms.
It is llkely to generate a bit of trash but the "in-context" adjustment really looks cute and applicable to many cases to me.
paul
Hi,
I'd like to propose adding a module named xwiki-platform-component-script in xwiki-platform.
It would allow a script to get access to the Component Manager (for now, we can imagine other apis later on).
The idea is to replace the ugly static and "deprecated":
com.xpn….Util.getComponentManager()
Of course the script Service will check for Programming Rights before giving back a CM instance.
This follows the strategy of offering script services for each module.
Here's my +1
Thanks
-Vincent
The XWiki development team is proud to announce the availability of
XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and
XWiki Enterprise Manager 4.0 Milestone 1.
This release brings reduced document database id collision and quite a
few improvements and bug fixes.
See the full release notes at
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris…
for more details.
Thanks
-The XWiki dev team
Hi devs,
Following the discussion on
http://lists.xwiki.org/pipermail/devs/2012-March/049889.html I'd like
to add a JSON Velocity tool that has (for now) just one method:
/**
* Serialize a Java object to the JSON format.
* <p>
* Examples:
* <ul>
* <li>numbers and boolean values: 23, 13.5, true, false</li>
* <li>strings: "one\"two'three" (quotes included)</li>
* <li>arrays and collections: [1, 2, 3]</li>
* <li>maps: {"number": 23, "boolean": false, "string": "value"}</li>
* <li>beans: {"enabled": true, "name": "XWiki"} for a bean that has
#isEnabled() and #getName() getters</li>
* </ul>
*
* @param object the object to be serialized to the JSON format
* @return the JSON-verified string representation of the given object
*/
public String serialize(Object object)
This method is able to do what both of the initially proposed methods
were able and it doesn't expose the JSON library used (so that we can
change it later if we want). I'll use json-lib for the initial
implementation and we can move to Jackson or other JSON library later.
WDYT? I'd like to commit this ASAP.
Thanks,
Marius