[gsoc-dev] (no subject)

pranjal mittal mittal.pranjal at gmail.com
Sat Aug 17 11:32:57 UTC 2013


On Sat, Aug 17, 2013 at 4:55 PM, pranjal mittal <mittal.pranjal at gmail.com>wrote:

> Hello Lance,
>
> I have improve instance placement now [1], by adding a panel-layout on the
> right that shows all
>

(Phew, Typos make things look so silly. Please excuse) * I have *improved *the
instance placement


> the primary instances corresponding to the node you clicked on.
>  Further if you click on an instance in this panel the Failover Edge is
> highlighted, and there should be no clutter between the instances on the
> graph and the edges between nodes now.
>
> This panel is visible only after you click a node and expands vertically
> depending on the number of instances. (The position of this panel is fixed
> for now)
>
> Further wanted to mention, that there is alphabetical sorting of instances
in this panel.
So "instance101.example.com" comes before "instance11.example.com"


> Also, I have (deliberately) not removed the "ingraph instances placement"
> completely. Its merely hidden to avoid any clutter.
> Keeping the "ingraph instances" alive, is important so that some other
> features, including the - *'s' feature *(Show me secondary instances)
> feature, do not break.
>
>
> & yeah!  "Additional Instance Information to be shown"
> Have this issue in mind -> Next on my TODO. :)
>
> Do let me know of further improvements to this instance placement here,
> (or as an issue) on [2]
> Perhaps -
>
>    - Color scheme for the right panel?
>    - Alternating between color / contrast for each list element, so that
>    each instance cell is delineated from the others?
>
>
> [1] http://pramttl.github.io/
> [2] https://github.com/pramttl/ganetiviz-cytoscape
>
>
>
>
> P.S:
> Here is a link to the docs of the framework I am using.
> cytoscape.github.io/cytoscape.js/
> They have an interesting enhancement in development that allows different
> layout's for a (subset) collection of graph elements, which is
> NOT available till now (includes grid layout) (That could be something
> useful to us in future for dynamic placement of instances in a grid fashion
> near a node.)
> Hope this information was useful.
>
>
> Thanking You,
> Kind Regards,
> - Pranjal
>
>
>
>
>
> On Fri, Aug 16, 2013 at 10:46 PM, Lance Albertson <lance at osuosl.org>wrote:
>
>> [adding back to gsoc-dev so other people can chime in too]
>>
>> It doesn't have to be a literal table for the grid layout. It can be
>> whatever element-style works best for the framework you're using. I just
>> don't think a circular layout for the instances is ideal for this.
>> Adjusting the cell-size might be way way around it, or if there are other
>> UI methods that work too I'm not sure.
>>
>> Also it doesn't have to be dynamic in where it places the grid. If it
>> works better to have a default place for that, then go for it. I think the
>> overall goal I was going for was trying to keep the instance placements
>> away from the inter-node relationship lines and having them organized in a
>> more grid-like fashion. I'm not sure what the limitations of the framework
>> you're using are but if you have a few examples I can look at I can give
>> you some pointers.
>>
>> Thanks!
>>
>>  On Fri, Aug 16, 2013 at 8:08 AM, pranjal mittal <
>> mittal.pranjal at gmail.com> wrote:
>>
>>>  An additional idea.
>>>
>>> The number of instances for each node will be variable.
>>> Acc. to me, It won't be so cool to have grid element of varying sizes
>>> depending on the number of instances. Instead what I could try to do is to
>>> adjust the  cell size as per the number of instances so that overall size
>>> of the table remains same?
>>>
>>> ^ What do you think?
>>>
>>>
>>> On Fri, Aug 16, 2013 at 7:51 PM, pranjal mittal <
>>> mittal.pranjal at gmail.com> wrote:
>>>
>>>> Hmm, this helps good.
>>>> Although, I am confused about how can I vary the position of the grid
>>>> (table) element to fit the nearest white-space next to a node.
>>>>
>>>> Cytoscape JS allows drawing vertices and edges and treat them as html
>>>> elements over a canvas.
>>>> It does not allow drawing Table elements on the canvas. Table can be
>>>> drawn over the body or div independently without any relation to the
>>>> position of the nodes on the canvas. (because positions on the canvas do
>>>> not relate to the position on the page.)
>>>>
>>>> I will start with a fixed grid layout on the page and then later see if
>>>> this could be made better, with dynamic placing of the grid element.
>>>>
>>>> Will that be ok?
>>>>
>>>
>> --
>> Lance Albertson
>> Director
>>  Oregon State University | Open Source Lab
>>
>
>
>
> --
> Best Regards,
> Pranjal Mittal
> B.Tech.  2014
> Indian Institute of Technology,BHU
> Varanasi, U.P,
> India
>
> Github <http://github.com/pramttl> | LinkedIn<http://in.linkedin.com/pub/pranjal-mittal/26/660/318/>|
> Blog <http://pranjalmittal.in>
>
> _______________________________________________
> gsoc-dev mailing list
> gsoc-dev at lists.osuosl.org
> http://lists.osuosl.org/mailman/listinfo/gsoc-dev
>
>


-- 
Best Regards,
Pranjal Mittal
B.Tech.  2014
Indian Institute of Technology,BHU
Varanasi, U.P,
India

Github <http://github.com/pramttl> |
LinkedIn<http://in.linkedin.com/pub/pranjal-mittal/26/660/318/>|
Blog <http://pranjalmittal.in>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/gsoc-dev/attachments/20130817/55a52ad2/attachment-0001.html>


More information about the gsoc-dev mailing list