[Drawkit] Strategy for managing updates to drawkit?

[Graham Cox]

This is rather a broad question. It's hard to answer definitely,  
because it will depend on what you want to do.

The demo app is a good example if you are using DrawKit in a similar  
way - in particular it follows the current recommendation that you set  
up a common build folder for the framework and the app, and have the  
app project include and depend upon the framework project. That way,  
you will always build the framework before it gets included in the app  
(only done once if it never changes). When there's a DK update, you  
should be able to replace the DrawKit folder complete, then simply  
build your app to update. Once we have an SVN repo up and running that  
you can update from, this is even easier as there's no manual folder  
replacement needed.

Structurally, I don't expect to be changing the layout of the DK folder.

hth,


Graham


On 17 May 2008, at 12:25 am, Steve Weller wrote:

>
> If I use DrawKit in my app, how should I integrate it? Is there a  
> recommended way of adding the files or structuring the folders?
>
> And when updates are available, what should my strategy be for  
> updating?
>
>
> _______________________________________________
> Drawkit mailing list
> Drawkit at lists.apptree.net
> http://lists.apptree.net/listinfo.cgi/drawkit-apptree.net