FS#2972 - Separating engine code from interface

Attached to Project: AUR web interface
Opened by Jaroslaw Swierczynski (swiergot) - Monday, 18 July 2005, 16:09 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 03 October 2009, 21:25 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To Jaroslaw Swierczynski (swiergot)
Loui Chang (louipc)
Callan Barrett (wizzomafizzo)
Architecture All
Severity Medium
Priority Normal
Reported Version 1.1
Due in Version 2.0.0
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I think that further development of AUR will be getting harder and harder as the code grows. In my opinion we should separate code from interface as soon as possible, perhaps in version 2.0. I think it will be the best to use XSLT. It will require some work but when it's done, everything will go much more smoothly. What do you think?
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 03 October 2009, 21:25 GMT
Reason for closing:  None
Additional comments about closing:  Old ticket. Aur2 has been off and on forever. Maybe just close this ticket?
Comment by Simo Leone (neotuli) - Friday, 12 August 2005, 04:25 GMT
That and take advantage of php5. Do we have a date for breaking ground on 2.0 yet?
Comment by Jaroslaw Swierczynski (swiergot) - Friday, 12 August 2005, 07:01 GMT
No, as far as I know. But we are going to have an AUR dev meeting when Paul is back.
Comment by Simo Leone (neotuli) - Wednesday, 19 October 2005, 00:46 GMT
I'm just going to start moving on this, I'm going to have time opening up in the next two weeks and from there on out for several months. I'll be branching the code, so we can continue to make fixes/improve the main codebase while completely mucking with a copy of it. We need to find a way to coordinate on work, perhaps just check it in with a certain file or something. Anyhow, letting ya know.

Loading...