Author Topic: MiniDoc  (Read 33231 times)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9504
Re: MiniDoc
« Reply #45 on: September 01, 2014, 08:05:25 am »
Or just commit it, if there are no obvious issues and we fix it in trunk.
I'm most likely not available much this week, so I decided to commit. It works fine on Windows. I am not sure if I did all the required stuff for the Linux build system, but at least "I did my very best"... ;-) The last update of Ubuntu in my VM broke it once again, so I cannot test it myself.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9504
Re: MiniDoc
« Reply #46 on: February 17, 2015, 09:01:04 pm »
Well with respect to the MiniDoc plugin:

Are there any news? In principle it works nicely, hence it takes away a lot CPU power thus scrolling of any editors becomes really clumsy. It goes away, if you disable the plugin, but NOT (?!) if you hide the minidoc Window.

I would love to see that working...
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9504
Re: MiniDoc
« Reply #47 on: February 21, 2015, 03:07:55 pm »
Ping... :-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12066
    • Travis build status
Re: MiniDoc
« Reply #48 on: February 21, 2015, 07:18:38 pm »
I would love to see that working...
I hope, I'll find some time to work on a real scrollbar replacement later this year.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9504
Re: MiniDoc
« Reply #49 on: February 21, 2015, 09:05:31 pm »
I hope, I'll find some time to work on a real scrollbar replacement later this year.
BTW: I just discovered Jens' fork.
@Jens: What are the changes? Is that working more reliable?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12066
    • Travis build status
Re: MiniDoc
« Reply #50 on: February 21, 2015, 09:17:43 pm »
If you're talking about this: https://github.com/danselmi/MiniDoc/network then Jens' fork is way older and doesn't contain lots of commits. But probably it could be easily rebased.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9504
Re: MiniDoc
« Reply #51 on: February 21, 2015, 09:49:16 pm »
If you're talking about this: https://github.com/danselmi/MiniDoc/network then Jens' fork is way older and doesn't contain lots of commits. But probably it could be easily rebased.
Ah - I didn't check the history. I was under the assumption that a fork must always be newer...  :P ::)

OK, but still: any comments on the performance? Am I the only one experiencing such?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: MiniDoc
« Reply #52 on: February 21, 2015, 10:01:02 pm »
My intention when forking the repo was to make a pull request, which can be integrated automatically into the original repo without the need to handle patches manually.
It's not a "normal" fork.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12066
    • Travis build status
Re: MiniDoc
« Reply #53 on: February 21, 2015, 11:22:50 pm »
I've not used it since the first try, because it had problems when using two editors side by side.
Also I think it should not land in trunk before next release.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline danselmi

  • Developer
  • Almost regular
  • *****
  • Posts: 202
Re: MiniDoc
« Reply #54 on: February 24, 2015, 11:43:42 pm »
...
OK, but still: any comments on the performance? Am I the only one experiencing such?
It is/was really bad. But I just commited some improvements. It still needs some resources but.. test it yourself.

I've not used it since the first try, because it had problems when using two editors side by side.
What problems?

Also I think it should not land in trunk before next release.
Reasons? I am not in hurry. But I can't take anything out of statements like this!

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12066
    • Travis build status
Re: MiniDoc
« Reply #55 on: February 25, 2015, 12:07:18 am »
What problems?
Unfortunately I don't remember the details. :(
I should see if I can give it a try at work, because there I'm using two editors side by side all the time.

Reasons? I am not in hurry. But I can't take anything out of statements like this!
I want to be careful. I'd rather prefer if there are several nightlies featuring it, so it can be tested a bit more.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2544
Re: MiniDoc
« Reply #56 on: September 08, 2018, 06:35:40 pm »
Hi!
I tested this plugin today and it performed really bad.. Is this only for me or also for other users? I remember that in the past this was not the case.... I suspect the wxScintilla update here?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12066
    • Travis build status
Re: MiniDoc
« Reply #57 on: September 08, 2018, 07:01:11 pm »
No idea, I'm not using this plugin.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Krice

  • Almost regular
  • **
  • Posts: 130
Re: MiniDoc
« Reply #58 on: September 24, 2019, 09:23:07 am »
Downloaded from github to check out the source code. It's quite bad if I'm being honest. The code doesn't have any helpful comments like you would expect from a decent source code and there are commented out parts of code without any explanation (=comment). In any case, the C::B project file doesn't even work, because it requires some kind of special compiler or something it's complaining when you open the project. If you want other people to contribute, you really need to write better comments and clean up the source code before you stuff it to github or release it. You don't have to be a professional programmer to figure this out, just think about it for a while. Just give your brains some time to think.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6663
    • My Best Post
Re: MiniDoc
« Reply #59 on: September 24, 2019, 08:11:11 pm »
Downloaded from github to check out the source code. It's quite bad if I'm being honest. The code doesn't have any helpful comments like you would expect from a decent source code and there are commented out parts of code without any explanation (=comment). In any case, the C::B project file doesn't even work, because it requires some kind of special compiler or something it's complaining when you open the project. If you want other people to contribute, you really need to write better comments and clean up the source code before you stuff it to github or release it. You don't have to be a professional programmer to figure this out, just think about it for a while. Just give your brains some time to think.

Your comment is useless; have you built Code::Blocks from source, before?

Edit: Your comment can almost be summed up by "the project is not newbie friendly".
It fails to mention
The OS used to build
The WX version used to build
The CB version used to build
And, it does not contain any error messages!
Edit2: It also fails to mention compiler version.

Tim S.
« Last Edit: September 24, 2019, 09:03:57 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org