Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Has anyone tried OpenFin? What are its pros and cons?
In terms of Development effort, stability, development support, maintenance, performance, memory footprint.
I am part of the OpenFin Dev team and I have to say in terms of Development effort we are always improving our development tools, and have a large collection of example code that tackles some of the popular scenarios, we also have a yeoman generator that makes it super easy to get started: https://github.com/openfin/generator-openfin
In regards of stability, we ship a mayor release twice a year and you can chose to stick to a particular version at an application level. each deployed application can choose a particular version and it only takes a change in the server to have the clients updated on next app start.
Development support is highly active and we will work with you to resolve any issues. as I mentioned above we have created example code for popular scenarios.
Maintenance, would be similar to any web application without the need to support multiple browser versions, additionally we provide API's to create Windows installers for any OpenFin application.
Performance, you get all of the benefits of the V8 engine for JavaScript and the Blink layout engine. you also get API calls to monitor CPU and Memory.
Memory footprint, The OpenFin Runtime will create processes for each application and has several internal processes of its own, the actual footprint depends on what features you are using.
You can see a feature comparison between OpenFin and other solutions here https://openfin.co/runtime/compare/
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
We are a startup based in India with an application built on Qt Quick, which is deployed in HD touch devices in retail stores. The application runs more like a web-app rather than a desktop app. But we have serious hiring problems and fear of future while using Qt Quick. Hence we need to know if to go ahead with the same or shift to a more widely adopted stack like HTML, CSS and JS.
The data is served using a locally deployed web server(syncs with cloud from time to time) which serves data using the recommendation and search engine. We use Qt Quick for both getting data using AJAX and the UI is made using QML's elements, Touch Events, Animations, State - Transitions. We are left with very basic operations in C++ which read configuration files, etc.
We had developed a prototype 2 years ago in HTML5 using Sencha and were not very happy with the performance and touch behaviour, hence we picked Qt. But because it is much harder to develop 'beautiful' looking apps in a fast development cycle on Qt, stylesheet'ing is extremely naive on Qt, I want to reconsider if to move from Qt back to HTML5 or think of another framework. You can safely assume we want to deploy across Windows and Android.
Both tools can help developers to have high-quality graphical UI in embedded and mobile space. It all depends on your needs to choose one for developing your application. I think that QML/C++ is better in terms of fluidity, quick iterations, consistency and scalable data visualization.
HTML5 has some difficulties:
Implementing rich UI’s with good performance
Mixing with native technologies
Finding developers with knowledge of HTML5 & CSS3 in resource-limited environments
You can also use HTML5 in Qt-based applications. So i think having hybrid applications leveraging the best of native and Web depending on the use case seems a good idea.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm currently setting up ghost on my server. I will host my own blog and probably some more for my friends.
Ghost uses sqlite per default. Sqlite is good for small applications and development environments.
I plan to run my blog for at least 1 - 2 years or longer if ghost will work out well. A blog contains a lot of images and text. The sqlite db will grow over time with more and more images and so on.
Is it ok to use sqlite for this purpose for several years? MySQL would be much more powerful but also more complex to setup.
What would be the best choice for a Ghost Blog?
Please note that database performance depends not so much on the amount of data (until you run out of local disk space) but on the amount of concurrency.
The SQLite documentation says:
SQLite usually will work great as the database engine for low to medium traffic websites (which is to say, 99.9% of all websites). The amount of web traffic that SQLite can handle depends, of course, on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic.
[…]
But if your website is so busy that you are thinking of splitting the database component off onto a separate machine, then you should definitely consider using an enterprise-class client/server database engine instead of SQLite.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am starting a simple windows forms application that requires a database to store inventory and purchasing records (less than 1000 items). What I want to ask is for your opinion which 'lite' database should I use for this small project, considering that the prerequisites I'll be installing in a client computer should have 'minimal' file size.
The client computer has a running OS of Windows 7, and I don't want him to install so many files, such as the .NET framework and the server that hosts the database, just to install the main application I'm currently developing.
What I'm really asking from you guys is to find out which of these two commonly known databases should I use, and look for the 'right recipe' to be used when building the installer. Thank you.
Of the two, SQLite is simpler to install and deploy. Fewer files, smaller distribution footprint and fewer configuration options to deal with (mostly because SQLite is a library that links into your application where as MySQL is a full client/server RDBMS).
SQLite is made for extremely simple database needs, and is probably a good fit based on your description.
I have never heard of MySQL Lite and a web search turned up nothing, so I will assume you meant MySQL. MySQL is a RDBS client/server system and probably major overkill unless you plan to store many records, or to have multiple people accessing the database at the same time.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I am a software development guy. Lately I was thinking of trying out some firmware development, as the company I work for is trying to enter that domain.
I have many questions regarding firmware devlopment - like:
What are the tools used - like IDE?
In which language is most of the code written in?
How to port the code into microcontroller?
How to code for different microcontrollers?
How to determine things I would need for building a specific application(choosing the microcontroller etc.)?
Anything else I should know about and where do I start? Sorry if this question is too basic, but I could not find out any satisfactory answers elsewhere.
Most microcontrollers have decent C compilers so are best coded for in C, although you might need to delve into assembly routines for occassional high performance routines. The choice of microcontroller is usually determined by the hardware demands, on board peripherals, performance and cost constraints.
You wouldn't generally be porting code from a Windows/Linux/Mac environment to a microcontroller one; you would generally be writing directly for the microcontroller, so strictly the compiler is a cross compiler - compiling on your PC to run on a different processor. You typically get debuggers, emulators and full editor capabilities in the IDE, so its a similar experience to writing code in a PC environment, but it runs slower, and has to be downloaded to the target hardware or emulated to be tested.
A great authority to start reading about embedded development is Jack Gansle and his firmware handbook. Also www.embedded.com for general articles.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
How do you estimate a EAI project using Function point?
FP analysis is inappropriate for integration projects of any sort as it presupposes that you can specify the application up-front. Most of the work in any integration project of non-trivial complexity is reverse-engineering the nuances of the environment. Typically the environment will not be exhaustively documented in the sort of cases you would expect to use an EAI system in.
By the time you have actually done this level of reverse engineering to the point of having a complete specification you have done most of the work in the project - the actual development is fairly short and sweet by comparison. Therefore the function point analysis is only providing an estimate for a small part of the system.
As an aside, much of the work I do is data warehouse systems in Commercial insurance companies, where extensive prototyping and reconciliation exercises to produce detailed specification documents are actually quite appropriate to the environment. Typically this takes longer than actually developing the production system as most of the data issues are resolved in the prototyping work. EAI systems have a similar class of implementation issues.
Well given that FP counting is based on storage and end user interface, not sure if its even meaningful for EAI (from what little I remember).
I would say you can't, at least not in a useful way. FP counting is generally viewed as a dubious practice of varying accuracy, doing it to an integration project would just add more fuzzyness.