ok, controller areas

[Dru Sellers]

not sure what FUBU calls them.

/admin/controller/action

how do I put something in a sub folder?

-d

[Ryan Kelley]

You don't, you just make the URL what you want it to be. It's kind of
a pain, and I have a few other concerns in this area too

Sent from my iPhone

[Dru Sellers]

do you have anything you could share, and maybe we could talk about how to make it a convention?

when you are back on the main machine?

-d

[Ryan Kelley]

Definitley, will write some stuff up later tonight

Sent from my iPhone

[Dru Sellers]

coolio

[Ryan Kelley]

I think more importantly than having folders determining URL's is what we do with User Controls. Because I may have a BlogPostController, it has actions for New, Edit, and View. So New and Edit are /admin prefixed and View may be /BlogPost/2009/09/12/this-is-my-slug

I think the URL specification should be higher priority in the chain maybe. To me it doesn't matter if it is conventional or not because we are having to configure something on 98% of our Url's/Actions

Problem I have, which we alleviated somewhat is that I can put controls that are used by ControllerA into A's folder, but I can't use those anywhere else on another controller. So still my shared folder has 95 controls in it, just so I can use them in different controllers. I don't know what we could do, but it would sure be nice to be able to logically organize all these files.

I can't remember right now how Fubu goes out and finds controls and views, and I don't think we want to box ourselves in to strict on a "Required" Folder structure.

-Ryan

[Chad Myers]

Personally, I've been questioning the wisdom of conventional inference/wiring of URLs.  We do have patterns in our code where some things are conventional, but we end up also having a LOT of "almost the same" actions that require a one-off or two-off configuration similar to what Ryan describes.

My current thinking is that you start with the URLs you want and then map those to the actions you want executed.  Some of this wiring-up could be conventional, but most of it will end up being specified.

-Chad

[Dru Sellers]

I have no problem with it not being conventional, but some guidance around how to best do this would then be very much apperciated. :)
-d

[Chad Myers]

That's the thing. Right now, the Fubu 'trunk' is only-conventional. There is no (good) way of configuring it explicit. It's also Controller/Action-focused with URLs being inferred from the action names and such.

In the Fubu 'semodel-rewrite' branch, there is currently no configuration (I had to do redo some of the bowels/plumbing in order to allow for other options besides JUST one-model-in/one-model-out).  

I've asked for suggestions for how the new Fubu configuration should work. Raif stubbed out a few things which look good, but I haven't implemented it yet.

My original thoughts on this were to have at least three types of configuration:

1.) Full explicit (or maybe a few conventional options)

2.) Full conventional

3.) External DSL

-Chad

[Mark Nijhof]

What do you think about the suggestion I made a while back? Is that
something that looks ok to you?

-Mark

[Chad Myers]

I'm sorry :(  Which suggestion?

-Chad

[Mark Nijhof]

Thread: "Conventional configuration pseudo code" from a few months ago :)