Picon

GitHub Issue #13 - Change files in Docs project to be markdown files

Documentation has been converted to MarkDown as requested.

Please see pull #24 https://github.com/CosmosOS/Cosmos/pull/24

Kevin Meredith

------------------------------------
Posted by: Kevin Meredith <kebinu.chiousu@...>
------------------------------------

--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------

------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/Cosmos-Dev/
(Continue reading)

Picon

Current state

I started a bit on network. Looks promising, however, I hit a compiler bug. (CPU exception 6, invalid opcode at EIP 0x3, so something is probably corrupting the stack..)



__._,_.___
Posted by: Matthijs ter Woord <matthijsterwoord-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

Github

We've moved sourcecode over to github:

www.github.com/CosmosOS/Cosmos




__._,_.___
Posted by: Matthijs ter Woord <matthijsterwoord-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

GIT Discussion


As a proof-of-concept, the entire COSMOS source code repository, including all history, has been ported to the following GIT repository:

Website:

GIT:

If the group decides to go forward, the GIT repository would be re-created once more with the most recent source code and CodePlex's user name mapped to e-mail addresses for the versioning metadata (optional for those opt-in).

With Git & GitHub in place, it should be much simpler to setting up Continuous Integration (CI) to test the builds and later even build the entire user-kit as well.


On Wed, Dec 3, 2014 at 5:25 AM, Matthijs ter Woord matthijsterwoord-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [Cosmos-Dev] <Cosmos-Dev-hHKSG33TihhbjbujkaE4pw@public.gmane.org> wrote:


Replying in a combined post:

As Chad already said: pull requests aren't available for Cosmos, because we don't use Git/Mercurial

At this moment, we don't have a CI-setup. We also don't have any automated tests. If we would have some, there would be possible ways to get CI-going right now. (I have a machine to sponsor for that, and other options as well)


I like git, but not because of the multi user workflow, just because of the split of commiting and pushing to the server (ie, commits are blazingly fast, even if its several MB's to upload). Don't have too much experience with multi-dev environments..


Luke:

- Moving to Github "just to make clear old releases are from the past" is like moving buttons around in software, just to show the user you worked on a form. On our current codeplex site, it should be clear enough to users what the current version is, and what previous versions are. No point in switching sites for that.

- Playground projects in the main solution has a big advantage: I can add tests in my project, and someone can very easily jump in and have test my code for bugs.
I know using git you can switch to a different fork, but that means lots of network activity.
Also, sub projects or sobmodules are complicated to setup in git.




2014-12-02 21:26 GMT+01:00 Luke Herbert herbert.luke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [Cosmos-Dev] <Cosmos-Dev-hHKSG33TihhbjbujkaE4pw@public.gmane.org>:


Hello,

I have been a longtime Cosmos follower. Currently the rules that allow people to contribute to Cosmos (https://cosmos.codeplex.com/wikipage?title=How%20to%20fix%20an%20issue%20with%20Cosmos%20or%20start%20developing%20for%20us ) are as follows:

1. You are going to need to join the mailing list and introduce yourself with your Codeplex username and real name you will also need to mention any changes here before you make them. (https://groups.yahoo.com/neo/groups/Cosmos-Dev/info)
2. Once you get developer status you are going to need to get a copy of the source, we use team explorer in Visual Studio to do our source control, you will need to download a copy of the source using this, you can find the required info to do this in the Source Code tab above (you must be signed in to get this info)
3. Tell the project coordinators that you are making a change by starting a new topic on the mailing list, you will need to tell them what you are doing. If your changes sound good they will tell you to shelve the changes so they can check them. If all is good they will tell you to commit those changes. NEVER commit without asking.

These rules would not be needed when using git with github, I believe this alone would be a great help in getting people to help working with Cosmos (although personally I see far more long-term potential in MOSA).  

In addition, the source for Cosmos contains a number of projects under 'users', using git this problem simply disappears and small personal experiments can make use of source code revision and not impact the main core development.

Further, anybody who has followed Cosmos for a while, will see the regular "I am using milestone X, how do I..." messages. Moving to github would give you the opportunity to wipe the slate clean and make it very clear that those releases are a thing of the past. Should people be running an older version pulled from github (for some reason) it would be much simpler to first tell them to simply update from the master branch.

Yours, Luke

-Luke Herbert

On 2 December 2014 at 18:59, Phil Garcia phil-LfjDTmiWaXNl57MIdRCFDg@public.gmane.org [Cosmos-Dev] <Cosmos-Dev-hHKSG33TihhbjbujkaE4pw@public.gmane.org> wrote:
 

Let me break down the two issues and provide some first hand experience:

1. Merging - Merging is a fact of life for any developer working on a project with other contributors. GIT makes this process much easier. GIT has a very intelligent merge process and can automatically merge most code except for when true conflicts (i.e.., where multiple developers modified the same line of code.) And even then, resolving conflict is pretty easy using a tool like TortoiseGIT (TortoiseGIT integrates with the Windows explorer). It shows you the conflicts, presents the conflicts and gives you the ability to pick and choose which lines to merge or not. It's pretty painless. Most of the time a merge is a trivial task.

2. GitHub & Patch Request & Merging - GitHub makes the process of creating patch requests, managing issues, and merging almost point and click tasks. As a contributor, you simply click "Patch Request" within your repository and branch on the website. By default, it defaults to the root repository (but you can change that if you wish to send the patch request to a colleague for example). On the other side, the "Patch Request" comes in as an issue. If there are no conflicts, it takes one click to "Merge". That's the power of GIT with GitHub.

I understand that learning new tools, such as GIT and GitHub, require some up front learning. However, I think it's valuable - personally and professionally, since there is clearly a move to distributed systems in the open source communities, and also a move to better source code workflows for both the open source and professional communities.

I have a several years of working experience with GitHub and Git. I would be happy to demonstrated to setup a screen-sharing session with anyone on the COSMOS team to demonstrate these features.











__._,_.___
Posted by: Phil Garcia <phil-LfjDTmiWaXNl57MIdRCFDg@public.gmane.org>


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

X#

Hello I have just started back up with cosmos and I what to know to use X#. I see the tutorials and info on the physical language but how do you use the code. Do you call it in the c# kenerl code?



__._,_.___
Posted by: shawk08033-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

Source Reorganized

Just a heads-up. The Cosmos source has been reorganized and cleaned up. We are going with a flat structure on disk and we will use solution folders to organize projects. I think I fixed up all the paths in the user projects, but I didn't open all of them to test. If anything is broken, let me know, and I will get it fixed up.


__._,_.___
Posted by: Charles Betros <charles.betros-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

Cleanup.....

With MS releasing VS Community, we are going to remove "express" support, as it basicaly is dead now..

Any takers?

(Trivalik, can you please contact me?)



__._,_.___
Posted by: Matthijs ter Woord <matthijsterwoord-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

VS2013 Community Edition

Since MS has now released what basically amounts to VS2013 Professional as a free community edition(http://www.visualstudio.com/products/visual-studio-community-vs) for non-commercial use or commercial use for small organizations, should this maybe be the premier target for Cosmos Developer kit?


It would eliminate the need for any support for the Express editions, and provide a semi-stable basis for developers to target


BTW, I'm not volunteering. Just a suggestion ;-)



__._,_.___
Posted by: sschocke-LzPWRcFV0Gjk1uMJSBkQmQ@public.gmane.org


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

Dev-Kit Setup error [1 Attachment]

Hello,


When

  1. Open a command prompt and "cd" to the root directory of the source.
  2. Run "install.bat"

then Error says: "Setup did not start". I add picture p>


I have VS Ultimate, Windows 8.1 pro


I need some help.


Thanks



__._,_.___

Attachment(s) from selcuk.gural-/E1597aS9LQAvxtiuMwx3w@public.gmane.org [Cosmos-Dev] | View attachments on the web

1 of 1 Photo(s)

Posted by: selcuk.gural-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

Latest checkin

Question for trivalik: You changed the cleanup sequence of the installation. Are you sure innosetup will cleanup old files when doing updates? We introduced the cleanup sequence because old files wouldn't get deleted accordingly....



__._,_.___
Posted by: Matthijs ter Woord <matthijsterwoord-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___
Picon

Implementing plugs.

Hello,

this is my first time asking for help,

I want to try and implement a plug, more specifically data types like Dictionary<Tkey, Tvalue>.

Im not sure if this would be a plug? and any tips on creating plugs ?

 



__._,_.___
Posted by: myvarhd-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


--------------------------------------------------
More things to join for Cosmos!

1) Cosmos chat room:
http://tinyurl.com/pc7bds

2) Please add yourself to the map:
http://tinyurl.com/qhttde

3) Help publicity and join our Facebook page:
http://tinyurl.com/plrloa

--------------------------------------------------






__,_._,___

Gmane