Tonyt_ For me, I like to learn by solving a real problem, helps keep me interested. I would suggest you create a simple application, and learn Ruby in the process. Perhaps a blog
My customer wants to access the functionality of niche desktop applications through a web application. I am struggling to provide compelling arguments as to why this is a bad idea. Any thoughts?
My customer wants to access niche desktop applications from a web application. These are not libraries, but full blown Desktop applications with GUI front ends and no API's, and we have no control over them. I am struggling to provide compelling arguments as to why this is a bad idea.
the niche application(s) are complex, they calculate room heating and lighting based on building size, shape, windows, topography, oreientation and locations, also taking into account reflections
A client of mine has made some company acquisitions ~30. Each of these companies has their own site and authentication. They want me to create a master authentication system that can be used by all the company sites, and that will allow for a gradual consolidation of accounts over a period of time. Any ideas on good approach to this problem please?
thanks, good advice. I was thinking more about the mechanism by which consolidation could take place. How would a user go from an account on subsidiary site, to a master account on the parent site?