I'm working on my project's versioning and I want to adopt the guidelines from here.
I just have one question that either I didn't get or the material didn't cover. How should the release version look?
My understanding is that having a pre-release label is for internal development, as well as the build metadata. When building the artifacts for a release version, should you strip all the labels and keeping only the version core, i.e.: major.minor.patch? What label could get into source control and which must never do?
In the spec, there are release and prerelease versions. A release version does not have zero for the major field or have a prerelease tag attached. You are free to do whatever you like with regards to build-meta.
In the real world, a "release" is anything you've published, such that it is publicly available. So for internal use, do what you want, but for external use, follow the spec. In other words, you can release a prerelease version by publishing it.
Related
The methods that are missing from the apk file are
BorderLayout.centerEastWest()
Dialog constructor with (String, Layout) as arguments.
There are probably more but these are the ones I encountered. I can work around the problem by using alternate methods and constructor but there seems to be a mismatch between the local library and the android build library.
Please note that when building the project I had to use the android.gradle=false hint for the apk to be readable on my older android 2.3.6 device. Without this hint the apk is not accepted on the device.
In addition the theme resource file is not loaded on the device while it is in the simulator. All these problems might be related ?
Thanks for your help
New features are no longer added to the old Ant build pipeline as maintaining it has become unwieldy since Google no longer supports proper versions of play services or other features we need.
We still have it for compatibility for people who built old applications with it but it's version of the Codename one libraries is frozen in time as newer versions of the libraries will break it. Google killed support forthe 2.x device family ages ago in play services so basic things like in-app purchase or proper location API's can't work on those old devices. The problem is that supporting them would make support for newer features MUCH harder.
I've edited the docs to reflect that this flag is deprecated.
I recently read FIRST CLASS ECLIPSE SUPPORT which made me expect a cn1lib-wizard. But there still is none, right?
The gist of the article is that we will update the Eclipse plugin with the NetBeans & IntelliJ versions. With the trend of migrating towards common code across IDE's within our plugin (the new settings UI) this should be much easier and Eclipse should no longer be out of date with the other IDE's.
I'm not sure when we'll get around to do the library template, unlike the other features it requires some work since the Ant implementation on Eclipse is rather different. So it's hard to give a specific date.
GtkGlArea is listed in the Widget Gallery of Gtk+3.0. There is official documentation for it, which states that I only have to include gtk/gtk.h to use the desired widget.
But I can't find any OpenGl mentions among header files of gtk+-3.0 package. And of course, I can't call any of the gtk_gl_area_* functions without stumbling upon undefined reference error.
Is GtkGlArea not available in Gtk+ 3.0? If so, why is it showcased on the official website?
If it is available, how can I use it in my C project?
GtkGLArea was added in GTK+ 3.16. If you look at the documentation page for GtkGLArea, you will see
Since: 3.16
under gtk_gl_area_new().
If you are running GTK+ 3.14 or lower, you do not have access to GtkGLArea. Your distribution can tell you which version you have installed. If your distribution does offer a newer version, then you will need to install it. (The current version as of this writing is GTK+ 3.18.)
If you don't have GTK+ 3.16 or newer, and need to stay with the version of your distribution that you use, you have a few options:
find someone else's OpenGL widget; here's one and here's another
use jhbuild to install a local version of a newer GTK+ version and use that to develop
use a virtual machine with a newer distro to develop
EDIT: You can also see documentation for the specific version of GTK+ you need to target by choosing a version from this list. (The same applies to the other documentation sets on developer.gnome.org.) If backward compatibility is your thing, you should also look into the GDK_VERSION_MIN_REQUIRED and GDK_VERSION_MAX_ALLOWED macros.
Yesterday I downloaded the new Agile Toolkit 4.3 and found that the licensing and subscription model has been changed. Additionally a "developer sandbox" has been included which launches when the toolkit is first run and requires me to login with a registered account.
While I understand the reasons for these changes, and I'm fully supportive, the sandbox appears to be unnecessarily restrictive. However, there seems to be no easy way to bypass the sandbox, and logging in to the sandbox in a vanilla install of 4.3 leads to a screen where you are forced to choose between a pre-canned Admin or Frontend site.
The key reason for me to upgrade from 4.2 to 4.3 is the introduction of an Application class to support RESTful services. I have no need for either an Admin, nor a Frontend web user interface and yet the sandbox does not provide this option.
Is it possible to bypass the sandbox setup process and, if so, how would one go about doing this?
Looking at this in a different way, the folder structure of the ATK4 library seems to have changed under 4.3. Version 4.2 included documentation on the folder structure and how a developer should setup their application in relation to that structure. I have been unable to find corresponding documentation for Version 4.3 which would give clear guidance on how to build an application around the toolkit without relying on the included sandbox.
Hi Tim (i'm author of Agile Toolkit)
Agile Toolkit framework will continue to be available on github. You will find link to github on the bottom of the page, simply select branch 4.3. All of the documentation still applies and you can use the framework (you still need to respect the license). Github does not contain "admin" or "frontend", it is included for the convenience of new users.
The licensing terms has slightly changed, Agile Toolkit has always used AGPL and Commercial licensing. The reason to introduce the sandbox is because developers were not respecting the license terms. I also wanted to give easier ability to deploy projects for new PHP developers and for security it can only be done through sandbox.
Here is a blog-post outlining all of the changes: http://www4.agiletoolkit.org/blog/rebooting-agile-toolkit
The folder structure have changed, but it must still be compatible with the 4.2 branch. I've adopted the usage of "public" folders for improved security, but please do look into PathFinder documentation on how to customise folder structure.
I've been looking around to find the release notes for the latest releases but I couldn't find it. Anyone have a link?
Different parts of the project have different logs of the changes between versions. The most comprehensive changelog for the project is the one for the Java language bindings, and it can be found here. Other portions of the project may have their own changelogs, but they are usually limited to changes only within that part of the project. Examples include the changelogs for the .NET language bindings and for the IE driver standalone server.