- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] best way to integrate a neighbour webapp

by Paul Libbrecht

Hello XWiki fellows, in order to customize Curriki for our needs, I need to some functionaiity. I need some GUI modifications, some of which can be done in GWT, some of which have to happen on the server, within velocity or java to call to a lucene-based tool. This tool is already as a webapp, aside of /xwiki, as /SearchI2G What would be the best way to make such a call? - make curriki's java server code depend on SearchI2G's or make a macro. In both cases, most webapp's jars need to be shared which I don't like too much - make a web-call (such as json RPC call), that's the loosest integration - make something else that would use some sort of naming interface (pointers welcome). what do you think? paul

17 years

2
1
0 0

[xwiki-devs] Tutorial to write validations and tooltips in forms

by Ludovic Dubost

Hi developers, I've written a tutorial to help write validation and tooltips in forms. It's available here: http://platform.xwiki.org/xwiki/bin/view/DevGuide/Creating+a+form+with+vali… Some features are enabled only with the following patch: http://jira.xwiki.org/jira/browse/XWIKI-2386 Reviews of the patch are welcome for inclusion in the XWiki Core. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

17 years

3
3
0 0

[xwiki-devs] toucan skin style in trunk

by Pascal Voitot

Hello, I have compiled XE from trunk... (NOT UNDER Eclipse3.4, it can't work :)) I see some rendering differences using Toucan skin... apparently Headings renderer has changed! For example: 1.1 chboing before(version 1.5) was rendered as: <h3 class="heading-1-1><span>chboing</span></h3> but now as: <h2><span>chboing</span></h2> So some style has disappeared and under FF3, paragraph begins just under header without any margin and edit section is not more aligned with paragraph but stands on a line between header and paragraph... I can change it by myself but this is a "standard" skin so I prefer asking. Is it normal or is it a side-effect of recent modifications? regards Pascal

17 years

3
3
0 0

[xwiki-devs] Dependencies in skins

by adoro

Hello devs, it was a good idea to separate templates and skins, but skins are still not completely self-contained – e.g. toucan uses .js files from the albatross skin. (fullscreenEdit.js, userandgroups.js etc). It would be great fo fix it, so xwiki-users could use only one skin as prototype to create their own skins. Thanks, Alla -- View this message in context: http://n2.nabble.com/Dependencies-in-skins-tp781062p781062.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years

2
3
0 0

[xwiki-devs] [VOTE] Monospace, superscript and subscript in XWiki Syntax 2.0

by Vincent Massol

Hi, I'd like to propose the following syntaxes: * Monospace: ##monospace## * Subscript: ,,subscript,, * Superscript: ^^superscript^^ This is the same syntax as creole and several other wikis: * http://www.wikicreole.org/wiki/CreoleAdditions * http://www.wikimatrix.org/syntax.php?i=26 * http://www.wikimatrix.org/syntax.php?i=28 * http://www.wikimatrix.org/syntax.php?i=29 Note: We need a syntax since otherwise users will have to write: * Mono: {{html}}<tt> monospace</tt>{{/html}} * Superscript: {{html}}<sup>superscript</sup>{{/html}} * Subscript: {{html}<sub>subscript</sub>{{/html}} ... which is hardly convenient... Here's my +1 Thanks -Vincent

17 years

7
7
0 0

[xwiki-devs] Javascript var to Velocity Var

by MikSan

Hi guys! Here is a quick question that I hope gets a quick answer.=) I have a Java Script var and a velocity var and what I want to do on the macro.vm file is: VelocityVar = JavaScriptVar Anyone know if this is possible being one on server side and the other on client side? And if possible how? Thanks! -- View this message in context: http://n2.nabble.com/Javascript-var-to-Velocity-Var-tp676366p676366.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years

4
4
0 0

[xwiki-devs] [GSOC]get control of the conversion target temp file path

by Wang Ning

Hi Vincent, Sorry for not send the mail to the dev list. I just reply the mail. On Sun, Aug 24, 2008 at 6:13 PM, Vincent Massol <vincent(a)massol.net> wrote: > > On Aug 24, 2008, at 10:15 AM, Vincent Massol wrote: > >> >> On Aug 24, 2008, at 6:40 AM, Wang Ning wrote: >> >>> Hi, >>> >>> Yes, I think it's necessary, if the client want to control the output >>> directory. >> >> Ok I've thought a bit about this and here's what I propose: >> >> 1) Introduce a new ConverterOutput interface with the following methods: >> - saveImage(String imageName, InputStream imageData); >> - saveDocument(InputStream documentData); > > Actually just realized that in some cases you'll have more than 1 output > file so instead you should have: > > saveDocument(String documentName, InpuStream documentData); > > Also is there a notion of main file? When there are several files how do the > user know which one is the start/main file? If the use give the target File to output to, like then the main result file is just it. We can get the main output file in the DefaultOfficeConverter as I change the inputstream to File and create a temp file for the main target output file. > >> 2) Modify Converter interface to be: >> >> void convert(InputStream sourceData, OfficeDocumentType sourceType, >> ConverterOutput outputData, OfficeDocumentType outputType); >> >> 3) Provide 1 implementation of ConverterOutput for the moment (+ a mock >> one for the unit tests of the Converter): > > I didn't mean a mock class but to use jmock as we're doing in other tests to > dynamically mock the ConverterOutput interface. > [snip] -- Thanks Wang Ning -- Thanks Wang Ning

17 years

2
1
0 0

Re: [xwiki-devs] [GSOC]get control of the conversion target temp file path

by Vincent Massol

On Aug 24, 2008, at 6:40 AM, Wang Ning wrote: > Hi, > > Yes, I think it's necessary, if the client want to control the > output directory. Ok I've thought a bit about this and here's what I propose: 1) Introduce a new ConverterOutput interface with the following methods: - saveImage(String imageName, InputStream imageData); - saveDocument(InputStream documentData); 2) Modify Converter interface to be: void convert(InputStream sourceData, OfficeDocumentType sourceType, ConverterOutput outputData, OfficeDocumentType outputType); 3) Provide 1 implementation of ConverterOutput for the moment (+ a mock one for the unit tests of the Converter): XWikiDocumentConverterOutput. This implementation stores the result of the conversion in a XWiki Document (it's name/location is passed in the constructor). In the future if we need other implementations we could add them (like a FileConverterOutput, etc) but they're not needed for now. Note 1: 3) is much cleaner and allows to move some of the code in the plugin to the XWikiDocumentConverterOutput class. Note 2: We can fully read the sourceData internally to save the input data to a file in a XWiki temporary directory (and thus control the output of the image files by jodconverter) WDYT? Thanks -Vincent PS: In the future please use the mailing list for everything related to xwiki. > > In jodconverter, there a two main interface: > > 1) void convertInternal(InputStream inputStream, DocumentFormat > inputFormat, OutputStream outputStream, DocumentFormat outputFormat); > > 2) void convertInternal(File inputFile, DocumentFormat inputFormat, > File outputFile, DocumentFormat outputFormat); > > The 1) just create a temp file for the outputstream in the system temp > directory. So if you want to control the output file directory, you > just have to change system temp directory which is not a way. In our > case, we want to get all the output when convert to html. So I don't > think this interface is enough. > > The 2) interface just can output all the result file to the > outputFile's directory which can get from xwiki.getTempFile(). > Maybe you think we can use two Files in clients and deliver the > FileOutputStream and FileInputStream to the 1) interface, you just get > one output file in the FileOutputStream and can get the other results. > The client still can't get the temp directory where the other output > files. > > WDYT? > > On Sun, Aug 24, 2008 at 4:02 AM, Vincent Massol <vincent(a)massol.net> > wrote: >> Hi Wang, >> >> On Aug 23, 2008, at 9:55 PM, Wang Ning wrote: >> >>> Hi Vincent, >>> >>> I add a interface in the OfficeConverter >>> void convert(File inputFile, OfficeDocumentType inputDocumentType, >>> File outputFile, >>> OfficeDocumentType outputDocumentType) throws >>> OfficeConverterException; >>> I think this useful. >> >> I don't think we need this since you can use a FileInputStream and a >> FileOutputStream. >> >> Thanks >> -Vincent >> >>> And I change the OfficeConverterPlugin that I can control the output >>> directory of the conversion.

17 years

1
1
0 0

[xwiki-devs] WYSIWYG editor in trunk

by Vincent Massol

Hi Marius, Just to let you know that it seems the editor you've committed on last Friday doesn't use an updated version of the XWiki syntax and is thus out of sync with the renderer. For example: * Bold is **bold**, not *bold* * Macros use 2 curly braces * etc We need to fix this ASAP since otherwise it won't work and we need to release a working version for 1.6M1 (not everything should work but easy stuff like this should work). Thanks -Vincent

17 years

2
8
0 0

[xwiki-devs] [Rendering] Wiki syntax for quotes and block quote?

by Vincent Massol

Hi, I've noticed that wikimodel uses the space character for representing quotes in XWiki syntax. Here's Mikhail's explanation: " These events are send by quotation blocks. Example: > The first line >> The second line >> The third line > The fourth line Gives the following sequence of events: <beginQuotation> <beginQuotationLine>The first line <beginQuotation> <beginQuotationLine>The second line </endQuotationLine> <beginQuotationLine>The third line</endQuotationLine> </endQuotation> </endQuotationLine> <beginQuotationLine>The fourth line </endQuotationLine> </endQuotation> In XWiki syntax quotation lines are represented by spaces at the beginning of each line. The quotation block is a block of lines starting from a space-prefixed line. Something like . The first line .. The second line .. The third line . The fourth line (I used the "." symbol to show a space) In CommonSyntax quotation blocks starts with the ">" symbol as I wrote in the example above. " I don't think we've really been using leading spaces to represent quotes, have we? Also I don't think the space character is a good character for this. So my question here: Do we want to have a syntax for quotes/block quotes? And what character to use? I think we do want to have this syntax and the ">" character sounds good to me. WDYT? Thanks -Vincent

17 years

5
6
0 0

Re: [xwiki-devs] [xwiki-notifications] r11992 - in platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store: hibernate/query jcr/query query

by Vincent Massol

On Aug 23, 2008, at 1:07 AM, amelentev (SVN) wrote: > Author: amelentev > Date: 2008-08-23 01:07:59 +0200 (Sat, 23 Aug 2008) > New Revision: 11992 > > Added: > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store/ > query/QueryException.java > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store/ > query/QueryExecutor.java > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store/ > query/QueryImpl.java I really don't like to have Impl in class names. I'd really like that we define it as a rule not to use them. All or classes are implementations anywyay... I think it's also important it ends with Query since all queries should do that. I can propose: - DefaultQuery - BasicQuery - BaseQuery Thanks -Vincent PS: Haven't reviewed the commit, just this that jumped in front of my eyes. If we're ok with it I'll put it in our best practices guide on dev.xwiki.org [snip}

17 years

3
3
0 0

[xwiki-devs] [New Rendering] Macro syntax

by Vincent Massol

Hi, Right now wikimodel implements the following syntax for xwiki macros: 1) {{macro param1="value1" param2="value2"}}content{{/macro}} {{macro param1=value1 param2=value2}}content{{/macro}} This is different from the original proposal of: 2) {{macro:param1="value1"|param2="value2"}}content{{/macro}} Notes: * I think 1) is cleaner and easier to read * There's no default param in 1) so you don't write something like: {{include:Main.WebHome}}. You have to write: {{include document=Main.WebHome}} * 2) is the same as the current syntax Which do we want? I don't have any particular preference. Thanks -Vincent

17 years, 1 month

7
10
0 0

Re: [xwiki-devs] [New Rendering] Automatic new lines?

by Joshua Marks

Regarding extra lines with multiple enter/carriage returns: +1 you bet- WYS should be WYG. If I put in 32 returns while typing, I want 32 empty lines on output. Joshua Marks CTO Curriki: The Global Education and Learning Community jmarks(a)curriki.org www.curriki.org ****************************

17 years, 1 month

2
1
0 0

[xwiki-devs] [New Rendering] Link rendering when no alias

by Vincent Massol

Hi, In the current rendering a link like [Space.MyPage] is displayed as "My Page" (camelcase rendering + removal of space prefix) when no alias is specified. We need to decide what to do with the new rendering. There are several options: * MyPage * Space.MyPage * My Page * wiki:Space.MyPage * (the page title) I propose to default to the page name without space nor wiki name (i.e. "MyPage" in our example). We could also make it configurable with variables like %w (wiki name), %s (space name), %p (page name), %P (camel cased page name, i.e. "My Page") and %t (page title). The default would be %p but users could change it to %s.%p or %w:%s.%p or whatever else they want. WDYT? Thanks -Vincent

17 years, 1 month

4
4
0 0

[xwiki-devs] XWIKI - Getting Space Rights.

by Prathap Pandian

HI, I have link [Panels>Panels.WebHome] in the *"Main"* Space. And i want to display this only for the user who having admin rights for the *"Panels"* Space. I tried with this one *$hasAdmin* but it getting the rights for the current space. Any other way to do this...? -- Prathap

17 years, 1 month

2
1
0 0

[xwiki-devs] [GSoC][officeimporter]the interface of office converter

by Wang Ning

Hi Vincent, I think OutputStream convert(InputStream inputStream, OfficeDocumentType inputDocumentType, OfficeDocumentType outputDocumentType) is not appropriate. The OutputStream is a place to write data to. I just can't get the data from the OutputStream. I think the OutputStream should be a special outputStream the user provide, so I have these to proposals for this interface: 1. ByteArrayOutputStream convert(InputStream inputStream, OfficeDocumentType inputDocumentType, OfficeDocumentType outputDocumentType) return type change to ByteArrayOutputStream. Then client can use ByteArrayOutputStream.toByteArray() to get the contents in OutputStream. 2. void convert(InputStream inputStream, OfficeDocumentType inputDocumentType, OutputStream outputStream, OfficeDocumentType outputDocumentType) Client provide a output Target to store the contents. Example: ByteArrayOutputStream outputStream = new ByteArrayOutputStream(); convert(inputStream, inputDocumentType, outputStream, outputDocumentType) WDYT? -- Thanks Wang Ning

17 years, 1 month

2
2
0 0

[xwiki-devs] Exporting/Importing pages

by gerem44＠free.fr

Hi, Everytime i try to export pages in .XAR, and when i try to open it, i get a corrupted archive, i tried with 2 different XWiki installation. Actually i try to see the XWwiki page format to match with the pages i created. If nobody has an idea about XAR problem, maybe someone could tell me what to put in the XAR archive to be able to import it into XWiki. The package.xml format and the page format or extension. I dont know if its possible to send me as an attached file, A wokring XAR archive. Best Regards, Gerem

17 years, 1 month

3
4
0 0

[xwiki-devs] Watch Lucene integration: XWATCH-116

by Anca Paula Luca

Hi devs, my research about Lucene querying for Watch (http://jira.xwiki.org/jira/browse/XWATCH-116) from the past weeks brought me to the following results: First of all, as I already mentioned, since Lucene is a fulltext indexing engine and Watch data is, even if wiki data, quite structured data (and so are its queries), something feels not right in trying to do this. But the query speed improvements are / should be significant so we could try to workaround -- XWiki Lucene plugin indexes object properties in documents as fields so basically, a structured search is plausible (with the right type of Lucene fields, etc). Even like this, not all Watch SQL queries are fully translatable to Lucene queries without having Watch specific Lucene querying code and / or Watch specific Lucene indexing. Second, there is a problem with the Lucene reliability and "response time", as mentioned in the jira issue comments: * there is a delay between the moment a document is created / modified and the moment the change is retrievable through Lucene queries, because first it needs to be indexed by Lucene. This fuzzyness, although acceptable in some situations (for example, retrieving the list of articles to show to the user) it is not desired in situations like article properties updates (star, read, trash) or feed adding / deleting -- "caching" these changes until they are retrievable through Lucene querying is not at all an option. * XWiki Lucene plugin seems quite buggy / unstable: a lot of exceptions (server restart seems to be fatal due to some hanged file lock), duplicate documents in results sometimes, missing results some time, all explainable and acceptable in the "fuzzy" situation of a fulltext search engine, but not when trying to use it for structured search. Despite all these, I devised some code to help me test Lucene and compare it to SQL in the real-watch situation, for the article list retrieval. The results for the time spent on the server (I assumed that the time taken to transport documents and print them in the Reader is the same regardless of the querying technique), for a mysql server with ~60000 articles in ~200 feeds, are: * for the initial loading of the articles, in a newly started server, SQL can take up to 30-40 seconds, Lucene takes "only" up to 20 (15-16) * for the initial load of the interface, in a non-newly started server, it takes ~15 seconds for SQL and ~4-5 on average (but can go up to 10) for Lucene * for a click on the All group, which it's basically the same query as for the initial load of the article list, it can go under a second for Lucene and around 7-8-9 seconds for SQL * for a click on a feed with 1023 articles (therefore loading the list of articles in a specific feed), SQL goes to 3 seconds while Lucene can take from under a second to a couple of seconds, depending on the time took to load the actual documents corresponding to the search results * for pagination navigation, Lucene takes a second on average and SQL 2-3 seconds. Note that Lucene retrieval still uses the database and SQL access because its results are LuceneDocuments (that hold names of XWikiDocuments), not XWikiDocuments. All the tests above were made with a server running on my computer with a 5.0.51a mysql version, a 1.6-SNAPSHOT XWiki version , java 1.5.0_15 version, AMD Turion64 x 2 TL-56, 1.8 GB RAM, but with other applications running too. I feel that, overall, Lucene querying improvements are not so spectacular, especially because it cannot solve all situations and we would still need SQL querying in some cases, and because of its relative instability (which we could think about fixing, though). The other option for performance improvements in Watch would be to have a Watch specialized server (as we've already discussed) which would allow, amongst other things, to use Watch specific SQL queries (as opposed to now when we use generic queries since we have to go through the XWiki GWT API) and optimize as much as possible at that level. I haven't tested yet the amount of improvement but, since I think we might be able to drop some tables from some of the SQL joins we're doing right now, it should be better. Of course, this kind of approach requires heavy refactor, and potentially complete rewriting and rearchitecturing of some pieces. Despite the coding challenge, I'd go for the second approach, WDYT? Happy coding, Anca Luca

17 years, 1 month

4
6
0 0

Re: [xwiki-devs] Questions regarding A,B,C,D .. Views on spaces.

by Ludovic Dubost

Hi Asiri, You are perfectly right that we have a coherence problem with these virtual views. Maybe one way to solve it would be to show the last 20 pages directly in the Space view. This way if you create a new page it will show up in the space view refresh. We are kind of stuck between a view system that is not perfect (the A, B, C, D) and one that will cause performance issue (normal flat view). I think users will have to live with the caveats of the A, B, C, D system. So I propose to implement A, B, C, D + the last 20 recent pages. Maybe Guillaume can give his point of view ? WDYT ? Ludovic Asiri Rathnayake wrote: > Hi Ludovic, > > I've been thinking of implementing A,B,C,D view for spaces but i came > across few obstacles. > > Currently we have SpacesView->Space->Page kind of a hierarchy and > there, both Space & Page are domain objects. But if we change the > hierarchy to categorize pages by first letter, the situation changes a > bit. > > Then the hierarchy would be like, > SpacesView->Space->PagesByFirstLetter->Page. Here the Space is no > longer a domain object but kind of a view and adding pages to it poses > problems. I mean if we add a page to an space, we would have to move > it immediately to the correct category (by first letter). And this is > not that good. > > One solution is to restrict the user's ability to add pages / spaces > (these are what complicates the issues). But this might not look that > pretty. > > I have the following hierarchy in my mind but i'm not quite sure about > it : > > XWikiDocumentsDavView->XWikiDocumentBySpaceNameDavView->XWikiDocumentsByFirstLettersDavView->XWikiDavPage > > This way it looks pretty much alike attachments view. But again, > adding pages to a space seems to pose the same problem. > > I think these problems are mainly due to the fact that XWiki domain > does not directly map into a directory hierarchy. > > Please let me know how should i proceed. > > Thanks. > > - Asiri -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

17 years, 1 month

2
1
0 0

[xwiki-devs] [Proposal] Move the new WYSIWYG into the platform

by Marius Dumitru Florea

Hi devs, I propose to move the new WYSIWYG editor into the platform in order to have it as an experimental feature for 1.6M1. The following steps should be taken: * Create a platform/web/wysiwyg module to host the code currently resided in sandbox/wysiwyg * Change templates/edit.vm, templates/editpanels.vm and create templates/editwysiwygnew.vm to make XE aware of the new editor. This way our users will be able to experiment the new WYSIWYG editor on any page, by having editor=wysiwygnew in the edit URL. * Change platform/web/pom/xml and enterprise/web/pom.xml Here's my +1 Marius

17 years, 1 month

13
28
0 0

[xwiki-devs] [GSoC][officeimporter]finish code clean for office converter and status update

by Wang Ning

Hi Vincent & all devs, I finished the code clean and document for the current version of office converter. If you want to see the detail, please visit http://dev.xwiki.org/xwiki/bin/view/Design/OfficeConverter This project is dependence on the XE 1.6 which is not released yet. So if you want to try the newest version of this project, you need build the latest version of xwiki from the svn and download the officeconverter for XE 1.6 and follow the README. Important change: 1. add the support for ppt and odt 2. encapsulate the convert2xwiki to the Util So the todo list is * improve the xhtmlparser in the xwiki-core-rendering and wikimodel * improve the xwiki-core-xml 's HTMLCleaner -- Thanks Wang Ning

17 years, 1 month

2
2
0 0

[xwiki-devs] XWIKI - Problem In Getting The Rights.

by Prathap Pandian

Hi, I had some problem in the rights, i have created a user and assigned admin for that user in the XWiki space. Now in the Main Space i had the following code #if ($xwiki.hasAdminRights()) You have admin rights for this space. #else You don't have admin rights for this space. #end Now login as newly created user and go to the Main space. It showing "You have admin rights for this space". Actually it has to display "You don't have admin rights for this space." since i have assigned admin rights for the XWiki Space. -- Prathap

17 years, 1 month

1
0
0 0

[xwiki-devs] strange behavior for XWikiGlobalRights and register

by Pascal Voitot

Hello, I deny(or just keep blank) Register right for XWikiAllGroup<http://www.mandubian.org/xwiki/bin/view/XWiki/XWikiAllGroup> Then I deny "register" right for "unregistered users" aka XWiki.XWikiGuest I logout It appears that anyone is able to register!!!!!!!!! Then, I allow register right for XWikiAllGroup while keeping it denied for XWikiGuest. The register menu disappears by default! Apparently, the right management requires the right to be defined at least for XWikiAllGroup to take XWikiGuest into account. is it normal? best regards Pascal

17 years, 1 month

1
0
0 0

[xwiki-devs] [GSoC][officeimporter]code clean and javedoc almost done

by Wang Ning

Hi Vincent, Just FYI, I almost finish the code clean and javadoc from my current code(two class left). I think I can finish it tomorrow morning. And we can submit it to the code.xwiki.org soon. -- Thanks Wang Ning

17 years, 1 month

1
0
0 0

Re: [xwiki-devs] XWiki wysiwyg editor

by Marius Dumitru Florea

Hi Darren, I'm currently moving the new WYSIWYG from the sandbox into the platform. Next Monday we are going to release XWiki Enterprise 1.6M1 including the new editor as an experimental feature. Experimental because, for the moment, it doesn't have all the features of the TinyMCE. We hope it will have them by the end of September. Also the new editor depends on the new rendering module, made by Vincent, which is very complex and requires an tremendous effort. So you can wait for the 1.6M1 release and then try to extend the new editor to fit your needs. On our side, it will take a few months till the current editor will be replaced. Thanks for your interest in the XWiki platform! Marius > Hello Marius, > > I was wondering if you had made any progress with > http://jira.xwiki.org/jira/browse/XWIKI-2497. > > I am new to XWiki and the only real stopper from us using it more widely > is the problems with the wysiwyg editor. We are very keen on getting the > new version you are developing. Is it in a state that we can start using > it, and if so can you tell me where to get it and how to integrate it. > If it helps we could help you test it. > > Thank you for your time and keep up the good work, > > Darren > > >> Darren Owens >> E-Strategy Senior Web Developer >> Simplyhealth > t: 01264 353211 x2850 > m: 07595 393651 > e: darren.owens(a)simplyhealth.co.uk > > ----------------------------------------------------------------------------------------------- > This email, and the contents contained within, are private > and confidential between the sender and the individual(s) > to whom it is addressed. > The contents do not necessarily represent the views of Simplyhealth Group > Limited. > > In the event of misdirection, the recipient is prohibited from > using, copying or disseminating it or any information contained in it. > If you have received this email in error please notify Simplyhealth > immediately by telephone on 0845 075 2020, or by email to > network.administrator(a)simplyhealth.co.uk > > Simplyhealth Group Limited is registered and incorporated in England and > Wales > as a company limited by guarantee. Its registered office is at Hambleden > House, > Waterloo Court, Andover, Hampshire, SP10 1LQ, registered no. 5445654. We > may record or monitor telephone calls to help improve our service and > protect our > members. > ----------------------------------------------------------------------------------------------- >

17 years, 1 month

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs