<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">The frontend is an appliance. The backend is a server, and should be<br>
looked at as such. That includes being able to configure it over a<br>
network without having to stuff around.<br>
<div class="im"><br></div></blockquote><div>My view is, the back/frontend are on the same system in your living room. A complete entertainment appliance.<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> Now, I realize, that BrowserBasedSetup is in it's infancy. However what<br>
> immediately comes to mind is instead of running mythtv-setup which I can<br>
> fully control with a just a remote, I'll have to launch a browser. Will<br>
> MythBrowser work? Will it work well with just a remote? If I have to go to<br>
> another system to connect to the web server running on the backend, instead<br>
> of making it simpler, another layer of complexity has been added to setup<br>
> process.<br>
<br>
</div>Why the heck would you WANT to run Setup with just a remote, though?<br>
There's things to type, long lists to traverse, long paths that don't<br>
lend themselves to being displayed on a 10' interface - if your<br>
Mythboxen + TV is your only computer, I can see what you're getting<br>
at, but I can't imagine that being the case for anyone at this point.<br>
<div class="im"><br></div></blockquote><div>Again, appliance. Most (if not all) of the items that would require long paths, etc. we already setup with LinHES. So all one would need is a remote.<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> Granted it is a rarity that one should have to run mythtv-setup, moving to<br>
> an all browser based setup seems short sighted. Whatever issues exist in<br>
> setting up MythTV (distros aside), should be resolved in mythtv-setup. If<br>
> desired, a broswer based setup should complement mythtv-setup not, replace<br>
> it.<br>
<br>
</div>Non sequitur.....I'm not sure how moving a rarely used tool to a<br>
browser is an obvious backwards step? Imagine how much less painful<br>
the channel editor could be....<br>
<br></blockquote><div>Robert has already cleared this up for me... <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
- Chris<br>
<div><div></div><br></div></blockquote></div><br>-- <br>Enjoy the day,<br><br>Cecil<br>