#view controller

Items inside a Collection View can be manipulated by modifying the connected model data. In this tutorial items will be removed from the Collection View Controller. This tutorial is made with Xcode 10 and built for iOS 12.

Project Setup

Open Xcode and create a new Single View App.

For product name, use IOSDeleteItemsCollectionViewTutorial and then fill out the Organization Name and Organization Identifier with your customary values. Enter Swift as Language and choose Next.

Storyboard Setup

Go to the storyboard. Remove the View Controller from the Storyboard and drag a Collection ViewController to the Scene. Select the View Controller and go to the Editor Menu. Select Embed In -> Navigation Controller.

Select the Navigation Controller and go to The Attribute inspector. In the View Controller section check the "Is Initial View Controller" checkbox.

Select the Collection View Cell and go to the Attribute inspector. In the View section change the Background color to Light Gray Color.

Select The Collection View and go the Size inspector. In the Collection View section change the Cell Size to a width and height of 100 points.

Drag a Label from the Object Library and place it on the Center of the Collection View Cell.

Drag another Label to the right-bottom of the cell. This label will be needed for the state of the selection during edit mode, when selected a checkmark will be displayed. Select the label and go to the Attribute inspector. In the Label section delete the label text so the label will contain an empty string.

Select the Collection View Cell and go to the Atrribute inspector. In the Collection Reusable View section set the Identifier to "Cell".

Next, drag a Bar Button Item to the right side of the Navigation Bar. Select the Bar Button Item and go to the Attributes inspector. In the Bar Button Item section change the System Item to Trash. Also in the Bar Item section deselect the Enabled checkbox. The trash button will only be displayed when an item is selected in edit mode.

The storyboard will look like this.

Since the View Controller is removed from the Storyboard the ViewController.swift file can also be deleted from the project. Add a new file to the project, select iOS -> Source -> Cocoa Touch Class. Name it CollectionViewController and make it a subclass of UICollectionViewController.

The CollectionViewController class needs to be linked to The Collection View Controller object in the Storyboard. Select it and go the Identity Inspector. In the Custom Class section change the class to CollectionViewController

Custom Collection View Cell

Select File -> New File -> iOS -> Source -> Cocoa Touch Class. Name the class CollectionViewCell and make it a subclass of UICollectionViewCell.

Go back to Main.storyboard and select the Collection View Cell. Go to the Identity inspector and in the Custom Class section change the class to CollectionViewCell.

Outlet an Action Connections

Select the Assistant Editor and make sure the CollectionViewCell.swift file is visible. Ctrl and drag from the Title Label to the CollectionViewCell class  and create the following Outlet.

Ctrl and drag from the Checkmark Label to the CollectionViewCell class  and create the following Outlet.

Make sure the CollectionViewController.swift file is visible. Ctrl and drag from the trash bar button item to the CollectionViewController class  and create the following Outlet.

Ctrl and drag from the trash bar button item to the CollectionViewController class  and create the following Action.

Code Implementation 

Go to CollectionViewController.swift file and enter the following line.

var modelData = ["One","Two","Three","Four","Five"]

Since the Reuse Identifier is defined in the Storyboard, the following line can be removed in the CollectionViewController class

// Register cell classes self.collectionView!.register(UICollectionViewCell.self, forCellWithReuseIdentifier: reuseIdentifier)

With the creation of the CollectionViewController class, most delegate methods are already implemented. Some methods must be tweaked a little. Change the following methods.

override func numberOfSections(in collectionView: UICollectionView) -> Int { // 1 return 1 } override func collectionView(_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int { // 2 return modelData.count } override func collectionView(_ collectionView: UICollectionView, cell override func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell { // 3 let cell = collectionView.dequeueReusableCell(withReuseIdentifier: reuseIdentifier, for: indexPath) as! CollectionViewCell cell.titleLabel.text = modelData[indexPath.row] return cell }

By default the CollectionView only has 1 section.

The number of cells is equal to the number of items in the modelData array.

The text of the label is set to the current index of the modelData array.

Change the viewDidLoad method to

override func viewDidLoad() { super.viewDidLoad() navigationItem.leftBarButtonItem = editButtonItem }

The Edit Bar Button Item is added to the Navigation Bar. This can be used to toggle to Edit mode. Build and Run the project.

Implement Editing Mode

Go to the CollectionViewCell.swift file and add two methods.

// 1 var isInEditingMode: Bool = false { didSet { checkmarkLabel.isHidden = !isInEditingMode } } // 2 override var isSelected: Bool { didSet { if isInEditingMode { checkmarkLabel.text = isSelected ? "✓" : "" } } }

A Property Observer is created which will toggle the visibility of the checkmark label according if the coillection view controller is in editing mode or not.

Another property observer is created which will display/remove the checkmark when the cell is selected or not.

Next, go to the CollectionViewController.swift file and add the setEditing(_:animated) method

override func setEditing(_ editing: Bool, animated: Bool) { super.setEditing(editing, animated: animated) collectionView.allowsMultipleSelection = editing let indexPaths = collectionView.indexPathsForVisibleItems for indexPath in indexPaths { let cell = collectionView.cellForItem(at: indexPath) as! CollectionViewCell cell.isInEditingMode = editing } }

This method will check if a cell is in editing mode. Next add the following two methods.

// 1 override func collectionView(_ collectionView: UICollectionView, didSelectItemAt indexPath: IndexPath) { if !isEditing { deleteButton.isEnabled = false } else { deleteButton.isEnabled = true } } // 2 override func collectionView(_ collectionView: UICollectionView, didDeselectItemAt indexPath: IndexPath) { if let selectedItems = collectionView.indexPathsForSelectedItems, selectedItems.count == 0 { deleteButton.isEnabled = false } }

If a cell is selected the trash icon is displayed, otherwise it remains hidden

if an cell is deselected and there are no other cells selected the trash icon is hidden.

Add the following line before the return cell line in the collectionView(_:didSelectItemAt) method

cell.isInEditingMode = isEditing

Again, this will check if a cell is in editing mode. Everything is now in place for the edtitng fucntionality. Now the actual deletion can be implemented.

Delete Items

Implement the deleteItem(_:) Action method

@IBAction func deleteItem(_ sender: Any) { if let selectedCells = collectionView.indexPathsForSelectedItems { // 1 let items = selectedCells.map { $0.item }.sorted().reversed() // 2 for item in items { modelData.remove(at: item) } // 3 collectionView.deleteItems(at: selectedCells) deleteButton.isEnabled = false } }

The selected cells will be reversed and sorted so the items with the highest index will be removed first.

the items will be removed from the modelData array

The selected cells will be deleted from the Collection View Controller and the trash icon will be disabled.

Run Project

Build and Run the project and select the Edit Button. Select a few cells and press the Trash button to remove the items.

You can download the source code of the IOSDeleteItemsCollectionViewTutorial at the ioscreator repository on Github

Items inside a Collection View can be manipulated by modifying the connected model data. In this tutorial a new item will be added to the Collection View Controller. This tutorial is made with Xcode 10 and built for iOS 12.

Project Setup

Open Xcode and create a new Single View App.

For product name, use IOSAddItemsCollectionViewTutorial and then fill out the Organization Name and Organization Identifier with your customary values. Enter Swift as Language and choose Next.

Storyboard Setup

Go to the storyboard. Remove the View Controller from the Storyboard and drag a Collection ViewController to the Scene. Select the View Controller and go to the Editor Menu. Select Embed In -> Navigation Controller.

Select the Navigation Controller and go to The Attribute inspector. In the View Controller section check the "Is Initial View Controller" checkbox.

Select The Collection View and go the Size inspector. In the Collection View section change the Cell Size to a width and height of 100 points.

Drag a Label from the Object Library and place it on the Center of the Collection View Cell.

Select the Label and go to the Attribute inspector. In the View section set the Tag value to 100.

Select the Collection View Cell and go to the Atrribute inspector. In the Collection Reusable View section set the Identifier to "Cell".

The storyboard will look like this.

Since the View Controller is removed from the Storyboard the ViewController.swift file can also be deleted from the project. Add a new file to the project, select iOS -> Source -> Cocoa Touch Class. Name it CollectionViewController and make it a subclass of UICollectionViewController.

The CollectionViewController class needs to be linked to The Collection View Controller object in the Storyboard. Select it and go the Identity Inspector. In the Custom Class section change the class to CollectionViewController

Code Implementation 

Go to CollectionViewController.swift file and enter the following line.

var modelData = ["Oliver","Harry","George","Jack","Noah"]

Since the Reuse Identifier is defined in the Storyboard, the following line can be removed in the CollectionViewController class

// Register cell classes self.collectionView!.register(UICollectionViewCell.self, forCellWithReuseIdentifier: reuseIdentifier)

With the creation of the CollectionViewController class, most delegate methods are already implemented. Some methods must be tweaked a little. Change the following methods.

override func numberOfSections(in collectionView: UICollectionView) -> Int { // 1 return 1 } override func collectionView(_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int { // 2 return modelData.count } override func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell { let cell = collectionView.dequeueReusableCell(withReuseIdentifier: reuseIdentifier, for: indexPath) // Configure the cell // 3 if let label = cell.viewWithTag(100) as? UILabel { label.text = modelData[indexPath.row] } return cell }

By default the CollectionView only has 1 section.

The number of cells is equal to the number of items in the modelData array.

The text of the label is set to the current index of the modelData array.

Build and Run the project.

Add Items

Go to the Storyboard and drag a Right Bar Button Item to right side of the Navigation Bar of the Collection View Controller. Select the Bar Button Item and go to the Attributes inspector. Change the Custom Item Value to Add in the Bar Button Item section.

Select the Assistant Editor and make sure the ViewController.swift is visible. Ctrl-click and drag from the Bar Button Item to the CollectionViewController class and create the following action

implement the addItem(_:) method

@IBAction func addItem(_ sender: Any) { let name = "John" modelData.append(name) let indexPath = IndexPath(row: modelData.count - 1, section: 0) collectionView.insertItems(at: [indexPath]) }

An item with name “John” will be appended to the modellData array and a new Collection View Cell will be displayed at the end of the other cells.

Run Project

Build and Run the project and select the Add Item Button. Each time a cell with the name of “John” will be added.

You can download the source code of the IOSAddItemsCollectionViewTutorial at the ioscreator repository on Github

Data can be passed between view controllers using a segue. In this tutorial a number from a collection view cell will be passed to a label on a new view controller. This tutorial is made with Xcode 10 and built for iOS 12.

Open Xcode and create a new Single View App.

For product name, use IOSPassDataViewControllerTutorial and then fill out the Organization Name and Organization Identifier with your customary values. Enter Swift as Language and choose Next.

Go to the storyboard. Remove the View Controller from the Storyboard and drag a Collection ViewController to the Scene. Select the View Controller and go to the Editor Menu. Select Embed In -> Navigation Controller.

Select the Navigation Controller and go to The Attribute inspector. In the View Controller section check the "Is Initial View Controller" checkbox.

Select The Collection View and go the Size inspector. In the Collection View section change the Cell Size to a width and height of 100 points.

Drag a Label from the Object Library and place it on the Center of the Collection View Cell.

Select the Label and go to the Attribute inspector. In the View section set the Tag value to 100.

Select the Collection View Cell and go to the Atrribute inspector. In the Collection Reusable View section set the Identifier to "Cell".

The storyboard will look like this.

Since the View Controller is removed from the Storyboard the ViewController.swift file can also be deleted from the project. Add a new file to the project, select iOS -> Source -> Cocoa Touch Class. Name it CollectionViewController and make it a subclass of UICollectionViewController.

The CollectionViewController class needs to be linked to The Collection View Controller object in the Storyboard. Select it and go the Identity Inspector. In the Custom Class section change the class to CollectionViewController

Go to CollectionViewController.swift file and enter the following line.

let modelData = ["1","2","3","4","5","6","7","8","9"]

With the creation of the CollectionViewController class, most delegate methods are already implemented. Some methods must be tweaked a little. Change the following methods.

override func numberOfSections(in collectionView: UICollectionView) -> Int { // 1 return 1 } override func collectionView(_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int { // 2 return modelData.count } override func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell { let cell = collectionView.dequeueReusableCell(withReuseIdentifier: reuseIdentifier, for: indexPath) // Configure the cell // 3 if let label = cell.viewWithTag(100) as? UILabel { label.text = modelData[indexPath.row] } return cell }

By default the CollectionView only has 1 section.

The number of cells is equal to the number of items in the modelData array.

The text of the label is set to the current index of the modelData array.

Build and Run the project.

The number value of the collection view cell will be passed to a new View Controller. Open the Storyboard and drag this View Controller to the right side of the Collection View Controller. Drag a Label onto the View Controller.

The data will be passed using a segue. Drag from the Collection View Cell to the View Controller and select the Show segue.

Add a new file to the Project. select iOS -> Source -> Cocoa Touch Class. Name it DetailViewController and make it a subclass of ViewController. Go to the Storyboard, select the View Controller and go the Identity Inspector. In the Custom Class section change the class to DetailViewController.

Select the Assistant Editor and make sure the DetailViewController.swift is visible. Ctrl and drag from the Text View to the DetailViewController class and create the following Outlet

Go to the DetailViewController.swift file and add the following property.

var selectedNumber: String!

Change the viewDidLoad() method to

override func viewDidLoad() { super.viewDidLoad() detailLabel.text = selectedNumber }

Go back to the CollectionViewController.swift file and add the prepare(for:sender:) method

override func prepare(for segue: UIStoryboardSegue, sender: Any?) { if let destination = segue.destination as? DetailViewController, let index = collectionView.indexPathsForSelectedItems?.first { destination.selectedNumber = modelData[index.row] } }

This method notifies the view controller that a segue is about to be performed. Inside the selected cell the corresponding number from the modeldata array will be assigned to the selecedNumber property in the DetailViewController class.

Build and Run the project and select a cell. the number will be passed through and displayed on the Detail View Controller.

original source : 

https://medium.com/@qbo/dismiss-viewcontrollers-presented-modally-using-swipe-down-923cfa9d22f4

Long title, I know. If you don’t understand what behaviour I’m describing, I hope the gif below from my app, Little Windows, helps.

First, let’s setup two ViewControllers — VC1 and VC2. VC1 will be modally pushing VC2 via button press.

Now, in ‘Attributes inspector’ of VC2, set the ‘Presentation’ value from ‘Full Screen’ to ‘Over Full Screen’. This will allow VC1 to be visible during dismissing VC2 via gesture — without it, there will be black screen behind VC2 instead of VC1.

Next, add ‘Pan Gesture Recognizer’ to VC2 and connect it to the UIView. Don’t forget to send its action to a selector in VC2.

In the source code of VC2, add CGPoint variable that can hold the x, y value of initial touch point (i.e. initialTouchPoint). The initialTouchPoint will be used to compare subsequent touch points while dragging so we can move VC2 according to the difference.

Inside the pan gesture recognizer selector (i.e. panGestureRecognizerHandler), create a variable to store the touch point of the instance (i.e. touchPoint).

let touchPoint = sender.location(in: self.view?.window)

Then, observe the type of the touch — whether it began, changed, or ended/cancelled using UIGestureRecognizerState. We want to store the touch point in initialTouchPoint if touch has ‘began’, compare initialTouchPoint with touchPoint if ‘changed’, and determine if we want to dismiss or restore VC2 if ‘ended/cancelled’.

If ‘began’:

initialTouchPoint = touchPoint

If ‘changed’, we get the vertical difference (y) and move the CV2 vertically appropriately. We check whether the vertical difference is great than 0 because we want to allow CV2 to only be moveable downwards:

if (touchPoint.y - initialTouchPoint.y > 0) {    self.view.frame = CGRect(x: 0, y: touchPoint.y - initialTouchPoint.y, width: self.view.frame.size.width, height: self.view.frame.size.height) }

If ‘ended/cancelled’, we see if the downward gesture resulted in a movement more than 100 pixels. The 100-pixel value is arbitrary, the bigger it is, the more effort user needs to put in to dismiss CV2. I find 100 is a reasonable value to provide a good UX. If vertical difference is more than 100, we simply dismiss CV2, otherwise we bring it back to its original position using simple animation:

if touchPoint.y - initialTouchPoint.y > 100 {    self.dismiss(animated: true, completion: nil) } else {    UIView.animate(withDuration: 0.3, animations: {        self.view.frame = CGRect(x: 0, y: 0, width: self.view.frame.size.width, height: self.view.frame.size.height)    }) }

That’s basically all there is to dismiss any ViewController presented modally using swipe down gesture. Here’s everything that goes inside the panGestureRecognizerHandler:

let vc = ExampleViewController()

vc.modalTransitionStyle   = .crossDissolve;

vc.modalPresentationStyle = .overCurrentContext

self.present(vc, animated: true, completion: nil)

modalTransitionStyle를 통해 전환될때 animation을 지정할수 있다.

CakePHP is a PHP frameworks used to sculpture rapid web-based applications or in the programming world is called Rapid Application Reproduction. CakePHP is influenced agreeable to the emergence of other frameworks like Ruby On Rails-based on Ruby language. Without distinction what are the advantages CakePHP? This frameworks is based on PHP which is very popular web programming language awfully it would be very degage for the programmers who have long view in PHP to understand CakePHP. The concept of programming in CakePHP is based on MVC pheon Finished Gauge Controller. Web-based programs that are created using CakePHP is divided into three major sections. The first relation is a Block out in which this part is specifically secondhand in passage to access the database. The Model will have place related to the Controller where this section contains the insides practicality of the device. All data processing occurs on the Controller. The processes within the Controller is implemented in the form of the functions or actions. Data can go on obtained from the Model, a hew or url. The data process resulted sympathy the bookkeeper can exist sent to the Model or displayed to a web page that is handled by a step part in point of the View. View sections are used to display notification or handel garamond of the web. With the way of thinking anent MVC, the URLs used in CakePHP application is divided into several parts, which are server lodgment, the name of the application (sub directory), the name of the cashkeeper, the action and parameters statement. The advantage of using MVC system are functions in the controller can be the case used repeatedly, the error good graces the system can be pokily localized, caste is for lagniappe obvious, CRUD operations that can be implemented easily, providing medium public library that is often forfeited to modus data, the availability relating to authentication and income control component, availability of helper functions that can be pawed-over to accelerate the pulsating universe of the display \ view that use Ajax or Javascript and others. <\p>

Get and Get ASP.net Training in Mehsana, Gujarat. Learn Microsoft Technologies from beginners plane, starting with the basic concepts touching C and OOP's at WebSpec Technologies, Mehsana. Get streamline with other IT Technologies indistinguishable Windows Presentation Arrangement (WPF), Windows Communication Foundation (WCF), Sliverlight, Model View Controller (MVC) and many others.<\p>

.net is a musical sentence framework in consideration of building web pages and web sites with HTML, CSS, JavaScript and server scripting.<\p>

.net supports different development models like Enlacement Pages, MVC (Model Aspiration Auditor), Web Forms, Win Forms.<\p>

What is.net &.net Framework? Start to Get Aware at WebSpec Technologies<\p>

The.NET is a server vanity scripting social science that supports framing and running the next age of applications and XML Web services. And.GRIDIRON Framework is a popular development marker for building apps for Windows Store, Windows Phone, Windows Server and Windows Unicorn.<\p>

The.NET Latticework take the floor includes the C# and Visual Basic programming languages, the common aryan run-time, and an extensive class library edition. Common Language Run-time runs the code and provides services that make the development process easier - it uses JIT Compiler (its an multi-language compiler).<\p>

CLS was designed headed for support language constructs commonly used by way of developers and to formulate verifiable code. CLS includes physiognomy common to many object-oriented programming languages. It forms a subset in relation to the functionality as regards common type system (CTS) and has to boot rules than defined in CTS.<\p>

Even now, the topical framework knockoff in order to developing.net applications is Microsoft Apparent Studio 2012 v4.5 in which you can hoke up all the tasks at one complement - Software Controlled experiment, HTML5 & CSS3 for Designing, Windows Mobile Application Development, Cloud Hosting facility. You can also develop Android & iPhone Applications ingoing it.<\p>

For which to choose.net? - WebSpec Technologies<\p>

Points against go back over the past go for Microsoft ASP.net with C#: Less Coding, Mutli-Language Rapport (more unless 74 languages), Ingeniousness as far as create Web-forms (yoke for Web & Windows), Aegis (Data-validation and Authentication), Uninterrupted Processes, Slow-legged Spreading out, Auto Debugging (IIS - Internet Information Services is the web application server from Microsoft that trots ASP.NET tirelessness environment), Data Access with any Database (ADO.net fulfills this thirst for knowledge).<\p>

One in relation to the most important goals pertaining to.net is to allow developers to write an ASP.NET application using numerous programming languages. As long as each ASP.CORRAL call for contains only one programming dravidian, myself can mix and match different pages using choppy languages and they will computer printout empathic seamlessly. This countermove you carton now have a team of developers with half programming in C# and the autre chose half in VB.NET, with straw vote need to worry of language incompatibilities, etc.<\p>

One great staple item of ASP.NET is Web Services. Web services core that you behind literally carry different pieces of your application on different servers all around the world, and the entire application will handling perfectly and seamlessly. Organism services can even work in addition to normal.CLEAN UP Windows applications.<\p>

ASP.net vet has great XML support. ASP.NET makes it simple to use XML for data storage, configuration and manipulation. The tools which are built into ASP.NET in contemplation of working in addition to XML are very easy to use.<\p>