@SimonAndréForsberg I think this might be more a matter of which properties should be sent to the client. The only thing the client needs to work with the card is an ID, and then it needs some properties to display. I was imagining this working like this...
Each card would have a function named something like getDisplayProperties, and this would return a table with just the stuff the UI needs to display the card. This table gets sent over the wire, and the UI drops the properties of the table into an SVG template... for example if the tables have "name," "description," "health," and "defense" properties, the SVG files would have matching tokens like {name} and {health}, and the data would be inserted with simple replacement
The SVG files themselves would be part of the mod, sent to the client at the beginning of the game (there would probably only be one or two "templates" for an entire game), so there is no problem with the results of getDisplayProperties (or whatever) matching the placeholder values in the SVG
@skiwi Even these commits are not totally 'finished'. There is a lot of things that needs to be added. It compiles, but it still isn't totally possible to play a network game
I am running into this error of:
$ git push heroku master
Warning: Permanently added the RSA host key for IP address '50.19.85.132' to the list of known hosts.
! Your key with fingerprint b7:fd:15:25:02:8e:5f:06:4f:1c:af:f3:f0:c3:c2:65 is not authorized to access bitstarter.
I tried to add t...
> Webhooks are delivered with a application/x-www-form-urlencoded content type using HTTP POST, with the body including a payload parameter that contains the JSON webhook payload in a URL-encoded format.
Caused by: java.lang.IllegalStateException: Cannot convert value of type [java.lang.String] to required type [com.skiwi.githubhooksechatservice.travis.events.BuildEvent]: no matching editors or conversion strategy found
This could be done with a custom editor, that converts the JSON into a UserProfile object:
public class UserProfileEditor extends PropertyEditorSupport {
@Override
public void setAsText(String text) throws IllegalArgumentException {
ObjectMapper mapper = new ObjectMapper();
...
I am trying to figure out why I can't receive a request from a jQuery.ajax call when then Spring @Controller handler method includes a @RequestBody annotation. Consider the following:
HTML/JavaScript:
<form id="foo" action="/baz">
<input name="bar">
</form>
<script>
$(function() {
var ...
@Malachi Cannot seem to reach you, read your question two days ago... There should be a fair explanation on the github site itself if you are familiar with Tomcat, if not catch me or @SimonAndréForsberg at some point
What if one developer only wants to finish half the feature, and let someone else take care of the rest? Then it does not necessarily build successfully.
Sometimes I hear people saying something like "All committed code must be working". In some articles people even write descriptions how to create svn or git hooks that compile and test code before commit.
In my company we usually create one branch for a feature, and one programmer usually works ...
I would never make big not staible commit. I prefer to make always small commits so i can always find out in history what happend. And so on Jeff, ask yourself what would happend if you commit hundreds of modified files with hundreds new and changed lines of code in one commit? No one except you would not understand what happend. Maybe it is better to make commits while developing? — Astronavigator Nov 14 '11 at 11:20
> Each branch should have the option to opt-in for travis support, most likely via a small configuration file. This should be by default enabled on the master branch.
This could be done with a custom editor, that converts the JSON into a UserProfile object:
public class UserProfileEditor extends PropertyEditorSupport {
@Override
public void setAsText(String text) throws IllegalArgumentException {
ObjectMapper mapper = new ObjectMapper();
...
I am trying to figure out why I can't receive a request from a jQuery.ajax call when then Spring @Controller handler method includes a @RequestBody annotation. Consider the following:
HTML/JavaScript:
<form id="foo" action="/baz">
<input name="bar">
</form>
<script>
$(function() {
var ...
