Hi,
I thing time has come to enter is project some developer's
hierarchy. IMHO, BSD style hierarchy is great.
Some peoples will be "core team". I thing you know them ;)
Some peoples will be "commiters" with write access to cvs repository.
Peoples who write some code for project transfer it to commiter,
commiter checks that code and if it is good, commit this stuff.
Core team will determine general project's policy.
What averybody thing about this plan?
---
Best Regards
tappak
I actually prefer what Casper did. It looks at @implemented and
@unimplemented tags in source files and compiles a status report from
that. It even used Javascript to expand/minimize any area of the
tree.
But perhaps ideas from this work can be used as well.
Cheers
Jason
Robert K�pferl wrote:
> Hi,
> I just finished a project status reporting in html perl script.
> It is intended to produce kind of report in html based on
info-files
> which are spread over a repository.
> It's output looks like the attached file.
>
> It's input consists of files. In this case status.txt which are
> formatted like that:
> -----------------8<-------------
> Status: halted
> Project: ROS.apps.gugu
> Finished: 100%
> TODO: there's nothing left
> Maintainer: God
> ------------------
>
> These files all are read, put together, computed and written as
> HTML-file.
>
> I wrote that for a status page on the project homepage and hope it
is
> of use and gets installed.
>
> However there is surely improovement.
> for example I am poor at HTML. Now it is a <ul> with tables inside.
I
> think it would be nicer if it were with clickable [+]es. Maybe
someone
> can post me a template.
>
>------------------------------------------------------------------------
>
>
>
> *
> *Projectpath:* ROS
> *Finished:*
> 45.25%
> *Subprojects:* 4
>
> o
> *Projectpath:* apps
> *Finished:*
> 100%
> *Subprojects:* 1
>
> +
> *Project:* ROS.apps.gugu
> *Finished:*
> 100 %
> *Status:* halted
> *Maintainer:* God
> *TODO:* there's nothing left
>
> o
> *Projectpath:* p2
> *Finished:*
> 24%
> *Subprojects:* 2
>
> +
> *Project:* ROS.p2.dd
> *Finished:*
> 34%
> *Status:*
> *Maintainer:* Seppel
> *TODO:* work out the source code and clean all
bugs.
>
> +
> *Project:* ROS.p2.5
> *Finished:*
> 14%
> *Status:*
> *Maintainer:* Seppel
> *TODO:* work out the source code and clean all
bugs.
>
> o
> *Projectpath:* xx
> *Finished:*
> 33%
> *Subprojects:* 1
>
> +
> *Projectpath:* apps
> *Finished:*
> 33%
> *Subprojects:* 1
>
> #
> *Projectpath:* gugu
> *Finished:*
> 33%
> *Subprojects:* 1
>
> *
> *Projectpath:* profet
> *Finished:*
> 33%
> *Subprojects:* 1
>
> o
> *Project:*
ROS.xx.apps.gugu.profet.winamp
> *Finished:*
> 33%
> *Status:*
> *Maintainer:* Gustel
> *TODO:* work oUt the source code
and clean
> all bugs.
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>ros-general mailing list
>ros-general(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-general
>
__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
I did ask this on the ReactOS forum, but I thought I'd ask on the mailing
list as well :)
How would I go about implementing a DOS subsystem? I used to use DOS for all
my programming, even when Windows 95 and 98 were around. I used to mess with
software interrupts (had a copy of Ralf Brown's interrupt list) to do things
like read raw data from floppy disks etc.
I understand that Windows NT protects the hardware from direct access from
non-kernel mode applications/drivers. How is this achieved? What prevents an
application from simply executing an OUT or IN opcode? And what happens if
an application attempts to?
I assume x86 CPUs have some form of mode... Protected mode?... that allows
this kind of protection.
I also assume you can use normal DOS interrupts from a cmd.exe session in
Windows. How does Windows use software interrupts? As when an IRQ is
triggered, it causes the CPU to execute a software interrupt, what's there
to stop usermode applications from stealing the system timer interrupt
handler and thus break the kernel scheduling?
But basically, what I'd like to know is where I'd start for creating a DOS
subsystem? Where do I start?
-Andrew
Hi,
im trying to get WinRar 3.2d to load under Reactos. After adding 2
exports to
advapi32 (GetFileSecurityW & SetFileSecurityW) it complaints about an
unfindable
export called "Borland32". Is this export related to the missing SEH
support ?
regards,
--
Johannes Anderwald
> > Thats wrong.
> > I have tested it. After appendixes you are at
> > http://reactos.com/en/content/view/full/257
> > And this document is _empty_ !
>
>Look at the menu on the left
Hmmm...
I have now tested it with Mozilla-FireFox 0.8, Mozilla 1.2.1, an Netscape
4.x and Konqureor 2.2.2. All are Linux-version.
On FireFox the side Appendix-side at
http://reactos.com/en/content/view/full/257
is empty. What you mean is that under "Navigation" something stand. But
thats with Firefox not true. There stand nothing.
But for some time there stand under
http://reactos.com/en/content/view/full/258
of the "Knowledge Base Articles" the Changelog and Knowledgebase under
"Navigation". But now, there isn't anything, too.
And all the other browsers show _all_ nothing under "Navigation". Neither on
the Appendix-side, nor under the Knowledgebase-side.
Please try other browser and you see, what I mean.
Greatings
theuserbl
_________________________________________________________________
MSN Messenger - sehen, welche Freunde online sind!
http://www.msn.de/messenger Jetzt kostenlos downloaden und mitmachen!
> > how does one navigate from the ReactOS.com frontpage to this changelog?
> > I don't see the route that I need to follow for finding changelogs.
> >
> > ReactOS.com
> > --> developer
> > --> ???
> > (--> ???)
> > --> 0.2.1 changelog
> >
> >
> >http://reactos.com/en/reactos_unified_library/reactos_developer_documentatio
> > >
> > >
> >
> >n/reactos_development/the_reactos_project/appendixes/changelogs/0_2_1_change
> > >
> > >
>
>Library -> ReactOS Developer Documentation -> ReactOS Development -> The
>Reactos Project -> Appendixes (shouldn't that be appendices btw?)->
>Changelogs
Thats wrong.
I have tested it. After appendixes you are at
http://reactos.com/en/content/view/full/257
And this document is _empty_ !
Greatings
theuserbl
_________________________________________________________________
MSN Messenger - sehen, welche Freunde online sind!
http://www.msn.de/messenger Jetzt kostenlos downloaden und mitmachen!
Oh, and what mw wonder:
At the main-page and on other sides the menu-entries on the left are
visible.
But at http://reactos.com/en/content/view/full/257 it isn't.
Greatings
theuserbl
_________________________________________________________________
MSN Messenger - sehen, welche Freunde online sind!
http://www.msn.de/messenger Jetzt kostenlos downloaden und mitmachen!
At 21.54 29/02/2004, you wrote:
>>I am strictly _against_ sharing code between dlls, or ntoskrnl and ntdll.
>the directory listing of the leaked Windows sources
to make things clear: I have *not* downloaded or otherwise obtained said
sources. The listing was posted on a site and linked to on the Slashdot
story about the leakage, and I took some time to examine it to tell if it
could be genuine, and to catch something interesting if it was (I did find
something interesting, and it was the proof that NtUserXxx/NtGdiXxx aren't
considered real system calls, but rather glue code, like before I only knew
by heart, and like I have speculated in the past on the mailing lists)
Sorry, that I need always so much time, to answer.
>You may have more luck using FreeLoader to boot ReactOS. Download
>http://reactos.csh-consult.dk/download.php?sid=FreeLoader-20040229-bochs.i38
>6.tar.gz
>
>Write it to a floppy disk using RawWrite or similar tool. RawWrite is at
>http://uranus.it.swin.edu.au/~jn/linux/rawwrite.htm
>
>Boot ReactOS using the floppy disk.
>Note that this floppy disk will only boot ReactOS from the first partition
>on the
>first harddisk.
I have yesterday downloaded and tested it. And it runs now. :-)
Thank you very much for this hint.
ReactOS looks very nice.
One of the best thing is the booting.
At first the Freeloader which let you choose between ReactOS and ReactOS
with Debug-outputs.
Then opens the blue WinNT-screen and wrote something down there. But it's so
fast, that I can't read it. So fast on my old computer. :-)
Then the nice booting ReactOS-Logo. And I think, in this time, it loads also
faster then WinNT.
Then there xomes for a half second the blue screen back and then there comes
the ReactOS-desktop. And all comes very fast. :-)
And under ReactOS the programs (like sol.exe) are running partially fast
too.
To take a new card of the pack of cards in the left corner of the top, is
fast like on WinNT, I think.
But moving a card or moving windows is very slow.
The menus of the program exist, but they are not usable, what me wonder. :-o
And the console-window needs a lot of time, too, to write there the letters,
if I type "dir" or anything else in there.
But for a 0.2.0-version its excellent.
But I am wondering, why the freeloader-floppy-image is not an offical part
of ReactOS and why it is not published at Sourceforge. :-/
I think the binary-version of ReactOS plus the FreeLoader floppy-image is a
nice combination.
But on Sourceforge are actually - of the 0.2.1.RC2-version - only versions
for bochs and iso-images vor CDROMs. And my computer is for bochs too slow
(and have too less memory) and for the iso-image I have no CD-burner.
So I could only test the last final-version: ReactOS 0.2.0.
And now a little thought of myself.
I think, it would be nice if somethink like the DOS "sys.exe" exists for
ReactOS.
sys.exe copies the basical system-files to a dos-filesystem (that can be a
floppy, a harddisk-partition or anything else) and writes in the MDR which
systemfile have been to load.
Something else, existing with the FreeLOader-floppy-image. There is the mdr,
which says, that freeldr.sys have to load. But the floppy-image is only for
a floppy and all files on it will be deleted.
So I think something like sys.exe would be nice.
So that sys.exe write to the mdr of a floppy, harddisk, - if possible to the
CDROM, DVD or anything else. :-)
Greatings
theuserbl
_________________________________________________________________
E-Mails sind Ihnen nicht schnell genug? http://www.msn.de/messenger MSN
Messenger - Kommunikation in Echtzeit
Hi all
Ros-translate(a)reactos.com is now available.
Send an email to ros-translate-subscribe(a)reactos.com to subscribe to
the
new list.
Cheers
Jason
__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools
