I thought I saw docs out there.... https://github.com/Behavior-UI/behavior-ui/tree/master/js/Docs
Are those the correct ones? Thanks, Jon On Tuesday, June 24, 2014 2:59:28 PM UTC-7, Nutron wrote: > > It's based on the pro version, but the only things that absolutely require > it are the select elements (a DOM replacement for the native select > controls) and the charts (and those mostly work w/o flat-ui, they have one > small dependency that could be mitigated easily). > > What's missing that would make it infinitely easier for you to adopt it is > the docs themselves. You really aren't going to get far just reading the > source. I'll try and get something on github before the end of the week if > I can. If not, we can maybe come up with a creative way for you to view > them within our system. > > -a > > > On Tue, Jun 24, 2014 at 2:18 PM, Jonathan Bomgardner <jo...@comcast.net > <javascript:>> wrote: > >> I'm starting the backend in earnest this week. I hope to get moving on >> the frontend late in the week or early next if possible. I took a look >> through the Github repo (at least cursory) and it looks like it would have >> most of what I need with only a few exceptions (I'm actually pretty excited >> to dive into learning Behavior and all the goodies that come with it). Is >> most everything needed to get started at least in the repo? Also, what >> version of the Flat UI is this based on - the free version or the pro? >> >> Thanks, >> Jon >> >> >> On Tuesday, June 24, 2014 12:19:27 PM UTC-7, Nutron wrote: >> >>> The JS is all there. It's built on top of Bootstrap and, optionally, >>> Flat-UI (http://designmodo.github.io/Flat-UI/ >>> <http://www.google.com/url?q=http%3A%2F%2Fdesignmodo.github.io%2FFlat-UI%2F&sa=D&sntz=1&usg=AFQjCNGPuranqv5V5CRuAS403_CDVFwLdA>) >>> >>> (and HighCharts if you want the charts). If I'm honest, we're still a few >>> weeks before we have the website up with all the demos and docs, most of >>> which exist but the application that runs it is currently internal to us. >>> What's your timeline? I could, in theory, try and get you access to the >>> internal tools so that you can see the documentation and demos as it >>> currently stands (basically, it's kind of bound up within our proprietary >>> application and needs to be pushed out). Maybe you could help us with the >>> work of pulling it apart... >>> >>> -a >>> >>> >>> On Tue, Jun 24, 2014 at 11:53 AM, Jonathan Bomgardner <jo...@comcast.net >>> > wrote: >>> >>>> Aaron, >>>> >>>> Any thoughts on when the UI stuff might happen? I'm starting a project >>>> and would love to use this for the UI. If it works out and gets >>>> open-sourced I would also, most likely, be interested in contributing >>>> (after I get a good handle on it). >>>> >>>> Thanks, >>>> Jon Bomgardner >>>> >>>> >>>> On Monday, June 23, 2014 12:02:54 PM UTC-7, Nutron wrote: >>>> >>>>> Allo. >>>>> >>>>> There's no reason that behavior wouldn't work with custom tags, though >>>>> it's not designed to work with them as semantic replacements for the >>>>> behavior listing itself. For example: >>>>> >>>>> <foo> I'm a foo </foo> >>>>> >>>>> wouldn't translate into Behavior instantiating it as a Foo. Instead >>>>> you'd have to do: >>>>> >>>>> <foo data-behavior="Foo"> I'm a foo </foo> >>>>> >>>>> This is ideal for two big reasons: >>>>> >>>>> - You might have more than one behavior for the tag (both >>>>> Form.Request and Form.Validator, for example) >>>>> - You only have to do one DOM search to find them all >>>>> ($$('[data-behavior]')). This search is far more scalable than having >>>>> to do >>>>> a DOM search for each behavior you write. >>>>> >>>>> On an unrelated note, I've been working towards open-sourcing our UI >>>>> kit here where I work. There's still a lot of work to do (we have a bunch >>>>> of demos we hope to get online as well as docs and css/less files that >>>>> accompany them), but you can at least see what's in it now: >>>>> >>>>> https://github.com/Behavior-UI/behavior-ui/tree/master/js/Source >>>>> >>>>> -aaron >>>>> >>>>> >>>>> >>>>> On Mon, Jun 23, 2014 at 11:21 AM, Eric Patrick <patric...@gmail.com> >>>>> wrote: >>>>> >>>>>> Has anyone experimented with porting Aaron's behaviors >>>>>> <http://www.clientcide.com/code-releases/bootstrap-3-0-clientcide-3-1-0-behavior-1-3-0-and-more-behaviors-1-0-8/> >>>>>> to >>>>>> HTML5 custom tags >>>>>> <http://www.html5rocks.com/en/tutorials/webcomponents/customelements/> >>>>>> ? >>>>>> >>>>>> Our toolset targets business 'power users' who are not js experts, >>>>>> but do learn basic markup. I've found behaviors are a very powerful >>>>>> tool >>>>>> in enabling this user base to achieve things that normally require >>>>>> 'traditional' coding. >>>>>> >>>>>> However, we also have client shops with JS expertise (usually >>>>>> jQuery), and I am weighing porting our custom behaviors to HTML5 custom >>>>>> tags, and allowing JS devs to create new custom tags following a similar >>>>>> structure using jQuery, instead of requiring MooTools. >>>>>> >>>>>> (I continue to love Moo; just trying to leverage existing knowledge >>>>>> bases out there. I'm in an enviable position of generally dictating the >>>>>> browser to our user base, so I get to ensure an evergreen >>>>>> <http://tomdale.net/2013/05/evergreen-browsers/> browser.) >>>>>> >>>>>> Anyway, just wondering if anyone on this list has weighed pros and >>>>>> cons of such an approach, of if you might be interested if I just put >>>>>> this >>>>>> in GIT for joint development? >>>>>> >>>>>> -- >>>>>> >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "MooTools Users" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to mootools-user...@googlegroups.com. >>>>>> >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "MooTools Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to mootools-user...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "MooTools Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to mootools-user...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- You received this message because you are subscribed to the Google Groups "MooTools Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mootools-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
