It there any free to use plugin or javascript library compatible with Nativescript so I could make at least bar charts vertically or horizontally. There seems to be lack of information around this criteria. I'm not going to use telerik pro stuff.
Update March 1, 2018
As Shaunti mentions in a comment, the chart library from NativeScript is now free of charge.
Using native third party libraries:
One of the main benefits of NativeScript is that you're free to use any native third party libraries you want (iOS Cocoapods or Android libraries). For example, you can use Charts Cocoapod or MPAndroidChart.
There's several hundred free-to-use/open source chart libraries available out there. It's just a matter of finding one which suits your needs.
Here's a blog post about using native third party libraries in NativeScript: http://developer.telerik.com/featured/using-native-libraries-in-nativescript/
About chart.js etc
Chart.js etc are HTML solutions. They produce HTML. Nativescript is not a HTML based solution (such as PhoneGap etc). Nativescript produces actual native code. Here's a short video explaining the difference between a native solution and a web based solution: https://www.youtube.com/watch?v=R98cdsq1qxA
Therefor you will not be able to use web based technologies.
Final words
I suggest that you rethink not wanting to use the readymade Telerik components. If you don't have experience with working with Cocoapods/Android libraries and don't have that much experience with NativeScript itself it will most probably cost you quite a bit of time to get things up and running.
Compare your time cost with the $199 cost for the UI for NativeScript components
Related
I am not a web application pro but need to start working on a project so I need to know if pyjamas ( or shall I say the javascript generated o/p of pyjamas ) is as good as pyqt in terms of 2d graphics and widget features. I have a desktop python application which has some rich 2d graphics (with animations / collision detection etc..) implemented using pyqt.
Now I am specifically looking for equivalent web client with similar graphics and widget features . Does pyjamas support all the pyqt UI features with same look and feel??
I am also exploring GWT for this since I believe GWT has a good set of UIs and also supports decent 3rd party tools like vaadin,smartgwt but my preference is for pyjamas because its python and I am writing a equivalent pyqt based desktop app so am more comfortable with python then java. Also am not sure if GWTs look and feel would match with that of pyqt based UI on windows.
Any insights would be very helpful
Thanks in advance
Regards
Shyam
Probably too late, but if anyone else would need an answer,
Pyjamas' widgets are mostly same as GWT's (most are direct translation from GWT, but we have some own widgets too), and do not target Qt, GTK or any other toolkit.
If you are looking into using webkit, you could get best of the two worlds, and use Pyjamas with PyJD. This way your very same application could be compiled into html/css/javascript and run in web browsers and at the same time you could run it in pyqt-webkit, xulrunner or mshtml with original python code.
I am on searching special features of GWT which are present only in GWT and not in other web framework. I am a student and I am not well acquainted to the many web frameworks on the market, so if u can help me increasing my list of special GWT features, it would be a great help. Some which i know are:
1. GWT allows using java to program
web. (only, it also allows merging
javascript through JSNI of course)
2. The developer does not have to be a guru in browser incompatibilities
to develop web sites which works on
a variety of browsers because
incompatibilities are handled by GWT
through differed bindind
3. GWT allows easy integration of popular Java Tools such as ,
hibernate through gilead
4. GWT enables server implementation not only in java but also other
languages such as php
5. GWT enables code splitting which improves application interactivity
by allowing javaScript file to
download only when required
6. In essence GWT is toolkit, it does not force a way to program,
other layers can be placed on top of
it to program such as placing MVP or
MVC framework on top of GWT and then
develop app
7. GWT MVP is great because first it allows collaborative working, faster
testing with JUnit and the event bus
allows many updates in client side
application by placing event on the
event bus
8. GWT compiled java files to obfuscated mode which is first small
and make the application safer
because bots fails on the javascript
generated during the obfuscated mode
In case in the 8 points, i've mention something which not special to GWT, then let me know.
There's also 'perfect caching', which is the term used to describe the way that GWT optimises JavaScript for each browser.
Instead of building a large JavaScript file, with code that can handle all of the various browsers, GWT builds multiple JavaScript files at compile time, and downloads only the one that is relevant to the browser type that is being used.
EDIT: Every time you make a change to your Java code, GWT changes the name of the corresponding JavaScript file. Web servers can turn on caching for the JavaScript files (so that browsers won't re-download the same file), assured that the name will change when the Java code changes, and the browser will then download the latest version.
EDIT: I also really like the CssResource feature. By creating obfuscated CSS style names, GWT effectively gives each widget its own namespace for CSS styles; for example, I could define a 'pretty' style name on two different widgets, and have those styles using different CSS rules. Of course, it is possible to share CSS styles between widgets too.
Image resources are cool too. They optimise the way that images are downloaded and accessed.
Don't forget internationalization.
I think you pulled together a pretty decent list of differentiators there already. I think that one point worth adding is the RequestFactory feature in the most recent release, which, if you will, is simplistically speaking and RPC for data and makes it quite easy to develop Create, Read, Update and Delete - type (CRUD) of applications.
There are other, more important/wider accepted GUI-Frameworks that are based on Java.
There are for example Struts and JSF. That's why some of your points don't fit only for GWT, but for all GUI java frameworks in general, e.g. bullet point 1, 2 & 3.
But to add another one:
I think GWT is an easy way to code an AJAX-application, because it hides the AJAX stuff quite well. Wouldn't you agree?
Furthermore, GWT is a proprietary framework (which is somehow a unique property). JSF is standardized and Struts is lead by Apache.
is there a difference between Ext GWT and GWT-Ext? Cos i was surfing Ext GWT and saw this page http://gwt-ext.com/demo/. any help guys?
ExtGWT is marketed and maintained by the same guys who developed ExtJs library. ExtGWT shares its look and feel and API structure with ExtJS. Contrary to popular perception, ExtGWT is not a wrapper around ExtJS javascript, but written ground up using GWT DOM and other low level GWT API's. It is 99% java based and uses no (or very little) JSNI to get things done. It also supports data binding. This library is actively supported and also has a paid commercial version.
On the other hand GWT Ext was developed by Sanjeev Jeevan as a wrapper around LGPL version (no support now) of ExtJS. So the library is a very shallow wrapper around ExtJS javascript and uses JSNI extensively. This can create problems, particularly if you need to debug the library. GWT Ext does not enjoy the same level of community support as ExtGWT and also the original author has long since moved on to a different project. Read about the reasons here.
If you have to choose between the two, and plain old GWT is not an option, choose ExtGWT. Keep in mind that it is GNU GPL licensed.
Neither. You'll have nothing, but problems with third-party GWT widget libraries. I've wasted four years on significantly more refined and mature SmartGWT and finally gave up.
Styling standard GWT components that wrap native browser controls is easy. You should strive for native portable control set and you'll rarely need anything more for a modern minimalistic mobile-friendly UX. However if you still crave some third-party widgets, look at GWT-Bootstrap3: https://github.com/gwtbootstrap3/gwtbootstrap3
I'm looking for some static library or open source project (in obj-c, released under some permissive license) to parse CSS in iPhone. Any recommendations?
OK, I found good library for parsing CSS - libCSS from the NetSurf web browser project. Released under MIT license, can be used without problems for commercial iPhone applications distributed via the AppStore.
It requires some code for the programmer to write (e.g. you need to provide your own DOM hierarchy handlers), and there are no examples available... but people from the NetSurf dev mailing lists are very helpful. In case of problems you can search the list for my questions.
libCSS
NetSurf dev mailing list
I would recommend htmlcxx. It's pretty actively maintained, written in C++ and you can use it to parse HTML and CSS.
Of course, since it's written in C++, you can use it in your iPhone application with no problems at all.
I've taken this project and made it easy to add to your iOS or OSX projects. Clone my github project and add the html (and or css) folder to your project. There is an Xcode project too - so you can build and run the simple test provided by the original authors
I'm work in an aplication that need be capable of support plugins, but i dont know how this work.
See Design Pattern for implementing plugins in your application?
The answers tend to get very platform specific. It also depends on how much control of your core app data and logic the plugin must have.
The C++ QT4 book has a good description of adding a file-type plugin to it's architecture, there area also a bunch of modeling apps (openscenegraph, blender, povray ) that have good documentation for their plugin architectures.
You need to design your application's API in such a way that plugins can be created, and you need to add the necessary plugin management interfaces and supporting code to invoke the plugins. There is no catch-all way of managing plugins.
Take a look at the open source application called Rawr (c#). Each addin is a seperate .dll and the main app uses reflection to access the code. Very nicely done.
www.codeplex.com/Rawr