I just saw the demo (not looked at the code yet) and i would like to contribute.
First, i would like to develop a Java based server-side code (as a "proof of concept" that psych desktop doesnot rely on a particular server technology ;) ) , as well as to help with the client side code.
I already have a CLA at dojotoolkit.org, and i'm pretty used to work with dojo.
Awesome, you've come at a perfect time too, because we're going to be completely rewriting the server-side code for 1.1, so that it uses RPC and doctrine/yaml for communication and database storage, respectively. Java-based backends would be pretty slick, that way you can just drop it in as a servlet. I'll have to get svn:externals set up, that way we can have the two backends in different repositories and the client-side code will always be up-to-date with them. As I said before, the best time to start working on those is when we start putting together 1.1.
Right now we're finishing up 1.0, most of the work that has to be done involves the client-side code. Since you have a CLA signed, you can start working right away. Pick any 1.0 ticket that you want to work on (trac is acting strange right now, if it doesn't work now, try again later). I'll assign it to you, and you'll post up a patch once you're done. Once we feel you're contributing quality code, we'll give you SVN access.
We don't really have a mailing list, but we have these forums and we've got IRC. Most of us communicate via email or IM though, you can find my information in my profile. I'll tell the other guys to start using IRC more though.
Anyways, I'm looking forward to seeing what you kick out. If you have any other questions, just reply to this thread.
Once/if you feel comfortable with working with dojo, I'll assign some tickets to you, and you can submit some patches. I'll give you some guidance when needed, don't hesitate to ask :)
I'm not going to give you commit access right away just so that I can review any code you submit. Don't take it personally, it's just standard procedure.
Do you have any specific thing that you want to work on, or should I come up with a task for you to do? There isn't much for a new developer to do ATM, since we're finishing up the 1.0 release in the 1.0 branch, and trunk needs to get the backend restructuring finished before anyone can do anything with it.
Submitted by ovalenzuela on Thu, 10/16/2008 - 03:49.
i want to help, i write some code to use the cloud computing very easy, you could connecto to facebook, linkedin, google apps (contacts, maps, talk, calendar, etc), twitter and others. But i can't find a way to write apps.
Other hand, i cant find a way to translate to spanish.
It would be nice to have access to anything that has been written so far, even if it is not finished. Right now, I'm writing an Address Book app based on the Application Tutorial (and writing a tutorial along with it) but I need to figure out lots of things by myself.
I [b]do[/b] want to learn this thing (hmm ok no bbcode here) .
But, for example, where do I assign an extension to an application? When I double-click on welcome.txt, the Text Editor starts. Very nice. But what is the extension for the Word Processor? Where do I register my own .lad extension (for Lucid Address Book)? How to put an application icon on the desktop so we can start it by clicking on it? What is a Launcher?
I have a lot more questions to ask. Right now, I'm reading the code (and writing another article called "Lay of the Land" to figure this out and help others understand it).
Would be nice to have some docs about all of this, even if it is sketchy. I'll help flesh them out if need be. I downloaded and installed Sphinx, did a checkout of your documentation trunk and started writing. It is working and producing my articles in HTML (they are not finished evidently... I'm writing as I go).
As has been said in this thread, the community will write the apps. You guys need to concentrate on the core and make it rock solid. And help us help you by providing documentation on how to do things. For my part, I am ready to help with documentation, unit testing (which seems to be missing here), API docs (which are really needed), writing a couple of applications and documenting their howtos, and so on...
To be honest, I am really excited by Lucid. I am the new maintainer of an PHP ORM open source project (won't name it here 'cause it is not stable enough to be usable) but I do intend to proove its worth by using it one day for the Lucid 1.1 ORM, beside Doctrine.
And, as an aside while I'm here, when do we get to see the new web site? I'd like xsite.php to stop putting out 403s.
eheh, sorry for the pressure I'm putting on ;)
Tourelou,
L
PS It would be nice to have a small presentation of you core dev guys. What's your name? Where do you live? What part do you play in development? Would be very nice to know you a bit and know who to say thanks for this awesome software.
PPS Maybe I should have posted this in its own thread... but eh I started it here so here it is.
You're right, application structure should be elaborated on. I documented the package format last night, which is what determines which applications can handle which document formats. Right now there is no way to associate with a specific extension, but I'll fix that today. Anyways, I've been spending a lot of time documenting the core, as well as the APIs. I'll be sure to write some docs explaining application structure tonight.
I should add that the documentation that's on this site is updated from SVN every hour, so it's always up-to-date.
I agree with you regarding the applications though. We focus on providing a great core with an easy to use base set of APIs and libraries, as well as widgets. From the start we wanted the community to make the apps for us, sort of like a real operating system.
As for the new site, it's pretty much finished. We've been waiting for quite some time for our designer to finish the design. I really think that our website was one of the things that prevented us from having a community settle in. I've been pestering him about this for quite some time, but he is working on it.
Oh, and all of our names, as well as yours are in the credits. It's under System > About Psych Desktop. I live on Long Island in New York, and Jay lives in Brittan. I forgot where Dave lives, but he did a lot of the artwork, including the current logo. Steven, the person who is working on the new site design, lives in NYC. I'll tell you more in IRC if you want :D.
Wanting to contribute.
Hello.
I just saw the demo (not looked at the code yet) and i would like to contribute.
First, i would like to develop a Java based server-side code (as a "proof of concept" that psych desktop doesnot rely on a particular server technology ;) ) , as well as to help with the client side code.
I already have a CLA at dojotoolkit.org, and i'm pretty used to work with dojo.
How to begin with ?
Is there any mailing list ?
Thanks
Awesome, you've come at a
Awesome, you've come at a perfect time too, because we're going to be completely rewriting the server-side code for 1.1, so that it uses RPC and doctrine/yaml for communication and database storage, respectively. Java-based backends would be pretty slick, that way you can just drop it in as a servlet. I'll have to get svn:externals set up, that way we can have the two backends in different repositories and the client-side code will always be up-to-date with them. As I said before, the best time to start working on those is when we start putting together 1.1.
Right now we're finishing up 1.0, most of the work that has to be done involves the client-side code. Since you have a CLA signed, you can start working right away. Pick any 1.0 ticket that you want to work on (trac is acting strange right now, if it doesn't work now, try again later). I'll assign it to you, and you'll post up a patch once you're done. Once we feel you're contributing quality code, we'll give you SVN access.
We don't really have a mailing list, but we have these forums and we've got IRC. Most of us communicate via email or IM though, you can find my information in my profile. I'll tell the other guys to start using IRC more though.
Anyways, I'm looking forward to seeing what you kick out. If you have any other questions, just reply to this thread.
Well, the first thing is
Well, the first thing is that you should know a thing or two about dojo. Here's some stuff you can take a look at:
http://dojotoolkit.org/book/dojo-book-0-9/part-3-programmatic-dijit-and-...
Once/if you feel comfortable with working with dojo, I'll assign some tickets to you, and you can submit some patches. I'll give you some guidance when needed, don't hesitate to ask :)
I do development work with
I do development work with dojo. I comfortable in it.
Awesome. I'm not going to
Awesome.
I'm not going to give you commit access right away just so that I can review any code you submit. Don't take it personally, it's just standard procedure.
Do you have any specific thing that you want to work on, or should I come up with a task for you to do? There isn't much for a new developer to do ATM, since we're finishing up the 1.0 release in the 1.0 branch, and trunk needs to get the backend restructuring finished before anyone can do anything with it.
Oh, by the way, before I
Oh, by the way, before I commit any patches from you, you need to send a CLA to the Dojo Foundation. (http://dojotoolkit.org/cla)
Are you still interested at
Are you still interested at all?
Hi!!!
i want to help, i write some code to use the cloud computing very easy, you could connecto to facebook, linkedin, google apps (contacts, maps, talk, calendar, etc), twitter and others. But i can't find a way to write apps.
Other hand, i cant find a way to translate to spanish.
We're working on some
We're working on some up-to-date documentation for developers, it will be available once 1.0 is finished. You can see what's been written so far here:
http://trac.psychdesktop.net/browser/website/trunk/desktopsite/apps/content/templates/flatpages/documentation
The app tutorial is pretty much done, but there are still some things that have to be documented, like packaging, and the other APIs.
@psychcf, It would be nice
@psychcf,
It would be nice to have access to anything that has been written so far, even if it is not finished. Right now, I'm writing an Address Book app based on the Application Tutorial (and writing a tutorial along with it) but I need to figure out lots of things by myself.
I [b]do[/b] want to learn this thing (hmm ok no bbcode here) .
But, for example, where do I assign an extension to an application? When I double-click on welcome.txt, the Text Editor starts. Very nice. But what is the extension for the Word Processor? Where do I register my own .lad extension (for Lucid Address Book)? How to put an application icon on the desktop so we can start it by clicking on it? What is a Launcher?
I have a lot more questions to ask. Right now, I'm reading the code (and writing another article called "Lay of the Land" to figure this out and help others understand it).
Would be nice to have some docs about all of this, even if it is sketchy. I'll help flesh them out if need be. I downloaded and installed Sphinx, did a checkout of your documentation trunk and started writing. It is working and producing my articles in HTML (they are not finished evidently... I'm writing as I go).
As has been said in this thread, the community will write the apps. You guys need to concentrate on the core and make it rock solid. And help us help you by providing documentation on how to do things. For my part, I am ready to help with documentation, unit testing (which seems to be missing here), API docs (which are really needed), writing a couple of applications and documenting their howtos, and so on...
To be honest, I am really excited by Lucid. I am the new maintainer of an PHP ORM open source project (won't name it here 'cause it is not stable enough to be usable) but I do intend to proove its worth by using it one day for the Lucid 1.1 ORM, beside Doctrine.
And, as an aside while I'm here, when do we get to see the new web site? I'd like xsite.php to stop putting out 403s.
eheh, sorry for the pressure I'm putting on ;)
Tourelou,
L
PS It would be nice to have a small presentation of you core dev guys. What's your name? Where do you live? What part do you play in development? Would be very nice to know you a bit and know who to say thanks for this awesome software.
PPS Maybe I should have posted this in its own thread... but eh I started it here so here it is.
You're right, application
You're right, application structure should be elaborated on. I documented the package format last night, which is what determines which applications can handle which document formats. Right now there is no way to associate with a specific extension, but I'll fix that today. Anyways, I've been spending a lot of time documenting the core, as well as the APIs. I'll be sure to write some docs explaining application structure tonight.
I should add that the documentation that's on this site is updated from SVN every hour, so it's always up-to-date.
I agree with you regarding the applications though. We focus on providing a great core with an easy to use base set of APIs and libraries, as well as widgets. From the start we wanted the community to make the apps for us, sort of like a real operating system.
As for the new site, it's pretty much finished. We've been waiting for quite some time for our designer to finish the design. I really think that our website was one of the things that prevented us from having a community settle in. I've been pestering him about this for quite some time, but he is working on it.
Oh, and all of our names, as well as yours are in the credits. It's under System > About Psych Desktop. I live on Long Island in New York, and Jay lives in Brittan. I forgot where Dave lives, but he did a lot of the artwork, including the current logo. Steven, the person who is working on the new site design, lives in NYC. I'll tell you more in IRC if you want :D.
Well, very nice to know you
Well, very nice to know you guys. For my part, I'm Louis Lapointe and Ilive in Laval, a suburb city north of Montreal, in Quebec, Canada.
For the docs, I'll keep on reading yours and writing mines a I go along.
Post new comment