Hi, everyone:
I am James Xu, and now I am an undergraduate student. I would like to
join GSoc this year. I am interested in the idea "Auto Completion in
Content Editors".
I have more than 4 years web developemnt, php for 4 years, and java
for 3 years. For java web development, I used
SSH(struts2+spring+hibernate) often,
and I also have project experience using velocity as view layer.
Beside, I am very interested in front-end design, and have more than 3
years experience in javascript development, I am the one of the early
user of
dojo since the 0.9 version, and I am now using jquery a lot, I am also
a big fans of google, I start getting to know GWT this year, but I
think I would
be a quick learner based on the kownledge gained from other tools and
my own experiences.
Though I don't have experience in developing rich text editor before,
but I had used a lot of them, and also I have done one project related
to
auto completion for facted search input form of the resource search system.
I read some documents of the idea page, I am attracted by the
autocompletion functions for a web rich text editor, I think we can
refer to the eclipse
HTML editor, when you first typing "<", there will be a suggest box
for next input of html tags, and it will be narrowed when you type
more. I think
it can be applied to xwiki editor for various syntax.
For example, if user type"{{", then it should suggest him a list
like"code,box..."which are the macro tags started with "{{", when user
type "enter",
then it will insert to the text area the following:
"{{box cssClass="" title="" width=""}} {{/box}}"
I think this will save the time for user to type all the macro tags by them own.
Another useful function could be the same as described in the idea
page, when user type "[[" it will auto suggest the documents of the
wiki.
However, some of the xwiki syntaxes are different from the enclosure
style of HTML tags, and some function looks very intuitive, it will be
very
confusing when using it, so I should think more about it.
Hope you all can give me some tips to complete this idea. thank you very much
and I would like to participate in GSoC-2011. I am mainly
interested in contributing to the project idea "Mobile Skin for XWiki
Enterprise". I have been working on web development for the past two years
and developed a couple of websites. I have a good knowledge of HTML,XHTML
and CSS , I also know PHP and am learning Javascript. If someone could help
me regarding this , I would be really thankful.
--
Best wishes,
许凌志(Jame Xu)
MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University
Department of Computer Science and Technology, Xi’an Jiaotong University
Hey
I am Supreet and I would like to participate in GSoC-2011. I am mainly
interested in contributing to the project idea "Mobile Skin for XWiki
Enterprise". I have been working on web development for the past two years
and developed a couple of websites. I have a good knowledge of HTML,XHTML
and CSS , I also know PHP and am learning Javascript. If someone could help
me regarding this , I would be really thankful.
Hi,
I've tried the dashbord on 3.0 snapshot and could not make the "Add
Gadget" function work on an empty dashboard.
From what I see the issue seems to be in the wysiwyg code. I got the
dialog box from the wysiwyg, when clicking on Insert Gadget" I got an
exception:
uncaught exception: Class$dF: One or more exceptions caught, see full
set in UmbrellaException#getCauses
at
function nr(){try{null.a()}catch(b){return b}}
This issue seemed to only happen with an empty dashboard macro (with not
gadget yet added).
I think we need to work on two things for each feature that we are
developping:
1/ Having a status of where we are:
In the case of Dashboard, I think that's updating this page:
http://dev.xwiki.org/xwiki/bin/view/Design/Gadget+Scenarios+Prioritized
2/ Write a test plan and have Sorin include the testing of new features
in his testing.
For that he needs to know how to test and what is supposed to be
there/not there.
Concerning the development priorities, I think for the next period of
development on the dashboard we need to focus on wiring the UI for
"beginners", making it easy for them to create their first dashboard. In
my view this is in priority:
- Create page with a dashboard macro (In the Add Menu in XE)
- Go to edit more (I'm still convinced that we need the dashboard
editing in "view" mode and not in "inline" mode)
- Add a column in your dashboard
- Editing a dashboard
Also for the 3.1 timeframe I think we need to have some brainstorm to
add some more "Dashboard" friendly macros/gadgets to make dashboards
more usefull and interesting for users, but that's another story.
Right now I think the most important is that we agree on the priorities
for the next step and that for 3.0 we have a simple but coherent
dashboard feature.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi,
Right now logs go to a file on the filesystem. However this is not right since most logs are application logs and should be visible to wiki developers. For ex, if I use a deprecated API, I need to see it. It shouldn't go to admins only and shouldn't "pollute" the system logs.
Hence I believe we need a Log Console available somewhere (we could make it avail in the Admin UI FTM).
I'd like to discuss an implementation idea I've had this morning:
* Send application logs as Observation Events and make the available in the Activity Stream (AS)
Pros:
* Infrastructure already in place
* Fits the AS goal: temporary information and is purged regularly
* (Of course the Activity gadget would not display them)
* They can be sent remotely as remote events in the future; this allows implementing a remote console to monitor an XE or XEM from a distance
Cons:
* We need to assess the performance risk and more generally we need to make the AS scalable (I don't think it is now).
* 2 ideas for scaling up the Observation/AS:
1) Have the Observation Manager save events to be notified into a Queue and have one or several separate threads take those events and send them to listeners. Right now if one listener takes time in its onEvent() method it slows down the whole chain since they are called serially. Note that if we want even better scalability, the Queue could be stored externally to XWiki (a JMS queue for ex) and scalability can be achieved by app server instances listening to this queue to process it.
2) Have a way to tell the AS what storage to use for specific Event Types. For example the AS could use an in-memory storage for Log Events while using a DB storage for other events. This would be useful since I don't think we really need to store logs in the DB. Note that the cache could be indexed on the message so only one instance of each log message is preserved (no need for dups), possibly with a counter to mention how many of them there were (that's an optimization).
I believe 2) might be enough for performances in a first implementation of the log console.
WDYT?
Thanks
-Vincent
Hi Sergiu,
I would have thought that users would only need the delete (or edit but I prefer delete) rights to remove comments.
Could you explain the rationale?
BTW for logged in users, what do they need now?
Thanks
-Vincent
On Mar 18, 2011, at 12:36 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2011-03-18 00:36:44 +0100 (Fri, 18 Mar 2011)
> New Revision: 35698
>
> Modified:
> platform/web/trunk/standard/src/main/webapp/templates/commentsinline.vm
> Log:
> XWIKI-4842: Issues on Preview/Edit Comments for Unregistered Users
> Guests should not be allowed to delete comments unless they have admin rights.
>
> Modified: platform/web/trunk/standard/src/main/webapp/templates/commentsinline.vm
> ===================================================================
> --- platform/web/trunk/standard/src/main/webapp/templates/commentsinline.vm 2011-03-17 23:29:08 UTC (rev 35697)
> +++ platform/web/trunk/standard/src/main/webapp/templates/commentsinline.vm 2011-03-17 23:36:44 UTC (rev 35698)
> @@ -151,7 +151,7 @@
> <span class="commenttool commentedit"><a class="edit" href="$doc.getURL('view', "viewer=comments&number=${comment.number}&xredirect=$xredirect")" title="$msg.get('core.viewers.comments.edit')">$msg.get('core.viewers.comments.edit')</a></span>
> #end
> #end
> - #if ($hasEdit)
> + #if ($hasAdmin || (!$isGuest && $hasEdit && $comment.author == $xcontext.user))
> <span class="commenttool commentdelete"><a class="delete" href="$doc.getURL('objectremove', "form_token=$!{services.csrf.getToken()}&classname=${xCommentClass}&classid=${comment.number}&xredirect=$xredirect")" title="$msg.get('core.viewers.comments.delete')">$msg.get('core.viewers.comments.delete')</a></span>
> #end
> </span>## commenttools
Things noticed that we should improve
==============================
1) When the apache server on myxwiki.org is down there's no maintenance page appearing. We should get a nice "maintenance in progress" page.
2) When doing upgrades it's best to plan it a bit ahead of time and notify of the upcoming upgrade using the myxwiki twitter account/mailing list
3) In the upgrade notes, I'd like to suggest that we do things differently:
- before restarting tomcat, stop apache (after disabling the crontab)
- create a tunnel to your local machine: ~C + -L8080:<ip>:8080
(you get the ip using /sbin/ifconfig)
- start tomcat
- ensure it all works fine
- upgrade the XARs
- verify all is ok
- restart apache
4) Right now port 8080 is open on apache, this needs to be closed
5) we should subscribe the notifications list to the main wiki on myxwiki.org to perform community checking of the wiki
Who can help perform 1), 4), 5)? I can do 3).
Problems fixed while doing the upgrade
===============================
I noticed that one user page was called frequently in the logs and after checking it had over 3K comments, all spams with lots of external URLs.
I removed this page but we need to watch out for pages giving xwik guest rights to edit/comment on them.
I hope this was the problem causing lots of downtime on myxwiki.org and poor perfs.
Thanks
-Vincent
Hi community,
Time flies when you're having fun, so we missed last week's Thursday
bugfixing day (which would have made it a monthly event). So, tomorrow
there will be another bugfixing day, in preparation for a clean 3.0 release.
As usual, everyone is welcome to participate in bugfixing, but not only:
bug triage and bug reporting is also very much appreciated.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
LinkedIn
------------Arvind Gupta requested to add you as a connection on LinkedIn:
------------------------------------------
Guillaume,
I'd like to add you to my professional network on LinkedIn.
- Arvind Gupta
Accept invitation from Arvind Gupta
http://www.linkedin.com/e/3vasf0-glco4h7h-5q/9s_c-0fN05p6qjQq9meQgfVB/blk/I…
View invitation from Arvind Gupta
http://www.linkedin.com/e/3vasf0-glco4h7h-5q/9s_c-0fN05p6qjQq9meQgfVB/blk/I…
------------------------------------------
Why might connecting with Arvind Gupta be a good idea?
Have a question? Arvind Gupta's network will probably have an answer:
You can use LinkedIn Answers to distribute your professional questions to Arvind Gupta and your extended network. You can get high-quality answers from experienced professionals.
http://www.linkedin.com/e/3vasf0-glco4h7h-5q/ash/inv19_ayn/
--
(c) 2011, LinkedIn Corporation