Monday, February 19, 2007

Is it possible to include a (empty) "skins" folder in the next release?

Sure.

Seems that SETI@Home is a victim of its own success; or maybe a run-away train. Has there been any discussion on methods to allocate resources between projects? For example, implementing a per user work unit limit based on the users contributions to the project; contributions such as money, time, other projects in which user participates.

The philisophy of the BOINC the framework is to let the participants decide how they want to volunteer their resources.  To that end, it is up to each project to sell their project to the community.  Donating computation time to a project is already an expensive proposition, it costs time, electrictity, and internet bandwidth.  To be honest I cannot see a project being successfull if they started selling workunits to process.  At that point I think a project would loose it's fun and cool factors and would find it's big iron contributors defecting to other projects.  Eventually that project would only be left wth the die hard fans wth money to burn and those who were not affected by the cap.

At that point the project is pretty much on life support, and waiting for the people who are funding the project to pull the plug.

What's the development progress in getting the boinc code (I assume 5.9.x now) up to scratch to use wxWidgets 2.8?

Charlie started the port to 2.8, there are a few things on my plate to tackle. Text gets clipped in the wizard for instance. We'll have it up to spec when we start the 5.9-5.10 release push.

Can auto update (I see it in the code for 5.9.x) be turned on in 5.8.8+ or has it been left out?

I'm not sure what the client will do at this point if it receives the auto update tag, it should just be ignored at this point. That feature has another month of work or more before it is ready for use.

What do you think are the major improvement in 5.8.8+ over 5.4.9/11?

There have been so many under the cover improments, I think the big ones are the improved CPU scheduler, the improved work fetech policy, and CPU throttling.  On the Mac we have the sand boxed environment which is a huge improvement.

What are you most chuffed about getting fixed/working/added?

What do you mean by chuffed?

 

To submit questions for next week just click on the comments link below and submit your question.

Thanks in advance.

----- Rom

Monday, February 19, 2007 12:47:23 PM (Eastern Standard Time, UTC-05:00)
To be "chuffed" is to be happy and/or pleased (about/with something)

for example; i was chuffed to fix an ongoing problem last week
Saturday, February 24, 2007 2:45:47 PM (Eastern Standard Time, UTC-05:00)
'chuffed' I guess it is and English word.

'Most happy with'

i.e. Out of all the things you (you personaly) have put in to boinc since the last major release are you most impressed with yourself for actualyl getting to work.

sorry about that.


---

I'll have to think of some mote Q&A's


Thought of one.

How is boinc going to get around the problem on Windows VISTA where you are not suppose to (and often cannot) write to the 'program files' directory.

My thoughts are to do it properly but that may require quite some work.
i.e. You install as normal to the program files directory (as is standard and good practice) but do all the other stuff in the correct user profile directory for the actual altering files.
It does take away simple 'boinc' folder aspect though.

This may explain better what you are
Copy&Paste I had collected from arounf the net ( I think the ms vista newsgroup )


----
The correct location to store machine wide common application data is in the CSIDL_COMMON_APPDATA folder retrieved via the SHGetFolderPath api.

You will also need to ensure the permissions on your file allow full access to the appropriate accounts, such as giving BUILTIN\Users full permission to your file/directory.
----
Comments are closed.

Theme design by Jelle Druyts
Header image by FreeWebPageHeaders