ProductReview Example: Difference between revisions

From DataFlex Wiki
Jump to navigationJump to search
← Older edit
Jka (talk | contribs)
1,134 edits
m Changed from Web Programming to Web Applications category
 
(34 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{underconst}}
= Introduction =
 
= Functionality =
 
This is yet another example of how to create a [[AJAX]] solution using [[Visual DataFlex]].
 
Before you continue you should take a look at the existing examples in the VDF AJAX library.


This page contains a description of an example project that can be used to study different implementation techniques using VDF as a backend.


In this example the overall goal is to be able to see what users think about a particular item . As an added benefit - users can also share information about where to buy the particular items.
In this example the overall goal is to be able to see what users think about a particular item . As an added benefit - users can also share information about where to buy the particular items.


To accomplish this, then users should be able to:
To accomplish this, then users should be able to:


*login
*login
*choose an item from a list (use a [[AJAX Lookup List]] )
*choose an item from a list
*enter information about a known item ( [[AJAX Form]] )
*enter information about a known item  
**supply information about the place where an item was bought.
*supply information about the place where an item was bought.
*supply a rating of an item  
*supply a review of an item  
*Overview supplied ratings from other users
*Overview supplied reviews from other users
*Find out where to buy the requested item
 
 
 
= VDF Ajax implementation =
The implementation will be split up into Data Dictionaries, Web Service Objects  and web markup . All of these should be familiar to you if you have taken the time to look at the other examples in the VDF Ajax library.
 
 
== [[DataDictionary|Data Dictionaries]] ==
We want to store information about users, places, purchases and known items. The other tables should hold sufficient information about the items purchased and how the users liked them.
 
Create these tables in the database builder and create the associated data dictionaries .
 
The following data dictionaries  should now be available:
 
*Item_DataDictionary
*Place_DataDictionary
*Purchase_DataDictionary
*Rating_DataDictionary
*UserInfo_DataDictionary
 
 
== [[Web Service objects]] ==
Create a [[AJAX WebService Object]] to call from the clientside VDF Ajax lib. This webservice will be responsible for handling the serverside calls.




The Web Service object should provide the following functionality for session management.
The workspace is available here https://github.com/jacobandresen/ProductReview
*UserLogin: checking if the supplied password is correct. Use UserInfo_DD
*HasRights: does the logged in user have the rights to perform the chosen function. Use UserInfo_DD


= [[DataDictionary|Data Dictionaries]] =
We want to store information about users, places and known items. The other tables should hold sufficient information about the items and how the users liked them.


== [[Using AJAX Web Browser Objects|Web Browser Objects]] ==
The following data dictionaries  should now be available (Note that attributes like "UserId" in Token implies a index  on UserId on Token and a relation to the table "User")


*SessionManager.wo: Handle session related information
==User==
*item.wo : handling information about items.
*UserId (Numeric) 
*userinfo.wo : handling information about users
*LoginName (Ascii)
*place.wo: handling info about places
*FirstName (Ascii)
*purchase.wo: handle information about places
*LastName (Ascii)
*rating.wo: handle information about ratings
*Password (Ascii)
*EmailAddress (Ascii)
*Rights (Ascii)
*StreetAddress (Ascii)
*City (Ascii)
*ZIPCode (Ascii)
*Country (Ascii)


The Web Object should use the corresponding data dictionaries
==Token==
*UserId (Numeric)
*TokenValue (Ascii)
*LastAccessed (Date)


=== Access restrictions ===
==Shop==
"ordinary" users should only be allowed to alter information about themselves - e.g "Joe" should not be allowed to alter the address of "Bob".
*ShopId (Numeric)
only "Administrators" should be allowed to add new products and places to the database. E.g "Joe" should not be able to add all his favourite places and products to the list. "Ordinary" users should only be able to rate an item allready in the system .
*Name (Ascii)
*Type (Numeric)
*Description (Ascii)
*StreetAddress (Ascii)
*City (Ascii)
*ZIPCode (Ascii)
*Country (Ascii)


== [[How to develop ASP pages|Web markup]] ==
==Product==
The web markup should be designed around forms, that evolve around the web objects.
*ProductId (Numeric)
Version 1.1 of the AJAX Library has wizards to create most of this functionality.
*Name (Ascii)
*Rating.asp: a list of items with detailed ratings. show details about related users and items.
*Type (Numeric)
**Should use a [[AJAX Lookup list]] to choose the item to supply a rating for
*Description (Ascii)
**Should use a [[AJAX Form]] to supply details about the rating
*ShopId (Numeric)
*RateItem.asp: a form to supply rating information about a particular item ( [[AJAX Form]] )
*Price (Numeric)
*Place.asp: information about a place where items can be bought ( [[AJAX Form]] )
*Purchases.asp: information about what items users has bought at what place ( [[AJAX Form]] )


=== UI specifics ===  
==Review==
*"Administrators" have a different ui than "ordinary" users.
*ReviewId (Numeric)
*ItemId (Numeric)
*UserId (Numeric)
*Rating (Numeric)
*Comment (Ascii)


= Implementation =


[[ProductReview VDF AJAX implementation]]


[[Category: Web Programming]]
[[Category: Web Applications]]
[[Category: Data Dictionaries]]

Latest revision as of 14:14, 8 April 2020

Introduction

This page contains a description of an example project that can be used to study different implementation techniques using VDF as a backend.

In this example the overall goal is to be able to see what users think about a particular item . As an added benefit - users can also share information about where to buy the particular items.

To accomplish this, then users should be able to:

  • login
  • choose an item from a list
  • enter information about a known item
  • supply information about the place where an item was bought.
  • supply a review of an item
  • Overview supplied reviews from other users


The workspace is available here https://github.com/jacobandresen/ProductReview

Data Dictionaries

We want to store information about users, places and known items. The other tables should hold sufficient information about the items and how the users liked them.

The following data dictionaries should now be available (Note that attributes like "UserId" in Token implies a index on UserId on Token and a relation to the table "User")

User

  • UserId (Numeric)
  • LoginName (Ascii)
  • FirstName (Ascii)
  • LastName (Ascii)
  • Password (Ascii)
  • EmailAddress (Ascii)
  • Rights (Ascii)
  • StreetAddress (Ascii)
  • City (Ascii)
  • ZIPCode (Ascii)
  • Country (Ascii)

Token

  • UserId (Numeric)
  • TokenValue (Ascii)
  • LastAccessed (Date)

Shop

  • ShopId (Numeric)
  • Name (Ascii)
  • Type (Numeric)
  • Description (Ascii)
  • StreetAddress (Ascii)
  • City (Ascii)
  • ZIPCode (Ascii)
  • Country (Ascii)

Product

  • ProductId (Numeric)
  • Name (Ascii)
  • Type (Numeric)
  • Description (Ascii)
  • ShopId (Numeric)
  • Price (Numeric)

Review

  • ReviewId (Numeric)
  • ItemId (Numeric)
  • UserId (Numeric)
  • Rating (Numeric)
  • Comment (Ascii)

Implementation

ProductReview VDF AJAX implementation

Retrieved from "https://dataflex.wiki/index.php?title=ProductReview_Example&oldid=3284"