Hi, For a while, I've been meaning to edit the "Performance Python with Weave" article and make corrections/modifications. http://www.scipy.org/documentation/weave/weaveperformance.html I haven't had the time to do it so far. John Hunter just brought to my notice that these links were broken: http://www.scipy.org/documentation/weave/laplace.html http://www.scipy.org/documentation/weave/laplace.tgz I was wondering if it would be possible for members to edit the pages (or atleast some of the pages) and fix them? Ideally this is the job for a Wiki. However a lot of the content on the site is in the form of regular non-editable articles and it is not possible for a member to modify the article at all. Its probably a lot easier if members could be allowed to edit content. Alternatively it would be nice if some of the members could be allowed to edit certain sections. Something like a group of users who can add/modify content if they belong to the group. The user can email the admin to get privileges and the admin can effectively eliminate the possibility of any vandalism by removing any offending users from the group. Is this possible with Plone? Can something be done about this or is there an alternative? Thanks! regards, prabhu
Hi Prabhu, On Wed, 28 Apr 2004, Prabhu Ramachandran wrote:
Hi,
For a while, I've been meaning to edit the "Performance Python with Weave" article and make corrections/modifications.
http://www.scipy.org/documentation/weave/weaveperformance.html
I have added you to the list of managers (not sure if this is the correct role..) of this page. Try again to edit document.
I was wondering if it would be possible for members to edit the pages (or atleast some of the pages) and fix them? Ideally this is the job for a Wiki. However a lot of the content on the site is in the form of regular non-editable articles and it is not possible for a member to modify the article at all. Its probably a lot easier if members could be allowed to edit content. Alternatively it would be nice if some of the members could be allowed to edit certain sections. Something like a group of users who can add/modify content if they belong to the group. The user can email the admin to get privileges and the admin can effectively eliminate the possibility of any vandalism by removing any offending users from the group. Is this possible with Plone?
I guess it is if the above works. Pearu
Pearu Peterson wrote:
Hi Prabhu,
On Wed, 28 Apr 2004, Prabhu Ramachandran wrote:
Hi,
For a while, I've been meaning to edit the "Performance Python with Weave" article and make corrections/modifications.
http://www.scipy.org/documentation/weave/weaveperformance.html
I have added you to the list of managers (not sure if this is the correct role..) of this page. Try again to edit document.
I think we're all still trying to figure out how to give members the rights they need to make improvements to the site... One of these days we'll probably get the Plone workflow model figured out. Prabhu, if you have trouble doing what you need to do, let me know, and I'll see if I can get you the permissions you need.
"JC" == Joe Cooper <joe@enthought.com> writes:
JC> Pearu Peterson wrote: >> On Wed, 28 Apr 2004, Prabhu Ramachandran wrote: >>> For a while, I've been meaning to edit the "Performance Python >>> with Weave" article and make corrections/modifications. >>> >>> http://www.scipy.org/documentation/weave/weaveperformance.html >> >> >> I have added you to the list of managers (not sure if this is >> the correct role..) of this page. Try again to edit document. JC> I think we're all still trying to figure out how to give JC> members the rights they need to make improvements to the JC> site... One of these days we'll probably get the Plone JC> workflow model figured out. Prabhu, if you have trouble doing JC> what you need to do, let me know, and I'll see if I can get JC> you the permissions you need. Great! Thanks everyone for the help. I am able to edit the page. For now I've added new versions of the sources and updated the links on the page. I've tested the examples on my version of weave and it works fine. The only trouble is that weave has changed a bit since I wrote the article and some of the syntax is wrong currently. Editing that is going to be a pain since right now its all HTML. I'll need to re-write it as structured text. I'll get to that when I have some time. For now the links to the examples should work and the source code itself will work correctly with the latest weave. Eric, the Py::new_reference_to(...) is no longer valid. The interface for handling non-blitzed Numeric arrays has also changed. The existing weave docs use it and so do the current examples. I believe this has all changed quite a bit. Any chance you can update the weave docs? If that is not possible can you atleast send in a small update of what has changed and where. I could try to update the docs next month (after submission of the PhD). I also need to mention that VTK support is already there. I have a few questions on that but I'll ask them later. cheers, prabhu
Prabhu Ramachandran wrote:
"JC" == Joe Cooper <joe@enthought.com> writes:
JC> Pearu Peterson wrote:
On Wed, 28 Apr 2004, Prabhu Ramachandran wrote:
For a while, I've been meaning to edit the "Performance Python with Weave" article and make corrections/modifications.
http://www.scipy.org/documentation/weave/weaveperformance.html
I have added you to the list of managers (not sure if this is the correct role..) of this page. Try again to edit document.
JC> I think we're all still trying to figure out how to give JC> members the rights they need to make improvements to the JC> site... One of these days we'll probably get the Plone JC> workflow model figured out. Prabhu, if you have trouble doing JC> what you need to do, let me know, and I'll see if I can get JC> you the permissions you need.
Great! Thanks everyone for the help. I am able to edit the page. For now I've added new versions of the sources and updated the links on the page. I've tested the examples on my version of weave and it works fine.
The only trouble is that weave has changed a bit since I wrote the article and some of the syntax is wrong currently. Editing that is going to be a pain since right now its all HTML. I'll need to re-write it as structured text. I'll get to that when I have some time. For now the links to the examples should work and the source code itself will work correctly with the latest weave.
Eric, the Py::new_reference_to(...) is no longer valid. The interface for handling non-blitzed Numeric arrays has also changed. The existing weave docs use it and so do the current examples. I believe this has all changed quite a bit. Any chance you can update the weave docs? If that is not possible can you atleast send in a small update of what has changed and where. I could try to update the docs next month (after submission of the PhD). I also need to mention that VTK support is already there. I have a few questions on that but I'll ask them later.
I can't get to this right now. But, we will get it cleaned up as soon as possible. Thanks for the pointers on things that need to be fixed. eric
cheers, prabhu
_______________________________________________ Scipy-dev mailing list Scipy-dev@scipy.net http://www.scipy.net/mailman/listinfo/scipy-dev
"EJ" == eric jones <eric@enthought.com> writes:
EJ> Prabhu Ramachandran wrote: >> Eric, the Py::new_reference_to(...) is no longer valid. The >> interface for handling non-blitzed Numeric arrays has also >> changed. The existing weave docs use it and so do the current >> examples. I believe this has all changed quite a bit. Any >> chance you can update the weave docs? If that is not possible [...] EJ> I can't get to this right now. But, we will get it cleaned up EJ> as soon as possible. Thanks for the pointers on things that EJ> need to be fixed. Here is a slightly longer list of things in that case. I'm sure you know better than me but just in case you forget here is a list. :) 0. These links in the TOC are broken: http://www.scipy.org/documentation/weave/weaveusersguide.html#Passing_Variab... http://www.scipy.org/documentation/weave/weaveusersguide.html#inline_file_ar... http://www.scipy.org/documentation/weave/weaveusersguide.html#inline_callabl... http://www.scipy.org/documentation/weave/weaveusersguide.html#Customizing Conversions 1. The Py:: namespace is gone and anything related to that needs to be updated appropriately. From what I can tell SCXX is used by default now which changes the docs all over the place. 2. Py::new_reference_to is also gone and its not clear what one should do to return a float/int or even a user defined type. 3. Using non-blitz arrays is not documented. From what I can see this is what the user needs to know: # Python a = Numeric.ones(10, 'd') # Inlined C int* Na = a_array->dimensions; // a.shape int* Sa = a_array->strides; // strides int Da = a_array->nd; // number of dimensions double* a (double*) u_array->data; // the actual data. 4. The type_factories keyword arg to inline is gone it is now called type_converters. The keyword list probably needs to be checked as well. The section on "Customizing Conversions" mentions that the default converters are in ext_tools.py. They are actually in converters.py. 5. VTK and swig2 support need to be documented. I would not mind writing these sections when I get some time. I'll let you know when this does happen. 6. Examples and possibly tests need to be updated. cheers, prabhu
On Wed, 28 Apr 2004, Prabhu Ramachandran wrote:
Can something be done about this or is there an alternative?
Actually I like the way how a similar issue was resolved for "Building SciPy on Mac OSX" document. That is, the non-editable area contains a link to a document in members scipy homepage. As a result, the authors can freely edit their contributions (I'll presume that scipy managers can also edit members documentations, e.g. fixing typos etc) without asking permissions for every small change.. Pearu
Pearu Peterson wrote:
On Wed, 28 Apr 2004, Prabhu Ramachandran wrote:
Can something be done about this or is there an alternative?
Actually I like the way how a similar issue was resolved for "Building SciPy on Mac OSX" document. That is, the non-editable area contains a link to a document in members scipy homepage. As a result, the authors can freely edit their contributions (I'll presume that scipy managers can also edit members documentations, e.g. fixing typos etc) without asking permissions for every small change..
Yes...and I think that's probably the method the Plone folks were invisioning. Though it does require a bit of work to make sure the new documents get linked to from the main pages, where they will be found by users.
Pearu Peterson wrote:
On Wed, 28 Apr 2004, Prabhu Ramachandran wrote:
Can something be done about this or is there an alternative?
Actually I like the way how a similar issue was resolved for "Building SciPy on Mac OSX" document. That is, the non-editable area contains a link to a document in members scipy homepage. As a result, the authors can freely edit their contributions (I'll presume that scipy managers can also edit members documentations, e.g. fixing typos etc) without asking permissions for every small change..
The only problem was that the author of the Mac OSX document didn't have edit access to the document once it was published. We need to find a way to let authors fully control their documents, even after publication. If we can make that change, I think this scheme will work fine. It might eventually get to be a headache to have documents spread all across member's pages, but "too many contributions" would be a good problem to have. Prabhu's document was a special case because it was migrated from the old site, so he wasn't the person who created it on the new site. (And in the migration rush, some pieces got left behind -- sorry about that.) That won't be an issue for new documents going forward. --Janet
participants (5)
-
eric jones -
Janet Swisher -
Joe Cooper -
Pearu Peterson -
Prabhu Ramachandran