A big difference is cf.Objective()'s is ending November 30. Check out Sean Corfield's post for more information on the cf.Objective() call.
A big difference is cf.Objective()'s is ending November 30. Check out Sean Corfield's post for more information on the cf.Objective() call.
Here are the tentative tracks for sessions:
They note as well that they're always open to new speakers.
Finally, the pointed out as well that the early bird deadline is Nov 30. More at CFUnited.com.
One is a 3-minute conglomeration of comments from several people. These are both the "official" Adobe talkinghead-style videos, and some are more like "live remote shots" taken from the floor of CFUnited. Besides a couple of appearances in it, near the end they included me saying something fairly quotable. I'll let you find it. :-)
Then there's a another set of individual interviews with different folks (the talking head style), which appear (currently) at the top of the CF9 product page. You click on whichever one shows up (or click "community feedback") and an interface like slide show picker appears. You can pick any of them and at the end it offers to advance to the next. (That link to them at the top may eventually no longer appear on that page, I suppose.)
It was a treat being interviewed for these.
I got the invite over the summer and was told they'd be taken in a room at CFUnited. I assume the others were done there, too, but I don't know. The room was staffed by a video production team.
There was no way of telling for sure as we did them whether what we said would be included ultimately, and/or how much. Indeed, the interviews were a lot longer than what was showed (about 30 minutes for less than a couple), so much ended up on the cutting room floor for each of us, obviously. That was to be expected, of course, and I'm just thrilled to have been included at all.
My only disappointment: well, if you look at the videos and even the pictures at the top of the page, you'll notice something about mine stands out from the others. The production folks had made a point from the start about wanting me to "be sure to use my hands", so my inteview and picture show me gesticulating pretty vigorously. :-) It's not really my normal style, but if that's what they wanted.
But then I notice NO ONE ELSE is. Maybe I was an early interview and they dropped it eventually. If I knew the folks doing the interviews, I might feel like they punked me. :-) Heck, even on the tight shots (where they zoom in the editing) you can still see my fingers flying into the frame. Grr... :-)
I notice that my shiny face also appears (for now) further down the product page next to a link labeled "Get Inspired". That's cool to see. I suppose it may well rotate with other folks (but it hasn't when I've refreshed it today).
Guess my 12 years of CF experience have born yet more fruit. Thanks, Adobe. And certainly I hope what I said is of value to some viewers, brief though the interviews are. Next time, if invited back, I'll also wear a less floppy-looking shirt! :-)
The problem is annoying, because if you have no other sync failures (such as Outlook calendar sync errors), you can't know for sure without digging into the hotsync log.
The good news is that Palm has come out with a solution to make this finally go away:
As it discusses, you install that app onto your phone, and then run the FixPMTrace app on your device. It's important to note that it's NOT ENOUGH just to install the app onto your device. You do have to run that app from the Palm launcher (the list of apps, accessed by the "home" key, as usual) in order to have it do its magic. All it does is turn off the archive bit on a file so it stops trying to back it up.
Hope that helps someone else.
PS And before some of you jump on me for still using a Palm, :-) just know that yes I am seriously considering moving to an iPhone after several years of relative happiness with my Palm devices. I've been using a iPod Touch for a couple of years and really like that. Carrying both devices is of course a pain, so reducing it to one just makes sense.
And yes, I know about the Palm Pre. It's just that Sprint coverage in my home is really poor, and since I generally work from home, I just can't take it anymore. The Pre won't solve that (I called: they said it wouldn't likely be any better.) Since my wife has ATT and she's been happy, the forced move to ATT with the iPhone isn't a problem.
Still, I leave this Palm tip for those who may benefit.
One interesting document you might miss is the "Windows Vista SP2 and Windows Server 2008 SP2 Test Focus Guide", which is a 40-page guide that lists various changes, with scenarios and step-by-step instructions to recreate and observe the feature changes.
That's a nifty idea, and one I wish more vendors offered. It's not something I've seen offered for previous Windows OS releases (base or SP's).
I don't think it lists every feature, but it does list many that I'd not seen mentioned in the more glitzy "what's new" docs (at the URL offered up top here). By contrast, the Test Focus Guide is more text-heavy (all stuff, no fluff) and kind of rough.
For instance, I wish it offered more of a table of contents, because you can't readily eyeball what all it covers. I found the easiest way to find each topic is to search for "goal:", since each scenario has a listed goal.
Anyway, check it out. You may find something of interest there among its dozens and dozens of scenarios.
If you start to use the new Adobe Presentations service, an online presentation-building tool, now at labs.adobe.com, you may want to engage in some discussion with other users, so may go looking for some forums. You may struggle as I did.
Sadly, there's none for it listed at the acrobat.com forums page. Perhaps that's because Presentations is still in lab status.
There's also none listed in the Help menu for Presentations. There is a link to share feedback, which gives you an email address. That's better than nothing, but it's not a discussion forum. Some may even fear using it if it might be a black hole.
I decided to go ahead use that feedback address. I was delighted to get a response pretty quickly (well, first an automated one, and then a real person).
But what surprised me most was that the automated email (offered in response to using that feedback address) offered the URL for the forum!
So where is the forum? It's at: http://forums.adobe.com/community/labs/presentations/.
I responded that this link really ought to be listed in the Help menu of Presentations, but that suggestion seems to be challenge for them to implement. Oh well. I decided to share the info here, and also as a comment in a blog entry on Presentations in the Acrobat.com blogs.
Just seems it shouldn't be so hard to find these forums.
Still others aren't specific to web development, but can be valuable to all kinds of developers, and it was one of these that led me to the site in the first place:
The site is Better Explained, whose tag line is "Explanations for everyone". The author does a pretty good job of that. Some of the topics are a little too one-sided (the discussion of HTTP compression does only show setting it up in Apache, not IIS), and of course there's no mention of CF anywhere. :-) But we can't expect that from everyone. There are lots of positive comments and linkbacks on on many of the entries, so he'd done a good job in the eyes of most.
Indeed, if you may be hearing the siren call of Ruby on Rails, they have an article on that: Starting Ruby on Rails: What I Wish I Knew. There's also an intro to MVC, but again it's from a Rails perspective: Intermediate Rails: Understanding Models, Views and Controllers.
If there's something you'd like to see the author address on the site, he has a post for that, too: What do you want Better Explained?.
Some may read this and say, "big deal, I've been doing that for years", but it's one of those little things that some just never notice or think of. If you've not considered the option, why not check it out?
(Update on 9/30/2010: Others may have noticed that they DID have it set to more than 10, but recently they lost that functionality. I have the solution for that, as well.)
Others may say, "well, why choose to see more than 10? They offer buttons to let you page through the results", but the point is that people often will not page through them. I can tell you from my own experience that seeing more than just those "top 10" results when searching makes me more inclined to quickly consider more results. More on why do it in a moment.
The change it really simple. Just click the "Search Settings" box to the right of the top of the search page at google.com. (It used to appear to the right of the search box as a "preferences" link, but now it appears at the top right instead.)
If you're logged in, it will instead show as a link to "Settings", with "Search Settings" as a menu option under that when you click on it.)
On the preferences page, the 4th option controls the number of results.
Sure, they warn that 10 results per pages is "faster", but in these days of high speed internet, that's of course a relative assertion.
As I noted above, some may have noticed that even with that setting set, and saved, they still see only 10 results. In fact, if you re-open the preferences page, you'll see that it just ignored your choice and is back to 10. What gives?
The problem is the new "Google Instant" search feature, implemented recently (by default), which allows search results to appear as you type in your search criteria. If that's enabled, then Google does not let you set the results to more than 10. That's a shame, but worse is that they don't warn you of this when you try to change the number of search results.
The setting appears two below the "number of search results". Choose "Do not use Google Instant", if you want to see more than 10 search results.
Sadly, if you try to change both settings at once (turn off "Google Instant" and change "number of results"), that doesn't work either for the same reason above. Instead, do it in 2 steps: turn off Google Instant, save the preferences, then edit them again and change the number of results, and save that.
It really is too bad that Google doesn't handle both problems more gracefully.
So why make the change to see more results? We all tend not to want to page forward through search results, right? But often some of the best results--those with real valuable info--are beyond the top 10, perhaps just beyond them, or perhaps 30 or 40 down.
Of course, hucksters know that people are reluctant to page down and go to great lengths to get their stuff in the top 10. (Granted, there are many fine entries which also show up in the top 10 just because they deserve to.)
But if you set your results to 30 at a time (or some other number larger than 10), you're just more likely to find (or consider) other results. It's surely paid off for me, and the speed to show more results is hardly noticeable.
Also, seeing 30 at a time makes it feel like no problem to go through a hundred results (including following the link to look at some of them) in a matter of minutes. Just something psychological about feeling that paging forward a couple of times is no big deal, but I see a lot more results doing that than if it was set to 10.
(And given the conflict with "Google Instant" discussed above, I'm happy to forego that feature to see more results instead.)
Hope this may help some of my readers.
PS Oh, and if you have changed the Google preferences but find your browser keeps losing the changes over time, check out the other recent entry I referenced at the top here, which addresses this very problem.
So Firefox 3.0.7 landed on my machine today as an auto update. Like me, you may find that these point releases aren't too much to write home (or blog) about. Often it's things like adding "Estonian, Kannada, and Telugu" language support. No offense to them, of course, but it's not something to get me get excited.
Still, I watch the release notes whenever a new release is pushed (just like I comb more carefully the far more interesting release notes for any new CF release), as you never know what surprise may be in store.
Today, my reading the release notes paid off. There's word of a fix to the problem that's the subject of this blog entry:
"For some users, cookies would appear to go "missing" after a few days (bug 444600)."
Well heck yeah. It's been really annoying. And reading into that also showed how to solve the problem in other browsers.
Just like those in the support team (discussing the problem in the bug note), I would find that every couple of weeks various sites I visit often would have lost their cookies.
For instance, I set my Google search result preferences so that I see 30 search results at a time, rather than the default of 10. Suddenly it would be reset, which was very noticeable.
Or my bank would suddenly act like I'd visited the site for the first time on my laptop (when I'd used it just last week), and it make me go through extra authentication. That was annoying.
I knew it had to be a problem of the cookies being lost, but none of the obvious things were the problem. It was a nuisance, but not the end of the world.
Before pointing out the solution, I'll note that some may put on their debugging hats and wonder about what might have been other possible causes. It would have been easy to suspect a lot of things when faced with this problem.
Was it that the cookies being set (and lost) just had a suddenly early expiration date? Well, no, that wasn't it. (And these were major sites, like Google, my bank, etc. They don't make such mistakes, at least not more than once, typically.)
You might wonder if it was something I was doing on my system. No, I wasn't clearing out cookies. I just don't have call to do that, though I know some do when facing some development challenges.
I also don't regularly run any tools that might have been doing this for me, such as registry cleaners, anti-virus tools, etc. (And no, I don't run an AV tool all the time, and I've never suffered for it. I'll blog about that in a future note.)
So, sure, good to do the diagnostics. And an A for your effort, but it wasn't the problem. (BTW, this troubleshooting and helping people think through problems and use diagnostics is indeed what I do for a living now, helping people solve problems related to CF, so I really do respect and appreciate those who try to solve things on their own first. But if you do that and still have a problem, or can't take the time or don't know where to look, I can help.
So, back to the fix, it's great to see this it may well have been due to this issue now recognized and fixed in FF 3.0.7, which basically comes down to a combination (explained well in the bug note) of both a low default for how many cookies FF should keep (1000) and an eviction algorithm that didn't take into account how recently you'd visited a site before kicking it out when the limit was reached. Very nice.
You can learn more about the release, and get it if you've not auto-received it yet, here.
Oh, and if you want to up the number without applying the fix, the setting is called network.cookie.maxNumber, and you can tweak it using about:config (in FF), to access the underlying configuration settings.
As always with such tweaks, be careful. And naturally, raising the limit could eventually cause FF to take up a little more space in its repository to hold permanent cookies, and in memory. The bug note reports an estimate of about 1-2m per number increased, FWIW, so forewarned is forearmed.
As for those using Chrome or other browsers, note that you may find the same default setting of 1000 is limiting you. Whether and how to set it may vary, of course. Chrome, for instance, offers no about:config or other seeming way to edit its config settings (correct me if that's changed.)
I looked briefly and couldn't find how to set this in IE, Safari, or Opera, but if anyone reading this finds it, please share as a comment.
A couple of final observations: the bug note talks about how to get an interface tool for querying the underlying SQLite database, including SQL statements for detecting most recently accessed cookies,etc. Interesting to explore.
I also wanted to talk about an interesting observation from seeing discussions that took place from people trying to solve this problem. It's an interesting case study in troubleshooting and where one can go wrong. And I wanted to explain why changing the Google preference from 10 to 30 is a good idea. This has gotten way long, so I'll write those up as separate entries.
Well, sadly, his wife Dale has been diagnosed with Multiple Sclerosis, something he's made public on his blog. In addition to his sharing his experience there, she's has been journaling her experience and emotions on their blog. I'm sure many are finding comfort in their incredible strength and fortitude in the face of such a trying experience.
Still, the costs for treatment will be monumental, and so a group of CF community members have gotten together to create a site, www.helpsupportjoeanddale.com offering a way for those interested to offer donations to help offset those costs. So far the collections have been going really well, and all the money goes to them directly.
You can even watch a short video at the bottom of the page where Joe and Dale express their appreciation for this outpouring of support. All this was a surprise for them, and it's been a touching testament to the greatness of this community. I wanted to wait a couple of weeks to put the news out there again for those who may have missed it the first time.