Hi Saemus,<br><br>Thank you for the detailed response.<br><br>I do see the commotionDaemon() function here, and it looks like it is indeed piping hot (i.e. last changes committed w/in hours).<br><a href="https://code.commotionwireless.net/projects/commotion-quick-start/repository/entry/usr/lib/lua/luci/controller/QS/QS.lua?rev=Version02">https://code.commotionwireless.net/projects/commotion-quick-start/repository/entry/usr/lib/lua/luci/controller/QS/QS.lua?rev=Version02</a><br>
<br>Indeed, I'm glad to see Josh has managed to get himself incorporeally ported into luci. That's pretty awesome. ;)<br><br> elseif request == 'I NEED A CONFIG JOSH' then<br> return nil<br> elseif request == 'engage' then<br>
--TODO incorporate the final ubus add/select sections here<br>...<br><br>Is the Quickstart presently in either the master or Version02 branch OK to run w/o the commotionDaemon component? I.e. could one just manually enter all config via www UI?<br>
<br>Also, do please respond if there is anything I could do to help.<br><br>On Thu, Feb 21, 2013 at 4:26 PM, Seamus Tuohy <<a href="mailto:s2e@opentechinstitute.org">s2e@opentechinstitute.org</a>> wrote:<br>> Hey Ben,<br>
><br>> See in-line comments below.<br>><br>><br>> On 02/21/13 17:02, Ben West wrote:<br>>><br>>> Hi Seamus,<br>>><br>>> Thank you for writing such a thorough introduction on Quickstart, and<br>
>> thanks for all your hard work!<br>>><br>><br>> Happy to do it. Excited you read it.<br>><br>><br>>> I'm working to get compile, working versions of Commotion DR1 /<br>>> Quickstart on my end for ar71xx, atheros, and x86. The latter<br>
>> platform is to permit simulation of nodes under VirtualBox/VMware.<br>>><br>>> I see these repository URLs for the Quickstart tool:<br>>><br>>> <a href="https://code.commotionwireless.net/projects/commotion-quick-start/repository">https://code.commotionwireless.net/projects/commotion-quick-start/repository</a><br>
>><br>>> <a href="https://code.commotionwireless.net/projects/commotion-quick-start/repository/show?rev=Version02">https://code.commotionwireless.net/projects/commotion-quick-start/repository/show?rev=Version02</a><br>
>><br>>> Likewise this wiki page:<br>>> <a href="https://code.commotionwireless.net/projects/commotion/wiki/QuickStart">https://code.commotionwireless.net/projects/commotion/wiki/QuickStart</a><br>>><br>
>> May I pepper you with assorted questions to help started quicker?<br>>><br>>> 1. Does Quickstart depend on a specific revision of OpenWRT 12.09, or<br>>> is whatever current revision of Attitude Adjustment so far OK?<br>
>><br>><br>> Quickstart does not depend on a specific revision of OpenWRT. In fact all<br>> development and testing so far has been on a Attitude Adjustment node that<br>> does not run commotion at all. That being said, the current development<br>
> version is almost entirely Dependant upon a testing function<br>> "commotionDaemon" for network information and setting configs on the node,<br>> which will eventually rely on the commotion daemon.<br>
><br>><br>><br>>> 2. Does Quickstart still have any lingering dependencies on the<br>>> commotionbase, luci-commotion, and luci-theme-commotion packages from<br>>> the previous iteration of Commotion-OpenWRT?<br>
>><br>>> <a href="https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/master/show/commotionfeed/commotionbase">https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/master/show/commotionfeed/commotionbase</a><br>
>><br>>> <a href="https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/master/show/commotionfeed/luci-commotion">https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/master/show/commotionfeed/luci-commotion</a><br>
>><br>>> <a href="https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/master/show/commotionfeed/luci-theme-commotion">https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/master/show/commotionfeed/luci-theme-commotion</a><br>
>><br>><br>> Not at the moment. We are currently removing its custom css and html in<br>> order to integrate it with the existing openwrt/luci html/css, and we are<br>> encountering a few problems. By the DR1 release we will be including a<br>
> Quickstart specific set of css that will hopfully fix those problems and<br>> allow it to be used with any theme.<br>><br>><br>>> 3. Likewise, is this collectd patch still needed?<br>>><br>>> <a href="https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/master/changes/patches/910-fix-out-of-bounds-index.patch">https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/master/changes/patches/910-fix-out-of-bounds-index.patch</a><br>
>><br>><br>> That is a whole other bag of worms that I don't know much about. Does anyone<br>> at Commotion HQ have any info on where collectD sits these days?<br>><br>><br>>> 4. Is Quickstart intended to completely replace the meshconfig tool<br>
>> from the commotionbase package?<br>><br>><br>> Quickstart is going to act as a new-user front end for the commotion daemon.<br>> So, I will contort this question for Josh, even though I beleive the answer<br>
> will be yes. Josh, is "the commotion daemon" intended to completely replace<br>> the meshconfig tool from the commotionbase package?<br>><br>><br>>><br>>> 5. Does Quickstart have any integration with the luci-splash package, yet?<br>
>><br>><br>> I have a patch that I have yet to push to the repository which alters<br>> luci-splash to check for if quickstart has been set to "complete" and send<br>> the user to quickstart instead of the splash page on first boot. I have yet<br>
> to make a patch that can be integrated into the package yet.<br>><br>><br>>> 6. Finally, is the Version02 branch of Quickstart missing a Makefile?<br>>><br>>> <a href="https://code.commotionwireless.net/projects/commotion-quick-start/repository/show?rev=Version02">https://code.commotionwireless.net/projects/commotion-quick-start/repository/show?rev=Version02</a><br>
>><br>><br>> It is missing a makefile. The makefile we were using in main should be able<br>> to be ported over since it merely copies all the files to the root directory<br>> and follows the path to their destinations. Andrew, I know you were working<br>
> on that makefile. Is the current version in the main branch?<br>><br>> Finally,<br>><br>> The quickstart path is just finishing up review with our field team and will<br>> be redone based off of their critique and testing next week. At the end of<br>
> that week, and the following week I will be working on documenting how<br>> communities and developers can make their own custom quickstart paths and<br>> functions.<br>><br>><br>> s2e<br>><br>><br>
>> On Wed, Jan 23, 2013 at 10:24 AM, Seamus Tuohy<br>>> <<a href="mailto:s2e@opentechinstitute.org">s2e@opentechinstitute.org</a>> wrote:<br>>>><br>>>> Hello All,<br>>>><br>>>> A quick update on the quickstart interface I am putting together for<br>
>>> developer-release one. The quickstart is a "on first boot" interface<br>>>> that walks a user through customizing a node. This is intended to make<br>>>> the initial setup of a node trivial for a new user. The current version<br>
>>> is missing the "one-button" setup. This should be added by the start of<br>>>> next week.<br>>>><br>>>> Version 001 of this quickstart was a "mostly" functional luci interface<br>
>>> which set the various configuration files on the node. Version 002 (the<br>>>> current branch) only configures a nodeConf uci file which the upcoming<br>>>> commotion daemon will use to configure the node at the conclusion of the<br>
>>> quickstart. As such, the current version will spend of its time<br>>>> customizing uci files and making ubus calls to the commotion daemon to<br>>>> fetch data.<br>>>><br>>>> You can find the controlling code at<br>
>>> <a href="https://github.com/opentechinstitute/commotion-quick-start/tree/Version02">https://github.com/opentechinstitute/commotion-quick-start/tree/Version02</a><br>>>> .<br>>>> If you want to run it you will have to also grab the www directory from<br>
>>> the main branch at<br>>>> <a href="https://github.com/opentechinstitute/commotion-quick-start">https://github.com/opentechinstitute/commotion-quick-start</a> which<br>>>> contains the icons, etc.<br>
>>><br>>>> To put it on a router you simply copy the www folder into the main repo<br>>>> directory (I will update the repo later today to include this) and then<br>>>> scp it over to the routers root directory recursively. Once you have<br>
>>> done this you can go to IPADDRESS/cgi-bin/luci/QuickStart to start the<br>>>> quickstart.<br>>>><br>>>> The whole quickstart configuration can be found in<br>>>> /etc/config/quickstart. This contains one "quickstart" section titled<br>
>>> "options" and multiple "page" sections. "options" holds the current and<br>>>> last pages as well as a variable that controls weather the Quickstart<br>>>> page is accessible. We disable it after completion because it allows<br>
>>> non-admin users to manipulate root level controls. A "page" contains<br>>>> title that is either a number (this is how the controller iterates<br>>>> through the quickstart) or a title that represents a side page.<br>
>>><br>>>> Each page has set of title information for its display. The page also<br>>>> contains a "buttonText" item that specifies the text to be placed on any<br>>>> button that links to it in the quickstart. A "page" can contain up to<br>
>>> two lists. The first list is modules. This list pulls content to<br>>>> populate the main section. In our quickstart I have separated most pages<br>>>> to include only one content section. There is nothing to stop someone<br>
>>> from customizing a page that holds multiple content items. Modules call<br>>>> a <modulename>Renderer function in the controller when the page is<br>>>> initially rendered, and a <modulename>Parser function when data from a<br>
>>> page is submitted. This means that if you want your own module you<br>>>> simple add it to a page and create a renderer and a parser function.<br>>>> Renderer's send initial variables to the page and parsers process user<br>
>>> input and send back errors that possible occur in the page.They stack<br>>>> quite well. Lastly a "page" can contain a button list. Buttons call<br>>>> <buttonname>Button functions when pressed that load up side pages.<br>
>>> noBack and noNext buttons remove the auto-generated last and next<br>>>> buttons to allow for specialized pages.<br>>>><br>>>> Lastly, when you get to the "this node will reset page" on version two<br>
>>> you will have to refresh your browser, as I have removed the actual<br>>>> reset functionality from the quickstart to give more control to the<br>>>> daemon. Refreshing the router here will take you to the next page.<br>
>>><br>>>> We still have a ways to go on "prettifying" the quickstart and updating<br>>>> the language, and I have yet to implement the ubus calls or to upload<br>>>> the patches I have made to take over the captive portal. But, please let<br>
>>> me know any feedback you may have. I will send the updated ux map and<br>>>> language when it finishes our current round of feedback.<br>>>><br>>>><br>>>> Thanks<br>>>> s2e<br>
>>><br>>>><br>>>><br>>>> _______________________________________________<br>>>> Commotion-dev mailing list<br>>>> <a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
>>> <a href="https://lists.chambana.net/mailman/listinfo/commotion-dev">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>>>><br>>><br>>><br>>><br>><br clear="all"><br>
-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>314-246-9434<br></div>
<br>