The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
||||
|
||||
I much prefer text-based instructions than HTML-based ones. It's just easier to copy/paste from a text file and follow instructions, plus it means not having to open a browser window to view the instructions.
BUT, I still say go for it. Some coders might want to offer text-based and html based so that everyone is happy. |
#12
|
||||
|
||||
Make it generate images instead of text.
Text ones are fine for the most part as long as everything is seperated clearly. HTML would be much better though, if you can handle the reduce in speed. The copy pasting would depend on the CSS (i think), so it just depends on how you do it. Useful, but not everyone would use it, so go for it. |
#13
|
||||
|
||||
As long as it doesn't add a tag-line (eg. powered by ??) and allows us to create our own templates - I'd be the first to say that I would use it.
If I had something like this already I'd be releasing more addons. Just starting a list for you...
|
#14
|
|||||||
|
|||||||
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
2. Umm... Textarea does not show code indentations. Or does it? Because if it does not, then it would be a hard to read code. 3. What do you mean? Color where? |
#15
|
||||
|
||||
Quote:
Quote:
Quote:
Quote:
|
#16
|
|||
|
|||
Quote:
Quote:
Quote:
What is even better is the fact that a textarea also supports colored text |
#17
|
||||
|
||||
Quote:
Download my GTP ALLOW GROUP TO READ TITLES/ NOT CONTENT installation file (link in sig) and you will see an example of what I mean by 'color coding'. |
#18
|
||||
|
||||
Quote:
|
#19
|
||||
|
||||
I say go for it. Readmes are a butt pain to do however a very important butt pain to do.
If you dont mind me saying, the generated header, footer, content block openers, closers and areas should all be templates that the user can customize. Otherwize it becomes as much of a burden to tweak the HTML output as it does to just write your own - all I do is use the exact same shell and change the content accordingly. I would also suggest a standard 'dont upload' folder that will hold the generated css and associated images. The generator should only need to accept something like: 1- Project name 2- Version 3- Link & title to release thread 4- Bookmarks to intall, upgrade, uninstall, settings and quick start blocks (actually, each of these could be specified by settings) 5- An infinate number of information blocks Templates should be something like: 1- Header 2- Navigation 3- Content block 4- Footer THen each project should be persisted to the db where you can recall, edit and regenerate based on project. Hope you dont think Im trying to tell you how to do it - Im more or less thinking aloud from my experience writing them (which isnt vast in any sense). Anyhooo - hope any of these suggestions can help. I would use it for sure if it did. O yea, on a side note, I second the dislike of copyright notices visible to the end user. Sure we all want our names up in lights - however I generally avoid installing or using anything with copyright notices. For 1, they make it easy to identify easy targets if security holes are ever discovered (though I know that isnt really the case here) for another - why bother? I dont need the hundreds that have installed my stuff to have to parade my name. If users want it - they know where they can get it... here Again, just my 2 yen (which doesnt add up to much with the exchange rate)... I hope it helps. nJoy |
#20
|
|||
|
|||
Ok, then, I will not put it in footer, but instead in a 'generator' meta-tag where it is invisible
I do not intend to make an 'edit' feature in the first version, but maybe later I will if I come up with an easy way to store data in a text file in a way that a program can easily parse into blocks and display. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|