eactos.org] On Behalf Of Can Tasan
Sent: 17 March 2017 12:48
To: ReactOS Development List <ros-dev@reactos.org>
Subject: Re: [ros-dev] New ideas added to GSoC Ideas list
Dear Ricardo,
Firstly, Win16 application support doesn't interrupt our project. It
strengthens us. On technical view, support
eactOS Development List <ros-dev@reactos.org>
Konu: Re: [ros-dev] New ideas added to GSoC Ideas list
Sorry for the non-developer intrusion, this is the point of view of an IT
technician that would happily substitute Windows machines with ReactOS machine
in an hypotetical future.
To me, thi
Development List <ros-dev@reactos.org>
Subject: Re: [ros-dev] New ideas added to GSoC Ideas list
Wine still maintains and even improves Windows 3.x support! I hope they don't
give up!
Can we use Wine code while implementing WoW16?
___
Ros-dev mailin
Wine still maintains and even improves Windows 3.x support! I hope they don't
give up!
Can we use Wine code while implementing WoW16?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Wine still maintains and even improves Windows 3.x support! I hope they don't
give up!
Can we use Wine code while implementing WoW16?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
That second Windows should have been ros.
On 17 March 2017 at 01:25, David Quintana (gigaherz)
wrote:
> Running windows inside a vdm window isn't the same as running the apps
> directly in windows, as if they were native apps.
>
> On 17 March 2017 at 01:07, Javier Agustìn
Running windows inside a vdm window isn't the same as running the apps
directly in windows, as if they were native apps.
On 17 March 2017 at 01:07, Javier Agustìn Fernàndez Arroyo wrote:
> some people have had success in running Win 3.1 under ReactOS thanks to
> NTDVM, so
some people have had success in running Win 3.1 under ReactOS thanks to
NTDVM, so win3.1 apps can be run too :)
On Thu, Mar 16, 2017 at 11:49 PM, David Quintana (gigaherz) <
gigah...@gmail.com> wrote:
> That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order
> to support 16bit
(the corresponding 16-bit
part), krnl386.exe (the “kernel” of Win 3.1) and the thunk dlls/exes user, gdi …
De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de David Quintana
(gigaherz)
Envoyé : jeudi 16 mars 2017 23:50
À : ReactOS Development List
Objet : Re: [ros-dev] New ideas added to GSoC
That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order to
support 16bit (windows 3.1) applications, a whole other system is needed.
On 16 March 2017 at 23:37, Javier Agustìn Fernàndez Arroyo wrote:
> "-Implementing WoW16 support. I suppose that'll draw
I can tell you some possible next steps:
- x64: implement PAE support in the 32 bit kernel
- SMP: Implement resource translators and arbiters (I have some initial work
for this somewhere)
- Also SMP: build a CONFIG_SMP kernel (with some hack to use the regular HAL)
and debug any issues coming
Am 16.03.2017 um 00:03 schrieb Huw Campbell:
> SMP or 64 bit processor support would be great. Too hard?
I think that's too much for a single GSoC student. But we also keep
saying this for a long time... The result is that everybody is afraid of
those "big topics".
What we need is some kernel
Hi all,
SMP or 64 bit processor support would be great. Too hard?
Cheers,
Huw
On Thu, Mar 16, 2017 at 7:28 AM, Can Tasan wrote:
> I also have some ideas here, not fully sure about their feasibility. Tried
> to be wise as much as I can.
>
> -Continuing USB work that
I also have some ideas here, not fully sure about their feasibility. Tried to
be wise as much as I can.
-Continuing USB work that vardanm started. Yes, I know a developer is working
on that. Another joining student would be great and speed up things.
-Continuing TCP/IP stack work if noone is
the selected ones)
>> different dialogs of the different languages, in e.g. mosaic positioning,
>> which should help the translator to easily see whether he needs to adapt a
>> layout for a given language, or whether he can just copy/paste an existing
>> layout.
>>
>>
>
gt; which should help the translator to easily see whether he needs to adapt a
> layout for a given language, or whether he can just copy/paste an existing
> layout.
>
>
>
> Hermès.
>
>
>
> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Rafal
> Har
yout for a
given language, or whether he can just copy/paste an existing layout.
Hermès.
De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Rafal Harabien
Envoyé : mardi 14 mars 2017 23:44
À : ReactOS Development List
Objet : Re: [ros-dev] New ideas added to GSoC Ideas list
PO f
PO files supports "context" markers to make it possible to differentiate
usage of the same string in different contexts.
About different layout - yes, we would have only one layout but IMO for
project like this with human resource problems its more important to
make development less boring and
Gettext-style translations are really really bad, because they use the
original text (usually in english) as a translation key, which means they
simply can not handle situations where the same english text needs
different translations depending on where the text is used. And yes, I have
come
In my opinion it's very sensible proposal. I remember changing dialog
layout in resources was a big pain because of amount of repeated work
for all languages (and error prone). It was demotivating.
On the other hand there are free translation platforms making project
translation more organized
Marți, 14 martie 2017 12:00:02 +, Mark Jansen
a scris:
> How about a better way to translate ros?
> For example integrating .po files with our rc files (possibly needs a
> preprocess step or something tho),
> Or creating a resource editor that allows multiple files
rigine-
>> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Colin Finck
>> Envoyé : dimanche 12 mars 2017 17:27
>> À : 'ReactOS Development List'
>> Objet : [ros-dev] New ideas added to GSoC Ideas list
>>
>> Hi all!
>>
>> Daniel and me colle
org] De la part de Colin Finck
> Envoyé : dimanche 12 mars 2017 17:27
> À : 'ReactOS Development List'
> Objet : [ros-dev] New ideas added to GSoC Ideas list
>
> Hi all!
>
> Daniel and me collected some additional ideas for GSoC today, which I've
> added to our Wiki
Am 12.03.2017 um 23:34 schrieb Thomas Mueller:
> Also, the ability to build or cross-build ReactOS and install directory to a
> FAT32 partition, mounted on a directory, without having to burn to CD and
> boot/install from there: would that be appropriate?
That's basically our previous "make
org
> <mailto:ros-dev-boun...@reactos.org>] De la part de Colin Finck
> > Envoyé : dimanche 12 mars 2017 17:27
> > À : 'ReactOS Development List'
> > Objet : [ros-dev] New ideas added to GSoC Ideas list
>
> > Hi all!
>
t; De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Colin
>> Finck
>> > Envoyé : dimanche 12 mars 2017 17:27
>> > À : 'ReactOS Development List'
>> > Objet : [ros-dev] New ideas added to GSoC Ideas list
>>
>> > Hi all!
>>
>>
> Victor thought also about adding registry hive healing.
> Hermès.
> -Message d'origine-
> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Colin Finck
> Envoyé : dimanche 12 mars 2017 17:27
> Ã : 'ReactOS Development List'
> Objet : [ros-dev] Ne
Victor thought also about adding registry hive healing.
Hermès.
-Message d'origine-
De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Colin Finck
Envoyé : dimanche 12 mars 2017 17:27
À : 'ReactOS Development List'
Objet : [ros-dev] New ideas added to GSoC Ideas list
Hi all
Hi all!
Daniel and me collected some additional ideas for GSoC today, which I've
added to our Wiki Ideas list:
https://reactos.org/wiki/Google_Summer_of_Code_2017_Ideas
In particular:
* Fundamental WiFi components
* USBXHCI driver for supporting USB 3.x controllers
* Bluetooth Stack
*
29 matches
Mail list logo