Help Me To Get Lucy Working

bhepler

@mykle1 - That raises an interesting question. Since you have to modify the module’s main JS file, does that imply that every time the module updates you’d have to re-enter your changes?

Mykle1

@bhepler

Hey b. :-)

To answer your question directly, yes. It has always been that way. I don’t know another way of doing it that wouldn’t require re-entering the changes unless module authors wanted Lucy functionality by default. In that case, a simple addition to their module.js is all that is required. I would handle the Lucy side.

When I got the idea for Lucy there was nothing like it here. I knew what I wanted her to do and I accomplished that. Simple coding, looking back, but no small undertaking for me with no prior coding experience at all. Look at my first posts on this site. I couldn’t add a module correctly.

Anyway, I continue to use Lucy very successfully to this day,

bhepler

@mykle1 - Ah. That’s fine. Considering the functionality added, it seems a small price to pay. I just want to be sure I’m aware of the ramifications. If I’m building mirrors for friends, I need to weigh the pros & cons of including Hello Lucy into their builds. If I can maintain access to their mirror, then I can make it work. I just have to remember to redo my modifications to the module code.

But if the owners intend to run the updates… then I should probably hold off on the Hello Lucy module. I barely trust myself with modifying the code, let alone teaching someone else how to do it!

Mykle1

@bhepler said in Help Me To Get Lucy Working:

Ah. That’s fine. Considering the functionality added, it seems a small price to pay. I just want to be sure I’m aware of the ramifications. If I’m building mirrors for friends, I need to weigh the pros & cons of including Hello Lucy into their builds. If I can maintain access to their mirror, then I can make it work. I just have to remember to redo my modifications to the module code.

I have not and would not be so bold to ask all module authors to include these four lines to their module.js files. Doing so would not affect their modules but doing so would make them immediately available to Lucy and survive all updates.

if (notification === 'HIDE_COMMAND') {
            this.hide(1000);
        }  else if (notification === 'SHOW_COMMAND') {
            this.show(1000);

But if the owners intend to run the updates… then I should probably hold off on the Hello Lucy module.

Agreed, but it’s there for people that want to use it. Again, when I made Lucy there was no other module like it in function. I wanted to be able to do exactly what it does. I’m sure there are better modules that do it now, but not then. Not a single one. Ironically, Lucy’s name turned out to be more appropriate than I thought. I only used it because it’s my granddaughter’s name.

I barely trust myself with modifying the code, let alone teaching someone else how to do it!

Well, for me, learning involved modifying code. I’m not encouraging anyone to do anything. However, if they want to use Lucy then this is what they must do. If they want to get their feet wet I think that is admirable. Most copy and paste their config.js entries. This is basically the same thing, if they want to experiment and learn.

racampbellky

When I run git pull in the \modules\Hello Lucy folder it gives me a:

“fatal: refusing to merge unrelated histories”

How can I get Hello Lucy updated?

Mykle1

@racampbellky

Rename your current Hello-Lucy folder. (just in case)
Open a new terminal window
Type cd MagicMirror/modules and Enter
Type git clone https://github.com/mykle1/Hello-Lucy and Enter
Type cd Hello-Lucy/installers and Enter
Type bash dependencies.sh and Enter

This does NOT solve your issues with github but it does get you the most recent Lucy.