El dt 27 de 03 del 2007 a les 14:15 +0200, en/na Matthijs ter Woord va escriure: > Hi Lluis, > > > On the other hand NApf is more focused on building an application > > framework. It has an add-in engine similar to Mono.Addins (since it is > > based on the SharpDevelop engine), although it isn't probably as > > optimized as Mono.Adidns (it's just a guess, since I haven't analyzed > > the code). In addition to add-in engine it offers other modules for > > managing settings, logging, and other high level UI components. That's > > not covered in Mono.Addins and never will. > > > > NApf's modules are just addins providing you with basic/standard > functionality common in many applications. > > > > Maybe we should have a chat once, about how different NApf's core (the actual > addin engine) is with Mono.AddIns, so we can maybe share ideas/merge or what > ever. > > Is this something you would be interested in?
Sure, pretty much. I'll take a more detailed look at the NApfs code to see the main differences. Lluis. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
