Re: [xwiki-devs] XEclipse Off-Line

Short message to say I've tried the standalone version (thx Asiri, Tharindu & Fabio :-) and it works simply great! Guillaume On 11/10/2007, Asiri Rathnayake <asiri.rathnayake(a)gmail.com> wrote: glad if someone can test it a bit :) persistence, all connections approach compares to eclipse's native hierarchy. That is, under the main cache location directory for caching it's spaces. space and another directory for each space to followed this method to avoid caching the whole re-written each time a page is changed). cache his data. uncommitted etc.). This need to be improved. committing pages which have been expired (overriding others work). The user can then revert his changes or manually do the changes. This is not a complete solution but I believe it works for the moment. refactored and re-designed a bit to accommodate for future changes. Recent additions and modifications have made the code bit dirty and it will be hard to maintain it if we do not refactor it now. Once we have a solid design, it will be easy to extend the product. I think Fabio agrees with me. (for an example, when the connection is removed). While this is a minor thing, it can be unpleasant for the user. I wish someone could fix it. I would start a thread with status updates (as told by Vincent). repository. When the user navigates through the document hierarchy, each visited node is stored into the local repository. Also, all edits to documents are saved into local repository as well. To complete XEclipse off-line, following tasks need to be done, into local repository when user is working off-line. local repository. server. weeks (till 28th), but I will definitely get on with it after that. A big sorry about the missed dead-line (XEclipse Off-line was promised to deliver on 10th). -- http://wikibc.blogspot.com/ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs