[opensuse-buildservice] Opensuse API doc
Hi i try to write a C# dll to use opensuse API, i use https://api.opensuse.org/apidocs#61 for doc , there is a more complete doc/description, for example if i want to set user data : PUT /person/<userid> I gess after i should put somthing like : ?realname=test But it doesn't work Another thingh missing for example is the list of aviable tag and metada. All GET should be okay, but most of PUT are not compety documented. -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Aug 06, 2008 at 11:51:12PM +0200, Petit Eric wrote:
Hi i try to write a C# dll to use opensuse API, i use https://api.opensuse.org/apidocs#61 for doc , there is a more complete doc/description, for example if i want to set user data : PUT /person/<userid> I gess after i should put somthing like : ?realname=test But it doesn't work Another thingh missing for example is the list of aviable tag and metada. All GET should be okay, but most of PUT are not compety documented.
Yes, it's really lacking. Your best bet is to observe what osc, the command line client is doing and reverse engineer from there. osc can "explain" what it does. Use -d as global option to see all URLs of requests issued, and -H to for the gory details. Of course you could also look at the code. The example you mentioned loosely corresponds to the 'osc -e meta user <userid>' command. In that particular case, the data is XML which is sent in the request body. The XML being the complete data blob. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Wed, Aug 06, 2008 at 11:51:12PM +0200, Petit Eric wrote:
Hi i try to write a C# dll to use opensuse API, i use https://api.opensuse.org/apidocs#61 for doc , there is a more complete doc/description, for example if i want to set user data : PUT /person/<userid> I gess after i should put somthing like : ?realname=test But it doesn't work Another thingh missing for example is the list of aviable tag and metada. All GET should be okay, but most of PUT are not compety documented.
Yes, it's really lacking.
Your best bet is to observe what osc, the command line client is doing and reverse engineer from there. hum really hasardous task, not a twice time, my brain say enouth of reverse engenering lol osc was write by suse/novell, they certainly have a better doc/spec,
2008/8/7 Peter Poeml
osc can "explain" what it does. Use -d as global option to see all URLs of requests issued, and -H to for the gory details.
Of course you could also look at the code.
The example you mentioned loosely corresponds to the 'osc -e meta user <userid>' command. In that particular case, the data is XML which is sent in the request body. The XML being the complete data blob.
Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH Research & Development
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Aug 07, 2008 at 01:32:22AM +0200, Petit Eric wrote:
hum really hasardous task, not a twice time, my brain say enouth of reverse engenering lol osc was write by suse/novell, they certainly have a better doc/spec, this not public.
Not really - there is no better spec inside Novell, unfortunately. Funny thing is, and I just realize it, in fact I started out exactly like you. (Being the first author of osc.) Tried things, asked here, and so on. (Got me this far ;) The api docs are sometimes updated. It helps to ask for it. I'll also check back with my colleagues to emphasize the importance of this.
I start the project here and shear generous guy to finish to copy/pste the heavy part (all the function) :
http://sourceforge.net/projects/monoosc/ code is in the svn, the engine(basic and simple) is finish, there is also a "samlpe" to use it.
Interesting. You might want to add something to the wiki pages about it, to increase visibility. Maybe around here: http://en.opensuse.org/Build_Service#Build_Service_Clients Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
2008/8/7 Peter Poeml
On Thu, Aug 07, 2008 at 01:32:22AM +0200, Petit Eric wrote:
hum really hasardous task, not a twice time, my brain say enouth of reverse engenering lol osc was write by suse/novell, they certainly have a better doc/spec, this not public.
Not really - there is no better spec inside Novell, unfortunately.
Funny thing is, and I just realize it, in fact I started out exactly like you. (Being the first author of osc.) Tried things, asked here, and so on. (Got me this far ;)
The api docs are sometimes updated. It helps to ask for it. I'll also check back with my colleagues to emphasize the importance of this.
I start the project here and shear generous guy to finish to copy/pste the heavy part (all the function) :
http://sourceforge.net/projects/monoosc/ code is in the svn, the engine(basic and simple) is finish, there is also a "samlpe" to use it.
Interesting. You might want to add something to the wiki pages about it, to increase visibility. Maybe around here: http://en.opensuse.org/Build_Service#Build_Service_Clients First of all , really thank's and clap hand for this quick response. In fact i will do it later(or i missunderstood, you speak about novell wiki not SF one), because, as i say the "engine" is here, but the haevy and very simple task is to "copy/paste" all function, not very interesting but needed,i think after write a GUI to made easy and friendly the use of OBS. So is there a way to colaborate in this heavy task and why not in fully in my project ?
Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH Research & Development
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2008/8/7 Petit Eric
2008/8/7 Peter Poeml
: On Thu, Aug 07, 2008 at 01:32:22AM +0200, Petit Eric wrote:
hum really hasardous task, not a twice time, my brain say enouth of reverse engenering lol osc was write by suse/novell, they certainly have a better doc/spec, this not public.
Not really - there is no better spec inside Novell, unfortunately.
Funny thing is, and I just realize it, in fact I started out exactly like you. (Being the first author of osc.) Tried things, asked here, and so on. (Got me this far ;)
The api docs are sometimes updated. It helps to ask for it. I'll also check back with my colleagues to emphasize the importance of this.
I start the project here and shear generous guy to finish to copy/pste the heavy part (all the function) :
http://sourceforge.net/projects/monoosc/ code is in the svn, the engine(basic and simple) is finish, there is also a "samlpe" to use it.
Interesting. You might want to add something to the wiki pages about it, to increase visibility. Maybe around here: http://en.opensuse.org/Build_Service#Build_Service_Clients First of all , really thank's and clap hand for this quick response. In fact i will do it later(or i missunderstood, you speak about novell wiki not SF one), because, as i say the "engine" is here, but the Really nice, i saw i can and make the modification at the novell wikki, i hope i didn't do a mistake, i'm not an Wiki "expert". haevy and very simple task is to "copy/paste" all function, not very interesting but needed,i think after write a GUI to made easy and friendly the use of OBS. So is there a way to colaborate in this heavy task and why not in fully in my project ?
Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH Research & Development
--
Cordially.
Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. ---------------------------------------------------------------------------
Few people are done for independence, it is the privilege of the powerful ones. ---------------------------------------------------------------------------
No key was wounded during the drafting of this message.
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Aug 07, 2008 at 02:32:39AM +0200, Petit Eric wrote:
http://sourceforge.net/projects/monoosc/ code is in the svn, the engine(basic and simple) is finish, there is also a "samlpe" to use it.
Interesting. You might want to add something to the wiki pages about it, to increase visibility. Maybe around here: http://en.opensuse.org/Build_Service#Build_Service_Clients First of all , really thank's and clap hand for this quick response. In fact i will do it later(or i missunderstood, you speak about novell wiki not SF one), because, as i say the "engine" is here, but the Really nice, i saw i can and make the modification at the novell wikki, i hope i didn't do a mistake, i'm not an Wiki "expert".
This is what I meant, yes, and it looks just fine. Thanks a lot! Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Thu, Aug 07, 2008 at 02:25:08AM +0200, Petit Eric wrote:
I start the project here and shear generous guy to finish to copy/pste the heavy part (all the function) :
http://sourceforge.net/projects/monoosc/ code is in the svn, the engine(basic and simple) is finish, there is also a "samlpe" to use it. [...] First of all , really thank's and clap hand for this quick response. In fact i will do it later(or i missunderstood, you speak about novell wiki not SF one), because, as i say the "engine" is here, but the haevy and very simple task is to "copy/paste" all function, not very interesting but needed,i think after write a GUI to made easy and friendly the use of OBS. So is there a way to colaborate in this heavy task and why not in fully in my project ?
I do not completely understand so far what you mean is needed to copy and paste -- could you elaborate? As the engine is there, is it an intermediary task needed to allow implementing a GUI, or are you referring to the act of programming a GUI using the enine? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Thu, Aug 07, 2008 at 02:25:08AM +0200, Petit Eric wrote:
I start the project here and shear generous guy to finish to copy/pste the heavy part (all the function) :
http://sourceforge.net/projects/monoosc/ code is in the svn, the engine(basic and simple) is finish, there is also a "samlpe" to use it. [...] First of all , really thank's and clap hand for this quick response. In fact i will do it later(or i missunderstood, you speak about novell wiki not SF one), because, as i say the "engine" is here, but the haevy and very simple task is to "copy/paste" all function, not very interesting but needed,i think after write a GUI to made easy and friendly the use of OBS. So is there a way to colaborate in this heavy task and why not in fully in my project ?
I do not completely understand so far what you mean is needed to copy and paste -- could you elaborate? As the engine is there, is it an intermediary task needed to allow implementing a GUI, or are you referring to the act of programming a GUI using the enine? The GUI will come very later, i think to do it, if time permit or a man doesn't start before me, for the copy /paste, i speak for example at the about function : http://monoosc.svn.sourceforge.net/viewvc/monoosc/MonoOSC/MonoOSCFramework/Class/Functions/About/About.cs?revision=5&view=markup
2008/8/7 Peter Poeml
Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH Research & Development
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello pete
Are you busy now, or simply look my code and think my
startup/structure project is bad ?
2008/8/7 Petit Eric
On Thu, Aug 07, 2008 at 02:25:08AM +0200, Petit Eric wrote:
I start the project here and shear generous guy to finish to copy/pste the heavy part (all the function) :
http://sourceforge.net/projects/monoosc/ code is in the svn, the engine(basic and simple) is finish, there is also a "samlpe" to use it. [...] First of all , really thank's and clap hand for this quick response. In fact i will do it later(or i missunderstood, you speak about novell wiki not SF one), because, as i say the "engine" is here, but the haevy and very simple task is to "copy/paste" all function, not very interesting but needed,i think after write a GUI to made easy and friendly the use of OBS. So is there a way to colaborate in this heavy task and why not in fully in my project ?
I do not completely understand so far what you mean is needed to copy and paste -- could you elaborate? As the engine is there, is it an intermediary task needed to allow implementing a GUI, or are you referring to the act of programming a GUI using the enine? The GUI will come very later, i think to do it, if time permit or a man doesn't start before me, for the copy /paste, i speak for example at the about function : http://monoosc.svn.sourceforge.net/viewvc/monoosc/MonoOSC/MonoOSCFramework/Class/Functions/About/About.cs?revision=5&view=markup
2008/8/7 Peter Poeml
: this an class for the about function, so each function will come in an standalone class and use a specific namespace, so the "copy/paste" is here, most of get function are really similar, just took lot of time to do them one by one. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH Research & Development
--
Cordially.
Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. ---------------------------------------------------------------------------
Few people are done for independence, it is the privilege of the powerful ones. ---------------------------------------------------------------------------
No key was wounded during the drafting of this message.
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi
Finaly, i think it took too mutch time to start by writing all
function and so i will write GUI with needed function and all other
will come after.
A first result make me happy :
http://sourceforge.net/project/screenshots.php?group_id=236037.
2008/8/7 Petit Eric
Hello pete Are you busy now, or simply look my code and think my startup/structure project is bad ?
2008/8/7 Petit Eric
: On Thu, Aug 07, 2008 at 02:25:08AM +0200, Petit Eric wrote:
I start the project here and shear generous guy to finish to copy/pste the heavy part (all the function) :
http://sourceforge.net/projects/monoosc/ code is in the svn, the engine(basic and simple) is finish, there is also a "samlpe" to use it. [...] First of all , really thank's and clap hand for this quick response. In fact i will do it later(or i missunderstood, you speak about novell wiki not SF one), because, as i say the "engine" is here, but the haevy and very simple task is to "copy/paste" all function, not very interesting but needed,i think after write a GUI to made easy and friendly the use of OBS. So is there a way to colaborate in this heavy task and why not in fully in my project ?
I do not completely understand so far what you mean is needed to copy and paste -- could you elaborate? As the engine is there, is it an intermediary task needed to allow implementing a GUI, or are you referring to the act of programming a GUI using the enine? The GUI will come very later, i think to do it, if time permit or a man doesn't start before me, for the copy /paste, i speak for example at the about function : http://monoosc.svn.sourceforge.net/viewvc/monoosc/MonoOSC/MonoOSCFramework/Class/Functions/About/About.cs?revision=5&view=markup
2008/8/7 Peter Poeml
: this an class for the about function, so each function will come in an standalone class and use a specific namespace, so the "copy/paste" is here, most of get function are really similar, just took lot of time to do them one by one. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH Research & Development
--
Cordially.
Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. ---------------------------------------------------------------------------
Few people are done for independence, it is the privilege of the powerful ones. ---------------------------------------------------------------------------
No key was wounded during the drafting of this message.
--
Cordially.
Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. ---------------------------------------------------------------------------
Few people are done for independence, it is the privilege of the powerful ones. ---------------------------------------------------------------------------
No key was wounded during the drafting of this message.
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, On Thu, Aug 07, 2008 at 02:16:52 +0200, Petit Eric wrote:
Hello pete Are you busy now, or simply look my code and think my startup/structure project is bad ?
I'm not really at work today, and I have no clue about Mono anyway. I'm sorry, I won't be of much help ;) Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
participants (2)
-
Peter Poeml
-
Petit Eric