; --michael
>
>
>> -Original Message-
>> From: anton@pigeonpoint.com [mailto:anton@pigeonpoint.com]
>> Sent: Thursday, May 27, 2010 4:13 PM
>> To: openhpi-devel@lists.sourceforge.net
>> Subject: Re: [Openhpi-devel] HPI GUI application proposal
>&
hpibrowser
-Original Message-
From: anton@pigeonpoint.com [mailto:anton@pigeonpoint.com]
Sent: Thursday, May 27, 2010 6:13 PM
To: openhpi-devel@lists.sourceforge.net
Subject: Re: [Openhpi-devel] HPI GUI application proposal
My ideas:
- (q)hpiview3
- (q)hpiviewer
- (q)hpiexplorer
a holiday here in the US.
>
> --michael
>
>
>> -Original Message-
>> From: anton@pigeonpoint.com [mailto:anton@pigeonpoint.com]
>> Sent: Thursday, May 27, 2010 4:13 PM
>> To: openhpi-devel@lists.sourceforge.net
>> Subject: Re: [Openhpi-devel] H
gt; >
>> > --michael
>> >
>> > Regards,
>> > Michael Bishop
>> > Enterprise Servers and Storage (ISB Linux/Telco)
>> > Hewlett-Packard Company
>> > 3404 E. Harmony Rd. Bldg. 5L, Post B7, Mailstop 42
>> > Fort Collins, CO 8052
Mohan asked me to comment on licenses; I think what's being proposed is
fine. Let me clarify what I think I've heard to this point:
* The new code will not be a required part of the OpenHPI
library/daemon
* The new code will be licensed under the BSD, consistent with the
5L, Post B7, Mailstop 42
> > Fort Collins, CO 80528-9599
> > Phone: 970-898-4393
> > E-Mail: michael.bis...@hp.com
> >
> >
> >
> >
> >> -Original Message-
> >> From: Anton Pak [mailto:anton@pigeonpoint.com]
> >> Sent: Thursday, May
hael
> >>
> >>
> >>> -Original Message-
> >>> From: anton@pigeonpoint.com [mailto:anton@pigeonpoint.com]
> >>> Sent: Thursday, May 27, 2010 3:35 PM
> >>> To: openhpi-devel@lists.sourceforge.net
> >>> Cc:
sday, May 27, 2010 3:35 PM
>>> To: openhpi-devel@lists.sourceforge.net
>>> Cc: 'openhpi-devel@lists.sourceforge.net'
>>> Subject: Re: [Openhpi-devel] HPI GUI application proposal
>>>
>>>
>>> Corrent.
>>>
>>> I suggest new su
; From: anton@pigeonpoint.com [mailto:anton@pigeonpoint.com]
>> Sent: Thursday, May 27, 2010 3:35 PM
>> To: openhpi-devel@lists.sourceforge.net
>> Cc: 'openhpi-devel@lists.sourceforge.net'
>> Subject: Re: [Openhpi-devel] HPI GUI application propos
forge.net'
> Subject: Re: [Openhpi-devel] HPI GUI application proposal
>
>
> Corrent.
>
> I suggest new subdirectory here:
> http://openhpi.svn.sourceforge.net/viewvc/openhpi/
>
> At the same level as openhpi, hpiview, hpiview2, subagent.
>
>Anton Pak
&g
main openhpi development tree. Is that
> right?
>
> --michael
>
>
>> -Original Message-
>> From: anton@pigeonpoint.com [mailto:anton@pigeonpoint.com]
>> Sent: Thursday, May 27, 2010 3:16 PM
>> To: openhpi-devel@lists.sourceforge.net
>>
y, May 27, 2010 3:16 PM
> To: openhpi-devel@lists.sourceforge.net
> Subject: Re: [Openhpi-devel] HPI GUI application proposal
>
>
> My proposal is to organize it in the same way as for existing
> hpiview or
> pyOpenHPI:
> - openhpi and hpiview are in the same SVN repo. (not su
We include the GUI application source
>> code in the
>> > OpenHPI project - but in order for it to compile - the use
>> must first
>> > download the QT4 libraries? In other words, we include the
>> HPI GUI - but
>> > not the QT4 libraries - in the OpenHPI project?
>&g
t
> Cc: 'openhpi-devel@lists.sourceforge.net'
> Subject: Re: [Openhpi-devel] HPI GUI application proposal
>
>
> Michael,
>
> Yes, it requires QT4.
> Yes, one need to have Qt4 for compilation (like glib or
> openssl for OpenHPI).
> Dan pointed out there is
m [mailto:anton@pigeonpoint.com]
>> Sent: Thursday, May 27, 2010 2:27 PM
>> To: openhpi-devel@lists.sourceforge.net
>> Subject: Re: [Openhpi-devel] HPI GUI application proposal
>>
>>
>> Great! BSD license works!
>>
>>Anton Pak
>>
>>
ginal Message-
> From: anton@pigeonpoint.com [mailto:anton@pigeonpoint.com]
> Sent: Thursday, May 27, 2010 2:27 PM
> To: openhpi-devel@lists.sourceforge.net
> Subject: Re: [Openhpi-devel] HPI GUI application proposal
>
>
> Great! BSD license works!
>
>Anton Pak
>
Great! BSD license works!
Anton Pak
> anton@pigeonpoint.com pÃÅ¡e v ÄŒt 27. 05. 2010 v 16:03 -0400:
>> 1. We are fine with BSD license and PPS copyright note in the
>> source files. In the same fashion like in OpenHPI source code.
>> However QT4 is LGPL2/GPL3 and I read there were incompa
anton@pigeonpoint.com píše v Čt 27. 05. 2010 v 16:03 -0400:
> 1. We are fine with BSD license and PPS copyright note in the
> source files. In the same fashion like in OpenHPI source code.
> However QT4 is LGPL2/GPL3 and I read there were incompatibility
> issues with the original BSD license.
mpany
> 3404 E. Harmony Rd. Bldg. 5L, Post B7, Mailstop 42
> Fort Collins, CO 80528-9599
> Phone: 970-898-4393
> E-Mail: michael.bis...@hp.com
>
>
>
>
>> -Original Message-
>> From: Anton Pak [mailto:anton....@pigeonpoint.com]
>> Sent: Thursday, May 2
g. 5L, Post B7, Mailstop 42
Fort Collins, CO 80528-9599
Phone: 970-898-4393
E-Mail: michael.bis...@hp.com
> -Original Message-
> From: Anton Pak [mailto:anton@pigeonpoint.com]
> Sent: Thursday, May 27, 2010 11:56 AM
> To: OpenHPI-devel
> Subject: [Openhpi-devel] HPI GUI
Anton Pak píše v Čt 27. 05. 2010 v 21:56 +0400:
> Hello All!
>
> There is a small QT4 based HPI application that shows information about
> HPI service:
> Domains, RPT, Entities and so on.
> The main idea is to present HPI system in an hierarchical tree and allow
> to walk over it.
> I've atta
Hi Anton,
it looks very good!I think such a GUI is the right way and a thing which is
really missing in the openhpi projekt at the moment.
Lars
On Thursday, 27. May 2010 19:56, Anton Pak wrote:
> Hello All!
>
> There is a small QT4 based HPI application that shows information about
> HPI servic
enHPI-devel
Subject: [Openhpi-devel] HPI GUI application proposal
Hello All!
There is a small QT4 based HPI application that shows information about
HPI service:
Domains, RPT, Entities and so on.
The main idea is to present HPI system in an hierarchical tree and allow
to walk over it.
I've
23 matches
Mail list logo
