Unified Library for StackIdeas Components?
By David Montoya on Thursday, 20 April 2017
Posted in General
Replies 1
Likes 0
Views 99
Votes 0
Why do your components have redundant assets? I've been customizing between EasySocial and EasyDiscuss, and I find things that get reused. Has a unified StackIdeas library ever been considered? It would reduce the number of files the end-user would have to edit and would further reduce the size of footprint; inodes are precious on shared servers!

Although, I do get that this kind of refactoring would be a massive undertaking, I'm curious as to whether or not it's ever been considered. As it is I'm having a paint getting Prism.JS to function the same in both ED and ES because they're both driven by separate files.
Hello David,

We tried to unify all our assets files which was why we created foundry but it is just too difficult to ensure that there are no conflicts between these extensions.

Just giving one simple scenario:

1. Assuming that if we shared the same Prism library on EasyDiscuss and EasySocial and we probably call it Foundry 1.0 (central library)

2. On EasySocial we might be using an older version of Prism

3. On EasyDiscuss we might be using a later version of Prism as it performs some other functions better than the old version.

4. Updating to Foundry 1.0 (with prism) may break EasySocial since it relies on the old syntax of Prism.

5. Ends up, you have Prism on Foundry 1.0 alongside Prism on Foundry 1.1 (for EasyDiscuss)

This is the issues we had with quite a number of libraries and not Prism. Just giving it as an example.
Mark
·
Thursday, 20 April 2017 11:28
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post