Re: approaches to PHP-based application interface? [message #176723 is a reply to message #176721] |
Fri, 20 January 2012 09:43 |
crankypuss
Messages: 147 Registered: March 2011
Karma:
|
Senior Member |
|
|
On 01/20/2012 02:27 AM, M. Strobel wrote:
> Am 20.01.2012 09:53, schrieb crankypuss:
>> On 01/19/2012 08:00 AM, The Natural Philosopher wrote:
>>> crankypuss wrote:
>>>> I'm not even sure how to ask the question. Maybe it's several questions.
>>>>
>>>> Supposing one wants to run a local apache server that supports a
>>>> PHP-based system interface, things like file editing, file management,
>>>> archive support, and various other applications. For some things like
>>>> file management it may need root privileges. It also needs to be
>>>> "safe" so that the applicable parts of it can run on a public server.
>>>> Are there approaches to this that have been successfully used in the
>>>> past?
>>>>
>>>> One major advantage of sticking with PHP is that my fairly large
>>>> codebase won't need to be rewritten. The html/browser paradigm is
>>>> perfectly adequate to all the things that I can foresee doing. On
>>>> Windows there is this thing, http://www.zzee.com/php-gui/
>>>> What it does is let you plug your PHP browser-based application into a
>>>> stripped-down browser so it runs as a Windows application without any
>>>> apache involvement. But I wish to do this on Linux.
>>>>
>>>> Failing both those approaches, can anyone recommend a good GUI package
>>>> that supports PHP applications, preferrably something gtk-based?
>>>>
>>>> Sorry this is such a scattered question. Basically I'm working on
>>>> building a system-independent PHP-based system front-end, parts of
>>>> which can be made available on a public web server.
>>>
>>> well look at webmin first, before you decide to 'go php' for everything.
>>>
>>> There are good reasons NOT to be TOTALLY php as well.
>>>
>>> Vis if the whole php regime has 'root access' ten you are in deep
>>> trouble if someone hacks the php layer.
>>>
>>> Better to write specific tools in - say C - that are expressly 'su root'
>>> type programs designed to edit just one part of the installation.
>>>
>>> So you might write a C program that can READ any file in /var/log with
>>> any permissions, but not WRITE one. So as to get to your log files for
>>> example. But not alter them.
>>>
>>> That the way we access mysql - we cant from php access the raw data
>>> files, but mysqld is a daemon that can, and we talk to that...
>>>
>>>
>>> Miking this easier for yourself always makes it easier for an
>>> incompetent or malicious person to screw things up as well.
>>
>> "Webmin is a web-based interface for system administration for Unix."
>>
>> I'm not really much interested in "system administration", but thanks for the thought.
>>
>>
>> What I'm really looking at is more about replacing user interfaces like Ubuntu's
>> Unity with something "browser-based" but which does not require an apache server.
>
> Not very convincing. Browser based GUIs are far behind the possibilities of a true
> GUI like Qt or Gtk+ or Tk.
>
> You want to carry over the browser like link n click to the desktop? MS is on this
> way with all the management consoles, and it is as fast as flowing rubber.
>
> Start some true GUI programming and you will see there is nothing to win in the way
> you think now.
>
> /Str.
Thank you for your opinion, but I've done "true GUI programming" and
I've had a bellyful of talking paper-clips and wiggling icons.
|
|
|