This is too much for many people to both read and answer.
I gave me a kik and do it anyways.
Klemens Friedl wrote:
> ReactOS 'Support Database' for the new ReactOS Homepage
>>> The 'Support Database' will contain the following 'databases':
>> * Compatibility Database (application, driver and hardware)
> * Package Database (a list of download-able applications/driver; principal
> for the ReactOS Package Manager)
> (* Media Database (like the ReactOS Fansite Media Database; maybe we can
> implement this later))
I think the first 2 is the minimum we need. I'd rather say for the first
step this would also be enough. Application compatibility, Locations of
working packages. This can be ONE DB.
A Media DB is not needed, just a link collection. Maybe it's just easier
to generate this from a db-table. But where's the difference between
filling a file or a DB
> The 'Support Database' (project codename 'RosDB') will base on the package
> manager alpha page that i have created april 2005.
ok
>> Note: the package database will be combined with the compatibility datbase.
> Both 'databases' will share the same 'application tree'! So it will be easy
> e.g. you browse the compatibility db, you found a working app and think, "i
> also want to download this app", then you will be able to click on a link
> (on a central position) and you will be redirected to the package database.
> In near future it should be possible (if you run ReactOS or Win32 with
> installed and runing ReactOS Package Manager), that you can select your
> favorite apps/driver you want to install (navigation like
> amazone/ebay/compatibility db) and then click install (a normal link on the
> package manager page) and your running (maybe as a service) ReactOS Package
> Manager check/capture every clipboard item and if it is a valid 'package
> style link' then it will connect to the online database and download all the
> selected apps/driver and download it from mirror server (from their
> developers/sourceforge/etc.) and then install all items (without or with
> minimum of user interaction). In my (frik85) opinion, that would be one of
> the 'hottest' feature someone can imagine (in connection with a homepage,
> package manager, etc.).
> This feature will became a main feature and everyone will use that *hope*
> for ReactOs and also possible for Win32 (from MS). :) -- frik85
I think that's good, amazing and can support that decision. (Merge both
DBs)
>>>> "ReactOS Compatibility Database
> ReactOS has an Compatibility Database where Windows
> application/driver/hardware compatibility is recorded. Registered users can
> submit new items, and comment on existing ones. Screen shots are also
> available for many apps. Users can also vote on their favorite apps." -- a
> possible description
I've never seen a compatibility DB, hoewve I can imagine this:
An app can have several versions.
Each version can have several Variants (eg. Shareware, Dongled, free)
Each of these tuples can have different requirements in terms of dll and
drivers /services
And thus make compat. fail or succeed.
Compatibility is in my Eyes a multi-step (eg. Not at all, Dies at some
action, works but this means work by user, works just fine + errors,
perfectly, .... more)
Every such tuple shall have a note, and voting+comment info for
end-users (n-times) to vote on whether it works or not.
*Tested on What reactos version
*if problems occoured, what to do
*What do I need
*Associate a download like a patchfile?
*associate a pic (screenshot )`(nice to have)
Information should be delegated further with some kind of hint.
eg. If App v1 works, and App v2 has no information about, The system
could show "Is suspected to work since v1 worked" or "No info, but see
[App v1] as most simmilar"
The same shall happen if App v3 variation x has info while App v3
variation z has no info. That's even more suspectable for it to work,
too. So a more sure hint may be shown.
Information about compatibility of several drivers, dlls and services
shall be collected, too. With the knowledge of the requirements of an
app, we can infer the information of wheter an app is supposed to work
or not.
OK, this becomes sofisticated. But a DB should be defined from begin on
full, souldn't it?
>> Management Issues/Goals:
>>> We need a high 'input data quality', then the administration work will be a
> minimum.
> To reach this high data quality, i want to code a simple to use wizard for
> the 'submit item' page.
> You can view the sample wizard on the package manager alpha page (see link).
>>> Have some form of a moderation system to let end users know the quality of a
> given persons entry.
> Maybe like the appDB from winehq? Where a registered user can ask for a kind
> of moderator right for one specific item (e.g. application), so he can
> manage the comments, add new info, etc.
> -> taking ownership of an item (e.g. application): monitor comments on it,
> track bugs (close bugs), and make sure quality level is high for application
> description.
>
I see it as this: Let someone of ours have the apps entered and let
people vote about wheter an app works or not. The wiki principle
applies. Of couse we can vote, too.
> NO redundant entries for the same product! We need moderators who review all
> new entries. The moderators should be able to read as many comments as
> possible and help the normal users, report bugs to the bugzilla system, etc.
>
sure
>> Reviews (aka user comments) should expire. (expire time 1 year?)
>
????
>> Track hit counts on each item (auto magic way of knowing which apps are most
> desired) and maybe voting like in appDB (WineHQ) or in C4 (CodeWeaver).
nice to have, but at least a good idea
> "Idea: Tie the apps database to the api database. The idea is that we know
As i sayd before
>> "Idea: Tie the apps database to bugzilla. If users have a problem with an
> app, it's a bug, and should be in bugzilla. If we can get to a point where
> we can easily get a report that says 'here are all the bugs that Quicken
> depends on'. Or, here are the five bugs, the fixing of which will make 50
> apps suddenly work. This would be wicked cool." -- winehq newsletter from 18
> Oct 2000
>> Note: the bugzilla will be a subsystem of the RosCMS, so it will be (maybe)
> possible to implement the idea above. Is something like this usefull for
> someone? -- frik85
I can't imagine this. I'd vote against
>
More information about the Ros-dev
mailing list
CHAPTER VII. THE FOUR CLASSES OF SOCIETY. THE FOUR CLASSES OF SOCIETY. "After the herald had given the names of the wrestlers who were to make the first round, the fellows came in. They were dressed without any clothes to speak of, or rather they were quite undressed, with the exception of a cloth around their loins. They came in on opposite sides of the ring, and stood there about five feet apart, each man resting his hands on his knees, and glaring at the other like a wild beast. They[Pg 231] looked more like a pair of tigers than human beings, and for a moment I thought it was not at all unlike what a bull-fight in Spain might be. I turned upon her choking with anger, but her melting beauty rendered me helpless. Black woods were on our left. "Shall we turn in here?" I asked. "None of that with me," he growled. "Do you know who I am, Countess Lalage? I am Leon Lagage, Count of the Holy Roman Empire, and your husband. Incomparable woman, you cannot alter that fact. For better or worse, for richer or poorer, till death do us part!" I have in this way imperfectly indicated a methodical plan of generating a design, as far as words alone will serve, beginning with certain premises based upon a particular work to be performed, and then proceeding to consider in consecutive order the general character of the machine, mode of operation, movements and adjustments, general arrangement, strains, special arrangement, and proportions. ‘Alas! what is life, what is death, what are we, 11th January two best dresses. Commencement was as usual, with a few showers “All right,” agreed Sandy. “Dick, you and I are the ground crew. As soon as you’re ready, Mr. Whiteside, we’ll take hold!” Effects of Walpole's Administration—Formation of the new Ministry—Attitude of the Malcontents—Committee of Inquiry into Walpole's Administration—Walpole's Protectors—Ministerial Measures—Prorogation of Parliament—Disasters of the French—British Division in the Netherlands—Opening of Parliament—The German Mercenaries—Amendment of the Gin Act—George goes to Germany—Stair and De Noailles in Franconia—Stair in a Trap—Bold Resolution of King George—The Battle of Dettingen—Resignation of Stair—Retreat of the French—Negotiations for Peace—Treaty of Worms—Pelham becomes Prime Minister—The Attacks of Pitt on Carteret—Attempted Invasion of England—Its Failure—Progress of the French Arms—Frederick II. invades Bohemia—His Retirement—Resignation of Carteret—Pelham strengthens his Ministry—Death of the Emperor—Campaign in Flanders—Battle of Fontenoy—Campaign of Frederick II.—The Young Pretender's Preparations—Loss of the Elizabeth—Landing in the Hebrides—The Highland Clans join him—The First Brush—Raising of the Standard—Cope's Mistake—He turns aside at Dalwhinnie—Charles makes a Dash for Edinburgh—The March to Stirling—Right of the Dragoons—The "Canter of Coltbridge"—Edinburgh surprised by the Highlanders—Charles marching against Cope—Battle of Prestonpans—Delay in marching South—Discontent of the Highland Chiefs—The Start—Preparations in England—Apathy of the Aristocracy—Arrival of the Duke of Cumberland—Charles crosses the Border—Capture of Carlisle—The March to Derby—Resolution to retreat—"Black Friday"—The Retreat—Recapture of Carlisle—Siege of Stirling—Battle of Falkirk—Retreat to the Highlands—Cumberland's Pursuit—Gradual Collapse of the Highlanders—Battle of Culloden—Termination of the Rebellion—Cruelty of the Duke of Cumberland—Adventures of the Young Pretender—Trials and Executions—Ministerial Crisis. The next morning he was up betimes, and cooked the boys as good a breakfast as he could out of the remainder of his store and what he could get from the hospital, and then gave what was left to whoever came. The comfortable crib, which had cost the Deacon so much labor, had been pre-empted by the Surgeon for some of his weakest patients. "You two step forward one pace," he commanded. "Gentleman, I've got my six. The rest are yours." "Where are you goin'?" he said sternly. Every now and then the crowd would break into the latest rhymings of MacKinnon's poet: A large thicket, at this moment, gave the dusty foot an opportunity of doubling, and, for an instant, diverging from the straightforward course, though it availed him little, he seemed to feel the breath of his pursuer on the back of his neck; his foot sounded as if at his heels; he drew his garment closely around him, turned suddenly to the right, and, bounding from the ground, the next instant a splash was heard in the little river, and the fugitive was safe from his pursuer. HoME明日之后怎么免费刷一级纳米材料
ENTER NUMBET 0018www.sb9hii5p.com.cn jy-fuding.com.cn cqcq06.com.cn haoke168.com.cn www.socway.com.cn zhunta.com.cn mysimon.com.cn www.go616.com.cn www.bmdl747.com.cn 16a.net.cn