Micha Bayer wrote: > Hi Jari, > > That sounds perfectly reasonable when you put it like this, but I was put off > going down that route by a post to the list from Nicklas > (http://www.mail-archive.com/basedb-users@lists.sourceforge.net/msg00228.html) > where he says that it is best to not use a plugin to do this because of > interface issues (whatever they are).
I think Nicklas was thinking about very interactive plug-ins. > Personally, I think a plugin would be far better than what I have done -- if > I was to persist with my solution I would have to modify the BASE source > every time a new version comes out. Our belief is that basically no modification to BASE is needed if one creates a import plug-in that creates all needed items automatically (using information from files of course). Trouble starts when communication is needed from the user after plug-in start. The plug-in system allows for communication just before a plug-in is started (at least was design like this, I suppose one can tweak user interaction with the plug-in but thats out of this topic). > I also think that batch import *is* a high priority thing for most users, > whether they have a pile of legacy data or not. Most biologists I know would > probably rather spend a solid period doing labwork, and then process a whole > bunch of experiments in a oner. I also think it is a nonsense to have a human > doing boring, repetitive stuff -- computers are there to do that. Why waste > your time on something that a for loop can do. So perhaps the dev team should > reconsider this. I agree, I think it is an important issue as well. However, we think that we work on many other important issues already. We are mainly working on core stuff and hoping that others contribute with things that can be written as plug-ins. You are already doing this, and unfortunately you were pushed in the wrong direction. > I am just talking to my boss about code ownership issues but I can probably > offer up my stuff one way or another, and people can then either cannibalise > it and turn it into a plugin, or adopt it (or a modified version) into the > core etc etc -- happy with any solution that makes others benefit from my > blood sweat and tears shed ..... :-) > Dominic would probably benefit from your code and through him the code will probably end up in the BASE repository. Contributions are welcome and we consider all of them for inclusion the the BASE code base. > Cheers > > Micha > Cheers, Jari ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to [EMAIL PROTECTED]
