At Mystic we’ve used our little pastebin experiment to teach on building code with Apache Wicket. We plan to continue this tradition in the near future talking about some of the new items in MysticPaste.com’s feature list:
- Raw Text (for copy and paste)
- Using the JavaScript-based SyntaxHighlighter and tossing JaSHi. Show me a Java-based syntax highlighter with as clean an interface and respectable highlighting, and I’d prefer it. Searches returned nothing though.
- Send to Twitter – follow us @mysticpaste and let more people know about your paste and get solutions
- Comments – each paste can have any number of comments attached to it. the owner of a paste could comment on what problem he’s encountering, and get multiple comments about solutions. Email address is never shared anywhere.
- Line Number Highlighting – if you’d like to highlight certain lines in your paste just add another parameter, comma-separated, with the line numbers (e.g. /view/10/4,5,10 or /view/10/4-10,15-20)
- Abuse Reporting – it happens all the time, spam fills a pastebin, we’ve added a few measures to combat this nuisance along with a “Report Abuse” function which takes the paste out of the history
- Code Refactoring – nothing to do with the UI, but there have been a few changes and enhancements under the hood.
With all of that in mind, we think those are pretty great updates to an already fantastic tool. What would you like to see in the pastebin next? image support? diff support? durations to keep a post? something else?
{ 4 comments… read them below or add one }
First: fantastic job, guys! I’m rolling our first Wicket project internally at our company and have struggled with a lot of minor things. Your work with MysticPaste and this tutorial is awsome. Now, I can go back and compare, and pick up a tip or two from your work. Cudos!
I noticed the currently checked in code seem to be broken, in that if running the tests, it chokes on missing “twitter.username” from the configuration.
I use MyEclipse and have run “mvn eclipse:eclipse” to setup it up for eclipse. I then later found that in order to have the config right, I had to do a “mvn:clean deploy -P DEV”.
Btw, your tutorial briefly mentions “-P PROD” where “PROD” isn’t a filters-PROD.properties file.
So, are these inconsistencies simply not checked into the repo, or do I have to do anything else to get it up and running?
Also, there’s no sql script to set up the database, so I wonder if it will automagically be created by hibernate?
Cheers,
/Peter
Congratulations on rolling out a new project with Apache Wicket! It’s definitely a worthwhile endeavor and a whole lot of fun. Glad the tutorials and the pastebin are providing some benefits to the process.
I haven’t run the tests since last week, so I’m not surprised they broke. You can add an application-override.properties file with “twitter.username” and “twitter.password” entries to get it running.
The tutorial is probably using some intention to create PROD filter, and we only push it from LOCAL to DEV. You can safely ignore that, or add that filter as well. Another possibility you can see from using the tool, is to just use Spring’s PropertyPlaceholder’s and let Spring do the replacing with a supplemental properties file.
There’s a maven plugin for setting up the hibernate database, and the configuration as written should auto-create the tables.
fantastic work
but definately please add a delete function & also if possible a timeout you can set by default (hopefully it’ll remember settings via a cookie)
great suggestions. i’ll add them to the wishlist and see when we can get some time to add them. we always take patches if you’re so inclined