Re: [Pharo-users] GSOC 2015 application
Some project ideas 1 Better support for cross-platform co-development Glorp is originally maintained in VisualWorks. We now have a version in Pharo that is forked. It would be nice if we could make sure that changes can be synchronized. The rewriting engine is available on both platforms, and Glorp has a large number of unit tests. If we can describe both migrations with refactorings, we should be able to create builds in ci for both that show when changes break things and otherwise synchronize two-way. This might also be beneficial for Roassal2 and Seaside, that currently use a compatibility layer. Another place where this rewriting can be useful would be in maintaining compatibility between Squeak and Pharo, and in making it easier keeping older code alive. Marcel Taeumel has written a number of interesting applications (UIBuilder, Widgets, XPForums) using a 'signals' style communication. In Pharo it would make sense to have them use Announcements. 2 Use code rewriting to help migrate projects forwards In https://pharo.fogbugz.com/default.asp?13754 cleaning strings API there are 3 method renames. These were included in build 40165. Projects source for pharo can be found on a number of repositories (smaltalkhub, squeaksource, ss3, etc). Upgrade scripts can be generated for these projects to help do these migrations. Stephan
+1 Can I brainstorm a wishlist? I could get wild on it :D
On Feb 11, 2015, at 9:19 AM, Stephan Eggermont <stephan@stack.nl> wrote:
Some project ideas
1 Better support for cross-platform co-development
Glorp is originally maintained in VisualWorks. We now have a version in Pharo that is forked. It would be nice if we could make sure that changes can be synchronized. The rewriting engine is available on both platforms, and Glorp has a large number of unit tests. If we can describe both migrations with refactorings, we should be able to create builds in ci for both that show when changes break things and otherwise synchronize two-way.
This might also be beneficial for Roassal2 and Seaside, that currently use a compatibility layer.
Another place where this rewriting can be useful would be in maintaining compatibility between Squeak and Pharo, and in making it easier keeping older code alive.
Marcel Taeumel has written a number of interesting applications (UIBuilder, Widgets, XPForums) using a 'signals' style communication. In Pharo it would make sense to have them use Announcements.
2 Use code rewriting to help migrate projects forwards
In https://pharo.fogbugz.com/default.asp?13754 cleaning strings API there are 3 method renames. These were included in build 40165. Projects source for pharo can be found on a number of repositories (smaltalkhub, squeaksource, ss3, etc). Upgrade scripts can be generated for these projects to help do these migrations.
Stephan
On Wed, Feb 11, 2015 at 8:51 PM, Sebastian Sastre < sebastian@flowingconcept.com> wrote:
+1
Can I brainstorm a wishlist? I could get wild on it :D
Yes. Go wild! But it should be achievable in 12 weeks, in some cases by students with limited Pharo/Smalltalk experience. Anyway, a wild brainstorm list could carry over to a longer term ex-GSoC list. However there is only 8 or 9 days before the organisation application is due, and the ideas should come with some flesh. ( http://en.flossmanuals.net/GSoCMentoring/making-your-ideas-page/) cheers -ben
participants (3)
-
Ben Coman -
Sebastian Sastre -
Stephan Eggermont