In all cases your browser will take you to Issues, the system we use to track these reports. It's designed to gather all the necessary information that helps us track down bugs and implement feature requests.
To create a new issue, click the New Issue button. You can then enter a Title and Description of your issue and attach any relevant files such as screenshots and projects. As you enter the title, any existing issues that match your keywords will appear. You can then click on the title of any of these issues to review them. If you find your issue has indeed already been reported, comment on that issue rather than create a new one.
REALbasic Project Requests up, Up, UP!
A good issue is well defined, with (in the case of bugs) reproducible steps and a project that demonstrates the issue (if applicable). Our statistics show that issues with sample projects are fixed faster than cases without sample projects.
Any pictures you use in your project or open and display via code are going to be sent from the server to the user's browser. The bigger those pictures/files are, the longer sending will take and the less responsive your app will be. The smaller the file can be the better.
Pictures that are part of the project take up space in the app binary and are always loaded into memory, which causes your app to take longer to load. They also can take up up to twice as much memory as the picture when you go to use it because they are converted from Picture to WebPicture.
Displaying small images (stored in the project) is generally fine. However browsers will cache the images that don't change, so it's important to use a WebPicture whenever possible (as shown above) because they return caching headers.
WFS is still available on GitHub, but it has languished over the years. For example, it has lots of legacy code in it for older versions of Windows that is no longer needed since Xojo only supports Windows 7 and later. WFS is also not really compatible with 64-bit projects since the Declares mostly assume 32-bit or bust.
I would like to finish this post with a huge thank you to every user that has helped directly or indirectly creating Issues, attaching a sample project, posting on the Forum and testing the beta releases.
The first app that I demonstrated is SuiteTalk Explorer, which can be used to send requests to NetSuite's SuiteTalk REST API. I developed SuiteTalk Explorer because I figured that if I could use Xojo to build that type of app, then it was likely that I could use it to develop any app that required integration with NetSuite. SuiteTalk Explorer is a desktop application that can be run on macOS, Windows, and Linux-based computers.
I also demonstrated a few basic iOS and Web apps. One of the apps can be used to lookup inventory in NetSuite, while the other two provide access to employee information. In demonstrating those apps, my goal was to show the variety of apps that can be developed with Xojo, how easy developing apps can be, and how you can reuse code between Xojo project types.
To use any of Mapbox's tools, APIs, or SDKs, you'll need a Mapbox access token. Mapbox uses access tokens to associate API requests with your account. You can find your access tokens, create new ones, or delete existing ones on your Access Tokens page or programmatically using the Mapbox Tokens API.
Each access token you create will have a set of permissions that allow the token to make certain types of requests to Mapbox APIs -- these are called scopes. The API documentation lists the scopes required for each Mapbox API. When creating an access token, you will have the option to add public or private scopes to the token.
You can make your access tokens for web maps more secure by adding URL restrictions. When you add a URL restriction to a token, that token will only work for requests that originate from the URLs you specify. Tokens without restrictions will work for requests originating from any URL.
Unfortunately, building console helper apps is much more difficult than it needs to be. I first wrote about the need for the IDE to abstract away a huge portion of this effort in the first part of my 2017 review series in March of last year. I have not received any feedback from Xojo or heard anything in this area to facilitate this need. It is getting harder to sell Xojo as a rapid application development tool when your projects become significantly more complex when the IDE could so clearly help you. I hope to see some announcements in this area at XDC.
All responses are returned in JSON format. We specify this by sending the Content-Type header. The Web API v3 provides a selection of response codes, content-type headers, and pagination options to help you interpret the responses to your API requests.
Time to hit the run button! Because you always have to compile a Xojo app every time you want to test the result, this can take take quite some time if you are working on a big project. Xojo has no live code swapping so this is something you have to do even for a minor change, like changing the color of a label. But that is just the way the tool works.
Just Add Software creates most of its products in Xojo, a powerful cross-plaform language and development environment. This section contains a number of free classes and controls that any other Xojo user can download and use in their projects.
Over 10 professions were represented (collection supervisors, managing director, archivist, publishing manager, communication manager, project manager, curator, national mission manager for PatSTeC (contemporary scientific and technological heritage) and RéMUT (network of technical museums and collections), etc.)
Meetings with the Muséum d'Histoire Naturelle, Lille, mobilized teams with a view to a GLAM project in 2015. The aim will be to eventually highlight the 350,000 items grouped into 4 major heritage collections: the naturalist collections (110,000 animals, stuffed or in jars, or living in aquariums or terrariums), the earth science collections with a wide range of geological samples and fossils from the coal mining area, the little-known extra-European ethnographic collection and the regional industrial and technical history collection.
On several occasions, partners of all types have been interested to note that the Wikimedia movement has an international scope and have considered deploying certain pilot projects on a larger scale. Wikimedia France would like to capitalize on this interest in order to combine the efforts of the different entities in the movement and give greater visibility to its actions.
The inspectors responsible for drawing up directives in agreement with the Ministry of Education are still just as reticent about using Wikimedia projects in class. The approval, which gives the association legitimacy in its educational actions, should remove this reticence in the long term, but it will take more time than for the people involved directly with the classes (teachers, instructors, etc.).
This quarter also so the launch of the first Wikimedia France crowdfunding project: WikiCheese.The project aims to use participative financing to finance a project to illustrate articles on Wikipedia linked to cheese, which will begin in Q3 and run by a member of the local Île de France group (cf Crowdfunding, Focus 6)
An association member has offered the theme of project management by volunteers for the next strategy weekend. Invitations have been sent out to all local group contacts. They will have two days in which to get to know each other and talk about setting up local actions and the structuring of communities.
Alongside this, another target was to start prospecting for new partners for the Afripedia project.Finally, Wikimedia France has made great efforts to continue to build up links with the various people involved in the movement (hosting, regular telephone conferences between opposite numbers, training sessions and exchanges of good practices, etc.).
In October, French-language contributors organized events to publicize Wikipedia and contribute to the encyclopaedia during the second French-language contribution month.Contribution Month has several aims:To encourage the production of content locally;To enable local contributors to meet in the different participating countries;To introduce newcomers to Wikipedia publishing and its brother projects.
Two Wikipedians, Florence (France) and Isla (South Africa) have decided to organize an annual photo competition on the subject of Africa. For the competition, participants will send in photographs, videos or audio documents for use on Wikipedia, Wikimedia Commons or the other Wikimedia projects. The competition theme will change every year. The aim is to share the lives, environment and day-to-day activities of Africans with all the inhabitants of the planet on Wikipedia.
With an eye on the revision of the Afripedia project and, more globally, on supporting the French-language Communities project embodied by WikiFranca, Wikimedia France met with the International Organization of French-language Communities in November.The meeting was productive, producing outlines for possible collaboration with third places in Africa, which could become involved and take on a project such as Afripedia, adapting it to their own local issues.
We were also visited by Honoré Yameogo, from Burkina Faso. Honoré had asked to spend 3 days with our chapter collecting ideas for setting up a Burkinabé chapter. He felt that the Afripedia project was a good way of starting off a unifying action locally. He was also made familiar with the existence of WikiFranca, the French-language list run by WMCH, the African-Wikimedians list and a wide range of tools and processes used by Wikimedia France.
The various French-language chapters and other organizations linked to WikiFranca have not yet managed to produce an international evaluation of support for the event. This is a challenge, particularly as the WikiFranca coordinator is a volunteer and is running a large number of other projects in Canada. However, we are hoping to receive a detailed evaluation of the action with figures, with a view to developing Wikimania, for example.Another Wikimedia France action (a survey of the French-language Wikipedia readership) has aroused interest in Canada and Switzerland, but these chapters are not showing much evidence of involvement, again through the lack of time available for this action.Given the difficulty of collecting the necessary information concerning the impact of the action on the Wikimedia projects, we will draw up this evaluation during the next quarter. 2ff7e9595c
Comments