Hey Dragan, I really like your initiative. I'd be willing to mentor a student this year, so go ahead and discuss your ideas. You'll have to understand though that it's not the mentor's task to guide you through technical issues you encounter or give you lessons on the product's internals. I'll give you feedback on your ideas, provide you with pointers to documentation and code should you need it and help you integrate with the community. But your main point of contact for everything should be the community as a whole, that is the users and developer mailing lists.
That being said, you'll find my comments to your ideas inline. You might also want to look at https://issues.apache.org/jira/browse/TAP5-1474 as well as at some of the wishlist items for additional ideas. Uli On 24.03.2011 09:32, [email protected] wrote: > Hey, that's great thanks. > > I would really appreciate if everyone reading this list could just write > their ideas here for what the project should focus on. > > I have no problem with working on new components (like GSOC 2010) or some > other functionalities. IMO I think that this project should focus on > something that will be useful for the vast majority of users. Please feel > free to discuss the ideas I wrote in the prev email, or I could elaborate > them in more detail if needed. > > Thanks, > 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. Some thought has to be put into that as to what happens when there are multiple Grids on the same page. Generally I like the idea but it's not my favorite. >>> 2. Multi-upload component: >>> 1. based on http://valums.com/files/2010/file-uploader/demo.htm >>> https://github.com/valums/file-uploader Sounds like a good addition. It would be nice if https://issues.apache.org/jira/browse/TAP5-638 could be fixed at the same time. You'll have to pay attention to license issues though. The file-uploader you mentioned is licensed under GPL and LGPL. Both are incompatible with the Apache License and that component thus can't be integrated into Tapestry core. >>> >>> >>> 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. Sounds interesting. >>> >>> >>> 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. You can already achieve that with what Tapestry provides today. What's the additional benefit? >>> >>> >>> 1. Asynchronous Ajax updates (like gmail). I have no idea how to do >> this >>> ATM but its a very compelling UI feature. What's wrong with Zones? >>> >>> >>> 1. Right click menu: Comprehensive configuration options. Use it as a >>> mixin, component etc. Have it configured by page, component etc. Nice. I like that one. >>> >>> >>> 1. Better transaction support with Hibernate. What's wrong with the current solution? What would you change and why? >>> 2. Integrate Tapestry with some NoSQL database. I have small experience >>> with CouchDB and MongoDB. This would be a nice addition. How would such an integration look like? Also, I'd like to see a generic integration that can be connected to differnt NoSQL databases with the right driver and a driver implementation for one of them. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
