Hi!
I want to remove the "autoregister" feature from rbuild. Let me explain
why I want to do this.
The "autoregister" feature in rbuild is used to automatically add dlls
to the syssetup.inf file which require an ole server registration. The
ole servers in these dlls will then be registered in the 2nd setup stage.
The gain of adding the ole server dlls to syssetup.inf automatically is
almost non existant as a developer needs to add an 'autoregister'
element to the rbuild file of the dll.
For example:
<autoregister infsection="OleControlDlls" type="DllInstall" />
The corresponding line in the 'OleControlsDll' section of syssetup.inf is:
11,,comctl32.dll,2
Please remember that the line above only needs to be added once.
Now, what do we loose by generating syssetup.inf automatically? Right
now it is only the comments in this file as it is parsed and serialized
by the inflib library.
OTOH, my future plans for syssetup.inf are severely hampered by the way
rbuild handles syssetup.inf because rbuild is not able to create or
modify a Unicode version of syssetup.inf. But, a Unicode version of
syssetup.inf is required in order to replace the hard-coded creation of
the start menu and desktop links in syssetup.dll by a configurable,
localizable and Windows compatible inf-based method.
And finally since Timo suggested to replace rbuild by cmake: The
autoregister feature would surely be one of the victims of this change.
So why not drop this almost useless feature now?
What do you think?
Regards,
Eric
Recently, I've been watching MiLoadImageSection(). It takes PVOID casted
to ROS_SECTION_OBJECT parameter. Why is that?
Furthermore, it isn't really a same definition as on MS Windows (XP).
Why You've made this difference?
--
Pozdrawiam,
Mariusz Gliwiński
Not again.
Why on earth do we need a bluetooth driver when we don't even have a stable
OS to run it on?
On 12 June 2010 13:46, Aleksey Bragin <aleksey(a)reactos.org> wrote:
> Even though it's abandoned, I feel it's going to be abandoned in our source
> tree too.
>
> WBR,
> Aleksey Bragin.
>
>
> On Jun 12, 2010, at 4:29 AM, cgutman(a)svn.reactos.org wrote:
>
> Author: cgutman
>> Date: Sat Jun 12 00:29:09 2010
>> New Revision: 47761
>>
>> URL: http://svn.reactos.org/svn/reactos?rev=47761&view=rev
>> Log:
>> [FBTUSB]
>> - Import the FreeBT USB generic bluetooth driver (abandoned)
>> - Some slight modifications to make it build
>> - WMI is currently commented out because our WMI headers are lacking
>> (particularly wmistr.h)
>> - Not building by default for now
>>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
Even though it's abandoned, I feel it's going to be abandoned in our
source tree too.
WBR,
Aleksey Bragin.
On Jun 12, 2010, at 4:29 AM, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Sat Jun 12 00:29:09 2010
> New Revision: 47761
>
> URL: http://svn.reactos.org/svn/reactos?rev=47761&view=rev
> Log:
> [FBTUSB]
> - Import the FreeBT USB generic bluetooth driver (abandoned)
> - Some slight modifications to make it build
> - WMI is currently commented out because our WMI headers are
> lacking (particularly wmistr.h)
> - Not building by default for now
On 12 June 2010 01:29, <cgutman(a)svn.reactos.org> wrote:
>
> - WMI is currently commented out because our WMI headers are lacking
> (particularly wmistr.h
>
WMI is completely missing from reactos in every way
I beg my pardon, I accidentally pasted wrong name there. The real
thanks goes to Maarten Kroese (nickname Drazic in the Freenode network).
WBR,
Aleksey Bragin.
On Jun 12, 2010, at 12:19 AM, fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Fri Jun 11 20:18:59 2010
> New Revision: 47757
>
> URL: http://svn.reactos.org/svn/reactos?rev=47757&view=rev
> Log:
> - Merge in changes from Wine-1.1.44 related to supporting the
> ETO_PDY flag. Unregresses the text rendering in FF 3.5. Thanks to
> Jan Roeloffzen for help finding this problem and suggesting the
> right solution.
>
> Modified:
> branches/arwinss/reactos/dll/win32/winent.drv/font.c
> branches/arwinss/reactos/subsystems/win32/win32k/gre/font.c
Hi Ian,
Your help would be very much welcome and appreciated.
You've actually come at a very good time. Our whole backend, known as RosCMS
has just been rewritten and is now at version 4. It's a content management
system similar to Joomla, but written to better serve the needs of this
project.
Whilst the backend is now running and stable, the frontend needs a complete
rewrite. We had a design contest a few months ago and this was the winning
design : http://img200.imageshack.us/img200/7833/reactoswebsitedesign4.png
So far no one has had the time to make a start on it, so we're still running
on the now outdated site. What we need is for someone to get involved in
bringing this new layout to life.
It's probably best if you join the IRC channel and chat to our web designer.
He's called Danny and he goes by the nick of DangerGround in IRC. He should
be able to give you more info and guidance on what is required.
I'm posting this mail to the ros-dev mailing list so he and our other web
guys can pick it up.
You can continue to converse with me via private mail if you prefer to.
Regards,
Ged Murphy.
From: Ian Hilton [mailto:ian7hilton@gmail.com]
Sent: 04 June 2010 02:13
To: dev-interest(a)reactos.org
Subject: I have a lot of Questions
Hi My name is Ian Joseph Hilton I am a freshman in community college.
I consider myself a website developer of sorts in training, and for the past
year or so been familiarizing myself with website coding. I have been mostly
using Google based programs as my platform, and have so far just barely
stuck my toe in the water in attempting to write extensions for Google's
chrome browser. My main project is what I call Titanways Teaching (or
Tutoring) In Terrific And New ways and was my High school Exhibition project
required by the state of California to graduate, and it has got moderate
attention. the link is here : http://sites.google.com/site/titanwayssite/
I know what you must be thinking by now most likely that I have lack of
what you need and as my Uncle who currently writes programs for Medical
Equipment says I need at least two years or so to be taken seriously and not
laughed, but it never hurts to ask some things and worst comes to worse I
learn some things to point me in new directions which is always great.
Anyway I of course have been aware of your ReactOS project for a few
years and only recently has it occurred to me that I should inquire
somethings regarding it. Note I have not been "Tainted" at all as whatever
you are talking about with Microsoft's source code totally goes over my
head. I do use XP as my operating system However on a Toshiba NB 305
net-book. This is because a lot of my programs I am satisfied with run on
this operating system. My point to that is my net-book has further taught me
terms like debugging as not every program will run on it without a little
help by doing various things like editing a config file to fit its 1024x600
resolution frame. I has also used Linux Ubuntu and am familiar with
Macintosh interface via that is the main platform students use at general
educational institutions.
Now to get right to the point, right now I might not know much but if
there is anyway in the future that I may offer assistance in any form I
would be happy to, and also any helpful training or guidance you can point
me in in regards to coding website components for ReactOS would be even
better. I use mostly opensource alternatives to windows programs anyway such
as Open Office.org as I kinda share that feeling with you that Microsoft
kinda took a monopolistic view to its commercial applications.
I wish to ask how compatible is it currently with opensource apps
that run on Java platforms if it is integrated with as well as the web
browsers that it is compatible with? I have been familiarizing myself with
all three of the basic website rendering engines Trident, Gecko, and Web-kit
via the experimental triple engine browser being developed by a Japanese
software Company and is known as Lunascape. I also want to know if this OS
can support docking software such as Object dock or Rocket-dock and if not
what would I say need to do to learn how to make that kind of thing a
possibility. I will conclude by saying once again right now you may view me
as inexperienced but that I am quickly learning and any pointers I take
gratefully and with interest in consideration.
High Regards to you, Ian
P.S. will be taking Computer Classes in future semesters however it is my
opinion that the best in the field should try to learn from scratch ,and so
I am going to start by attempting to teach myself to write programs in C/C++
coding and see where that leads
Hello,
First I was asked if a certain developer could talk to me regarding ARM3. I said yes, never heard back, and then saw commits done to pfnlist.c. While interesting and useful code, some communication would've been nice in order to talk about the goals, since much of that code is in flux (I feel bad when someone improves a function that I will later remove, as two of the improved functions are only temporary -- the changes to the other functions will remain, obviously). Normally, this would not have been a problem, if not for the strange formatting and the fact this code was now broken and causing a boot regression.
I showed up in the #reactos-dev channel and instructed developers on how to fix the problem: remove the entire function and use MiInsertPageInFreeList instead, or fix MiInitializePagingLists to perform its work at DISPATCH_LEVEL instead, by acquiring the PFN lock as it should do.
None of this was done, instead "janderwald", in 47514, "Fixed" the ASSERT by saying "Any IRQL lower than DISPATCH_LEVEL" is okay. Janderwald, whoever you are, do you even understand this code? Are you even a kernel-mode developer? Does it make to you that the code would need to assert for low IRQL? The whole point is to validate that the PFN lock is being held. Even if you are not a kernel-mode dev, isn't it clear that all the other assertions are also checking for DISPATCH_LEVEL+?
And even if that's not clear, I had written down the solution in the #reactos-dev channel, expecting that probably not many people would figure it out.
So I guess some lessons to learn for this project:
1) If you modify someone's code, make sure you test your changes (and preferably don't mess up the formatting) so their code is not now blamed for a boot regression.
2) If someone tells you how to fix their code after it's been messed up, apply the fix.
3) If you choose to roll your own fix, write something useful instead of breaking the function (logic-wise) even more.
Again, I'm afraid the problem is most of you are students and don't have work ethics of real employees -- this seems to be the root of many problems this project has had since the last 2 years I've been watching and working on the ARM port.
Next steps:
- Janderwald: remove your ASSERT hack. Either 1) Remove the ASSERT (stop checking for an invariant that doesn't happen) or 2) Fix the caller (so the invariant holds)
- Arthur: changes are appreciated, but let's talk more so you don't end up improving dead code.
Carry on!
-r
hello,
i have thinking about an easy way to show people the ReactOS roadmap, and
there came to my mind two projects where i have submitted some bug reports
before joining ReactOS. They use the "milestone" field in their bug reports
for the roadmaps, and its a quite clean way to show it, IMO
Here are the links
Is there any way to do something similar using Bugzilla? (none of these 2
projects use this Bug Management System)
http://www.kdenlive.org/mantis/roadmap_page.phphttp://developer.pidgin.im/roadmap