Hi Olaf, about styles missing, probably is since we remove default styles from HTML (and something to improve this library would be to remove HTML dependency at all in the future)
this is what makes in our maven pom.xml that builds the example <additionalCompilerOptions>-compiler.exclude-defaults-css-files=HTML-0.8.0-SNAPSHOT.swc:defaults.css</additionalCompilerOptions> About build tool: For me maven is so convenient and easy to develop with. The main problem with maven is the setup, that use to be very complex, but that was that Chris Dutz make for us, and IMHO it was a genius setup. So once we have a the setup we can develop framework and/or apps at the same time with a real easy and quick workflow. In my case: 1.- I'm on Mac and use to have tree terminal windows open pointing to three repos. In each window I run "mvn clean install" (first in falcon, then on typedefs and finaly on asjs). And I have in my local maven repo the updated artifacts with all the changes I code (added or fixed). Notice that Chris has plans in the future to unify all so we only need to do one mvn clean install. These are 28, 11 and 46 secs what's really cool, I use to update from Git (with source tree) at least once a day and rebuild to develop with fresh code. So this is somewhat residual in my day-to -day right? :) 2.- Then for daily development: In concrete for dev MDL lib and MDL example, have two VSCode windows one with each project open. Then, as I create or fix something in MDL swc library project, I push CTRL+CMD+B to build with maven (and this refresh the maven artifact with latest code) - This is 5 secs build (so great too :)). Finaly I make changes or test fixed in MDLExample pushing agains in its window CTRL+CMD+B, again 5 secs or so... So I think this is very confortable way of develop your app. If you don't have a build env set up, you only can do step 2, with your own app and libraries. So If you find some problem you'll have to make some patch that could be lost in a future FlexJS update. So, imagine that MDL Button has a bug, and you need to fix it, and at that time you can't get help from any of us. So you decide to fix yourself. I think is better to fix in the project and ensure that it will be part of FlexJS SDK in the future. You can do it since is so simple! :) For that reason I encourage you to adopt maven A side form this, some minutes ago, to help fixing a RadioButton MDL click problem, Alex said us to create a minimum project example. I did it in 2 minutes project, config to build, create a branch in git and share it. That's so amazing fast don't you think? So in the end, I create a SDK distribution with maven (with another terminal window), but I only use that to get NextGenAS a recognizable SDK to point to and get Code intelligence. But for me, a nigthly does not has more value that that. Hope I help you understand the motivations behind. Take into account that get the build maven env is just few steps following the Flex Maven setup in our wiki that I share with you. 2017-02-01 19:54 GMT+01:00 OK <p...@olafkrueger.net>: > Hi, > thanks to all for help. > asconfigc compiles successfully with 0 errors and 2 warnings. > But the output seems to me that there'e some styles missing [1]. > > However, probably I'm annoying you with this topic but I still don't > understand the benefit of using a build tool to compile the examples. Maybe > I'm a fool or to old for this stuff. > I understand that this maybe makes sense if somebody would like to build > the > examples without using an IDE. > But in case of the MDL examples the tasks.json is included in the .vscode > folder. > And for me that implies that you have a working VSCode IDE with a working > (already build) SDK. > So in this case you just could call asconfigc without the need to download > and re-build the whole stuff. > > Could somebody enlighten me? > > Thanks, > Olaf > > > [1] https://snag.gy/6pXEhm.jpg > > > > -- > View this message in context: http://apache-flex- > development.2333347.n4.nabble.com/FlexJS-Need-help-with- > compiling-MDL-examples-tp58870p58932.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.
