Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » UppHub / Plugin directory
UppHub / Plugin directory [message #56374] Mon, 01 March 2021 11:12 Go to next message
Didier is currently offline  Didier
Messages: 693
Registered: November 2008
Location: France
Contributor
Hello,

After reading the UppHub instractions here https://www.ultimatepp.org/app$ide$UppHub_en-us.html, It says all packages have to be root or in Plugin directory

I would like to have a directory in which all addons specific to my package would be grouped (instead of beeing mixed with all others in the plugin directory).
This enhances readability a lot

Is there a real reason for restriction about Plugin directory ?
Re: UppHub / Plugin directory [message #56375 is a reply to message #56374] Mon, 01 March 2021 12:01 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 14160
Registered: November 2005
Ultimate Member
Didier wrote on Mon, 01 March 2021 11:12
Hello,

After reading the UppHub instractions here https://www.ultimatepp.org/app$ide$UppHub_en-us.html, It says all packages have to be root or in Plugin directory

I would like to have a directory in which all addons specific to my package would be grouped (instead of beeing mixed with all others in the plugin directory).
This enhances readability a lot

Is there a real reason for restriction about Plugin directory ?


No. The wording there should be changed. I think the really important bits are:

- do not mix packages in single UppHub nest that are solving different problems (like mixing SysInfo with STEM4U).
- try to make sure the package names that are to be used are unique (obvious reasons) - does not apply the name of examples, tests and other main packages that come with nest.
- if you are adapting 3rd party code (or perhaps format), consider putting it to plugin (like plugin/md).
- put examples into examples directory
- put U++ style tests (those that can be be compiled / run automatically and fail with non-zero exit, e.g. with ASSERT) into autotest directory
- put other tests to test

Mirek

[Updated on: Mon, 01 March 2021 12:02]

Report message to a moderator

Re: UppHub / Plugin directory [message #56382 is a reply to message #56375] Mon, 01 March 2021 20:35 Go to previous message
Didier is currently offline  Didier
Messages: 693
Registered: November 2008
Location: France
Contributor
Thank you Mirek,

it's clear now
Previous Topic: UppHub - automatic dependency installation
Next Topic: How can I use CORE/SSL to sign something or check signatures?
Goto Forum:
  


Current Time: Sat Dec 07 22:12:16 CET 2024

Total time taken to generate the page: 0.02206 seconds