xeriph

Hi ppl! I am starting to get more spare time to try some Wherigo coding for real, but as far as i know, there is a lot of improvements to be made. I already instaled the Player on a borrowed IPAQ (QVGA) and my own Acer (VGA), and the graphics and text on Acer does not give the feel i except. This could be one of the first things to be handled. IMO the argument of the majority of PDA are QVGA is not a reliable one, since there is a lot of PDA on the user hands already VGA. If that is a valid argument, why support the Colorado now? We could wait until it becomes a sales hit and then do the builder improvements for it... I think for the development and feedback of all the coders outhere, the main issues to be handled are: the QVGA/VGA adaptation, the international units issue (metric/imperial), the non-english characters problem (also common around the globe) and some Hw issues as they are identified. Trying to get more people to code and detect problems on player and builder can only be achieved by suporting the main situations of PDA users everywhere firstly, and the main diferences but common between devices (resolution and regional units/settings).... do not neglet the target-VGA coders... i am one of them and that can make the decision of continue to code or stop...

In adition to the things I mentioned, I stated also the following situation: as Portuguese uses accentuated chars ( ç, á , é,etc.... ) there's currently no way to get those texts correct and variable names working fine... The name created/edited for a zone ion builder is used both for the 'name' property and lua object name... Let's get WhereitGo builder with worldwide support...

Hi there ppl... As this builder is still growing up and many as I are making basic experience on coding with it, I think cartridges not involving complex challenges, but basic event handling, should have source opened to those who may have good ideas but still are figuring out 'how to do it'.. At this time, my experiences are facing two problems... builder-ones (bugs or things still unpolished) and lack of proper know-how (by absence of builder documentation). So it is time to all of those who have progress more share it to newbies like me....

Hi to all Wherigo community... this is my first post and I wish all the envolved a good future for this project, as it opens new space for ideas, events and all sorts of outdoor activities. I started to use the Builder to do some basic program testing. I never used lua, but the IDE is simple enough to start with. I have a lot of raster maps georeferenced for my area and also i am used to cross GE information and raster map information. As I experienced before, there's an variable offset in GE satelllite coordinates which affects more or less 'the hole world', so urban areas, narrow zones and distances below 30 meters in most cases should be field checked if used for accurate Wherigo experiences and coding. My zone creation tests showed a bug I think it is easy to take care of: I am from Portugal, so metric units are my mother unit. When creating a zone, in the editing of distance and proximity, although changed to metric unit, the builder saves and create script file as 'feet' with the same value, affecting those spaces in the field. I stated this on the code generated and in the emulator, as I felt distance and proximiity boundaries too close to the zone defined. Only editing by hand the .lua file parameters in Distance(...,"[uNITTYPE]) to metric made the cartridge act as i expected. A second point relates to this, as the emulator shows also distance in feet or miles. Can this be an option on the emulator too?. Is this contemplated in the player for PocketPC for metric users? I will try to make some field testing with a QTEK 9090 PDA in some weeks so see if things run, triyng to check if ithis HW works too and how... I hope to write more about Wherigo, as i became immediate fan of this idea.