Meta tags:

Headings (most frequently used words):

2006, may, thursday, sitecore, wednesday, friday, core, development, 23, 2007, august, 24, july, 27, june, 09, 04, 03, april, 28, about, previous, archives, jespers, blog, multi, upload, template, builder, debugging, sheer, image, alt, attributes, html, validation, xpath,

Text of the page (most frequently used words):
the (117), and (28), that (24), this (22), you (22), sitecore (20), media (20), item (17), 2006 (13), #template (12), which (12), are (12), user (12), can (11), for (11), alt (10), upload (9), new (9), have (9), with (9), has (9), xpath (8), #builder (8), from (8), content (8), not (8), editor (8), image (7), posted (7), jakobchristensen (7), comments (7), items (7), will (6), may (5), html (5), blog (5), home (5), fields (5), button (5), text (5), been (5), still (5), uploaded (5), 2005 (4), about (4), key (4), database (4), use (4), some (4), speed (4), all (4), library (4), was (4), what (4), browser (4), box (4), each (4), field (4), dialog (4), july (3), validation (3), attributes (3), sheer (3), previous (3), core (3), developer (3), write (3), used (3), probably (3), good (3), more (3), really (3), now (3), name (3), could (3), one (3), developers (3), make (3), files (3), allows (3), texts (3), attribute (3), link (3), thursday (3), way (3), file (3), line (3), like (3), start (3), command (3), while (3), most (3), when (3), shown (3), first (3), images (3), required (3), meta (3), data (3), writing (3), 2007 (2), august (2), june (2), april (2), debugging (2), multi (2), jespers (2), query (2), implemented (2), main (2), using (2), client (2), also (2), net (2), real (2), but (2), over (2), added (2), reason (2), hashs (2), news (2), corporate (2), before (2), address (2), would (2), part (2), friday (2), tools (2), compliance (2), w3c (2), checking (2), hope (2), these (2), wednesday (2), inside (2), changed (2), versions (2), specify (2), blank (2), general (2), very (2), seeing (2), actually (2), sent (2), controls (2), look (2), boxes (2), after (2), comment (2), see (2), number (2), get (2), lot (2), happy (2), however (2), last (2), couple (2), editing (2), clicks (2), should (2), row (2), change (2), versioned (2), work (2), they (2), haven (2), quite (2), design (2), attach (2), popup (2), width (2), height (2), multiple (2), pane (2), shows (2), jesper (2), development (2), march, january, november, october, september, archives, wallpaper, ignoreurlextensions, json, details, inner, workings, implementation, issues, language, custom, subset, difference, instead, much, easier, api, selectitems, selectsingleitem, methods, sources, lookup, valuelookup, multilist, yields, subitems, center, performance, another, story, tasks, prefer, simplicity, rarely, happends, update, bit, explanation, post, made, small, addition, syntax, quote, identifiers, suppose, dash, interpreted, operator, solve, everything, between, considered, identifier, check, standards, telerik, built, support, review, tab, functions, help, users, compliant, debugger, current, page, received, major, overhaul, stored, folder, versioning, workflow, control, howthe, handled, fetched, different, depending, where, didn, overridden, per, there, useful, event, shell, debug, parse, function, uncomment, refresh, reload, javascript, message, every, gets, annoying, back, soon, above, registers, code, c68, ctrl, mesage, duplicate, single, named, value, usually, request, generates, commands, gettting, positive, feedback, recent, beta, release, extremely, nice, people, seem, system, particular, keeps, recurring, improved, enough, prevaliant, decided, needed, issue, spent, days, implementing, try, listen, saying, veterans, laugh, out, bears, striking, similarites, version, changes, sections, only, saved, save, improves, working, dramatically, metaphor, creating, sql, table, familiar, why, grid, style, add, section, simply, typing, magically, appears, purpose, hidding, complex, settings, setting, titles, languages, specifing, security, open, unchanged, advanced, ribbon, aware, prompted, need, store, side, effect, were, given, chance, how, works, wanted, exactly, same, feel, just, embedded, class, citizens, strategy, turned, true, especially, apparent, common, scenario, uploading, our, switch, create, then, cumbersome, next, allowed, directly, ensure, supplied, information, click, times, finally, surrended, activex, solution, input, trick, concepts, type, via, web, config, means, implement, your, own, supplying, validate, correct, validated, lighthouse, jpg, two, warnings, empty, case, size, either, created, features, glad, seems, collegues, blogs, long, lack, time, internal, debate, proper, unfortunately, hasn, solved, frustrating, http, jesperen, wordpress, com,

Text of the page (random words):
sitecore core development sitecore core development wednesday may 23 2007 jespers blog first of all jesper has a new blog at http jesperen wordpress com i am glad to see jesper writing a blog and it seems that more and more of my collegues are also writing blogs the main reason i haven t been writing in a long while is lack of time and an internal debate on what is proper to write in a blog unfortunately that still hasn t been solved which is very frustrating posted by jakobchristensen at 6 40 am 10 comments thursday august 24 2006 multi upload as most of you are aware of the media library has changed a lot in 5 3 the change was prompted by the need to store the media files inside the sitecore database so that media could be versioned as a side effect we were given the chance the change how the user works with the media library from the start we wanted the user to work with media items in exactly the same way that they work with items the user should feel that a media item is just an item with an embedded file this would make media item first class citizens of sitecore which they really haven t been before this strategy has turned to be not quite true this is especially apparent when you look at the common scenario of uploading 8 images to sitecore our first design required the user to switch from the content editor to the media library create 8 items and then attach the 8 images to each item quite cumbersome the next design allowed the user to upload the items directly from the image browser dialog after each upload the content editor was shown in a popup dialog box to ensure that the user supplied required information like alt texts and width and height however this still required the user to click to the upload button 8 times finally we have surrended and implemented a new upload dialog that allows the user to upload multiple images in one go this is still not an activex solution so we have to use the multiple input field trick that we have used in previous sitecore versions when the user clicks an item in the uploaded media items pane the content editor is shown in a popup dialog box the upload box shows a couple of new features uploaded media items either be versioned or not this controls which template the media item is created from the uploaded files pane shows meta data for each media item in this case the size of the uploaded file uploaded media item are validated lighthouse jpg has two warnings which is probably that the width and height fields are empty media meta data and media validation are new concepts that the developer can attach to a media type via the web config this means that you can implement your own way of supplying meta data to a media item and validate that the fields are correct posted by jakobchristensen at 4 48 am 3 comments thursday july 27 2006 template builder we are gettting a lot of positive feedback on the recent beta release which is extremely nice people seem to be happy about the speed of the client and the system in general however one particular comment keeps recurring which is that while the template editor has been improved it is still not good enough this has been so prevaliant that i decided that we needed to address this issue so i spent that last couple of days implementing the template builder the purpose of the template builder to speed up template editing by hidding some of the complex settings like setting field titles in all languages and specifing security you can still open the template editor which is unchanged by using the advanced button in the ribbon the metaphor in the template builder is creating an sql table which should be familiar to most developers that is why the field are shown in a grid style to add a new section or field you simply start typing in the last row and a new row magically appears the user can make changes to all sections and fields and these are only saved when the user clicks the save button this improves the working speed dramatically some sitecore veterans will probably get a good laugh out of the template builder as it bears striking similarites to template editing in version 2 and 3 i hope most developers will be happy about the new template builder and that we actually try to listen to what you are saying posted by jakobchristensen at 12 23 am 7 comments friday june 09 2006 debugging sheer there is a very useful way of seeing what is actually sent to the browser in a sheer event in the sitecore shell controls sitecore js file look for a line like this this debug it is in the parse function if you uncomment this line and refresh the browser to reload the javascript you will start seeing message boxes for every command that is sent to the browser after a while this gets really annoying so you will comment the line back soon what you see in the box is a single command with named attributes and the value usually each request generates a number of commands so you will get a number of boxes the above command registers the key code c68 which is ctrl d with the mesage item duplicate posted by jakobchristensen at 2 51 am 1 comments thursday may 04 2006 image alt attributes the media library has received a major overhaul in 5 3 the image files are now stored inside the database and not in the upload folder which allows real versioning and workflow control over media items as part of this and the tools for w3c compliance we have changed howthe image alt texts are handled in the previous 5 x versions the alt text was fetched from the alt attribute on the link to the media item so that you could have different alt texts depending on where you used the link if you didn t specify a text in the attribute the alt text was blank in 5 3 if the alt attribute is blank we use the alt text on the image item this allows the user to specify a general text on the image that can be overridden per link posted by jakobchristensen at 2 34 am 1 comments wednesday may 03 2006 html validation in 5 3 we have added some tools to check for compliance with the w3c standards the new html editor r a d editor from telerik have built in support for this the content editor has a button for checking all html fields in one go in the review tab and the debugger has a button for checking the current page we hope that these 3 functions will help users and developers make compliant html posted by jakobchristensen at 3 17 am 1 comments friday april 28 2006 sitecore xpath the sitecore xpath query language is a custom implemented subset of xpath the main difference is that instead of this item key sitecore item key content item key home you can write sitecore content home which is much easier sitecore xpath can be used from the api using the database selectitems or database selectsingleitem methods in the sitecore client you can use the it in the sources for lookup valuelookup and multilist fields e g query sitecore content home which yields the subitems of home you can also use sitecore xpath in the new xpath builder in the developer center of 5 3 the performance in net 2 0 is probably not as good as real xpath net 1 0 and 1 1 is another story but for some tasks you prefer simplicity over speed rarely but it happends update i have added a bit more explanation the reason for this post is really that we made a small addition to the syntax you can now quote identifiers with hashs suppose you have an item with the name news corporate before you could not address this item as the dash would be interpreted as an operator and not a part of the name to solve this you can now write sitecore content home news corporate everything between the hashs is considered a name or an identifier posted by jakobchristensen at 5 47 am 32 comments about details about the inner workings and implementation issues in sitecore from a core developer previous jespers blog multi upload template builder debugging sheer image alt attributes html validation sitecore xpath json ignoreurlextensions wallpaper archives july 2005 september 2005 october 2005 november 2005 january 2006 march 2006 april 2006 may 2006 june 2006 july 2006 august 2006 may 2007