Zane,
Thank you. I have added ASL 2.0.
Drago
On 8/28/14, 9:10 PM, Zane Bitter zbit...@redhat.com wrote:
On 28/08/14 13:31, Drago Rosson wrote:
You are in luck, because I have just now open-sourced Barricade! Check
it
out [4].
[4]https://github.com/rackerlabs/barricade
Please add a license
Timur,
I am excited to hear that you think that Barricade could be used in
Merlin! Your feedback is fantastic and I am impressed that you have been
able to understand Barricade so well from only the source and the spec.
I am replying to your feedback inline:
On 8/29/14, 2:59 PM, Timur Sufiev
Drago,
It sounds like you convinced me to give D3.js a second chance :). I'll
experiment with what can be achieved using force-directed graph layout
combined with some composable svg object, hopefully this will save me
from placing objects on the canvas on my own.
I've read the barricade_Spec.js
Hello, Drago!
I'm extremely interested in learning more about your HOT graphical
builder. The screenshots you had attached look gorgeous! Yours visual
representation of Heat resources is much more concise and simple than
I had drawn in Merlin PoC mock-ups [1]. On the other hand I have some
Timur,
Composable entities can be a real need for Heat if provider templates
(which allow templates to be used as a resource, with a template’s
parameters and outputs becoming properties and attributes, respectively)
are to be included in the app. A provider template resource, since it is a
On 28/08/14 13:31, Drago Rosson wrote:
You are in luck, because I have just now open-sourced Barricade! Check it
out [4].
[4]https://github.com/rackerlabs/barricade
Please add a license (preferably ASL 2.0). Open Source doesn't mean
the source is on GitHub, it means that the code is licensed
David,
I'm happy to hear that :)! After thinking a bit, I came up with the
following strategy for further Merlin development: make all the
commits into a separate repository (stackforge/merlin) at least until
the PoC is ready. This will allow to keep project history more
granular instead of
On 8/6/14, 1:41 PM, Timur Sufiev tsuf...@mirantis.com wrote:
Hi, folks!
Two months ago there was an announcement in ML about gathering the
requirements for cross-project UI library for
Heat/Mistral/Murano/Solum [1]. The positive feedback in related
googledoc [2] and some IRC chats and emails
Hi, folks!
Two months ago there was an announcement in ML about gathering the
requirements for cross-project UI library for
Heat/Mistral/Murano/Solum [1]. The positive feedback in related
googledoc [2] and some IRC chats and emails that followed convinced me
that I'm not the only person
