Hi Devs, Hi Marius,
Could you give me some clues how to generate and save a page url that could
locate to the position of a certain title/section of the article within the
WYSIWYG editor, for example like this url,
http://platform.xwiki.org/xwiki/bin/view/DevGuide/APIGuide#HAccessobjectsin…,
click this link it will bring me to "Access objects in a page" subtitle.
What I want to achieve is that in the WYSIWYG editor after I highlighted a
sentence and clicked the Requirement tree node, it will highlight the
background of the text and generate a link to the highlighted text, so this
generated link could bring designer/system maintainer to the context of the
document.
Could you point me to the place of your WYSIWYG editor source code that I
need to add/change? Do you know how can I get the value of the selected
text, should I directly right javascript or should I modify your WYSIWYG
source code?
Thank you so much! Have a nice new week!
Jue Wang (Leon)
Hi all!
How are you?
I apologize that I wasn't so active recently. I spent all my time with
tasks from my job and my Master.
Now I have a little bit more free time (in the evenings and weekends) and I
would like to continue the XOO project. I'm not clear what should I exactly
do next and maybe you can help me with your feedback and ideas.
I'd really like to contribute again to the XWiki software . Although I was
not so happy with the API from OpenOffice , last summer was a really
interesting experience for me.
Thank you,
Cristina S.
Hi,
I'd like to commit a new standalone tool,
xwiki-tool-standards-validator, it allows to run XHTML and Dutch Web
Guidelines validation tests (only a few rules for the moment) on an
InputStream.
This tool will be used by a new enterprise module that I'll commit
right after, xwiki-enterprise-test-webstandards which runs the
validators on every pages present in the XE distrib.
Here's my +1,
JV.
Hi Thibaul, all
Something easy to do that would contribute to reduce the number of CSS
files is to concatenate all the WYSIWYG CSS files from the various
plugins at build time (there are more than 10 AFAIK). Marius, have you
looked into this? Do you know if this could be done in the 2.1 timeframe ?
Note that the target of 1 CSS and 1 JS is pretty challenging for XWiki
as we are also making it a modular software where CSS and JS extensions
can be conditionally loaded on some (not all) of the pages. Something to
investigate for JavaScript extensions could be a dynamic JS loading
mecanism, a la dojo
(http://dojocampus.org/content/2008/10/09/dojo-module-packaging-and-loading/)
Jerome.
PS: I put devs in copy as this is more a developer topic.
On 11/5/09 5:28 PM, Thibaut Camberlin wrote:
> Hi all,
>
> Page Loading time is a very important criteria when developing a web site.
> According to a recent
> survey<http://www.webdesignerwall.com/general/users-place-more-weight-on-design/>more
> than half people would drive away from a site with slow loading pages.
>
> There are several interesting issues that could be implemented to
> substantially improve page loading time in XWiki.
>
> Number one is aggreation of CSS and JS files in order to reduce HTTP
> requests. (For info, we have a total of 25 external CSS and JS files on a
> basic XWiki install when in the best world we would have just 2 - 1 CSS and
> 1 JS)
>
> Someone interrested in working on this with me ?
>
<p>I know you like good deals on clothing/fashion so I got you a private invitation for Shop It To Me:</p>
Go here:
http://www.shopittome.com/expiring_invitation/abvba9a9a1e
-Sai
This private invitation will expire in 24 hours.
Sai (pvsaikrishna(a)gmail.com) has sent you a private invitation for Shop It To Me. If you do not want to receive these messages, paste the following link into your browser:
http://www.shopittome.com/blocked_email/ZGV2c0B4d2lraS5vcmc_
Shop It To Me, Inc. 340 Brannan Street #201 San Francisco, CA 94107
It's XWiki Enterprise 2.0.4 obviously.
On Fri, Nov 27, 2009 at 21:19, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
> The XWiki development team is pleased to announce the release of XWiki
> Enterprise 2.0.4 and XWiki Enterprise Manager 2.0.4.
>
> Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
>
> This is a bug fix and enhancement release.
>
> Among other things it contains:
>
> Â Â * this time statistics are working, promise
> Â Â * several important users management related issue fixed mainly
> visible in path based multiwiki mode
>
> For more informations see the Release notes at:
> http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise204
> and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM204.
>
> Thanks
> - The XWiki dev team
>
--
Thomas Mortagne
Hi devs,
in order to complete the clean implementation of the annotation features using
components, I would need some API for manipulating objects from the DAB. I
thought of 2 versions for it:
1/
create ObjectModelBridge interface implemented by BaseObject with:
Object get(String propertyName)
void set(String propertyName, Object propertyValue)
int getNumber()
Add to DAB:
ObjectModelBridge createObject(DocumentName docName, String className)
Collection<ObjectModelBridge> getObjects(DocumentName docName, String className)
void removeObject(DocumentName docName, ObjectModelBridge object)
void saveDocument(DocumentName docName)
2/
Add to DAB:
int createObject(DocumentName docName, String className)
Collection<Map<String, Object>> getObjects(DocumentName docName, String className)
void setProperties(DocumentName docName, String className, int objNumber,
Map<String, Object> properties)
void removeObject(DocumentName docName, int objectNumber)
void saveDocument(DocumentName docName)
any of the two solutions is fine with me (maybe second a little more because
it's minimal)
WDYT?
Also, since XWikiDocument.getRenderedContent() gets more and more used by
various access API to XWiki (GWT, XMLRPC, etc), I propose to add to DAB:
getRenderedContent(DocumentName docName, String text, Syntax sourceSyntax,
Syntax finalSyntax)
which would call XWikiDocument.getRenderedContent() but also
xwiki.prepareResources() before so that the msg tools are initialized too
(hoping this would help to programatically render a document as similar as
possible with what is obtained through the view action & templates). Is there
anything I'm missing from the list to achieve this? (any other setting,
configuration needed, context setup, etc)
Thanks,
Anca