#11 library
Would be very nice to be able to store elements in
a 'library' which would be a place where geometry could be
reused by drag/drop onto the canvas. To create the
element, you could drag/drop into the library, and the library
gui would be a panel (seperated from main app via
splitpane or something) which would display a
reduced 'snapshot' of the library item and optionally it's
name. Libraries would need to be externally persistable
(external to the drawing file) in order to be loadable into
many different sessions. This would pretty much be
idential in concept to Visio. This was one feature in JGraph
that made it more appealing for me than JHotDraw, but I
know it wouldn't probably be terribly difficult to implement
given the well thought out design.
Great effort everybody, this is a really neat project!
Logged In: YES
user_id=280374
I am working on this functionality. I tis the reason I
added the Drag n drop tool. it is also the reason I worked
on the Desktop structure.
But the full functionality is not part of the library. you
need some way to manage the files and reopen them. perhaps
Ill add a demo app to show what I have been doing. but its
just an example.
Logged In: YES
user_id=105573
Not sure I understood your second paragraph, but I'll await the
demo and it will probably make sense then.
Thanks!
Logged In: YES
user_id=280374
What I mean is, demo apps such as javadraw are not part of
the library per se. they are for example. the user must do
his own implementation.
But I did do an app that had images on a side panel that
drops into another panel. lately I am cleaning up other
areas of the code so it may be a while for the app. have
you made any apps yet with JHD?
Logged In: YES
user_id=403318
adding created objects to a library is a genius idea! I've
created a very basic graphical representation of this idea here:
http://research.salutia.com/tiki/tiki-index.php?page=TikiDraw#
scroll down to see my simplistic representation
dgd
Logged In: YES
user_id=280374
You can rest assured I will be implementign this. I did it
before but didnt like all the hoops I jumped through.
I basically started my project using Visio, VisualBasic, and
Access. (in truth I started even earlier with java and
VisualCafe before I found JHD)
so I am dead set on getting the visio functionality. I even
made the side tabs to move to the top and bottom like visio
did in visio 2000.
sooner or later...
Logged In: YES
user_id=1043393
A work-around I'm using is to put a hidden drawing in the
editor and crate a series of commands to:
1. load the hidden drawing,
2. tag figures on the visible drawing with a replacement
figure's name,
3. perform a 'search and replace' of tagged figures in the
visible drawing with figures from the hidden drawing whose
name matches the replacement tag.
You then create a drawing with the desired library figures
(presumably very complex composite figures) and save it.
Put very simple placeholder figures (I use rectangles) on the
drawing in the desired locations, and tag them for
replacement. Load the library drawing and issue the replace
command.
I implemented this aproach in a commercial product based on
JHotDraw in 3 to 5 days. My implementation is completely
based on attributes so you'd also need a mechanism to
inspect the attributes of the drawing and figures.
Logged In: YES
user_id=1043393
A work-around I'm using is to put a hidden drawing in the
editor and crate a series of commands to:
1. load the hidden drawing,
2. tag figures on the visible drawing with a replacement
figure's name,
3. perform a 'search and replace' of tagged figures in the
visible drawing with figures from the hidden drawing whose
name matches the replacement tag.
You then create a drawing with the desired library figures
(presumably very complex composite figures) and save it.
Put very simple placeholder figures (I use rectangles) on the
drawing in the desired locations, and tag them for
replacement. Load the library drawing and issue the replace
command.
I implemented this aproach in a commercial product based on
JHotDraw in 3 to 5 days. My implementation is completely
based on attributes so you'd also need a mechanism to
inspect the attributes of the drawing and figures.