Posts:
8,374
Registered:
31-Jan-2006
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
29 Jun 20, 22:49
in response to: xexyl
|
|
|
The basic way to turn off widget support is to plant this in the skin.properties file: autoWidgetInjection=false
The user, however, can still choose widget support in the settings - Settings > Advanced > Metadata - and then choose some widgets on the Widgets tab. He will then be puzzled about why they're not working. So, I go the extra step and provide a warning to the user. From the init.bsh of one of my skins (they all do pretty much the same thing): if(Widgets.hasWidgets(rootFolder, engine)) coWarning("You have chosen to include one or more jAlbum widgets in this album.<br>This skin does not support widgets, so your choices will be ignored.");
That coWarning method is defined earlier in the file: private void coWarning(String var) {
String w = "<html>" + var + "</html>";
JOptionPane.showMessageDialog(context.getExplorer(), w, "Warning", JOptionPane.WARNING_MESSAGE);
}
|
|
|
Posts:
157
Registered:
1-Sep-2009
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
29 Jun 20, 23:01
in response to: JeffTucker
|
|
|
The basic way to turn off widget support is to plant this in the skin.properties file: autoWidgetInjection=false
The user, however, can still choose widget support in the settings - Settings > Advanced > Metadata - and then choose some widgets on the Widgets tab. He will then be puzzled about why they're not working. So, I go the extra step and provide a warning to the user.
I had actually thought of this. Thanks for the tip. Did these things and got rid of the parsing of the widgets template. Much appreciated.
|
|
|
Posts:
157
Registered:
1-Sep-2009
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
5 Jul 20, 23:53
in response to: xexyl
|
|
|
So today I've been looking at cleaning up a bit and getting ready to publish the updated skin. I have disabled one feature of the reflection filter because it's problematic and I'd rather get this worked out after updating the skin.
However I do wonder about one thing: I have a text file of questions - like a short FAQ (even if never been asked) - but is there a good (or correct?) way to link to it so that it opens for the user? I tried the JLinkLabel but that didn't want to do it and maybe there's a better idea anyway that I'm unaware of. Maybe it's not even the appropriate way with jAlbum, I really don't know.
What do you recommend?
|
|
|
Posts:
3,944
Registered:
4-Aug-2006
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
6 Jul 20, 00:30
in response to: xexyl
|
|
|
Most of us now use the web for skin manuals, after adding your GUI elements to a control panel, add putClientProperty("helpPage", "http://robm.jalbum.net/Journal Skin/Typography/index.html");
You could store the information in the wiki, add it to https://jalbum.net/help/en/Skins
You would need to register for the wiki though, see https://jalbum.net/help/en/Help#Want_to_contribute.3F
If you need help with the wiki let us know.
Edited by: RobM on 05-Jul-2020 23:30
|
|
|
Posts:
157
Registered:
1-Sep-2009
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
6 Jul 20, 17:38
in response to: RobM
|
|
|
Most of us now use the web for skin manuals, after adding your GUI elements to a control panel, add putClientProperty("helpPage", "http://robm.jalbum.net/Journal Skin/Typography/index.html");
So how did you generate that though? Actually this isn't even the manual though: it was just an FAQ of sorts. My skin UI is relatively simple (as in not a lot of options) and probably the tooltips will be more than enough. However depending on the way you generated that help page I might consider it (I actually hate web design but that's really another matter entirely).
This somehow reminds me though: I know that jAlbum has skins that you can share (obviously I know) but what about filters and/or effects? Is there a place to share those? Because what David said - that effects have a proper UI - sounded interesting and good for my filters (maybe - I would have to make some refinements first) but I don't know if there's a way for this to happen?
Thanks. It's funny you would mention the Wiki because I suggested it years ago that jAlbum have a wiki in the first place. Maybe suggested it to Carl but I don't really know now. Glad it worked out.
So to recap:
- How did you generate that page for your skin help/manual?
- What about effects/filters as far as uploading them (much like skins)?
|
|
|
Posts:
3,944
Registered:
4-Aug-2006
|
|
|
Posts:
157
Registered:
1-Sep-2009
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
6 Jul 20, 19:49
in response to: RobM
|
|
|
Ah so you're saying you used your own skin to make the documentation for it? Reminds me of compiler bootstrapping. Nicely done. (I've certainly done similar things but not with web design anyway.) Or you mean something else? I might consider it anyway but I don't know if it's worth it. However I would like a way to have the questions open up. Maybe just having a separate page on the jAlbum website would suffice then (though currently it's just a text file but I could change that - I just have to find where to add it under the skin). It doesn't really need anything fancy and I could just have it for the entire skin even. I'll take a look at the skin page to see if I can find out how to upload documentation to it and will ask you if I can't find it.
So there's no actual set up on the jAlbum website like there is for skins? That's what I was actually getting at. David maybe that's something to consider?
Ta.
|
|
|
Posts:
3,944
Registered:
4-Aug-2006
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
6 Jul 20, 20:14
in response to: xexyl
|
|
|
I’m sure there is a skin that has help files in a text document, just can’t recall the name, or if I have imagined it. You can though open the file in jAlbums built in text editor, TextEditor.openDocument(File);
See http://jalbum.net/api/se/datadosen/jalbum/TextEditor.html#openDocument(java.io.File,int,int,java.lang.String)
Edited by: RobM on 06-Jul-2020 19:14
|
|
|
Posts:
8,374
Registered:
31-Jan-2006
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
6 Jul 20, 20:47
in response to: RobM
|
|
|
MIrage has both text files and PDF's - see the Help tab in the skin settings. It opens them in the user's default viewer, of course - it makes no attempt to open them within jAlbum.
|
|
|
Posts:
3,944
Registered:
4-Aug-2006
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
6 Jul 20, 21:10
in response to: JeffTucker
|
|
|
MIrage has both text files and PDF's - see the Help tab in the skin settings. It opens them in the user's default viewer, of course - it makes no attempt to open them within jAlbum.
I thought it might be that skin, but difficult to tell on an iPad - back on the Mac now
|
|
|
Posts:
3,567
Registered:
18-Oct-2002
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
7 Jul 20, 11:25
in response to: xexyl
|
|
|
So there's no actual set up on the jAlbum website like there is for skins? That's what I was actually getting at. David maybe that's something to consider?
I understand, but we've seen very little activity in this area, that's why I also recommend using that forum section for now.
|
|
|
Posts:
157
Registered:
1-Sep-2009
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
7 Jul 20, 18:04
in response to: davidekholm
|
|
|
So there's no actual set up on the jAlbum website like there is for skins? That's what I was actually getting at. David maybe that's something to consider?
I understand, but we've seen very little activity in this area, that's why I also recommend using that forum section for now.
No worries David. Thanks for the information. I can imagine how indeed little activity would be there; it's not something that as many people would do as skins as the latter is more for albums whereas the former is more specialised (or something like that).
Cheers.
|
|
|
Posts:
157
Registered:
1-Sep-2009
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
7 Jul 20, 22:20
in response to: JeffTucker
|
|
|
MIrage has both text files and PDF's - see the Help tab in the skin settings. It opens them in the user's default viewer, of course - it makes no attempt to open them within jAlbum.
Thanks. I only just saw this. I thought I had seen this too - the pdf and text files - in Mirage. I'll look at the skin. This might be what I'm after. Appreciate the reply.
|
|
|
Posts:
157
Registered:
1-Sep-2009
|
|
|
Re: What has changed the past 9 years that might break a skin rebuild?
Posted:
7 Jul 20, 22:29
in response to: davidekholm
|
|
|
Another question for you David.
I was thinking back on the thing you said about effects versus filters. It occurred to me that for at least one of my filters it would be rather useful to have a filter control panel UI where I could preview the changes (like you can with effects in the Effects tab).
I noticed AbstractFilter and looking at an old version of GrayscaleFilter.java I noticed it extends AbstractFilter and it has a UI instance as well as a private class that extends ControlPanel.
Looking at these very quickly in my tired eyes I guess that this is part of how it's done but there would also I guess have to be a way to install it into the jAlbum UI (I presume that just like a skin has to add itself to the UI so too do filters/effects?).
Is there more information on this? Looking at the extensions forums quickly I did not see many things on effects and given that the current version of GrayscaleFilter doesn't seem to use AbstractFilter I don't know.
Any feedback here would be good. Oh and if it's in the wiki I apologise for not seeing it. I do remember skins being there but don't recall effects. Thanks.
|
|
|
Posts:
3,944
Registered:
4-Aug-2006
|
|
|
|
Legend
|
|
Forum admins
|
|
Helpful Answer
|
|
Correct Answer
|
|