On Mon, Mar 30, 2009 at 7:35 PM, Harsha Halgaswatta < [email protected]> wrote:
Hi
Now i have gone through many tutorials and documents and obtained a good picture of xwiki photo album over existing old photo album. I saw that the commenting features and some other features are very basic and even don't comply with the expected flow.
Now i am in the process of making some mockups while thinking the class level interaction just to illustrate you the flow of the photo album along with their functionalities.
After going through the xwiki way i feel it would better create a class while creating a new album and attach it to the page. Then anyone who creates an album would gain the reference (instance) of that class. This class would consist of the functionalities that are possible with the newly created album.Consequently the front end would invoke underlying logics as they suppose to gain the functionality out of the class. Perhaps i may need two or three classes accordingly (one class may be too big etc). What do you think ?
Other than that Would you please let me know where the xwiki commenting features and tagging features retain, From where i would learn it. And also in some situations i may need to involve with Ajax based scenarios (maintaining privacy information , tagging features etc). How Ajax is used in xwiki , would i free to use any Ajax library or what else.
Adding something : Commenting features are ok , i just went through it. It's pretty cool It mentions the UI should be Ajax based and should also be functional in browsers without JavaScript. In that case would i have to implement the same scenarios in two ways ? . I mean if i use Ajax libraries for a function it works on javascript enabled browsers, if not it fails. Then the functionality should be preserved without javascript using another techniques. is there a specific library or method in Xwiki to handle those kind of scenarios.
I hope to present you the mockups of the photo album today evening or tomorrow.
Thanking you. Harsha