I'm almost ready to release a build of the VSCode extension that supports
MXML. I finished up the most critical features earlier this week. I just
need to put on some finishing touches. Next week is the US Thanksgiving
holiday, and I have family visiting all week, so I may not have time to
look at the extension again until the following week. I'm expecting that
the final details will be quick and easy!
- Josh
On Fri, Nov 18, 2016 at 12:58 AM, Carlos Rovira <
carlos.rov...@codeoscopic.com> wrote:
> Hi Piotrz,
>
> great you finaly have this working :)
>
> 1) As I understand code each component is consistent with "Logic" + "CSS -
> > appearance" - Am I understand correctly?
> >
>
> I think you refer if I'm making a "Card" component since there's an MDL
> one...yes.
> There's some standard controls, like Button, CheckBox or RadioButton...but
> for example in MDL there's no TextInput, I think they call it TextField, so
> maybe we should rename our MDL component to "TextField"?
> For Others like Card or Badge, there's no flexjs counterpart, so...I stick
> with that...
>
> But what about MDL Table...should it be a DataGrid....I'm trying to discern
> this days things like this...
> a MDL List, could be a js:List... and so with others, we should estimate as
> we go...
>
>
>
> > 2) When I'm looking into [1] I see that components has css classes
> > "mdl-js-button" - Where is the place that you are adding this css
> classes ?
> > - They are probably downloaded somehow from google repository as I
> > understand ?
> >
>
> This classes comes from the basic needs of MDL and are added in the
> index.html template (resources/mdl-js-index-template.html
>
> see in the pom.xml for line
> : <htmlTemplate>${basedir}/src/main/resources/mdl-js-index-
> template.html</htmlTemplate>
>
> so is the basic html with some MDL required lines in it.
>
> I think we as well insert some new vars to customize colors when
> build...but I didn't see already if we could do this. Maybe we should ask
> to other guys here about how to tweak this. if there are already compiler
> support, or index.html support
>
>
> > 3) When I see compilation result it's only js result - what about swf -
> you
> > do not bother how it is working on flash sight ?
> >
>
> I'm focusing in HTML output, since Flash will need more work (make the MDL
> look in flash and components are needs more work in general). So my
> approach is to have the MPV (minimum product viable) of a MDL flexjs
> component set and from there evolve. If you think flash is important, hope
> you could grab the torch here and handle the effort.
>
> Until some weeks, flash output has no point for me since we have old
> flex...but then I talk with people that makes me turn 180º. HTML in mobile
> has poor performance, and we need go native. I don't know how flash effort
> is going on, but I think if we go stage3d (like feathers) then flash output
> would be very important.
>
>
>
> > 4) General question - What is your plan for MDL - Are you going port all
> > MDL
> > components ?
> >
>
> Yes, as I get time, I'm porting the components I see here:
> https://getmdl.io/components
> This is my actual RoadMap, I'm as well attracted to port Bootstrap
> component...
>
> I think this is our first main step to get flexjs have a great look and
> feel so more people would join us.
>
>
>
> > 5) Visual Studio Code is a helper for build and debugging of project, but
> > is
> > intellisence is working there ? Cause I see like blind or random things
> > when
> > I'm trying to write something.
> >
>
> I think VSCode is a good starting point, but is a IDE in development. Hope
> Josh would make live latest works on MXML, and other things. Meanwhile is
> not a speed IDE, but for me is working great.
>
>
> > 6) Maybe I will repeat this question, but I wanted to have it in this
> > thread: When you writing new component - You are adding it to FlexJS -
> > building whole framework by maven and then your example is picking it up
> > where you can debug it ?
> >
>
> I setup two projects to respond to CTRL+CMD+B, to build with maven:
> MaterialDesignLite and MDLExample.
> As I add a new component to MaterialDesignLite.swc I build only that
> pressing CTRL+CMD+B in VSCode (until now I had some Terminal window open in
> a OS X space and run mvn clean install)
>
> Then I go to MDLExample and instantiate the new component and again
> CTRL+CMD+B and open in browser to see results.
>
> I think is a pretty fast workflow
>
>
> >
> > A lot of question, but I'm trying to find some small cycles to help with
> > MDL.
> >
>
> Great Piotrz, keep it coming, I think there's much to make here, and things
> are in a state where we could make a different with some help and
> dedication :)
>
> Thanks!
>
>
> > [1] https://getmdl.io/components/
> >
> > Thanks,
> > Piotr
> >
> >
> >
> > -----
> > Apache Flex PMC
> > piotrzarzyck...@gmail.com
> > --
> > View this message in context: http://apache-flex-
> > development.2333347.n4.nabble.com/FlexJS-MDL-Help-with-MDL-tp56556.html
> > Sent from the Apache Flex Development mailing list archive at Nabble.com.
> >
>
>
>
> --
>
> Carlos Rovira
> Director General
> M: +34 607 22 60 05
> http://www.codeoscopic.com
> http://www.avant2.es
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.
>
