Why two pieform directories?

Bug #1434316 reported by Robert Lyon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Confirmed
Low
Unassigned

Bug Description

Currently the basic pieform elements information lives in:

htdocs/lib/pieforms/pieform/

but there are also pieform elements that live in
htdocs/lib/forms/

Why do we need to have them in two places?

I can imagine that there might have been a reason to keep the pieform plugin separate from custom pieform elements but seeing as mahara pieform is really a fork of the original this seperation is not needed within mahara.

Revision history for this message
Robert Lyon (robertl-9) wrote :

This would be good to sort out for 15.10

Changed in mahara:
milestone: none → 15.10.0
importance: Undecided → Low
Revision history for this message
Aaron Wells (u-aaronw) wrote :

Yeah, it's as you say. Way back when, the Mahara team destribute Pieforms as a separate library from Mahara. http://pieforms.sourceforge.net/doc/html/

So, we separated out the "custom" parts of Pieform as used in Mahara, from the standard parts. But I think after Nigel left Catalyst, we stopped trying to support Pieforms as a standalone forms library, so you're probably right, we're probably better off merging the "custom" and "standard" stuff now.

description: updated
Aaron Wells (u-aaronw)
Changed in mahara:
milestone: 15.10.0 → 16.04.0
status: New → Confirmed
Aaron Wells (u-aaronw)
Changed in mahara:
milestone: 16.04.0 → 16.10.0
Robert Lyon (robertl-9)
Changed in mahara:
milestone: 16.10.0 → 16.10.1
Robert Lyon (robertl-9)
Changed in mahara:
milestone: 16.10.1 → 17.04.0
tags: added: pieforms
Changed in mahara:
milestone: 17.04.0 → 17.10.0
Robert Lyon (robertl-9)
Changed in mahara:
milestone: 17.10.0 → 18.04.0
Robert Lyon (robertl-9)
Changed in mahara:
milestone: 18.04.0 → 18.10.0
tags: added: code-cleanup
Changed in mahara:
milestone: 18.10.0 → none
Lisa Seeto (lisaseeto)
tags: added: refactoring
removed: code-cleanup
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.