I’ve been a fan of Pebble smartwatch for a very long time, both as a user and developer, but recently, even before announcement of Pebble acquisition by FitBit I got curious – what else’s out there? Two mainstream branches of smartwatches – Android Wear and “The Watch” are of no interest to me – too boring. So I looked into Samsung Gear watches – Tizen platform is very interesting, then it was Vector Watch (which ended up being bought by FitBit as well) and now a new ePaper watch from Chinese company Shenzhen – SMA Q2 (sometimes called SMA Time).
There is no question that despite obvious visual similarities, at this point in time Pebble Time Steel is vastly superior to SMA Time. PTS is on 4th generation firmware which brought many advanced features over the years, PTS has a very popular appstore and high quality developer ecosystem. SMA Time feels like Pebble circa firmware v1.x (probably even less, e.g. it has only 3 slots for watchfaces on the watch) but it seems to have great potential.
I am posting here a few pics comparing PTS with SMA Time. Continue reading 'There’s new reflective LCD in town (SMA Q2 vs PTS)'»
One would think that classic UltraWebGrid control would not be touched by 2010+ Infragistics NetAdvantage upgrades, perhaps some bugs would be fixed, but definitely no new ones should be introduced – since no new development is done on the control.
One would be mistaken, The Adventure Of Upgrading liveth on.
If you’re using UltraWebGrid, and its columns’ width is set as a percentage and some columns are hidden, e.g. you have something like this:
<igtbl:UltraGridColumn Key="COL1" Width="25%" Hidden="True">
<Header Caption="My Important Column"></Header>
var oBand = igtbl_getGridById('xMyGrid').Bands;
When you add a subdomain to your site, many hosting providers will automatically create a new physical folder on the server to match the subdomain name and to serve the subdomain content from. Which is all fine and good if your subdomain has a completely different content from main site/other subdomains.
But there’re situations when you need several subdomains to point to the same physical folder. Case in point: WordPress multisite install. There’s only a single installation of WordPress software, but depending on how you access it – it will serve different content. For example if you visit http://kitchen.galanter.net you will see a culinary blog, but if you open http://codecorner.galanter.net – a programming content will be served to you. This is achieved by WordPress by reading host header information (HTTP_HOST) and depending on header name (“kitchen” or “codecorner”) different content will be served. But it will be served from the same physical folder
Many hosting providers allow you to select root folder for the subdomains – in this case it’s easy: just add subdomain, point it to the root folder of the main domain and you’re done. But some, like my current host hard-code subdomain-subfolder relationship and it’s not allowed to change. In my case my root domain (which serves http://www.galanter.net) is physically located in /galanter.net/public folder. When I added subdomain codecorner, provider automatically created folder /galanter.net/codecorner/public which would have a completely different content, but I needed its content to be served from main /galanter.net/public folder, just pass “codecorner” HTTP host header to it. Enter symlinks. Continue reading 'Use symlinks to serve subdomain content'»