Windower v4 Development - Which plugins are *required*?

[Tawa]

Spellcast, recast, and StatusTimer for me.
As an additional note, its not a plugin, but dare I ask for... Tetramaster support?
(I'm probably the only person that actually plays that anymore >_>)

[Tsuki]

most of what i use has already been mentioned as the norm, so i wont bother.

what it must have for me to switch over:

The ability to jump back and forth between POL/FFXI without crashing, while using a controller.

edit: With multiple instances running.

[Shalafi]

just like to add that yarnball sucks compared to the original pre-plugin and gets a bare minimum update only when required.

[ZhiGaruda]

just like to add that yarnball sucks compared to the original pre-plugin and gets a bare minimum update only when required.

Accusations of this nature should be punishable by death in all countries.

GO AWAY

[Feon]

IME
DrawDistance
Blinkmenot
TParty
Recast
Distance
Lightluggage
Timestamp

[Miroku_Asura]

Distance
Silence
TParty
Timestamp
Recast
BlinkMeNot
ExpWatch
DrawDistance
SSOrganizer

[didgist]

IME
Recast
Distance

[Esvedium]

Accusations of this nature should be punishable by death in all countries.

GO AWAY

Except that he's right...

[SephYuyX]

Ragns bans people who poke at yarnball :E
I would know ;-;

[ZhiGaruda]

Except that he's right...

You can go with him.

[nitsuj]

More or less the replies fit in with what I was thinking....

In no particular order, the stuff I'd like to implement for the next major release:

- recast (would contain logic from recast, yarnball, statustimer, tickle and zone timer). This would feed into the new "bar" functionality Azaril started with lua
- Timestamp (seems to be a pretty big deal. Maybe make this built into the core and toggle on/off by an option?)
- Expwatch (also part of the bar functionality)
- screenshot organizer (built into the core)
- TParty - finish Azaril's existing code
- infobar - ported from v3 but fed into the new bar plugin up top.

Obviously no spellcast, and I'd likely get some more small things into the release if all goes well. How does that set with you?

I'd also like to know how you guys feel about having things like Timestamp and screenshot organizer built into the core as opposed to plugins (and turned on/off with settings).

Likely eventually most of the logic from expwatch, recast etc will be in the core code anyways and the actual "plugin" you're used to will be controlled with lua...

Since SE has it's own "windower" anyways, having "Core windower functionality" seems less important. v3 had the plugins VERY abstracted from the core. I see little reason to keep certain logic out in v4, but I'm curious if anyone has a logical reason not to do that.

Thanks <3

[Onorgul]

I wouldn't be upset if Timestamp were part of the core code of the program, but I don't necessarily see the logic of building it in? I suppose it really depends on which is easier. People who want a timestamp in their chatlog will use it, whether it's core or plugin, and those who don't will turn it off, one way or another.

[Ezhno]

What is your view on IME support, nitsuj? Will it be easy or hard to implement it (either in the core or as a plugin)?

Forgive the programming noob, but I also would like to know what the difference between making a function part of the core v. a plugin. For example, does it make the program more bulky in terms of resources to run if more features are added into the core as opposed to optionally loaded as plugins?

[enoch]

IME support is big, given the situation with the lack of 3.x support for IME in Win7. I'd even be willing to give up spellcast for IME (at least... for a while... maybe).

As for core vs. plugins... I'm of the mind that you'd want to stick stuff in core that wouldn't need to be constantly updated as SE makes changes/additions. That said, it'd be great to be able to update plugins from within Windower itself, the way you do with browser extensions.

[Spagnutty]

Did you windower wizards have to write any serious code for the IME? Or did you just flip a bit or something to enable it in non-JPN clients?

Kinda wondering.

[Belgaer]

I don't know about others, but I highly doubt I'd bother using Windower 4 as long as there's no spellcast for it. :/ I just can't be bothered to remake macros and all that if I don't have to.

Out of curiosity though, what about script macros? I've seen no evidence of it being likely so far. If neither of the two would work in w4, I certainly hope there will be continued support for w3 and plugins.

EDIT: Oh, an I'm concerned about building plugin functionality into the core.. When plugins that are in the core create problems (IE: updates), wouldn't that shaft Windower 4 altogether temporarily? That seems very problematic to me.

[Ropeydonkey]

In no particular order, the stuff I'd like to implement for the next major release:

- recast (would contain logic from recast, yarnball, statustimer, tickle and zone timer). This would feed into the new "bar" functionality Azaril started with lua
- Timestamp (seems to be a pretty big deal. Maybe make this built into the core and toggle on/off by an option?)
- Expwatch (also part of the bar functionality)
- screenshot organizer (built into the core)
- TParty - finish Azaril's existing code
- infobar - ported from v3 but fed into the new bar plugin up top.

That sounds like a substantial release: Good job! But: if this is all going in that 'bar' isnt that going to get pretty crowded? I have windows scattered all over my screen at present, trying to fit infobar, recast/yarnball/status timer etc all into that bar... or am I mis-reading?

[Ropeydonkey]

EDIT: Oh, an I'm concerned about building plugin functionality into the core.. When plugins that are in the core create problems (IE: updates), wouldn't that shaft Windower 4 altogether temporarily? That seems very problematic to me.

Im assuming they could be disabled/toggled in the same way we do with plugins at the moment before launch to get around this?

[Ropeydonkey]

On a slightly off-topic note:

If there is a way for windower V4 to force FF to render in an area of the GFX buffer that would fully support Antialiasing, AAF etc and allow GPUs to do thier thing, the potential improvements in graphic quality would be enough to move most people accross to V4 instantly lol (or is there already a workaround for this? As far as I can find out, the way FF is rendered at present doesnt allow these features)

[montgomery]

Out of curiosity though, what about script macros? I've seen no evidence of it being likely so far. If neither of the two would work in w4, I certainly hope there will be continued support for w3 and plugins.

This. If there's no scripts, I probably won't upgrade to v4. I don't use spellcast, and making the regular old 6 line only macros is not an option.