View Single Post
Old 22nd November 2011, 12:03   #4
Anders
Moderator
 
Anders's Avatar
 
Join Date: Jun 2002
Location: ${NSISDIR}
Posts: 5,332
Quote:
Originally Posted by Yathosho View Post
i know unicode isn't official, but unlike the official build it makes the impression of progressing. despite svn commits, there haven't been new versions in two years - and isn't that against the open source mantra of "release often, release early"? even a service release with updated plugins would be better than no release and would send a sign to developers that are uncertain about nsis' future and tend to switch to the unicode build. anyway, this is to be discussed elsewhere.
There will be a 2.47, alpha by xmas if we are lucky but there is no rush and no specific target date. Which new feature from SVN is so important that you need a release right now? Even if we wanted to do a release today we can't since there are at least two show stopping things that need to be fixed before a we can do a release. If you need a sign so bad, check the log, I am committing fixes and features almost every day.


Quote:
Originally Posted by Yathosho View Post
i was only referring to the experimental build, which you might give away via irc only. thanks to the wiki's history, one can access some older versions of the uac plugins and despite an annoying visual glitch one older version is doing the job for me (and it comes in ansi and unicode flavors)
There is no might, I believe I have given it out to everyone that asked on IRC. I have not tested the plugin, do you think I should post a totally untested plugin on the wiki? I'd rather work on 2.47, testing and debugging a plugin on a unsupported platform will have to wait...


Quote:
Originally Posted by Yathosho View Post
i'm not always happy with plugin maintenance in general. i'd like to see some guidelines for developers that suggest certain ways of how to publish a plugin (e.g. use of wiki pages, version history including downloads for old versions, licensing, availability of source code, documentation standards)
Everything is zlib unless stated otherwise. I tried to come up with a standard wiki header for plugins but it does not seem like anyone is following my lead but it is a wiki so if you are unhappy there is nothing stopping YOU from fixing things...


Quote:
Originally Posted by Yathosho View Post
i did due to the lack of documentation. needless to say this isn't ideal, which is why i'd like to see old versions of the plugin still being available for download (without digging through the wiki history) and a newer version without documentation marked experimental/beta/etc.
The syntax changed after I wrote that html readme so it is no longer part of the docs (It used to document the exact behavior of the export functions but this really limits future changes and features). The code example on the wiki shows the intended usage, if you feel more documentation is needed you can edit the wiki or send me a suggestion of what you think the docs should look like...



Quote:
Originally Posted by Yathosho View Post
in a sense i don't really care what it says, as i probably wouldn't have the time to read it. i don't how this is different on slow computers, but if the banner appears there should be some feedback on what is going on. so why not just put a status message saying what's actually happening (e.g. "executing setup with elevated rights")
In most cases you are on the secure uac desktop so you can't really read any message, the uac prompt itself is a indicator of what is happening.

IntOp $PostCount $PostCount + 1
Anders is offline   Reply With Quote