Hi all, I started to separate the GUI code from library code. We have now two files: MAC.pm for the library code and GUI_MAC.pm for the GUI code. Note that a MACops.pm is already existing and duplicates some code.
I did some basic tests and everything seems to be fine using the GUI. I did not check for the CLI but it should work. Let me know if you have any problem. It is just a first step, a lot has to be re-organized/cleaned-up. I will try to have a look within the new few weeks, but any help is welcome. :-) Regards, On Monday 22 January 2007 11:47, Thomas Naughton wrote: > As for the MAC.pm related aspects, I can't speak for Wesley but I'm pretty > sure things were done to avoid interruption and duplication as much as > possible. > > Also, I seem to remember that this MAC.pm was initmately tied to the GUI > which had a load of problems. The main thing to remember is that we want > to keep library routines as vanilla as possible in order to keep the same > code path for the GUI & CLI, minus the user interface aspects. > > So, if we're doing something specific for the CLI or the GUI that could be > done in a more generic (reusable) manner then please make the changes in > that direction. Otherwise, I think we need to make the effort to think how > we can make things more generic and reusable by both CLI & GUI to make > testing much easier in the long run. -- Geoff ------------------------------------------------------------------------- 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 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
