eHome Digial Tools

After kicking it around for awhile we have started on a version 6 of eHome...

A couple of things to come.
1 - eHome is getting trimmed down. Will only include weather, PH screen designer and browser
2 - Main program will still be in VB6 so as to run on low end hardware
3 - Built in Snapin architecture so custom audio, video or whatever can be added via DLL's
4 - Admin side is being re-written in .NET / Mono
5 - Install will be *MUCH* easier
6 - Source code will be available.
7 - PPC is planed to be supported via the screen designer as well as more support for different HA products.

This is more of an intern type of release, the end result is for all of eHome to end of in Mono so as to run in either Windows or Linux.

eHome V5.x will be left as is (converted to donation-ware) but a branch will be produced that will include only Audio, video and games. (can you say IFE?)

Comments?

I like it.

It seems like you could have two products here: A general touch screen app and a front-end for automation systems. Diversification can't be bad!

That I have noticed. I have a few dedicate people who are just using the Audio - Video and building collections. The CD and DVD rippers as well as unlimited multi location storage make it a unique product but these people have ZERO interest in screen builders and recipe editors. Then there is the HA screen builder people. They have there audio and video collections already and just want some nice cool HA screens. So yeah, two products really.

Also, I am at over 100,000 lines of code for all, for 1 programmer its getting unmanageable and really difficult to add to - debug. Toss in my touch screen died and that my a@@ is in Eastern Europe and replacement parts cost an arm and a leg get anything over here. (Power here is SO bad that in the last 2 years my immediate family has lost a refrigerator, 2 microwaves, 1 boom box, 1 TV, 3 computers and 3 power bricks to various items) to bad power. OK, off of my soapbox!

So OK, 2 base products with the eventual migration of the HA - screen designer to mono for Linux, Any other suggestions? I will wave at all of you in my 12 hour layover at the windy city airport!!!!

Also... Screen designer format is staying the same so migration (if you chose ) will just be copying the DB.
Question, anybody running more then 1 location for their custom screens?

Also... (got to love also's)
One of the other big reasons for the change is debugging the product as is - is getting really difficult. I use a whole lot of sub classing and other Win32 tricks (and while these are fine compiled) the VB editor has really begun to choke on debugging, sometimes what should be 20 minute fix is a half a day with a few blue screens of death and allot of Russian vulgar!

Questions - thinking of supporting multi weather channels, basically 3 or 4 buttons so you can check weather in different cities? What do you think?

Question, anybody running more then 1 location for their custom screens?

Looks like I need to do some ripping and shredding here. Going for simple remember?

Gets your votes in!!!! LOL

anybody running more then 1 location for their custom screens?

Err, eh? As in multiple clients?

TonyNo wrote:

anybody running more then 1 location for their custom screens?

Err, eh? As in multiple clients?

Yep! 2 touch screens running custom EH custom designed screens

On another note... weather is done, browser is done, converting screen designer now.

I have one remote client and plan to add at least two more once I get my WHA re-done.

Running two clients here.

Screens are being rendered...
Now working on the .NET new admin. So much simpler now...

Question?
What speed are the computers are you using?
Ram? , Processor?

Questions - thinking of supporting multi weather channels, basically 3 or 4 buttons so you can check weather in different cities? What do you think?

Anybody care?

I only live in one place.

Server: 1.7Ghz P4, 768M RAM
Clients: 1GHz Athlon, 768M RAM; 1.8Ghz P4, 384M RAM

Sounds great to me. I like the idea of a simpler system and more robust plug-in components. It also gives you the chance to focus on the more important aspects of the system, the parts that are purchased more frequently.