« Another optional core feature
Scheduled tasks interface
Aeva - Forum owned albums »

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Scheduled tasks interface
« on October 29th, 2010, 01:02 PM »
Two things should be done with scheduled tasks.

Firstly, there should be an extra field which holds the name of a file to load that contains the scheduled task function, so it doesn't have to be added to a file that will be known to be loaded when AutoTask() runs (i.e. ScheduledTask.php IIRC)

Secondly, there should be some kind of interface for the admin to actually add a new task that follows the above. Not quite sure how that squares out with respect to language strings, mind, but perhaps we could have each scheduled task broken into its own subfolder with its own language strings or something. Don't know yet about that (or maybe, just add the scheduled task's name/description into the DB)
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

spuds

  • Posts: 94
Re: Scheduled tasks interface
« Reply #1, on October 29th, 2010, 03:34 PM »
Quote
Secondly, there should be some kind of interface for the admin to actually add a new task that follows the above. Not quite sure how that squares out with respect to language strings, mind, but perhaps we could have each scheduled task broken into its own subfolder with its own language strings or something. Don't know yet about that (or maybe, just add the scheduled task's name/description into the DB)
That would be a nice feature, its pretty cumbersome to add tasks today, maybe doing something via SSI as a thought so its mod accessible.  Also along those lines, adding/removing package servers from the admin interface would also nice feature.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Scheduled tasks interface
« Reply #2, on October 29th, 2010, 07:16 PM »
You already can add package servers via the admin UI...

The problem is that almost nobody knows how to add tasks, even when I documented it >_<

spuds

  • Posts: 94

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Scheduled tasks interface
« Reply #4, on October 30th, 2010, 08:33 PM »
Seriously? Admin > Packages > Download Packages... it's right there. How could it be more intuitive, exactly?

You have to go there to pick the server you want to browse...

spuds

  • Posts: 94
Re: Scheduled tasks interface
« Reply #5, on October 31st, 2010, 01:36 AM »
Yeah ... probably not the best example of the various find waldo problems with that interface, I'm sure its programatically sequenced but often non intuitive, non natural (wrt other programs) for end users .... Anyway to me it should be

Admin > Packages > Options

Set the options of how I want packages, browsed, saved, installed, whatever ... done via options.  In that same package area there is the browse packages and installed packages tabs ... installed seems to just be a subset of whats in browse so I'm not sure why its there, I'm sure there is a reason but its not obvious to me.

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Posts: 1,670
Re: Scheduled tasks interface
« Reply #6, on October 31st, 2010, 06:50 AM »
Quote from spuds on October 31st, 2010, 01:36 AM
installed seems to just be a subset of whats in browse so I'm not sure why its there, I'm sure there is a reason but its not obvious to me.
*nods*

That section is kinda misleading... there is a mod by someone which groups the package listing
A confident man keeps quiet.whereas a frightened man keeps talking, hiding his fear.

YogiBear

  • Great Britain's Eurovision result...arghhhh !!
  • Posts: 140
Re: Scheduled tasks interface
« Reply #7, on October 31st, 2010, 12:51 PM »
Quote from spuds on October 31st, 2010, 01:36 AM
...
 In that same package area ... and installed packages tabs ... installed seems to just be a subset of whats in browse so I'm not sure why its there, I'm sure there is a reason but its not obvious to me.
It occurs to me by relying on that screen a mod can be accidentally deleteted before firstly uninstalling it. It does seem confusing.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Scheduled tasks interface
« Reply #8, on October 31st, 2010, 01:08 PM »
Well, I have no idea what the hell the installed packages area is for. I'm of the view it probably should be ripped out.

Dismal Shadow

  • Madman in a Box
  • Me: Who is Arantor? Cleverbot: It stands for time and relative dimensions in space.
  • Posts: 1,185
“I will stand on my ground as an atheist until your god shows up...If my irreligious bothers you much, and if you think everything I do is heresy to your god I don't care. Heresy is for those who believe, I don't. So, it isn't heresy at all!


   Jack in, Wedge,
   EXECUTE!

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Scheduled tasks interface
« Reply #10, on October 31st, 2010, 10:19 PM »
And you can't do that from the browse page like the rest of us? :P

Dismal Shadow

  • Madman in a Box
  • Me: Who is Arantor? Cleverbot: It stands for time and relative dimensions in space.
  • Posts: 1,185
Re: Scheduled tasks interface
« Reply #11, on October 31st, 2010, 10:24 PM »
Quote from Arantor on October 31st, 2010, 10:19 PM
And you can't do that from the browse page like the rest of us? :P
I can...even better with Sortable Packages. :D

You asked what it was for...which it serves no purpose, so rip it out. :)

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Scheduled tasks interface
« Reply #12, on November 11th, 2010, 09:48 PM »
Quote from spuds on October 31st, 2010, 01:36 AM
Yeah ... probably not the best example of the various find waldo problems with that interface, I'm sure its programatically sequenced but often non intuitive, non natural (wrt other programs) for end users ....
I think if one wants to be intuitive for end users, one would have to start renaming the "package" stuff...
We have "modifications" and "packages". Basically, one is contained within the other or something, but really, some people say "plugin", others say "extensions", others say "add-ons", but SMF chose to say "packages" which is probably not as intuitive as the rest... They should stick to 'mods' entirely or choose something else!

+1 to rip out the installed packages list. I never understood it, myself.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Scheduled tasks interface
« Reply #13, on November 11th, 2010, 11:35 PM »
There is a logic to it, albeit a twisted one.

* A mod is a set of instructions of how to modify the code in a certain way.
* A plugin is a drop-in extra that requires merely configuration and is often not directly involved in current operation.
* An extension is a mostly drop-in extra that takes current operation and extends its scope.
* A package (in SMF terms at least) is a bundle containing the information for one or more of the above.

I'd encourage us to run with 'plugin' as a term since that's closer to how I see it working but here's a thought. Something I suggested tongue-in-cheek during the latter days I was with SimpleDesk, after I'd started the plugin system there, was to rename it 'drawers' (as they fit into a desk).

Other systems name them differently, I seem to recall being told that PHP Fusion names them InFusions, so why not go nuts and think of a different name entirely.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Scheduled tasks interface
« Reply #14, on November 12th, 2010, 08:32 AM »
Seriously, who would use "drawers" to discuss mods ;)
No, I think we should just use "mods" everywhere, including where "packages" is being used. Nobody cares about the container.

This is really where the issue is: there's already a name for these. Mods. "Packages" is barely used, and confusing. If you choose "Drawers", or "Cogs", or anything silly or not, newbies are still not going to understand it, just like "packages" is hard to understand... While "Modifications" is a bit easier, and "plugins/extensions/add-ons" DEFINITELY is easy to understand. That's what matters. Remember one of our mottos: if it needs explaining, then it's not good ;) (Interestingly, the iPod Touch comes without a proper manual... I was quite surprised with that. But it's really efficient, most of the time.)
Posted: November 12th, 2010, 08:22 AM

Maybe we could do this:
- We change the whole terminology to "Extensions" or "Addons".
- We then use two sub-genres.
- Some extensions will be called "modifications" or "mods". They're the addons that use a xml file to modify the Wedge code. No warranty is given as to what happens when you upgrade, and in case of conflicts. "It may work, but good luck".
- Other extensions, those without the xml modifications, will be called "plugins", will be showed as such in the admin, and will be properly supported by Wedge. We will encourage modders to release plugins.
« Another optional core feature
Aeva - Forum owned albums »