Tuesday, March 6, 2007

More jEdit stuff

Hello everyone,
I had been working on some jEdit Scripts this week, this scripts are like the Java Tool Set we have made in the past, but it is much better it has Graphical Interface. And is integrated with one of my favorite editors jEdit.

Here you can read about his new tools: http://code.google.com/p/aircable/wiki/jEdit_Tools, you can even watch a video there to see the scripts in action.

If anyone has a comment, suggestion, question, etc, don't doubt to ask,
Thanks
Manuel Naranjo
AIRcable Development Blog Admin

Saturday, March 3, 2007

Code Highlight for JEdit

Hello everyone,
I just ended submitting a file that does the code Highlighting for AIRcable Basic code in the JEdit editor.

You can find the file here: download
You will need to modify the file that is under $HOME/.jedit/modes called catalog, you need to add this line:
before the tag.

$HOME is C:\Documents and Settings\\ in Windows or /home/ in Unix systems like Linux or Mac.

Here you have an snapshot of how the code highlighting looks like:

With this new tool you can tell if you are writing the code well or not. If any of the commands you write doesn't highlight somehow then that command doesn't exist on the OS.

This is the first part of our next AIRcable JEdit's Pluging, feel free to try it, and to give us your comments.

Thanks,
Manuel Naranjo
AIRcable Development Blog Admin.

Friday, March 2, 2007

Command Line Version 0.6 Released

Hello everyone,
We had just released the command line version 0.6. This new version includes a lot of new and exciting stuff like:
  • Command line over Bluetooth for the AIRcableSMD.
  • Power Measurement for the future AIRcableOS.
  • PIO list editing from the command line.
  • PIN and Name settings regarding the unique number of each AIRcable device.
  • Parity and Stop Bits configuration from the command line.
  • .....
You can see the electronic version of the docs from: here.

And you can download the code here:
UART Version - For all Devices
SPP Version - Only for AIRcableSMD

Please leave your comments with feedback, suggestions and questions, feel free to ask.
Thanks,
Manuel Naranjo

Tuesday, January 30, 2007

Tutorial Started

Hello everyone,
We had started working on our Tutorial/Example series, you can find it all here.
As we continue working on this you will start finding more links.
Thanks,
Manuel
AIRcable Development Blog Admin

Monday, January 29, 2007

Sample Programs

Hello again,

We know how hard is to start knowing a new technology from the scratch, with that in mind, we had made a list of example programs we are going to put on the web, so our costumer can use them as a reference for they're code.

This list is temptative, and can change a lot, so please if you think there is something we are missing, something you think we can add or delete please let us know, we are here to help you. Here is the list (the order is not relevant):
  • Micro Slave: A simple code that opens the slave port on discoverable mode and accepts all the incoming connections. It will teach you how to open the slave channel, and how to make slave connections, and finally how to handle leds.
  • Little Slave: Like the micro slave, but now it will open the shell if the user press "+" when the connection is firstly started. It will teach you how to handle input characters and how to open shell connections.
  • Filtered Service Slave: A more complex mode, it will open the port in discoverable mode, but will check that those who want to connect to this peer complies with an address pattern. It will teach you how to compare string, and reject incoming connections.
  • Cable Slave: This is a piece of code taken from our command line, that will pair to a device, and then will apair invisible to all the other devices. It will teach you how to make an slave device discover and undiscoverable.
  • Mini Master: This code will make inquires, and once it found a device it will try to connect, once the connection is closed. This will teach you how to handle alarms, make inquires, handle inquires results, make master connection, and check master connections.
  • Filtered Service Master: This code will make inquires, and if the device it discovers matches a given pattern it will make a connection, once the connection is lost it will connect to the first thing it can find. It will teach you how to work with inquires showing how sensitive they are.
  • Listed Master: Those interested on buying AIRcable Mini or SMD can be very interested in this code. This code will have a predefined list of devices (between 0 and 30), will open a connection to each one of this (one at the time), will make some work over the connection, will close the connection and will continue with the next device, all this on an endless working cycle. It will teach you how to iterate, control state and close master connections from the master side.
  • Cable Master: This code is like our Cable Master, it will make inquires and will pair with the first device it can find. Once it is paired it will not inquiry any more and will only connect to it's peer. This code will show you a way to handle pairs from the master side.
  • Interactive Code: Sometimes you need an interactive shell on the other side, this code will teach you how to write a simple interactive program that will let the user control a series of leds and will read some analog/digital inputs.
  • Relay Mode Code: This code will show you how easy is to create a network of AIRcable devices. For this example you will need at least 3 different bluetooth devices, and one of those 3 must be an AIRcable OS enabled device. In this mode the AIRcable OS device will be connected to two other devices and will make a bridge between them, this way you can make the range of your bluetooth devices much longer.
Please let us know if you think we can add something more, or if you have your examples and want to show us your way to achieve things feel free to do it. Also if you need some support with your work, let us know we can surely help you.

Thanks,
Manuel
AIRcable Development Blog Admin

Saturday, January 13, 2007

Command Line Version 0.5 Released, Devel Tools Alpha Release

Hi,
The version 0.5 of the command line is ready for be used. You can download it from here: http://aircable.googlecode.com/files/0.5_.zip you can also download our source code from here: http://aircable.googlecode.com/files/0.5-src_.zip

We have also been working on a set of tools that you can use to make BASIC code development easier. The tools can be downloaded from here: http://aircable.googlecode.com/files/aircabletools.jar, this devel tools need and will only run with Java 6 which you can get from java.sun.com . If you want to try this tools simply do java -jar aircabletools.jar (from inside the folder where you downloaded the tools), you will see the list of commands, and if you do java -jar aircabletools.jar you will get the list of arguments to that command. This set of tools is the base for our next JEdit Plugin, so you can start trying them while we work on the plugin.
Just one thing, there is a bug on the code related to lines movement. In case you want to move code you firstly must move the code to an empty area (For example line 2000 which can't be used), you make all your work on those lines and then get them back to it's original place. We know this bug, we will correct it in the future.

Fell free to test our stuff, and give us your comments.

Thanks,
Manuel

Tuesday, December 19, 2006

AIRcable's JEdit Plugin

We are starting to work on a plugin to JEdit, the idea is to someday on the future have a full IDE for working with our Basic code.

Here are a list of somethings that our pluging might do in the future (not in order):
  • Find References, this will simply find all the places where a certain line is called.
  • Move Line, this will change a line number and update the references.
  • Move Piece of Code, this will move a selected piece of code to some other place, will also take care of references.
  • Full Code Renumbering: this will make all the code related to each interrupt be togheter (I mean all the lines will be one after each other) then it will renumber all the interrupt and will try to leave 10 lines between one interrupt and the other.
  • Syntaxis higlighting.
  • Systaxis and Gramtic checking, this will also check that all the command used are real, and nothing is miss spelled.
I wait for your suggestions,
Thanks,
Manuel