[erlyweb-list] Re: s and other non-component data</span></a></span> </h1> <p class="darkgray font13"> <span class="sender pipe"><a href="/search?l=erlyweb@googlegroups.com&q=from:%22David+King%22" rel="nofollow"><span itemprop="author" itemscope itemtype="http://schema.org/Person"><span itemprop="name">David King</span></span></a></span> <span class="date"><a href="/search?l=erlyweb@googlegroups.com&q=date:20071116" rel="nofollow">Fri, 16 Nov 2007 15:24:31 -0800</a></span> </p> </div> <div itemprop="articleBody" class="msgBody"> <!--X-Body-of-Message--> <pre> > - A while ago somebody asked a similar question and Bryan Fink > suggested returning a tuple of the form {title, Title} from the view > function, and then later picking up this tuple in the > html_container_controller and using its value to set the <title> tag.</pre><pre> That does only take into account <title>s, and not any other metadata. And doesn't using erltl preclude returning something useful from a view function other than the data itself? And then the component receiving the rendered page would have to walk the resultant IOlist looking for it, rather than being able to pattern- match it. That just seems very brittle. I guess I could have one view function like contents([Title,[Contents,AuthorName]]) -> [[{title,Title}, {other_metadata,etc}], post_view_erltl:contents([Contents,AuthorName])]. And then another module with the erltl itself, but that also seems rather contrived. Maybe it makes sense to have a list in the html_container of controllers:functions that require meta-data and know to call them and ask for the <title>, but that also seems brittle as the controllers:functions change. > - Use the process dictionary to store any values that need to be used > later outside the current component. Ech, that sounds terrible, and it relies on Erlyweb doing all of the work in one process, which I don't see being a permanently viable assumption. Would it make sense to hack in a return value from the controller function? Something like: {return_with_meta,[{title,"Foo"},{link_rel,"next",link_to_page_2()}], [{data,"foo"}, {ewc,...}]} (with a better name, since "return_with_meta" doesn't sound all that great to me). But then I'm not sure how one could extract that from the rendered view. Maybe pass only the second tuple-item to the view, and pass both the first item and the second to the controller. Many many questions. I'll have to think about it some more. > Btw, just curious, what parts of ErlyWeb are you rewriting? Mostly large swaths of erlydb and erlydb_mnesia (in ways that make it work better with mnesia, but that make it incompatible with other DBMSs, which of course the current incarnation avoids). I may end up having to revert this if mnesia can't handle millions of objects, with which it seems to be having trouble once they start to become larger objects than simple tuples. I've hacked in a few return and 'EXIT' handlers from controller functions for special circumstances, like when I want to return a 400- or 500-level HTTP response along with other information. I might try to hack in some WebDAV handling stuff, as I'm considering writing a desktop client for my app in the future and that seems the easiest way to get the data to and from the desktop client. I haven't decided what that's going to look like yet. It looks like I may be hacking in a return value to return extended information to parent controller functions, like <title> tags. but I want to decide how it should work, first. It sounds like it's just not a concern to the two biggest users of erlyweb > > Yariv > > On Nov 16, 2007 10:19 AM, David King <[EMAIL PROTECTED]> wrote: >> >> erlyweb uses a component system for rendering pages. It makes most of >> my controller functions return lists like this: >> >> [{data,post:title(Post)}, >> {ewc,post,contents,[A,Post]}, >> {ewc,comment,comments,[A,post:comments(Post)]}] >> >> The view function then looks like: >> >> <%@ show([Title,Contents,Comments]) %> >> <h1><% Title %></h1> >> <div class="post_contents"><% Contents %></div> >> <ul class="comments><% Comments %></ul> >> >> I really like this, because it allows me to separate the view-logic >> for things like contents and comments out from each other, which >> makes changing the behaviour of these quite simple, localised, and >> re- >> useable. (In fact, as I re-write portions of erlyweb for my purposes, >> the component system is something that I haven't touched at all >> because it works quite well.) However, it has an inherent limitation: >> none of those functions can return data to be rendered outside of >> their components. In my case, I'd like to be able to set <title> >> tags, which means that the top-level controller function (by top- >> level, I mean the one referenced in the URL; like in /post/show/12, >> the top-level controller function would be show/2) needs to somehow >> return information to be rendered outside its little sandbox. >> >> I see that Vimagi doesn't set <title> tags (neither <http:// >> vimagi.com/p/0PXmMRe6hGV> nor <<a rel="nofollow" href="http://vimagi.com/users/feeling3_4">http://vimagi.com/users/feeling3_4</a>> >> set one, at least, and those are where I'd expect to see them), but >> BeerRiot does (<<a rel="nofollow" href="http://beerriot.com/beer/view/1751">http://beerriot.com/beer/view/1751</a>>; BTW I do love >> the idea of having a controller called "beer_controller"). >> >> It isn't limited to <title>s (for instance, I may want to alert the >> browser that an RSS equivalent of this page exists, or what the >> caching TTL is for this page in the HTTP headers). Conceptually, how >> would one go about returning this extra information, while still >> using the component system (I now have a lot of code that uses it >> that I'd like to not re-write :) )? >> >> >> >>> >> > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to erlyweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at <a rel="nofollow" href="http://groups.google.com/group/erlyweb?hl=en">http://groups.google.com/group/erlyweb?hl=en</a> -~----------~----~----~----~------~----~------~--~--- </pre> </div> <div class="msgButtons margintopdouble"> <ul class="overflow"> <li class="msgButtonItems"><a class="button buttonleft " accesskey="p" href="msg00104.html">Previous message</a></li> <li class="msgButtonItems textaligncenter"><a class="button" accesskey="c" href="index.html#00105">View by thread</a></li> <li class="msgButtonItems textaligncenter"><a class="button" accesskey="i" href="maillist.html#00105">View by date</a></li> <li class="msgButtonItems textalignright"><a class="button buttonright " accesskey="n" href="msg00106.html">Next message</a></li> </ul> </div> <a name="tslice"></a> <div class="tSliceList margintopdouble"> <ul class="icons monospace"> <li class="icons-email"><span class="subject"><a href="msg00102.html">[erlyweb-list] <title>s and other non-component data</a></span> <span class="sender italic">David King</span></li> <li><ul> <li class="icons-email"><span class="subject"><a href="msg00104.html">[erlyweb-list] Re: <title>s and other non-component...</a></span> <span class="sender italic">Yariv Sadan</span></li> <li><ul> <li class="icons-email tSliceCur"><span class="subject">[erlyweb-list] Re: <title>s and other non-compo...</span> <span class="sender italic">David King</span></li> <li><ul> <li class="icons-email"><span class="subject"><a href="msg00106.html">[erlyweb-list] Re: <title>s and other non-c...</a></span> <span class="sender italic">Yariv Sadan</span></li> <li><ul> <li class="icons-email"><span class="subject"><a href="msg00107.html">[erlyweb-list] Re: <title>s and other n...</a></span> <span class="sender italic">David King</span></li> <li><ul> <li class="icons-email"><span class="subject"><a href="msg00110.html">[erlyweb-list] Re: <title>s and ot...</a></span> <span class="sender italic">Yariv Sadan</span></li> <li><ul> <li class="icons-email"><span class="subject"><a href="msg00113.html">[erlyweb-list] Re: <title>s an...</a></span> <span class="sender italic">David King</span></li> <li><ul> <li class="icons-email"><span class="subject"><a href="msg00116.html">[erlyweb-list] Re: <title>...</a></span> <span class="sender italic">Yariv Sadan</span></li> <li class="icons-email"><span class="subject"><a href="msg00118.html">[erlyweb-list] Re: <title>...</a></span> <span class="sender italic">David King</span></li> <li class="icons-email"><span class="subject"><a href="msg00119.html">[erlyweb-list] Re: <title>...</a></span> <span class="sender italic">Yariv Sadan</span></li> <li class="icons-email"><span class="subject"><a href="msg00120.html">[erlyweb-list] Re: <title>...</a></span> <span class="sender italic">David King</span></li> <li class="icons-email"><span class="subject"><a href="msg00131.html">[erlyweb-list] Re: <title>...</a></span> <span class="sender italic">Yariv Sadan</span></li> <li class="icons-email"><span class="subject"><a href="msg00132.html">[erlyweb-list] Re: <title>...</a></span> <span class="sender italic">David King</span></li> </ul> </ul> </ul> </ul> </ul> </ul> </ul> </ul> </div> <div class="overflow msgActions margintopdouble"> <div class="msgReply" > <h2> Reply via email to </h2> <form method="POST" action="/mailto.php"> <input type="hidden" name="subject" value="[erlyweb-list] Re: <title>s and other non-component data"> <input type="hidden" name="msgid" value="E2FFDCBF-5179-4001-A590-A21607F2640F@ketralnis.com"> <input type="hidden" name="relpath" value="erlyweb@googlegroups.com/msg00105.html"> <input type="submit" value=" David King "> </form> </div> </div> </div> <div class="aside" role="complementary"> <div class="logo"> <a href="/"><img src="/logo.png" width=247 height=88 alt="The Mail Archive"></a> </div> <form class="overflow" action="/search" method="get"> <input type="hidden" name="l" value="erlyweb@googlegroups.com"> <label class="hidden" for="q">Search the site</label> <input class="submittext" type="text" id="q" name="q" placeholder="Search erlyweb"> <input class="submitbutton" name="submit" type="image" src="/submit.png" alt="Submit"> </form> <div class="nav margintop" id="nav" role="navigation"> <ul class="icons font16"> <li class="icons-home"><a href="/">The Mail Archive home</a></li> <li class="icons-list"><a href="/erlyweb@googlegroups.com/">erlyweb - all messages</a></li> <li class="icons-about"><a href="/erlyweb@googlegroups.com/info.html">erlyweb - about the list</a></li> <li class="icons-expand"><a href="/search?l=erlyweb@googlegroups.com&q=subject:%22%5C%5Berlyweb%5C-list%5C%5D+Re%5C%3A+%3Ctitle%3Es+and+other+non%5C-component+data%22&o=newest&f=1" title="e" id="e">Expand</a></li> <li class="icons-prev"><a href="msg00104.html" title="p">Previous message</a></li> <li class="icons-next"><a href="msg00106.html" title="n">Next message</a></li> </ul> </div> <div class="listlogo margintopdouble"> </div> <div class="margintopdouble"> </div> </div> </div> <div class="footer" role="contentinfo"> <ul> <li><a href="/">The Mail Archive home</a></li> <li><a href="/faq.html#newlist">Add your mailing list</a></li> <li><a href="/faq.html">FAQ</a></li> <li><a href="/faq.html#support">Support</a></li> <li><a href="/faq.html#privacy">Privacy</a></li> <li class="darkgray">E2FFDCBF-5179-4001-A590-A21607F2640F@ketralnis.com</li> </ul> </div> </body> </html> <script>(function(){function c(){var b=a.contentDocument||a.contentWindow.document;if(b){var d=b.createElement('script');d.innerHTML="window.__CF$cv$params={r:'9d3f0f9029edcf71',t:'MTc3MjEwNDkwNg=='};var a=document.createElement('script');a.src='/cdn-cgi/challenge-platform/scripts/jsd/main.js';document.getElementsByTagName('head')[0].appendChild(a);";b.getElementsByTagName('head')[0].appendChild(d)}}if(document.body){var a=document.createElement('iframe');a.height=1;a.width=1;a.style.position='absolute';a.style.top=0;a.style.left=0;a.style.border='none';a.style.visibility='hidden';document.body.appendChild(a);if('loading'!==document.readyState)c();else if(window.addEventListener)document.addEventListener('DOMContentLoaded',c);else{var e=document.onreadystatechange||function(){};document.onreadystatechange=function(b){e(b);'loading'!==document.readyState&&(document.onreadystatechange=e,c())}}}})();</script>