I am new to React and I just stumbled to amazing Blueprint components. However, I am unable to use it and I am confused by the installation guide. Its quite different from what I am used so far.
Can anyone explain me how to use Blueprint without Typescript?
You can simply ignore the Typescript parts. Since you are writing a React app, it needs to be compiled through Babel anyways.
I never used Typescript before and also just started to use blueprint a few days ago and was able to use the JSX components completely without any Typescript knowledge.
Just start using it like any other React components you write - or use DIVs with the blueprint CSS classes directly when necessary. Its up to you.
Related
I have a question about Bootstrap and CoreUI on Laravel Boilerplate.
I've been trying to use some core features that are a part of Bootstrap by default, however, some things just don't work. Collapse, Modals, these features don't seem to be available. Is there something I'm missing? Some element that is customizable and needs to be loaded?
Any advice on where to look would be helpful as I'm having trouble even determining where to search for researching a solution.
I am newbie with nativescipt-vue. I need to connect identity server with nativescript-vue. I found a plugin in this repo. But its developer gives only angular example. Can I use this plugin with nativescript-vue. Do you have any suggestion? Thank you in advance.
Good news: Most of 'things' developed on the top of NativeScript are interoperable, meaning that you can swap frameworks as desired.
Bad news: There is some problems of doing so. I've looked into the repository that you reported on the question and I saw that you have to deal with some Interfaces there.
export class AuthComponent implements OnInit { //...
Dealing with interfaces in NativeScript is a little bit confusing since you have to deal with classes in both NativeScript and Java in the same script.
The lack of documented behavior of this keyword, for example, can lead to some undesired behaviors. I am dealing with this problem right now. So, be careful.
Please provide us some parts of the code that you want to transpile to NativeScript-Vue.
Also, I highly recommend you to study how NativeScript works before understanding how NativeScript-Vue works. You are probably accessing the NS docs way more than NativeScript-Vue docs in a near future (assuming that you are already familiar with Vue).
I have some Android development experience along with React.js. I'm working on a new mobile project and I haven't been sold entirely on either framework yet.
I'm thinking about using the NativeScript framework for its maturity and because it has more libraries with the functionality that I need but I'd like to design my views in a manner similar to ReactJS. I know I could write my own modules for ReactNative but that would require then I'd have to write modules for both Android and iOS. I'd like to avoid that if I could.
I was thinking about importing the necessary ReactNative libraries into a NativeScript project and then being able to write views in a way similar to ReactNative but still using NativeScript.
Is this doable?
Not sure about your exact question. I did just see an integration between Preact and NativeScript you may be interested in. Take a look here: https://github.com/staydecent/nativescript-preact
I believe that repo is in the early stages, but if enough people want something similar, it'll get worked on faster.
Using React Native in NativeScript is not the right approach, either of it are not built to work together and wouldn't work due to architectural reasons. Here is an NativeScript official comparison of these two.
Both are built for solving same problem (building native apps using JS, without webview hybrid app approach) by trans-compiling XML based view layer(which both these framework has its own syntax and so cant be shared) to build Native UI.
Said that view layer has its own syntax for both and cant be shared, model and controller layer cant be shared as well, due to the fact that NativeScript has few things packed as part of the application package, like JavaScript runtime, c++ and Java API layer which helps in exposing all the Native API without the need for any explicit native API wrapper we have in ReactNative.
React Native have platform specific UI components as well as hardware capabilities, which is not the case with NativeScript. Offcouse, that comes with the cost of a fatter app package size(50+MB) compared to <10MB for ReactNative. More on ReactNative vs NativeScript comparison here.
First of all many thanks for the incredible source of information that you are providing to people like me.
I am visiting this site very often and most often finding the answer I need, but this is this is the first time I post a question, so please accept my apologies if I don't fully conform to rules.
Here is my issue:
I am "playing" with Dart Editor and Polymer to try to understand if I could use these technologies in my job moving forward
I was able to import the Polymer Core and Paper components in Dart Editor and to install polymer.dart
I was able to create a simple web page with a "core-selector" and to add some Dart code to handle a click on this component
I can't find how to listen using Dart code for component-specific event ("core-activate" & "core-select" here) and how to read component-specific attributes ("selected" & "multi" here)
I don't seem to be able to find good examples showing how to use "standard" polymer components in a web app created Dart Editor
I could find material on how to create my own polymer components using polymer.dart but I would just like to use standard components
I understand both Polymer and Dart are young but I can't imagine the clever brains at Google not having a solution or plans on this.
Regards and many thanks again.
Sebastien
The problem is not that Polymer and Dart are young. Dart is quite mature, Polymer is not even beta but also not so young anymore. The problem are the core- and paper-elements. They are very new and developed in JavaScript and the Polymer.dart team just created a code generator that wraps the JS core- and paper-elements in Polymer.dart elements. This process is only available since a few days and there are several issues which are yet to be solved.
I think you should provide a concrete example in your question of what you can't get working. Basically Polymer.dart core- and paper-elements work exactly as other Polymer.dart elements. So it's hard to know what to explain.
I have used backbone boilerplate on the past
https://github.com/backbone-boilerplate/backbone-boilerplate
I want to use marionette on my next project and I have found this
https://github.com/BoilerplateMVC/Marionette-Require-Boilerplate
My question is if it's a good idea to go with the marionette boilerplate or start form scratch.
As an aside, I'd like to suggest you give Yeoman a shot for scaffolding your first Marionette app. Yeoman works via what are called "generators", and provide much more than the the above Boilerplate MVC can offer you (Chai and Sinon for testing, Bower for client-side package management, etc...). Plus, Addy Osmani, who runs backbone-boilerplates is one of the heads of the project. Check out generator-marionette here.
I haven't used BoilerPlate, but glancing through it, it certainly seems like a valid approach to writing Marionette apps. If you're just getting started it will certainly help you see how the various pieces are supposed to be used. One gripe I've got is the folder structure. I prefer to break my applications down into modules, and then add models, collections, views, etc under each module. But this will certainly get you up and running quick, and there's nothing stopping you from customizing it to suit your needs.
I agree with others here: it is a useless limitation to imitate a folder structure that follows the 'old mvc model for server-side code'. You will remain more flexible further down the road if you think of your application strictly as completely self-containing modules, i.e. they contain their own controller/router/views/collections/templates etc. You can have a separate folder structure for shared code that is not a module, although anything can be made a module :)
Regarding boilerplate code and generators: i think in the beginning you should actually NOT do it, because you won't understand what you're doing. But that's just my personal opinion.