Re: Community Meeting ( Jan 25 ): An artifact to aid the design of 3D printed audio-tactile graphics for blind students: a Ph.D. research

lt;https://wiki.fluidproject.org/display/fluid/Community+workshops+and+design+crits> > wiki > page. I’ve fixed a broken link to the Presentation on the wiki page as well. > > Thanks > Justin > > On Jan 28, 2022, at 12:32 PM, Tony Atkins > wrote: > > Hi, Justin. >

Re: Community Meeting ( Jan 25 ): An artifact to aid the design of 3D printed audio-tactile graphics for blind students: a Ph.D. research

Hi, Justin. I get an error when trying to open the attachment. Also, was there a recording of the presentation made? T On Mon, 24 Jan 2022 at 14:17, Justin Obara wrote: > At this week’s Community Meeting > >

Re: Sub-task fields displayed in JIRA.

Hi, All. As it would help us on the C2LC team and I haven't heard any objections, I plan to add the issue key to the sub-tasks table (and hide the sub-task icons) tomorrow. If you're just catching up, there's still time to say something. Cheers, Tony On Tue, 19 Oct 2021 at 17:

Sub-task fields displayed in JIRA.

Hi, All. In our recent usage of sub-tasks on our shared JIRA instance , we have been lamenting the lack of an issue key when viewing the sub-tasks of an issue, as illustrated here: [image: Screenshot 2021-10-19 at 16.38.23.png] (To see the table in context, chec

Re: GSoC update and retrospective

Hi, All. A few thoughts: > >- Regarding GSoC 2020 (and past iterations if you like) > - What did we do well? > - What can we do better? > - What are ways we can improve? > > Although there was a lot of time required for the community bonding and application period, I was ve

Re: Stylesheet linting

for the information, Tony. This is great. > > It will be really useful to document this feature in the > fluid-grunt-lint-all README. > > On Sep 28, 2020, at 5:19 AM, Tony Atkins wrote: > > Hi, Cindy. > > When working on the plugin, I explicitly wanted to make sure that it was &

Re: Stylesheet linting

t and where to find the configuration. > > Thanks > Justin > > On Sep 28, 2020, at 5:19 AM, Tony Atkins wrote: > > Hi, Cindy. > > When working on the plugin, I explicitly wanted to make sure that it was > possible to configure settings per project. As an example, her

Re: Stylesheet linting

Hi, Cindy. When working on the plugin, I explicitly wanted to make sure that it was possible to configure settings per project. As an example, here is the test fixture I use to confirm that I can pass a custom configuration option to each of the tasks that fluid-grunt-lint-all currently handles:

Re: Issue tracking

allows for > versioning, milestones and etc to be specific to the code base being > released/developed. > > I’m curious to hear more of your thoughts, especially because you’ve used > both systems. Also please let me know if there are workarounds or workflows > to address the issues

Re: Issue tracking

Hi, Justin. When working on the GPII JIRA instance I simply set up a component for each repository and tracked things in the main GPII project. We might do something similar, handle them as components within the FLUID project on issues.fluidproject.org. Particularly for the plugins used in linti

Re: GitHub Actions

Hi, Gio. Great to hear this. I know we could all work our way through the documentation and experiment with our own projects in time, but It'd be great for maintainers in the community to save time by learning from what you had to do. Would you be able to briefly write up what you had to do or p

Re: GSOC Proposal

". > > I had been maintaining a constant feedback loop with *Mr. Tony Atkins* > regarding this project and have hence included a proposal with 2 > subsections as we had discussed. I have however stopped receiving any > communication from him for over a month now and have notice

Re: GSoC'20 : Using a Game Controller as a Navigation Aid

Hi, Nakul. Thanks for posting. I wanted to comment a bit on your ideas about using/enabling search, especially voice search. It's an interesting addition to the core idea, but does add a requirement for both end users and the implementation. End users have to have a microphone. The implementers

Re: GSoC

Hi, Yash. First, I wanted to comment on the difficulties you mention with IRC, which is a common problem for new community members. The IRC channel is a real-time means of communicating with the community, and you'll see the most responsive feedback if you use the channel during the hours when pe

Re: My experience with Keyboard on Browsing Web

Hi, Mohit. Thanks for taking the time to write up your experience. As you pointed out, power users who prefer keyboard shortcuts can more easliy use sites that can be easily navigated by keyboard. This is a nice illustration of how it's possible to make something that benefits multiple groups.

Re: Discussion regarding the project "Using a Game Controller as a Navigation Aid"

Hi, Neetigya. Thanks for getting in touch, and for going through the exercise. Quite a few candidates have had similar ideas about using mouse navigation. This may be a good addition to my original concept, which was more concerned with keyboard navigation. One of things that inspired me to wri

Re: GSoC - Using a Game Controller as a Navigation Aid

Hi, Mohit. Sorry for the delay in responding, the other mentors and I needed time to talk about a few things. Probably the best place to start is by familiarising yourself with our community and its practices, and going through the rest of the material here: https://wiki.fluidproject.org/display

Re: Enabling Github Issues for Infusion project

Hi, All: To answer Colin's question, there is a third party plugin that is meant to add support for logging into to JIRA using GitHub credentials: https://marketplace.atlassian.com/apps/1211397/openid-authentication-for-jira?hosting=server&tab=overview It's free for open source and available for

Re: Evaluating options for static site searching.

#x27;re interested, you can try it out by: 1. Checking out the branch associated with the pull. 2. Running npm install 3. Running npm run docpad. 4. Opening the docpad URL in a browser. Feel free to comment here or on the pull if you have questions, concerns or ideas. Cheers, Tony

Re: Evaluating options for static site searching.

ggles). > > > > There are a few examples of integrating both Fuse and Lunr with Hugo (the > direction the IDRC has been going lately for static sites) here that may > usefully inform this discussion: > https://gist.github.com/eddiewebb/735feb48f50f0ddd65ae5606a1cb41ae > > &

Evaluating options for static site searching.

Hi, All. This week I took a few minutes to evaluate a few options for searching static sites (like the Infusion documentation) and wrote up my experiences as a technology evaluation on the GPII wiki: https://wiki.gpii.net/w/Technology_Evaluation_-_Static_Site_Search As this issue affects both th

Re: ndb

Thanks, Gio! This looks like a promising alternative to node-inspector, which I have used in the past to troubleshoot problems in VMs (where I don't have an IDE or other tools). I'll have to give it a try. Cheers, Tony On 21 July 2018 at 16:05, Tirloni, Giovanni wrote: > https://github.com/

Re: CLA service for Fluid GitHub repos

Hi, Avtar: I took at look at their docs and presence on GitHub. It looks well done, and they seem responsive, but there are exactly two committers. All projects had to start somewhere, this might simply mean that they're doing something new and better than other groups and it's just early days,

Re: Community Design Crit - April 10, Inclusive Combination Locks

Hi, All: Very interesting topic. I chatted with Jonathan about this, but wanted to share with the group, I bought one of these a few years ago just because I was so excited that something like it was available for a few dollars at a non-specialty store: https://www.masterlock.com/personal-use/pr

Re: Draggable - New #a11y drag-and-drop library from Shopify

Hi, Alan. I looked beyond the splashy page. They do seem to add a smattering of ARAI roles as claimed, but my impression after navigating their demos with a keyboard is not all that good. At least in their demos, most draggable elements do seem to support keyboard focus, but there doesn't seem t

Re: Considerate Pair Programming (3-parter)

Hi, Alan: Thanks very much for sharing this. I am taking the time over the next few days to read each entry and think it over, the first entry was both a good introduction and already very insightful and useful. Although some of the mechanics and the intensity described are unique to sustained f

Re: vagrant and 404 metadata warnings

Very helpful, Gio. Thanks for getting out ahead of this before it surprised people down the road. Cheers, Tony On 8 February 2018 at 16:38, Tirloni, Giovanni wrote: > Hello, > > If you're seeing this warning during `vagrant up`: > > ==> default: There was a problem while downloading the me

Re: Icon font building

n artefact associated with a successful build. > > > I’m not sure if that would work in the process I described, but I guess we > can touch base on it once there’s something in place to work from. > > Thanks > Justin > > On February 2, 2018 at 4:57:26 AM, Tony Atkins (t...

Re: Icon font building

> overhead of the VM shouldn’t be too much to worry about. > > Regarding location, I think I’d prefer having it in the main repo. I feel > like it will be easier to update the icons if the build process is > colocated, and it should be fine to version the icons alongside Infusion. I &

Re: Icon font building

rsion the icons alongside Infusion. I > suppose if we break Infusion out into a monorepo we could explore > separating the icons into their own package(s) (there will likely be > separate fonts for each component that uses icons in order to keep file > sizes to a minimum). I’m open

Re: Icon font building

Thanks for the writeup, Justin. I think the obvious solution here is to use our existing VM infrastructure to make it easy to build the font regardless of the host platform. There are fontforge packages for Linux, we just need to have a Vagrant VM that installs fontforge as part of its setup step

Re: Glorious merge of code coverage and testem configuration

bul/blob/master/ignoring-code-for- > coverage.md#ignore-default-assignments > > Thanks > Justin > > > On January 16, 2018 at 11:19:48 AM, Antranig Basman ( > antranig.bas...@colorado.edu) wrote: > > I'm happy to report the merge of a major and significantly usefu

Re: Current best practices for representing text edits in a screen reader?...

the visually highlighted elements. Cheers, Tony On 6 November 2017 at 16:55, Tony Atkins wrote: > Hi, All: > > So, I tried a bunch more things. Here is an updated chart of what did and > didn't work: > > > *Chrome:VO* > > *FF:VO* > > *Opera:VO* > >

Re: Mozilla's open-source speech recognition

Hi, Alan: I studied voice recognition quite a bit in the 90s as part of my master's, and wanted to comment with my impressions. In those days, the tradeoff was between being able to recognise a very limited vocabulary for a wide range of speakers, or training a computer to recognise a wide vocabu

Re: Current best practices for representing text edits in a screen reader?...

is to use the previous "clipped" approach (#1), but to write the announcements as editorial comments (#4) so that they display reasonably in GMail. Any other ideas or refinements are greatly appreciated. Thanks, Tony On 6 November 2017 at 14:03, Tony Atkins wrote: > Hi, All. > >

Re: Current best practices for representing text edits in a screen reader?...

Tony On 26 October 2017 at 12:57, Tony Atkins wrote: > Hi, All. > > I finally upgraded my OS over lunch just to see if it changed anything. > Firefox is still exactly the same. Previously, the label behaviour was to > read the label instead of the associated text, everything b

Re: Current best practices for representing text edits in a screen reader?...

) information from the label, and then the labelled text. Given that this does not work with NVDA, it's not really anything we can use versus the clipped but visible text approach. Cheers, Tony On 26 October 2017 at 11:29, Tony Atkins wrote: > Hi, Joseph: > > I think I'll ca

Re: Current best practices for representing text edits in a screen reader?...

have a technique that works everywhere I've tested, but there is risk of a small percentage of users getting double announcements. Any ideas to improve on what I have so far are welcome. Thanks, Tony On 25 October 2017 at 20:06, Joseph Scheuhammer wrote: > On 2017-10-25 11:25 AM, Tony Atk

Re: Current best practices for representing text edits in a screen reader?...

or styling; > the DOM is for content. CSS content was intended for decorative > content. Note that textual content added using CSS "content" rules > cannot be searched, nor selected, and does not behave like DOM content. > It renders on screen, but it kinda/sorta acts lik

Re: Current best practices for representing text edits in a screen reader?...

ve and its associates should force the issue. > >- aria-live: https://www.w3.org/TR/wai-aria-1.1/#aria-live >- aria-relevant: https://www.w3.org/TR/wai-aria-1.1/#aria-relevant >- aria-atomic: https://www.w3.org/TR/wai-aria-1.1/#aria-atomic >- aria-busy: https://www.w3

Current best practices for representing text edits in a screen reader?...

Hi, All: In recent work on the UL, I have been trying to represent revisions to a document in a way that also makes sense with a screen reader. I started by using *aria-label* attribute to add hints like "this content was added" and "this content was removed". At least with VoiceOver, this resu

Re: contributor guidelines, CLAs and attribution

nks > Justin > > > On October 6, 2017 at 5:21:59 AM, Tony Atkins (t...@raisingthefloor.org) > wrote: > > Hi, All: > > There was a tangential question about whether we could cover this by > customising the signup page or site footers on our JIRA instance. I took a >

Re: contributor guidelines, CLAs and attribution

Hi, All: There was a tangential question about whether we could cover this by customising the signup page or site footers on our JIRA instance. I took a few minutes to look at the options. In short, we can: 1. Modify one of the built-in templates. 2. Install a plugin that adds the ability

Re: Alternatives to the "marked" markdown renderer...

cally a drop-in replacement for marked with one minor configuration change (enabling html, which is disabled by default). Cheers, Tony On 19 September 2017 at 18:47, Tony Atkins wrote: > Hi, All: > > [I posted this earlier, crossposting as suggested by Justin to include a > wider a

Re: Article on personalisable interfaces...

ous about the discussions regarding > "generating Uis from JSON schemas" but couldn't find details looking > through mailing lists / wikis, are those taking place as part of the GPII > Architecture meetings? > > From: fluid-work on behalf > of Tony Atkins > D

Re: CouchDB - managing design documents?

AM, Tony Atkins wrote: > Hi, Simon: > > That's a fair point, at a minimum we should be aware of the need and see > what if any ground work we can take care of in working on managing design > documents. > > As far as I know we do not currently have a general solution to

Re: CouchDB - managing design documents?

ic in discussions on managing design documents. > > Simon > > > From: fluid-work on behalf of > Harnum, Alan > Sent: August 28, 2017 11:19:59 AM > To: Tony Atkins > Cc: Fluid Work > Subject: Re: CouchDB - managing design documents? &g

Re: CouchDB - managing design documents?

Hi, Alan: Thanks again for starting yet another interesting and important discussion. I've had to do a lot of this in my own work, and have alternated between: 1. Storing the design documents as raw JSON (mainly for testing). This is similar to the approach used in the example you shared.

Re: Puppeteer - new headless Chrome library from Google

Hi, Alan. Thanks for pointing this out. The first and biggest question that has to be asked when considering something new, is "why should we use this?" First, why should we use this and not Testem/gpii-testem ? Testem already supports a range of browsers,

Re: Yeoman generator for Infusion projects

Hi, Alan. Fantastic effort, thanks for getting this started. Can you talk for a bit about template inheritance, i.e. whether we can create a "core" template and then overlay a "client" and "node" template on that? I'm really interested in helping create the "node" template, just want to get a ro

Re: New Infusion introductory tutorial

Thanks, Alan! Although the whole effort is commendable, the live environments on CodePen are especially nice. It's nice to see at least a part of our docs taking advantage of the work you did with CDN. Cheers, Tony On Tue, Jul 25, 2017 at 3:54 PM, Harnum, Alan wrote: > After review and feed

Re: Developer Introduction to Infusion - substantially revised

Hi, Alan. Thanks again for leading this effort. It looks much improved. I left some comments on the PR with various typos and small improvements. Cheers, Tony On Thu, Mar 23, 2017 at 5:51 PM, Harnum, Alan wrote: > Hello all, > > > > After many helpful comments on the pull request and in th

Re: JIRA upgraded

Hi, All: I just reviewed the release notes for a bit and experimented on the upgraded instance. The biggest change is that the new WYSIWYG editor is now enabled by default for comments, editing descriptions, et cetera. As we have had very serious concerns with the Confluence WYSIWYG editor, I re

Re: Code of Conduct

Thanks, Colin: This is looking good. There's still an "INSERT EMAIL ADDRESS HERE" bit late in the doc that I'm guessing should be replaced with the new advoc...@lists.fluidproject.org address. Cheers, Tony On Thu, Mar 16, 2017 at 9:01 PM, Clark, Colin wrote: > Hi all, > > Now that we've had

Re: YouTube Channel for Fluid Project videos, transferring videos to it, general video standards

Hi, Alan: Great effort, and a good reminder of some of the videos out there. I have subscribed to the channel so that I can work through them and remind myself of ongoing efforts across the wider team (also to remind myself to share new videos with wider groups as they come out). So, I use close

Re: Removing "resolved" status from the GPII workflow...

s > Justin > > > On February 14, 2017 at 9:56:47 AM, Tony Atkins (t...@raisingthefloor.org) > wrote: > > Hi, All: > > Hi, All. In the spirit of "lazy consensus", barring any objections, I > plan to make the proposed changes in the morning. > > Cheers, >

Re: Removing "resolved" status from the GPII workflow...

Hi, All: Hi, All. In the spirit of "lazy consensus", barring any objections, I plan to make the proposed changes in the morning. Cheers, Tony On Thu, Feb 9, 2017 at 10:58 AM, Tony Atkins wrote: > Hi, All: > > In last night's architecture meeting, we discussed th

Re: fluid-lab GitHub organization

Hi, Justin: Now that I'm actually considering submitting something to fluid labs, I have a practical question about the process here. For GPII contrib projects, we request a new repo, and then fork/branch and submit our contribution as a pull request against the new repo. This allows us to have

The "resolved" status and the UX workflow...

Hi, All: I wanted to follow up on a second discussion point around the use of the "resolved" field on issues.gpii.net, which came up in last night's meeting. In reviewing the use of the "resolved" status in the GPII project, I discovered what I consider to be another problem. The UX project allo

Removing "resolved" status from the GPII workflow...

Hi, All: In last night's architecture meeting, we discussed the "resolved" status as currently used in the following projects: - GPII - Developers Space - GPII Projects - Onboarding The "resolved" status is meant to be a stage at which the reporter of the issue verifies that they are

Re: Code of Conduct

Hi, All: This looks really promising, and I absolutely agree that our community should champion these ideals as an important part of working in open source. To save everyone a couple of clicks, here's a direct link to the latest version in HTML format: http://contributor-covenant.org/version/1/4

Re: Meeting to discuss deploying versioned Infusion Docs

Thanks, Justin. Just to be clear, it's *this Thursday* at 10-11 ET. Cheers, Tony On Mon, Feb 6, 2017 at 8:45 PM, Justin Obara wrote: > The meeting is scheduled for 10 - 11am ET. We can sync up in the > fluid-work channel before hand and meet in one of our vidyo rooms. > > Thanks > Justin > >

Re: New GitHub org for GSoC and experimental work

Hi, Justin: Love the idea, but I'd prefer not to use fluid-sandbox, as to me a "sandbox" is more like a live playground, as in: https://github.com/the-t-in-rtf/fluid-sandbox How about fluid-contrib? Cheers, Tony On Fri, Jan 20, 2017 at 2:07 PM, Justin Obara wrote: > > I’m planning on creat

Re: Developer-oriented introduction to Infusion core concepts (for 2.0 version)

following URL in your browser: http://127.0.0.1:9778/ infusion/development/to-do/DeveloperIntroductionToInfusionFramework.html <http://127.0.0.1:9778/infusion/development/to-do/DeveloperIntroductionToInfusionFramework.html> Cheers, Tony On Tue, Jan 17, 2017 at 10:41 AM, Tony Atkins

Re: Developer-oriented introduction to Infusion core concepts (for 2.0 version)

Hi, All: I will leave feedback on the PR, but just to comment, the use of markdown within HTML breaks things on GitHub. For example, the links on GitHub do not look as they do within docpad. To view the content in the way it would be displayed in our documentation: 1. git clone https://gi

Re: Infusion dev numbering proposal

; On January 13, 2017 at 7:36:53 AM, Justin Obara (obara.jus...@gmail.com) > wrote: > > +1 to Colin and Tony’s latest suggestions. > > > On January 13, 2017 at 5:29:54 AM, Tony Atkins (t...@raisingthefloor.org) > wrote: > > Hi, Colin: > > Updating master to a futur

Re: PROPOSAL: add Infusion to cdnjs

Hi, Alan: This is a fine idea. I often find myself writing demonstrations of bugs or sketches of new design patterns in micro-projects. This would be so much better, we're a distributed group, and we need shared tools to inform discussions, investigate bugs, develop workarounds, et cetera. We es

Re: Infusion dev numbering proposal

is work/discussion. > https://issues.fluidproject.org/browse/FLUID-6105 > > Thanks > Justin > > > On January 9, 2017 at 11:57:48 AM, Justin Obara (obara.jus...@gmail.com) > wrote: > > Hi Tony, > > Warning and using the deprecated command sound like a good approach. >

Re: Infusion dev numbering proposal

either carry on from here as >Tony suggested and make a new branch for 2.x work, or we could just assume >everything else will be part of the next major release. > > I wouldn’t say this is the ideal solution, but it might be easiest. > > Thanks > Justin > > > > O

Re: Warning against sourcing Infusion from git-based package references

Hi, All: I just wanted to point out that this is not at all unique to fluid. Any repo/hash whose version in the package.json file matches a released version will suffer from this problem. I have had the same problem with kettle, and with my own gpii-x contrib packages, which also use the last re

Re: Infusion dev numbering proposal

Hi, All. I was thinking about this very thing yesterday. For the near future, I think Antranig's suggestion is fine. As our community continues to grow, I would argue that we need to adopt a strategy that better supports minor and/or patch releases between major releases. Although we cannot kno

Re: JIRA and Confluence updated

Hi, All: I took a few minutes to try out the new versions, to see what if anything has changed, especially with regards to keyboard navigation, and wanted to summarize my experiences. First, the new version of JIRA added a wysiwyg editor, which was a red flag to me, as I remember the transition C

Re: [Architecture] Vagrant QI - Split node_modules

Hi, Giovanni: Glad to see there is a new option here. Is the fix already reflected in Alfredo's work? I have started using that, and would rather not move back to maintaining local Vagrantfiles. Cheers, Tony On Tue, Nov 8, 2016 at 7:45 PM, Tirloni, Giovanni wrote: > Hello, > >Some peop

Re: Moving away from Markdown to straight HTML for Inclusive Design Guide site

Just to extend Alan's last point: >- It may be worth looking at the issue at https://github.com/chjj/ >marked/issues/556 & its linked issues – it's possible we may be able >to use the plugin configuration options to get a Markdown parser that >behaves more as we would like it. > >

Re: Moving away from Markdown to straight HTML for Inclusive Design Guide site

Hi, Jonathan: I agree with a lot of Alan's points, moving to pure HTML seems like a step we should only consider once we have reasonably exhausted the remaining options. Thankfully, I can already think of a few options off the top of my head that would get us back to more pure markdown. Let's st

Re: Reset pouch for GPII development config

Hi, Cindy: First, apologies in advance for the code in the body of the message, pastie.org is down at the moment... :| The first problem is the use of "gpii.express.router". Although this was not always the case, the "gpii.express.router" grade is currently mainly intended to contain other piece

Re: [community] Community Design Crit - Wednesday Aug 24

Hi, All: Sorry for the short notice, but here, for today's crit, is a demonstration of the Fluid Sandbox: http://the-t-in-rtf.github.io/sandbox-demo/ I will discuss some of the current shortcomings in the meeting and get your input, for now, the "reorderer" demo is the one that shows things off

Re: My Lifelong Learning Lab - High-Level Design Document

sonable facsimile > of what it's like serving the project from nginx or Apache without actually > having to go through setting those up. > > Alan > > From: fluid-work on behalf of > Tony Atkins > Date: Thursday, August 4, 2016 at 4:04 AM > To: Fluid Work > Subje

Re: My Lifelong Learning Lab - High-Level Design Document

Hi, Alan: I tried out your repo. I wasn't able to successfully run *npm install*, as the chart authoring dependency fails to install. I suspect it's because grunt and its plugins that are used in your post install step within that package are dev depencies and not plain old dependencies. Thus,

Re: How about having a generic demo component

you were hoping for as the > sandbox content. > > https://github.com/fluid-project/infusion/tree/master/examples > > Thanks > Justin > > On July 6, 2016 at 8:18:52 AM, Tony Atkins (t...@raisingthefloor.org) > wrote: > > Hi, Michelle: > > There are no formal plans

Re: How about having a generic demo component

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 > wrote: > >> Hi, Dinuka: >> >> Earlier in my own learning process, I worked on something similar, a >> sandbox for w

Re: How about having a generic demo component

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 change

Re: infusion-tooltip-sample

Hi, Dinuka: Thanks for setting up the demo site, that makes it really easy to give feedback. The first thing I tried was keyboard navigation, which needs a little work. Neither of your demo buttons has a tabindex attribute, which means you can't get to them with the keyboard, at least not in the

Re: "Monorepo style"

Hi, Antranig: This is fantastic. I have followed more of the "micromodule" approach, I have to admit it can be pretty maddening to coordinate. Lerna gives us a great new option for our larger projects, and is especially nice because it gives us the ability to transition in whatever direction we

Re: Anyone know a good tool for adding descriptive audio to (YouTube) videos...

s below (Josh Miele) have something exactly as you > describe, but they may. > > http://www.vdrdc.org/research > > > > > > *** > Jim Tobias > Inclusive Technologies > +1.908.907.2387 v/sms > skype jimtobias > > > > *From:* fluid-work [mailto:fluid-work-

Anyone know a good tool for adding descriptive audio to (YouTube) videos...

Hi, All: I was briefly thinking about adding descriptive audio to a few of my YouTube videos. I took a look at http://youdescribe.org/ Their app requires you to sit down with a microphone, pause the videos and record the audio yourself. I was hoping to use a text-to-speech engine to do somethin

Re: Heads up: website deployment

Hi, Gio: Can you share details about how you set that up (a link is fine)? I would like to do the same for my github pages blog. Cheers, Tony On Fri, Apr 15, 2016 at 7:17 PM, Tirloni, Giovanni wrote: > Hello, > > The following GitHub repositories were reconfigured to work with our > automa

Re: Proposal: better intermediary means of managing external front-end Javascript dependencies in Infusion-based projects using nom + grunt

y different approaches > to the same problem when the space is tumultuous or uncertain (as I feel JS > front-end dependency management is, and perhaps always will be). > > *ALAN HARNUM* > SENIOR INCLUSIVE DEVELOPER > INCLUSIVE DESIGN RESEARCH CENTRE, OCAD UNIVERSITY > > *E *ahar

Re: Proposal: better intermediary means of managing external front-end Javascript dependencies in Infusion-based projects using nom + grunt

ce is tumultuous or uncertain (as I feel JS > front-end dependency management is, and perhaps always will be). > > *ALAN HARNUM* > SENIOR INCLUSIVE DEVELOPER > INCLUSIVE DESIGN RESEARCH CENTRE, OCAD UNIVERSITY > > *E *ahar...@ocadu.ca > > *OCAD UNIVERSITY* > 100 McCaul Stree

Re: Proposal: better intermediary means of managing external front-end Javascript dependencies in Infusion-based projects using nom + grunt

uild the module out at least enough to start exercising it in my tests. To use this approach, we would need to create and maintain bower.json files for our packages. I would also create a PR that adds a bower.json for infusion. Cheers, Tony On Wed, Mar 2, 2016 at 9:26 PM, Tony Atkins wrote: &

Re: Proposal: better intermediary means of managing external front-end Javascript dependencies in Infusion-based projects using nom + grunt

Hi, All: At the risk of offering to address any particular problem with a hammer I happen to be familiar with, I was thinking about making a gpii-express router for something like this earlier. I already commonly use a wrapper around the express "static" router to serve up content from node_modul

Re: Updating Fluid JIRA to use wiki markup...

Hi, All: With the help of the admin team, I've made the change, comments and descriptions now support wiki markup on the Fluid JIRA instance. Cheers, Tony On Tue, Oct 20, 2015 at 9:53 AM, Tony Atkins wrote: > Hi, All: > > I didn't hear any feedback on this, I will assume

Re: Updating Fluid JIRA to use wiki markup...

Hi, All: I didn't hear any feedback on this, I will assume everyone is OK with the improvement and work with the admin team to set this up this week. Cheers, Tony On Tue, Oct 13, 2015 at 9:58 AM, Tony Atkins wrote: > Hi, All: > > I have been recently working more on the Fluid

Updating Fluid JIRA to use wiki markup...

Hi, All: I have been recently working more on the Fluid JIRA instance. I noticed that the description and comments fields are not configured to support wiki markup. This prevents using code formatting, for starters. It also prevents the use of "at mentions", which would allow you to do IRC-like