Silverlight Views - GUI Work

The scope of this project is for the following: This is a Silverlight project for the visual layer of an application. The business logic has already been generated, and follows an MVVM pattern. The design has already been generated and has been attached this project. The business workflow of the application is uploading images for coupons/advertisments. The names of instances, their types, and how to use the XAML to attach to the view will be provided. The worker will have to generate a stubbed out version of the View Model under the direction of an architect. The stub will also have to generate the data to work with in the view. The attached zip file has a rough version of the requirements. Minor adjustments have been made small features and a new design doc will be provided. For example, the scope is actually reduced by remove the "Items Panel" from the Coupon Designer. See attached doc. Scope will be settled before the winning bidder is selected. The deliverable will be a Silverlight application and a Visual Studio solution. **THE ATTACHED RFP IS A SECOND VERSION OF PROJECT SCOPE** ## Deliverables * * *This broadcast message was sent to all bidders on Thursday Aug 18, 2011 9:17:53 PM: Hi, The following is a set of questions and answers. _--------------------------------- 1. I assume that you want everything done as vector graphics in Silverlight. Do you need logo done as vector graphics too? A : The work for the logo will be generated by the lead designer. It is out of scope for this project. Just the placement will be required. 2. It will be pretty hard to match perfectly the design which I guess was done in Photoshop or Illustrator. For example, the background looks like a gradient with some glows(starting from the bottom of the logo) and there is another on the right I think. Gradient can be done I think but glows are harder. I will do my best to match the design but from my experience it's very hard or impossible to do the same things you do in Photoshop\Illustrator. A : The background will be a static image. Best effort will be made to create a similar implementaion to the design. 3. I guess all strings need to be localized, so the work must include setting strings in the .resx and bind to them from XAML. Is this correct? A : Yes, the strings will need to have a localized setup. Only english will be required in the initial strings. 4. About Tools Panel: It's not clear to me if the functionality of the tools are already implemented in the ViewModels. Do you need them created for this phase? For example, is image uploader coded already? This requires some webservices on the server, storage access, etc. Also, the same question for other tools you mentioned: shape tools(draw, select, edit them, move points, etc), gradient tool(what kind of gradient?, both UI and functionality for the gradient tool is needed to select gradient shades). If the tools are not implemented and need to be implemented, there are many details regarding the tools which came to my mind. For example, should gradient orientation be edited? How should the edit on shapes work? Allow point edit? A : The tools panel is out of scope for this project. Only the marketing panel will be required, with the ability to upload an image. The tools panel will be worked on in the next release. 5. I am not sure exactly what is what you refer to as stub data. Is it the design view model necessary to display data at design time in Visual Studio? A : A "Stub" creates dummy data that can ben consumed by the View. It also allows the developer to work with the application in a simulated manner to test out the view. The creation of the stub will be up to worker. * * *This broadcast message was sent to all bidders on Friday Aug 19, 2011 4:15:47 PM: In an effort to clarify the requirements, I have changed the file that is attached to this project description to a powerpoint that includes screenshots of the final design for the scope of this project. The previous document that I had posted included a larger design, and hence a larger scope. The document that I have now attached to this project has a smaller scope as the tools for the coupon design have been reduced. Let me know if you have any questions. Cheers, Jeff