On Fri, Mar 25, 2011 at 3:35 AM, [email protected] <[email protected]> wrote: > On Thu, Mar 24, 2011 at 9:28 PM, Kalle Korhonen <[email protected]> > wrote: >> On Thu, Mar 24, 2011 at 1:32 AM, [email protected] >> <[email protected]> wrote: > About conversations with local storage: I'm very interested in doing this, > but I have a question. I have went over the source code of > tapestry-conversations, and I'm asking: if I decide to do it, will it be > better to be a part of tapestry-conversations or build > a separate conversations module? > Also I'm interested in some ideas about using the local storage for other > purposes as well.
Yes, local storage can be used for a lot of interesting purposes. There's no way to know for sure before prototyping it first what the best approach is. If you decide on this idea, I think you should definitely draw as much insipiration and code from tapestry-conversations as possible but not worry about breaking any interfaces. I have no interest in keeping tapestry-conversations as a Tynamo module - if the community wants, we could fairly easily (me being a committer in both and Tynamo using Apache license) make it into a tapestry core or apache extras module. It might need a different @Persist identifier though, especially given that you cannot count on local storage to be automatically available. But as said, difficult to know for sure what it's going to turn into before writing the code first. HTML5 features definitely have some sex appeal, which is always good marketing. > About websockets: I think it would be very good to integrate it with zones, > and make it trivial to push data from the server (trigger zone updates). I > also read this great article from Robin Komiwes (from the wooky project), > about using WebSockets with T5, NodeJS and Redis. The important thing here > was using NodeJS as a server fro the WebSockets communication because of > scalability, performance and locking issues of java web servers. I'm not > sure what exactly the performance issues will be here, but I am > interested in trying it out. Also about the implementation with T5 I don't > know the WebSockets protocol well and I like to ask is tapestry's page > render using singletones now an obstacle for this or no? Yes, I'm thinking something along those lines as well and certainly I've also read the same interesting post from Robin. I think it's also a very interesting, strong and well-enough defined idea to make a GSoC project out of. Just to address the question, I don't think the server side of the websocket would live on the page, but perhaps there'd be a WebSocketService that would manage the sockets client have opened - that would seem more in tune with Tapestry, don't you think? Kalle > >> >> Kalle > > Cheers , > Dragan Sahpaski >> >> > On Thu, Mar 24, 2011 at 3:47 AM, Kalle Korhonen >> > <[email protected]> >> > wrote: >> >> >> >> Thanks for volunteering Dragan. I think it's too good of a opportunity >> >> for T5 to pass up. I think there are many more qualified T5 committers >> >> to serve as mentors (hoping that Andreas would step up :) but if all >> >> the other committers are too busy, I'll do it. I'm way busy at the >> >> moment myself but I'll make time to make a strong proposal for >> >> whatever topic you and us decide on. >> >> >> >> Kalle >> >> >> >> >> >> On Wed, Mar 23, 2011 at 3:15 PM, [email protected] >> >> <[email protected]> wrote: >> >> > Hi, >> >> > I want to be a T5 GSOC student because I want to contribute to the T5 >> >> > community and I think that the GSOC programme can provide me with >> >> > mentorship >> >> > (from a T5 commiter or high skilled developer) that will get me >> >> > familiar >> >> > with the internals of the T5 web framework and IOC container. >> >> > >> >> > I know that the T5 devs are really busy, but I think it wont be much >> >> > of >> >> > a >> >> > burden for the mentor to have me as a student because I have some >> >> > background >> >> > with t5, and I’m available on IM and email 24/7 (no fullltime >> >> > obligations - >> >> > just studies). >> >> > >> >> > I'm a first year masters student from Macedonia and I have about 2.5 >> >> > years >> >> > experience with t5. I'm pretty familiar with Tapestry IOC, I've done >> >> > AOP >> >> > and >> >> > meta-programming in t5 and I know jQuery (for some custom >> >> > components). >> >> > >> >> > Here are some of my thoughts about potential GSOC 2011 tasks. Please >> >> > give me >> >> > some guidlines to discuss these or new ideas that would benefit the >> >> > T5 >> >> > community the most in order to get my proposal good and ready ASAP. >> >> > >> >> > GSOC 2011 - Applicant Dragan Sahpaski >> >> > Tapestry ideas/proposals: >> >> > >> >> > 1. Grid component enhacements: >> >> > 1. Sorting: Support url query parameters for sort keys (property >> >> > ids >> >> > in the BeanModel). Example without zones: If you have a >> >> > List<Employe> >> >> > and sort by employee.department you can get a URL like: >> >> > /employeeslist?sort=department&order=asc. >> >> > Example with zones: /employeeslist#sort=department&order=asc. >> >> > The SPI behaviour can be generalized for zones but thats a >> >> > different >> >> > story all together. >> >> > 2. Pagination: better pager. Also page-number can go into the >> >> > url. >> >> > 3. Better HibernateDataSource for the grid >> >> > 4. Changing column order and visibility and saving this in a db. >> >> > 2. Multi-upload component: >> >> > 1. based on http://valums.com/files/2010/file-uploader/demo.htm >> >> > https://github.com/valums/file-uploader >> >> > >> >> > >> >> > 1. Persistence strategy for persisting @Persist-ed fields in the >> >> > DB. >> >> > Exporting and changing saved values between users. Example: This is >> >> > usefull >> >> > when you are building a personalized app and the user changes UI >> >> > state >> >> > that >> >> > gets saved in the DB and the changes he did are there the next time >> >> > he >> >> > logs >> >> > in. >> >> > >> >> > >> >> > 1. Asynchronous DB operations. This would be a use case where the >> >> > DB >> >> > operation is not causing changes visible to the user so the request >> >> > does not >> >> > need to wait for it. Example: Logging requests, the user is not >> >> > aware >> >> > of >> >> > this and doues not have to wait the logged request to get commited. >> >> > >> >> > >> >> > 1. Asynchronous Ajax updates (like gmail). I have no idea how to do >> >> > this >> >> > ATM but its a very compelling UI feature. >> >> > >> >> > >> >> > 1. Right click menu: Comprehensive configuration options. Use it as >> >> > a >> >> > mixin, component etc. Have it configured by page, component etc. >> >> > >> >> > >> >> > 1. Better transaction support with Hibernate. >> >> > 2. Integrate Tapestry with some NoSQL database. I have small >> >> > experience >> >> > with CouchDB and MongoDB. >> >> > >> >> > >> >> > Cheers, >> >> > Dragan Sahpaski >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
