Voor sommige apps is het geweldig, voor andere ronduit belachelijk : Drag & Drop in websites. Use it wisely. Mocht je beslissen dat je het nodig hebt dan is het de laatste jaren in elk geval een stuk makkelijker geworden. Onderstaande artikeltjes lezen zou moeten volstaan.

http://www.jqueryui.com/demos/sortable/#empty-lists http://www.webresourcesdepot.com/dynamic-dragn-drop-with-jquery-and-php/

Ask yourself this question: what if everything could be queried with SQL? Microsoft’s LogParser does just that. It lets you slice and dice a variety of log file types using a common SQL-like syntax. It’s an incredibly powerful concept, and the LogParser implementation doesn’t disappoint. This architecture diagram from the LogParser documentation explains it better than I could:

Coding Horror: Microsoft LogParser.

Many developers have asked for a faster, more powerful way to access google Analytics account configuration data through the Data Export API. We’ve listened and today we’re releasing a preview of the new google Analytics Management API.

The Management API provides read-only access to google Analytics configuration data. It consists of 5 new google Data Feeds that map directly to the google Analytics data model…

Google Analytics Blog: Launched: New Google Analytics Management API!.

Assume nothing, test everything! En het kan gratis, met google Website Optimizer kan je eenvoudig A/B testen en multi-varianten testen uitvoeren. Dolle pret!

http://www.google.com/websiteoptimizer

Leuk nieuw experimentje. Mijn eigen FrontierVille blog. Het doel is om alles ‘by the book’ te doen. Give google what they want. Een keurige blog, mooi maar braaf geoptimaliseerd, 150 unieke keyword rijke posts, een domein met de keywords in, goeie linking (ongoing)… En nu kijken wat er gebeurd. Gaat de SEO werken? Gaan de adwords Quality score hoog zijn? Voorlopig ziet het er veelbelovend uit. +-30 UV een dag of 2 na launch, terwijl de linking nog moet geoutsourced worden.

Ook de click-throughs naar de producten (2 FrontierVille guides) zijn redelijk. Dat is dan meteen de volgende stap, A-B testen en optimizen. Fun fun fun. Ook zowat het enige dat ik voor dit project niet ge-outsourced heb.

www.IPlayFrontierVille.com

In ASP.NET 2.0 ResourceProviders allow extension of the native resource mechanism with your own resource backing store by implementing a custom ResourceProvider. I’ve recently published an extensive articlethat talks about this process in detail and why this can be quite useful.

One of the issues that I’ve been struggling with is that the ASP.NETResourceProvider(s) are not directly accessible from your ASP.NET code. ASP.NET basically gives you access to HttpContext.GetGlobalResourceObject() and HttpContext.GetLocalResourceObject() but that’s about as close as you can get to the loaded providers ( ASP.NET actually loads many instances of providers – one for each resource set).

Since I built a provider that allows live resource editing as part of the application, and so it’s only logical that you would want to see the changes in the resource provider either immediately or after explicitly refreshing the resources. As it turns out this is not easy to do because ASP.NET hides the Providers from you. No unloading for you!

In the past I’ve used a hack http://west-wind.com/WebLog/posts/5688.aspxto accomplish this: Basically force the AppDomain to unload by either calling HttpRuntime.UnloadAppDomain() or even more hacky by touching web.config causing the timestamp to change and thus forcing ASP.NET to reload the application. Both of these actually work, although both have security issues you need to worry about. The former requires full trust, the latter that you have write file access rights to Web.config neither of which is guaranteed to be available.

*A better way: Hang on to your Hats – er, Providers*

So as I was wrapping up my article I got to thinking about this problem again. With a custom provider implementation it’s actually possible to keep track of the providers as they are loaded. Once you have a list of the providers, unloading the resources is really not difficult – since resources are typically cached in Hashtables/Dictionaries in memory it’s easy to clear them out by releasing each of the dictionaries holding the resource data.

So here’s what I did in my provider (which otherwise is fairly standard implementation so this should be easy to apply to any custom implementation).

I set up a static LoadedProviders property (List<>) that keeps track of all the loaded provider instances, and a method called UnloadProviders() to loop through the list and then call a custom interface method that unloads the providers.

volledig artikel http://www.west-wind.com/weblog/posts/121171.aspx

Deze is een aanrader. Met de Autoblogged.com plugin kan je heel eenvoudig RSS feeds in je wordpress importeren. Je kan ze sorteren, bewerken, combineren. Een aanrader dus. Klein nadeel, deze is niet gratis. Maar het is de $59 zeker waard ($129 voor meerder sites). Als ik er ergens nog een promocode voor vind zet ik die er zeker nog bij. AutoBlogged.com

3.200 kg, 50 cm

kleine test met postie plugin, benieuwd of het online komt

#IMG%#

Met image dus

http://ppcblog.com/how-google-works/