How to use drakxtools-http ?

[dglent]

Do you know what this is about and how can be used ?
http://pkgs.org/mageia-1/mageia-core-re ... 6.rpm.html

thanks

[wobo]

Did you go to that address? The first sentence on that web page reads:

This package lets you configure your computer through your Web browser: it provides an HTTP interface to the Mandriva tools found in the drakxtools package.

You find the same description of the package in the software management in MCC. It's been around since 2004 or longer.

[dglent]

i have to setup a web server first ?
Did you try it ?

[wobo]

No, I did not try it, the need for such a tool did not come to my mind yet because I can always start the real thing (MCC). Yes, I would think it is necessary to run a web server which can host the tool.

[alf]

No, You needn't set up a webserver. Drakxtools-http works similar to webmin which has it's own "miniserv". You start drakxtools-http with "localhost:10001" in browser. That's all.

[dglent]

Thanks very much for the answer
I could open the drakxtools-http with this: https://localhost:10001/
I tried it, it have some bugs, i thought that it could give a better access to the control panel but finaly not, it has only some basic functions

[doktor5000]

Would you please mind explaining the need for "better access to the contol panel" you seem to see?

[dglent]

there is few drak tools available
there are missing functions in them and missings buttons
some of them does nt work at all

Did you try it ? Please try it before replying because these things are easy to see from a user side.

[alf]

hm, i think you missunderstood doktor5000. He wanted to know, why you thougt that drakxtools-http gave better access to the control functions than MCC self.

[doktor5000]

No, i meant more in the direction "why would one want to use drakxtools-http when you can use drakxtools directly" ...

referring to your mention of

i thought that it could give a better access to the control panel but finaly not, it has only some basic functions

@alf: Exactly!
Or why there would be need for a better access to control center functions, i.e. what the MCC itself is lacking, which his questions implies.

[wobo]

@dglent: YOu must understand that drakxtools-http is just a front end for the tools which are available in the MCC. As most frontends drakxtools-http can not offer more than the tools themselves do.

[dglent]

better access from a user point of view
take an example when you use webmin, it is fast, flexible, modular, integrated to your environment, customizable, you can open it the same time you are in the internet with your browser.
Thinks easy to remark, even from a newbie

Try to install a package from mcc and try to do the same thing from packagekit. You will see the difference.
If you dont see any difference you can be comfortable with mcc but there are other users that has a little more worry mind and they look about improve things and they experience.

First, i read this post:
viewtopic.php?f=29&t=148
after that, i took a look to the draktools package (because i had free time)
i saw a package named drakxtools-http.
As i wanted a better access to the tools, i thought that it could fit my needs (thinking to webmin)
Unfortunately it cant be a front-end for the draktools because it cant replace the mcc (if someone wants to know why please try it)


I asked here how to use the functionality of the web interface of draktools and i find my self guilty to want something, that I DONT NEED IT but i did nt know it.
The same time you have to reply to the above post in the other section, why someone wants to improve mcc, and convince him that he does nt need it really but, he did nt know it.

And sorry if my reply sounds aggressive, the phrases sound different when writing down them.

[wobo]

Of course every user has his own way of working. What is easy for one user may be a nightmare for the other and vice versa. So the Linux world constantly puts out variations of existing tools & applications. That's a Good Thing(tm).

Try to install a package from mcc and try to do the same thing from packagekit. You will see the difference.
If you dont see any difference you can be comfortable with mcc but there are other users that has a little more worry mind and they look about improve things and they experience.

That's what I meant with "different ways to work".

But in this case of mcc vs drakxtools-http the original tools have a strong point ahead of the browser approach: drakxtools-http needs a certain environment to run, a browser and (for the sake of comfort) a running x server (a GUI). The original tools don't need a browser, for most of these tools you don't even need a running x server, which is very helpful if your x server does not start.
For example: when I know that I will do only system management on my laptop I don't start the x system, I do everything with terminal tools. Running the MCC (and other tools like MC for file management) with ncurses graphics needs less than 50% of battery lifetime.

Another strong point of the original MCC: It provides the full scale of the drakx tools while drakxtools-http only provides a selection.

Unfortunately it cant be a front-end for the draktools because it cant replace the mcc (if someone wants to know why please try it)

drakxtools-http IS a frontend for some of the MCC tools. It only provides another way to work with these tools.

Anyhow, you are right in one point: if you want to use it then use it, it's your decision. All explanations here only wanted to explain what drakxtools-http is and what it is not.