Its soon getting time to freeze development of version 2.3 that includes boostfuel, nitrouscontrol, biking shifter, gear based shifting times and some new maps too. This means that I am soon stopping further development of version 2.3 and we shall move into developing 2.4 or maybe 3.0 how ever we wish to call it.
There will be no major improvements or new functionality from end user perspective, but some fundamental changes to the development environment.
Jasa and Justin have been during past weeks working together a shared codebase development which means that we shall take yet another step towards becoming a more opensource development project enabling developers to start contributing to the codebase more easily.
I am really glad that this may now help us to reach a point where we have a truly multideveloper environment for implementing new functionality into ecueditor.com
__________________
When asking a question, you can also consider posting it to facebook:
Jasa and I have been running a trial with editing ECU Editor source code using mucrial and bitbucket.org . So far so good, we are starting to document the best practices for multiple people working on the same code base.
Glad to Hear Petrik is getting some LONG OVER DUE Help in the Software Side. Thank you guy's for Stepping up and Helping Make ECU Editor what it is.....Simply the BEST!
that is great justin, i have had murical installed since last sept, or nov, when jasa was setting it up, now i have gone to gen2 and am excited about all of this....
__________________
09 busa.????? now what....still got what it takes.......!
that is great justin, i have had murical installed since last sept, or nov, when jasa was setting it up, now i have gone to gen2 and am excited about all of this....
Yeah it should be a good step forward! We are also restructuring the code into Common, Gen1, Gen2 and BKing folders and cleaning up the code base to make it easier to understand and work on the code.
Glad to Hear Petrik is getting some LONG OVER DUE Help in the Software Side. Thank you guy's for Stepping up and Helping Make ECU Editor what it is.....Simply the BEST!
Its great to be able to contribute to such a cool project, Petrik (and the other contributors) have done so much already to give us a great way to better control the ecu on our bikes!
I still scratch my head when i see guys on the other bike forums still buying Power Commanders etc for their Busas and BKings
Yeah - back in business again sorry for being away so long but I have had too much other projects..
PetriK your latest changes have been uploaded and it seems that Justin has also made bunch of structure changes for code. Advantages of different Time Zones - code will be modified all around the clock
After we have done all these trivial changes, we need to establish some kind of testing period to check out that all functionality is still working. There are no functional changes introduced but still when files will fly around folders there might be breaks and wrong files called etc..
After we have understanding that it works as should, we publish the central repo for everyone. In the meantime it is private one, but people can join just by creating account on bitbucket.org and let me or Justin to know about it so we can grand access for current test repo.
All those changes are needed in order to keep codebase in shape and enable parallel development without waste effort for merging files on every push or pull.
Structure follows bike versions and file types. There are folder for G1, G2, Bking and common files. Also for bin files will have/is already having (according to latest changeset in bitbucket) own folder. In that way bike specific source are handled in one folder. Common files are maintained in one.
Also some VB internal structure change will happen - just to secure future proof maintainability of code.
We also try to create short instructions for code contributors how to install and use mercurial and central repo to keep all development in good shape. We'll follow pretty much Open Source common practices having contributors, package owners and some other roles. Just to keep parallel development in shape. I'm hoping to see bunch of contributions once SW is available for everyone. Still there is needed kind of control what can be contributed on release branches, when, how to solve change conflicts, , how to test each release and how to keep all the SW in good shape with good quality - in here Package Owners play big role with persons who create releases.
But be patient you will see it in live pretty soon..
-- Edited by jasa on Thursday 17th of June 2010 09:40:04 AM
Great....now I may have to spend even more time online and working on motorcycle related things.... I guess I'm going to have to get my wife a wrap for her wedding ring or something....
Seriously though, great work on making this happen!
Is Sourceforge file sharing a benefit to something like this? Perhaps that is "Too Public"? Maybe mimicing their file sharing techniques adn keeping it more in a targeted usergroup?
Is Sourceforge file sharing a benefit to something like this? Perhaps that is "Too Public"? Maybe mimicing their file sharing techniques adn keeping it more in a targeted usergroup?
Good question..
No other reason than bitbucket is "small" enough for testing purposes - I just wanted to keep this small in this pilot phase.
I have no more experience on bitbucket than on sourceforge, therefore no prefer solution by me - Bitbucket was just selected from the list initially I was setting up own Linux Mercurial server for this but hosting it is too big task for me. I have one but only for my personal projects.
On the other hand as we have seen there are only handful of people who really contributes code so I guess Sourceforge won't give any big advantage for us with it's bigness - I might also be wrong...
But as said no prefer solution and if we see that Sourceforge would be better I have no problems to clone repo over there. We can locate repo(s) where ever Mercurial servers are supported when piloting is done and structural changes are done for EE code.
Is Sourceforge file sharing a benefit to something like this? Perhaps that is "Too Public"? Maybe mimicing their file sharing techniques adn keeping it more in a targeted usergroup?
Good question..
No other reason than bitbucket is "small" enough for testing purposes - I just wanted to keep this small in this pilot phase.
I have no more experience on bitbucket than on sourceforge, therefore no prefer solution by me - Bitbucket was just selected from the list initially I was setting up own Linux Mercurial server for this but hosting it is too big task for me. I have one but only for my personal projects.
On the other hand as we have seen there are only handful of people who really contributes code so I guess Sourceforge won't give any big advantage for us with it's bigness - I might also be wrong...
But as said no prefer solution and if we see that Sourceforge would be better I have no problems to clone repo over there. We can locate repo(s) where ever Mercurial servers are supported when piloting is done and structural changes are done for EE code.
I didn't know "bitbucket" was a file sharing / management type site. Sounds like it is good to go!
I really should get more into the software side of things....
From bitbucket's public repository list you should be able to find ecueditor repository where all further development for Ecueditor will happen. EE_test will be saved for Mercurial testing purposes for us and for new contributors to learn and test mercurial tool.
Wiki on ecueditor repo will have soon all needed info. Justin has already made some good work already.
Anyone who has account on Bitbucket can see EE code and clone his/her local repo. Writing to central repo is still restricted - just to avoid too much parallel development for same files and in that way to avoid irrelevant merge work.
Those who really wants to contribute can contact me (jasa) on G1 case, Justin (jkwool) on Bking case and pertik in other cases (G2 and common files). Those are the roles at beginning.
When more people will join in development we will grand also writing access for them and maybe we can get more people to share responsibilities too. EE releasing and releases distribution will still happen through www.ecueditor.com.
Here is direct link to brand new ecueditor public repository:
Is someone (jasa, justin, or PetriK) paying for a membership to bitbucket for the group? If so, please do not hesitate to allow us to pay for the membership.
Is someone (jasa, justin, or PetriK) paying for a membership to bitbucket for the group? If so, please do not hesitate to allow us to pay for the membership.
Thanks for your offer, but Bitbucket offers 1G free space. No money needed so far. Let's see what kind of services will be needed in the future and if we need to upgrade our service level let's check the situation then..
What would be very good is to get a web page designer for www.ecueditor.com and then over some time also we can put it into a hosted environment now when there is more persons that can build the code - not right now, but when we have learned first how to work together with a shared codebase.
__________________
When asking a question, you can also consider posting it to facebook:
What would be very good is to get a web page designer for www.ecueditor.com and then over some time also we can put it into a hosted environment now when there is more persons that can build the code - not right now, but when we have learned first how to work together with a shared codebase.
Heh just checked from ecueditor repo - PetriK you are learning pretty fast.. Full speed once again lot of changes in short time as well as bunch of issue reports crated.
no, not full speed - not even close as fast as you. just had promised to get something done today so that we can test it next week. tight timeschedule on this one.
__________________
When asking a question, you can also consider posting it to facebook:
http://www.bitbucket.org/ecueditor/ecueditor/wiki/ECU_Editor_Coding_Conventions 3. Clone local repo: on commend line: hg clone <your bitbucket account>@bitbucket.org/ecueditor/ecueditor [your destination folder on local drive.This is optional and if not given local repo will be created at the location where hg clone command was given] Same can also be executed through GUI (hg clone) 4. install Visual Basic 2008 Google helps
Now you are ready to work on local repo.
Once you have something ready please contact, PetriK (G2 and common parts), Justin (Bking part) or me (G1 part) to check/review your SW contribution.
Before contributing anything, Id propose to create issue on bitbucket issue tracker to describe your idea/contribution. In that way we all can give comments for your idea and be prepared for upcoming SW contribution.
-- Edited by jasa on Wednesday 30th of June 2010 10:56:32 AM
http://www.bitbucket.org/ecueditor/ecueditor/wiki/ECU_Editor_Coding_Conventions 3. Clone local repo: on commend line: hg clone <your bitbucket account>@bitbucket.org/ecueditor/ecueditor [your destination folder on local drive.This is optional and if not given local repo will be created at the location where hg clone command was given] Same can also be executed through GUI (hg clone) 4. install Visual Basic 2008 Google helps
Now you are ready to work on local repo.
Once you have something ready please contact, PetriK (G2 and common parts), Justin (Bking part) or me (G1 part) to check/review your SW contribution.
Before contributing anything, Id propose to create issue on bitbucket issue tracker to describe your idea/contribution. In that way we all can give comments for your idea and be prepared for upcoming SW contribution.
-- Edited by jasa on Wednesday 30th of June 2010 10:56:32 AM
THAT'S GREAT! Thank You you Jasa, like I've mentioned B4 around here......I have No experience with Code, But AWAYS willing to learn something new. Thanks to "ALL" involved For giving us a Way to Learn and Be apart of ECU Editor.
I am hoping to find some useful bits for my project on a Suzuki Boulevard C50. I'd like to make a logger for my bike, and from what I understand the ECU is based on the GSXR ECU. So I hope that the communication protocol is the same or at least similar.
I've been reading the threads here for a long time, and figured it was time to sign up, and possibly contribute to the ecu editor.
This is now very possible with the bitbucket repo, Python, hg, and VB.
I've cloned the repo to my hg folder as per Jasa's instructions, and will start digging in.
I can't promise big things except a willingness to learn new stuff.
I recently took on JavaScript at work....found it frustrating and fascinating once I got the hang of it, and hope to have as much fun with VB.
Thanks to Jasa, Petrik, and JK for making all their work available in an orgainized place (bitbucket), and to Smitha (and many others) for testing and their feedback!!
Regards!
J
-- Edited by GenOneTurbo on Friday 9th of July 2010 08:40:29 PM
stayed away for a while and now that I am back I am very pleased to see the great work that is done in this bord. Keep it up the new beta version is just what I wanted six months ago so I am sure that your path gives to all of us some very usefull tools. I hope that during this winter both gen 1 & 2 will be put to the test on the dyno and hopefully to the dragstrip. Thanks to all of you .
The shared codebase seems to work very well for all of us. Thanks for Jasa and Justin for setting it up - and a very prosperous new year to all of you !!!
__________________
When asking a question, you can also consider posting it to facebook: