Hi Chris and Lucas, On Wed, Mar 26, 2008 at 12:42 PM, percious <[EMAIL PROTECTED]> wrote: > I like all of your widget ideas. Hopefully you aren't biting off more > than you can chew (those are some complex widgets you are proposing).
We are still working on refining the proposal. We would greatly appreciate any suggestions in terms of what is useful and feasible to the TurboGears project. We should have a formal proposal posted later tonight. > How many people are planning to work on this project? I am unclear if > it is two people. We currently have one student who is interested in working on this project for a GSoC, that is Ming. There is a chance that there may be another student also working on this project (but possibly a different aspect of it) for a course credit or something like that. > Can you explain what you mean by database harmonizer? The database harmonizer is a kind of framework for merging similar, but differently organized, databases into a single unified database. We intend to do this by creating a unified local database schema, and accept foreign data in CSV format with the different columns mapped to columns in the local database. For example: A health services provider might have a database of all the walk-in clinics in a given area. Similarly, a restaurant review blog might have a database of all the various restaurants it reviewed, where they're located, and what hours they're open, etc. We want to create a system for taking this kind of geographically positioned data and aggregating it into a single database that is searchable and displayable via a Google Maps mashup. Jane, the organizer of the weMap effort, has already managed to get some providers in Toronto (Canada) to give us access to their databases, and we believe this effort could be extended to a national, if not international, scope. On Wed, Mar 26, 2008 at 10:00 AM, Lukasz Szybalski <[EMAIL PROTECTED]> wrote: > I wonder how similar or different it will be then google opensocial > http://code.google.com/apis/opensocial/ (yahoo and myspace have joined > also)? > If some of the components are similar or the same then will weMAP > support opensocial api? The scope of the weMap project does not really include any social networking. When I said "social services", I meant in the literal sense such as public health facilities. Given that, I don't see how opensocial would have any overlap with this project. This would be a lot like going to Google Maps and typing "hospital" and getting listings of all the nearby hospitals. Only difference is, Google gets this data from a small number of very specific sources. In our system, we would allow any organization to include their database, and maintain it within weMap. Hope this answers your questions. Ming might have more insight on this as he was the one that worked on this project for a course credit in the previous semester. Thanks, Andrey > On Mar 25, 9:44 pm, "Ming T. Chow" <[EMAIL PROTECTED]> wrote: > > Hi Chris, > > > > My name is Ming T. Chow and I am the student that wants to work on > > this project this summer under GSoC. I am currently developing the > > back-end of weMap using TurboGears as part of a consulting course at > > the University of Toronto under professor Greg Wilson. > > > > Let me try to clarify the questions you have about Andrey's post: > > > > >I'm a bit confused. Do you already have a student who wants to work on > > >this project? Or are you looking for students to help you with weMap? > > > > I am the primary student who will be working on weMap this summer and > > depending on the tasks that are agreed upon, we may enlist the help of > > other students (most likely not under GSoC). > > > > >Which tasks do you want students to do exactly? > > > > I have identified some tasks that are consistent with weMap and the > > growth of TurboGears. The tasks can be split into two parts, the > > application and the widgets: > > > > 1. Create a general-purpose database harmonizer that would serve both > > as an application suitable for the cogbin and provide documentation to > > make working with the project instructional for new users. On this > > vein, we may want to switch over development of the project to using > > TG 2.0 or use as many of the new components as possible (Genshi and > > ToscaWidgets looks mighty attractive). This task shares similar > > ideals as the TG CMS project on the ideas page where the point is to > > make components that are extensible outside of the core application. > > > > 2. Individual Widgets: Currently, we are looking to expand on or > > create three widgets that weMap needs and will most definitely benefit > > the TG widget toolbox. > > > > a. A Column A-> Column B selector that handles ordering. The idea is > > to expand on SelectShuttle and add a set of UP/DOWN buttons beside the > > selected items column such that the ordering of the items can be > > adjusted. However, that is only a start. We can take this one step > > further and allow functions to be selected between the columns such > > that the functions are applied to the item(s) in the source column > > before insertion into the destination column. For weMap, this will > > help in removing bad address components (e.g. PO Boxes) that can > > affect geocoding results. For TG, this widget will have wide > > applications in any selection operation where ordering and > > customization of selected items are useful (e.g. Home decor site that > > lets users choose colours, textures, and ornaments for a wall; or a > > pizza parlour that allows users finer control of the toppings that > > goes on the pizzas) > > > > b. An interactive datagrid. The current datagrids available in the TG > > toolbox do not allow for row/column/cell interactions. This poses a > > bit of a problem for weMap as a datagrid is the best control to use > > for displaying database items. A much needed function for weMap is to > > be able to edit the database to better handle duplicates and other > > inconsistencies. Without an interactive datagrid, the interface just > > won't be as intuitive. For TG, I am sure you can see having an > > interactive datagrid (preferably Ajax enabled) in the TG toolbox will > > be a great asset to the TG community. The creation of this widget > > coincides with the TwTools project on the ideas page since we will > > likely be looking into javascript toolkits for the core code. As well, > > the interactive datagrid is one of the tasks of the DBSprockets User > > Interface project. > > > > c. An ajax file uploader. The need for this widget for weMap and TG > > is quite trivial. There are no ajax-enabled file uploaders in the TG > > toolbox and weMap allows users to upload large/multiple database files > > and we will need to develop some callbacks during the uploads. > > > > I spoke with Matiu on the TG IRC channel about these widgets and he > > seems to like the idea a lot. He recommended that I implement them in > > ToscaWidgets so that it can be more usable for TG 2.0. I agree with > > him. > > > > (Possibly) 3. Since the database harmonizer is the backend to weMap, > > I am also interested in giving the Google Maps enabled front-end the > > TG treatment (front-end is currently written in php). I read on the > > mailing list archive that someone did attempt to create a google maps > > widget for TG, but I was not able to identify the current status of > > the project. So if this is still in need and it is consistent with > > the weMap objectives (it may be a matter of discussion in the near > > future), integrating TG and google maps will prove to be an exciting > > challenge. Also, this coincides with one of the objectives in TwTools > > (Notice how many existing project ideas we are stepping on?) > > > > I understand that it is likely not possible to achieve all of the > > above tasks within the summer, this is why we would like to be > > affiliated with TG through GSoC to both establish a tighter > > integration with the TG community and to seek project-specific > > guidance from you and the other mentors. Most importantly, given that > > the above tasks have the tendency to intersect with currently proposed > > ideas, we will want to coordinate our efforts with the other GSoC > > projects so that we don't end up doing duplicate work. I am hoping > > through GSoC, we can better align ourselves with the objectives that > > are beneficial to the TG community, the weMap project, and the mentors > > and student(s) involved. > > > > I will be sending in my application as a student for this project as > > soon as it is posted up on the ideas page. > > > > Thank you. > > > > Ming T. Chow > > > > On Mar 25, 7:38 pm, Christopher Arndt <[EMAIL PROTECTED]> wrote: > > > > > Andrey Petrov schrieb: > > > > > > Hello there, > > > > > Hi! Welcome to the TurboGears GSoC 2008 mentors! > > > > > > Project of interest: > > > > > > I originally proposed this project to the PSF GSoC list but after some > > > > discussion, it appears that it would be a better fit for the > > > > TurboGears community. > > > > > > The weMap effort is organized by Jane (CC'd), who approached me to act > > > > as a mentor for it. > > > > > > While I'm at it, here's a draft of our formal TurboGears GSoC > > > > application for the project: > > > > > I'm a bit confused. Do you already have a student who wants to work on > > > this project? Or are you looking for students to help you with weMap? > > > Which tasks do you want students to do exactly? Your project proposal > > > only lists general goals but no actual tasks. Can you please update it > > > and put it on our projects page (if it's not already there). > > > > > http://docs.turbogears.org/GSoC/Ideas2008 > > > > > Chris > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
