It is true that development was halted. I had an to leave the project for a while due to work issues, I was seeking new employment as my current employer SUCKS! But, things here at work straightened themselves out. I have restarted work on the APP and will release the source code for the newest version in the next week or two. Until I release the new version, which is a complete redesign, I can give you a look at the old code and resources used to build the initial database import. Below is a URL to my personal git repo I use to release that source.
http://git.shadowbranch.com The source is the current source running on the APP page. This is ment to plug into my current CMS. But, I have begun rewriting it to utilize classes within PHP, which were not available at the time of the initial writing of my CMS. The new version will be easier to use and far more generic. Please view the source if you want. Any and all ideas will be greatly appreciated. I'm unable to send mail from my work due to outbound firewall rules to prevent virus propagation. So, I must logon to my webmail, which I hate doing. But there is my point of view. BTW, the database structure is ment to be agnostic and should work on any compatible SQL server. On Tue, 15 Mar 2011 18:23:26 -0300, Eduardo Martins Lopes wrote: Hello guys, I've read the meeting log and found out that the APP development is halted because the responsible is currently unreachable. Unfortunatelly i dont have any php skills but I could, following the wiki guidelines, work on something over Django. The history behind this idea is the following: - several days ago, some guys from the AL Brazil started to discuss the viability to gather themselves and develop a successor of the current AUR. When we brought the idea to the upstream list, they kindly asked us to work on the current AUR bugs reported on the tracker. Because it is written in PHP and no one of us (at least those who had the time to get involved) is profficient on it, the team ended up disbanding in the belief that it would be a fruitless effort. I believe that, as a team, we could achieve the goal. The unfortunate is that it would be written in python. Using django as the framework is somewhat preferable to some of them, but i believe it's discussable since the system shouldnt be much complex. As a side note, the entries could have also one extra field to flag them about their urgency to be upgraded by the users (on a security criteria for example). I would like to ask some opinions on this matter, what you guys think of it, it's desirable something like that and if i could begin assembling the team again. Regards, -- Eduardo Martins Lopes Laboratory of Theoretical Chemistry Universidade Federal de São Carlos, SP - Brazil
_______________________________________________ ArchServer Project General Mail List Post messages to: [email protected] Administer your subscription: http://lists.archserver.org/listinfo/general
