I tryed to use the method CreateIssue() but nothing was added to the redmine project. After a short look into the implementation of this method it looks as if this feature is not yet fully implemented.
Is it planed to extend Redmain Client so that CreateIssue() is working but also other features like CreateProject() etc.?
Thanks,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
CreateIssue() is in the works right now and should be ready as soon as I get some free time to finish it. Having a complete API for Redmine administration in the library would be very nice but it's quite a bit of work as there's no API on the server side so at least for now I'm not planing it as I don't need it myself and can't guarantee the ability to maintain it in the future. Implementing parts of it, especially the easy parts like creating projects would be very easy though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your quick answer. Just another, more general question. Do you know, why most webapplications are done in this way, working directly on top of the database instead of using a layer in between which provides an API to access the database/application logic?
I'm not so deep into web programming, but dividing the application into database, logic and presentation/frontend would be to my mind a much better approach. I'd like to write a "meta"-frontend to summarize the services of all needed applications during the development process (like mantis, redmine, ...). But everytime I find a application which looks good to use, I face the same problem - no or an incomplete/bad maintained API...
So long,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The short answer would probably be: Questionable design decisions at the beginning of the project and a lack of time and manpower to make the changes later.
In fact most of the people seem to prefer new features over the API and that's why http://www.redmine.org/issues/296 lives for more than two years and is still not implemented. Fortunately Redmine uses MVC pattern so implementing an API for it is something that can happen without having to rewrite the whole thing from scratch so I believe we will get there sooner or later as some considerable progress in the right direction is on it's way for the 0.9 release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After seeing this video: http://www.youtube.com/watch?v=v_UyVmITiYQ, I think this will be the answer for what I search for. Google wave has the potential to be a meta tool. I think they started a the right end, first building an infrastructure, framework and API, and second start to build/let build applications using this. :o)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I tryed to use the method CreateIssue() but nothing was added to the redmine project. After a short look into the implementation of this method it looks as if this feature is not yet fully implemented.
Is it planed to extend Redmain Client so that CreateIssue() is working but also other features like CreateProject() etc.?
Thanks,
Thomas
CreateIssue() is in the works right now and should be ready as soon as I get some free time to finish it. Having a complete API for Redmine administration in the library would be very nice but it's quite a bit of work as there's no API on the server side so at least for now I'm not planing it as I don't need it myself and can't guarantee the ability to maintain it in the future. Implementing parts of it, especially the easy parts like creating projects would be very easy though.
Thanks for your quick answer. Just another, more general question. Do you know, why most webapplications are done in this way, working directly on top of the database instead of using a layer in between which provides an API to access the database/application logic?
I'm not so deep into web programming, but dividing the application into database, logic and presentation/frontend would be to my mind a much better approach. I'd like to write a "meta"-frontend to summarize the services of all needed applications during the development process (like mantis, redmine, ...). But everytime I find a application which looks good to use, I face the same problem - no or an incomplete/bad maintained API...
So long,
Thomas
The short answer would probably be: Questionable design decisions at the beginning of the project and a lack of time and manpower to make the changes later.
In fact most of the people seem to prefer new features over the API and that's why http://www.redmine.org/issues/296 lives for more than two years and is still not implemented. Fortunately Redmine uses MVC pattern so implementing an API for it is something that can happen without having to rewrite the whole thing from scratch so I believe we will get there sooner or later as some considerable progress in the right direction is on it's way for the 0.9 release.
After seeing this video: http://www.youtube.com/watch?v=v_UyVmITiYQ, I think this will be the answer for what I search for. Google wave has the potential to be a meta tool. I think they started a the right end, first building an infrastructure, framework and API, and second start to build/let build applications using this. :o)