Also to take this further if a user types in @tabname, The code will hunt down to see if that name fits with a live tab they have on their portfolio and it links to it. so now users can talk about their other portfolios and maybe sites they have created as well as talk about one tab from another and create direct easy to use links between tabs.
Some layout fixing I have done such as the edit tab button has now been floated to the far side and the position of the box that appears is fitted nicely to it's side so that it doesn't have any flash z-depth problems. Also a smaller fix was the delete button for tabs has been fixed so that if users resize the window it will stay in position which is done by using relative position on it and a absolute on its parent.
I have fixed a small bug with the add items textboxes that now when you open/close them they clear themselves so that if you go from title where you have typed something to Youtube. It will not have the title text in the Youtube textbox.Now the big one. The issue that's been sitting on my to do list the longest out of anything I have done so far. The validation issue which has now been resolved with a use of a transactional method which rolls back changes if they fail. This means I was free to add and use the RuleViolation method on all classes and post them to the page as seen below.
There is alot of text inputs around the site which could easily be errored on so this is the list where its implemented:-- Edit/Create portfolio page
- Login
- Sign up account
- Add tab
- Add text/title
- edit tabs names
- Edit Links
- Add Links
- Post Article
- Change Account Details (email/password)
As there are different types of validation, and different ways to implement it, I have been flexible. For example above is a js alert as a user didn't enter text for added a tab(they just hit enter) as its a json response I have responded in the above example instead of a post on a page.The plan is to implement Javascript jQuery validation which can take over for alot of the validation done on the background so things like this could be alot cleaner as well as saving post backs to the database. Sometimes a post back is required such as checking email/usernames are not in use.
No comments:
Post a Comment