-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a spec #4
Comments
This should go in a top level readme but for now here's where the idea for this repo started: http://irclog.greptilian.com/friendlyjava/2015-03-28#i_105286 All the REST stuff is something I added because I felt like it. And because I find Jersey more fun than JSF. :) Some more discussion at http://irclog.greptilian.com/sourcefu/2015-04-06#i_107536 but let's say for now your address book should allow you to enter a name and phone number. :) But yes there absolutely should be a spec or at least some more guidance! Thanks for opening this issue! |
Here's my original idea:
|
I think you should stardardize the front-end a bit. like decide if it's all ajaxy or not It would be hard to compare frameworks if, eg, one is pretty much only doing ajax, and another is proccessing form submissions |
The plan was to keep it really simple. If it's up to me, I'd say no ajax. |
I think we should do two thigns:
|
I don't think an API should be required. What's the point of that? |
Yeah I dunno really; I just don't think you're demonstrating much by not having an API and just rendering a bunch of HTML depending on the Request path :) |
"just rendering a bunch of HTML"?! No, it's about listing, adding, deleting and changing entries in a contact list on the server side. |
Yeah I know :) But to me I see the two as being very different. |
A few separate comments: A. B.
C. |
prologic: I'm not sure what you're talking about. |
@aditsu |
Um.. I don't think it's feasible to have a common stylesheet for all implementations, unless we standardize the html structure of every page. I'm just saying: let people use a little css if they would like to. Unstyled pages, especially with tables, can look pretty ugly. |
Since this project is focused on comparing/demonstrating the server-side technologies, the backend, I don't see any reason why we shouldn't standardize the html of each page. Or at least offer a default. |
That seems quite restrictive, and some things may be a natural fit in one framework but inconvenient in another one. For example, two frameworks could provide different default ways to list a bunch of items or to show error messages, including different css class names. Some implementations will have to do more work to customize the generated html, which they would not normally do in a real project. |
ok, soften it to: "offer an example" |
Great discussion! Everyone should pay attention to the summary by @aditsu at #4 (comment) because it does capture the original idea. I would say that a database is not a requirement but some sort of server-side persistence is. Also, as I just commented at https://github.com/pdurbin/addressbookmvc/pull/12/files#r33887453 I think we should de-emphasize anything about a RESTful API in any kind of readme describing the goals. The implementation still needs to function if you disable the RESTful API. The emphasis of this project is a comparison of building the same simple web application using a traditional server-side approach to build the user interface. Recently I was listening to http://ttlpodcast.com/episodes/emily-nakashima.html with @eanakashima and @rmurphey and this quote should provide some inspiration:
|
If we create specification, it would make it easier to create examples in new languages/frameworks (and test them).
This could be done iteratively with several levels depending on the time/effort available:
The text was updated successfully, but these errors were encountered: