Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Source Formatter
Ceniza:
--- Quote from: Michael ---What it would be also good, would be the possibility to define and register new styles. In this was users could define more than one custom style.
--- End quote ---
That could even be considered a Feature Request for the current plugin, but if any of you do that it'd mean pending work for me (right, I'm the maintainer of the plugin, but some bug reports and requests are for AStyle itself, not the plugin) :P. I'll have it in mind :)
--- Quote from: Michael ---IMHO, the code should also thought extensible and scalable to allow integration of e.g., another parser.
--- End quote ---
IYHO, you still insist (I agree, but it'd be even more work) :)
If this plugin goes somewhere (instead of just converting the current file in a (token, lexeme) pair as it does now), it could have the same luck of the CodeCompletion plugin (redisign) :P. I wonder if Rick would like to suffer with this one too... :twisted:
--- Quote from: thomas ---The AStyle way is not so bad actually, it is simple and it works. But there are just a few things which AStyled does not do the way I like it (for example, it compresses white space in comments and around '=', and always puts {} in a new line, so if you spend a lot of time laying out things properly, the code formatter destroys it later). Also you can only configure everything from hand, or nothing, which is annoying (for example, I like the way ANSI style looks, but I don't like spaces for indentation).
--- End quote ---
I've had it in mind since you sent me that PM, so don't worry. If it gets somewhere I'll try to get that working... eventually :)
--- Quote from: thomas ---Why don't you make a simple "choose one out of n" interface (list box, for example). The actual configuration is read in from a config file, and you just provide 3-4 such configs. If somebody wants something different from ANSI, Gnu, or K&R, then he can write his own config and is not limited to a stiff GUI. Most people will use one of the default sets, so they have a 1-click configuration.
--- End quote ---
So, have a simple "choose one of..." interface and save the stiff GUI for customization so everybody will stick with the 3-4 configs. Understood :P
(Oh, and thanks, you just suggested the name for the customization button: "Stiff GUI" :))
--- Quote from: thomas ---... (designing a GUI takes 90% of your time, but only 10% of the people use it 1% of their time...).
--- End quote ---
I love that sentence, but I bet it'sn't yours :wink:
It's now time to focus on the Stiff GUI...
thomas:
--- Quote from: Ceniza on January 16, 2006, 08:40:28 pm ---
--- Quote from: thomas ---... (designing a GUI takes 90% of your time, but only 10% of the people use it 1% of their time...).
--- End quote ---
I love that sentence, but I bet it'sn't yours :wink:
--- End quote ---
I guess you could call it a free interpretation of the good old 90/10 rule, or of the hot spot concept which derives from it :)
Michael:
--- Quote from: Ceniza on January 16, 2006, 08:40:28 pm ---
--- Quote from: Michael ---IMHO, the code should also thought extensible and scalable to allow integration of e.g., another parser.
--- End quote ---
IYHO, you still insist (I agree, but it'd be even more work) :)
If this plugin goes somewhere (instead of just converting the current file in a (token, lexeme) pair as it does now), it could have the same luck of the CodeCompletion plugin (redisign) :P. I wonder if Rick would like to suffer with this one too... :twisted:
--- End quote ---
Sorry :oops:. I do not want to make you crazy about my extensibility and scalability bla bla :D.
In a previous project, I have had several problems in hard-coding things and do not thinking about extensibility/scalability. I still remember the nights where I was re-working my classes...... :roll:
May be you can make your hard code parts easier to be successively re-coded. Of course, if this does not mean too much additional work for you :D.
Michael
yop:
--- Quote from: thomas on January 16, 2006, 09:08:14 pm ---
--- Quote from: Ceniza on January 16, 2006, 08:40:28 pm ---
--- Quote from: thomas ---... (designing a GUI takes 90% of your time, but only 10% of the people use it 1% of their time...).
--- End quote ---
I love that sentence, but I bet it'sn't yours :wink:
--- End quote ---
I guess you could call it a free interpretation of the good old 90/10 rule, or of the hot spot concept which derives from it :)
--- End quote ---
Funny I've only read the Meyer's 80-20 law
thomas:
--- Quote from: yop on January 16, 2006, 09:09:48 pm ---Funny I've only read the Meyer's 80-20 law
--- End quote ---
I guess Meyers was not even a child when they made the 90/10 rule. It is a really, really old rule, dating way back before computers were invented :)
On an interesting side note, the X Window system's design philosophy follows a kind of 90/10 rule, too, which is addmittedly quite clever. It says something like "if you can get 90% of your features implemented with 10% of the trouble, then leave it at that".
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version