From: Frederik D. <fre...@we...> - 2002-12-15 17:27:34
|
> [snip] > > Too bad. :/... does general CVS have these limits, or is SourceForge > using some security restrictions? These are limitations from sourceforge. If I would have shell access, I could easily do a "rm -r org" and your problem would be solved ;-) > > > >No problem. I would rename it to "python" but future plans are to make > >it available as separate download, which just needs to be added to the > >program-/config-folder. > > I have not understood this. > Anyway, what are the .py.class files? > [Don't ask me to open them in notepad, please :P] Sorry. These are the libraries for the python scripting support. I will remove the Lib directory in the future. So, for using python in Columba you will need to download the python-package. > > > >every module in src contains the folders (when needed): > >- independent (this is for code usable also for third party people, > for example our > > imap implementation could be used by other programs, too. Another > example are > > common gui-elements which can be re-used) > > This means that a dialog or a wizard is not independent, right? > Who would need to use a columba wizard? I'm talking about the infrastructure for creating wizards ;-) This is independent. But no one would be interested to use our AccountWizard. Actually all the code in "core" is code which is shared by mail and addressbook. > > GlobalResourceLoader could be inside independent, though. So, your GlobalResourceLoader is already shared and used by mail and addressbook! > > >- test (all the test-cases for the module) > > How does this work? > How do I enable a test? I'm talking about test-cases written with the junit framework. Basically, we wanna have test-cases for all important parts of the code, to test them individually. Test-cases can be combined in a test-suite. For example: Imagine someone wants to write a new folder-type (maybe with a database as back-end). He/She would just write it down and start the folder test-suite. If all the tests run without errors the folder is working. You should talk a look at www.junit.org for more information and examples. Writting test-cases is a good way of contributing to Columba ;-) > > > >I don't like the core/core either. We need to make the decision if > its better to remove one > >level of "core" or we keep it for better consistency to the modules > mail and addressbook. > > The first "core" can be changed to "columba" or "columba-core". > "columba" is better, since it has less "core" in it :P So, we would have "/src/columba/core". This is what most people suggest. I like this idea, too. We should also consider moving /src/main into /src/columba/core, to make things even clearer. > > > [src & resources] > >This is also something worth discussion. > > I don't even think it to be worth discussion :D Just split source and > resources :D We need to check first, if we need to change the sources for that and what the needed changes for the build.xml are. If these things are all ok, I say, too: just split it! > > > [Options and configuration] > >Yes exactly. Tony Parent contributet the new configuration back-end. > It uses a > >sax-based callback parser, which means better performance. As a nice > add-on > >we have less memory consumption, smaller/easier datastructures, etc. > > Without having to read the posts, can you write here two examples of > how the new option "API" will work? We have three config objects which can be accessed statically: - Config - MailConfig - AddressbookConfig > > > Example a) Suppose I need to know if the main columba window was > maximized when it was closed. What code returns me this boolean result? if you want to have your maximized config option: XmlElement windowElement = MailConfig.get("mainframeoptions","/options/gui/view/window"); boolean isMaximized = windowElement.getBoolean("maximized"); XmlElement is representing a treenode with a parent, children, a value and attributes. You can easily create your own config-nodes: XmlElement window = new XmlElement("window"); window.addAttribute("maximized","true"); > > Example b) Suppose I need to know the name of the font which is used > by the message composer during the composition of a message. > What code returns me this String result? GuiItem guiItem = new GuiItem( Config.get("options","/options/gui") ); Font textFont = guiItem.getTextFont(); GuiItem is just a wrapper class which transforms the font-name and size to a Font class. > > > >We completly rewrote all config-files. So you have to basically > delete your config-folder > >and start from scratch. The benefits are of course worth it: > > I already destroyed everything just to test the fixed options which > didn't increase the xml size endlessly ;-) Loading times dropped from > 25 seconds to 5 seconds... ;-) damned bugs! Yeah, took some time to track down. > > > >We are at the moment working on another branch and will warn everyone > when > >merging. > > Why aren't you putting this in the "test" folder? What is the use of > the test folder? :-) Already answered above. Such big code re-organisations should be better handled in using branches. [snip] > I executed a small java application and the menu had HUGE fonts. I'm > currently using KDE but I configured GTK's interface too (I think) > when I configured XMMS. Java applications show even different fonts > and sizes. Where do I configure them? ?__? > > Hrk Columba has this option ;-) Sadly there is no such thing as a central font configuration in Linux. You have to configure fonts for kde and gnome application separately. Same applies for java apps. Theirs a font.properties file in your java-folder where you can customize the fonts to your needs. Cheers, Frederik |