jspro-devel Mailing List for jsPro
Brought to you by:
wigleys
Menu
▾
▴
jspro-devel — This is the mailing list for discussing jsPro development
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(14) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ben...@id...> - 2004-05-25 07:45:52
|
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: Randolph T. F. <gat...@ci...> - 2003-09-24 04:47:01
|
Hey Stuart - Here are my thoughts on what you mentioned below: (1) The Debug window - I totally agree with you that the Debug window is = a great addition to the toolset and a nice way to watch for errors. So, I obviously think it should remain. Having said that, I also know that it = has a few big design flaws that need to be rearchitected. I say we just = leave it as is for now. I know what needs to be fixed to make it much more system-friendly from a design standpoint, but I would like to take a = little more time to make sure that we both agree on a design path for it and = then attack the task with that plan. My suggestion is that we get back to = this topic when I get back from my honeymoon. If I forget, don't forget to remind me. (2) API docs - I am glad you went and took a look at jsDoc. It is much better than us starting from scratch, and we should be able to modify it = for our specific purposes (certain tags we use, etc.) if they decide not to incorporate everything we need. Overall, it's nice to know that we = should be able to generate some very good documentation soon. (3) New methods - The only methods that I particularly had planned were = some browser-sniffing routines for the Browser class that I began work on. Anything else besides that is fair game, so get to it! ;-) (4) Breaking up Math and Array - Although I completely agree that Array = and Math should be broken up, I think it would be good to keep the classes "whole" for at least one or two more releases due to the rapid = development schedule and upgrade cycle we have put in place. This would give us = time to better plan out what we want to do to accomplish this, since we could account for methods that we plan to build in as well as the ones we = have. (5) Website - I have finally begun work on our website. This is where I will be spending the majority of my time on jsPro for the near future, = along with my other task...(see below). However, I will be leaving for my honeymoon soon, so I won't be around for 2+ weeks starting a week from = this Sunday. So, you could take over while I am gone or just wait until I = get back to finish it up. All in all, I hope to have something simple completed. (6) QA - Honestly, Stuart, I really enjoy doing the QA stuff. I think I = am good at it, and it makes me feel like I am making a good contribution to = our code base given that most of the ideas are coming from you. Once I have = the time (post-wedding) to be able to commit more time to jsPro, I plan to = do some new development for jsPro myself, but up until now, I felt that = this was the best way for me to add value to the project. So, don't really = worry if your code is not perfect or close to it (no offense! :-) the first = time out of the gate, since your initial development tasks are what is making jsPro more awesome of a library of tools all the time. If you keep developing the new things to push the toolset forward, I am more than = happy to come behind to ensure consistency, clarity, etc. All in all, I think this separation of tasks is what is really making us quite a powerful development team for two people (almost like extreme programming, except = we aren't sitting at the same computer! :-) Cheers, Randy -----Original Message----- From: jsp...@li... [mailto:jsp...@li...] On Behalf Of Stuart = Wigley Sent: Monday, September 22, 2003 7:50 AM To: jsp...@li... Subject: [Jspro-devel] Aims for Release 3 Hi Randy, There are a few things i'd like to clear up for release 3, and I'd like to know thoughts on how achievable they are: 1. The Debug window: how can we improve it? should we just dump it? Do its benefits exceed the flaws that it has? I do find it quite useful during debugging but it could be something that we keep in cvs but don't package into releases? Alternatively we could just leave it for now and plan a longer term development of it so that it becomes a more useful development utility. 2. API docs: i've raised a support request with the jsDoc guys because you can't currently generate docs against our String, Array etc libraries (as they don't have a Class definition). I think we should hold off on generating API docs until we can create a full set. 3. New methods: I've got about a thousand new methods I want to add in (:-) and as you've probably noticed my approach is haphazard - is there in particular you have planned? 4. Breaking up Math and Array: I want to split a lot of the methods here out into new classes but I'm not sure this is a job for R3. Maybe we should wait until we have a few more methods available. 5. Website: if you are struggling with time commitments i might just put something simple up to prove that we exist...ok with you? 6. QA: thanks for what you've been doing. I really need to spend more time checking my code. Maybe we should write a developers guide and QA checklist? Anything else? I hope all is well at your end Cheers Stuart ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jspro-devel mailing list Jsp...@li... https://lists.sourceforge.net/lists/listinfo/jspro-devel |
|
From: <stu...@ya...> - 2003-09-22 11:50:17
|
Hi Randy, There are a few things i'd like to clear up for release 3, and I'd like to know thoughts on how achievable they are: 1. The Debug window: how can we improve it? should we just dump it? Do its benefits exceed the flaws that it has? I do find it quite useful during debugging but it could be something that we keep in cvs but don't package into releases? Alternatively we could just leave it for now and plan a longer term development of it so that it becomes a more useful development utility. 2. API docs: i've raised a support request with the jsDoc guys because you can't currently generate docs against our String, Array etc libraries (as they don't have a Class definition). I think we should hold off on generating API docs until we can create a full set. 3. New methods: I've got about a thousand new methods I want to add in (:-) and as you've probably noticed my approach is haphazard - is there in particular you have planned? 4. Breaking up Math and Array: I want to split a lot of the methods here out into new classes but I'm not sure this is a job for R3. Maybe we should wait until we have a few more methods available. 5. Website: if you are struggling with time commitments i might just put something simple up to prove that we exist...ok with you? 6. QA: thanks for what you've been doing. I really need to spend more time checking my code. Maybe we should write a developers guide and QA checklist? Anything else? I hope all is well at your end Cheers Stuart ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk |
|
From: Randolph T. F. <gat...@ci...> - 2003-09-14 07:20:55
|
Stuart - This sounds great to me, since I am all for automatically doing = anything. I mean, that's what we programmers are for! However, before you get too carried away, and since you know how to script in Perl, why don't you = take a look at this: http://jsdoc.sourceforge.net It may not do exactly what we want, and (having reviewed it a bit) I = don't think it follows the JavaDoc standard as much as we have. But, this = could be just the thing we needed. Since it is an open source project, we = could take the scripts and modify them freely to fit our needs, as long as we relay the good news to the development team. What do you think, = partner? Cheers, Randy -----Original Message----- From: jsp...@li... [mailto:jsp...@li...] On Behalf Of Stuart = Wigley Sent: Thursday, September 11, 2003 8:37 AM To: jsp...@li... Subject: [Jspro-devel] New @summary commenting tag Hi Randy, I've been playing around with writing a Perl script to generate the README file - i guess you could consider it the first step in a javascript comments parser, and also I'm too lazy to keep updating the README file manually :-) Anyway, during this process I thought it would be useful to invent a @summary comment for holding a very brief summary of the method - ie one or two words. Does this sound ok to you? I'll check the perl script in soon - at the moment its messy as hell and isn't complete. Cheers Stuart ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jspro-devel mailing list Jsp...@li... https://lists.sourceforge.net/lists/listinfo/jspro-devel |
|
From: <stu...@ya...> - 2003-09-11 12:36:45
|
Hi Randy, I've been playing around with writing a Perl script to generate the README file - i guess you could consider it the first step in a javascript comments parser, and also I'm too lazy to keep updating the README file manually :-) Anyway, during this process I thought it would be useful to invent a @summary comment for holding a very brief summary of the method - ie one or two words. Does this sound ok to you? I'll check the perl script in soon - at the moment its messy as hell and isn't complete. Cheers Stuart ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk |
|
From: <stu...@ya...> - 2003-09-05 10:04:51
|
Hi Randy, The mailing list is created and should take effect the next time we check something in (if i managed to follow the instructions properly) I'm more than happy for you to fine tune my code. Its nice for me to have such good Quality Assurance :-) Cheers Stuart --- "Randolph T. Fielding" <gat...@ci...> wrote: > Stuart - > > Sure thing. I agree with you completely. > Right now, I run an update every night and > then do CVS diffs on each file that has been > modified, so that I can see what was done and > keep up with the changes. This list sounds > like it would help me out greatly, since I > wouldn't need to do updates right away if it > wasn't necessary. By the way, thanks for > putting up with my anal-retentiveness...I > know some of my commits are pretty lame! :-) > I just want to make sure that you know that I > am never mocking or devaluing your work in > any way. In fact, it's quite the contrary. > I am really excited about jsPro, and I really > look forward to our continued collaborations. > > Cheers, > Randy ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk |
|
From: Randolph T. F. <gat...@ci...> - 2003-09-04 21:41:19
|
Stuart - Sure thing. I agree with you completely. Right now, I run an update every night and then do CVS diffs on each file that has been modified, so that I can see what was done and keep up with the changes. This list sounds like it would help me out greatly, since I wouldn't need to do updates right away if it wasn't necessary. By the way, thanks for putting up with my anal-retentiveness...I know some of my commits are pretty lame! :-) I just want to make sure that you know that I am never mocking or devaluing your work in any way. In fact, it's quite the contrary. I am really excited about jsPro, and I really look forward to our continued collaborations. Cheers, Randy -----Original Message----- From: jsp...@li... [mailto:jsp...@li...urceforge.n et] On Behalf Of Stuart Wigley Sent: Thursday, September 04, 2003 11:04 AM To: jsp...@li... Subject: [Jspro-devel] New CVS Commit Mailing List Hi Randy, SF provide a automated way of sending details of all CVS Commits to an email address of your choice. I'd quite like to set up a jspro-commit mailing list so that subscribers will see a digest of the days CVS activity - if any :-) Are you happy with this? The only thing to consider is that all messages at the time of the Commit would become immortalised in this mailing list. Cheers Stuart _____________________________________________ ___________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk --------------------------------------------- ---------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________ __ Jspro-devel mailing list Jsp...@li... https://lists.sourceforge.net/lists/listinfo/ jspro-devel |
|
From: <stu...@ya...> - 2003-09-04 15:04:41
|
Hi Randy, SF provide a automated way of sending details of all CVS Commits to an email address of your choice. I'd quite like to set up a jspro-commit mailing list so that subscribers will see a digest of the days CVS activity - if any :-) Are you happy with this? The only thing to consider is that all messages at the time of the Commit would become immortalised in this mailing list. Cheers Stuart ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk |
|
From: <stu...@ya...> - 2003-09-03 08:02:44
|
Hi Randy, Thats great news!!! I've set up two VHOSTS as requested: www.jspro.org jspro.org They should be created in the next 6 hours. Cheers Stuart ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ |
|
From: Randolph T. F. <gat...@ci...> - 2003-09-03 06:12:38
|
Stuart -
Give me another day or so, and I'll get back
to you on this. After spending all the time
I had tonight reading documentation and
setting up the domain stuff, I didn't have
the time to look over this stuff much. I
will let you know my thoughts very soon.
Cheers,
Randy
-----Original Message-----
From: jsp...@li...
[mailto:jsp...@li...urceforge.n
et] On Behalf Of Stuart Wigley
Sent: Tuesday, September 02, 2003 6:46 AM
To: jsp...@li...
Subject: [Jspro-devel] How to use the Debug
window
An initial version of the Debug class has
been checked
into CVS. This is still a work in progress
and i'd
appreciate some comments, but not a full code
review
just yet :-)
To use the Debug window include debug.js and
create an
instance of Debug. The debug window will open
when the
page refreshes (unless you have
popup-blocking
enabled). The only interface is
myDebug.print("stuff");
To send Exceptions and Errors to the debug
window get
the latest Error.js and set the debugLevel to
4.
Cheers
Stuart
_____________________________________________
___________________________
Want to chat instantly with your online
friends? Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/
|
|
From: Randolph T. F. <gat...@ci...> - 2003-09-03 06:10:09
|
Stuart - All right! Now that's more like it! :-) I have more good news... Last night, I registered the domain name jspro.org for our use! It is ours! I figured this would give us a great and easy way to publicize jsPro down the road. I have everything from my side configured for the virtual hosting services at SourceForge.net, so that jspro.org references the appropriate SourceForge.net subdomains when traffic is pointed toward the jspro.org domain. The references should be in place within the next couple of hours. There is only one step left to complete, and I need you to help me out on it, since I am not the project administrator. The step requires you to configure the VHOST services for jsPro at the SourceForge.net end. Here are the directions you need straight from the SourceForge.net documentation: "The VHOST configuration process has been automated using a self-service tool (as a project administrator, you may set up the VHOST configuration for your project). This new self-service tool is available by clicking on the 'Virtual Host (VHOST) Configuration' link from the Project Admin page for your project. This tool accepts entries for the hostnames for which you would like our servers to accept traffic. For example, if you want our servers to answer for both mydomain.org and www.mydomain.org, both must be added via the VHOST configuration interface. VHOST additions will become active within six hours of being submitted." So, all I need you to do is add jspro.org and www.jspro.org to the SourceForge.net servers through the VHOST configuration interface. After that is complete, both jspro.org and www.jspro.org should send us and anyone else to the jsPro website hosted at SourceForge.net. The only thing left to do then is actually MAKE a website for people to browse to! :-) Send me a note if you run into any issues (or just to let me know it all worked!). Later, Randy -----Original Message----- From: jsp...@li... [mailto:jsp...@li...urceforge.n et] On Behalf Of Stuart Wigley Sent: Tuesday, September 02, 2003 11:13 AM To: jsp...@li... Subject: [Jspro-devel] jsPro gets a mention on CogWorks Just thought i'd let you know that i forwarded some details on jsPro to the guy who runs CogWorks after reading that he has an interest in JavaScript APIs. Yipee we got a mention on the site :-) http://cogworks.manilasites.com/newsItems/vie wDepartment$web%20design _____________________________________________ ___________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ |
|
From: Randolph T. F. <gat...@ci...> - 2003-09-03 04:49:15
|
Stuart - I am sure that this isn't the answer you were looking for, but both browsers are correct in their implementation of the DOM Level 1 Specification [http://www.w3.org/TR/2000/WD-DOM-Level-1-200 00929/level-one-core.html#ID-F68F082] (although Microsoft adds a proprietary third parameter that makes the comparison between the first parameter of the method and the actual HTML-element attribute name case-insensitive [http://msdn.microsoft.com/workshop/author/dh tml/reference/methods/setattribute.asp?frame=3D true]). The thing to remember when utilizing the setAttribute method is that the method--although a standard DOM method--is implementation dependent within the environment the method is running in. Therefore, in IE, the method is dependent on the JScript implementation of the DOM and DHTML, and in Mozilla, the method is dependent on the JavaScript implementation of the DOM and DHTML. Unfortunately, Microsoft's JScript implements the "class" attribute in the DOM and DHTML as the property "className". Likewise, JScript implements the "colspan" attribute as the property "colSpan". Why Microsoft did this is beyond me, but that is just the way it is in JScript. Therefore, the setAttribute method in IE has to respect these property names to function correctly, and you will need to have browser-specific forks in jsPro if you plan on using these attributes. Personally, the way the Mozilla team implemented the DHTML functionality is the way it should be, since the DHTML property names match up identically with the HTML-element attribute names, but we sure can't do anything about changing JScript. This won't be the last time we run into this sort of thing! :-) Cheers, Randy -----Original Message----- From: jsp...@li... [mailto:jsp...@li...urceforge.n et] On Behalf Of Stuart Wigley Sent: Tuesday, September 02, 2003 5:59 AM To: jsp...@li... Subject: [Jspro-devel] Cross-browser compatibility Hi, I've got two problems with the use of HTMLElement.setAttribute() that i'd like to discuss in terms of cross-browser compatibility. I (kind of) understand why IE and Mozilla are different in the following examples but I'm not really sure which browser is 'correct'. myTableCell.setAttribute('colspan', 2) - Mozilla, not IE myTableCell.setAttribute('colSpan', 2) - IE, not Mozilla myTableCell.setAttribute('class', 'foo') - Mozilla, not IE myTableCell.setAttribute('className', 'foo') - IE, not Mozilla I've found myself wanting to use these examples in jsPro to implement a new Debug class for handling custom debug messages and the redirection of Error messages. Lets make this our first Mailing List discussion :-) Cheers Stuart _____________________________________________ ___________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ |
|
From: <stu...@ya...> - 2003-09-02 15:12:57
|
Just thought i'd let you know that i forwarded some details on jsPro to the guy who runs CogWorks after reading that he has an interest in JavaScript APIs. Yipee we got a mention on the site :-) http://cogworks.manilasites.com/newsItems/viewDepartment$web%20design ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ |
|
From: <stu...@ya...> - 2003-09-02 10:46:21
|
An initial version of the Debug class has been checked
into CVS. This is still a work in progress and i'd
appreciate some comments, but not a full code review
just yet :-)
To use the Debug window include debug.js and create an
instance of Debug. The debug window will open when the
page refreshes (unless you have popup-blocking
enabled). The only interface is
myDebug.print("stuff");
To send Exceptions and Errors to the debug window get
the latest Error.js and set the debugLevel to 4.
Cheers
Stuart
________________________________________________________________________
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/
|
|
From: <stu...@ya...> - 2003-09-02 09:58:42
|
Hi,
I've got two problems with the use of
HTMLElement.setAttribute() that i'd like to discuss in
terms of cross-browser compatibility.
I (kind of) understand why IE and Mozilla are
different in the following examples but I'm not really
sure which browser is 'correct'.
myTableCell.setAttribute('colspan', 2) - Mozilla, not
IE
myTableCell.setAttribute('colSpan', 2) - IE, not
Mozilla
myTableCell.setAttribute('class', 'foo') - Mozilla,
not IE
myTableCell.setAttribute('className', 'foo') - IE, not
Mozilla
I've found myself wanting to use these examples in
jsPro to implement a new Debug class for handling
custom debug messages and the redirection of Error
messages.
Lets make this our first Mailing List discussion :-)
Cheers
Stuart
________________________________________________________________________
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/
|
