On Fri, Sep 15, 2017 at 1:53 PM, Adam Malejko <a...@malejko.com> wrote:

> I have another developer going through our apps and identifying components
> that are potential issues going forward.
>
> So far they have only found a few third-party components - so, not a fault
> of FlexJS really.
>
> The datagrid is a little lacking as well; we have been spoiled with the
> Flexicious one, and they have gone with a new React one... can we use that
> in FlexJS? Haven't tried yet.
>

Have you looked at the MDTable? http://s.apache.org/MDLExample
That is a good starting point to add more features.

Thanks,
Om


>
> Giving the 'freedom to not care about JS' should have been Flex's motto in
> the beginning! Now FlexJS has to care about it, as that's the end result..
>
> On Fri, Sep 15, 2017 at 1:28 PM, Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
> > Hi Adam,
> >
> > What components are you looking for that haven't been done yet?
> >
> > Again, the supposed advantage of contributing is that you get control
> over
> > your destiny.  If there is a bug in the framework that is high priority
> > for you and you have earned committer status by contributing in the past,
> > you can just commit the change.
> >
> > Thanks,
> > -Alex
> >
> > On 9/15/17, 12:22 PM, "Adam Malejko" <a...@malejko.com> wrote:
> >
> > >More strengths to add:
> > >- AMF support getting better
> > >- RemoteObject support!
> > >- Less to re-write when porting Flex apps
> > >- Can use other JS components (with caveats, unfortunately)
> > >- Type-checking, SWF output and validation
> > >- Works in several IDE's
> > >
> > >A few weaknesses to add:
> > >- It's not done yet. The components we use from Flex are not all done in
> > >FlexJS yet.
> > >- No commercial support if you want it (but the Apache support is
> > >wonderful!)
> > >- Lack of documentation
> > >- Smaller community than some of the bigger JS frameworks
> > >
> > >I like the Opportunities listed, and the Threats I agree with.
> > >
> > >Yes, we could volunteer to contribute; or we could switch to React,
> > >Angular, ExtJS, or something else.. we're on the fence and looking in to
> > >all of our options, of which there are many these days.
> > >
> > >
> > >
> > >On Thu, Sep 14, 2017 at 10:46 PM, Berty Tonta (Leadstalk) <
> > >berty.to...@leadstalk.pro> wrote:
> > >
> > >> If it has not been done yet, and from a marketing perspective, would a
> > >>SWOT
> > >> help?
> > >>
> > >> The point of the SWOT (example below) would be to look at the reality
> > >>and
> > >> then identify those engaging arguments to (1) answer weaknesses and
> > >>threats
> > >> and (2) leverage on Strength and opportunities.
> > >>
> > >> We could then select the 3 - 4 key arguments that really makes FlexJS
> > >>stand
> > >> out.
> > >>
> > >> STRENGTH
> > >>
> > >>    - Robust AS3 foundations
> > >>    - Multiplatform
> > >>    - Open Source
> > >>    - Security???? (I'm not a developer and need you to confirm)
> > >>    - ...
> > >>
> > >>
> > >> WEAKNESSES
> > >>
> > >>    - Association with Flash
> > >>    - Abandoned by Adobe???
> > >>    -
> > >>
> > >>
> > >> OPPORTUNITIES
> > >>
> > >>    - AS3/Flex a more robust/structured development platform
> > >>    - A potential enterprise class solution
> > >>    - Rebirth into an open source platform
> > >>    - Powered by the community
> > >>
> > >> THREATS
> > >>
> > >>    - Other "native" JS platforms
> > >>    - Potential to be rejected by pure JS/HTML5 developers
> > >>    - Perception of poor security....Flash legacy
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Berty Tonta
> > >>
> > >> ____________________________________________________________
> > >> ________________
> > >>
> > >>
> > >>
> > >> LEADSTALK - 4 BENGALI STREET, BEAU BASSIN, MAURITIUS
> > >> TEL  +230 57 43 81 34 - berty.to...@leadstalk.pro - LEADSTALK.PRO
> > >>
> > >> On Thu, Sep 14, 2017 at 11:38 PM, gkk gb <modjkl...@comcast.net>
> wrote:
> > >>
> > >> > In addition to...
> > >> >
> > >> >
> > >> > "Why should a web dev choose FlexJS to write JS applications, and
> not
> > >>go
> > >> > with a more mainstream option like e.g. TypeScript/Angular?"
> > >> >
> > >> >
> > >> > it may also be useful to think of the end customer. That is,
> > >> >
> > >> >
> > >> > "Why should a company prefer their app to be written in FlexJS
> rather
> > >> than
> > >> > ..."
> > >> >
> > >> >
> > >> > The company will need to support their app throughout its lifecycle
> by
> > >> > hiring developers, etc, which, the further you go from mainstream
> > >> > technologies, is harder to justify. There should be some compelling
> > >> > business reason(s) to do so (faster development, etc.).
> > >> >
> > >> >
> > >> >
> > >> > >
> > >> > >     On September 14, 2017 at 6:38 AM Piotr Zarzycki <
> > >> > piotrzarzyck...@gmail.com> wrote:
> > >> > >
> > >> > >     Hi All,
> > >> > >
> > >> > >     Erik on dev [1] list came up wit interesting question. I'm
> > >>posting
> > >> > it also
> > >> > >     here:
> > >> > >
> > >> > >     With the upcoming fork and renewed focus and most likely some
> > >> > publicity, I
> > >> > >     want to ask the community to answer this question:
> > >> > >
> > >> > >     Why should a web dev choose FlexJS to write JS applications,
> and
> > >> not
> > >> > go
> > >> > >     with a more mainstream option like e.g. TypeScript/Angular?
> > >> > >
> > >> > >     I think that if we can answer that question in a compelling
> > >>way, we
> > >> > are in
> > >> > >     a good place as a project (from a code perspective, at least)
> > >>and
> > >> it
> > >> > gives
> > >> > >     the marketing folks something to work with.
> > >> > >
> > >> > >     [1]
> > >> > >
> > >>https://na01.safelinks.protection.outlook.com/?url=
> > http%3A%2F%2Fapache-fl
> > >>ex-development.2333347.n4.nabble&data=02%7C01%7C%
> > 7Cdab072253c474bc9c0dc08
> > >>d4fc6f3d48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> > 7C63641100209603241
> > >>9&sdata=Z5wdmDlGuaDWy96FIy0Q4UaBCfOWAMctoTgATFbHIaY%3D&reserved=0.
> > >> > com/FLEXJS-Marketing-why-should-a-web-dev-choose-
> FlexJS-td64292.html
> > >> > >
> > >> > >     Thanks,
> > >> > >     Piotr
> > >> > >
> > >> >
> > >>
> >
> >
>

Reply via email to