Comments for dotEvan

Comment on iPhone and Diabetes by johnO

johnO — Sat, 02 Apr 2011 14:16:45 +0000

Hi Evan, I am totally frustrated, as you are with the lack of integration of kit. There are iphone components being publicised without any release date, which seems common from the industry – I have had my hopes raised countless times by the “cure diabetes” stories in the past, hard to take when I was younger.
I live in the UK, and have just bought an ipod touch 4th gen, explicitly for tracking etc, but imagine my annoyance when Apple refused to let me pay for the FREE wavesense app, because it is only allowed for US customers. I complained, but got nowhere.

You are not an edge case, I am an engineer, and am very used to dealing with data in my life, and really want something with good analysis tools for reviewing data.

Like you, I have concluded that you need to write your own tools.

If you ever come up with something, I am interested and would pay if someone creates an app with integrated, or “cloud” data analysis.

Thanks John.

Comment on Third Party Headsets and iPhone 4 (UPDATED) by Augusta

Augusta — Wed, 23 Feb 2011 06:31:50 +0000

Yes I have the same problem – though not with the Bose kit. I also upgraded from the 3G to the iPhone 4 and have lost the ability to use my headset. I had been using an over the head telephone operator style headset because it was excellent while driving (non-distracting, easy to hear, comfortable) and because I’m somewhat paranoid about excessive exposure to the kind of radiation generated by phones, esp. “smartphones.” Anyway my mic no longer works and I too get intermittent clicks and or the iPhone “decides” to switch to the internal mic. Very frustrating and I really wish Apple had been more forthcoming about this. It’s not like their engineers would not have known they were making this kind of change to the audio hardware. Anyway I’d love to find a solution. After many years in camp Apple I think this is the “Steve knows better than you consumer” moment that’s going to make me jump ship. Hope someone has an answer or that at least Bose can engineer a work around.

Comment on Creating a self-signed (wildcard) SSL certificate by Vector

Vector — Fri, 18 Feb 2011 13:05:57 +0000

Eh, sorry, one more thing, it looks like this doesn’t work for those of us who do not use “www” in our domain name? Is there a way around that.

Comment on Creating a self-signed (wildcard) SSL certificate by Vector

Vector — Fri, 18 Feb 2011 13:04:22 +0000

I’m guessing that as long as you have your stuff setup from the last time you created a cert, that means that you don’t have to sign the new one? I thought that i remember having to type in a password the last cert i created.

Man, i guess it sounds like i should take some time to crack down and learn more about ssl. Anyway, great article, thanks. I’m using it for both my mail/imap and web server.

Comment on Creating a self-signed (wildcard) SSL certificate by Vector

Vector — Fri, 18 Feb 2011 12:39:47 +0000

Hey, great article man! I’m about to see if this kind of cert breaks my postfix imap functionality (i know nothing about ssl…).

Thanks!

Comment on Why I use Smarty: PHP is an ugly templating language by Maarten Tibau

Maarten Tibau — Fri, 10 Dec 2010 10:04:45 +0000

@Jesse Dhillon

Quote “Did you know that you can use to echo a variable? That is the same as .”

When working with the Zend Framework and if you follow the coding conventions, the use of short opening tag of PHP isn’t allowed.

I’ve been working with Smarty for 4 years now. I love it, but I hate it sometimes as well. Like some people already said, you should have to look at each project and see which choice is best.

The idea of Smarty is giving people who don’t have PHP skills the ability to change templates and for that it should be used.

Comment on Why I use Smarty: PHP is an ugly templating language by Paul Ellsworth

Paul Ellsworth — Fri, 03 Dec 2010 14:56:55 +0000

A small clarification… I don’t code the HTML in PHP, and I do use standard but high speed text replacement logic in smaller HTML sections, which means that technically I am using templating. But it only takes about four functions, and is so simple I can teach it to a new programmer in less than an hour.

Comment on Why I use Smarty: PHP is an ugly templating language by Paul Ellsworth

Paul Ellsworth — Fri, 03 Dec 2010 14:54:08 +0000

I’m not sure that there is a tool out there I’d recommend, and that includes any of the main templating engines. My reasoning is simple: the amount of work that goes into making the engines perform has always outweighed the amount of work it takes to learn to break the construction of a good website and page into easily managed programming tasks.

For example take the typical 3 column “blog, link, and article site” with the following components: A header bar, a footer bar, a top menu, a left side menu, stacked right side boxes, and a main area where all of the links in the main page place their results. Make it even more complex by making the top menu a “tab bar menu”. Now decide to make the whole thing very dynamic and web 2.0 and how about the mobile site, the android version, and the iPhone app… Oh, and now that my CSS skills are coming up to snuff, I can really….

Do what? go back and redo all of my templates? perhaps double, triple, or quadruple the number of templates I have to use?

It’s not that I don’t believe in the separation of user interface from business logic from pure programming. It’s just that I can use nearly pure programming to build easily comprehensible components that output to pure HTML/JS-Ajax/css’d files (which is what the server sends out to the world anyway, and let CSS, etc. take care of the rest.

Comment on Why I use Smarty: PHP is an ugly templating language by williamjxj

williamjxj — Thu, 02 Dec 2010 01:04:46 +0000

Things depend. smarty just a option.

Currently developing includes html, css, js, maybe some libraries. the testing and debug is not a easy work.
using php without template (in dreamweaver) is a total WYSIWYG (that’s why dreamweaver is hot).

the purpose of php is to make developing easier and rapidly. forget the templates and mvc framework, except you use some CMS or open-source framework.

Smarty is only smart on present level template, but not smart on whole web developing at all!

Comment on Why I use Smarty: PHP is an ugly templating language by dek bryon

dek bryon — Mon, 29 Nov 2010 05:53:11 +0000

Had to fix a site made with Smarty, my first experience and a bad one – it’s an admirable effort but pointless. They’re years behind MVC and anyway, I think the task is so large a small team will always play catch-up. Version 3 is horrendously buggy and anyway, replacing php tags with their own is only going to lead to a new language (IF it continues), perl verses php and so on. I wouldn’t recommend it to anyone I like.