thicky-developers Mailing List for Thicky
Brought to you by:
paul-h
Menu
▾
▴
thicky-developers — Thicky Developers
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: <ben...@id...> - 2004-05-25 09:52:11
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: <Joe...@El...> - 2004-04-27 13:49:30
|
Hi Paul, the sample from the website does not run, the groovy scripts are not = found/available anymore. Regards, J=F6rg |
|
From: Paul H. <pa...@ha...> - 2004-04-22 08:56:15
|
Lads, I've changed the back button processing for Thicky. This after a conversati= on with Alan Francis as the airport on Friday. One thing I hate about the web is the back button. If you've done InBox ..= ViewMail .. Inbox .. ViewMail .. InBox (as links all in a hypothetical web= mail app), then hit prev a few times you ar eall over the place. It is wors= e when a post was involved. Tis hard for us as IT professions to understand= let alone anyone's gran. Thicky now operates a stack concept. Some pages are marked (they mark them= selves) as BackPoints (like checkpoint). If you hit the back button many pa= ges will be popped until you get to that back point. If you hit Previous (= yes it still exists), only a single page will be popped. A page may late m= ark itself as a backpoint (or unmark itself). Seems to work well. Try it out. Related to this, it is possible that the previous button should dissapear f= rom the nav bar leaving only the back button. The point is that a page dev= eloper may make breadcrumbs that would invoke back() or prev(). Regards, - Paul |
|
From: Maksim L. <ma...@fa...> - 2004-04-21 20:32:47
|
Hi, I recently found out about thicky and it looks like an interesting approach, but it seems like quite 'heavy weight'. I was wondering if anyone on the list could compare it to the direction I'm taking which is to add javascript (mozilla rhino) to thinlets (www.thinlet.com) and so allow xml & javascript to be streamed at runtime by applets running on any browser with java1.1 support. My reasons for going in this direction is that thinlet is tiny (~40kb jar), lots of people know javascript already and I can use the same script language as I do in my webpages. I dont mean this to be a troll or anything, as I am genuinely interested to hear peoples opinions on the difference between the approaches and for instance possible mixing off the 2, like what would be any benefits of me switching to using groovy instead of javascript for my scripting engine? thanks, Maks. |
|
From: Maksim L. <ma...@fa...> - 2004-04-21 08:34:16
|
Hi, I recently found out about thicky and it looks like an interesting approach, but it seems like quite 'heavy weight'. I was wondering if anyone on the list could compare it to the direction I'm taking which is to add javascript (mozilla rhino) to thinlets (www.thinlet.com) and so allow xml & javascript to be streamed at runtime by applets running on any browser with java1.1 support. My reasons for going in this direction is that thinlet is tiny (~40kb jar), lots of people know javascript already and I can use the same script language as I do in my webpages. I dont mean this to be a troll or anything, as I am genuinely interested to hear peoples opinions on the difference between the approaches and for instance possible mixing off the 2, like what would be any benefits of me switching to using groovy instead of javascript for my scripting engine? thanks, Maks. |
|
From: Rob L. <ro...@ju...> - 2004-04-06 12:10:54
|
Hi, I met Paul a couple of weeks ago and he suggested I take a look at Thicky. Well I have and it seems like it has potential. A couple of ideas/questions popped into my head at first glance. 1) Is there an intention to couple it to a standard java servlet solution, passing data back via the magic of http or is an RMI/RPC/Web Services architecture < ooh the a word > imagined. We haven't decided or don't plan to impose one is a perfectly valid response. 2) From reading the groovy mailing list there seems to be two very different trains of thought going on there. One camp wants a scripting language that has good tool support for things like refactoring tools. The other group wants to use macros, dynamic parser extensions and NodeBulder like markup. To me these goals are mutually exclusive. My gut feel is that the first group will win out, the rigours of the JCP process will make a more strictly defined language the only viable choice. With this in mind I'd expect to see the SwingBuilder stuff go at some point. Is it wise to start off using it? Beyond that, and this is purely personal bia, I find it off-putting and confusing. Is it markup, is a programming language...it's neither. Or both. I think that web designers will view it as strange and complex and java developers will sneer at is as being sort of like that crappy html/javascript combination they loathe. To write this stuff you have to know java, swing, groovy and understand how SwingBuilders see the world. That's quite a lot to get buy in on. The target audience on day one is java developers, handcrafting the swing code will make it more accesible. If people want, and if it survives, they can use SwingBuilder. Just not sure it should be the first thing people come across. 3) Does it have to have the name Thicky. I find getting any sort of managment buy in to use technoligies with novely names 10 times harder. "I want to use Groovy and Thicky on this project", sound like an attempt to recruit Snow Whites friends. Not a phrase I want to utter. Ken Schwaber says he regrets the name SCRUM because it makes it much harder to take it seriously. $) Where are all the tests man ....? Rob Lally |
|
From: Ben W. <be...@wa...> - 2004-04-04 11:22:55
|
I was just taking a look at the cvs release of thicky and had a few questions. 1) Where can I get the jar for the mozilla pluglets? (I can upload it to ibiblio as soon as I get it. It will need to be added as a dependency to the project.xml as well). It looks incredibly painful to build... 2) Why the coupling to mozilla pluglets? (as opposed to using java web start delivery of the app) Cheers, Ben |
