Luigi, I should have waited to post until I thought about Studio being a plugin itself! I'll start with a separate copy and experiment, and report back my results.
Thanks again for responding to what should have been an RTFM question :) On Wednesday, April 1, 2015 at 7:52:10 AM UTC-4, Luigi Dell'Aquila wrote: > > Hi Cameron > > Studio at this time does not have an internal structure for plugins and > there are no plans for that, but you know, many decisions come from > community needs, so if it's a common need we can think about it. > At a higher level, OrientDB itself has a plugin architecture and Studio is > actually a plugin. You could create another plugin with additional features > just copying Studio and it would live together with Studio without any > problems. > > Regards > > Luigi > > > > 2015-03-31 20:48 GMT+02:00 Cameron Hunt <camero...@metanomy.org > <javascript:>>: > >> Luigi, >> >> I'm also interested in contributing improvements and extensions to >> Studio. Before I just start making a mess, do you know if there are any >> plans to support a plug-in type architecture so that users can contribute >> extensions that won't alter the base behavior, and (hopefully) decrease >> chances that changes to the base code maintain compatibility (to the degree >> it is rational to do so) to the user-contributed extensions? >> >> In the spirit of sharing, here are the use cases I'm looking to develop: >> >> >> 1. Embed the interactive graph in another application. In my >> particular use case, I would want to use a URL with parameters to perform >> a >> query to OrientDB, and return the results as an interactive graph >> embedded >> within another application. >> 2. As a variant to the use case above, I would like to modify the >> graph display behavior so that double-clicking a vertex would only expand >> edges of one or more user-specified edge superclasses. >> 3. Extend the vertex/edge option wheel to include custom icons and >> functions. One use case would be to allow the user to "change" the class >> of >> a vertex by calling a custom script that would create a new vertex under >> the desired class, and copying all properties and relationships of the >> old >> vertex to the new one, and once finished, delete the old vertex. The >> other >> use is sending a parameterized URL query to a mapping application that >> would show me all recent position data (as points) of the vertex in >> question. >> 4. Extending the property type options to include geospatial >> attributes. The use case is that I would like to associate an existing >> and/or user-defined polygon with a vertex. Defining a "polygon" type >> would >> then let the user select or draw a polygon in a pop-up window (in the >> same >> way a user can pick a date from the pop-up for date and datetime property >> types). In my specific case, the polygon itself would be stored as WKT >> <http://en.wikipedia.org/wiki/Well-known_text>, or optionally in an >> external geospatial system (i.e., using WFS-T to an OGC-compliant >> goeserver). >> >> >> On Wednesday, March 25, 2015 at 11:52:32 AM UTC-4, Luigi Dell'Aquila >> wrote: >>> >>> Hi Fabio, >>> >>> OrientDB Studio is open source, you can find source code here: >>> https://github.com/orientechnologies/orientdb-studio >>> It would be great if you could improve the standard behavior and become >>> an OrientDB contributor! >>> >>> Regards >>> >>> Luigi >>> >>> >>> >>> 2015-03-25 14:34 GMT+01:00 Fábio Costa <fcost...@gmail.com>: >>> >>>> I'm developing a software visualization tool and by chance using >>>> OrientDB as the underlying database. As it has a graph visualization >>>> option, I'd like to know if it is open source or how can I customize it. >>>> For now, I just need to show a meaningful name for a vertex instead of its >>>> native id. Later on, it could be very useful to customize edges as well, >>>> with properties such as color, type of line, thickness, etc. Attach >>>> specific visual attributes to specific data without having to select every >>>> single vertex or edge is what I'm looking for. >>>> Thank you in advance. >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "OrientDB" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to orient-databa...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to orient-databa...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
