Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - John Hughes

Pages: 1 ... 169 170 [171]
2551
Applied Requests / Elve 1.0 is feature frozen
« on: April 12, 2010, 11:29:50 pm »
While we appreciate all feature requests from our users, Elve 1.0 is currently in its final development phase, meaning it's feature frozen and the developers focus mainly on tying up loose ends and fixing bugs. This means reading and replying to feature requests will not be a priority of the developers before Elve 1.0 goes gold.

Requests are welcome and may make it into minor post v1.0 Elve updates.

Bug reports for pre 1.0 betas are very welcome in this development phase. Those may be posted in our bug reports board.

2552
Bug Reports / READ FIRST: How to post a bug report
« on: April 12, 2010, 11:25:20 pm »
We try hard to ensure that there are as few bugs as possible before a new version of Elve is released. Unfortunately however some bugs do slip through, so we greatly appreciate the help from members of the SMF community, by reporting any issues found while using Elve, to the team. Sometimes, these reports do not contain enough information that would be vital in assisting the team in troubleshooting the issue. This topic will guide you in helping us to isolate the problem with our software. Thus, this gives us a detailed bug report to our developers.

Search First
Be sure to search for topics which may already address the issue you would like to report.  If you find an existing topic feel free to add any additional information.

Post Bugs In Separate Topics
If you are posting about 2 unrelated bugs please create a separate topic for each bug. This will help us keep things organized and will reduce confusion.

Latest Version
When reporting a bug, please make sure you are using the latest version of Elve. If you are beta testing a release, make sure you are using the most up-to-date beta release.

3rd Party Drivers
This is not the place to report bugs or issues with third party drivers. Please direct these reports to the developer of the device driver.

Application or Service
Please identify which application or service the bug appears to be in.

Device Drivers
If the bug appears to be in a device driver please post your device driver configuration report. There is a toolbar icon for this in the devices window. If the bug occurs when accessing a specific device property or method please specify the property or method name exactly as it appears.

Touch Screen Interfaces
If the bug occurs in a specific control type please be sure to specify the control type exactly as it appears in the Touch Screen Builder application, such as Label or Loader Radio Button. If a user interface element is not updating properly please use the diagnostics tools in Elve Management Studio to determine if the associated values in the device are accurate and indicate this in the report.

Rules, Scenes, or Action List Editor
If the bug appears to be in a a rule, scene or the action list editor, please post the associated report using the toolbar icon in the related application window.

Error Logs
It is important to know that there are usually errors that are generated when bugs occur. Please include any errors from the Event Viewer in the Elve Management Studio application that might be relevant to the bug.

By providing us with this information will make sure that your bug report is able to be looked at quickly and swiftly and the possibility of it being considered a support issue is far less.

Thanks

2553
General Discussion / Re: Impressive!
« on: April 12, 2010, 11:04:02 pm »
I have created new Bug Reports and Feature Requests boards. In the past bugs were reported in the most related board, but moving forward I would like to consolidate them to help keep things organized.

Thanks

2554
Please keep topics as separate as you can, so it would be best to start a new topic for you CM15A thoughts.  Also, we recommend the ACT X10 device if X10 is your preference.

2555
Feature Requests / Re: Iviewer
« on: April 12, 2010, 12:44:36 pm »
I'll have to take a look at the overlap in functionality, but we are happy to aid third party developers in creating viewer/control applications for Elve. iViewer is more of a control interface as opposed to a full backend automation solution as I recall?

There are a couple options depending on the iViewer architecture:
1. Create an iViewer driver for Elve that knows how to talk to iViewer.
2. iViewer could use the RESTful web service.
3. iViewer could use the persistant tcp xml protocol.



2556
Third Party Device Driver Software Development / Re: Driver builds
« on: April 12, 2010, 12:39:45 pm »
That's good news.

1. Yes you should create the Drivers directory if it does not exist. (I'll take another look at why I didn't have setup auto-create the directory).
2. I'm open to suggestions but your installer can programmatically stop/start the services in a couple ways. One is to run the net command in the shell, but the better way would be to use the the .net class that does this... I forget the name, maybe something like ServiceInstaller?


2557
Thanks for the excellent details. It sounds like the PPC is making a connection but is losing the connection soon after that?  Did you install the new Elve version of the ppc viewer?  The new version will show a message box if it fails to make the initial connection.

I look into updating the screen so you can see if it is attempting to sign in.  I'll also look into adding diagnostic debugging to the Touch Service and try to get you something later this week to try.

Generally the "The persistent connection with the server was lost." message is an indication that a connection WAS made there was a problem sending or receiving data. 


2558
General Discussion / Re: Congratulations
« on: April 12, 2010, 12:03:05 am »
We're glad to hear it!  Our new forum software should provide a much better user experience.

2559
General Discussion / Re: Elve Enthusiast
« on: April 11, 2010, 09:32:06 pm »
We are still working on the details of the Professional version availability and pricing, and who qualifies as an integration partner. We debated on how much information to disclose regarding the Professional version and hope we haven't caused to much confusion. I will modify the information in an attempt to make it less ambiguous.

The bottom line is that we want to make Elve available to everyone with fair but clear distinctions between the products.  The questions in this thread have been regarding those users who want more than Elve Enthusiast but do not want to hire a professional integrator. We are still working on the details of how to provide this to our users, but rest assured we will have a solution.

Options that we have considered are an intermediate Elve Power Enthusiast license, or even à la carte licensing which would be unlikely.

We are very open to your comments and suggestions and are happy to hear from you.


2560
The default original system administrator account sign in information is:

Username: Admin
Password: admin

These are documented in the FAQ, the Quick Start Guide, and the Elve Management Studio manual. ;)

2561
General Discussion / Re: Elve Enthusiast
« on: April 11, 2010, 05:37:32 pm »
Each user who falls outside the scope of Elve Enthusiast will likely have the same questions. Unfortunately if we made it 5 touch screens and 20 devices there would still be users asking the same questions and that would also narrow the clear distinction between Elve Enthusiast and Elve Professional.

If your needs are more demanding than Elve Enthusiast we have Elve Professional.

If your needs are somewhere in between... we are listening. :)

2562
General Discussion / Re: Elve Enthusiast
« on: April 11, 2010, 03:43:01 pm »
Morten, thank you for your comments.

For most end users who want to configure their own system and don't need support, the Elve Enthusiast package should fit in their scope.  We understand that Elve Enthusiast is not a perfect fit for everyone, such as some veteran automation users and those who are very technically inclined. We will try to work with user's in situations such as yours on a one on one basis.

There is another solution which it sounds like may apply to you. If you really were to write several non-trivial devices and share them, then you would likely qualify for a free version of the software that does not have the same limits as Elve Enthusiast.  Please see our Device Driver Development Incentive Program for more details.

Regarding the comparisons to the other product you mention, we kindly but strongly disagree.

John

2563
General Discussion / Re: Elve Enthusiast
« on: April 11, 2010, 01:29:12 pm »
The feature comparisons between Elve Enthusiast and Elve Professional were designed to provide a clear distinction between the two products and to avoid confusion or conflicts with integration partners and their clients.  Upgrades for individual components or features such as the maximum number of touchscreens available in the Elve Enthusiast version will not be available in our online store. We will monitor this as we go as there may be exceptions for example for long time diy users who want to add a touch screen, etc.

2564
News and Updates / Version 0.21 is now available
« on: April 10, 2010, 06:39:38 pm »
Elve v0.21 is now available for download.

Elve, formerly known as J9 Automation Engine is now available at http://codecoretechnologies.com with free time-limited licenses during the public beta period.

IMPORTANT: After upgrading to version 0.21, each Elve user account must be edited, choose a default touch screen and save. You must save each user account even if you do not change the default touch screen. The user will not have access to touch screens until this is done.

This version has been updated to include our new name, graphics, installation path and other changes related to our new name. Running setup.exe will upgrade your previous J9AE version and migrate your configuration files.

Major changes below have been highlighted blue.

Touch Screen Viewer
* Added new Media Player Seek Slider control.
* Added new Media Player Track Position control. Ex: 1:34
* The On-screen keyboard tab key now tabs to the next text entry field for non-multiline controls.
* Numerous usability improvements to the Sign-In interface.
* In windowed mode the touch screen is centered each time a new one is loaded.
* Fixed: The Media Browser control inadvertently allowed navigating out of the valid page range.
* Fixed: A shown on-screen keyboard is now removed when changing touch screens.
* Fixed: Nested popups were not working.

Touch Screen Viewer Lite
* The Pocket PC app no longer needs to be restarted after changing the settings.
* Fixed: Toggle fullscreen mode was not working in the PC app.
* Fixed: Connection failure messages are now shown in the PC app and PocketPC app.
* Fixed: The PC app not longer tries to reconnect after a bad username/password.
* Fixed: On rare occasions the ppc app could crash during screen interaction after failing to connect.
* Fixed: Nested popups were not working.

Touch Screen Builder
* Touch Screens are now saved/loaded using a hierarchical filesystem-like naming convention. You must edit and resave all your user accounts to ensure they their associated touch screen setting are valid since touch screen names now require a full path.
* The look of a transparent background can now be set to black, white, gray, and several checkered sizes.
* Fixed: Setting an image's opacity when the regional settings used a non-period as the decimal separator would cause an error when the control was edited.
* Fixed: The inner touch screen control was inadvertently loading the specified touch screen.

Configuration
* Fixed: The IR Library window's delay field was incorrectly allowing decimal numbers to be entered.
* For a first time installation, the admin account's default touch screen now defaults to "\General Purpose Sample\General Purpose Main".

Setup Installer
* Fixed: The installer was installing all items even if unchecked.

Scripting
* Scripting error descriptions now include a snippet of the line with the error.

Production Drivers
* All production drivers have had their version number increased to 1.0.

iTunes Support
* Added support for named playlists.

Russound Support
* Updated for XM radio support.

CM15A Support
* Outgoing commands are now logged.

Logging
* Fixed: The log entries are now date stamped with a higher precision resulting is better ordering for events which occur within the same millisecond.

RESTful Web Service
* All requests now return xml, see the documentation for changes.
* All date formats are now consistent, see the documentation for changes.

3rd Party Drivers
* 3rd Party drivers should now be placed in a "Drivers" subdirectory in the program files path.

Driver SDK
* Fixed: The SerialCommunication class's connection monitoring system was failing to send the bytes specified in ConnectionMonitorTestBytes.

Built-in Web Server
* Fixed: The web server did not work on Windows 7.
       
Thanks for all the great user feedback and user provided device drivers.  If you are a .net software developer and are interested in a free software license, please see the Device Driver Development Incentive Program.

John

2565
If you have developed an Elve device driver and are interested in sharing it with the Elve community, we would be happy to award you for your community contribution.

Submitting your driver for inclusion in the Elve installer will give your driver more exposure, a simpler installation process for users, and your name is kept stamped within the driver as the author giving you credit for your contribution.

Once a driver is submitted to us for inclusion within Elve it is normally considered open source. Anyone in the Elve community is welcome to the driver source code and to make changes to it.

Community Contribution Award
As an incentive to those who submit nontrivial device drivers, a free license to the v1 software product will be given in exchange for granting the right to include the driver source code in the product as a built-in driver, to reproduce, modify and create derivative works from at no cost, royalty free, and without limitations, and providing continued support for driver bugs.

While the Elve Enthusiast license is normally awarded, those contributors who produce exceptional drivers, support, and/or multiple drivers may be awarded an Elve Professional (Residential) license at the discretion of the Codecore Technologies staff.

Drivers should be in a form that is usable by the community and not just the author's unique environment.

Getting Started
Sometimes developers will send their initial templated driver and we'll tweak it to get them started. Others request that we template the driver for them to get them started.

We would work with the developer on developing the driver by doing code reviews and making tweaks to the source code to provide assistance. During the continued support of the driver, any modifications to the driver source code would be available to the driver developer.

The Device Driver Development Documentation can be found here.

If you are interested please send me a PM.

Thank you for your your interest in developing device drivers.

Johnny

Pages: 1 ... 169 170 [171]