La description :mostly sharepoint stuff but some general it stuff as well ...
Classement Alexa Global: # 12,601,099
Server:GSE...
L'adresse IP principale: 213.186.33.19,Votre serveur France,Roubaix
ISP:OVH SAS TLD:com Code postal:fr
Ce rapport est mis à jour en 30-Jul-2018
Created Date:
2007-02-28
Changed Date:
2016-02-18
Données techniques du jonathanroussel.com
Geo IP vous fournit comme la latitude, la longitude et l'ISP (Internet Service Provider) etc. informations.
Notre service GeoIP a trouvé l'hôte jonathanroussel.com.Actuellement, hébergé dans France et son fournisseur de services est OVH SAS .
Les informations d'en-tête HTTP font partie du protocole HTTP que le navigateur d'un utilisateur envoie à appelé GSE contenant les détails de ce que le navigateur veut et acceptera de nouveau du serveur Web.
MX preference = 1, mail exchanger = mx1.ovh.net. MX preference = 5, mail exchanger = mx2.ovh.net.
HtmlToText
skip to main | skip to sidebar mostly sharepoint stuff but some general it stuff as well saturday, june 15, 2013 scroll gantt view to today in sharepoint 2010 & 2013 abstract , here is a trick to have the sharepoint gantt view displayed scolled to today instead of the first day of the earliest task. tested on sharepoint 2010 & sharepoint 2013. here comes the trick and how it was found sharepoint gantt views are a great tool to visualy embrace a set of data\dates but they suffer from a few usability issue. first one is that gantt view always center on the earliest date of the tasks displayed. this is often an issue if you display projects spanning multiple months or year as you don’t see today’s situation : we decided to fix it. our first stop was to take a look at sharepoint out of the box spgantt.js file (spgantt.debug.js for convenience), where best to find out what was possible. searching for scroll brought up a few reference including this very promising one : this.scrollgantttotask=function() …. _jsgridcontrol.scrollgantttodate(date); …. next step was to manage to get an handle on this jsgridcontrol object. fiddling through the dom with google chrome (elements and console tabs) we found out the *_listviewwebpartjsgrid object had a nice jsgrid property that returns the object we need and this object indeed have a scrollgantttodate function if you use jquery here is how to retrieve the object and scroll to today. depending how\where you use it, you might want to make sure the object exists (if($("div [id$='_listviewwebpartjsgrid']").length) ) before using the property jsgrid. $("div [id$='_listviewwebpartjsgrid']")[0].jsgrid.scrollgantttodate(new date()) tada ! publié par joe à l'adresse 7:22 pm 19 comments: email this blogthis! share to twitter share to facebook share to pinterest libellés : javascript , sharepoint , sharepoint 2010 , sharepoint 2013 , sp2010 , sp2013 friday, february 15, 2013 sharepoint 2010, power up your tags by making them clickable sharepoint 2010 introduced a great new feature that is used even more in sharepoint 2013, the tags. a major drawback of tags is that they are not clickable except in very specific scenario. this post will explain some termstore\tagging concept before explaining how to make these tags clickable through a relatively small development. i’ll also talk very briefly about how to put in place a custom tag page as a target of these clickable tags. not all tags are born equal the managed metadata service application aka as the termstore or to put it simply: tags serves a lot of purpose from document classification to libraries navigation, search facet (even navigation and friendly url in sharepoint 2013). but it’s not so simple; microsoft actually introduced two kind of tagging in sharepoint 2010: tags as properties of documents (actual tags thereafter) where the property values are picked from a list of possible values (part of the termstore with managed metadata typed column or whole termstore with enterprise keyword site column ). users can be allowed to submit values (folksonomy basis). the tag becomes a property of the document and actually describes it. the tag value is cached in the site collection itself in an hidden library (always at http:// yoursite /lists/taxonomyhiddenlist ) tags as social actions (social tags), users can also in some places (at least enabled document libraries, pages) social tags items. the tags values are picked from the termstore, however in this case the tags is not actually associated with the documents, it’s actually a property of the user. this action is not written down in the site collection content database at all but only lay in the user profile social database. there is a major difference between these two types of tagging, one is an actual document property that can be used to classify and find the document, the other one is just a social action. microsoft decided to make social tags clickable, these links points to the tagpage. however to make sure we get confused, the tagpage actually just display the contents that has been “social tagged”. if a document has been classified with an actual tag, it will not appear in the tagpage. this is because the tagpage is actually a page to display the social actions of the users, the fact that it lay in the user profile web application leaves no doubt. the issue is that social tags are not so useful for actual content management whereas actual tags are a must. thus we realized we had no choice but to make these tags clickable and create our own tag page. click me ! click me ! for the sake or maintainability\ease of use\compatibility and future evolutions we decided not to create a custom field type. instead we focused our efforts on finding a way to make the out of the box field types clickable. there are actually only two of these, the singletaxonomyfieldtype and multiptaxofieldtype that are used for both enterprise keywords site columns and managemed metadata columns. we wanted to stick with supported customization so we made use of an extensibility option proposed with sharepoint 2010 (msdn: overview of xslt list view rendering system http://msdn.microsoft.com/en-us/library/ff604024(v=office.14).aspx ) that allow to change the rendering of an existing type, a real improvement from sharepoint 2007 by the way. so to change multiple tags fields to red, create a xsl file named fldtypes_whatyouwant.xsl in \program files\common files\microsoft shared\web server extensions\14\template\layouts\xsl <xsl:stylesheet version="1.0" exclude-result-prefixes="xsl msxsl ddwrt" xmlns:xsl="http://www.w3.org/1999/xsl/transform"> <xsl:template match="fieldref[@fieldtype='taxonomyfieldtypemulti']" priority="1" mode="lookup_body"> <xsl:param name="thisnode" select="."/> <span style="color:red"> <xsl:value-of select="$thisnode/@*[name()=current()/@name]"/> </span> </xsl:template> </xsl:stylesheet> beware of the priority setting above, that’s the key to make sure your customization is applied. you can quick-test that manually by placing the file and iisreset. with a bit more work to get the actual link we need, here is the result before after cherry on the cake, there isn’t anything easier to deploy with a wsp, absolutely no code involved, just a folder mapping in visual studio. note that this works fine for list\libraries views when displaying multiple items, when displaying a single item (view form), we used a small javascript to introduce the link, displaying only a single item means that performance is not an issue in this case. a link, but where to ? it’s great to have a link but links are supposed to point somewhere. as the default tag page only uses social tags it’s useless so we decided to create our own tag page. the easiest solution we found to have both speed and security trimming was the search engine. thus all the heavy-lifting is done by search while we can focus on displaying these results. this is possible because the search engine (tested on fast 4 sharepoint, not enterprise search) has got a dedicated managed property to store tags that is queryable : owsmetadatafacetinfo. this is the one used to render the tags facet on out of the box search pages. so to test it, just run a search for : owsmetadatafacetinfo: atag that’s it plain and simple and now you have the main ingredient to build your own tag page from scratch. conclusion it first seemed like a major challenge at first to make tags as document properties useful (clickable + tag page) in the end it’s actually fairly simple when you know the tricks and the results is definitely worth it. if you wonder about sharepoint 2013, this development has not yet been tested in this configuration, though we know for sure that it will be needed as tags are still not clickable in sharepoint 2013.the good news sp2013 news is that there seems to be an out of the box tag page that actually work since it’s based on search. i will test
Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;
For more information on Whois status codes, please visit https://icann.org/epp
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
REGISTRAR OVH
SERVERS
SERVER com.whois-servers.net
ARGS domain =jonathanroussel.com
PORT 43
TYPE domain RegrInfo DOMAIN
NAME jonathanroussel.com
CHANGED 2016-02-18
CREATED 2007-02-28
STATUS clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Nous utilisons des cookies pour personnaliser votre expérience sur notre site. En poursuivant votre navigation, vous acceptez cette utilisation. Apprendre encore plus
jonathanroussel.com rapport :
Visitez le site