Blergh, suite is the wrong word, so please don't repeat it. I need to check for the
right word :-)
On 11 Feb 2013, at 12:32, Kris Borchers wrote:
OK, I think that makes sense to me. Anyone else want to chime in?
On Feb 11, 2013, at 6:30 AM, Pete Muir <pmuir(a)redhat.com> wrote:
>
> On 11 Feb 2013, at 12:27, Kris Borchers wrote:
>
>>
>> On Feb 11, 2013, at 5:48 AM, Pete Muir <pmuir(a)redhat.com> wrote:
>>
>>> Kris/Douglas,
>>>
>>> I also realised there might be another point of confusion in this discussion.
I'm definitely not proposing a strategy that Aerogear needs to adopt (for you guys
it's really important to be more JS framework neutral IMO), but for JBoss. So the
answer to "What JS frameworks can I use with Aerogear?" is different to the one
"I want to use JBoss to build a mobile app, how do I do it?".
>>
>> Hmmm. I feel like that could be confusing to someone new who says, "I want
to use JBoss and AeroGear to build a mobile app" and we tell them JBoss says go with
framework "X" but AeroGear says use what ever you like. This is not an easy
thing to sort out. :-)
>
> I suppose I see it as:
>
> * You guys cover building apps with Aerogear on
aerogear.org. Here, you cover a
variety of JS frameworks working with Aerogear.
> * You guys say "if you want to learn more about using Aerogear with other
products in the JBoss suite, then see JBoss.org"
> * On
JBoss.org we are more focused on showing one JS framework.
>
> WDYT?
>
>>
>>>
>>> Pete
>>>
>>> PS not sure what your team (internal) list is, please add it to the cc :-)
>>
>