Having read through some of the recent stuff I suddenly realised a
fundamental point of the original conversation I had with Stefano that
kicked off a lot of the discussions might have been missed, so I am
going to try and note it here just to be sure, to be sure.
This all started because a little
On 16/02/16 16:27, John Crisp wrote:
So the point of the exercise was never to prove that one panel system or
framework was better than another. Nor was it to say definitively we
should use cockpit. We were really trying to find solutions to a couple
of issues we (SME) have had for a longtime.
Il 16/02/2016 18:43, Jim McLaren ha scritto:
One quick question. Would it be any harder for someone such as
yourself to write a panel with mojo as a framework, rather than
cockpit? IOW once a new server-manager has been written with
Mojolicious is it as easy to use thereafter?
I'll try t
On 17/02/2016 5:20 AM, Stefano Zamboni wrote:
> Il 16/02/2016 18:43, Jim McLaren ha scritto:
>>
>> One quick question. Would it be any harder for someone such as yourself to
>> write a panel with mojo as a framework, rather than cockpit? IOW once a new
>> server-manager has been written with Mojol
> I had a lot of long chats with Filippo last year at FOSDEM. FormMagick
> was just one of the reasons they went their own way. They wanted
> something that might attract devs with some general coding skills that
> are easily available today. HTML/CSS/JS are clearly popular. Lets leave
> out PHP as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 17/02/2016 15:20, Filippo Carletti a écrit :
> But NethGUI, while aesthetically appreciated, is still hard to use
> (ask Stephane or Giacomo :-) ).
mort de rire :) LOL
- --
Cordialement
Stéphane de Labrusse
Membre de l'Aru2Lhttp://www.aru2L
On 17 February 2016 15:20:04 CET, Filippo Carletti
wrote:
>> I had a lot of long chats with Filippo last year at FOSDEM.
>FormMagick
>> was just one of the reasons they went their own way. They wanted
>> something that might attract devs with some general coding skills
>that
>> are easily avail
> If you started from scratch today, with a clean sheet, what would you use ?
I'm relaying other's opinions. Our #2 rule is "follow upstream", so I
must say "cockpit".
A second choice would be angular+nodejs, because we have a lot of
expertise here.
> PS great night again with you team in Brusse
