TWines Application

From Tallus LLC Wiki
Jump to: navigation, search


Tallus Wines allows you to manage your local wine database.

It is currently in pre-alpha stage and will require some beta testers later on. This wiki page is in development and suffers from some unedited copy & paste from other pages...

File:TWines connections.jpg


Once released, TWines will be available through Tallus's app store for $XX.XX.


Latest PC Software version:

- TWines executable.
- Recent version of Windows (XP or newer).
- .NET Framework 3.5.

Client Devices:

- Android device.
- TaWines Application Trial.
- Apple device (iPod/iPad/iPhone) with the iOS 3.2 or newer.



Variety: Grape type.

How to setup for connection with TWines

1) Install TWines_Setup.exe on the Server PC
2) You can now License the application, or continue in trial. TA_Application_Licensing Licensing info
3) On the General Tab, click External and keep External port as 9870 and Image port as 9875. Click Save.
4) On the Wines database tab, Add an inventory name. We will use "My Wines" as the example.
5) If you are connecting to MainLobby or CQC, add that Control type and set a port. 9850 is the default for the first inventory. Use 9851 for the second, etc. Click Add button.
6) On the Updates Tab, select a Database name. Click on the Search 1 tab. You can then type your search terms above in the "Your search" fields. For example, type "Champagne" and click the Search button. You should shortly see several existing Champagnes. If you find one same or close, click on it. You will see the bottom fields populated, including an image if available. You can edit the fields including bottle quantity. Once satisfied, click the Add button.
7) You should then see your first bottle in inventory in the Content tab.
8) You can create a new wine by filling in the appropriate fields and clicking the New button. Image support will be added later.
9) Install the client application of your choice (see above) and follow the directions from the Wiki for that application.


To access the configuration, go to the Home screen of your device (not the Home page of TWines), go to Settings and select the TWines option.

Snoot database connection

The Snoot database allows for easy lookup of wine metadata and importing of your online Snoot catalog.

Client Configuration



File:TWines Status.jpg

Managing your Wine Collection[edit]


Updating Your Online Database[edit]


MLComDevice Configuration (for MainLobby use)

Within the MLComDevice Plugin (running in MLServer application), Add a new Device using the "TallusApp" Family. You can name this "TRadio_XM_1" (as example). This would be a TCP Control. Enter the IP address of the TRadio PC that MLComDevice should connect with. Enter Port 9670 (typical) and Encoding should be UTF8.

Make sure the port you choose is open on the TRadio PC firewall(s) as well as the MLServer PC (if different).

The "TallusApp" family has these default settings: General tab: Header = <STX> Checksum: leave blank Command end: <ETX> Trigger end: <ETX> Description: Connection to a Tallus Application

Commands tab: Name: ChangeValue Code: FieldChanged|<Var1>

Name: ChangeValue2 Code: FieldChanged|<Var1>~<Var2>

Triggers tab: 1st trigger Name: SetVariable Code: SetVariable|<Mask> MLServeCmd: SetVariable|<Device>_<Mask>

2nd trigger Name: SetVariableFast Code: SetVariableFast|<Mask> MLServeCmd: SetVariableFast|<Device>_<Mask>

3rd trigger Name: DelVariable Code: DelVariable|<Mask> MLServeCmd: DelVariable|<Device>_<Mask>

4th trigger Name: AppVersion Code: AppVersion|<Mask> MLServeCmd: SetVariableFast|TRadio_AppVersion~<Mask>

MainLobby scene support configuration

TWines scene is designed to support multiple TWines wine inventories. The variables in the scene display information based on that inventory choice.

Other variables used with the sample scenes:

TWines_tclient1_activeinventory=TWines_Inventory1_1 (this defines the radio being interacted with from a given client PC)

tclient1_radio_1_buylistselection=1 (this defines the particular row selected from the past song playlist)

tclient1_radio_name=HDRadio1 (The display name of the chosen radio)




MLServer Variables[edit]

{{TWines_appversion}}  (defined in MLComDevice Triggers tab)

When displaying wine <X>, where X = 1 to number_of_wines:


Detailed information about one wine (through SetItem~X)



Release notes[edit]

Version 0.33

- Can now release the license during uninstall.
- Changed the ComputerID.

Version 0.32

- Updated the licensing.

Version 0.31

- Added more fields.

Version 0.30

- Keep track of when a wine entry was modified.

Version 0.20 - 0.29

- Fix: Updated entries did not propagate properly.
- Added a delete wine button.
- Enabled the Organic/Sulfites/Parker_Score.
- Fix: was displaying TWine instead of TWines.
- Fix: database now using Sulfites.
- Added support to send images to the external control.
- Added support for external control.
- Enabled the Online registration.
- Can add a wine manually through the Save as new button.
- The Wines class now inherit from TallusModule...
- Can update (save) the current content.
- Keep a local copy of the images.
- Now remembers which item was selected.

Version 0.10 - 0.19

- Redesigned the UI.
- Can view selected properties when displaying the database's content.
- Can modify selected properties when saving to the database.
- Possible work around for MLClient not clearing deleted variables.
- Fix: The Wines_Search_Terms was not getting populated.
- The databases are no longer "model" dependent.
- Can access detailed information about a whine through ML.
- Move the configuration file to its proper folder.
- Fix: The connection to the database was not always properly closed.
- Renamed the Snooth searches tab.
- Enabled the ML navigation.
- Enabled the CQC/ML variables creation.

Version 0.01 - 0.09

- The content list is now filled with proper data.
- Fix: Some escaped HTML characters were not properly displayed.
- Fix: was wiping the wrong list on search.
- Improved the presentation of results from a wine search.
- Results are presented in a listview.
- Can perform a generic query.
- Return the results from Snooth as XML instead of JSON.
- Implemented connection to the Snooth database.
- Proof of concept.