<html><head></head><body style="font-size: 10pt; font-family: Verdana,Arial,Helvetica,sans-serif;">On Dec 5, 2011 09:48 "John Schinnerer" <a href="mailto:john@eco-living.net"><john@eco-living.net></a> wrote:<br><blockquote type="cite">On 12/04/2011 09:56 PM, Fernando Martins wrote:<blockquote type="cite">On 12/04/2011 09:31 PM, John Schinnerer wrote:<blockquote type="cite">In any case, this looks (to me anyhow) like a very object-oriented<br>system you are modeling so an object oriented approach and language<br>would seem most suitable.</blockquote><br>And how would you create (and update) objects in Python for:<br><br>"at least 500 tools as of now, and it is bound to grow in the future as<br>newer tools are introduced. Existing tools will also have version updates.<br><br>Each tool, on average, has at least 100 properties that define the tool.<br>Some of them have as high as 1000 unique properties."</blockquote><br>How familiar are you with OOP?<br><br></blockquote>I think you are confusing me with the OP. And you did not answer my question. Are you recommending that a programmer codes all these objects by hand in Python? <br><br>The know-how of what constitutes a tool, their properties and even the tool selection criteria is not developer know-how. Therefore, this information should be defined outside the program in way that the tool expert(s) can manage it. Which leads us to some storage solution, an RDB being the most common. <br><br>Since, as I pointed out before, SQL most likely would not be able to do the tool selection alone, Python would merely load the data from the external source and create objects and expertise on the fly.<br><br>Anyway, I agree with you that the main issue does not seem to be the web publishing solution, but rather how to represent the tool information and how to do tool selection, which is off-topic.<br><br>Regards,<br>Fernando<br></body></html>