I've been away for quite some time and just getting back into FlexWiki, so
apologies if I've missed a few points along the way.
As I understand it, we have two potential file attachment solutions, one is
ready now, but is an addition to the Web application only and does not
integrate with the new security model, but still requires the 2.0 branch as
it's basis. The second is not ready yet, but integrates into the core and
"plays nicely" with the new security model.
On the basis of this, my "two cents" are as follows:
Include the "ready now" option in the 2.0 release now because file
attachments are a feature that the user community have been clamouring after
for quite some time. We should heavily comment that this feature does not
adhere to the new security model and turn it off by default.
At some point in the future, preferably not too far down the line, we
replace it with the core-integrated version instead.
Derek <http://flexwiki.com/default.aspx/FlexWiki/DerekLakin.html>.
On 7/24/07, Pascal Normandin <[EMAIL PROTECTED]>
wrote:
Like it was said before I also think it would be best to put John's code
in
the branch only especially if we dont plan to be backward compatible on
this
feature.
But this brings me another question, whether it should be part or not of a
flexwiki release. I find it quite unusual to decide to add a feature when
we know up front that it will not be supported in a near future version,
especially when it comes to user documents/work. In my opinion if WebApp
level attachment is added to a fw release then it should be supported in
the
next version in order to be fair with the users and IT Pros that decides
to
go with FW. So that brings two choices, either we create a tool to
convert
the existing attachments or FW supports 2 kinds of attachments ( WebApp
level and Core level ).
BTW, I also think it's weird to create a new core that's more secure than
ever and add another feature that do not respect the core policies. It's
my
first participation to an open source project so maybe my thoughts are too
enterprise oriented...
I truly understand the need to add this feature as soon as possible
(that's
why I decided to work on it) but I just want to make sure we make the
right
move on this. I really think it's a good value for FW and I like how it
looks but I'm just not sure it should be published by FW.
I'm sorry to bring this kind of questions at this stage and I hope is was
not discussed earlier.
If it's incorporated, then I also think it should be part of a branch only
and the package should come with huge warnings.
John, I would really like to see how you add a new attachment. Unless I
missed something I was unable to see how from the 3 links you sent.
Pascal
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
