Hi Thomas,<br><br><div><span class="gmail_quote">On 11/10/07, <b class="gmail_sendername">Thomas Richard</b> <<a href="mailto:thomas9999@gmail.com">thomas9999@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hey Belgian Rubyists,<br><br>I've just completed the book 'Agile web development in Rails' and I've<br>been playing around a bit before i start to work in my first real<br>rails application. Now while playing I came to a problem wich i might
<br>be able to solve but if I'd do it my way it would break all the Rails<br>conventions the book was been telling about. So there should be a more<br>'agile' solution to this problem.<br><br>Let me try explain the problem:
<br>The application would be build on a few big modules e.g: projects,<br>services, delivery's, stock, ...<br>Under these big modules I'd have a few smaller modules e.g: employees,<br>products, price requests, ...
</blockquote><div><br><br>What do you understand under "module"? From your explanation, it seems that you consider one module as one web page.<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The big problem now is that i would need to share the functionalirty<br>of these smaller modules between the bigger modules. The functions of<br>all the smaller modules should be exactly the same everywhere. It<br>probably has a simple solution but i can't seem to find one. The way
<br>I'd try to solve the problem is making a controller for the projects,<br>services, .. modules , but i don't know how I'd have to handle the<br>smaller ones. I could put them in different rb files and require them
<br>into the controllers but that just doesn't seem right.</blockquote><div><br><br>I'm still a bit lost here... How do the smaller modules belong to the bigger ones? Why are they put "everywhere"?<br><br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">When i was thinking about the URI's i came to a possible second<br>solution. The URI's would have to look something like
<br>app/projects/pricerequests/new<br>Now that gave me a new perspective on the case. I could actually put<br>the smaller modules into controllers and just use the greater modules<br>as dummies. They're just there to organize the smaller modules into
<br>groups. Then again, i wouldn't know how i could get something like<br>this working in rails as this would screw up the way the view system<br>works?<br><br>As you can probably see i found it hard to explain the problem but i
<br>hope any of you can make something out of this. Would be nice of<br>someone wants to discuss about this with me (in private or not). </blockquote><div><br><br>A whiteboard (or a scrap or paper) would indeed be nice, I think. But
please try to explain your problem a bit more here, I'd like to help. What does your application look like? How do you see the user flow? What are the relations between the modules?<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I<br>hope questions like these are allowed in this mailing list ;)</blockquote><div>
<br><br>That's why this list is here in the first place, isn't it?<br><br></div></div><br>-- <br>Tom Klaasen<br>10to1<br><br>