Sounds like a cool feature, I'm waiting for it eagerly :)
-Gregor
cfinck(a)svn.reactos.org wrote:
> Author: cfinck
> Date: Mon Feb 11 21:43:40 2008
> New Revision: 32303
>
> URL: http://svn.reactos.org/svn/reactos?rev=32303&view=rev
> Log:
> New ReactOS People Map based on Google Maps API (not yet on the Web server)
>
> The map integrates into the existing website and is linked with the RosCMS accounts.
> You can add a group of users (like Translators, Developers, Administrators, etc.) to the map or search for people and add them individually. I made tests with 500 random users on one map and it was still usable :-)
> Also there are easy features for setting your own position.
>
> I successfully tested the People Map with Firefox 2.0, Opera 9.21, Safari 3 Beta, Konqueror 3.5.6 and IE6/7.
> The marker graphics were done myself with Inkscape and the other graphics were composed out of icons from the Tango Icon Project or taken from other ReactOS web apps.
> The PNGs with alpha transparency are also shown correctly under IE6 using a trick in "ie6-fixes.css".
>
>
Even more, I think it was you who implemented this entrypoint in the
ReactOS kernel :-).
I'll discuss with PPC and ARM ports, and then we could make a switch
alltogether.
WBR,
Aleksey Bragin.
On Feb 12, 2008, at 5:56 PM, Alex Ionescu wrote:
> Actually, I've never heard of the entrypoint being called
> NtProcessStartup for the kernel...
>
> Why not fix the name in the x86 sources?
Actually, I've never heard of the entrypoint being called
NtProcessStartup for the kernel...
Why not fix the name in the x86 sources?
On 12-Feb-08, at 8:34 AM, fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Tue Feb 12 16:34:33 2008
> New Revision: 32321
>
> URL: http://svn.reactos.org/svn/reactos?rev=32321&view=rev
> Log:
> - Kernel's entrypoint is called NtProcessStartup right now, for
> ReactOS. If this is to be changed, it should be changed for all
> archs, not only for ARM.
>
> Modified:
> trunk/reactos/tools/rbuild/module.cpp
>
> Modified: trunk/reactos/tools/rbuild/module.cpp
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/tools/rbuild/module.cpp?re…
> =
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
> --- trunk/reactos/tools/rbuild/module.cpp (original)
> +++ trunk/reactos/tools/rbuild/module.cpp Tue Feb 12 16:34:33 2008
> @@ -1033,7 +1033,7 @@
> switch ( type )
> {
> case Kernel:
> - return "KiSystemStartup";
> + return "NtProcessStartup";
> case KernelModeDLL:
> case KernelModeDriver:
> return "DriverEntry@8";
>
>
Best regards,
Alex Ionescu
I wonder why those functions spread around that much (cacls, sndvol, aclui, servman, etc...), since windows has already the needed function:
LoadString will store a pointer to the string resource in *lpBuffer, if nBufferMax is set to 0, so allocating additional memory is not neccessary in most cases. And it also returns the full length.
http://msdn2.microsoft.com/en-us/library/ms647486(VS.85).aspx
>
> Author: cfinck
> Date: Sat Feb 2 00:40:18 2008
> New Revision: 32079
>
> URL: http://svn.reactos.org/svn/reactos?rev=32079&view=rev <http://svn.reactos.org/svn/reactos?rev=32079&view=rev>
> Log:
> Wrote a Win32 Font Editor for our VGA Fonts used in blue.sys.
>
> It has a MDI user interface, imports binary fonts (.bin) and PC Screen Fonts (.psf) and exports .bin fonts.
> Compiles without any warnings with GCC and MSVC (at /W3).
>
> The "misc.c" file was taken from devmgmt (thanks Ged!) and modified.
>
>
Hi!
Somehow NtUserGetWindowThreadProcessId was moved to the main list.
This is wrong! With in the next six months
NtUserGetWindowThreadProcessId (unless it was added in Vista) and
friends will no longer be in ReactOS. Please do not create more work
than it is necessary to accomplish this rewrite.
-# ReactOS only system calls
-NtUserAcquireOrReleaseInputOwnership 1
-NtUserGetWindowThreadProcessId 2
-NtUserGetQueueStatus 1
Thanks,
James
Hello
I want port some function from wine kernel32.dll to ReactOS
kernel32.dll but have some problems.
First i have two modules and the question is where is the right place
to put them.
I need /tools/unicode/wctype.c also here /dll/win32/kernel32/misc/ to
compile.
1.) Is it better to leave this module in /tools/unicode/ ?
-> What must i write in kernel32.rbuild to build this module
with kernel32.dll
2.) or copy this file to /dll/win32/kernel32/misc/
the second solution is a bit ugly because we have tow files whit the
same contents.
3.) ???
thanks
Daniel
________________________________________________________________________
More new features than ever. Check out the new AIM(R) Mail ! -
http://webmail.aim.com