Hi devs,
It's been reported to me that this feature isn't working. Here are issues I know about it:
- the pencil icon doesn't appear on Chrome
- foxwiki is in version 1.0b and not even a final 1.0 version
- when you try to install the FF extension it says it's not compatible with FF 3.6.3 (it doesn't work with other FF 3.6 versions either)
- it's a built in feature and it's not working so it's misleading
- doesn't work in IE either
See also xwiki.markmail.org/thread/ychoon432tugvlbm
The main problem is that FoxWiki is not supported by our dev team. Apart from this it's a very nice to have feature.
Thus we have 2 choices:
- someone volunteers to work on it and make FoxWiki work with FF and IE relatively quickly since the feature is currently broken
- we move foxwiki to contrib/ and remove that feature (ie. we could make it active only if the extension is installed for ex)
WDYT?
Thanks
-Vincent
Hi Eugen,
On Thu, Apr 15, 2010 at 2:17 PM, Colesnicov Eugen <ecolesnicov(a)gmail.com>wrote:
>
> Hi developers!
>
> According discussion about this FoxWiki & "Edit attachments" feature at
> XWiki-Dev subforum. I want to write my opinion for developers.
>
> Current situation:
> - In IE this feature working good without any additional jobs (I tested
> 2.2.4).
> - In FF - need to use FoxWiki extension (download manualy xpi-file, and
> edit
> max-version property).
> - In Chrome - "Edit attachments" - doesn't work.
>
> I have proposal about using this feature in FF. FoxWiki working, but I
> don't
> like that users MANUALY everytime should add file extention and application
> path in FoxWiki. From other side, exists some other extentions for FF (for
> example http://openwebfolder.mozdev.org/). As I understand, this extention
> adds to FF functionality of windows WebFolder WebDAV client - same as IE.
> But now, I cannot use (or try) this extention with XWiki, because XWiki
> programming code obviously use ONLY FoxWiki at FF. As I understand, If we
> will try to use openwebfolder extention - no any special code needs for
> XWiki - programming code can be same as a IE part.
>
> Other collaborative suits software also use openwebfolder extention for FF
> (see for example
>
> http://help.collab.net/index.jsp?topic=/teamforge530/action/connecttowebdav…
> ).
>
Openwebfolder has the following description:
"*openwebfolder* itself does *not* contain any platform-independant WebDAV
related code. It just adds hooks so that Microsoft's "Webfolder" WebDAV
client can be invoked in a similar way like in IE."
So this is a windows only solution. May be we should have some logic like:
if (IE) {
// Use native webdav support in IE.
} else if (FF && Win32) {
// Use openwebfolder.
} else if (FF) {
// Use FoXWiki.
}
But first someone has to evaluate if openwebfolder + FF on Win32 is better
than FoXWiki + FF on the same. Anyway, I'm not sure if above logic can be
implemented or if it is the best approach, someone has to digg a little
deep.
Just my opinion :)
- Asiri
>
> For this reason, alternative proposal: no use any special extention for
> WebDav - use standart openwebfolder extention (this extention is better
> because not need to manualy add file extentions and application paths).
> According this - need to change XWiki programming code for WebDav using in
> Firefox.
>
> I am not a specialist with XWiki programming, for this reason - sorry, if I
> write something stupid ... What do you think about my variant?
>
> --
> Best Regards
> Eugen Colesnicov
>
>
> --
> View this message in context:
> http://n2.nabble.com/FoxWiki-Edit-attachments-feature-tp4906288p4906288.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
Good morning,
I wanted to create a kind of bibliographic data base.
To do that I create a "Document" class which have some properties (title,
autor, year...) and each of its page "objects" would have an attachment (for
instance, a pdf of an scientific article) which correspond to the document.
Then, I use the Live Table to display all my class objects but I have some
problems I can't resolve... I put the code of my Live Table at the bottom of
the mail.
So, obsiously, I have a template attached to my class which contains an
object of it. My problem is when I display in my Live Table all my
"Document" class pages (with the option :
"className":"Biblio.DocumentClass"), the template is also display. I would
like it doesn't. Is there a way to do that ?
Secondly, I have a column in my Live Table to display attachment (with
"_attachments") but i don't find how to link to the download link. Indeed,
i'm not sur it's possible !! I try to put the option "link" : "view" and
"link" : "field" but the first link to the document page and the second
doesn't work.
Finally, it's about the class creation. I create a date property but I don't
want to have a default today date. I notice the field "Empty is today". But
whenever I put 0 or 1 or nothing, there always is the default today date in
the form creation...
Thank you.
Marine
My Live Table code ("TitleDoc", "Autor", "Year are properties of my
Biblio.DocumentClass) :
> #set($columns = ["TitleDoc", "Autor", "Year", "_attachments", "doc.date",
> "doc.author", "_actions"])
> #set($columnsProperties = {
> "TitleDoc" : { "type" : "text", "link" : "view"},
> "Autor" : { "type" : "text", "link" : "view"},
> "Year" : { "type" : "number", "link" : "view"},
> "_attachments" : { "type" : "none", "sortable" : "false", "link" :
> "view"},
> "doc.date" : { "type" : "text", "link" : "view"},
> "doc.auth" : { "type" : "text", "link" : "field"},
> "_actions" : { "actions": ["delete","rename"]}
> })
> #set($options = {
> "className":"Biblio.DocumentClass",
> "rowCount": 10
> })
> #livetable("BDbiblio" $columns $columnsProperties $options)
>
Hi,
I've done fast test with some people here (10 users, 7 no-XWiki users, 3
XWiki users):
2. 1/10 has read *XNiki* in option A and *XWiki* in option B; she was
no-XWiki user.
3. 1/10 has read *lambda wiki* in option A and *XWiki* in option B; she
was no-XWiki user.
3. Some no-XWiki users, 5/10 have had some problems to identify the X
both in option A and B.
4. All users consider that *wiki* is clearer in option B.
5. XWiki users read XWiki in both A and B.
Please, consider that no experimental design is under the scene! :-)
Cheers,
Ricardo
Raluca Stavro wrote:
> Hi all,
>
> How about this alternative:
> http://dev.xwiki.org/xwiki/bin/download/Community/LogoChallengeRound2/16-va….
> I think that the W is readable now.
>
> Raluca.
>
> On Wed, Apr 14, 2010 at 11:06 AM, Valdis Vītoliņš
> <valdis.vitolins(a)odo.lv> wrote:
>
>> Readability is better, but for me upper right backgoing "serif" for w
>> seems unnecessary.
>> In place of (ascii art):
>> \// \
>> /\\/\/iki
>>
>> only in this way:
>> \/
>> /\\/\/iki
>>
>> Then X can be bigger and w can be aligned with k.
>> What do you think?
>>
>> Valdis
>>
>>
>>> I completely agree with Marius, I would also add that since this is a
>>> Community project, it should have a Community logo !
>>> Since 16 has receive many votes now, and that I also agree with
>>> Vincent,
>>> Ludovic and others, it is not readable enough, I have made an
>>> alternative
>>> design: W-angle. My feeling was that the W is difficult to read, so my
>>> proposal try to keep the style and reworked it. There is also small
>>> changes
>>> in spacing, and a different powered by button.
>>>
>>> Here is almost all that was requested in a proposal with this
>>> variable:
>>> http://dev.xwiki.org/xwiki/bin/download/Community/LogoChallengeRound2/16%2D…
>>>
>>> I really hope that if the logo 16 is chosen, my proposal could help in
>>> mitigating the disappointment of those that really find it
>>> unacceptable.
>>>
>>> WDYT ?
>>>
>>> Denis
>>>
>> _______________________________________________
>> users mailing list
>> users(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/users
>>
>>
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
--
Ricardo Rodríguez
CTO
eBiotic.
Life Sciences, Data Modeling and Information Management Systems
On 04/12/2010 04:30 PM, Thibaut Camberlin wrote:
> My corrected vote is +1 for 12A.
12A has been retired and is no longer a valid option. Please choose
another one.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi devs,
Note that the 2.3 branches have been created. Don't forget to merge
your fixes in those branches and fixes for blocker bugs in:
trunk/2.2/2.3.
XE 2.3 RC1 will be released as soon as tests succeed on the continuous build.
Thanks,
JV.
On Apr 12, 2010, at 12:05 PM, jvelociter (SVN) wrote:
> Author: jvelociter
> Date: 2010-04-12 12:05:45 +0200 (Mon, 12 Apr 2010)
> New Revision: 28239
>
> Modified:
> platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/usersandgroups/usersandgroups.js
> Log:
> XWIKI-5094 Administration rights editor cannot be used in portlet mode
>
> Merged from branch 2.2
>
>
> Modified: platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/usersandgroups/usersandgroups.js
> ===================================================================
> --- platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/usersandgroups/usersandgroups.js 2010-04-12 10:04:39 UTC (rev 28238)
> +++ platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/usersandgroups/usersandgroups.js 2010-04-12 10:05:45 UTC (rev 28239)
> @@ -367,8 +367,9 @@
> var uorg = table.json.uorg;
> var allows = row.allows;
> var denys = row.denys;
> - var saveUrl = "?xpage=saverights&clsname=" + table.json.clsname + "&fullname=" + row.fullname + "&uorg=" + uorg;
>
> + var saveUrl = window.docviewurl + "?xpage=saverights&clsname=" + table.json.clsname + "&fullname=" + row.fullname + "&uorg=" + uorg;
> +
BTW can we guarantee that table.json.clsname, row.fullname and uorg don't contain any character that would need to be URL-encoded?
Thanks
-Vincent
PS: We need a URL factory on the JS side to create valid URLs with proper encoding.
[snip]
Hi
After using my Groovy based XWiki Blog I decided that I am not going to pursue this any further because of these issues:
- Groovy applications still have more limitations than Velocity making it very difficult to use as an alternative
- It is very difficult to deploy my own Groovy blog application because I have to go over several hoops to install it (content, plugins, plugin configurations)
- Most of the issues where related to Groovy based Panels which seems not to be possible
- No interest in it
Even though I think that Groovy would be a much better way to script applications like the Blog XWiki seems not to be ready to embrace it. From my point of view the entrenched usage of Velocity makes it very difficult to go beyond a simple page script in another scripting language.
Cheers
Andreas Schaefer
CEO of Madplanet.com Inc.
Email: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter; andy_mpc
AIM: schaefera(a)me.com