give me chicken - Page 684

Read the article

Security Issues with Single Page Apps

- by Stephen.Walther

Read the article

iPhone SDK vs. Windows Phone 7 Series SDK Challenge, Part 2: MoveMe

In this series, I will be taking sample applications from the iPhone SDK and implementing them on Windows Phone 7 Series. My goal is to do as much of an apples-to-apples comparison as I can. This series will be written to not only compare and contrast how easy or difficult it is to complete tasks on either platform, how many lines of code, etc., but Id also like it to be a way for iPhone developers to either get started on Windows Phone 7 Series development, or for developers in general to learn the platform. Heres my methodology: Run the iPhone SDK app in the iPhone Simulator to get a feel for what it does and how it works, without looking at the implementation Implement the equivalent functionality on Windows Phone 7 Series using Silverlight. Compare the two implementations based on complexity, functionality, lines of code, number of files, etc. Add some functionality to the Windows Phone 7 Series app that shows off a way to make the scenario more interesting or leverages an aspect of the platform, or uses a better design pattern to implement the functionality. You can download Microsoft Visual Studio 2010 Express for Windows Phone CTP here, and the Expression Blend 4 Beta here. If youre seeing this series for the first time, check out Part 1: Hello World. A note on methodologyin the prior post there was some feedback about lines of code not being a very good metric for this exercise. I dont really disagree, theres a lot more to this than lines of code but I believe that is a relevant metric, even if its not the ultimate one. And theres no perfect answer here. So I am going to continue to report the number of lines of code that I, as a developer would need to write in these apps as a data point, and Ill leave it up to the reader to determine how that fits in with overall complexity, etc. The first example was so basic that I think it was difficult to talk about in real terms. I think that as these apps get more complex, the subjective differences in concept count and will be more important. MoveMe The MoveMe app is the main end-to-end app writing example in the iPhone SDK, called Creating an iPhone Application. This application demonstrates a few concepts, including handling touch input, how to do animations, and how to do some basic transforms. The behavior of the application is pretty simple. User touches the button: The button does a throb type animation where it scales up and then back down briefly. User drags the button: After a touch begins, moving the touch point will drag the button around with the touch. User lets go of the button: The button animates back to its original position, but does a few small bounces as it reaches its original point, which makes the app fun and gives it an extra bit of interactivity. Now, how would I write an app that meets this spec for Windows Phone 7 Series, and how hard would it be? Lets find out! Implementing the UI Okay, lets build the UI for this application. In the HelloWorld example, we did all the UI design in Visual Studio and/or by hand in XAML. In this example, were going to use the Expression Blend 4 Beta. You might be wondering when to use Visual Studio, when to use Blend, and when to do XAML by hand. Different people will have different takes on this, but heres mine: XAML by hand simple UI that doesnt contain animations, gradients, etc., and or UI that I want to really optimize and craft when I know exactly what I want to do. Visual Studio Basic UI layout, property setting, data binding, etc. Blend Any serious design work needs to be done in Blend, including animations, handling states and transitions, styling and templating, editing resources. As in Part 1, go ahead and fire up Visual Studio 2010 Express for Windows Phone (yes, soon it will take longer to say the name of our products than to start them up!), and create a new Windows Phone Application. As in Part 1, clear out the XAML from the designer. An easy way to do this is to just: Click on the design surface Hit Control+A Hit Delete Theres a little bit left over (the Grid.RowDefinitions element), just go ahead and delete that element so were starting with a clean state of only one outer Grid element. To use Blend, we need to save this project. See, when you create a project with Visual Studio Express, it doesnt commit it to the disk (well, in a place where you can find it, at least) until you actually save the project. This is handy if youre doing some fooling around, because it doesnt clutter your disk with WindowsPhoneApplication23-like directories. But its also kind of dangerous, since when you close VS, if you dont save the projectits all gone. Yes, this has bitten me since I was saving files and didnt remember that, so be careful to save the project/solution via Save All, at least once. So, save and note the location on disk. Start Expression Blend 4 Beta, and chose File > Open Project/Solution, and load your project. You should see just about the same thing you saw over in VS: a blank, black designer surface. Now, thinking about this application, we dont really need a button, even though it looks like one. We never click it. So were just going to create a visual and use that. This is also true in the iPhone example above, where the visual is actually not a button either but a jpg image with a nice gradient and round edges. Well do something simple here that looks pretty good. In Blend, look in the tool pane on the left for the icon that looks like the below (the highlighted one on the left), and hold it down to get the popout menu, and choose Border: Okay, now draw out a box in the middle of the design surface of about 300x100. The Properties Pane to the left should show the properties for this item. First, lets make it more visible by giving it a border brush. Set the BorderBrush to white by clicking BorderBrush and dragging the color selector all the way to the upper right in the palette. Then, down a bit farther, make the BorderThickness 4 all the way around, and the CornerRadius set to 6. In the Layout section, do the following to Width, Height, Horizontal and Vertical Alignment, and Margin (all 4 margin values): Youll see the outline now is in the middle of the design surface. Now lets give it a background color. Above BorderBrush select Background, and click the third tab over: Gradient Brush. Youll see a gradient slider at the bottom, and if you click the markers, you can edit the gradient stops individually (or add more). In this case, you can select something you like, but wheres what I chose: Left stop: #BFACCFE2 (I just picked a spot on the palette and set opacity to 75%, no magic here, feel free to fiddle these or just enter these numbers into the hex area and be done with it) Right stop: #FF3E738F Okay, looks pretty good. Finally set the name of the element in the Name field at the top of the Properties pane to welcome. Now lets add some text. Just hit T and itll select the TextBlock tool automatically: Now draw out some are inside our welcome visual and type Welcome!, then click on the design surface (to exit text entry mode) and hit V to go back into selection mode (or the top item in the tool pane that looks like a mouse pointer). Click on the text again to select it in the tool pane. Just like the border, we want to center this. So set HorizontalAlignment and VerticalAlignment to Center, and clear the Margins: Thats it for the UI. Heres how it looks, on the design surface: Not bad! Okay, now the fun part Adding Animations Using Blend to build animations is a lot of fun, and its easy. In XAML, I can not only declare elements and visuals, but also I can declare animations that will affect those visuals. These are called Storyboards. To recap, well be doing two animations: The throb animation when the element is touched The center animation when the element is released after being dragged. The throb animation is just a scale transform, so well do that first. In the Objects and Timeline Pane (left side, bottom half), click the little + icon to add a new Storyboard called touchStoryboard: The timeline view will appear. In there, click a bit to the right of 0 to create a keyframe at .2 seconds: Now, click on our welcome element (the Border, not the TextBlock in it), and scroll to the bottom of the Properties Pane. Open up Transform, click the third tab ("Scale), and set X and Y to 1.2: This all of this says that, at .2 seconds, I want the X and Y size of this element to scale to 1.2. In fact you can see this happen. Push the Play arrow in the timeline view, and youll see the animation run! Lets make two tweaks. First, we want the animation to automatically reverse so it scales up then back down nicely. Click in the dropdown that says touchStoryboard in Objects and Timeline, then in the Properties pane check Auto Reverse: Now run it again, and youll see it go both ways. Lets even make it nicer by adding an easing function. First, click on the Render Transform item in the Objects tree, then, in the Property Pane, youll see a bunch of easing functions to choose from. Feel free to play with this, then seeing how each runs. I chose Circle In, but some other ones are fun. Try them out! Elastic In is kind of fun, but well stick with Circle In. Thats it for that animation. Now, we also want an animation to move the Border back to its original position when the user ends the touch gesture. This is exactly the same process as above, but just targeting a different transform property. Create a new animation called releaseStoryboard Select a timeline point at 1.2 seconds. Click on the welcome Border element again Scroll to the Transforms panel at the bottom of the Properties Pane Choose the first tab (Translate), which may already be selected Set both X and Y values to 0.0 (we do this just to make the values stick, because the value is already 0 and we need Blend to know we want to save that value) Click on RenderTransform in the Objects tree In the properties pane, choose Bounce Out Set Bounces to 6, and Bounciness to 4 (feel free to play with these as well) Okay, were done. Note, if you want to test this Storyboard, you have to do something a little tricky because the final value is the same as the initial value, so playing it does nothing. If you want to play with it, do the following: Next to the selection dropdown, hit the little "x (Close Storyboard) Go to the Translate Transform value for welcome Set X,Y to 50, 200, respectively (or whatever) Select releaseStoryboard again from the dropdown Hit play, see it run Go into the object tree and select RenderTransform to change the easing function. When youre done, hit the Close Storyboard x again and set the values in Transform/Translate back to 0 Wiring Up the Animations Okay, now go back to Visual Studio. Youll get a prompt due to the modification of MainPage.xaml. Hit Yes. In the designer, click on the welcome Border element. In the Property Browser, hit the Events button, then double click each of ManipulationStarted, ManipulationDelta, ManipulationCompleted. Youll need to flip back to the designer from code, after each double click. Its code time. Here we go. Here, three event handlers have been created for us: welcome_ManipulationStarted: This will execute when a manipulation begins. Think of it as MouseDown. welcome_ManipulationDelta: This executes each time a manipulation changes. Think MouseMove. welcome_ManipulationCompleted: This will execute when the manipulation ends. Think MouseUp. Now, in ManipuliationStarted, we want to kick off the throb animation that we called touchAnimation. Thats easy: 1: private void welcome_ManipulationStarted(object sender, ManipulationStartedEventArgs e) 2: { 3: touchStoryboard.Begin(); 4: } .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Likewise, when the manipulation completes, we want to re-center the welcome visual with our bounce animation: 1: private void welcome_ManipulationCompleted(object sender, ManipulationCompletedEventArgs e) 2: { 3: releaseStoryboard.Begin(); 4: } .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Note there is actually a way to kick off these animations from Blend directly via something called Triggers, but I think its clearer to show whats going on like this. A Trigger basically allows you to say When this event fires, trigger this Storyboard, so its the exact same logical process as above, but without the code. But how do we get the object to move? Well, for that we really dont want an animation because we want it to respond immediately to user input. We do this by directly modifying the transform to match the offset for the manipulation, and then well let the animation bring it back to zero when the manipulation completes. The manipulation events do a great job of keeping track of all the stuff that you usually had to do yourself when doing drags: where you started from, how far youve moved, etc. So we can easily modify the position as below: 1: private void welcome_ManipulationDelta(object sender, ManipulationDeltaEventArgs e) 2: { 3: CompositeTransform transform = (CompositeTransform)welcome.RenderTransform; 4: 5: transform.TranslateX = e.CumulativeManipulation.Translation.X; 6: transform.TranslateY = e.CumulativeManipulation.Translation.Y; 7: } .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Thats it! Go ahead and run the app in the emulator. I suggest running without the debugger, its a little faster (CTRL+F5). If youve got a machine that supports DirectX 10, youll see nice smooth GPU accelerated graphics, which also what it looks like on the phone, running at about 60 frames per second. If your machine does not support DX10 (like the laptop Im writing this on!), it wont be quite a smooth so youll have to take my word for it! Comparing Against the iPhone This is an example where the flexibility and power of XAML meets the tooling of Visual Studio and Blend, and the whole experience really shines. So, for several things that are declarative and 100% toolable with the Windows Phone 7 Series, this example does them with code on the iPhone. In parens is the lines of code that I count to do these operations. PlacardView.m: 19 total LOC Creating the view that hosts the button-like image and the text Drawing the image that is the background of the button Drawing the Welcome text over the image (I think you could technically do this step and/or the prior one using Interface Builder) MoveMeView.m: 63 total LOC Constructing and running the scale (throb) animation (25) Constructing the path describing the animation back to center plus bounce effect (38) Beyond the code count, yy experience with doing this kind of thing in code is that its VERY time intensive. When I was a developer back on Windows Forms, doing GDI+ drawing, we did this stuff a lot, and it took forever! You write some code and even once you get it basically working, you see its not quite right, you go back, tweak the interval, or the math a bit, run it again, etc. You can take a look at the iPhone code here to judge for yourself. Scroll down to animatePlacardViewToCenter toward the bottom. I dont think this code is terribly complicated, but its not what Id call simple and its not at all simple to get right. And then theres a few other lines of code running around for setting up the ViewController and the Views, about 15 lines between MoveMeAppDelegate, PlacardView, and MoveMeView, plus the assorted decls in the h files. Adding those up, I conservatively get something like 100 lines of code (19+63+15+decls) on iPhone that I have to write, by hand, to make this project work. The lines of code that I wrote in the examples above is 5 lines of code on Windows Phone 7 Series. In terms of incremental concept counts beyond the HelloWorld app, heres a shot at that: iPhone: Drawing Images Drawing Text Handling touch events Creating animations Scaling animations Building a path and animating along that Windows Phone 7 Series: Laying out UI in Blend Creating & testing basic animations in Blend Handling touch events Invoking animations from code This was actually the first example I tried converting, even before I did the HelloWorld, and I was pretty surprised. Some of this is luck that this app happens to match up with the Windows Phone 7 Series platform just perfectly. In terms of time, I wrote the above application, from scratch, in about 10 minutes. I dont know how long it would take a very skilled iPhone developer to write MoveMe on that iPhone from scratch, but if I was to write it on Silverlight in the same way (e.g. all via code), I think it would likely take me at least an hour or two to get it all working right, maybe more if I ended up picking the wrong strategy or couldnt get the math right, etc. Making Some Tweaks Silverlight contains a feature called Projections to do a variety of 3D-like effects with a 2D surface. So lets play with that a bit. Go back to Blend and select the welcome Border in the object tree. In its properties, scroll down to the bottom, open Transform, and see Projection at the bottom. Set X,Y,Z to 90. Youll see the element kind of disappear, replaced by a thin blue line. Now Create a new animation called startupStoryboard. Set its key time to .5 seconds in the timeline view Set the projection values above to 0 for X, Y, and Z. Save Go back to Visual Studio, and in the constructor, add the following bold code (lines 7-9 to the constructor: 1: public MainPage() 2: { 3: InitializeComponent(); 4: 5: SupportedOrientations = SupportedPageOrientation.Portrait; 6: 7: this.Loaded += (s, e) => 8: { 9: startupStoryboard.Begin(); 10: }; 11: } .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } If the code above looks funny, its using something called a lambda in C#, which is an inline anonymous method. Its just a handy shorthand for creating a handler like the manipulation ones above. So with this youll get a nice 3D looking fly in effect when the app starts up. Here it is, in flight: Pretty cool!Did you know that DotNetSlackers also publishes .net articles written by top known .net Authors? We already have over 80 articles in several categories including Silverlight. Take a look: here.

Read the article

How to create Custom ListForm WebPart

- by DipeshBhanani

Mostly all who works extensively on SharePoint (including meJ) don’t like to use out-of-box list forms (DispForm.aspx, EditForm.aspx, NewForm.aspx) as interface. Actually these OOB list forms bind hands of developers for the customization. It gives headache to developers to add just one post back event, for a dropdown field and to populate other fields in NewForm.aspx or EditForm.aspx. On top of that clients always ask such stuff. So here I am going to give you guys a flight for SharePoint Customization world. In this blog, I will explain, how to create CustomListForm WebPart. In my next blogs, I am going to explain easy deployment of List Forms through features and last, guidance on using SharePoint web controls. 1. First thing, create a class library project through Visual Studio and inherit the class with WebPart class. public class CustomListForm : WebPart 2. Declare the public variables and properties which we are going to use throughout the class. You will get to know these once you see them in use. #region "Variable Declaration" Table spTableCntl; FormToolBar formToolBar; Literal ltAlertMessage; Guid SiteId; Guid ListId; int ItemId; string ListName; #endregion #region "Properties" SPControlMode _ControlMode = SPControlMode.New; [Personalizable(PersonalizationScope.Shared), WebBrowsable(true), WebDisplayName("Control Mode"), WebDescription("Set Control Mode"), DefaultValue(""), Category("Miscellaneous")] public SPControlMode ControlMode { get { return _ControlMode; } set { _ControlMode = value; } } #endregion The property “ControlMode” is used to identify the mode of the List Form. The property is of type SPControlMode which is an enum type with values (Display, Edit, New and Invalid). When we will add this WebPart to DispForm.aspx, EditForm.aspx and NewForm.aspx, we will set the WebPart property “ControlMode” to Display, Edit and New respectively. 3. Now, we need to override the CreateChildControl method and write code to manually add SharePoint Web Controls related to each list fields as well as ToolBar controls. protected override void CreateChildControls() { base.CreateChildControls(); try { SiteId = SPContext.Current.Site.ID; ListId = SPContext.Current.ListId; ListName = SPContext.Current.List.Title; if (_ControlMode == SPControlMode.Display || _ControlMode == SPControlMode.Edit) ItemId = SPContext.Current.ItemId; SPSecurity.RunWithElevatedPrivileges(delegate() { using (SPSite site = new SPSite(SiteId)) { //creating a new SPSite with credentials of System Account using (SPWeb web = site.OpenWeb()) { //<Custom Code for creating form controls> } } }); } catch (Exception ex) { ShowError(ex, "CreateChildControls"); } } Here we are assuming that we are developing this WebPart to plug into List Forms. Hence we will get the List Id and List Name from the current context. We can have Item Id only in case of Display and Edit Mode. We are putting our code into “RunWithElevatedPrivileges” to elevate privileges to System Account. Now, let’s get deep down into the main code and expand “//<Custom Code for creating form controls>”. Before initiating any SharePoint control, we need to set context of SharePoint web controls explicitly so that it will be instantiated with elevated System Account user. Following line does the job. //To create SharePoint controls with new web object and System Account credentials SPControl.SetContextWeb(Context, web); First thing, let’s add main table as container for all controls. //Table to render webpart Table spTableMain = new Table(); spTableMain.CellPadding = 0; spTableMain.CellSpacing = 0; spTableMain.Width = new Unit(100, UnitType.Percentage); this.Controls.Add(spTableMain); Now we need to add Top toolbar with Save and Cancel button at top as you see in the below screen shot. // Add Row and Cell for Top ToolBar TableRow spRowTopToolBar = new TableRow(); spTableMain.Rows.Add(spRowTopToolBar); TableCell spCellTopToolBar = new TableCell(); spRowTopToolBar.Cells.Add(spCellTopToolBar); spCellTopToolBar.Width = new Unit(100, UnitType.Percentage); ToolBar toolBarTop = (ToolBar)Page.LoadControl("/_controltemplates/ToolBar.ascx"); toolBarTop.CssClass = "ms-formtoolbar"; toolBarTop.ID = "toolBarTbltop"; toolBarTop.RightButtons.SeparatorHtml = "<td class=ms-separator> </td>"; if (_ControlMode != SPControlMode.Display) { SaveButton btnSave = new SaveButton(); btnSave.ControlMode = _ControlMode; btnSave.ListId = ListId; if (_ControlMode == SPControlMode.New) btnSave.RenderContext = SPContext.GetContext(web); else { btnSave.RenderContext = SPContext.GetContext(this.Context, ItemId, ListId, web); btnSave.ItemContext = SPContext.GetContext(this.Context, ItemId, ListId, web); btnSave.ItemId = ItemId; } toolBarTop.RightButtons.Controls.Add(btnSave); } GoBackButton goBackButtonTop = new GoBackButton(); toolBarTop.RightButtons.Controls.Add(goBackButtonTop); goBackButtonTop.ControlMode = SPControlMode.Display; spCellTopToolBar.Controls.Add(toolBarTop); Here we have use “SaveButton” and “GoBackButton” which are internal SharePoint web controls for save and cancel functionality. I have set some of the properties of Save Button with if-else condition because we will not have Item Id in case of New Mode. Item Id property is used to identify which SharePoint List Item need to be saved. Now, add Form Toolbar to the page which contains “Attach File”, “Delete Item” etc buttons. // Add Row and Cell for FormToolBar TableRow spRowFormToolBar = new TableRow(); spTableMain.Rows.Add(spRowFormToolBar); TableCell spCellFormToolBar = new TableCell(); spRowFormToolBar.Cells.Add(spCellFormToolBar); spCellFormToolBar.Width = new Unit(100, UnitType.Percentage); FormToolBar formToolBar = new FormToolBar(); formToolBar.ID = "formToolBar"; formToolBar.ListId = ListId; if (_ControlMode == SPControlMode.New) formToolBar.RenderContext = SPContext.GetContext(web); else { formToolBar.RenderContext = SPContext.GetContext(this.Context, ItemId, ListId, web); formToolBar.ItemContext = SPContext.GetContext(this.Context, ItemId, ListId, web); formToolBar.ItemId = ItemId; } formToolBar.ControlMode = _ControlMode; formToolBar.EnableViewState = true; spCellFormToolBar.Controls.Add(formToolBar); The ControlMode property will take care of which button to be displayed on the toolbar. E.g. “Attach files”, “Delete Item” in new/edit forms and “New Item”, “Edit Item”, “Delete Item”, “Manage Permissions” etc in display forms. Now add main section which contains form field controls. //Create Form Field controls and add them in Table "spCellCntl" CreateFieldControls(web); //Add public variable "spCellCntl" containing all form controls to the page spRowCntl.Cells.Add(spCellCntl); spCellCntl.Width = new Unit(100, UnitType.Percentage); spCellCntl.Controls.Add(spTableCntl); //Add a Blank Row with height of 5px to render space between ToolBar table and Control table TableRow spRowLine1 = new TableRow(); spTableMain.Rows.Add(spRowLine1); TableCell spCellLine1 = new TableCell(); spRowLine1.Cells.Add(spCellLine1); spCellLine1.Height = new Unit(5, UnitType.Pixel); spCellLine1.Controls.Add(new LiteralControl("<IMG SRC='/_layouts/images/blank.gif' width=1 height=1 alt=''>")); //Add Row and Cell for Form Controls Section TableRow spRowCntl = new TableRow(); spTableMain.Rows.Add(spRowCntl); TableCell spCellCntl = new TableCell(); //Create Form Field controls and add them in Table "spCellCntl" CreateFieldControls(web); //Add public variable "spCellCntl" containing all form controls to the page spRowCntl.Cells.Add(spCellCntl); spCellCntl.Width = new Unit(100, UnitType.Percentage); spCellCntl.Controls.Add(spTableCntl); TableRow spRowLine2 = new TableRow(); spTableMain.Rows.Add(spRowLine2); TableCell spCellLine2 = new TableCell(); spRowLine2.Cells.Add(spCellLine2); spCellLine2.CssClass = "ms-formline"; spCellLine2.Controls.Add(new LiteralControl("<IMG SRC='/_layouts/images/blank.gif' width=1 height=1 alt=''>")); // Add Blank row with height of 5 pixel TableRow spRowLine3 = new TableRow(); spTableMain.Rows.Add(spRowLine3); TableCell spCellLine3 = new TableCell(); spRowLine3.Cells.Add(spCellLine3); spCellLine3.Height = new Unit(5, UnitType.Pixel); spCellLine3.Controls.Add(new LiteralControl("<IMG SRC='/_layouts/images/blank.gif' width=1 height=1 alt=''>")); You can add bottom toolbar also to get same look and feel as OOB forms. I am not adding here as the blog will be much lengthy. At last, you need to write following lines to allow unsafe updates for Save and Delete button. // Allow unsafe update on web for save button and delete button if (this.Page.IsPostBack && this.Page.Request["__EventTarget"] != null && (this.Page.Request["__EventTarget"].Contains("IOSaveItem") || this.Page.Request["__EventTarget"].Contains("IODeleteItem"))) { SPContext.Current.Web.AllowUnsafeUpdates = true; } So that’s all. We have finished writing Custom Code for adding field control. But something most important is skipped. In above code, I have called function “CreateFieldControls(web);” to add SharePoint field controls to the page. Let’s see the implementation of the function: private void CreateFieldControls(SPWeb pWeb) { SPList listMain = pWeb.Lists[ListId]; SPFieldCollection fields = listMain.Fields; //Main Table to render all fields spTableCntl = new Table(); spTableCntl.BorderWidth = new Unit(0); spTableCntl.CellPadding = 0; spTableCntl.CellSpacing = 0; spTableCntl.Width = new Unit(100, UnitType.Percentage); spTableCntl.CssClass = "ms-formtable"; SPContext controlContext = SPContext.GetContext(this.Context, ItemId, ListId, pWeb); foreach (SPField listField in fields) { string fieldDisplayName = listField.Title; string fieldInternalName = listField.InternalName; //Skip if the field is system field or hidden if (listField.Hidden || listField.ShowInVersionHistory == false) continue; //Skip if the control mode is display and field is read-only if (_ControlMode != SPControlMode.Display && listField.ReadOnlyField == true) continue; FieldLabel fieldLabel = new FieldLabel(); fieldLabel.FieldName = listField.InternalName; fieldLabel.ListId = ListId; BaseFieldControl fieldControl = listField.FieldRenderingControl; fieldControl.ListId = ListId; //Assign unique id using Field Internal Name fieldControl.ID = string.Format("Field_{0}", fieldInternalName); fieldControl.EnableViewState = true; //Assign control mode fieldLabel.ControlMode = _ControlMode; fieldControl.ControlMode = _ControlMode; switch (_ControlMode) { case SPControlMode.New: fieldLabel.RenderContext = SPContext.GetContext(pWeb); fieldControl.RenderContext = SPContext.GetContext(pWeb); break; case SPControlMode.Edit: case SPControlMode.Display: fieldLabel.RenderContext = controlContext; fieldLabel.ItemContext = controlContext; fieldLabel.ItemId = ItemId; fieldControl.RenderContext = controlContext; fieldControl.ItemContext = controlContext; fieldControl.ItemId = ItemId; break; } //Add row to display a field row TableRow spCntlRow = new TableRow(); spTableCntl.Rows.Add(spCntlRow); //Add the cells for containing field lable and control TableCell spCellLabel = new TableCell(); spCellLabel.Width = new Unit(30, UnitType.Percentage); spCellLabel.CssClass = "ms-formlabel"; spCntlRow.Cells.Add(spCellLabel); TableCell spCellControl = new TableCell(); spCellControl.Width = new Unit(70, UnitType.Percentage); spCellControl.CssClass = "ms-formbody"; spCntlRow.Cells.Add(spCellControl); //Add the control to the table cells spCellLabel.Controls.Add(fieldLabel); spCellControl.Controls.Add(fieldControl); //Add description if there is any in case of New and Edit Mode if (_ControlMode != SPControlMode.Display && listField.Description != string.Empty) { FieldDescription fieldDesc = new FieldDescription(); fieldDesc.FieldName = fieldInternalName; fieldDesc.ListId = ListId; spCellControl.Controls.Add(fieldDesc); } //Disable Name(Title) in Edit Mode if (_ControlMode == SPControlMode.Edit && fieldDisplayName == "Name") { TextBox txtTitlefield = (TextBox)fieldControl.Controls[0].FindControl("TextField"); txtTitlefield.Enabled = false; } } fields = null; } First of all, I have declared List object and got list fields in field collection object called “fields”. Then I have added a table for the container of all controls and assign CSS class as "ms-formtable" so that it gives consistent look and feel of SharePoint. Now it’s time to navigate through all fields and add them if required. Here we don’t need to add hidden or system fields. We also don’t want to display read-only fields in new and edit forms. Following lines does this job. //Skip if the field is system field or hidden if (listField.Hidden || listField.ShowInVersionHistory == false) continue; //Skip if the control mode is display and field is read-only if (_ControlMode != SPControlMode.Display && listField.ReadOnlyField == true) continue; Let’s move to the next line of code. FieldLabel fieldLabel = new FieldLabel(); fieldLabel.FieldName = listField.InternalName; fieldLabel.ListId = ListId; BaseFieldControl fieldControl = listField.FieldRenderingControl; fieldControl.ListId = ListId; //Assign unique id using Field Internal Name fieldControl.ID = string.Format("Field_{0}", fieldInternalName); fieldControl.EnableViewState = true; //Assign control mode fieldLabel.ControlMode = _ControlMode; fieldControl.ControlMode = _ControlMode; We have used “FieldLabel” control for displaying field title. The advantage of using Field Label is, SharePoint automatically adds red star besides field label to identify it as mandatory field if there is any. Here is most important part to understand. The “BaseFieldControl”. It will render the respective web controls according to type of the field. For example, if it’s single line of text, then Textbox, if it’s look up then it renders dropdown. Additionally, the “ControlMode” property tells compiler that which mode (display/edit/new) controls need to be rendered with. In display mode, it will render label with field value. In edit mode, it will render respective control with item value and in new mode it will render respective control with empty value. Please note that, it’s not always the case when dropdown field will be rendered for Lookup field or Choice field. You need to understand which controls are rendered for which list fields. I am planning to write a separate blog which I hope to publish it very soon. Moreover, we also need to assign list field specific properties like List Id, Field Name etc to identify which SharePoint List field is attached with the control. switch (_ControlMode) { case SPControlMode.New: fieldLabel.RenderContext = SPContext.GetContext(pWeb); fieldControl.RenderContext = SPContext.GetContext(pWeb); break; case SPControlMode.Edit: case SPControlMode.Display: fieldLabel.RenderContext = controlContext; fieldLabel.ItemContext = controlContext; fieldLabel.ItemId = ItemId; fieldControl.RenderContext = controlContext; fieldControl.ItemContext = controlContext; fieldControl.ItemId = ItemId; break; } Here, I have separate code for new mode and Edit/Display mode because we will not have Item Id to assign in New Mode. We also need to set CSS class for cell containing Label and Controls so that those controls get rendered with SharePoint theme. spCellLabel.CssClass = "ms-formlabel"; spCellControl.CssClass = "ms-formbody"; “FieldDescription” control is used to add field description if there is any. Now it’s time to add some more customization, //Disable Name(Title) in Edit Mode if (_ControlMode == SPControlMode.Edit && fieldDisplayName == "Name") { TextBox txtTitlefield = (TextBox)fieldControl.Controls[0].FindControl("TextField"); txtTitlefield.Enabled = false; } The above code will disable the title field in edit mode. You can add more code here to achieve more customization according to your requirement. Some of the examples are as follow: //Adding post back event on UserField to auto populate some other dependent field //in new mode and disable it in edit mode if (_ControlMode != SPControlMode.Display && fieldDisplayName == "Manager") { if (fieldControl.Controls[0].FindControl("UserField") != null) { PeopleEditor pplEditor = (PeopleEditor)fieldControl.Controls[0].FindControl("UserField"); if (_ControlMode == SPControlMode.New) pplEditor.AutoPostBack = true; else pplEditor.Enabled = false; } } //Add JavaScript Event on Dropdown field. Don't forget to add the JavaScript function on the page. if (_ControlMode == SPControlMode.Edit && fieldDisplayName == "Designation") { DropDownList ddlCategory = (DropDownList)fieldControl.Controls[0]; ddlCategory.Attributes.Add("onchange", string.Format("javascript:DropdownChangeEvent('{0}');return false;", ddlCategory.ClientID)); } Following are the screenshots of my Custom ListForm WebPart. Let’s play a game, check out your OOB List forms of SharePoint, compare with these screens and find out differences. DispForm.aspx: EditForm.aspx: NewForm.aspx: Enjoy the SharePoint Soup!!!

Search Results

Search found 17187 results on 688 pages for 'give me chicken'.

Page 684/688 | < Previous Page | 680 681 682 683 684 685 686 687 688 | Next Page >

- by Bob

- by Kevin

- by Rick Strahl

- by skjagini

- by Rick Strahl

- by Bobby Diaz

- by Rick Strahl

- by Rick Strahl

- by SeanMcAlinden

- by Stephen.Walther

- by 4x10

- by Michael Williamson

- by Stephen.Walther

- by danx

- by Rick Strahl

- by Valter Minute

- by FransBouma

- by Maria Zakourdaev

- by Stephen.Walther

- by rituchhibber

- by user291729

- by user9154181

- by DipeshBhanani

< Previous Page | 680 681 682 683 684 685 686 687 688 | Next Page >