On Fri, Aug 3, 2012 at 1:54 AM, Suryajith Chillara <suryajith1...@gmail.com> wrote: > > I have been trying to write the frontend as a mediawiki extension but each > form has to be written very specifically
Do you want to say that one need to follow their system, structure and guidelines? > and this system as it turns out has become a pain in building and deploying. This normally happen, if we don't understand reason behind the structure or basic functioning of main application, and in this case it is mediawiki. > The process I was following: > 1. Create a tag <benchmarkform> with a hook which renders the form upon > invocation. Whenever this tag is used in the content of the wiki, the > corresponding data is rendered as needed. > 2. Action is a redirect to the same page and the action has a method which > is used as a hook and this renders the results on the same page. This is > turning out to be not so fine. What is "not so fine"? > 3. The page should be made non-editable. > 4. Deployment: Each and everytime the app has to be deployed, a page has to > be created whose content is the markup with the <benchmarkform> tag. This > could be a headache. For any one feature, it is one time, and deployment is automated through scripts, so it can't be a issue. > 5. Maintainability issues. How? > So I have decided to build another webservice than the existing webservices > which I was against in the beginning of the project and little did I know > that I would run into such issues. I am extremely sorry about that fact. > Nevertheless, I intend build a new service using a reliable webframework > like bottle(this also makes code much more maintainable.) (I've already > begun writing the base code.) I wish to have a base working setup up by 6th > August and I can totally complete it by Aug 13th. > > I would like to apologize for abrupt change in the plans and I would like to > hear from the community if that is fine by you. > > Pros: > > 1. Maintainable code > 2. Flexible framework to implement a wide range of things and porting > 3. One single language and code base > 4. Rapid development > 5. Could be extended to build and thus integrate materials database or any > other webproject > > > Cons: > 1. Another webservice to run but I shall assume complete responsibility for > the same now and later(Post SoC). You are very honest in writing all Pros and Cons, but IMO, even one single "Cons" make it less desirable. You are unable to use MediaWiki in your project in any useful manner. -- H.S.Rai ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
