The naming scheme is going to be how Linux names icons themes. For example, the setupapi icons would go into a folder called devices and the computer icon name would become computer just like Linux calls it. The way we are going to use the icons is replace "res/computer.ico" with "../../../media/icons/devices/computer.ico". That way we have one computer icon for the source code as sysdm.cpl, device manager setupapi, etc. all use the same computer icon. Setuapi uses the same icon twice! We won't touch the resource IDs at all. This would be a nice way to shrink the source code size down a bit as we won't have to download the same icon 5 times. The binaries size would remain the same. Sounds would stay in the media folder and animations would move into the animations folder. We would move every thing that can move. Most of the control panel applets use the app icons from the Linux icon them. For example, WINE IE and inetcpl.cpl, since the icons are the same, it would be copied to /media/icons/applications as internet-web-browser.ico as the two apps would share that icon. Hope that clears some stuff up. :)
Jared
From: gedmurphy.maillists at gmail.com
To: ros-dev at reactos.org
Date: Fri, 24 Jul 2015 16:32:57 +0100
Subject: Re: [ros-dev] Unify system icons into one central folder
I’m not sure it won’t create as many problems as it solves. The bulk of the icons are already grouped in setupapi and shell32, and with the exception of cpls, the majority of the OS uses these icons. Unless there’s a full icon replacement, it’s not particularly hard to maintain the existing stuff as there’s very little to change. What else do you propose to move? Control panel applet icons? Win32 dll icons? Application icons? What about other resources such as animations or sounds?What’s the naming convention going to be? Currently shell32 uses the resource ids from 2k3 as their names as it makes them easy to compare directly. I’m not saying it’s a bad idea, I’m just saying that you can’t propose “let’s move all the icons to one folder” without providing a planCan you or David (or anyone else) come up with a proposal that works? I’m guessing you’re thinking something like the following: Root Shell Icons Bitmaps Toolbars Animations Media Sounds Icons System Or do you prefer a layout more akin to how Tango does it just purely for icons:Root Action Animation Apps Devices … I’m also guessing you’d want all win32 dlls and cpls try to reference icons from this folder structure. Anything in base\applications should manage its own resources.Anything which doesn’t fit (what are the guidelines for “doesn’t fit”) should be stored local to the project? Ged. From: Ros-dev [mailto:ros-dev-bounces at reactos.org] On Behalf Of Jared Smudde
Sent: 24 July 2015 15:22
To: ReactOS Development List <ros-dev at reactos.org>
Subject: Re: [ros-dev] Unify system icons into one central folder Why not we leave the kernel and win32ss icons where they are and move the rest. win32ss has around 7 icons that need to be changed when going to a different icon theme. That's much better than having to go into each folder to check if there's icons in there. Of course the bitmaps will have to stay in each folder as most of the apps and dlls have unique bitmaps to them. Jared> Date: Fri, 24 Jul 2015 16:14:24 +0200
> From: gigaherz at gmail.com
> To: ros-dev at reactos.org
> Subject: Re: [ros-dev] Unify system icons into one central folder
>> Yes, it is indeed a ridiculous analogy. I believe there are too many
> advantages to have a unified place to have most of the common icons
> usable by any app that needs them.
>> Note that my idea was for common icons, thing such the usual "objects"
> (document icon, folder icon, the configuration cogs, warning triangle,
> ...) and "actions" (document-new, search, navigate-back/dorward,
> zoom-in/out, ...).
>> I believe this ADDS to modularization, since it removes duplicate
> copies of icons and unifies them in a more manageable way, while most
> people who work on code are going to download most of ReactOS AND
> RosTests either way, because it's not that useful with just the
> kernel. ;P
>> I do admit that it has one bigger side-effect: if someone wants to
> "move out" a single module/app away from the rest of the repository,
> they'd have to select the required icons manually, but this does not
> happen very often and it shouldn't really be bothering us. If a lot of
> people are taking pieces of ReactOS and moving them elsewhere, this is
> a sign of bad things.
>> On 24 July 2015 at 10:18, Ged Murphy <gedmurphy.maillists at gmail.com> wrote:
> > I like the idea in general, but there must be a cleaner and more modular way
> > of doing it instead of dumping everything in one location.
> >
> >
> >
> > In an area where many devs are pushing to modularize things (think current
> > win32ss and future minwin), this moves the tree in the opposite direction.
> > If you were a kernel and win32ss guy, you’d then need to have all the icons
> > for the whole OS in your WC just to build the area you’re interested in.
> >
> >
> >
> > This is a kinda ridiculous analogy, but imagine if you had to checkout KDE
> > just to build the linux kernel.
> >
> >
> >
> > Ged.
> >
> >
> >
> > From: Ros-dev [mailto:ros-dev-bounces at reactos.org] On Behalf Of Jared Smudde
> > Sent: 24 July 2015 02:39
> > To: ros-dev at reactos.org
> > Subject: [ros-dev] Unify system icons into one central folder
> >
> >
> >
> > Hello. I am Jared Smudde aka. Pi_User5. I propose that we move most of the
> > icons in trunk into a central folder in the media folder. Some icons will
> > need to stay because they might be application specific. The folder can be
> > called icons and it would be organized according to
> > http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html.
> > This way, we can eliminate duplicate icons thus making trunk slightly
> > smaller. It will also make changing ReactOS to a different icon theme much
> > easier. This idea was suggested by gigaherz and I would like to see it done.
> > Thanks!
> >
> >
> >
> > Jared
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev at reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
>> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev at reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.reactos.org/pipermail/ros-dev/attachments/20150724/147f2103/attachment.html>
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 0018lejinjidian.com.cn bjxtly.com.cn lanigem.com.cn iconey.com.cn 90le.com.cn jxqiche.com.cn www.zshggs.com.cn wisolo.com.cn www.fkn-12.com.cn bandong.org.cn