Not that I am aware of... but I could be wrong too because I never
hang around the bugzilla site lol
>> Can someone actually fix the radio buttons? It's getting annoying to
>> see it with no outlining on it, not sure why whoever wrote the code
>> for it left the outline of it out...
>>
>Hi,
>Is there a bug report for it already? I think we never finished it.
>Thanks,
>James
--
-David W. Eckert
Hey all,
Well, since time has been very restricted for me I have not done as
much code auditing as I would have liked.
However, I did add a page to the wiki about writing secure code
(Secure_Programming). I hope people find it useful and will add
ReactOS specific items to it.
I decided to use another page rather than add to
Programming_Guidelines as it could grow quite big on its own. It is
not linked from any other pages as I didn't want to tread on anyones
toes or get in the way of someone else.
Hope this helps people write a bit more securely :)
Martin
Can someone actually fix the radio buttons? It's getting annoying to
see it with no outlining on it, not sure why whoever wrote the code
for it left the outline of it out...
--
-David W. Eckert
WaxDragon wrote:
> I have the UIC's approval.
I never approved it to be non-user-selectable in the first place.
IRC log (18 Apr 2006):
22:27 -!- Irssi: Starting query in FreeNode with Christoph_vW
22:27 <Christoph_vW> http://www.ApiViewer.de/downloads/test.png
22:29 <mf> nice
22:29 <Christoph_vW> ok
22:30 <Christoph_vW> that is what I wanted to hear :-)
22:31 <mf> yeah i saw someone on the forum do that too
22:31 <Christoph_vW> I thought we should differ from windows in some way
22:31 <mf> now make a corner-to-corner gradient :)
22:31 <mf> a-la openstep
22:34 <mf> left-top to right-bottom
22:34 <Christoph_vW> not yet
22:49 <mf> it IS optional though, right?
22:49 <Christoph_vW> no...
22:49 <Christoph_vW> I replaced the old gradient
22:49 <mf> ...
22:50 <mf> please revert it until you can turn it on/off
22:50 <mf> or else there'll be a lot of complaints from devs and useres
22:50 <mf> users*
23:02 <Christoph_vW> http://www.ApiViewer.de/downloads/test2.png
23:05 <mf> slightly better ;)
23:05 <Christoph_vW> good
Not that anyone ever listens to what I have to say, though.
David Hinz wrote:
> What about a vote on this "problem"?
There is no vote necessary. The only thing that needs to be done is an
interface so people can turn it on/off to their own tastes.
Last week I have tested ReactOS build 21942.
And I wondern about the ugly changes:
- wrong gradient on the top of the windows.
- the symbols which say, which icon on the desktop is a link and which not,
is now on the right bottom, instead of the left bottom
But some icon-designer have the icons so designed, that its ok, if there
is something on the left bottom of the icon lost. But the icons are
not so designed, that it is lost on any other place.
It seems, there are now some ReactOS-developer, who don't like Windows.
I would prefering it, if ReactOS looks most as possible like Windows.
And if anybody wants to have its own look, that then existing options to
change the look of ReactOS.
Greatings
theuserbl
There is a hotkey meta bug please mark that bug as "depending on" the
last two you file.
Brandon
ReactOS.Bugzilla(a)reactos.org wrote
>http://www.reactos.org/bugzilla/show_bug.cgi?id=1514
>
> Summary: Edit control: Ctrl+Backspace/Delete doesn't work
> (correctly)
> Product: ReactOS
> Version: TRUNK
> Platform: VMWare 5
> OS/Version: ReactOS
> Status: NEW
> Severity: minor
> Priority: P3
> Component: Win32
> AssignedTo: ros-bugs(a)reactos.org
> ReportedBy: trondsg(a)gmail.com
> QAContact: ros-bugs(a)reactos.org
>
>
>In all edit controls, like the one you get when go to Start -> Run, Ctrl +
>Backspace does not work at all. It is supposed to delete the previous
>word.Ctrl+Delete deletes the rest of the contents (after the caret) instead of
>deleting the next word.
>
>
>
>
Exactly one months ago, I annouced the beta test for the ReactOS
Compatibility Database:
http://www.reactos.org/xhtml/en/news_page_18.htmlhttp://www.reactos.org/support/
We have currently 71 categories and 99 applications/drivers in the database.
I got some feedback from users. This lead to several interface
improvements. For example, some user commented that the submit process
is to confusing. It was confusing, well let say the submit pages were
too overloaded.
I tried with several updates to improve th interface and especially
the submit pages step by step.
As of today, the latest update bring a complete redesigned submit
process, a wizard like look&feel which looks and interact similar to
Wizard '97 / Vista (from the Win32 world) and has a lot of usability
improvements.
It has many user interacting feedback included so that the user will
see instantly if he e.g. inputted an invalid value. The submit pages
are using ajax, dhtml (=> javascript).
I want to invite you to visit the ReactOS Compatibility Database:
http://www.reactos.org/support/
Feedback is welcome, please use the mailing list and/or the website
sub-forum (http://www.reactos.org/forum/viewforum.php?f=18) to write
replies.
Klemens Friedl
ReactOS Dev & Website Admin
http://www.reactos.org/support/
> Nobody (ok, many didn't) objected to attacking Iraq at first either.
> Nor did they to the beginnings of the Holocaust.
>
> Best regards,
> Alex Ionescu
Whatever. I've had it having to justify my every breath in here. I'm
stepping down as UIC and icon designer.
Fireball, you can close my SVN account. It seems some people are
thinking we didn't lose enough developers from the Hartmut drama. I am
officially fed up with everyone's fucking around and bitching. The
person I expected it from the least is GreatLord.
> Why I wanted a UI coordinator, is because HE should solve SUCH
> questions [in a more or less diplomatic way :) ].
How am I supposed to impartially solve an issue I am personally
involved in? If people aren't willing to accept my condition of
"discuss with me first", then I don't know what I should do.
(sorry for initially having accidentally sent this mail to ros-general
instead of ros-dev)
> The ReactOS logo is an ugly design.
Until you manage to get that wonky off-balance thing you prefer to be
accepted as the official logo, whether it is ugly or not is not
relevant. There is a procedure for changing established things. Your
method of just going ahead and changing things without asking is not
only rude but wrong. If you want to change things, you will have to go
through me first. If you have a problem with me, you have a problem
with changing things. So I suggest you consider your options.
> Also, it's far too complex to be used as a start button image and looks out
of place.
It's a bloody orb with wisps (rings) around it. Complex my eye.
> The official Windows logo isn't used on the start button. A neater version
is used in the same way.
A "neater version". You mean the shadow? I have employed a similar way
to make the icon clear at 16x16:
http://img55.imageshack.us/img55/4972/startthingie3yn.png
As you can see, both with Windows and with ReactOS, it's practically
the same thing. I'm beginning to get the idea you are making arguments
up for the sake of having arguments in your offence.
> This logo is the original ReactOS start menu logo and should be kept IMO.
It's as much a placeholder as the "original" Everaldo icons were.
mf
> I know it is alot people reactos user and
> devloper dislike the new logo.
> if u do not revert it, (restore to the old one)
> I will do it this weekend.
GreatLord, there *IS* no new logo. The icon I re-committed has been in
ReactOS since r14357. That's March 27th 2005. Nobody objected back
then, yet now there's a fuss? Please mind your own business if you
don't know exactly what's going on. Thanks.
mf
mf wrote:
> Until you manage to get that wonky off-balance thing you prefer to be
> accepted as the official logo, whether it is ugly or not is not
> relevant. There is a procedure for changing established things. Your
> method of just going ahead and changing things without asking is not
> only rude but wrong.
I highly disagree with the fact that everyone must go through you. If we
initiated a kernel coordinator, do you also suggest that all kernel work
must be approved by them too?
Taking into account the smarmy comment which went along with the change,
it was my impression you changed it back just to try and annoy me.
Many of the developers I have spoken to agree that the original icon is
better. Nobody seems to want to say anything to you for fear of
upsetting you though. Great!
> If you want to change things, you will have to go
> through me first. If you have a problem with me, you have a problem
> with changing things. So I suggest you consider your options.
>
I have just considered my options. I choose to stop work on the UI as of
now.
The fact that you've tried to alienate me many times, and now in public
seals the fact that we can't work together.
I was the only person interested in working on the UI, and you managed
to take the fun out of it for me, are you sure you are the right man for
the job? I tend to think not.
Ged.
Hi
The new logo se does not look like reactos any longer
it is to dark and pixel, the balas and constrast in the new
logo is bad, it does not match at all, and it look not prof
have made it. more like a childer. So please revert
the new logo and keep, the old one.
If u look in ros it does not match the constrast or
any think. A logo should not be pixel or constat
does not match. That is exacly in the new logo
u have done MF.
I know it is alot people reactos user and
devloper dislike the new logo.
if u do not revert it, (restore to the old one)
I will do it this weekend.
Magnus Olsen (GreatLord)
ReactOS Devloper
----- Original Message -----
From: "mf" <mf(a)mufunyo.net>
To: <ros-general(a)reactos.org>
Sent: Thursday, May 18, 2006 11:53 PM
Subject: [ros-general] RE: [ros-diffs] [mflyer] 21918: Sorry Ged,but that's
not the Rea ctOS logo.
> > The ReactOS logo is an ugly design.
> Until you manage to get that wonky off-balance thing you prefer to be
> accepted as the official logo, whether it is ugly or not is not
> relevant. There is a procedure for changing established things. Your
> method of just going ahead and changing things without asking is not
> only rude but wrong. If you want to change things, you will have to go
> through me first. If you have a problem with me, you have a problem
> with changing things. So I suggest you consider your options.
>
> > Also, it's far too complex to be used as a start button image and looks
out
> of place.
> It's a bloody orb with wisps (rings) around it. Complex my eye.
>
> > The official Windows logo isn't used on the start button. A neater
version
> is used in the same way.
>
> A "neater version". You mean the shadow? I have employed a similar way
> to make the icon clear at 16x16:
>
> http://img55.imageshack.us/img55/4972/startthingie3yn.png
>
> As you can see, both with Windows and with ReactOS, it's practically
> the same thing. I'm beginning to get the idea you are making arguments
> up for the sake of having arguments in your offence.
>
> > This logo is the original ReactOS start menu logo and should be kept
IMO.
> It's as much a placeholder as the "original" Everaldo icons were.
>
> mf
>
> _______________________________________________
> Ros-general mailing list
> Ros-general(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-general
Aleksey and I thought it would be a good idea to end rumours and write
up an official stance on the topic, so here is a paste from the website,
for those of you that don't read it:
--
The official letter written by project coordinators of these projects
by fireball on 2006-05-18
ReactOS and TinyKRNL projects' official relationship
Prepared by Aleksey Bragin and Alex Ionescu, Project Coordinators.
There is a little information posted officially about TinyKRNL project
and this provides a base for gossip to appear. This short article is
intended to clear up official relations between these two projects.
TinyKRNL is an educational and documentation project which creates
plug-in replacements for various modules of Windows 2003 SP 1
(ultimately replacing the kernel too) and a series of papers ultimately
combined into a book. The methods used for development of TinyKRNL’s
modules source code involve all possible methods of achieving the end
result of having a 100% compatible (or even identical) result. Reverse
engineering is one of them (mainly so-called ‘dirty’ way, for further
reference see Wikipedia’s article about clean room reverse engineering
vs. dirty room reversing).
Unfortunately, due to copyright laws and other law-related stuff,
ReactOS (which aims at commercial usage too) can not directly utilize
methods of development like dirty reverse engineering, and thus ReactOS
can not share all code with the TinyKRNL project like we are sharing
code with WINE.
However, there are some very useful exceptions:
* Firstly, all interfaces are shared. This gives ReactOS project an
unbeatable level of compatibility and legal freedom too (interfaces can
not be copyrighted).
* Secondly, the great thing is that TinyKRNL will provide the most
complete documentation of the most recent and technically advanced
version of a released NT-famility operating system – Windows 2003 SP1.
ReactOS developers can use this documentation for reference when
creating a clean implementation of functions or improving already
developed code.
* Thirdly, any code in TinyKRNL which respects the ReactOS policies
regarding development can directly be added into ReactOS, as well as any
build tools or 3rd-party files.
For more detailed information regarding TinyKRNL project, please look at
http://www.tinykrnl.org. We also encourage you to signup on the TinyKRNL
. We also encourage you to signup on the TinyKRNL development Mailing
List by sending a blank email to devel-subscribe(a)tinykrnl.org as well as
joining the #tinykrnl channel on the same IRC server as #reactos; many
of the ReactOS developers and users are usually present and discuss
interesting and challenging kernel issues as well as general off-topic chat.
--
mflyer(a)svn.reactos.org wrote:
> Sorry Ged, but that's not the ReactOS logo.
The ReactOS logo is an ugly design.
Also, it's far too complex to be used as a start button image and looks out
of place.
The official Windows logo isn't used on the start button. A neater version
is used in the same way.
This logo is the original ReactOS start menu logo and should be kept IMO.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Can we agree on the following goals for 0.3.1 ?
- NDK
- Cache Manager Rewrite
- VMware Tools
- Ext2
It would mean that we would release 0.3.1 very closely after 0.3.0.
Maarten Bosma
Steven Edwards wrote:
> On 5/11/06, Murphy, Ged (Bolton) <MurphyG(a)cmpbatteries.co.uk> wrote:
> > The Wine syncs aren't quite as simple as Gé made them look.
> I think we took
> > them for granted back when Gé was doing them.
> > IIRC, comctl32 still needs doing. Last time it introduced
> regressions and
> > was reverted.
>
> I have offered to sync up a bunch of changes for the 0.3 cycle. I'm
> going to start doing this Friday evening for the dlls that are a 100%
> drop-in. There are a few other things that could be updated as well in
> advapi32, kernel32, etc as well as new regression tests. I expect its
> going to take me a while to do it all and make sure there is no
> regression.
Gé has a great awk script which automates a vast majority of the process,
including the laborious task of generating the logs/credits.
If he isn't around today, I can forward a copy on to you later.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Alex committed the NDK today, so I went ahead and branched 0.3.0 at
the previous revision. Aleskey and I decided that the NDK and CC
patches can go in trunk whenever they are ready, for inclusion into
0.3.1. 0.3.0 is still in need of bugfixing and regression testing.
Therefore, we are going to leave the 0.3.0 branch open to
development for a bit before we release RC1. Please discuss any large
changes on the list before commiting to the branch. I don't care of
the branch stays open for a month, as long as it's a good release in
the end.
Thanks for all your hard work,
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion
Aleksey Bragin wrote:
> If some of you wants to merge components which are left - please go
> ahead. Wine vendor import was done (some 10, some 12), so it's just
> the merge which is left. And main problem is merging 0.9.5->0.9.10,
> while 0.9.10-0.9.12 is quite easy due to not so big amount of changes.
The Wine syncs aren't quite as simple as Gé made them look. I think we took
them for granted back when Gé was doing them.
IIRC, comctl32 still needs doing. Last time it introduced regressions and
was reverted.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com