[Pharo-project] GSoC13: Google Summer of Code started, your ideas please!
Dear Smalltalkers, Time for your cool project ideas on this year Smalltalk GSoC! For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas. Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully! For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc. We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects. More on our special Smalltalk GSoC 2013 website: http://gsoc2013.esug.org I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC: http://groups.google.com/group/smalltalk-gsoc-mentors While students interested on GSoC please join a special Smalltalk GSoC mailing list for you: http://groups.google.com/group/smalltalk-gsoc-students Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
Hi janko How do you want to proceed for the topics? I have a list of topics now where do we write them. - tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
Hi Stef, Post on the mailing list for each project idea by following this template: Level: (beginner, intermediate, advanced) Possible mentor: Possible second mentor: Description Technical Details Benefits to the Student Benefits to the Community Best regards Janko Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
=============================================================== UIPainter =============================================================== Level: advanced Possible mentor: Stéphane Ducasse Possible second mentor: Esteban Lorenzano Description: The purpose is to offer a way to easily describe and create UI using a point and click interface. This interface should be extendable, as well as the widget proposed. The Painter should also propose a simple way to link widgets together, and to locally redefine behaviours. Technical Details: using Spec, the UIPainter should be able to generate the needed methods (and Layouts). The UI corresponding class could also be generated. Benefits to the Student: A deep understanding of UI creation. A good set of knowledges about widgets interactions. The students will also benefits of an understanding of Spec at all the levels. Benefits to the Community: The community will benefit of a new tool for generating UIs easily using the new platform independent UI framework. A UIPainter will help developers by improving the widgets reuse and simply the process of UI creation. =============================================================== Spec platform/framework Independence =============================================================== Level: intermediate Possible mentor: Stéphane Ducasse Possible second mentor: Nicolas Petton Description: The goal is to improve and ensure the platform independence of Spec. Indeed, one of Spec goals is to generate widgets on multiple UI rendering framework (Morphic, Seaside, etc). The student could improve Spec by providing a set of widgets for multiple framework, and ensure the usability of Spec in different Smalltalk dialect. Technical Details: Currently running only in Pharo, Spec should be able to be used easily on Squeak. One interesting target is to be able to use it in Amber by example. Benefits to the Student: the student will acquire knowledge and experience about different Smalltalk implementation. He will also experience different UI framework, and trough Spec how widgets interact with each others. Benefits to the Community: The community will benefit of the coolness of Spec, and will also have a single way to define UIs regardless of the framework used to render them. =============================================================== Nautilus In Spec =============================================================== Level: intermediate Possible mentor: Stéphane Ducasse Possible second mentor: Benjamin Van Ryseghem Description: Nautilus is the new default browser for Pharo3.0. But because the UI is fully platform dependent, it can not be used in other dialects (contrary to OB by example). The goal is to migrate the entire Nautilus UI to a Spec based version, ti be able to export Nautilus. Technical Details: Currently Nautilus is fully written using Morphic (and even have its own morphic widgets). The idea is to redefine the existing UI using Spec, rethink the way interaction between sub widget is done, and provide a way to statically describe Nautilus UI. Benefits to the Student: the student will acquire knowledge about Morphic. He will also learn how Spec is working and its mechanisms for event propagation as well as widget static description. He will also learn how to define new Spec widgets and how to link them to already existing Morphic widgets. Benefits to the Community: The community will benefit of a more modular UI for Nautilus (since every one can then specify its one Nautilus UI), as well as a browser which may be used in different dialects. ===============================================================
Janko I sent some topics now I think that it would be better to edit directly the web site because else somebody will have to do it again. So if you need I can edit directly a form. Stef
Hi Stef,
Post on the mailing list for each project idea by following this template:
Level: (beginner, intermediate, advanced)
Possible mentor:
Possible second mentor:
Description
Technical Details
Benefits to the Student
Benefits to the Community
Best regards Janko
Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
Hi Stef, Dne 09. 03. 2013 21:47, piše Stéphane Ducasse:
I sent some topics now I think that it would be better to edit directly the web site because else somebody will have to do it again. So if you need I can edit directly a form.
Direct editing will certainly be a better solution, just that for now only the whole ideas page will be editable and not through a form for each idea separately (I don't have a time right now for adding that). To edit a whole page publicly I need to recheck the locking mechanism first, then OpenID authentication currently don't work because of a expired Google's cert, so ... let me put ideas by me for now, later I'll try to open editing more broadly. Best regards Janko
Stef
Hi Stef,
Post on the mailing list for each project idea by following this template:
Level: (beginner, intermediate, advanced)
Possible mentor:
Possible second mentor:
Description
Technical Details
Benefits to the Student
Benefits to the Community
Best regards Janko
Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
Ok I will send other descriptions a plain text. I still continue to believe that we can create a real eco system where people can make money. Stef
Hi Stef,
Dne 09. 03. 2013 21:47, piše Stéphane Ducasse:
I sent some topics now I think that it would be better to edit directly the web site because else somebody will have to do it again. So if you need I can edit directly a form.
Direct editing will certainly be a better solution, just that for now only the whole ideas page will be editable and not through a form for each idea separately (I don't have a time right now for adding that).
To edit a whole page publicly I need to recheck the locking mechanism first, then OpenID authentication currently don't work because of a expired Google's cert, so ... let me put ideas by me for now, later I'll try to open editing more broadly.
Best regards Janko
Stef
Hi Stef,
Post on the mailing list for each project idea by following this template:
Level: (beginner, intermediate, advanced)
Possible mentor:
Possible second mentor:
Description
Technical Details
Benefits to the Student
Benefits to the Community
Best regards Janko
Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
Hi Janko! We have this: Level: intermediate Possible mentor: Guillermo Polito Possible second mentor: Esteban Lorenzano Description: DBXTalk database driver nowadays uses a native library called OpenDBX. This library stands as an adaptor between different database drivers, implemented in C. This native library supposes many problems: - it should be normally compiled for each different platform (Windows, *nix, macosx) and database vendor - each of its bugs should be fixed in a C source code base - OpenDBX do not expose the particular behavior of each database vendor, but their common denominator - difficulty for distribution, and problems to locate libraries. This project proposes to use NativeBoost bindings to remove the necessity of the native openDBX library, simplifying the deployment of applications using relational databases, and moving all the code base to Smalltalk. Technical Details: This project supposes the replacement of openDBX old FFI bindings by direct nativeBoost bindings to the database drivers. The new drivers should be completely written in Smalltalk, and take care of platform and library resolution in the image side. These drivers should be polymorphic while also enabling the access to specific API provided by database vendors. Benefits to the Student - Use a highly reflective dynamic language - Learn the basics of foreign function interface (and its exponent NativeBoost) - Learn how to manage external resources and platform specific native code - Put into usage its object design skills to transform a structured designed library into an object oriented one Benefits to the Community - A more malleable and full smalltalk implementation of relational database drivers - Easier deploy for applications using relational databases - Database divers exposing their particular apis, providing access to features not available before Guille On Sat, Mar 9, 2013 at 2:16 PM, Janko Mivšek <janko.mivsek@eranova.si>wrote:
Hi Stef,
Post on the mailing list for each project idea by following this template:
Level: (beginner, intermediate, advanced)
Possible mentor:
Possible second mentor:
Description
Technical Details
Benefits to the Student
Benefits to the Community
Best regards Janko
Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
And another one: Level: intermediate Possible mentor: Santiago Bragagnolo Possible second mentor: Guillermo Polito Description: Gamification is becoming more and more popular in a lot of applications. What about gamify the pharo development process? You get points by adding comments, fixing bugs or answering questions. You can be a comment healer, a bug slayer, a Zinc magician. The intend of this project is to build an application that integrates with the Pharo development process tools (issue tracker, smalltalkhub, stack overflow) and provides a gamified experience, so we get more and more motivated to code. Technical Details: This project implies the creation of an application which communicates with different applications APIs and perform some analysis on them such as running source code Lint rules. Additionally, this application should have a web frontend. Benefits to the Student - Use a highly reflective dynamic language - Learn to develop a complex application architecture with several communicating components - Learn about ramification concepts - Learn about an open source project development and integration process, such as Pharo - Learn web application development techniques Benefits to the Community - have a platform to organize activities and events around the Pharo development - be more motivated to participate into the development for rewards such as experience, badges and abilities On Wed, Mar 13, 2013 at 4:40 PM, Guillermo Polito <guillermopolito@gmail.com
wrote:
Hi Janko!
We have this:
Level: intermediate Possible mentor: Guillermo Polito
Possible second mentor: Esteban Lorenzano
Description: DBXTalk database driver nowadays uses a native library called OpenDBX. This library stands as an adaptor between different database drivers, implemented in C. This native library supposes many problems: - it should be normally compiled for each different platform (Windows, *nix, macosx) and database vendor - each of its bugs should be fixed in a C source code base - OpenDBX do not expose the particular behavior of each database vendor, but their common denominator - difficulty for distribution, and problems to locate libraries. This project proposes to use NativeBoost bindings to remove the necessity of the native openDBX library, simplifying the deployment of applications using relational databases, and moving all the code base to Smalltalk.
Technical Details: This project supposes the replacement of openDBX old FFI bindings by direct nativeBoost bindings to the database drivers. The new drivers should be completely written in Smalltalk, and take care of platform and library resolution in the image side. These drivers should be polymorphic while also enabling the access to specific API provided by database vendors.
Benefits to the Student - Use a highly reflective dynamic language - Learn the basics of foreign function interface (and its exponent NativeBoost) - Learn how to manage external resources and platform specific native code - Put into usage its object design skills to transform a structured designed library into an object oriented one
Benefits to the Community - A more malleable and full smalltalk implementation of relational database drivers - Easier deploy for applications using relational databases - Database divers exposing their particular apis, providing access to features not available before
Guille
On Sat, Mar 9, 2013 at 2:16 PM, Janko Mivšek <janko.mivsek@eranova.si>wrote:
Hi Stef,
Post on the mailing list for each project idea by following this template:
Level: (beginner, intermediate, advanced)
Possible mentor:
Possible second mentor:
Description
Technical Details
Benefits to the Student
Benefits to the Community
Best regards Janko
Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
âHi, my name is Mariano,i'm a student at University of Quilmes. i have a experience in other programing languages like Scala, or Objective-c, and i like to participate in a real Smaltalk project. My background in this tecnology, is a little small, i never make a real project (I do in other tecnlogies) and i think the summer of code is a great oportunity for learn and practice. My ideas are: Level: intermediate Possible mentor: guillermo polito Possible second mentor: (?) Description: jabber client / server to communicate smaltalk with this common protocol. Technical Details: Create a jabber client api, to provide the capacity to connect with accouts like google talk, or facebook chat. Create a jabber api server, with the capacity of accept connection of diferent jabber clients. Benefits to the Student: - Learn ââ ââ â and understand â architecture ââ server/client - Learn about the protocol jabber. â â - Use a highly reflective dynamic languageâ Benefits to the Community: - Server and client for jabber protocol - Posible implementations for chatbots, chatclients, chatservers â And : âLevel: intermediate Possible mentor: Guillermo Polito Possible second mentor: (?) Description: Animation Library based on Athens Technical Details: Animation Library, to make visual animation objects in the screen, such as move, bounce , etc. Benefits to the Student: - Learn the basics of animations and moving objects. - Learn about manage of graphics - Understand the concepts of movement functions Benefits to the Community: - Get a library to make custom animations with the posibility of add new ones. â âRegards, Mariano On Wed, Mar 13, 2013 at 7:14 PM, Guillermo Polito <guillermopolito@gmail.com
wrote:
And another one:
Level: intermediate Possible mentor: Santiago Bragagnolo Possible second mentor: Guillermo Polito
Description: Gamification is becoming more and more popular in a lot of applications. What about gamify the pharo development process? You get points by adding comments, fixing bugs or answering questions. You can be a comment healer, a bug slayer, a Zinc magician. The intend of this project is to build an application that integrates with the Pharo development process tools (issue tracker, smalltalkhub, stack overflow) and provides a gamified experience, so we get more and more motivated to code.
Technical Details: This project implies the creation of an application which communicates with different applications APIs and perform some analysis on them such as running source code Lint rules. Additionally, this application should have a web frontend.
Benefits to the Student - Use a highly reflective dynamic language - Learn to develop a complex application architecture with several communicating components - Learn about ramification concepts - Learn about an open source project development and integration process, such as Pharo - Learn web application development techniques
Benefits to the Community - have a platform to organize activities and events around the Pharo development - be more motivated to participate into the development for rewards such as experience, badges and abilities
On Wed, Mar 13, 2013 at 4:40 PM, Guillermo Polito < guillermopolito@gmail.com> wrote:
Hi Janko!
We have this:
Level: intermediate Possible mentor: Guillermo Polito
Possible second mentor: Esteban Lorenzano
Description: DBXTalk database driver nowadays uses a native library called OpenDBX. This library stands as an adaptor between different database drivers, implemented in C. This native library supposes many problems: - it should be normally compiled for each different platform (Windows, *nix, macosx) and database vendor - each of its bugs should be fixed in a C source code base - OpenDBX do not expose the particular behavior of each database vendor, but their common denominator - difficulty for distribution, and problems to locate libraries. This project proposes to use NativeBoost bindings to remove the necessity of the native openDBX library, simplifying the deployment of applications using relational databases, and moving all the code base to Smalltalk.
Technical Details: This project supposes the replacement of openDBX old FFI bindings by direct nativeBoost bindings to the database drivers. The new drivers should be completely written in Smalltalk, and take care of platform and library resolution in the image side. These drivers should be polymorphic while also enabling the access to specific API provided by database vendors.
Benefits to the Student - Use a highly reflective dynamic language - Learn the basics of foreign function interface (and its exponent NativeBoost) - Learn how to manage external resources and platform specific native code - Put into usage its object design skills to transform a structured designed library into an object oriented one
Benefits to the Community - A more malleable and full smalltalk implementation of relational database drivers - Easier deploy for applications using relational databases - Database divers exposing their particular apis, providing access to features not available before
Guille
On Sat, Mar 9, 2013 at 2:16 PM, Janko Mivšek <janko.mivsek@eranova.si>wrote:
Hi Stef,
Post on the mailing list for each project idea by following this template:
Level: (beginner, intermediate, advanced)
Possible mentor:
Possible second mentor:
Description
Technical Details
Benefits to the Student
Benefits to the Community
Best regards Janko
Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
âHi, my name is Mariano,i'm a student at University of Quilmes. i have a experience in other programing languages like Scala, or Objective-c, and i like to participate in a real Smaltalk project. My background in this tecnology, is a little small, i never make a real project (I do in other tecnlogies) and i think the summer of code is a great oportunity for learn and practice. My ideas are: Level: intermediate Possible mentor: guillermo polito Possible second mentor: (?) Description: jabber client / server to communicate smaltalk with this common protocol. Technical Details: Create a jabber client api, to provide the capacity to connect with accouts like google talk, or facebook chat. Create a jabber api server, with the capacity of accept connection of diferent jabber clients. Benefits to the Student: - Learn ââ ââ â and understand â architecture ââ server/client - Learn about the protocol jabber. â â - Use a highly reflective dynamic languageâ Benefits to the Community: - Server and client for jabber protocol - Posible implementations for chatbots, chatclients, chatservers â And : âLevel: intermediate Possible mentor: Guillermo Polito Possible second mentor: (?) Description: Animation Library based on Athens Technical Details: Animation Library, to make visual animation objects in the screen, such as move, bounce , etc. Benefits to the Student: - Learn the basics of animations and moving objects. - Learn about manage of graphics - Understand the concepts of movement functions Benefits to the Community: - Get a library to make custom animations with the posibility of add new ones. âRegards, Mariano On Wed, Mar 13, 2013 at 7:14 PM, Guillermo Polito <guillermopolito@gmail.com
wrote:
And another one:
Level: intermediate Possible mentor: Santiago Bragagnolo Possible second mentor: Guillermo Polito
Description: Gamification is becoming more and more popular in a lot of applications. What about gamify the pharo development process? You get points by adding comments, fixing bugs or answering questions. You can be a comment healer, a bug slayer, a Zinc magician. The intend of this project is to build an application that integrates with the Pharo development process tools (issue tracker, smalltalkhub, stack overflow) and provides a gamified experience, so we get more and more motivated to code.
Technical Details: This project implies the creation of an application which communicates with different applications APIs and perform some analysis on them such as running source code Lint rules. Additionally, this application should have a web frontend.
Benefits to the Student - Use a highly reflective dynamic language - Learn to develop a complex application architecture with several communicating components - Learn about ramification concepts - Learn about an open source project development and integration process, such as Pharo - Learn web application development techniques
Benefits to the Community - have a platform to organize activities and events around the Pharo development - be more motivated to participate into the development for rewards such as experience, badges and abilities
On Wed, Mar 13, 2013 at 4:40 PM, Guillermo Polito < guillermopolito@gmail.com> wrote:
Hi Janko!
We have this:
Level: intermediate Possible mentor: Guillermo Polito
Possible second mentor: Esteban Lorenzano
Description: DBXTalk database driver nowadays uses a native library called OpenDBX. This library stands as an adaptor between different database drivers, implemented in C. This native library supposes many problems: - it should be normally compiled for each different platform (Windows, *nix, macosx) and database vendor - each of its bugs should be fixed in a C source code base - OpenDBX do not expose the particular behavior of each database vendor, but their common denominator - difficulty for distribution, and problems to locate libraries. This project proposes to use NativeBoost bindings to remove the necessity of the native openDBX library, simplifying the deployment of applications using relational databases, and moving all the code base to Smalltalk.
Technical Details: This project supposes the replacement of openDBX old FFI bindings by direct nativeBoost bindings to the database drivers. The new drivers should be completely written in Smalltalk, and take care of platform and library resolution in the image side. These drivers should be polymorphic while also enabling the access to specific API provided by database vendors.
Benefits to the Student - Use a highly reflective dynamic language - Learn the basics of foreign function interface (and its exponent NativeBoost) - Learn how to manage external resources and platform specific native code - Put into usage its object design skills to transform a structured designed library into an object oriented one
Benefits to the Community - A more malleable and full smalltalk implementation of relational database drivers - Easier deploy for applications using relational databases - Database divers exposing their particular apis, providing access to features not available before
Guille
On Sat, Mar 9, 2013 at 2:16 PM, Janko Mivšek <janko.mivsek@eranova.si>wrote:
Hi Stef,
Post on the mailing list for each project idea by following this template:
Level: (beginner, intermediate, advanced)
Possible mentor:
Possible second mentor:
Description
Technical Details
Benefits to the Student
Benefits to the Community
Best regards Janko
Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
Hola tocayo! Maybe you can find this interesting: http://www.squeaksource.com/Jabber/ Best, On Thu, Mar 21, 2013 at 2:41 PM, Mariano Vicente <m.vicent@gmail.com> wrote:
âHi, my name is Mariano,i'm a student at University of Quilmes. i have a experience in other programing languages like Scala, or Objective-c, and i like to participate in a real Smaltalk project. My background in this tecnology, is a little small, i never make a real project (I do in other tecnlogies) and i think the summer of code is a great oportunity for learn and practice.
My ideas are:
Level: intermediate Possible mentor: guillermo polito Possible second mentor: (?) Description: jabber client / server to communicate smaltalk with this common protocol. Technical Details: Create a jabber client api, to provide the capacity to connect with accouts like google talk, or facebook chat. Create a jabber api server, with the capacity of accept connection of diferent jabber clients. Benefits to the Student: - Learn ââ ââ â and understand â architecture ââ server/client - Learn about the protocol jabber.
â â - Use a highly reflective dynamic languageâ
Benefits to the Community: - Server and client for jabber protocol - Posible implementations for chatbots, chatclients, chatservers â
And :
âLevel: intermediate Possible mentor: Guillermo Polito Possible second mentor: (?) Description: Animation Library based on Athens Technical Details: Animation Library, to make visual animation objects in the screen, such as move, bounce , etc. Benefits to the Student: - Learn the basics of animations and moving objects. - Learn about manage of graphics - Understand the concepts of movement functions
Benefits to the Community: - Get a library to make custom animations with the posibility of add new ones.
â
âRegards, Mariano
On Wed, Mar 13, 2013 at 7:14 PM, Guillermo Polito < guillermopolito@gmail.com> wrote:
And another one:
Level: intermediate Possible mentor: Santiago Bragagnolo Possible second mentor: Guillermo Polito
Description: Gamification is becoming more and more popular in a lot of applications. What about gamify the pharo development process? You get points by adding comments, fixing bugs or answering questions. You can be a comment healer, a bug slayer, a Zinc magician. The intend of this project is to build an application that integrates with the Pharo development process tools (issue tracker, smalltalkhub, stack overflow) and provides a gamified experience, so we get more and more motivated to code.
Technical Details: This project implies the creation of an application which communicates with different applications APIs and perform some analysis on them such as running source code Lint rules. Additionally, this application should have a web frontend.
Benefits to the Student - Use a highly reflective dynamic language - Learn to develop a complex application architecture with several communicating components - Learn about ramification concepts - Learn about an open source project development and integration process, such as Pharo - Learn web application development techniques
Benefits to the Community - have a platform to organize activities and events around the Pharo development - be more motivated to participate into the development for rewards such as experience, badges and abilities
On Wed, Mar 13, 2013 at 4:40 PM, Guillermo Polito < guillermopolito@gmail.com> wrote:
Hi Janko!
We have this:
Level: intermediate Possible mentor: Guillermo Polito
Possible second mentor: Esteban Lorenzano
Description: DBXTalk database driver nowadays uses a native library called OpenDBX. This library stands as an adaptor between different database drivers, implemented in C. This native library supposes many problems: - it should be normally compiled for each different platform (Windows, *nix, macosx) and database vendor - each of its bugs should be fixed in a C source code base - OpenDBX do not expose the particular behavior of each database vendor, but their common denominator - difficulty for distribution, and problems to locate libraries. This project proposes to use NativeBoost bindings to remove the necessity of the native openDBX library, simplifying the deployment of applications using relational databases, and moving all the code base to Smalltalk.
Technical Details: This project supposes the replacement of openDBX old FFI bindings by direct nativeBoost bindings to the database drivers. The new drivers should be completely written in Smalltalk, and take care of platform and library resolution in the image side. These drivers should be polymorphic while also enabling the access to specific API provided by database vendors.
Benefits to the Student - Use a highly reflective dynamic language - Learn the basics of foreign function interface (and its exponent NativeBoost) - Learn how to manage external resources and platform specific native code - Put into usage its object design skills to transform a structured designed library into an object oriented one
Benefits to the Community - A more malleable and full smalltalk implementation of relational database drivers - Easier deploy for applications using relational databases - Database divers exposing their particular apis, providing access to features not available before
Guille
On Sat, Mar 9, 2013 at 2:16 PM, Janko Mivšek <janko.mivsek@eranova.si>wrote:
Hi Stef,
Post on the mailing list for each project idea by following this template:
Level: (beginner, intermediate, advanced)
Possible mentor:
Possible second mentor:
Description
Technical Details
Benefits to the Student
Benefits to the Community
Best regards Janko
Dne 09. 03. 2013 13:46, piše stephane ducasse:
Hi janko
How do you want to proceed for the topics? I have a list of topics now where do we write them.
- tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets
Stef
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Mariano http://marianopeck.wordpress.com
Dear all, I would like to propose something related to SciSmalltalk: https://github.com/SergeStinckwich/SciSmalltalk This is really important if we want Smalltalk to be accepted in the scientific community. I want to submit a project that will only focus on ODE (Ordinary Differential Equation) solving. Some preliminary works has already be done in this direction. I would like to know if a GSOC student could be hosted in a lab ? Regards, On Sat, Mar 9, 2013 at 1:03 PM, Janko Mivšek <janko.mivsek@eranova.si> wrote:
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://doesnotunderstand.org/
Hi Serge, I also think SciSmalltalk project is important for us so please put it into a our GSoC idea template, then I'll put it on the ideas page. Best regards Janko Dne 10. 03. 2013 15:44, piše Serge Stinckwich:
Dear all,
I would like to propose something related to SciSmalltalk: https://github.com/SergeStinckwich/SciSmalltalk This is really important if we want Smalltalk to be accepted in the scientific community. I want to submit a project that will only focus on ODE (Ordinary Differential Equation) solving. Some preliminary works has already be done in this direction.
I would like to know if a GSOC student could be hosted in a lab ?
Regards,
On Sat, Mar 9, 2013 at 1:03 PM, Janko Mivšek <janko.mivsek@eranova.si> wrote:
Dear Smalltalkers,
Time for your cool project ideas on this year Smalltalk GSoC!
For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas.
Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully!
For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc.
We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects.
More on our special Smalltalk GSoC 2013 website:
I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC:
http://groups.google.com/group/smalltalk-gsoc-mentors
While students interested on GSoC please join a special Smalltalk GSoC mailing list for you:
http://groups.google.com/group/smalltalk-gsoc-students
Best regards Janko
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://doesnotunderstand.org/
-- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
Hi Janko, Here is another project proposition. Programming tools for Pharo based on Type Inference Level: intermediate/advanced Possible mentor: Camille Teruel Possible second mentor: Stéphane Ducasse Description: Type inference mechanisms can be used to compute the types of variables from the source code. This information is very interesting in the context of a dynamically-typed language like Smalltalk. Several type inference tools already exists for Smalltalk but the type information they bring has not revealed all its potential yet. The student will have to leverage this type information with new programming tools. Example of such tools are: Code analysis tools: better "implementors of" and "senders of" lists dead code finder Development tools: type mismatch hints at compile time better code completion Technical details: The student will have to analyze existing type inference tools and choose an appropriate solution. Then he will have to learn how to build UIs with Spec. Benefits for the Pharo community New useful development tools Improvement of existing code base thank to these tools Benefits for the student Use a highly reflective dynamic language Learn the basics of type inference Learn how to make UIs with Spec Have an impact on the code base of a large project
I like this project proposal. A little addition would be to add type inference for code written in the inspector where we already have concrete types that we could leverage for development tools. Would you consider that? Cheers, Doru On Tue, Mar 26, 2013 at 10:51 AM, Camille Teruel <camille.teruel@gmail.com>wrote:
Hi Janko,
Here is another project proposition. Programming tools for Pharo based on Type Inference
Level: intermediate/advanced
Possible mentor: Camille Teruel Possible second mentor: Stéphane Ducasse
Description: Type inference mechanisms can be used to compute the types of variables from the source code. This information is very interesting in the context of a dynamically-typed language like Smalltalk. Several type inference tools already exists for Smalltalk but the type information they bring has not revealed all its potential yet. The student will have to leverage this type information with new programming tools.
Example of such tools are:
- Code analysis tools: - better "implementors of" and "senders of" lists - dead code finder - Development tools: - type mismatch hints at compile time - better code completion
Technical details: The student will have to analyze existing type inference tools and choose an appropriate solution. Then he will have to learn how to build UIs with Spec.
Benefits for the Pharo community
- New useful development tools - Improvement of existing code base thank to these tools
Benefits for the student
- Use a highly reflective dynamic language - Learn the basics of type inference - Learn how to make UIs with Spec - Have an impact on the code base of a large project
-- www.tudorgirba.com "Every thing has its own flow"
yes for example. Stef On Mar 26, 2013, at 11:02 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
I like this project proposal. A little addition would be to add type inference for code written in the inspector where we already have concrete types that we could leverage for development tools. Would you consider that?
Cheers, Doru
On Tue, Mar 26, 2013 at 10:51 AM, Camille Teruel <camille.teruel@gmail.com> wrote: Hi Janko,
Here is another project proposition. Programming tools for Pharo based on Type Inference
Level: intermediate/advanced
Possible mentor: Camille Teruel Possible second mentor: Stéphane Ducasse
Description: Type inference mechanisms can be used to compute the types of variables from the source code. This information is very interesting in the context of a dynamically-typed language like Smalltalk. Several type inference tools already exists for Smalltalk but the type information they bring has not revealed all its potential yet. The student will have to leverage this type information with new programming tools.
Example of such tools are:
Code analysis tools: better "implementors of" and "senders of" lists dead code finder Development tools: type mismatch hints at compile time better code completion Technical details:
The student will have to analyze existing type inference tools and choose an appropriate solution. Then he will have to learn how to build UIs with Spec. Benefits for the Pharo community
New useful development tools Improvement of existing code base thank to these tools Benefits for the student
Use a highly reflective dynamic language Learn the basics of type inference Learn how to make UIs with Spec Have an impact on the code base of a large project
-- www.tudorgirba.com
"Every thing has its own flow"
On 26 mars 2013, at 11:02, Tudor Girba wrote:
I like this project proposal. A little addition would be to add type inference for code written in the inspector where we already have concrete types that we could leverage for development tools. Would you consider that?
Do you mean that type information could be gathered on object inspection? If so it's a cool idea and the same thing could be done with a debugger. I just didn't want to force the student to develop new type inference mechanisms because some solutions already exist in Pharo. The project is more about making cool tools that use type information provided by an existing solution. Doing both tasks would be too much work for one student. However, if the existing solutions don't fit the tool the student wants to develop he is still free to improve them.
Cheers, Doru
On Tue, Mar 26, 2013 at 10:51 AM, Camille Teruel <camille.teruel@gmail.com> wrote: Hi Janko,
Here is another project proposition. Programming tools for Pharo based on Type Inference
Level: intermediate/advanced
Possible mentor: Camille Teruel Possible second mentor: Stéphane Ducasse
Description: Type inference mechanisms can be used to compute the types of variables from the source code. This information is very interesting in the context of a dynamically-typed language like Smalltalk. Several type inference tools already exists for Smalltalk but the type information they bring has not revealed all its potential yet. The student will have to leverage this type information with new programming tools.
Example of such tools are:
Code analysis tools: better "implementors of" and "senders of" lists dead code finder Development tools: type mismatch hints at compile time better code completion Technical details:
The student will have to analyze existing type inference tools and choose an appropriate solution. Then he will have to learn how to build UIs with Spec. Benefits for the Pharo community
New useful development tools Improvement of existing code base thank to these tools Benefits for the student
Use a highly reflective dynamic language Learn the basics of type inference Learn how to make UIs with Spec Have an impact on the code base of a large project
-- www.tudorgirba.com
"Every thing has its own flow"
On 26 March 2013 10:51, Camille Teruel <camille.teruel@gmail.com> wrote:
On 26 mars 2013, at 11:02, Tudor Girba wrote:
I like this project proposal. A little addition would be to add type inference for code written in the inspector where we already have concrete types that we could leverage for development tools. Would you consider that?
Do you mean that type information could be gathered on object inspection? If so it's a cool idea and the same thing could be done with a debugger.
As an example, since you know the actual type of all variables and method arguments, you can use that information when writing code in the debugger: you've just written a message send to some variable but that that variable's class doesn't understand that message, for instance. (This should be a warning, not an error.)
I just didn't want to force the student to develop new type inference mechanisms because some solutions already exist in Pharo. The project is more about making cool tools that use type information provided by an existing solution.
That includes both Francisco Garau's and Santiago Bragagnolo's work on Concrete Type Inference, Roel Wuyt's RoelTyper and my own tiny inference engine in SqueakCheck (http://www.squeaksource.com/SqueakCheck/ and its ConfigurationOf might well need fixing for Pharo). frank
Doing both tasks would be too much work for one student. However, if the existing solutions don't fit the tool the student wants to develop he is still free to improve them.
Cheers, Doru
On Tue, Mar 26, 2013 at 10:51 AM, Camille Teruel <camille.teruel@gmail.com> wrote:
Hi Janko,
Here is another project proposition.
Programming tools for Pharo based on Type Inference
Level: intermediate/advanced
Possible mentor: Camille Teruel Possible second mentor: Stéphane Ducasse
Description: Type inference mechanisms can be used to compute the types of variables from the source code. This information is very interesting in the context of a dynamically-typed language like Smalltalk. Several type inference tools already exists for Smalltalk but the type information they bring has not revealed all its potential yet. The student will have to leverage this type information with new programming tools.
Example of such tools are:
Code analysis tools:
better "implementors of" and "senders of" lists dead code finder
Development tools:
type mismatch hints at compile time better code completion
Technical details:
The student will have to analyze existing type inference tools and choose an appropriate solution. Then he will have to learn how to build UIs with Spec.
Benefits for the Pharo community
New useful development tools Improvement of existing code base thank to these tools
Benefits for the student
Use a highly reflective dynamic language Learn the basics of type inference Learn how to make UIs with Spec Have an impact on the code base of a large project
-- www.tudorgirba.com
"Every thing has its own flow"
On 26 mars 2013, at 12:05, Frank Shearar wrote:
On 26 March 2013 10:51, Camille Teruel <camille.teruel@gmail.com> wrote:
On 26 mars 2013, at 11:02, Tudor Girba wrote:
I like this project proposal. A little addition would be to add type inference for code written in the inspector where we already have concrete types that we could leverage for development tools. Would you consider that?
Do you mean that type information could be gathered on object inspection? If so it's a cool idea and the same thing could be done with a debugger.
As an example, since you know the actual type of all variables and method arguments, you can use that information when writing code in the debugger: you've just written a message send to some variable but that that variable's class doesn't understand that message, for instance. (This should be a warning, not an error.)
I just didn't want to force the student to develop new type inference mechanisms because some solutions already exist in Pharo. The project is more about making cool tools that use type information provided by an existing solution.
That includes both Francisco Garau's and Santiago Bragagnolo's work on Concrete Type Inference, Roel Wuyt's RoelTyper and my own tiny inference engine in SqueakCheck (http://www.squeaksource.com/SqueakCheck/ and its ConfigurationOf might well need fixing for Pharo).
Thanks Frank, I wasn't aware of your engine, I will have a look on it.
frank
Doing both tasks would be too much work for one student. However, if the existing solutions don't fit the tool the student wants to develop he is still free to improve them.
Cheers, Doru
On Tue, Mar 26, 2013 at 10:51 AM, Camille Teruel <camille.teruel@gmail.com> wrote:
Hi Janko,
Here is another project proposition.
Programming tools for Pharo based on Type Inference
Level: intermediate/advanced
Possible mentor: Camille Teruel Possible second mentor: Stéphane Ducasse
Description: Type inference mechanisms can be used to compute the types of variables from the source code. This information is very interesting in the context of a dynamically-typed language like Smalltalk. Several type inference tools already exists for Smalltalk but the type information they bring has not revealed all its potential yet. The student will have to leverage this type information with new programming tools.
Example of such tools are:
Code analysis tools:
better "implementors of" and "senders of" lists dead code finder
Development tools:
type mismatch hints at compile time better code completion
Technical details:
The student will have to analyze existing type inference tools and choose an appropriate solution. Then he will have to learn how to build UIs with Spec.
Benefits for the Pharo community
New useful development tools Improvement of existing code base thank to these tools
Benefits for the student
Use a highly reflective dynamic language Learn the basics of type inference Learn how to make UIs with Spec Have an impact on the code base of a large project
-- www.tudorgirba.com
"Every thing has its own flow"
On 26 March 2013 11:11, Camille Teruel <camille.teruel@gmail.com> wrote:
On 26 mars 2013, at 12:05, Frank Shearar wrote:
On 26 March 2013 10:51, Camille Teruel <camille.teruel@gmail.com> wrote:
On 26 mars 2013, at 11:02, Tudor Girba wrote:
I like this project proposal. A little addition would be to add type inference for code written in the inspector where we already have concrete types that we could leverage for development tools. Would you consider that?
Do you mean that type information could be gathered on object inspection? If so it's a cool idea and the same thing could be done with a debugger.
As an example, since you know the actual type of all variables and method arguments, you can use that information when writing code in the debugger: you've just written a message send to some variable but that that variable's class doesn't understand that message, for instance. (This should be a warning, not an error.)
I just didn't want to force the student to develop new type inference mechanisms because some solutions already exist in Pharo. The project is more about making cool tools that use type information provided by an existing solution.
That includes both Francisco Garau's and Santiago Bragagnolo's work on Concrete Type Inference, Roel Wuyt's RoelTyper and my own tiny inference engine in SqueakCheck (http://www.squeaksource.com/SqueakCheck/ and its ConfigurationOf might well need fixing for Pharo).
Thanks Frank, I wasn't aware of your engine, I will have a look on it.
It's absolutely teeny: the summary of the project is that I add a TheoryTestCase, which runs the usual test* methods, and also finds methods marked with a <theory> pragma. A theory is a parameterised unit test, allowing you to throw randomly generated data at your theory. For instance you might check for right identity for #+: rightIdentity: x <theory> self assert: x class zero + x equals: x + x class zero and the engine (TheoryTyper) will see that you've sent #+ to x, and #zero to the class of x. It will look over the image to see what classes understand that mini protocol, and call the appropriate generator to throw data at the test. In this example, it'll generate Integers, Floats and ScaledDecimals. frank
frank
Doing both tasks would be too much work for one student. However, if the existing solutions don't fit the tool the student wants to develop he is still free to improve them.
Cheers, Doru
On Tue, Mar 26, 2013 at 10:51 AM, Camille Teruel <camille.teruel@gmail.com> wrote:
Hi Janko,
Here is another project proposition.
Programming tools for Pharo based on Type Inference
Level: intermediate/advanced
Possible mentor: Camille Teruel Possible second mentor: Stéphane Ducasse
Description: Type inference mechanisms can be used to compute the types of variables from the source code. This information is very interesting in the context of a dynamically-typed language like Smalltalk. Several type inference tools already exists for Smalltalk but the type information they bring has not revealed all its potential yet. The student will have to leverage this type information with new programming tools.
Example of such tools are:
Code analysis tools:
better "implementors of" and "senders of" lists dead code finder
Development tools:
type mismatch hints at compile time better code completion
Technical details:
The student will have to analyze existing type inference tools and choose an appropriate solution. Then he will have to learn how to build UIs with Spec.
Benefits for the Pharo community
New useful development tools Improvement of existing code base thank to these tools
Benefits for the student
Use a highly reflective dynamic language Learn the basics of type inference Learn how to make UIs with Spec Have an impact on the code base of a large project
-- www.tudorgirba.com
"Every thing has its own flow"
On Mar 26, 2013, at 12:05 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
That includes both Francisco Garau's and Santiago Bragagnolo's work on Concrete Type Inference,
yes we should build on top of them. I wish francisco would like to continue pushing his master with us but he is busy with banks :)
Roel Wuyt's RoelTyper and my own tiny inference engine in SqueakCheck (http://www.squeaksource.com/SqueakCheck/ and its ConfigurationOf might well need fixing for Pharo).
frank
Yeah, I wish I could push that a bit further... I've recently found a similar type of work for Python. Google for "Starkiller, Salib", if you are interested. - Francisco On 26 Mar 2013, at 11:17, stephane ducasse <stephane.ducasse@free.fr> wrote:
On Mar 26, 2013, at 12:05 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
That includes both Francisco Garau's and Santiago Bragagnolo's work on Concrete Type Inference,
yes we should build on top of them. I wish francisco would like to continue pushing his master with us but he is busy with banks :)
Roel Wuyt's RoelTyper and my own tiny inference engine in SqueakCheck (http://www.squeaksource.com/SqueakCheck/ and its ConfigurationOf might well need fixing for Pharo).
frank
Camille excellent idea!!! Stef On Mar 26, 2013, at 10:51 AM, Camille Teruel <camille.teruel@gmail.com> wrote:
Hi Janko,
Here is another project proposition. Programming tools for Pharo based on Type Inference
Level: intermediate/advanced
Possible mentor: Camille Teruel Possible second mentor: Stéphane Ducasse
Description: Type inference mechanisms can be used to compute the types of variables from the source code. This information is very interesting in the context of a dynamically-typed language like Smalltalk. Several type inference tools already exists for Smalltalk but the type information they bring has not revealed all its potential yet. The student will have to leverage this type information with new programming tools.
Example of such tools are:
Code analysis tools: better "implementors of" and "senders of" lists dead code finder Development tools: type mismatch hints at compile time better code completion Technical details:
The student will have to analyze existing type inference tools and choose an appropriate solution. Then he will have to learn how to build UIs with Spec. Benefits for the Pharo community
New useful development tools Improvement of existing code base thank to these tools Benefits for the student
Use a highly reflective dynamic language Learn the basics of type inference Learn how to make UIs with Spec Have an impact on the code base of a large project
participants (11)
-
Camille Teruel -
Francisco Garau -
Frank Shearar -
Guillermo Polito -
Janko Mivšek -
Mariano Martinez Peck -
Mariano Vicente -
Serge Stinckwich -
stephane ducasse -
Stéphane Ducasse -
Tudor Girba