redback-devel Mailing List for redback
Status: Pre-Alpha
Brought to you by:
x3ro
Menu
▾
▴
redback-devel — Development mailing list for redback
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: <ben...@id...> - 2004-05-25 08:46:25
|
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: Joshua M. <jo...@mi...> - 2004-04-19 14:06:42
|
OK so that one's sorted. We now have named nodes by default, with the option of specifying the row ID using 'nodeId' in the URL. The syntax is: http://example.com/doc/node/Welcome or ... http://example.com/doc/nodeId/348 ... I have abandoned the 'virtual.html' (as well as the 'virtual.css' and 'virtual.js' at the end of CSS and JavaScript URLs). My thoughts for the next steps with this system: - Better exception handling. I moved the database with my website's data from a live server to my local box, and, when it found 'www.mirtec.net' as the fqdn instead of 'localhost', it gave me a fatal error. That's not good. Should drop out gracefully. - Subnode handling. From the point of view of clean code, any node should be treated alike. From a performance point of view, much better to grab all data in one swoop (or as few as possible, maybe one to get the template html and another to get the prefs and related content). Of course I will have to go with the latter but I want to make it as clean as possible ... - Config files. We need stuff like database user/password, path to Smarty, etc, in some kind of config file. PHP5 is much better at handling XML but I need to write this in PHP4 because the server I have my website on also has live websites for clients that would not be amused by any PHP5 teething troubles. That's all from me, for now. Josh Joshua Mostafa wrote: >Here is my current dilemma: > >I am a bit unsure about the way the Site object is currently generating >URIs. At the moment they look something like: > >http://example.com/doc/node/423/virtual.html > >... or with a little more info (say, style info) they could look like: > >http://example.com/doc/node/423/style/58/virtual.html > >Now although this is good in that it doesn't show the technologies used >(i.e. PHP) it is, according to an article (which I'll be damned if I can >find again), bad in that it shows too much about the workings of the >database (the IDs of the nodes) and too little about the content. So >perhaps better would be to use: > >http://example.com/doc/all-about-fish/ > >... and then styling information could be more explicit, eg: > >http://example.com/doc/all-about-fish/style/blue-theme/ > >Of course this leads to naming conflicts, dealing with stupidly named >nodes, etc ... I guess we could implement validation (based on unique-ness >and absence of URL-friendly characters) and/or conversion of problemetical >characters (urlencode(), maybe). > >It'll be good if we get this sorted before we try to host the homepage on >redback. > >Thoughts? > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click >_______________________________________________ >Redback-devel mailing list >Red...@li... >https://lists.sourceforge.net/lists/listinfo/redback-devel > > > |
|
From: Joshua M. <jo...@mi...> - 2004-04-16 06:08:06
|
Here is my current dilemma: I am a bit unsure about the way the Site object is currently generating URIs. At the moment they look something like: http://example.com/doc/node/423/virtual.html ... or with a little more info (say, style info) they could look like: http://example.com/doc/node/423/style/58/virtual.html Now although this is good in that it doesn't show the technologies used (i.e. PHP) it is, according to an article (which I'll be damned if I can find again), bad in that it shows too much about the workings of the database (the IDs of the nodes) and too little about the content. So perhaps better would be to use: http://example.com/doc/all-about-fish/ ... and then styling information could be more explicit, eg: http://example.com/doc/all-about-fish/style/blue-theme/ Of course this leads to naming conflicts, dealing with stupidly named nodes, etc ... I guess we could implement validation (based on unique-nes= s and absence of URL-friendly characters) and/or conversion of problemetica= l characters (urlencode(), maybe). It'll be good if we get this sorted before we try to host the homepage on redback. Thoughts? |
