T
@Bri Yes there are solutions like Microsoft's vcpkg or even cppan.
But my tool would be more like a deployment complement: you would generate your binaries for the end user to download them but also an amalgamated version in case they want to use the quick n easy way.
One thing I'd like to setup if this happens to be successful would be a cloud service which would allow to easily amalgamate your project.
@Bri Hey thanks for the comment!
The use case is quite simple: downloading and installing a small library as a static/dynamic dependency is a (relatively) large amount of work compared to just throwing a packaged version within your own source.
It's kinda the same principle as of js files: you don't add <script>s tags for each file, you amalgamate and minify them to let the user directly use one single file. This is definitely easier for your end user, no need for him to add hundreds of <script>s tags!
About minification that's something I keep somewhere in my mind for a possible later feature, thanks!
Just updated to 0.8.0:
Once again, I'm open to any feedback/suggestion/comment you could make!
Have a nice day!
Hey everyone!
I'd like to share a project I'm currently working on!
Amie is a module I just started (two days ago) and that I'd like to see evolve in a sane and good way!
First of all, here is the link to the repo: https://github.com/Telokis/Amie
If you are not familiar with this word, no problem.
Amalgamation is when you take multiple things and put them together.
For example, in a random C++ project, you could have a file main.cpp that includes a file fun.hpp.
Amalgamation would combine those two files to create a single file in output: it would insert the whole content of fun.hpp at the line where you include it inside main.cpp.
The answer is simple: ease of integration.
If I am a developer using the above project, I don't have to care about the number of files anymore!
I just have to take the amalgamated file, throw it among my own sources and it will be treated as if I made it.
Magic: everybody's happy!
Sharing a single all-in-one file is way easier than a whole project!
If I were to take another example, think of JavaScript libraries.
When used in a browser, you don't have to include every file the library uses. You don't have to do so because it is amalgamated. (Even though we call if minification, it's a two way process: amalgamation then minification)
With that last example, I'll leave you there with this post.
Feel free to give me feedback/suggestions. I'd be really glad to hear what you think about this! (Even if you don't plan on ever using it!)
Telokis
@PitaJ @insuusvenerati Alright you guys totally convinced me, I downloaded VSCode and I'll give it a try!
@PitaJ @insuusvenerati Does vscode have a way to directly launch the program, tests or things like that from the UI? And how does it work related to git?
I finally decided to migrate back to Github. I'll update the main post but here is the new link https://github.com/Telokis/nodebb-plugin-save-plugins
And the npm package : https://www.npmjs.com/package/nodebb-plugin-save-plugins
Hey everyone!
First of all, I'd like to thanks you guys because I really think NodeBB is an awesome app and it's a pleasure using it.
(I particularly love the plugin system which is really powerful!)
As a developer myself, I've used NodeJS for several personal projects and to play with some interesting libraries (Socket.io, React, require, and so on).
But one think I am missing is some kind of guidelines reference.
Something that would make me start every project with the same modules/directories setup.
For example, I'm really fond of the way NodeBB handles translation, plugins, templating and everything. I'd really like to adapt those to make something completely different (like a personal website or another sandbox).
So, to summarize, I'd like to know where you get your inspiration from: do you have some talks/books/blogs/whatever that I could read and follow myself? Or is this just the result of lots of experimentations/ideas gathering?
Sorry if I'm not 100% clear with what I meant but it's kind of a meta question.
Thanks in advance.
And, if you want to bump minor or major version, simply do it in your package.json and the hooks will properly read and process it. Even updating the readme. And a new tag will be created.
I didn't know about npm version but this is one step too much for me. I want to update the patch version at each comimt.
This may not be optimal for js because it was originally meant to be a C++ thing. I just ported it to js.
Hey everyone !
I don't like having to manually update the package.json file's patch version (the 'x' in '1.0.x').
Because of that, I decided to take advantage of git hooks and wrote some scripts to make my life easier.
You can find the scripts here but I'll make a dedicated repo if this seem useful to people.
Here is how it works:
scripts folder is at the root of the repository (to generate the hooks)Then, after cloning a repo, I do this:
cd scripts./setup_hooks.shThis will generate a post and a pre commit hook.
The pre-commit hook is used to automatically create a new tag if major or minor version has changed. Inside handle_tags.sh
The post-commit hook is used to automatically update the package.json after each commit. It increases the patch version by one (each commit is considered a patch) by counting the number of commits since the last tag (or the beginning if no tags made)
The post-commit hook (file setup_readme_version.sh) also updates the readme.md of my project to write
_Current repository version : v<major>.<minor>.<patch>_
If you don't want this behavior, you don't have anything to do. If you want it, you have to put
_Current repository version : v_ somewhere in your readme. The regexp will match and update it.
And, if you want to bump minor or major version, simply do it in your package.json and the hooks will properly read and process it. Even updating the readme. And a new tag will be created.
Let me know what you think about this stuff !
Hey everyone !
I'd like to share a small plugin I just made : nodebb-plugin-save-plugins.
And the npm package : https://www.npmjs.com/package/nodebb-plugin-save-plugins
This plugin is meant to provide a way to store installed plugins and auto install them if they are missing.
This allows sharing plugins between multiple nodebb instances if needed.
I'm 100% open to feedback or suggestions !
Telokis