You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(34) |
Sep
(56) |
Oct
(12) |
Nov
(5) |
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(26) |
Feb
(15) |
Mar
(31) |
Apr
(7) |
May
(3) |
Jun
(2) |
Jul
(30) |
Aug
(3) |
Sep
(6) |
Oct
(2) |
Nov
(3) |
Dec
(6) |
2004 |
Jan
(43) |
Feb
(26) |
Mar
|
Apr
(4) |
May
|
Jun
(5) |
Jul
(21) |
Aug
(2) |
Sep
(1) |
Oct
(5) |
Nov
(1) |
Dec
(1) |
2005 |
Jan
(8) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(5) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
(24) |
Mar
(41) |
Apr
(2) |
May
(4) |
Jun
(4) |
Jul
(9) |
Aug
(10) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
(3) |
Nov
(5) |
Dec
|
2012 |
Jan
(5) |
Feb
(1) |
Mar
(18) |
Apr
(13) |
May
(5) |
Jun
(5) |
Jul
(7) |
Aug
(10) |
Sep
(4) |
Oct
(5) |
Nov
(29) |
Dec
(5) |
2013 |
Jan
(10) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(3) |
Oct
(3) |
Nov
(1) |
Dec
(2) |
2016 |
Jan
(2) |
Feb
(4) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Tim D. <tho...@ma...> - 2013-01-27 11:44:45
|
Hi Berenger, Certainly you are welcome to stop working. But it is a sad truth that there are more people interested in using a product than writing code to support it. Why? In many cases it is simple lack of time or expertise. I don't know whether or not I have the expertise to be a meaningful contributor, but I *know* I lack the time to do anything meaningful at the moment. I have my own personal coding projects, a demanding job, a family and non-coding hobbies. There simply isn't enough time to go around. PySide is going through some struggles right now and that is a project that has more than one developer familiar with the code base, a production product that is used by numerous people and users who want to contribute. But with Nokia destroying itself trying to keep Microsoft relevant the official corporate backing is gone. The Nokia employee who managed the project *tried* to do a handoff "to the community", but predictably it went less than smoothly. What I'm trying to say is that the situation you and autorealm are in is not entirely unexpected. Maybe at some point down the road there'd be more community effort (I was looking forward to there being enough completed to look at writing plugins), but there certainly is no guarantee of that. If you need more participation in order to make it worth your while to continue developing -- great, that is up to you. Just like it is up to me to prioritize working on creating some highly stylized shaders for 3d work over contributing to autorealm. But there is no need to go insulting people. No one promised you anything (at least on this list) so there was no statement for your trust in which to be violated. There is no community spokesman, there is just a collection of people who monitor the list and (infrequently) post to it. Tim Doty On Jan 27, 2013, at 12:30 AM, ber...@ne... wrote: > Ok. > It is enough. > I'm leaving. > > AutoREALM was fun, and I could have sent it to a working point. Well, > it is possible I will keep an eye on my own source code, but nothing > enough to make it alive. > > Why? > Because there is no fucking community!!! > At a moment, when I started to resurrect it, I thought I could have > some help, I thought I would not be alone on the project... > The experience I had with autorealm was.... you are better to learn > alone! > Alone! > Alone! > > Community? Are you fucking joking here? I was stupid to trust it.... I > had no help... > Oh, I forgive the contribution about finishing cmakefiles, but who > cares? We had no return! > I had no try on windows? Is it so hard? > Yes, I know, the software is not as useful as version 2.21, but I am > alone, to reproduce a software built by more than 10 people! > > > Conclusion: I will stop my contributions. I will make some > documentation about the code I did, and: : : BYE BYE > Yes, byebye. > People always work for something, at least it is friendship. Clone the > source quickly, I could change the license, now that I am bored... > because I might want to use my work to live, since I have no job. Be > quiet, I will always respect licenses. But remember who own them. I only > have my source code licences. > > If you wan't to insult me : > http://www.inlibroveritas.net/auteur13255.html > > > ------------------------------------ > > > Yahoo! Groups Links > > <*> To visit your group on the web, go to: > http://groups.yahoo.com/group/AutoREALM/ > > <*> Your email settings: > Individual Email | Traditional > > <*> To change settings online go to: > http://groups.yahoo.com/group/AutoREALM/join > (Yahoo! ID required) > > <*> To change settings via email: > Aut...@ya... > Aut...@ya... > > <*> To unsubscribe from this group, send an email to: > Aut...@ya... > > <*> Your use of Yahoo! Groups is subject to: > http://docs.yahoo.com/info/terms/ > |
From: Peter K. <le...@gm...> - 2013-01-27 09:12:38
|
Hi Berenger, We both started the "ressourection". I stopped because it was to much for me. And I struggeling with a lot of things. There was one who did the cmake stuff. So In parts you were not alone. And you sounded so knowing that I thought you will be faster then with my noob skills. (I would turn project 3 circles more, because I do not know) But in main parts. Most people only want to consume. Not be creativ. So best is to do things for yourself. Take friendship up as it comes along the way. Autorealm as a Open Source Project is the best documentation of your skill. It may help you find a new job quicker. (add Lead developer Autorealm Project to your CV) I can understand if you want to stop now. If you realy think that is your best move. Stopp it. There is no point to continue if you do not have fun and a win of it. my regards Peter P.S.: If you want to talk, you can always mail me personly. I'll answer. |
From: <ber...@ne...> - 2013-01-27 06:30:54
|
Ok. It is enough. I'm leaving. AutoREALM was fun, and I could have sent it to a working point. Well, it is possible I will keep an eye on my own source code, but nothing enough to make it alive. Why? Because there is no fucking community!!! At a moment, when I started to resurrect it, I thought I could have some help, I thought I would not be alone on the project... The experience I had with autorealm was.... you are better to learn alone! Alone! Alone! Community? Are you fucking joking here? I was stupid to trust it.... I had no help... Oh, I forgive the contribution about finishing cmakefiles, but who cares? We had no return! I had no try on windows? Is it so hard? Yes, I know, the software is not as useful as version 2.21, but I am alone, to reproduce a software built by more than 10 people! Conclusion: I will stop my contributions. I will make some documentation about the code I did, and: : : BYE BYE Yes, byebye. People always work for something, at least it is friendship. Clone the source quickly, I could change the license, now that I am bored... because I might want to use my work to live, since I have no job. Be quiet, I will always respect licenses. But remember who own them. I only have my source code licences. If you wan't to insult me : http://www.inlibroveritas.net/auteur13255.html |
From: <ber...@ne...> - 2013-01-26 00:08:14
|
Hello. I am starting to stop using IDEs for my developments and so, I am completely remaking the cmake build system. I think when I will have finish that, I will start to upload binaries for debian and windows. Then, when this job will be done, enhancements to the plug-in system will hopefully start to become easier. And if I manage things correctly, adding a plug-in will not need to add it in any cmake file, which means less headaches for people willing to contribute to autorealm v3. |
From: <ber...@ne...> - 2012-12-28 21:39:42
|
Le 26.12.2012 17:45, ber...@ne... a écrit : > The next alpha version, which should be released in few time will > bring some new features: > _ toolbars support > _ greatly improved configuration system > _ more powerful menu engine > > I did not implemented tessellation yet as I would like to do, because > I will needs to learn how to use openGL v2 minimum, and I've found no > code snippet about how to use it with wxWidgets. > > Contributors or people curious to build it will also enjoy: > _ CMake support, it is now really easier to build autorealm and it's > plugins, thanks to steve the ripper. > _ rewritten menu engine, which is easier to read > _ menu engine is no longer an external module, but is integrated > directly in the "gui project". It have been merged because it is > really smaller and it did not make sense to maintain it into a > different module. > _ menu and toolbars engines uses a small tool I have written, which > consist of a single file: tree.h. This is a generic implementation of > the composite design pattern. You will need that file, downloadable > on > my bitbucket homepage. > > Thanks to the new features, autorealm interface will start to be > usable, and it will allow me to implement tools to do basic tasks, > like changing the used color, so new features for user could start to > come now. > Note that currently, toolbars still does not fully work, I am > investigating why and I think I will fix that before the end of that > week. > > I understand that testing the software in it's current state is not > really fun, due to the lack of features it have. Be patient, I hope > that the most complex things are coming to an end, and so real > features for user will start to come soon... > And if you are wanting to help, making autorealm crash and saying me > how to reproduce the problem is a great help, since it makes the core > software more stable. The more stable the core will be, the faster > features will be implemented. > > Now, I can speak a little about what I plan for 3.0.2: > _ split plugin management for safer API and easier to read code: > drawers and tools must be split, since they have very different uses. > An example is, all possible drawers have to be known at software's > startup, unlike tools, which are only useful if needed by the IHM. > _ merge common code for file formats management into plugin API > instead of duplicating it in save/load plugins. > _ implement a new drawer to make sure plugin API is good enough. It > will make it cleaner in the process, so that contributors could add > their own with less problems. > _ implement xml support, for same reasons as implementing a new > drawer. Why XML when I really dislike it? Because I have no other > idea > of format to implement, and many users asked for it. > _ implement some tools plugin, for same reasons as previous tasks. I > think I'll add easy tools, like color changer. If someone have ideas > for easy things to do, I would be grateful to know it. > > Of course, I will probably *not* implement all of those features in > 3.0.2, since it would take times since I'm alone, but you can hope > implementation of at least 2-3 of the list. > Notice that tessellation is now out of my scope. It is simply because > I'm loosing great times for something like that, which needs many > hours of learning to fix, and while I am doing this, autorealm shows > no progress in terms of usability. > Now, I have the will of rewritting autorealm since a year, and having > such an unusable software makes me sad after all that time and effort > spent. So I'll focus a little more on user features instead of > complex > stuff. > Hopefully, at the birthday of my autorealm repo, autorealm will start > to at least be "sounds usable". I have 26 days for that :) Ok, things are done. I think I'll publish 3.0.1 Sunday, since everything sounds fine. Why Sunday? Because it will let people who want to look at result try to find bugs and things to enhance, in case someone in interested. If there are nothing to signal, the release will come, a little more than 2 months since the last one. Note: testing is really important, since I had myself some loosed time when "porting" the source code between my netbook to my desktop. The point in testing on different computers is to test with various configurations and user's errors, which will give various error messages, or crashes. Knowing error messages you will have is interesting for me, to know what will happen the most often, and how that can be enhanced. Crashes without error messages are far more important, since any crash without error message shows a situation that I did not encounter, and so did not protect the software against it. Each crash should at least explain causes of the crash, this is why I need testing from users not involved in development: to make a software which allows the user to self-explain problems. And problems are easier to solve when the code base is the smaller, of course. Since the user interface mechanism is now complete and clean enough, as I said in my last post, the next thing to greatly improve will be plug-in mechanism. I've learn many things about plugin systems, and AutoREALM did some big steps, so refactoring this is really useful. You may say that I'm a perfectionist to often refactor my code, but proofs are here: creating toolbars engine when menu engine has been refactored only took me few days. Refactoring plugin system will make possible some strong improvement in plug-ins themselves. Some technical details about what will happen in version 3.0.2. Actually, plug-ins are all considered being usable in the same way at very high level. I firstly thought that it could allow interesting tricks to save memory and CPU cycles, but current code shows the flaws of that: code become quickly messy with a lots of things needing dumb implementations, which, in fact, cost more. Code is also harder to read, and stuff is not obvious to the reader (even for me, the author!). Here, the famous quote "All problems in computer science can be solved by another level of indirection" shows how it is error-prone, while the man who said "early optimization is root of evil"... So, here are my plans, in distinct steps: _ remove Drawers inheritance from Plugin. This move will imply that drawers will have to be sent into another folder, and so, configuration will have to be improved. _ make all drawers to be systematically loaded in a first time. Things (starting time, memory consumption and resource usages, probably) might be enhanced by having them simply referenced and only loaded when effectively needed, but I have no clue at the moment for that, so it will wait another version. _ create specialized APIs for loading and saving other file formats. APIs for loading and saving must be separated, because it will, by example, be easier (in future) to save a JPEG that to import one. By importing one, I mean, creating a map from one, which might be possible if someone knows how to do: some other vector based softwares are able to do so. When this will be done, I will try to play with the API, by adding: _ a Drawer which make a line starting with a color, and finish with another one, progressively. _ XML saving/loading plug-ins _ a color selector Those plug-ins should be easier enough to implement, if API is correct. Anyway, when at least the refactoring will be done and at least one new plug-in will be implemented, I'll release the 3.0.2 alpha. With that 3.0.2 alpha release, the code should be clean enough to start a new very important feature: selection. So, starting with 3.0.3, I will hopefully start to release binaries. Hopefully, this version will be released before May. If someone have any comment, idea, suggestions, insults or simply words of encouragement, I'll be happy to read them :) |
From: <ber...@ne...> - 2012-12-26 16:45:58
|
The next alpha version, which should be released in few time will bring some new features: _ toolbars support _ greatly improved configuration system _ more powerful menu engine I did not implemented tessellation yet as I would like to do, because I will needs to learn how to use openGL v2 minimum, and I've found no code snippet about how to use it with wxWidgets. Contributors or people curious to build it will also enjoy: _ CMake support, it is now really easier to build autorealm and it's plugins, thanks to steve the ripper. _ rewritten menu engine, which is easier to read _ menu engine is no longer an external module, but is integrated directly in the "gui project". It have been merged because it is really smaller and it did not make sense to maintain it into a different module. _ menu and toolbars engines uses a small tool I have written, which consist of a single file: tree.h. This is a generic implementation of the composite design pattern. You will need that file, downloadable on my bitbucket homepage. Thanks to the new features, autorealm interface will start to be usable, and it will allow me to implement tools to do basic tasks, like changing the used color, so new features for user could start to come now. Note that currently, toolbars still does not fully work, I am investigating why and I think I will fix that before the end of that week. I understand that testing the software in it's current state is not really fun, due to the lack of features it have. Be patient, I hope that the most complex things are coming to an end, and so real features for user will start to come soon... And if you are wanting to help, making autorealm crash and saying me how to reproduce the problem is a great help, since it makes the core software more stable. The more stable the core will be, the faster features will be implemented. Now, I can speak a little about what I plan for 3.0.2: _ split plugin management for safer API and easier to read code: drawers and tools must be split, since they have very different uses. An example is, all possible drawers have to be known at software's startup, unlike tools, which are only useful if needed by the IHM. _ merge common code for file formats management into plugin API instead of duplicating it in save/load plugins. _ implement a new drawer to make sure plugin API is good enough. It will make it cleaner in the process, so that contributors could add their own with less problems. _ implement xml support, for same reasons as implementing a new drawer. Why XML when I really dislike it? Because I have no other idea of format to implement, and many users asked for it. _ implement some tools plugin, for same reasons as previous tasks. I think I'll add easy tools, like color changer. If someone have ideas for easy things to do, I would be grateful to know it. Of course, I will probably *not* implement all of those features in 3.0.2, since it would take times since I'm alone, but you can hope implementation of at least 2-3 of the list. Notice that tessellation is now out of my scope. It is simply because I'm loosing great times for something like that, which needs many hours of learning to fix, and while I am doing this, autorealm shows no progress in terms of usability. Now, I have the will of rewritting autorealm since a year, and having such an unusable software makes me sad after all that time and effort spent. So I'll focus a little more on user features instead of complex stuff. Hopefully, at the birthday of my autorealm repo, autorealm will start to at least be "sounds usable". I have 26 days for that :) |
From: <ber...@ne...> - 2012-12-22 04:51:31
|
Hello, long time without news, so here are some. I've just finished integration of some portions of clean code I built several weeks ago, which results in a far cleaner, more powerful, and less error-prone automatic menu. Of course, those results are from my own point of view, if nobody try it to give me some different opinions, I'll have no clue about how true it is :) Except the cleaner code, it is also now possible to give menus names which are not related to the file name or the plugin implementing the action, and to make those menus selectable as if they were usual radio or checkbox items. Not tried at the moment, because I have no clue if it is really useful, but it was only 5 lines of code, so I did it. Cost nothing and might give ideas to someone. I also hope that implementation of other GUI features will be easier, notably a toolbar system working in the same way. Just one thing: the code will not compile with a simple "git pull", you will need a file I have sent in another library (which is, in fact, that whole library). Why? Because that file could help other people for their development, since it is a generic implementation of the composite design pattern, a mechanism which allow to build tree data quite easily. I will integrate it with git module (or something like that) as soon as possible. On the graphic side, I did not managed actually to have the damned tessellation behave correctly... I do not know if it will work one day :/ This, and the fact that I discovered that autorealm is currently using a deprecated opengl versions make me think to opengl as my death... So, I have some doubts: should I do some testing on the menu thing and just release a new alpha, or should I try to implement at least one other thing like tessellation, which will dramatically slow down the process? There is also some problems about the lack of modularity of plugins: I will need to split them in more distinct categories: Drawers on a side, Plugins on another. Drawers should all be automatically loaded, unlike the plugins which should only be if and only if they are used by the interface. So, I still have many things to do, some could be fast, some could be slow. Should I wait for more stuff before a release or not? I am starting to think to do more minor releases, because it's easier to show progress when there are more smaller steps. Release early, release often, as they say... So, maybe you'll see AutoREALM v3.0.1 before christmas :D PS: and I just noticed that the end of the world date just passed, and I'm reworking on autorealm... is is a sign? xD |
From: lando <la...@gm...> - 2012-12-13 20:45:56
|
No worries. I'm working at things on my own end as well. Probably not as hard as I could, but this remains one of my top projects. Given time we'll get there. On Thu, Dec 13, 2012 at 11:31 AM, "Morel Bérenger" < ber...@ne...> wrote: > Hello > > I did not gave programming news since a while, because I temporarily > stopped working on autorealm. > > The main reason is that I have discovered that I used openGL 1.1, which is > completely obsolete, and so I need to learn the "new" way of doing things. > > I have some documents related to openGL 2, 3 and 4, and I started to read > them, but there are not so many good, quick and free resources* on that > subject (which sounds quite complex to me) and I do not have enough money > to afford books some people recommended to me. > Sounds like I will have to dig into code snippets and samples more than > lessons and tutorials, but that will take time anyway. Holidays will > probably help a lot. > > There is another reason: I am quite bored by all text editors and IDEs. > vim have poor integration with other applications and is not, IMHO, really > suitable to manage a project with as many files as AutoREALM. Eclipse is > just a pain in the ass: I have only slow machines, and C::B... well, is > better than nothing, but sometimes it makes me angry. > So I started to think to create my own text editor for development, which > obviously use time I can not spend on other projects. > > Finally, I also have some long but interesting documents to read, which > could help me to design better few things in code, by example I am not > very happy of my plug-in API, which need more specialization for code > reduction. ** > > But do not be fear, I do not intend to stop my work on autorealm (it > taught me so many things, and can allow me to learn many other), I'm just > taking some break. > > As hint about what I have to work on in order to go back on autorealm's > dev, here are resources I would like to read and understand. As you can > see, I will not have too much with the 3 weeks of holidays which are > coming for me :D > > *: > https://github.com/g-truc/ogl-samples > http://webstaff.itn.liu.se/~perla/Siggraph2011/content/courses/angel.pdf > > **: http://lcsd05.cs.tamu.edu/slides/keynote.pdf > > PS: of course, if someone knows about good documentation for opengl or > designing of API, I am highly interested. Or just some knowledge on those > topics, or even better some time to contribute ;) > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > |
From: Morel B. <ber...@ne...> - 2012-12-13 16:31:46
|
Hello I did not gave programming news since a while, because I temporarily stopped working on autorealm. The main reason is that I have discovered that I used openGL 1.1, which is completely obsolete, and so I need to learn the "new" way of doing things. I have some documents related to openGL 2, 3 and 4, and I started to read them, but there are not so many good, quick and free resources* on that subject (which sounds quite complex to me) and I do not have enough money to afford books some people recommended to me. Sounds like I will have to dig into code snippets and samples more than lessons and tutorials, but that will take time anyway. Holidays will probably help a lot. There is another reason: I am quite bored by all text editors and IDEs. vim have poor integration with other applications and is not, IMHO, really suitable to manage a project with as many files as AutoREALM. Eclipse is just a pain in the ass: I have only slow machines, and C::B... well, is better than nothing, but sometimes it makes me angry. So I started to think to create my own text editor for development, which obviously use time I can not spend on other projects. Finally, I also have some long but interesting documents to read, which could help me to design better few things in code, by example I am not very happy of my plug-in API, which need more specialization for code reduction. ** But do not be fear, I do not intend to stop my work on autorealm (it taught me so many things, and can allow me to learn many other), I'm just taking some break. As hint about what I have to work on in order to go back on autorealm's dev, here are resources I would like to read and understand. As you can see, I will not have too much with the 3 weeks of holidays which are coming for me :D *: https://github.com/g-truc/ogl-samples http://webstaff.itn.liu.se/~perla/Siggraph2011/content/courses/angel.pdf **: http://lcsd05.cs.tamu.edu/slides/keynote.pdf PS: of course, if someone knows about good documentation for opengl or designing of API, I am highly interested. Or just some knowledge on those topics, or even better some time to contribute ;) |
From: <ber...@ne...> - 2012-11-22 22:10:52
|
Hello, guys. There has been no commits those last days, but it does not means that there are no progress. I am currently working on implementation of tesselation, which will make it possible to draw stars, or hourglasses, by example. The only problem here is simply that I have some doubts about about how to reduce as best as possible the coupling between glu (the "high level" part of opengl) and the render engine. I have also a repository with a full rewrite of the menu system. This rewrite is necessary because the actual system works, ok, but in fact, no. I mean, if conditions are here, it works. But a simple problem, like a corrupter configuration file, or loading a file which need a drawer not present in the menu, will make everything crash. Those problems are due to the fact that there is a high coupling between plugin system and menu system. I known that I would have to rewrite it a day or another, and it appears with my configurations enhancements that it must be done now, because if I implement other things which can have links to configuration, it will become harder and harder to fix all those problems. And as most you know, I have always said that the rewrite can take a very long time, but I want to have something clean, because clean code and design imply less bugs, and less resources waste. It also imply ease of maintenance and enhancements, of course. But December approach quite fast, and I would like to release a new alpha soon, so the alpha 3.0.1 will not have toolbars yet. Maybe for 3.0.2 ;) You should now be used to my opinion changes, I think :D If I find enough time to work on those features, it would be possible to finish at least a basic tesselation this week, and why not have the next release before December. This is for the work I would like to do before release, but there has been some other work: _ now, things will be easier for contributors and testers, since stevetheripper have finished the cmake build system. _ in fact, things will be really easier, because the configuration system is also more robust: it can combine 3 sources for configuration: command-line, user's configuration, and system's configuration. It will take command-line informations, complete them with user's configuration, and if something still lacks, take it from system's configuration. This is at least true on linux, it have not been tested for windows. Yes, this is a signal: I'm waiting for some returns. Oh, and it is also possible to give to autorealm a specific configuration file from command-line to replace the user's one. I hope those news makes someone happy :) |
From: <ber...@ne...> - 2012-11-10 21:10:40
|
Now that cmake build system is done, next high priority targets are tesselation (to have complex polygons) and toolbars, with it's configuration. Tesselation will need probably need basic modifications in the whole render engine, but also opengl knowledge. I have started search for links: http://glprogramming.com/red/chapter11.html http://www.songho.ca/opengl/gl_tessellation.html On the other hand, the toolbar system in split into 2 parts: _ wxWidget's _ configuration system I still have no good clue about doing them, but that should not be too hard, I hope to reuse work done for menu system. This is also a good moment to clean the menu code which is quite dirty. Of course, there are many other things to do, but finishing those will allow to have a new release (https://sourceforge.net/apps/trac/autorealm/roadmap). If someone want to work on one of those tasks, please say it on the mailing list, to allow updating the trac. (note: steevetheripper: you should be able to update the tracker yourself) |
From: <ber...@ne...> - 2012-11-10 18:30:27
|
I just added you to the developper group. Also, I have enhanced (on my repo) the message error. Now, it said what drawer was not found, what it searched for, where he searched, and what he found. Hopefully, that will make futur users' problems easier to solve for them. (There will be no conflicts with your enhancements) Le 10.11.2012 19:05, apile a écrit : > Yes I do have a sourceforge account its stevetheripper > > On Sat, 2012-11-10 at 18:54 +0100, ber...@ne... > wrote: >> Welcome to the first contributor, stevetheripper! >> >> He finished the compilation/installation process with cmake, and >> made a >> cleaner config file. >> Now, compiling and installing will be very easy with cmake: >> _ go into the autorealm folder with a command line >> _ create a folder to contain the temporary stuff (the usual name is >> build) >> _ go in it >> _ run "cmake .. && make" >> _ as administrator, run "make install" >> _ enjoy >> >> Note: that procedure should works on linux (and maybe on mac, I'm >> not >> sure), windows users are invited to add support for their favorite >> operating system. Taking a look to all CMakeLists.txt files and >> adding >> them required lines should be really straightforward. >> >> This enhancement is present on his bitbucket repository and will be >> merged soon in mine (having some strange problems with bitbucket... >> or >> maybe it's my webbrowser uzbl... I'll see). >> >> Also, the wiki page will need to be updated, because procedures will >> become faster to follow. Do you have a sourceforge account? I would >> like >> to add you in developper list, to give you some rights on trac and >> other >> things like that. >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop |
From: apile <api...@gm...> - 2012-11-10 18:06:52
|
Yes I do have a sourceforge account its stevetheripper On Sat, 2012-11-10 at 18:54 +0100, ber...@ne... wrote: > Welcome to the first contributor, stevetheripper! > > He finished the compilation/installation process with cmake, and made a > cleaner config file. > Now, compiling and installing will be very easy with cmake: > _ go into the autorealm folder with a command line > _ create a folder to contain the temporary stuff (the usual name is > build) > _ go in it > _ run "cmake .. && make" > _ as administrator, run "make install" > _ enjoy > > Note: that procedure should works on linux (and maybe on mac, I'm not > sure), windows users are invited to add support for their favorite > operating system. Taking a look to all CMakeLists.txt files and adding > them required lines should be really straightforward. > > This enhancement is present on his bitbucket repository and will be > merged soon in mine (having some strange problems with bitbucket... or > maybe it's my webbrowser uzbl... I'll see). > > Also, the wiki page will need to be updated, because procedures will > become faster to follow. Do you have a sourceforge account? I would like > to add you in developper list, to give you some rights on trac and other > things like that. > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop |
From: <ber...@ne...> - 2012-11-10 17:54:51
|
Welcome to the first contributor, stevetheripper! He finished the compilation/installation process with cmake, and made a cleaner config file. Now, compiling and installing will be very easy with cmake: _ go into the autorealm folder with a command line _ create a folder to contain the temporary stuff (the usual name is build) _ go in it _ run "cmake .. && make" _ as administrator, run "make install" _ enjoy Note: that procedure should works on linux (and maybe on mac, I'm not sure), windows users are invited to add support for their favorite operating system. Taking a look to all CMakeLists.txt files and adding them required lines should be really straightforward. This enhancement is present on his bitbucket repository and will be merged soon in mine (having some strange problems with bitbucket... or maybe it's my webbrowser uzbl... I'll see). Also, the wiki page will need to be updated, because procedures will become faster to follow. Do you have a sourceforge account? I would like to add you in developper list, to give you some rights on trac and other things like that. |
From: <ber...@ne...> - 2012-11-10 14:36:51
|
It can draw shapes of straight lines, save files and reload them. It can NOT save or reload files in old autorealm format. Current file format is a barbarian text format, not really readable by human except if you understand the data structure of autorealm (yes, I can read simple files, but it needs autorealm and boost::serialization knowledge) Le 10.11.2012 10:10, api...@gm... a écrit : > The problem was with the cmake scripts It did not compile the plugins > I partially fixed that. Just to make sure its working properly what > is > the current functionality of Autorealm > Sent from my BlackBerry® wireless device > > -----Original Message----- > From: "Morel Bérenger" <ber...@ne...> > Date: Fri, 9 Nov 2012 16:28:45 > To: Developers of AutoREALM<aut...@li...> > Reply-To: Developers of AutoREALM > <aut...@li...> > Subject: Re: [Autorealm-develop] Autorealm initialization > > Strange. > It seems AutoREALM is able to find and open the config file, but not > to > find the good plug-ins... > > What is your operating system? I guess it is a linux distro, but I > would > like to be sure... > > Did you compiled autorealm with the unfinished cmake scripts in the > repo, > or with C::B? > If with the cmake scripts, IIRC, names could be different, so check > that... (but for color, it should not change anything as they are > loaded > differently) > > Can you give me some more informations on problems you had when > compiling, > by example, which version of pluma did you used (mine, or the > official > one)? > This could be the root of your problem. > > Sounds like I should enhance the error explanation... I only made it > to be > a simple hint for me when programming, I must admit :s > (I'll add an entry for that in trac, create a real debugging stuff > would > be useful) > > Le Ven 9 novembre 2012 16:10, api...@gm... a écrit : >> I have already edited the ~/.config/autorealm/config to my >> configuration >> but when the program starts it looks for /root.autorealm/ >> >> I had some library problems during compilation but I was able to fix >> them >> and get Autorealm to compile cleanly Sent from my BlackBerry® >> wireless >> device >> >> -----Original Message----- >> From: "Morel Bérenger" <ber...@ne...> >> Date: Fri, 9 Nov 2012 15:55:50 >> To: Developers of AutoREALM<aut...@li...> >> Reply-To: Developers of AutoREALM >> <aut...@li...> >> Subject: Re: [Autorealm-develop] Autorealm initialization >> >> >> Sure. You need to modify the file ~/.config/autorealm/config (on >> linux) >> to adapt it to your own configuration. >> >> Did you had any problems with the compilation? I am interested by >> any >> returns you could have to help improve this situation. >> >> Le Ven 9 novembre 2012 15:26, api...@gm... a écrit : >> >>> Sup >>> I have problems starting Autorealm it display the splash then say >>> fatal >>> error cannot initialize default border or filler could someone help >>> me >>> with fixing this error Sent from my BlackBerry® wireless device >>> >>> ----------------------------------------------------------------------- >>> --- >>> ---- >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_d2d_nov >>> _______________________________________________ >>> Autorealm-develop mailing list >>> Aut...@li... >>> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >>> >>> >>> >> >> >> >> >> ------------------------------------------------------------------------- >> ----- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >> >> -------------------------------------------------------------------------- >> ---- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >> >> > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop |
From: <api...@gm...> - 2012-11-10 09:10:59
|
The problem was with the cmake scripts It did not compile the plugins I partially fixed that. Just to make sure its working properly what is the current functionality of Autorealm Sent from my BlackBerry® wireless device -----Original Message----- From: "Morel Bérenger" <ber...@ne...> Date: Fri, 9 Nov 2012 16:28:45 To: Developers of AutoREALM<aut...@li...> Reply-To: Developers of AutoREALM <aut...@li...> Subject: Re: [Autorealm-develop] Autorealm initialization Strange. It seems AutoREALM is able to find and open the config file, but not to find the good plug-ins... What is your operating system? I guess it is a linux distro, but I would like to be sure... Did you compiled autorealm with the unfinished cmake scripts in the repo, or with C::B? If with the cmake scripts, IIRC, names could be different, so check that... (but for color, it should not change anything as they are loaded differently) Can you give me some more informations on problems you had when compiling, by example, which version of pluma did you used (mine, or the official one)? This could be the root of your problem. Sounds like I should enhance the error explanation... I only made it to be a simple hint for me when programming, I must admit :s (I'll add an entry for that in trac, create a real debugging stuff would be useful) Le Ven 9 novembre 2012 16:10, api...@gm... a écrit : > I have already edited the ~/.config/autorealm/config to my configuration > but when the program starts it looks for /root.autorealm/ > > I had some library problems during compilation but I was able to fix them > and get Autorealm to compile cleanly Sent from my BlackBerry® wireless > device > > -----Original Message----- > From: "Morel Bérenger" <ber...@ne...> > Date: Fri, 9 Nov 2012 15:55:50 > To: Developers of AutoREALM<aut...@li...> > Reply-To: Developers of AutoREALM > <aut...@li...> > Subject: Re: [Autorealm-develop] Autorealm initialization > > > Sure. You need to modify the file ~/.config/autorealm/config (on linux) > to adapt it to your own configuration. > > Did you had any problems with the compilation? I am interested by any > returns you could have to help improve this situation. > > Le Ven 9 novembre 2012 15:26, api...@gm... a écrit : > >> Sup >> I have problems starting Autorealm it display the splash then say fatal >> error cannot initialize default border or filler could someone help me >> with fixing this error Sent from my BlackBerry® wireless device >> ----------------------------------------------------------------------- >> --- >> ---- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >> >> >> > > > > ------------------------------------------------------------------------- > ----- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > -------------------------------------------------------------------------- > ---- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Autorealm-develop mailing list Aut...@li... https://lists.sourceforge.net/lists/listinfo/autorealm-develop |
From: Morel B. <ber...@ne...> - 2012-11-09 15:55:56
|
Here are some hints about what could give you such error: https://sourceforge.net/apps/trac/autorealm/ticket/16 Le Ven 9 novembre 2012 16:10, api...@gm... a écrit : > I have already edited the ~/.config/autorealm/config to my configuration > but when the program starts it looks for /root.autorealm/ > > I had some library problems during compilation but I was able to fix them > and get Autorealm to compile cleanly Sent from my BlackBerry® wireless > device > > -----Original Message----- > From: "Morel Bérenger" <ber...@ne...> > Date: Fri, 9 Nov 2012 15:55:50 > To: Developers of AutoREALM<aut...@li...> > Reply-To: Developers of AutoREALM > <aut...@li...> > Subject: Re: [Autorealm-develop] Autorealm initialization > > > Sure. You need to modify the file ~/.config/autorealm/config (on linux) > to adapt it to your own configuration. > > Did you had any problems with the compilation? I am interested by any > returns you could have to help improve this situation. > > Le Ven 9 novembre 2012 15:26, api...@gm... a écrit : > >> Sup >> I have problems starting Autorealm it display the splash then say fatal >> error cannot initialize default border or filler could someone help me >> with fixing this error Sent from my BlackBerry® wireless device >> ----------------------------------------------------------------------- >> --- >> ---- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >> >> >> > > > > ------------------------------------------------------------------------- > ----- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > -------------------------------------------------------------------------- > ---- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > |
From: Morel B. <ber...@ne...> - 2012-11-09 15:29:00
|
Strange. It seems AutoREALM is able to find and open the config file, but not to find the good plug-ins... What is your operating system? I guess it is a linux distro, but I would like to be sure... Did you compiled autorealm with the unfinished cmake scripts in the repo, or with C::B? If with the cmake scripts, IIRC, names could be different, so check that... (but for color, it should not change anything as they are loaded differently) Can you give me some more informations on problems you had when compiling, by example, which version of pluma did you used (mine, or the official one)? This could be the root of your problem. Sounds like I should enhance the error explanation... I only made it to be a simple hint for me when programming, I must admit :s (I'll add an entry for that in trac, create a real debugging stuff would be useful) Le Ven 9 novembre 2012 16:10, api...@gm... a écrit : > I have already edited the ~/.config/autorealm/config to my configuration > but when the program starts it looks for /root.autorealm/ > > I had some library problems during compilation but I was able to fix them > and get Autorealm to compile cleanly Sent from my BlackBerry® wireless > device > > -----Original Message----- > From: "Morel Bérenger" <ber...@ne...> > Date: Fri, 9 Nov 2012 15:55:50 > To: Developers of AutoREALM<aut...@li...> > Reply-To: Developers of AutoREALM > <aut...@li...> > Subject: Re: [Autorealm-develop] Autorealm initialization > > > Sure. You need to modify the file ~/.config/autorealm/config (on linux) > to adapt it to your own configuration. > > Did you had any problems with the compilation? I am interested by any > returns you could have to help improve this situation. > > Le Ven 9 novembre 2012 15:26, api...@gm... a écrit : > >> Sup >> I have problems starting Autorealm it display the splash then say fatal >> error cannot initialize default border or filler could someone help me >> with fixing this error Sent from my BlackBerry® wireless device >> ----------------------------------------------------------------------- >> --- >> ---- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >> >> >> > > > > ------------------------------------------------------------------------- > ----- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > -------------------------------------------------------------------------- > ---- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > |
From: <api...@gm...> - 2012-11-09 15:10:34
|
I have already edited the ~/.config/autorealm/config to my configuration but when the program starts it looks for /root.autorealm/ I had some library problems during compilation but I was able to fix them and get Autorealm to compile cleanly Sent from my BlackBerry® wireless device -----Original Message----- From: "Morel Bérenger" <ber...@ne...> Date: Fri, 9 Nov 2012 15:55:50 To: Developers of AutoREALM<aut...@li...> Reply-To: Developers of AutoREALM <aut...@li...> Subject: Re: [Autorealm-develop] Autorealm initialization Sure. You need to modify the file ~/.config/autorealm/config (on linux) to adapt it to your own configuration. Did you had any problems with the compilation? I am interested by any returns you could have to help improve this situation. Le Ven 9 novembre 2012 15:26, api...@gm... a écrit : > Sup > I have problems starting Autorealm it display the splash then say fatal > error cannot initialize default border or filler could someone help me > with fixing this error Sent from my BlackBerry® wireless device > -------------------------------------------------------------------------- > ---- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Autorealm-develop mailing list Aut...@li... https://lists.sourceforge.net/lists/listinfo/autorealm-develop |
From: Morel B. <ber...@ne...> - 2012-11-09 14:56:03
|
Sure. You need to modify the file ~/.config/autorealm/config (on linux) to adapt it to your own configuration. Did you had any problems with the compilation? I am interested by any returns you could have to help improve this situation. Le Ven 9 novembre 2012 15:26, api...@gm... a écrit : > Sup > I have problems starting Autorealm it display the splash then say fatal > error cannot initialize default border or filler could someone help me > with fixing this error Sent from my BlackBerry® wireless device > -------------------------------------------------------------------------- > ---- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > |
From: <api...@gm...> - 2012-11-09 14:27:01
|
Sup I have problems starting Autorealm it display the splash then say fatal error cannot initialize default border or filler could someone help me with fixing this error Sent from my BlackBerry® wireless device |
From: Morel B. <ber...@ne...> - 2012-11-08 15:56:41
|
I wrote a small software to generate a graph to allow me to see files relations of the current source code, and why not make it able to move a file and update all other files which depends on it. Would have been a nice idea. So, when I tried this little software on autorealm, I have been quite surprised... Here is a link to it: http://img713.imageshack.us/img713/6823/autorealm.gif Quite messy, is not it? But do not worry, most of the mess comes from including external libraries, and there are still small things I must fix on my tool. Maybe I should add a random color feature to allow using autorealm's files relations as a psychedelic wallpaper :D Anyway, it prove that my tool could really help me in the future with some improvements. The reason of the writing of this tool is to allow me to clean the current source-code file mess in autorealm, and write a clean cmake build system. Hopefully this task will be finished in few days, because it is really boring. And I will probably do other source cleaning work after this task. However, many peoples offered help. In this bunch of good souls, I think maybe one or two will really, but "only" one or two is "only" multiplying the task force by 2 or 3 :) Maybe other are just disgusted by the problem of having no way to compile without C::B, and worse, the lack of informations about how to compile on windows, so hopefully the work on cmakewill have nice side effects on contribution. Another solution would be to try to build on windows myself, but I do not really have the time to compile wxwidgets 2.9 on that OS (when I log in my windows, I am often attracted by the games I can not play on linux and they are really big time consumers 8) ) nor I am happy to start it. |
From: Morel B. <ber...@ne...> - 2012-11-05 11:34:23
|
Yes, the wiki contain links to the bitbucket repo. Le Lun 5 novembre 2012 12:24, lando a écrit : > No worries, bitbucket seem fine, just wanted to confirm. Is there a > link to the source on the wiki? I can't remember atm > > > On Mon, Nov 5, 2012 at 4:36 AM, "Morel Bérenger" > <ber...@ne...> wrote: > >> For now, I do not plan to move files to sourceforge, because it is not >> as easy to create an on-line fork. >> >> So, I just push modifications on SF when a release is ready. Maybe >> that'll change in the future, but that will need good reasons and >> discussions. >> >> Le Lun 5 novembre 2012 10:23, lando a écrit : >> >>> Are you planning to transfer the files to sourceforge or is bit >>> bucket our primary codebase? >>> >>> On Sat, Nov 3, 2012 at 11:30 AM, <ber...@ne...> >>> wrote: >>> >>> >>>> Hello. >>>> >>>> >>>> >>>> Since I had many requests to contribute, I have written a wiki page >>>> about how to contribute. Please say me what do you think about it >>>> please. >>>> >>>> >>>> Here it is: >>>> https://sourceforge.net/apps/trac/autorealm/wiki/contributing >>>> >>>> >>>> >>>> ------------------------------------------------------------------- >>>> ---- >>>> ------- >>>> LogMeIn Central: Instant, anywhere, Remote PC access and management. >>>> Stay in control, update software, and manage PCs from one command >>>> center Diagnose problems and improve visibility into emerging IT >>>> issues Automate, monitor and manage. Do more in less time with >>>> Central >>>> http://p.sf.net/sfu/logmein12331_d2d >>>> _______________________________________________ >>>> Autorealm-develop mailing list >>>> Aut...@li... >>>> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> ---- >>> ----- >>> LogMeIn Central: Instant, anywhere, Remote PC access and management. >>> Stay in control, update software, and manage PCs from one command >>> center Diagnose problems and improve visibility into emerging IT >>> issues Automate, monitor and manage. Do more in less time with Central >>> http://p.sf.net/sfu/logmein12331_d2d >>> _______________________________________________ >>> Autorealm-develop mailing list >>> Aut...@li... >>> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >>> >>> >>> >> >> >> >> ----------------------------------------------------------------------- >> ------- >> LogMeIn Central: Instant, anywhere, Remote PC access and management. >> Stay in control, update software, and manage PCs from one command center >> Diagnose problems and improve visibility into emerging IT issues >> Automate, monitor and manage. Do more in less time with Central >> http://p.sf.net/sfu/logmein12331_d2d >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >> > > ------------------------------------------------------------------------- > ----- > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > |
From: lando <la...@gm...> - 2012-11-05 11:24:49
|
No worries, bitbucket seem fine, just wanted to confirm. Is there a link to the source on the wiki? I can't remember atm On Mon, Nov 5, 2012 at 4:36 AM, "Morel Bérenger" <ber...@ne...> wrote: > For now, I do not plan to move files to sourceforge, because it is not as > easy to create an on-line fork. > > So, I just push modifications on SF when a release is ready. Maybe that'll > change in the future, but that will need good reasons and discussions. > > Le Lun 5 novembre 2012 10:23, lando a écrit : >> Are you planning to transfer the files to sourceforge or is bit bucket >> our primary codebase? >> >> On Sat, Nov 3, 2012 at 11:30 AM, <ber...@ne...> wrote: >> >>> Hello. >>> >>> >>> Since I had many requests to contribute, I have written a wiki page >>> about how to contribute. Please say me what do you think about it please. >>> >>> >>> Here it is: >>> https://sourceforge.net/apps/trac/autorealm/wiki/contributing >>> >>> >>> ----------------------------------------------------------------------- >>> ------- >>> LogMeIn Central: Instant, anywhere, Remote PC access and management. >>> Stay in control, update software, and manage PCs from one command center >>> Diagnose problems and improve visibility into emerging IT issues >>> Automate, monitor and manage. Do more in less time with Central >>> http://p.sf.net/sfu/logmein12331_d2d >>> _______________________________________________ >>> Autorealm-develop mailing list >>> Aut...@li... >>> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >>> >> >> ------------------------------------------------------------------------- >> ----- >> LogMeIn Central: Instant, anywhere, Remote PC access and management. >> Stay in control, update software, and manage PCs from one command center >> Diagnose problems and improve visibility into emerging IT issues >> Automate, monitor and manage. Do more in less time with Central >> http://p.sf.net/sfu/logmein12331_d2d >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >> >> > > > > ------------------------------------------------------------------------------ > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop |
From: Morel B. <ber...@ne...> - 2012-11-05 09:36:15
|
For now, I do not plan to move files to sourceforge, because it is not as easy to create an on-line fork. So, I just push modifications on SF when a release is ready. Maybe that'll change in the future, but that will need good reasons and discussions. Le Lun 5 novembre 2012 10:23, lando a écrit : > Are you planning to transfer the files to sourceforge or is bit bucket > our primary codebase? > > On Sat, Nov 3, 2012 at 11:30 AM, <ber...@ne...> wrote: > >> Hello. >> >> >> Since I had many requests to contribute, I have written a wiki page >> about how to contribute. Please say me what do you think about it please. >> >> >> Here it is: >> https://sourceforge.net/apps/trac/autorealm/wiki/contributing >> >> >> ----------------------------------------------------------------------- >> ------- >> LogMeIn Central: Instant, anywhere, Remote PC access and management. >> Stay in control, update software, and manage PCs from one command center >> Diagnose problems and improve visibility into emerging IT issues >> Automate, monitor and manage. Do more in less time with Central >> http://p.sf.net/sfu/logmein12331_d2d >> _______________________________________________ >> Autorealm-develop mailing list >> Aut...@li... >> https://lists.sourceforge.net/lists/listinfo/autorealm-develop >> > > ------------------------------------------------------------------------- > ----- > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > _______________________________________________ > Autorealm-develop mailing list > Aut...@li... > https://lists.sourceforge.net/lists/listinfo/autorealm-develop > > |