Ros-dev

ros-dev@reactos.org

1 participants
5793 discussions

Re: [ros-dev] Modularizing the ReactOS repo in Git
by Alex Ionescu 04 Aug '17

04 Aug '17

I would strongly suggest using one master repo. Multi-repo projects and their brethren are a mess. Best regards, Alex Ionescu On Wed, Aug 2, 2017 at 1:18 PM, David Quintana (gigaherz) < gigaherz(a)gmail.com> wrote: > We have! If you look at Colin's email, it has a link to a google doc, we > list Repo in it, and why we think it's not fit for our use :) > > That aside, I had a new idea, which I mentioned on IRC. I have added it to > the document. > > On 2 August 2017 at 11:52, Alexander Sh. <chaez.san(a)gmail.com> wrote: > >> Have a look at Repo: https://code.google.com/archive/p/git-repo/ >> It is used by Android devs. >> >> 2 авг. 2017 г. 12:28 пользователь "David Quintana (gigaherz)" < >> gigaherz(a)gmail.com> написал: >> >> The issue comes when we have to do regression-testing. We would need a >>> tool that knows how to match up core, system, tests, ... otherwise >>> debugging regressions is going to be hellish. >>> >>> On 2 August 2017 at 11:17, Alexander Sh. <chaez.san(a)gmail.com> wrote: >>> >>>> Since we have RosBE, we can have multiple repositories without actually >>>> binding them and download them on demand. Or we can make a build script for >>>> every new small module that downloads (clones) repos it needs. >>>> >>>> 2 авг. 2017 г. 11:41 пользователь "Colin Finck" <colin(a)reactos.org> >>>> написал: >>>> >>>> Hi all! >>>> >>>> After David has successfully tested a first SVN -> Git conversion of >>>> our repo, here comes the next challenge: Finding a way to preserve our >>>> current modularization into reactos, rosapps, rostests and paving the way >>>> for even more modularization. >>>> My vision for the future is a small "core" repo that only contains our >>>> host tools and SDK. We could also split off subprojects like fast486/ntvdm >>>> or Paint into individual repos. Now that Microsoft has abandoned them under >>>> Windows, they may individually attract developers who would never hack on >>>> the entire ReactOS repo. Furthermore, 3rd party components could be >>>> imported through their repo instead of copy-pasting their code without >>>> history (as we do now). >>>> Even if that vision is a distant goal, the technology for it is already >>>> required for a reactos, rosapps, rostests modularization. >>>> >>>> Isn't that a perfect scenario for Git submodules? >>>> Not sure: I'm not aware that they support the concept of optional >>>> modules. You could only check out the "core" repo with all defined >>>> submodules. This would make it impossible to use "core" only to build >>>> Paint. There also seem to be other drawbacks when using submodules: >>>> https://codingkilledthecat.wordpress.com/2012/04/28/why-your >>>> -company-shouldnt-use-git-submodules/ >>>> >>>> Alternatives like Git subtrees, Google Repo, and Gitslave exist, but >>>> there is even less information about them. Furthermore, I think a good >>>> integration into GUI tools like TortoiseGit is also a requirement for most >>>> of us. >>>> >>>> David and I have started to write down our findings: >>>> https://docs.google.com/document/d/1Ey1xdS_0GcG7p7ZgHZBh4A3V >>>> Mq2uxyw5MpnUXbT8z6w/edit >>>> Your input on this is very welcome! >>>> >>>> I guess any migration to Git is blocked before we have a solution here. >>>> >>>> >>>> Cheers, >>>> >>>> Colin >>>> >>>> _______________________________________________ >>>> Ros-dev mailing list >>>> Ros-dev(a)reactos.org >>>> http://www.reactos.org/mailman/listinfo/ros-dev >>>> >>>> >>>> >>>> _______________________________________________ >>>> Ros-dev mailing list >>>> Ros-dev(a)reactos.org >>>> http://www.reactos.org/mailman/listinfo/ros-dev >>>> >>> >>> >>> _______________________________________________ >>> Ros-dev mailing list >>> Ros-dev(a)reactos.org >>> http://www.reactos.org/mailman/listinfo/ros-dev >>> >> >> _______________________________________________ >> Ros-dev mailing list >> Ros-dev(a)reactos.org >> http://www.reactos.org/mailman/listinfo/ros-dev >> > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > >

1 0

Status Meeting (July 2017)
by Colin Finck 03 Aug '17

03 Aug '17

Hi all! We're going to have the missed monthly status meeting for July tomorrow. Time will be 19:00 UTC as always and you will get your credentials shortly before the meeting. Agenda proposals so far include: - The 0.4.6 release - The upcoming Hackfest - Design of the RAPPS setup mode Please post any additional agenda proposals here. See you tomorrow! Colin

1 1

Re: [ros-dev] Modularizing the ReactOS repo in Git
by Alexander Sh. 02 Aug '17

02 Aug '17

Since we have RosBE, we can have multiple repositories without actually binding them and download them on demand. Or we can make a build script for every new small module that downloads (clones) repos it needs. 2 авг. 2017 г. 11:41 пользователь "Colin Finck" <colin(a)reactos.org> написал: Hi all! After David has successfully tested a first SVN -> Git conversion of our repo, here comes the next challenge: Finding a way to preserve our current modularization into reactos, rosapps, rostests and paving the way for even more modularization. My vision for the future is a small "core" repo that only contains our host tools and SDK. We could also split off subprojects like fast486/ntvdm or Paint into individual repos. Now that Microsoft has abandoned them under Windows, they may individually attract developers who would never hack on the entire ReactOS repo. Furthermore, 3rd party components could be imported through their repo instead of copy-pasting their code without history (as we do now). Even if that vision is a distant goal, the technology for it is already required for a reactos, rosapps, rostests modularization. Isn't that a perfect scenario for Git submodules? Not sure: I'm not aware that they support the concept of optional modules. You could only check out the "core" repo with all defined submodules. This would make it impossible to use "core" only to build Paint. There also seem to be other drawbacks when using submodules: https://codingkilledthecat.wor dpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/ Alternatives like Git subtrees, Google Repo, and Gitslave exist, but there is even less information about them. Furthermore, I think a good integration into GUI tools like TortoiseGit is also a requirement for most of us. David and I have started to write down our findings: https://docs.google.com/document/d/1Ey1xdS_0GcG7p7ZgHZBh4A3V Mq2uxyw5MpnUXbT8z6w/edit Your input on this is very welcome! I guess any migration to Git is blocked before we have a solution here. Cheers, Colin _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

2 3

Modularizing the ReactOS repo in Git
by Colin Finck 02 Aug '17

02 Aug '17

Hi all! After David has successfully tested a first SVN -> Git conversion of our repo, here comes the next challenge: Finding a way to preserve our current modularization into reactos, rosapps, rostests and paving the way for even more modularization. My vision for the future is a small "core" repo that only contains our host tools and SDK. We could also split off subprojects like fast486/ntvdm or Paint into individual repos. Now that Microsoft has abandoned them under Windows, they may individually attract developers who would never hack on the entire ReactOS repo. Furthermore, 3rd party components could be imported through their repo instead of copy-pasting their code without history (as we do now). Even if that vision is a distant goal, the technology for it is already required for a reactos, rosapps, rostests modularization. Isn't that a perfect scenario for Git submodules? Not sure: I'm not aware that they support the concept of optional modules. You could only check out the "core" repo with all defined submodules. This would make it impossible to use "core" only to build Paint. There also seem to be other drawbacks when using submodules: https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-should… Alternatives like Git subtrees, Google Repo, and Gitslave exist, but there is even less information about them. Furthermore, I think a good integration into GUI tools like TortoiseGit is also a requirement for most of us. David and I have started to write down our findings: https://docs.google.com/document/d/1Ey1xdS_0GcG7p7ZgHZBh4A3VMq2uxyw5MpnUXbT… Your input on this is very welcome! I guess any migration to Git is blocked before we have a solution here. Cheers, Colin

1 0

Enabling themes in 3rd stage
by Giannis Adamopoulos 31 Jul '17

31 Jul '17

Hello, After recent changes in explorer, comctl32 and uxtheme the state of themes in reactos was improved a lot. I would like to ask your opinions about enabling themes in 3rd stage. It is also possible to have an option in 2nd stage to select if we want 3rd stage to have themes enabled. Do you think this should be enabled by default or not? All ideas are welcome. My intention is to complete it ASAP so that it can make in the release. Thanks, Giannis Adamopoulos

7 8

Re: [ros-dev] Enabling themes in 3rd stage
by Robert Naumann 31 Jul '17

31 Jul '17

I'd vote for a page in 2nd stage. If we would make it by default then only in the releases. Am 31.07.2017 16:31 schrieb "Giannis Adamopoulos" < giannis.adamopoulos(a)reactos.org>: Hello, After recent changes in explorer, comctl32 and uxtheme the state of themes in reactos was improved a lot. I would like to ask your opinions about enabling themes in 3rd stage. It is also possible to have an option in 2nd stage to select if we want 3rd stage to have themes enabled. Do you think this should be enabled by default or not? All ideas are welcome. My intention is to complete it ASAP so that it can make in the release. Thanks, Giannis Adamopoulos _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

1 0

Re: [ros-dev] Enabling themes in 3rd stage
by Javier Agustìn Fernàndez Arroyo 31 Jul '17

31 Jul '17

I didnt say so, lol El 31/07/2017 20:38, "Giannis Adamopoulos" <giannis.adamopoulos(a)reactos.org> escribió: So you volunteer to create a theme? Hermès BÉLUSCA-MAÏTO <hermes.belusca(a)sfr.fr> wrote on Mon, July 31st, 2017, 6:24 PM: > What about the « Whistler » - like theme ? ^^ > > > > H. > > > > De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Mark Jansen > Envoyé : lundi 31 juillet 2017 17:18 > À : ReactOS Development List > Objet : Re: [ros-dev] Enabling themes in 3rd stage > > > > I like this theme! > > > > Op 31 jul. 2017 16:44 schreef "Ged Murphy" <gedmurphy.maillists(a)gmail.com >: > > A link to the theme I mentioned would probably help... > http://aportz19.deviantart.com/art/Basic-Lite-and-Basic- 8-Visual-Style-for-Windows-XP-393826050 > > > -----Original Message----- > From: Ged Murphy [mailto:gedmurphy.maillists@gmail.com] > Sent: 31 July 2017 15:43 > To: 'ReactOS Development List' <ros-dev(a)reactos.org> > Subject: RE: [ros-dev] Enabling themes in 3rd stage > > Do you have some pics?? > > I've always been a big fan of seeing the Basic Lite theme being on by default, which would give ros a much more modern look and feel. > We're missing the start menu implementation for this though. > > > > -----Original Message----- > From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of Giannis Adamopoulos > Sent: 31 July 2017 15:29 > To: ros-dev(a)reactos.org > Subject: [ros-dev] Enabling themes in 3rd stage > > Hello, > After recent changes in explorer, comctl32 and uxtheme the state of themes in reactos was improved a lot. I would like to ask your opinions about enabling themes in 3rd stage. It is also possible to have an option in 2nd stage to select if we want 3rd stage to have themes enabled. Do you think this should be enabled by default or not? All ideas are welcome. My intention is to complete it ASAP so that it can make in the release. > > Thanks, > Giannis Adamopoulos > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

1 0

Re: [ros-dev] Enabling themes in 3rd stage
by Giannis Adamopoulos 31 Jul '17

31 Jul '17

So you volunteer to create a theme? Hermès BÉLUSCA-MAÏTO <hermes.belusca(a)sfr.fr> wrote on Mon, July 31st, 2017, 6:24 PM: > What about the « Whistler » - like theme ? ^^ > > > > H. > > > > De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Mark Jansen > Envoyé : lundi 31 juillet 2017 17:18 > À : ReactOS Development List > Objet : Re: [ros-dev] Enabling themes in 3rd stage > > > > I like this theme! > > > > Op 31 jul. 2017 16:44 schreef "Ged Murphy" <gedmurphy.maillists(a)gmail.com>: > > A link to the theme I mentioned would probably help... > http://aportz19.deviantart.com/art/Basic-Lite-and-Basic-8-Visual-Style-for-… > > > -----Original Message----- > From: Ged Murphy [mailto:gedmurphy.maillists@gmail.com] > Sent: 31 July 2017 15:43 > To: 'ReactOS Development List' <ros-dev(a)reactos.org> > Subject: RE: [ros-dev] Enabling themes in 3rd stage > > Do you have some pics?? > > I've always been a big fan of seeing the Basic Lite theme being on by default, which would give ros a much more modern look and feel. > We're missing the start menu implementation for this though. > > > > -----Original Message----- > From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of Giannis Adamopoulos > Sent: 31 July 2017 15:29 > To: ros-dev(a)reactos.org > Subject: [ros-dev] Enabling themes in 3rd stage > > Hello, > After recent changes in explorer, comctl32 and uxtheme the state of themes in reactos was improved a lot. I would like to ask your opinions about enabling themes in 3rd stage. It is also possible to have an option in 2nd stage to select if we want 3rd stage to have themes enabled. Do you think this should be enabled by default or not? All ideas are welcome. My intention is to complete it ASAP so that it can make in the release. > > Thanks, > Giannis Adamopoulos > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev

2 1

Re: [ros-dev] Enabling themes in 3rd stage
by Javier Agustìn Fernàndez Arroyo 31 Jul '17

31 Jul '17

hi all, honestly, i dont think theming is a crucial choose when installing. i would not add that screen, at 2nd stage at least. Maybe at 3rd, right after 1st run.... El 31/07/2017 18:28, "Hermès BÉLUSCA-MAÏTO" <hermes.belusca(a)sfr.fr> escribió: What about the « Whistler » - like theme ? ^^ H. *De :* Ros-dev [mailto:ros-dev-bounces@reactos.org] *De la part de* Mark Jansen *Envoyé :* lundi 31 juillet 2017 17:18 *À :* ReactOS Development List *Objet :* Re: [ros-dev] Enabling themes in 3rd stage I like this theme! Op 31 jul. 2017 16:44 schreef "Ged Murphy" <gedmurphy.maillists(a)gmail.com>: A link to the theme I mentioned would probably help... http://aportz19.deviantart.com/art/Basic-Lite-and-Basic- 8-Visual-Style-for-Windows-XP-393826050 -----Original Message----- From: Ged Murphy [mailto:gedmurphy.maillists@gmail.com] Sent: 31 July 2017 15:43 To: 'ReactOS Development List' <ros-dev(a)reactos.org> Subject: RE: [ros-dev] Enabling themes in 3rd stage Do you have some pics?? I've always been a big fan of seeing the Basic Lite theme being on by default, which would give ros a much more modern look and feel. We're missing the start menu implementation for this though. -----Original Message----- From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of Giannis Adamopoulos Sent: 31 July 2017 15:29 To: ros-dev(a)reactos.org Subject: [ros-dev] Enabling themes in 3rd stage Hello, After recent changes in explorer, comctl32 and uxtheme the state of themes in reactos was improved a lot. I would like to ask your opinions about enabling themes in 3rd stage. It is also possible to have an option in 2nd stage to select if we want 3rd stage to have themes enabled. Do you think this should be enabled by default or not? All ideas are welcome. My intention is to complete it ASAP so that it can make in the release. Thanks, Giannis Adamopoulos _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

1 1

Re: [ros-dev] Enabling themes in 3rd stage
by Giannis Adamopoulos 31 Jul '17

31 Jul '17

Lautus: http://i.imgur.com/lqrqvtu.png Basic lite (without any font changes): http://i.imgur.com/BcTIF9m.png To make basic lite look better needs to substitute its fonts with some we already have. Ged Murphy <gedmurphy.maillists(a)gmail.com> wrote on Mon, July 31st, 2017, 4:44 PM: > A link to the theme I mentioned would probably help... > http://aportz19.deviantart.com/art/Basic-Lite-and-Basic-8-Visual-Style-for-… > > > -----Original Message----- > From: Ged Murphy [mailto:gedmurphy.maillists@gmail.com] > Sent: 31 July 2017 15:43 > To: 'ReactOS Development List' <ros-dev(a)reactos.org> > Subject: RE: [ros-dev] Enabling themes in 3rd stage > > Do you have some pics?? > > I've always been a big fan of seeing the Basic Lite theme being on by default, which would give ros a much more modern look and feel. > We're missing the start menu implementation for this though. > > > > -----Original Message----- > From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of Giannis Adamopoulos > Sent: 31 July 2017 15:29 > To: ros-dev(a)reactos.org > Subject: [ros-dev] Enabling themes in 3rd stage > > Hello, > After recent changes in explorer, comctl32 and uxtheme the state of themes in reactos was improved a lot. I would like to ask your opinions about enabling themes in 3rd stage. It is also possible to have an option in 2nd stage to select if we want 3rd stage to have themes enabled. Do you think this should be enabled by default or not? All ideas are welcome. My intention is to complete it ASAP so that it can make in the release. > > Thanks, > Giannis Adamopoulos > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev

4 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev