How about having a generic demo component

[Tony Atkins]

Hi, Michelle:

There are no formal plans that I'm aware of.  There is some work that would
need to be done to make this possible, mainly adding the ability to load an
initial "starting point" per topic.  Once that is done, someone would need
to actually create the "starting point" for each topic.    Given that many
of our tutorials and documentation already contain examples, there might be
room to reuse some of those (and to add tests for our example code, which
would be a big improvement).

I'll bring up the topic in tonight's architecture team meeting as well, but
if anyone has time and interest in working on, please reach out.  If there
are at least a few people who are willing to contribute sandbox content,
I'm happy to kick things off by pushing the work I did on the sandbox into
a shared repository, and working the "starting point" loading code.

Cheers,



Tony

On Tue, Jul 5, 2016 at 8:40 PM, Michelle Brennan <nachtigallen at gmail.com>
wrote:

> Has there been discussion of making a hosted version of this sandbox
> available for folks as part of the Infusion developer documentation, or on
> the Fluid Infusion project web page?
>
> It seems like this could be super helpful for getting new devs up to
> speed.
>
> Michelle
>
> On Mon, Jul 4, 2016 at 3:19 AM, Tony Atkins <tony at raisingthefloor.org>
> wrote:
>
>> Hi, Dinuka:
>>
>> Earlier in my own learning process, I worked on something similar, a
>> sandbox for working with a Fluid component:
>>
>> https://github.com/the-t-in-rtf/fluid-sandbox
>>
>> That sandbox will let you make configuration changes to a component and
>> see the changes on screen.  It works for model changes, events, and view
>> components at the moment.
>>
>> If you have a little time to collaborate and can think of topics that
>> were hard to learn, I'm happy to set up a couple of pairing sessions and
>> work on some live tutorials together.
>>
>> Cheers,
>>
>>
>> Tony
>>
>> On Fri, Jul 1, 2016 at 2:15 PM, Dinuka Desilva <l.dinukadesilva at gmail.com
>> > wrote:
>>
>>> Hi all,
>>>
>>> When I go through infusion documentation, i felt like it's quit
>>> difficult to get a clear understanding of the infusion syntax and
>>> components since most of them are textual descriptions. Also I felt even
>>> lazy when I have to setup everything when I wanted to try out something.
>>> Actually I really had a need of having a live example available in the
>>> documentations.
>>>
>>> I had the same need even for my GSOC project and I came up with kind of
>>> an implementation like which is in this page
>>> http://dinukadesilva.github.io/music-ctrls/demo/piano.html.
>>>
>>> As a starting point of improving documentation pages, I think it would
>>> be great having a generic component which is capable in generating a live
>>> editor and a preview for a given code sample. So, that we can have this
>>> integrated into our documentations as well.
>>>
>>> Also using this, we can build a library which generates demo pages for
>>> front end libraries which expands to another project.
>>>
>>> Let me know your thoughts......
>>>
>>> Thanks
>>>
>>>
>>> _______________________________________________________
>>> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
>>> To unsubscribe, change settings or access archives,
>>> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>>>
>>
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
>> To unsubscribe, change settings or access archives,
>> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20160706/3c55bb6d/attachment.htm>