Tako, jutros, moj sin je odlučio vidjeti dobi trinaest ograničen Halo 3 Video na Gamespot. I’m outside shoveling snow, so I’m not there to help or hinder. Necessity is the mother of invention and all that … he has a eureka! moment. He realizes that even though Gamespot wants him to enter his pravi datum rođenja, on zapravo može ući bilo koji birth date he wants. Once he realized that, on je napravio sam dovoljno star da biste vidjeli video.
I’m not quite sure how I feel about this 🙂
Na moj prvi posao izvan koledž u 1991, Bio sam sretan da raditi tvrtka sa proizvodnim 13 mjesta, not including its corporate HQ in New Jersey. I joined just when the company was rolling out a new ERP system. We were a small IT department of about ten people altogether, two of whom Did Not Travel. Part of the project involved replacing IBM System 36 boxes with HP hardware and HPUX. Everyone used green tubes to access the system.
Projekt role zajedno, a ja sam poslan na Baltimore s novim suradnik, Jeff. Our job was to power up the Unix box, provjerite je li O / S je trčanje, instalirali ERP sustava, konfigurirati ERP, train people on the ERP and do custom work for folks on the spot. (To je bio posao iz snova, posebno dolazi ravno iz fakulteta). Before we could really get off the ground, trebamo raspakirati sve zelene cijevi, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.
Za neki razlog da ja nikada ne razumiju i zapravo nikada nije mislio pitati na vrijeme, smo je neki ugovorna tvrtka doći zajedno i pokrenuti kabel u cijeloj biljci, but we didn’t have them put on the connectors. Tako, došlo je do "patch box" s desecima od unlabeled kabela u "učionici" i to snaked oko zgrade na raznim mjestima u zgradi.
Radili smo naš put kroz nju tijekom vikenda, testiranje svake žice, stavljanjem na priključak (pazeći da je ravno vs. prešao), osiguranje su bitne postavke na zelenim cijevi i pisači su točni, labeling wires, pazeći da "Getty" was running correctly for each port and probably a thousand other things that I’ve suppressed since then. It all came together quite nicely.
Ali, there was one important cable that we couldn’t figure out. The plant in Baltimore had a relationship with a warehousing location in New Jersey. Some orders placed in Baltimore shipped out of that location. There were two wires that we had to connect to the HPUX box: a green tube and a printer. The green tube was easy, ali pisač pretvorio u noćnu moru tri tjedna.
Ako ne znate, ili su ga potisnut, koje se bave sa zelenim cijevima i pisača na taj način, there are various options that you deal with by setting various pins. 8-bit, 7-bit, paritet (ni / ak / ništa), probably others. If you get one of those settings wrong, cijev ili pisač i dalje pokazuje stvari, ali to će biti ukupno trtljanje, or it will be gibberish with a lot of recognizable stuff in between. Naravno, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.
Postavili smo prvi od mnogih brzih poziva s NJ Gvido (prosijed računalo mrzitelj koji su vjerojatno nam psuje na ovaj dan). We got the green tube working pretty quickly, but we couldn’t get the printer to work. It kept "printing garbage". We would create a new RJ11 connector, switching between crossed and straight. We would delete the port and re-created in Unix. We went through the arduous task of having him explain to us the pin configuration on the printer, nikada stvarno siguran ako je to radi ispravno.
To je oko vremena za ići uživo, sve u Baltimoreu se zuji, ali ne možemo dobiti prokleto pisač u NJ raditi! We’ve exhausted all possibilities except for driving back up to NJ to work on the printer in person. To avoid all that driving, napokon smo ga zamoliti da nam faksom što je sve kad je "smeće", u nadi da možda tamo će biti neki trag u tom smeću koje će nam reći što radimo krivo.
Kad smo dobili faks, we immediately knew what was wrong. Vidjeti, naša metoda ispitivanja da li mi je konfigurirati pisač ispravno je da izda "LP" Naredba ovako:
lp / etc / passwd
U osnovi, we printed out the unix password file. It’s always present and out of the box, always just one page. You standard Unix password file looks something like this:
kovač:*:100:100:8A-74(ured):/home / Smith:/usr / bin / sh :*:200:0::/home / gost:/usr/bin/sh
We had been printing out the password file over and over again for several weeks and it was printing correctly. Međutim, do krajnjeg korisnika, je "tiskanje smeće".
</kraj>
Moj klijent nedavno instalirali čarobni uređaj s Smreka da je očito zamijenio svoj stari Cisco napona mreže opterećenja (NLB). At about the same time, smo instalirali Hitni popravak za rješavanje problema tijeka rada.
Dan ili dva kasnije, uočili smo problem kada smo pristupili zajedničkom davatelja usluga (SSP). We could get to it, but we would be challenged for a user ID and password many times on each page. This didn’t happen with the main portal app, nor central administration. Naturally, nismo znali koja od dvije (Juniper ili hitni popravak) će biti problem, iako sam jako sumnja hitni popravak, figuring nismo ga instalirali u pravu.
It turned out that Juniper had some kind of compression setting. Jedan od robed figure over in the network group turned that setting off. That solved our problem.
This is not the first time that compression has been the root cause of a SharePoint problem for me. IIS compression adversely affected a 3rd party tool from the good people at The Dot Net Factory for IE 6 preglednici (IE 7 preglednici radio bez poteškoća).
Tako, dodati "kompresiju" na opasnosti popisa.
</kraj>
Krediti: http://www.elfwood.com/art/s/h/sherry/death_colour.jpg.html
Počela sam off my "blogging karijere" using Microsoft’s platform and it’s been good to me. It’s easy to post, postoje dobre opcije i dodaci za upravljanje "Space", pristojan web skladištenje i tako dalje.
Međutim, I really just fell into the MS solution with almost no planning. That alone calls for me to evaluate where I am and where I’m going, in terms of a blogging platform. There are also two important limitations that bother me right now vis-à-vis Windows Live Spaces.
Prvi, I can’t get very good statistics. There are stats but the detail is often truncated and not presented in a way that allows for any kind of analysis. There no sorting or export capability. I get many blog ideas based on the kind of information people find (ili posebno uspjeti pronaći) when they search my blog. It’s very hard to use lives spaces for that.
Drugi, there does not seem to be any mechanism to "monetize" a windows live space blog. Zapravo, kako da biste dobili osloboditi od MS oglasa (iz koje sam izvući nikakvu korist), I need to actually pay Microsoft. (Barem, to je kako ja to razumijem; Ja sam bio u mogućnosti da biste dobili konačne odgovore na ova i pitanja sviđa).
Sada sam dobio stalnu obrazac i skup blogging navike, I want to evaluate other options. I’ve done some research and there are a lot of choices, ali ja sam znatiželjan kao što drugi ljudi, osobito drugi u SharePoint zajednice (kao blogera ili čitatelja), like to use.
Ako vas zanima ovaj predmet i imate mišljenje ili su spremni podijeliti svoje iskustvo, molimo vas da ostavite komentar ili pošaljite email me izravno.
Hvala!
<kraj />
Forum korisnici povremeno pitati: Zašto SharePoint Designer staviti ???? u moj e-mail, umjesto polja vrijednosti?
Jedan od razloga se to dogodi, jer je varijabla u koju se odnose null.
To se može dogoditi, jer se pokušava referencirati polje iz "tekuće stavke" ali korisnik nije ušao u tu vrijednost polja obrasca.
<kraj />
Scenario: U tijeku rada SharePoint Designer, you need to determine if a date field is blank.
Problem: SPD does not provide a direct method for comparing dates to anything other than a date. You cannot create a condition like this: "Ako [DateField] jednako prazna ".
Otopina: Convert the date to a string. Use string comparison to determine if the date is blank.
Screen Shots:
The following screen shots show how to do this. U ovom scenariju, a field on an item, "Environmental Permits:First Permit Reminder Date", is submitted and the workflow fires in response.
Bilješke:
When I tried this, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (Varijabla:StringReminderDateDate) but it did allow it.
I was also concerned that allowing it, the value might be null and either blow up the WF at runtime or maybe raise the global temperature 1/2 a degree, but those concerns were unfounded.
</kraj>
Danas, I was working with a client and describing how to modify the content query web part and display additional bits of information from a content type.
"Prvo, možete konfigurirati CQWP da se povežu sa svojim izvorima podataka, onda izvesti da se vaše radne stanice, izmijeniti <CommonViewFields>, upload, remove the original and now it’s ‘primed’ to display those other columns. Sljedeći, open up SharePoint designer, navigate to the site collection root and locate ItemStyle.xsl. Copy one of the templates as a useful starting point. Go back and modify the CQWP to make use of this new template. Konačno, modify the template to render your new fields! (Don’t forget to check it back in so that other users can see the results)."
It’s all quite clear to me (and most of us SharePoint developer types) what’s going on and how it’s quite nice, stvarno, that the data retrieval aspects of the CQWP are so well-separate from the data presentation aspects. Ali, it’s not so easy to explain, is it?
<kraj />
Out of the box, MOSS’ Upit Sadržaj web-dio (CQWP) prikazuje svoje rezultate u obliku popisa, similar to search results. It is also possible to display the results in a grid format (i.e. HTML obliku tablice). Grid formats are better in some circumstances. I describe how to achieve that effect in this article.
I have worked with a client on an enterprise-wide MOSS rollout. We have designed their taxonomy such that projects are first class citizens in the hierarchy and have their own top level site. Project managers maintain a singleton list of project summary information, poput naslova, budžet, Očekuje se datum završetka, remaining budget and other summary type fields. By "singleton" I mean a custom SharePoint list guaranteed to contain only one item. Simplistically, to izgleda ovako:
Tehnički pristup je isti kao što je opisano ovdje (http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!447.entry). The CQWP uses an XSL transform to emit HTML for the browser to render.
I always envision the result before diving into the XSL because XSL is a nightmare. Here’s my desired result:
HTML kao što to stvara taj rezultat:
<html> <tijelo> <centar> <stol granica= 1> <!-- Etikete -> <tr bgcolor= Blue> <td><su boja= Bijeli><b>Naziv projekta</b></su></td> <td svrstati= Desno><su boja= Bijeli><b>Cijela Datum</b></su></td> <td svrstati= Desno><su boja= Bijeli><b>Budžet</b></su></td> <td svrstati= Desno><su boja= Bijeli><b>Stvarni rashodi</b></su></td> <td><su boja= Bijeli><b>Cjelokupna Status</b></su></td> </tr> <tr> <td>Re-wire računalo soba.</td> <td svrstati= Desno>02/01/08</td> <td svrstati= Desno>22,500.00</td> <td svrstati= Desno>19,000.00</td> <td>U tijeku</td> </tr> <tr> <td>Pružanje poslužitelji za SQL Upgrade</td> <td svrstati= Desno>04/01/08</td> <td svrstati= Desno>7,500.00</td> <td svrstati= Desno>0.00</td> <td>Planiran</td> </tr> </stol> </centar> </tijelo> </html> |
Slijedite ove korake kako bi stvorili mrežu:
I’m going to concentrate on number six. Numbers one through four are straight-forward and something that any CQWP user has already done. Number five has been well-documented by others including this exhaustive screen-shot laden article from MSDN ovdje (http://msdn2.microsoft.com/en-us/library/bb897399.aspx) Heather i Salomon blog ovdje (http://www.heathersolomon.com/blog/articles/CustomItemStyle.aspx).
Počnite i provesti korake od jedan do pet po MSDN dokumentacije i Heather Solomona članak.
U ovom trenutku, ste dodali svoj CQWP na stranici i imate <CommonViewFields> konfigurirati prema potrebi.
Nakon uobičajene korake, Ja se ove prijelazne rezultate:
1. Stvaranje vrste sadržaja, a templatized custom list for that content type and two sites. Here is the content type:
Ovdje je site struktura:
2. Dodajte CQWP nakon stvaranja podmjesta moj projekt i Singleton sažetak projekta popise:
3. Dodajte sve dodatne informacije putem želim <CommonViewFields>:
<svojstvo ime="CommonViewFields" tip="niz">Project_x0020_Name;Project_x0020_Expenses;Project_x0020_Status;Project_x0020_Start_x0020_Date;Project_x0020_End_x0020_Date;Project_x0020_Budget</svojstvo>
Imajte na umu da sam morao zadržati sve imovinsko polja u jednom retku ili neće raditi (CQWP će mi reći da je upit vratio artikala).
4. U ovom trenutku, we’re ready to move beyond the MSDN article and flip on over to Heather Solomon’s article. Follow her steps starting near step #5 stvoriti prilagođeno / unghosted version of ItemStyle.xsl. I follow Heather’s advice, se kroz korak 11 i dobiti ove prijelazne rezultate:
4.1: Ime mi je XSL predložak kako slijedi:
<XSL:template name="Grid" match="Row[@Style=’Grid’]" mode="itemstyle">
Također sam nešto mijenjati joj predložili <XSL:za-svakog …> dodavanjem <br /> označiti osigurati čišći oglas:
<XSL:za-svakog odabrati="@ *"> P:<XSL:vrijednost od odabrati="ime()" /><br/> </XSL:za-svakog>
4.2: Ja izmijeniti dio web, go to appearance and select my "Grid" stil:
Primijenite promjenu, a ovdje je rezultat:
Možemo vidjeti iz gore da polja želimo (Ime projekta, rashod, status, itd.) are available for us to use when we emit the HTML. Not only that, but we see the names by which we must reference those columns in the XSL. Na primjer, we reference Project Status as "Project_x005F_x0020_Name".
U ovom trenutku, krećemo iz Heather blog i na ramenima tih divova, Dodam svoje malo.
NAPOMENA: Prilikom promjene na obje ContentQueryMain.xsl kao ItemStyle.xsl, trebate provjeriti te datoteke vratiti prije nego što vidjeti učinak vaših promjena.
Za grid odluka svrhe, MOSS uses two different XSL files to produce the results we see from a CQWP. To generate the previous bit of output, we modified ItemStyle.xsl. MOSS actually uses another XSL file, ContentQueryMain.xsl to in conjunction with ItemStyle.xsl to generate its HTML. As its name implies, ContentQueryMain.xsl is the "main" XSL that controls the overall flow of translation. It iterates through all the found items and passes them one by one to templates in ItemStyle.xsl. We’ll modify ItemStyle.xsl to generate the open <stol> tag prije emitiranjem prvi redak podataka i zatvaranja <stol> tag after emitting the last row. To accomplish this, ContentQueryMain.xsl is modified to pass two parameters to our "grid" Predložak u ItemStyle.xsl, "last row" and "current row". ItemStyle.xsl uses these to conditionally emit the necessary tags.
Koristeći tehniku Heather Salamonovo, we locate ContentQueryMain.xsl. It is located in the same place as ItemStyle.xsl. This screen shot should help:
Moramo napraviti sljedeće promjene:
Locate the template named "OuterTemplate.CallItemTemplate" prepoznaje se po nizu:
<XSL:predložak ime="OuterTemplate.CallItemTemplate">
Vratite cijeli predloška kako slijedi:
<XSL:predložak ime="OuterTemplate.CallItemTemplate"> <XSL:zaustaviti ime="CurPosition" /> <!-- Add the "LastRow" parametar. We only use it when the item style pass in is "Grid". --> <XSL:zaustaviti ime="LastRow" /> <XSL:izabrati> <XSL:kada test="@ Style = 'NewsRollUpItem'"> <XSL:primjenjuju-predloške odabrati="." način="itemstyle"> <XSL:s param- ime="Modus" odabrati="$cbq_iseditmode" /> </XSL:primjenjuju-predloške> </XSL:kada> <XSL:kada test="@ Style = 'NewsBigItem'"> <XSL:primjenjuju-predloške odabrati="." način="itemstyle"> <XSL:s param- ime="CurPos" odabrati="$CurPosition" /> </XSL:primjenjuju-predloške> </XSL:kada> <XSL:kada test="@ Style = 'NewsCategoryItem'"> <XSL:primjenjuju-predloške odabrati="." način="itemstyle"> <XSL:s param- ime="CurPos" odabrati="$CurPosition" /> </XSL:primjenjuju-predloške> </XSL:kada> <!-- Pass trenutnu poziciju i lastrow na predlošku Grid itemstyle.xsl. ItemStyle.xsl će koristiti da se emitiraju otvorena i zatvaranje <stol> tags. --> <XSL:kada test="@ Style = "Grid""> <XSL:primjenjuju-predloške odabrati="." način="itemstyle"> <XSL:s param- ime="CurPos" odabrati="$CurPosition" /> <XSL:s param- ime="Zadnji" odabrati="$LastRow" /> </XSL:primjenjuju-predloške> </XSL:kada> <XSL:inače> <XSL:primjenjuju-predloške odabrati="." način="itemstyle"> </XSL:primjenjuju-predloške> </XSL:inače> </XSL:izabrati> </XSL:predložak> |
Komentari opisati svrhu promjene.
Naravno, the "OuterTemplate.CallItemTemplate" is itself called from another template. Locate that template by searching for this text string:
<XSL:predložak ime="OuterTemplate.Body">
Prođite kroz upute u OuterTemplate.Body i ubacite LastRow parametar na sljedeći (prikazano kao komentar u kurzivu):
<XSL:poziv-predložak ime="OuterTemplate.CallItemTemplate"> <XSL:s param- ime="CurPosition" odabrati="$CurPosition" /> <!-- Umetnite LastRow parametar. --> <XSL:s param- ime="LastRow" odabrati="$LastRow"/> </XSL:poziv-predložak>
Nakon svega ovoga, konačno smo postavili stvari ispravno, tako da je naša ItemStyle.xsl može emitirati <stol> oznake na pravom mjestu.
NAPOMENA: Opet, prijava ItemStyle.xsl nakon donošenja bilo kakve promjene, tako da možete vidjeti učinak tih promjena.
Imamo dva zadatka ovdje:
Prvi, pri vrhu ItemStyle.xsl, dodajte ovu liniju:
<!-- Neki mumbo jumbo koja nam omogućuje da se prikazati dopuštenje vlade. valuta. --> <XSL:decimal-format ime="osoblje" cifra="D" /> <XSL:predložak ime="Default" odgovarati="*" način="itemstyle">
Imajte na umu da sam ga dodao je neposredno pred <XSL:template name="Default" …> definicija.
Sljedeći, go back to our Grid template. Replace the entire Grid template with the code below. It is thoroughly commented, , ali nemojte se ustručavati da me e-mail ili ostavite komentare na mom blogu, ako imate pitanja.
<XSL:predložak ime="Rešetka" odgovarati="Red[@ Style = "Grid"]" način="itemstyle"> <!-- ContentMain.xsl prolazi CurPos i Zadnja. Mi koristiti za uvjetno emitiraju otvorena i zatvaranje <stol> tags. --> <XSL:zaustaviti ime="CurPos" /> <XSL:zaustaviti ime="Zadnji" /> <!-- Sljedeće varijable su neizmijenjeni od standardnog ItemStyle.xsl --> <XSL:varijabla ime="SafeImageUrl"> <XSL:poziv-predložak ime="OuterTemplate.GetSafeStaticUrl"> <XSL:s param- ime="UrlColumnName" odabrati="'ImageUrl'"/> </XSL:poziv-predložak> </XSL:varijabla> <XSL:varijabla ime="SafeLinkUrl"> <XSL:poziv-predložak ime="OuterTemplate.GetSafeLink"> <XSL:s param- ime="UrlColumnName" odabrati="'LinkUrl'"/> </XSL:poziv-predložak> </XSL:varijabla> <XSL:varijabla ime="DisplayTitle"> <XSL:poziv-predložak ime="OuterTemplate.GetTitle"> <XSL:s param- ime="Naslov" odabrati="@ Naslov"/> <XSL:s param- ime="UrlColumnName" odabrati="'LinkUrl'"/> </XSL:poziv-predložak> </XSL:varijabla> <XSL:varijabla ime="LinkTarget"> <XSL:ako test="@ OpenInNewWindow = 'True'" >_blank</XSL:ako> </XSL:varijabla> <!-- Ovdje smo definirali varijablu, "tableStart". Sadrži HTML . Imajte na umu da ako CurPos = 1, to uključuje i HTML u cdata oznaku. Inače, to će biti prazna. Vrijednost tableStart je emited svaki put ItemStyle se zove putem . --> <XSL:varijabla ime="tableStart"> <XSL:ako test="$CurPos = 1"> <![CDATA[ <Tablica border = 1> <tr bgcolor="blue"> <td><font color="white"><b>Naziv projekta</b></su></td> <td align="right"><font color="white"><b>Cijela Datum</b></su></td> <td align="right"><font color="white"><b>Budžet</b></su></td> <td align="right"><font color="white"><b>Stvarni rashodi</b></su></td> <td><font color="white"><b>Cjelokupna Status</b></su></td> </tr> ]]> </XSL:ako> </XSL:varijabla> <!-- Druga varijabla, tableEnd jednostavno definira oznaku zatvaranja stol. Kao i kod tableStart, uvijek je emited. To je razlog zašto je njegova vrijednost . --> <XSL:varijabla ime="tableEnd"> <XSL:ako test="$CURPOS = $ Zadnji"> <![CDATA[ </stol> ]]> </XSL:ako> </XSL:varijabla> <!-- Uvijek emitiraju sadržaj tableStart. Ako to nije prvi , onda znamo svoju vrijednost . Bez izlaz bježi jer kad tableStart nije prazan, to . Ako , it will generate stuff like "&Bilo;stol>" instead of "<stol>". --> <XSL:vrijednost od odabrati="$tableStart" disable-output-bijegu="da"/> <tr> <!-- P:Project_x005F_x0020_Name :Project_x005F_x0020_End_x005F_x0020_Date :Project_x005F_x0020_Budget :Project_x005F_x0020_Expenses :Project_x005F_x0020_Status --> <td> <XSL:vrijednost od odabrati="@ Project_x005F_x0020_Name"/> </td> <td svrstati="pravo"> <XSL:vrijednost od odabrati="@ Project_x005F_x0020_End_x005F_x0020_Date"/> </td> <td svrstati="pravo"> <XSL:poziv-predložak ime="formatCurrency"> <XSL:s param- ime="vrijednost" |
UPDATE (04/2008): Ovaj veliki blog entry pokazuje dobru javascript pristup temeljen na taj problem: http://webborg.blogspot.com/2008/04/add-functions-and-events-to-sharepoint.html
UPDATE II: (04/2008): Ovaj blog ulaz izgleda obećavajuće kao i: http://www.cleverworkarounds.com/2008/03/13/free-mosswss-2007-web-part-hide-controls-via-javascript/
Nekoliko puta tjedno, ako ne i svakodnevno, forum users describe a requirement that would normally be met via cascading drop-downs. Na primjer, Imam dvije kap-dolje kontrole:
Kao odgovorne UI usluga, želimo da djeluju poput ove:
There is no out-of-the-box support for this feature. Zapravo, there is no OOB support for any kind of direct intra-form communication. This includes programmatically hiding/enabling/disabling fields in response to field changes elsewhere on the form.
Pravi cilj ovog članka je opisati moguća rješenja, a to su opcije kao što sam ih znali:
Ako netko zna druge i / ili bolja opcija, molimo Vas da objavite komentar, a ja ću ažurirati tijelo ovog posta.
<kraj />
Za filtriranje za upit za da / ne potvrdni okvir pod nazivom "Milestone PG", konfigurirati CQWP ovako:
To je jedan od onih očito-jednom-you-know-it, ali teško pronaći--odgovor-na pitanja: Kako filtrirati na Da / Ne potvrdni okvir pomoću web-dijela za pretraživanje sadržaja.
The first search result I find using the search term "filter yes/no content query web part" is flat out wrong, so I thought I’d put this up there and see if it can replace the incorrect result in typical search results.
It’s quite easy: True values = "1" and false values do not equal "1" (pretty retro, actually).
In the above example, I created site column of type "Yes/No (checkbox)" named "PG Milestone". I added it to a doc library, uploaded a few documents, set the value for a couple and tested it.
<kraj />
