Here is what transpired on #maypole leading to the new and exciting
topic of Maypole Ribbons. Some preliminary and OT things snipped out
for brevity and clarity.

<snip>

* teejay likes to think of mixed control/config as a fuzzy 'application'
<teejay> but Maypole::Application is confusingly used for plugins and stuff
<davebaird> Like, you want a generic search, that can send a search to
one of a number of tables. Where's do you put the code to dispatch the
search? In the 'model'.
<pjsz> No. in the controller.
<pjsz> I mean i want to .
<davebaird> Precisely. So the Maypole model is in fact the controller.
Part of it.
* teejay thought Model meant schema and data
<teejay> which is a model of your entities
<pjsz> Right.  We get by with imperfect structure and separations of concerns.
<davebaird> Hmm. I think of it more as the domain part of the
application - schema, data, plus behaviour of those bits.
<pjsz> I think any easy to use and flexible framework will be a little fuzzy.
<davebaird> Yes.
<pjsz> But my experience is very limited.
* teejay likes the idea of calling inbetween bits 'ribbons'
<teejay> i.e. something that isn't clearly M, V or C
<davebaird> I like that a lot!
<teejay> Not sure how it would work
<teejay> handy for dumping non-table specific model stuff in I suppose
<teejay> and also plugins
<davebaird> There's also the fact that as developers of the thing, we
spend a lot of time at the interfaces, getting the M to talk to the V
and the C to send messages to the M
<teejay> indeed
<teejay> that would be what we should call ribbons
<teejay> the interconnecty bits
<davebaird> I like it.
<teejay> plugins are plugins - ought to really have a proper plugin
architecture and namespace, but can worry about that later
<teejay> cool
<pjsz> Like could they be global variables?
<teejay> we have a name, and it describes something, how it work?
<teejay> :)
<teejay> Could have Application Level variables
<pjsz> I would like a way for $r to be availabe any time I want it.
<davebaird> Where is it not?
<pjsz> Without having to pass it to a function. Like you get in
standare apps. Modperl
<teejay> pjsz, ick!
<davebaird> I wanted an instance() method a while back.
<teejay> that makes sense
<davebaird> Couldn't hack it under mod_perl though.
<teejay> I think you can the current request in mod_perl somehow
<pjsz> Yeah. Thats what I want too. I forget to pass $r to a method
all the time.
<teejay> no reason we can't use something similar to what mod_perl does
<pjsz> Also , if you write a method and dont think you need it, then
decide you need after using it 1000 times, you have a lot of code to
change.
<teejay> can you guys email about this as I have to go home and do
this freelance work
<pjsz> A perfect example i guess would be AsForm.
<snip>
<pjsz> Some methods could do more if they had $r accessible.
<teejay> yes
<davebaird> I'll start a 2.12/3.0 wishlist
<teejay> that makes sense - can you email me some examples
<teejay> davebaird, cool - I added something about adopt to rt.cpan,
can you include that
<davebaird> OK
<teejay> also integrating Sweet into the CDBI model, I don't think we
have time to include it in 2.11

<snip>

<teejay> right home time
<davebaird> see ya
<-- teejay has quit (Quit: Leaving)
<pjsz> hey dave.  To me it seems icky to have to pass $r around in my
model. Does that feel natural to you?
<davebaird> Kind of does, but that's maybe from mod_perl programming.
I never got in the habit of using Apache::Request->instance.
<davebaird> The thing that I sometimes miss is access to the config
object in the model, if the request isn't available.
<davebaird> OK, I've got to get back to boning up on DBI, I'll be
around tomorrow.
<pjsz> Right. That is one of the main things i miss too. config,
<pjsz> hey dave.  To me it seems icky to have to pass $r around in my
model. Does that feel natural to you?
<davebaird> Kind of does, but that's maybe from mod_perl programming.
I never got in the habit of using Apache::Request->instance.
<davebaird> The thing that I sometimes miss is access to the config
object in the model, if the request isn't available.
<davebaird> OK, I've got to get back to boning up on DBI, I'll be
around tomorrow.

To add to that,
<pjsz> I need to know how to make and parse a uri sometimes when I do
not have $r accessible.

 So Maypole needs ´Ribbons'  as Aaron aptly named them to  tie
everything together by feeding the various components the information
they need to function within the application.   Does that sound about
right?

"we have a name, and it describes something, how it work?"

Cheers,



--
pjs


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Maypole-devel mailing list
Maypole-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/maypole-devel

Reply via email to