Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2015-07-08 08:24:30 +0200

Welcome to QML hell. Each platform comes with it's own (Blackberry, Jolla, Nokia used to as well). My suggestion is to strongly anticipate design issues by generalizing as much qml code as possible, if you go cross-platform, and have a solid background either in c++ or javascript.

Welcome to QML hell. Each platform comes with it's own (Blackberry, Jolla, Nokia used to as well). My suggestion is to strongly anticipate design issues by generalizing as much qml code as possible, if you go cross-platform, and have a solid background either in c++ or javascript.javascript. The particular issue you are seeing is caused by a requirement of the SFOS sdk; which in turn is introduced by the type of packaging required (RPM's).

Welcome to QML hell. Each platform comes with it's own (Blackberry, Jolla, Nokia used to as well). My suggestion is to strongly anticipate design issues by generalizing as much qml code as possible, if you go cross-platform, and have a solid background either in c++ or javascript. The particular issue you are seeing is caused by a requirement of the SFOS sdk; which in turn is introduced by the type of packaging required (RPM's).(RPM's). You basically need to add the RPM's YAML file, out of whch the SPEC file will be created, that will then be used by the rpm utilities to create the actual RPM.

Sidenote : The more I type about this, the more I realize how crazy this whole process is ;)

Welcome to QML hell. Each platform comes with it's own (Blackberry, Jolla, Nokia used to as well). well, dont know about android). My suggestion is to strongly anticipate design issues by generalizing as much qml code as possible, if you go cross-platform, and have a solid background either in c++ or javascript. The particular issue you are seeing is caused by a requirement of the SFOS sdk; which in turn is introduced by the type of packaging required (RPM's). You basically need to add the RPM's YAML file, out of whch the SPEC file will be created, that will then be used by the rpm utilities to create the actual RPM.

Sidenote : The more I type about this, the more I realize how crazy this whole process is ;)

Welcome to QML hell. Each platform comes with it's own (Blackberry, Jolla, Nokia used to as well, dont know about android). My suggestion is to strongly anticipate design issues by generalizing as much qml code as possible, if you go cross-platform, and have a solid background either in c++ or javascript. The particular issue you are seeing is caused by a requirement of the SFOS sdk; which in turn is introduced by the type of sw packaging required format utilized by SFOS (RPM's). You basically need to add the RPM's YAML file, out of whch the SPEC file will be created, that will then be used by the rpm utilities to create the actual RPM.

Sidenote : The more I type about this, the more I realize how crazy this whole process is ;)

Welcome to QML hell. Each platform comes with it's own (Blackberry, Jolla, Nokia used to as well, dont know about android). My suggestion is to strongly anticipate design issues by generalizing as much qml code as possible, if you go cross-platform, and have a solid background either in c++ or javascript. The consistency problem got pushed over, or better, extended from C++ to QML. Bear in mind, I believe QML to be a great scripting language, and on top of that an excellent UI language. I believe the QML language is simply not (yet) flexible enough to handle "plugin abstraction", if we can call it like that. Sure, there are ways around it, but in most cases they are ugly.

The particular issue you are seeing is caused by a requirement of the SFOS sdk; which in turn is introduced by the sw packaging format utilized by SFOS (RPM's). You basically need to add the RPM's YAML file, out of whch the SPEC file will be created, that will then be used by the rpm utilities to create the actual RPM.

Sidenote : The more I type about this, the more I realize how crazy this whole process is ;)